oracle R12中，订单已发运，订单每行的状态都为"已关闭"，但为何有些行生成了销货成本，有些行却没有生成销货成本呢？
PS：已经运行过"连接行程停靠站”请求以及 销货成本确认的三个请求。
看看这个帖子^http://www.orastudy.com/posts/217.html
在ORACLE R12中OM改进了销货成本与收入确认的流程。一般来说，根据成本收入确认原则，收入与销售成本都必须记录在相同的期间。以前版本中，Oracle对此没有强制性的要求，COGS分录产生是货物发运前，但收入在发票登记后生成，一般情况下，发出货到登记发票这个期间很短，所以一般对于成本和收入都会同时生成。
但实际可能会是，发票登记后，并不一定就产生收入了（一般记到未得收入），另外，货物发运后，也不一定就可以马上确认为销货成本（COGS），可能需要等到客户收到并接受了这个货物后才能确认。
基于上述情况，R12对于这个收入与成本确认流程进行了一些调整。
首先，新增加了一个科目，即：deferred COGS Account（递延成本科目），设置位置在组织参数的other accounts底下。大家可能会发现这个设置其实在11中也有，但11中是灰的。
这个科目什么时候发挥作用呢？当我们在执行完成shipping后，在11中会生产：
借：COGS
贷：子库存物料成本
12中就记到：
借：deferred COGS
贷：子库存物料成本
那什么时候发deferred COGS结转到COGS上呢？一会我们再看。
接下来的流程，我们会去生成invoice，那生成invoice时，如何产生收入的分录？说到这，R12中又引入了一个新的流程，这个流程里的设置会决定如果生成收入。这个流程叫Customer Acceptance（客户接受），这个流程图如下：
Customer Acceptance实际上就是你的对于你的发运货物如果确认，是说一发出去就默认客户就确认了（一般情况如此），还是说需要再手工去记录一下客户确认流程（可以由客户自己登陆self-service界面确认或由销售方手工输入确认信息），前一种叫Post-billing，后一种叫pre-billing，即：
* Pre-billing：SO shipping后，需要由客户接受，然后 invoice和revenue一起产生
* Post-billing：SO shipping后，可以马上运行开票程序，此时产生invoice和unearned revenue，然后在客户接受后，生成收入
关于Customer Acceptance如何设置，以后再单独叙述。
最后，运行三个请求：
* Record Order Management Transactions – 获得事务处理信息
* Collect Revenue Recognition Information – 获得收入确认信息
* Generate COGS Recognition Event – 结转deferred COGS到COGS
运行成功后，可以在material transaction中找到这笔结转的分录
在R12的OM改进了对成本与收入确认的流程(2008-03-18 14:04:38)
我们知道在企业经营活动中，根据财务制度的要求，对于收入与成本确认有很复杂的原则，这里就不去细讨论这些原则了。这里主要说一下我了解到的在R12中，可以更加灵活的对收入和成本进行确认。
一般来说，根据成本收入确认原则，收入与销售成本都必须记录在相同的期间。以前版本中，oracle对此没有强制性的要求，COGS分录产生是货物发运前，但收入在发票登记后生成，一般情况下，发出货到登记发票这个期间很短，所以一般对于成本和收入都会同时生成。
但实际可能会是，发票登记后，并不一定就产生收入了（一般记到未得收入），另外，货物发运后，也不一定就可以马上确认为销货成本（COGS），可能需要等到客户收到并接受了这个货物后才能确认。
基于上述情况，R12对于这个收入与成本确认流程进行了一些调整。
首先，新增加了一个科目，即：deferred COGS Account（递延成本科目），设置位置在组织参数的other accounts底下。大家可能会发现这个设置其实在11中也有，但11中是灰的。
这个科目什么时候发挥作用呢？当我们在执行完成shipping后，在11中会生产：
借：COGS
贷：子库存物料成本
12中就记到：
借：deferred COGS 贷：子库存物料成本
那什么时候发deferred COGS结转到COGS上呢？一会我们再看。
接下来的流程，我们会去生成invoice，那生成invoice时，如何产生收入的分录？说到这，R12中又引入了一个新的流程，这个流程里的设置会决定如果生成收入。这个流程叫Customer Acceptance（客户接受），这个流程图如下：
Customer Acceptance实际上就是你的对于你的发运货物如果确认，是说一发出去就默认客户就确认了（一般情况如此），还是说需要再手工去记录一下客户确认流程（可以由客户自己登陆self-service界面确认或由销售方手工输入确认信息），前一种叫Post-billing，后一种叫pre-billing，即：
- Pre-billing：SO shipping后，需要由客户接受，然后 invoice和revenue一起产生
- Post-billing：SO shipping后，可以马上运行开票程序，此时产生invoice和unearned revenue，然后在客户接受后，生成收入
关于Customer Acceptance如何设置，以后再单独叙述。
最后，运行三个请求：
- Record Order Management Transactions – 获得事务处理信息
- Collect Revenue Recognition Information – 获得收入确认信息
- Generate COGS Recognition Event – 结转deferred COGS到COGS
运行成功后，可以在material transaction中找到这笔结转的分录。
以下摘自国外某一博客：New Customer Acceptance Feature in Order Management in R12
CUSTOMER ACCEPTANCE
This is a new feature in which revenue generation and costing of goods sold is deferred until the customer accepts the invoice generated from AR.
A new field called ‘Deferred COGS A/c’ has been included in the inventory organization parameter form. where item is accounted before customer acceptance.
After acceptance, COGS account and Revenue accounts are hit to the extent of the cost and value of the items accepted by the customer.
This is an optional feature demonstrated in the screenshots below
New Customer Acceptance Feature in Order Management in R12
Thursday, April 30, 2009Customer Acceptance (Oracle Apps Release12 Feature).Customer Acceptance is new feature introduced in Oracle Application Release 12.Customers in some industries have need to defer invoicing and/or revenue recognition for shipped goods until the customer receives the shipment and formally accepts the material.
In Oracle R12 Customer acceptance/rejection can be captured from customers, customer service representatives, or from an external system.
Customers can perform. the acceptance in following manners.
- Log into the self-service Order Information portal.
- Import customer acceptance/rejection from an external system with Order Import/Process Order API.
- Record Acceptance /Rejection from Sales Order Form.
Oracle Order Management supports only full acceptance or total rejection for each outbound order line. One can set the number of days for implicit acceptance, after the product has been shipped.
A New System parameter “Enable Fulfillment Acceptance” has been introduced in R12 at Operating Unit level for this Purpose. Once this parameter is enabled, the Accounts Receivables API is called to invoke the rules engine to validate customer acceptance on every order line.
The basic business need is to defer invoicing and/or revenue recognition for the shipped goods till the customer receives the shipment and accepts the material.
Customer Acceptance functionality offers
1. Pre Billing and Post Billing Acceptance
2. Explicit and Implicit Acceptance.
3. It is either Full Acceptance or full rejection, as of now it doesn’t support Partial Acceptance.
4. It support ATP/PTO/KIT/Service & Standard item. Acceptance defined at the parent level (Model) only, and child will inherit that from parent (e.g. ATO/PTO Model).
As of now Oracle in not support Acceptance in RMA Orders.
Setup for Customer Acceptance:
1.Customer acceptance can be enabled at Operating Unit level through OM systemParameter: Enable Fulfillment Acceptance – Y/N.
2.We need to enable function security for a given responsibility for the following two
Functions:
a. Sales Orders: Fulfillment Acceptance – This ensures that the action attribute Fulfillment Acceptance is available in the Actions LOV.
b. Sales Orders: Update Acceptance Attributes – This allows for updating the acceptance attributes of Acceptance Name and Acceptance Expire days.These are attached to the sales order menu – ONT_ Sales_Order.
3.Define Deferral Reason for Pre – Billing Acceptance
Define ‘Deferral reason’ under Receivables Revenue Management set up
Navigation: Revenue Management Super User -> Contingency Search / Definition ->
it launches an HTML page.
Define assignment rules to assign the deferral reason to customer, site, item, etc.
a. For defining a Pre-billing Acceptance, use the deferral reason removal event as
Invoicing.
b. For defining a Post-billing Acceptance, use the deferral reason removal event asCustomer Acceptance.
c. For defining an Implicit Acceptance, we need to define the Optional time attributes – Event Attribute and Days added to Event attribute.
As shown above please note that Order Management supports Ship Confirm Date as only event attribute for the current release.
The Days added to Event Attribute gets defaulted as Acceptance Expire days inSales Order Line.
Note: The deferral reason defined in AR’s Revenue Management setup page is actually used as Acceptance Name in Order Management
Enable Folder fields for Customer Acceptance in Sales Order Form. as well as Quick Sales Order Form.
The Invoice Interface Workflow sub process handles sending interface data to Oracle Receivable for invoice and credit memo creation.It us ysed to handle pre-billing Customer acceptance. If an order line requires pre-billing Customer Acceptance, this sub-process will prevent the order line from being interfaced to Receivables.
Pre-Billing AcceptanceSales 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:1. Acceptance through Order Information Portal, click on Sales Order Actions –Fulfillment Acceptance from Header or Lines.
2. Through Order Import.
Implicit Acceptance:1. Deferral reason has to be defined in AR with event attribute as Ship Confirm date and expiration days.
2. An Implicit Acceptance Request set that records Implicit Acceptance consists of the following concurrent programs:
· Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance
· Revenue Contingency Analyzer for Post-billing, Implicit Acceptance
Process Flow (Explicit Acceptance).
1.Enter orders that need to be accepted by the customer and this acceptance is to be Recorded by the Customer Sales Representative.
2.View/update Acceptance fields on the order line. The Others tab of the sales orders line displays the folder enabled Acceptance fields.
3.Sales Order Acknowledgment Report prints Acceptance Required.
4.Ship Confirm the items mview the line status ‘Pending Pre-Billing / Pending Post-Billing Acceptance’.
5.Perform. Acceptance/Rejection.(Below is Example of Pre-Billing Explicit Acceptance).
6.View Acceptance Details in Sales Orders line.
Process Flow (ONLY Screen short) of Implicit Acceptance
