ERP R12 Workshop OM

NCR Oracle R12 UpgradeProject Kick off

09 Aug 2011

R12 OM Workshop

Delta features in Order Management

1. MOAC (Multi-Org Access Control)

2. Cascading of Attributes from Header to Lines

3. Customer Acceptance, Deferred COGS and Revenues

4. Change Management for IR-ISO, Copy Order and Hold Order Enhancements

5. Item Order ability

6. Scheduling / Reservation Enhancements

7. Recurring Charge feature

8. Credit Card Security and Encryption

9. Item Substitution, Delayed Scheduling and Visibility to BOM

Multi Org Access Control (MOAC)

MOAC (Multi-Org Access Control)

• Access Multiple Operating Units from a Single Order Management Responsibility

• Perform Tasks for Multiple Operating Units without changing responsibilities

• Setup transaction types, Setup system parameters

• Enter Quote, Orders and Returns

• Schedule Orders, Apply and Release Holds

MOAC: Setup

MOAC: Setup

• MO: Security Profile (Responsibility Level): Allows access to all OUs attached to the Security

profile from the Responsibility

• MO: Default Operating Unit (Responsibility Level): Defaults the Operating Unit as setup in this

profile option to the OM forms when using the responsibility

• The Operating Unit has been added as a hidden field in the following folder forms and UIs:

• Sales Order Form (Standard and Quick)

• Sales Agreement Form

• Order Information Portal (OIP)

• Other forms

MOAC: Enabled forms

Cascading of Attributes from Header to Lines

Cascading of Attributes

R12 provides cascading capability for a large number of attributes

OM Quick codes have the list of attributes which can be cascaded and are determined by

this lookup

Ability to chose attributes by enabling / disabling them

Profile option determines cascading behavior

Cascading of Attributes

OM: Sales Order Form: Cascade Header Changes to Line This profile determines cascading behavior. The profile has 3 modes:

Askme: The user is given choice to cascade or not at save

Automatic: The changes made at header level are automatically cascaded to lines

Manual: The user will have to manually change the values at line level – cascading is

disabled

Setup > Quick codes > Order Management OM_Header_to_Line_Cascade :This quick code has lot of attributes defined under for which

user can enable the same for cascading

Use can enable the attributes required to cascade during update by checking the ‘enabled’

checkbox

Cascading of Attributes: Setup

Cascading of Attributes: Setup

Processing Constraints

If an update constraint is violated for an attribute that has been enabled it will not allow update.

Cascade will in this case will be to No lines. Cascade is either to all or none lines

Only Supported in the User Interface

This feature is not supported in any API (Process Order)

Cascading of Attributes: Dependencies

Customer Acceptance, Deferred COGS and Revenues

Customer Acceptance

Customer Acceptance of goods and services

Pre-billing or Post billing Acceptance

Implicit or Explicit Acceptance

Support for multiple item types: Standard, Service, Kit, ATO or PTO Model

For Service, Kit, ATO or PTO Model: Acceptance contingency is defined at the parent level,

child line inherit acceptance information from the parent

This feature is not valid for Returns, Internal Orders

A way to defer invoicing and/or revenue recognition until the customer accepts

Determine when acceptance is required

View/Update Acceptance attributes on order line

Record Acceptance/Rejection (from Header or Line)

View Acceptance details on order line

Defer Invoicing/Revenue Recognition

Customer Acceptance: Setup and Process

Customer Acceptance: Setup

Enable Customer Acceptance

Can be enabled at OU level through OU system parameter: Enable fulfillment acceptance: Y/N

Define Deferral Reason

Define ‘Customer Acceptance’ Deferral Reason under Receivables Revenue Management

Setup

Define Assignment rules to assign the deferral reason to customer, site, item etc

Enable folder fields for Customer Acceptance – SO / QSO forms

Sales Order Lines Region – Others Tab

Customer Acceptance: Setup

Customer Acceptance: Process

Enter Orders that are subject to acceptance

View/Update Acceptance attributes in Sales Order Line

Sales Order Acknowledgement can print Acceptance required

Status of Shipped Lines will show status as ‘Pending Pre-billing / Pending Post-Billing

Acceptance’

Perform Acceptance or Rejection

View Acceptance or Rejection Details in SO line


Pre-billing Acceptance:

Sales Order line in Pending Pre-billing Acceptance

Record Acceptance – explicit or implicit

Line status moves to ‘Closed’ and line gets interfaced to AR

Invoice generation and Revenue Recognition happen subsequently

Post-billing Acceptance:

Sales Order line in Pending Post-billing Acceptance

Invoice Generation

Record Acceptance – explicit or implicit

Line status moves to ‘Closed’

Revenue Recognition happens once acceptance is completed


