Professional Documents
Culture Documents
Agenda
Introduction Discuss Key New Features Questions and Answers
Key Features
Cascading Attributes from Header to Lines Customer Acceptance Deferred COGS and Revenue Exception Management Multi Org Access Sales Agreements Actual Ship Date Parallel Pick Release
Cascading Attributes
Overview
Cascading Attributes
Setups
Setup the Profile Option OM: Sales Order Form: Cascade Header Changes to Line
Cascading Attributes
Setups
Enable the Cascading Attributes. Setup Quick Codes Order Management Type OM_HEADER_TO_LINE_CASCADE
Customer Acceptance
Overview In high tech industries like Telecom, the order process may not end with the shipping of the goods and services to the customer. In many cases, the goods that are shipped might have to be installed, tested, and accepted before invoicing and revenue recognition. There is no feature in R11 to record Customer Acceptance.
Customer Acceptance
Overview
R12 Provides a new feature Revenue Contingency which can be used for pre billing or post billing customer acceptance.
In Pre-billing acceptance, the line gets invoiced, closed and revenue recognized after the acceptance.
In post Billing acceptance, the line gets closed and revenue recognized after the acceptance.
Customer Acceptance
Overview
Process diagram
Customer Acceptance
Overview
Invoice Pending Acceptance is New in R12 Can be used as Pre billing Acceptance
Customer Acceptance
Close Line Pending Acceptance is the new feature in R12 Can be used as Post Billing Acceptance
Customer Acceptance
Setups
Enable OM System Parameter Enable Fulfillment Acceptance Setup System Parameters Define ENABLE_FULFILLMENT_ACCEPTANCE
Customer Acceptance
Setups (Contd..)
Define a Deferral reason Customer Acceptance in the Revenue Management . Specify the removal event. There are 5 removal events
Define an assignment rule to assign the deferral reason to a parameter like receivables transaction type, customer, customer site, item etc.
Customer Acceptance
Setups (Contd..)
Deferral Reason
Specify one of the following 5 Create an assignment rule removal events to the deferral reason to associate the deferral reason to a parameter Contingency Expiration Bill to customer
Installation
UT Customer Acceptance
Pre-billing acceptance Customer creditworthiness Delivery
Customer Acceptance
Invoicing Payment Proof of delivery
Invoice Type
item Ship to customer Accounting Rule
Customer Acceptance
Usage
1) 2) 3) 4) Customer Acceptance is recorded by user in the OM in the order header or order lines. It is not possible to record acceptance for partial quantity. Either accept or reject full qty. The acceptance can be recorded explicitly by the user or implicitly by time out feature (like 30 days from shipping etc.) Once the acceptance is recorded, the line will progress to invoicing and close in the case of pre-billing or just close after post billing.
Customer Acceptance
Usage
A sales order with pre-billing customer acceptance
Customer Acceptance
Usage
Customer Acceptance
Usage
Use Additional Line Information or Order Information to record customer Acceptance
Customer Acceptance
Usage
Deferred COGS
Overview
Accounting Standards stipulate that COGS and Revenue are recognized in the same accounting period.
In R12, a new feature was provided to invoke deferred COGS instead of COGS upon shipment. When revenue is recognized upon customer acceptance or a deferral reason, then an accounting transaction is created to hit the COGS account. COGS will be recognized to the same percentage as the revenue.
Deferred COGS
Setups
Setup deferred COGS account in inventory organization Setup Organizations Inventory Other Accounts tab
Deferred COGS
Application
Exception Management
Overview
R12 provides a concurrent Program to preview and retry stuck transactions (due to errors in workflow)
In the Preview mode, a log is generated to give the reasons for the errors. In the execution mode, the error WFs are retried
A concurrent Program was provided to retry these error WFS. The Program name is Retry Errored Workflow Activities
Schedule to run this program probably once in a day.
Exception Management
Usage
Sales Agreements
Overview BSAs are renamed as Sales Agreements in R12 Sales Agreements have been enhanced to handle PTOs
Questions
Thank You
Ravi.sagaram@utstar.com sagaram@hotmail.com 630-849-9888