Professional Documents
Culture Documents
By setting the cost cutoff date for a cost accounting period, you can manage which
transactions are processed in that period, including backdated transactions. The following
examples illustrate how the cost processor sets the accounted date for backdated
transactions. Assume that the current date is November 2, the cost cutoff date is October
31, and the following costed and uncosted transactions are in process:
Below, the inventory transaction is backdated to position A. The transaction will be costed
with accounting date B before the transactions 2 and 3 are processed.
Below, the inventory transaction is backdated to position C. The transaction will be costed
with accounting date C after the transactions 2 and 3 are processed.
Below, the inventory transaction is backdated to position D. The transaction will be costed
with accounting date D after the cost cutoff is moved past October 31.
organizations if the start of the new costs is to be January 1 2012, that is the date that is
entered. New standard costs can then be established prior to January 2012, in December
2011 for example. These costs will not impact the December costing activities as they will
not be active until Jan 1 2012. No transactions that occur after the start of the day January
1, 2012 are costed.
This will allow the accountants to complete the costing for the December transactions, close
the period, and run the reports for review. A standard cost update can be performed using
the new cost type for January 2012. This will update the cost of the costed items up to the
end of the day (midnight) December 31, 2011. The reports can then be re-run with the
same quantity and newly updated costs. Still NO January 2012transactions will be costed.
This is true whether it takes a few days in the next period or a few weeks to finish the
costing of the previous period. The uncosted transactions will remain in the
MTL_MATERIAL_TRANSACTIONS with costed_flag = N waiting for a cost worker to
process them. The Cost Manager will spawn no cost worker until the Cutoff Date is
changed. To cost the January 2012 transactions once December 2011 is properly closed,
the Cost Cutoff Date is changed. This can be changed to the start of the next period or next
quarter or next year---whenever the rates need to be changed next. Once changed the cost
processing begins for the transactions that have been waiting. For standard costs the
processing of the transactions is immediate.
For Average, FIFO, and LIFO costing the process takes longer because of the need to
process the transactions sequentially to keep the costs accurate. For Average, FIFO, LIFO
cost organizations , Rate Cost Types are created and the old rates are copied to that new
cost type. This rate will not be used for cost processing until the Cost Cutoff Date is
changed. The cost type and the cutoff date need to be changed to allow the new costs to
be used and the transactions can be processed for the new period. For Shipping
transactions, the costs also use the cutoff date. The shipment in the new period will be
uncosted. If another organization receives the shipment, the receipt will also be uncosted.
This is due to the fact that the receiving transaction requires the accounting distribution from
the sending organization. In standard costing, once the cutoff date is changed, the
shipments are costed immediately. In Average FIFO LIFO costing, the first uncosted
transactions will cause an error. Once the cost cutoff date is changed and the errored
transaction reset, the transaction will be costed first for the shipment and then for the
receipt. All subsequent transactions will then be processed as well.
Important Note: If this functionality is not required or desired, the Cost Cutoff Date field
must be BLANK. If there is a date entered in that field, no costing will occur on transactions
for that organization from that date onwards..