Explicit Acceptance

Customer or CSR logs into the Order information Portal (OIP) or uses order import to record

acceptance explicitly

Implicit Acceptance

Deferral reason has to be defined in AR with event attribute as ship confirm date and expiration

days

Implicit Acceptance Request has to be scheduled to be run at regular intervals

Request set has 2 concurrent requests – one for pre-billing and one for post-billing scenarios

Customer Acceptance: Explicit

Customer Acceptance: Implicit

Deferred Revenue and COGS Accounting

Deferred COGS account invoked instead of COGS account after line is shipped

Once the deferral contingency reason is removed, COGS account reversals take place

and Revenue is Recognized at the same time

Percentage of Revenue recognition dictates the percentage of COGS recognition

Accounting standards dictate that COGS and Revenue be recognized in the same

accounting periods

At shipping, Deferred COGS is debited

As revenue is recognized, corresponding % of Deferred COGS moves to real COGS

Setup: No setups in OM Module. Setup of Deferred COGS A/c in Inventory Module

Change Management for IR-ISO, Copy Order and Holds Enhancements

Change Management for IR-ISO

Changes to quantities and dates are allowed on IR as well as ISO. In case of change of

qty and date in ISO, it gets propagated to IR

Cancellations on ISO are allowed. They get propagated to IR

Priorities are propagated from IR to ISO

Different Order Types can be assigned to ISO using defaulting rules of OM

Change Management for IR-ISO: Setup and Process

Change Management for IR-ISO: Setup


POR: Urgent Flag maps to Shipping Priority

Shipping Priority Code that should be assigned when IR is flagged urgent

High Priority: The Urgent flag maps to high priority

Standard: The Urgent flag maps to standard priority

OM: View Intercompany AR Invoice

Yes: can be viewed from Sales Order UI

No: cannot be viewed from Sales Order UI


POR: Sync IR Need by Date with OM

Indicated whether to Sync Need by Date of IR with Scheduled Arrival Date of SO

Line

Yes: Can be updated

No: Cannot be updated

Change Management for IR-ISO: Process

Change Management for IR-ISO: Process – Propagation of Priorities

Change Management for IR-ISO: Process – Multiple Order types for ISO

Change Management for IR-ISO: Process – View Intercompany Invoice

Copy Order Enhancements

Copy Order from One OU to another OU

Copy the Shipment and Fulfillment Arrival sets also while copying

Create multiple order copies at the same time

Navigate to the newly created order after copy

Copy Order Enhancements

Hold Enhancements

Create Hold Sources with more attributes

Apply one hold source to multiple operating units

Automatic restarting of workflow after releasing of holds

Hold Enhancements

Item Order ability and RMA Based on Shipped Quantity

Item Orderability

To control who can order what goods and services

Allows to ensure and enforce that goods and services are sold only when fulfillment

conditions have been met

Allows to restrict goods and services to select customers, regions and locations

Allows control by 11 attributes – customer, customer class, customer category, end

customer, order type, sales channel, sales person, ship to location, bill to location,

deliver to location and regions

Allows to define inclusive and exclusive rules

Item Orderability: Setup and Process

Item Orderability: Setup and Process

Profile Option: ‘OM: Use Materialized View for Items LOV’ (Honors Item Orderability

rules)

No: LOV will display all items

Yes: LOV will display only items that are orderable

Item Orderability: Setup - Rules

Item Orderability

RMA based on shipped quantity: Setup

Order Management System Parameters

Set the parameter ‘Overshipment Invoice Basis’ to value ‘Invoice Shipped Quantity

Valid values for the parameter ‘Overshipment Invoice Basis’ are:

Invoice Ordered Quantity

Invoice Shipped Quantity

RMA based on shipped quantity: Setup

Scheduling / Reservation Enhancements

Schedule Orders Concurrent Program: Mass Scheduling

Additional flexibility now provides in R12 support for Scheduling / Rescheduling /

Unscheduling in batch mode

Flexible query parameters for Schedule Order program

Ability to schedule lines across Operating Units

Ability to specify a Schedule Date, Warehouse


New Scheduling Modes:

Schedule: Using Warehouse, Schedule date

Reschedule: Using Warehouse, Schedule date

Reschedule: Using request date

Unschedule

Schedule ATO Items without BOM: Setup and Process

Recurring Charges

Recurring Charges

View Charge Periodicity for an Order Line

The charge periodicity is a new attribute on the order line. It shows the frequency at

which customer account is charged. Charge Periodicity can be Weekly, Monthly or

Yearly

Order lines with charge periodicity are considered as recurring charge lines

Order lines without charge periodicity are considered as one-time charges

View Totals for Recurring Charges and One-time charges

Totals for each of the charge periodicities on the order

Total for one-time charges – lines without charge periodicity

Recurring Charges: Setup and Process

Recurring Charges: Setup

Profile Option OM: UOM Class for Charge periodicity

This profile determines the domain for the list of allowable charge periodicities. The

value of the profile is the UOM Class referencing the UOMs corresponding to the

charge periodicities

OM System Parameter ‘Enable Recurring Charges’

This parameter enables the Recurring Charges functionality in Order Management.

It cannot be disabled once it is turned on

Yes: Enable Recurring Charge functionality

No: Disable Recurring Charge functionality

Recurring Charges: Setup

Recurring Charges: Process

Credit Card Security and Encryption

Credit Card Security Code

Credit Card Security Code in OM Forms

Security Code is a new field in Regular/Quick SO and Order Import Correction forms

Validations for security code field during order entry

Validations for security code correctness during card authorization

Credit Card Encryption

For Centralized credit card and bank account information system. This is a subset of

Oracle Payments’ larger project called Fund Capture enhancements

Vital and sensitive data like Credit Card Number. Holder Name, etc can be encrypted

and stored in the centralized model owned by Payments

Credit Card Security Code: Setup and Process

Credit Card Security Code: Setup

There is no OM specific setup

Security Code can be setup as mandatory in Oracle Payments Application

Navigation path:

Oracle Payments Administrator responsibility

Oracle Payments setup > Shared setup > System security Options> Credit Card

Owner Verification Control Region > Require Security Code Control > Yes/No

Credit Card Security Code: Setup

Credit Card Security Code: Process

Credit Card Encryption

Credit Card, Bank Account and other sensitive date to be stored in encrypted format in

the central model

No credit card and bank account information in OM tables

Payment details stored in Oracle Payments owned central model referenced through an

identifier (Transaction extension ID) in OM

Credit Card Encryption: Setup

No specific setup in OM

Setups related to Encryption, Instrument masking and Security code are with Oracle

Payments application

System Parameter: ‘Enable multiple payments’ will always be enabled

Forms in OM having Credit Card Security Code field:

Regular/Quick SO (folder enabled)

Order Import correction forms

Credit Card Encryption: Setup

Credit Card Encryption: Process

Credit Card Type will now be called ‘Card Brand’

Changes are made to Credit Card Number LOV with additional attributes like Card

Brand, Holder Name, Expiration Date etc. available

Security code entry if set mandatory

Copy Order with Credit Card Payment attributes supported when Security code is not

mandatory

Credit Card Encryption: Process

Item substitution, Delayed Scheduling and Visibility to BOM

Item Substitution

Items can be substituted even post booking through Scheduling / Rescheduling in Sales

Order, Quick Sales Order and Scheduling Order Organizer forms

Using Planners Workbench of Advanced Supply Chain Planning (ASCP)

No additional setup is required for enabling Item Substitution post Order Booking

Item Substitution

Delayed Scheduling

Enhances the Auto-Schedule functionality in Order Management by introducing an

additional option to users when they chose auto-schedule

Enables scheduling when order is saved from either the regular or quick sales order

form

Ensures that MRP Calls will be made only when user actually saves the changes and

eliminates the data discrepancy between OM and MRP Demand

Improves the overall performance of the Sales Order processing by optimizing the

number of calls made to MRP

Delayed Scheduling: Setup

Profile option OM: Delay Scheduling

Dependent on the value of OM Profile Option OM: Autoschedule being set to Yes

This profile option value has to be set to Yes along with OM:Autoschedule which

should also be set to Yes

Visibility to BOM

Usually there is a time lag between booking and picking/shipping of Configurations

The BOM itself can get modified during this time interval which will then require

reconfiguration of the model on the Sales Order

This feature allows to view the latest BOM definition to enable to make changes to a

configuration until pick release

Allows to adapt to BOM changes in case of long lead-time orders

No need to cancel the order/line if bill of material changes for a configuration

Helps to reduce error by displaying the latest Bill of Material when changes are made to

the configuration

Visibility to BOM: Setup

Order Management System Parameters ‘Configuration Effective Dates’

Value ‘System Date till Booking’ (Existing and Default Value)

Value ‘Model Creation Date’ (Existing Value)

Value ‘System Date till Pick Release’ (New R12 value)

Visibility to BOM: Setup

Other Enhancements

Other Enhancements

New RMA Workflows

Ability to change PO Number after shipment

New concurrent request: Batch Pricing

New RMA Workflows

Ability to change PO Number after shipment

New concurrent request: Batch pricing

Reference

Oracle E Business Suite Release 12.1 Transfer of Information (TOI) Online

Training

THANK YOU

ERP R12 Workshop OM

Documents

Transcript of ERP R12 Workshop OM