Prevent Costing of New Transactions that are in a Pending Close Period
When a period is in the Pending Close status, any new transaction that falls in or before this period won't be staged in Cost Accounting or Receipt Accounting. After this period is closed or reopened, these new transactions will be processed with the current logic. Costing period statuses enable you to manage the timing for processing and accounting of transactions. You can now use the Pending Close status to hold transactions from being accounted in a given period.
Cost Accounting Period Statuses and New Definition of Pending Close
| Status | Old Definition | New Definition |
|---|---|---|
| Never Opened | Default status for new periods assigned to a cost organization and cost book. This status does not allow creation of distributions for transactions. | - |
| Open | Inventory transactions can be accounted in the open period. When the period is not open, inventory transactions can't be accounted in that period, but they will be accounted in the next open period. Both costing and general ledger periods must be open for a transaction to be accounted. If the costing period is open but the corresponding general ledger period is closed, the transaction can't be accounted and is held pending further user action. | - |
| Pending Close | The Pending Close status works same as the Open status and doesn’t include any additional validations or restrictions for transaction processing. | If the period is set to Pending Close, then transactions will be held from being accounted in that period. Any new transactions entered with a transaction date that falls in a period that's in the Pending Close status will be held pending further user action. |
| Closed | When you set a period status to Closed, you've the option of configuring the processor to allow closing even if all the validations don't pass. This enables you to decide when discrepancies aren't material enough to delay period close. | - |
| Permanently Closed | Closes the period for all types of transactions irreversibly. | - |
When the period is set to Pending Close:
- Any new transactions for the period entered in the source application will be held.
- You can set the period status back to Open and then process the transactions, so that those which fall into the period will be staged for accounting in that period.
- You can also set the status of the period to Closed. When the next period is set to Open, the transactions will be accounted in that period.
When the cost processor is run after a period is set to Pending Close, the transactions from the following sources will be held, and error messages will be logged accordingly in the Cost Accounting Process Errors page to provide you with full visibility into the held transactions:
- Trade Events/ASNs
- PO Receipts
- Inventory Transactions
- Manufacturing Transactions
- Resource Transactions
- Payables Invoices & Credit Memos
- Landed Cost Charges (Estimates and Actuals)
The Pending Close status can be used to signal to the application that the period close process is starting and hold transaction processing for any new transactions in the current period, ensuring tighter control and cleaner period closure. This prevents reporting discrepancies that could creep up after snapshots of data are taken due to new transactions being processed during this time.
After the period is set to Pending Close:
|
Transactions |
Process or Hold |
|
Anything already in costing interface tables at the time of Pending Close |
Process |
|
Anything in error or not fully costed at the time of Pending Close |
Process |
|
Any new transactions from source systems after period is set to Pending Close |
Hold |
|
Manual cost adjustments (perpetual average/receipt/layer costs) |
Process |
Note: Execution of these transactions in the real world will continue, such as inventory being issued to work orders or ASNs being generated.
Set the Period to Pending Close
When you set the period to Pending Close, with this opt-in, you will see the message: "All new transactions will be put on hold and processed in the next period after the current period is closed, or if the current period is reopened. Any existing transactions in the interface or error before pending close will continue to be processed".
Period status update on Pending Close
Cost Processing Errors
When you run the Create Cost Accounting Distributions process, held transactions from various interfaces will be reported. Click the transaction count to drill down to specific held transactions, organized by interface. This allows you to monitor and investigate any transactions awaiting processing due to the Pending Close hold.
Cost Accounting Process Errors
Transaction level drill down provides you full visibility to take further action:
- Close the period if you want to sweep these transactions to the next open period.
- Open the period again If you want to process the relevant transactions in the current period.
Cost Processing Transaction Errors
Example of Transaction Processing:
For a given inventory organization, let's assume that the cost cut-off date is 31st July. The transactions processed towards the end of the period, when the period is set to Pending Close on 27th July 12:00, would be shown as here.
| Transaction Number | Transaction Date | Pending Close Datetime Stamp | Cost Date | Period Start Date | Period End Date | Period Status | Hold Processing |
|---|---|---|---|---|---|---|---|
| 1 | 7/24/2025 12:00:00 PM | NA | 7/24/2025 | 7/1/2025 | 7/31/2025 | Open | No |
| 2 | 7/26/2025 12:00:00 PM | NA | 7/26/2025 | 7/1/2025 | 7/31/2025 | Open | No |
| 3 | 7/27/2025 10:00:00 AM | NA | 7/27/2025 | 7/1/2025 | 7/31/2025 | Open | No |
| 4 | 7/27/2025 12:00:00 PM | 7/27/2025 11:00:00 AM | - | 7/1/2025 | 7/31/2025 | Pending Close | Yes |
| 5 | 7/28/2025 12:00:00 PM | 7/27/2025 11:00:00 AM | - | 7/1/2025 | 7/31/2025 | Pending Close | Yes |
| 6 | 8/1/2025 12:00:00 PM | NA | - | 8/1/2025 | 8/31/2025 | Open | Do not process |
Because the cost cut-off date is in July, the transactions in August (which is open) don't get processed. If the cost cut-off date was 31st August, then the transactions for August will be processed, and the cost date will move to August.
Some benefits of this feature include:
- Operational Continuity: The period close process doesn't impact processing of transactions in the source applications, such as ASNs or issuing material to work orders can still happen in the background without disruption of the operations.
- Stronger Period-End Controls: You now have a way to signal to the application that the period close process is starting and any transactions coming in after the period has been set to Pending Close will be held from transaction processing.
- Improved Reporting Accuracy: Avoid accounting variances caused by late-arriving transactions after period close, ensuring cleaner financial and operational reporting.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Manufacturing and Supply Chain Materials Management
Tips And Considerations
-
Run the cost processor before changing the period status to Pending Close.
Make sure you run the following processes and then run the Create Cost Accounting Distributions process before moving the period to the Pending Close status. This ensures that the latest transactions are accounted for, and won't be held when the period is set to Pending Close:- Transfer Transactions from Receiving to Costing
- Transfer Transactions from Inventory to Costing
-
Make sure to run validations, such as pending interface and pending preprocessing, before changing the period status to Pending Close.
Period end validations
- This feature works best if only one period is in the Pending Close status at a point of time. If there are multiple periods in Pending Close, the latest pending close date will be used. This could cause multiple periods' transactions to be held until the latest period is closed.
- Any transactions entered before the pending close date will be processed, even if they are in an error state. Transactions created after the pending close date, even if they relate to a current or prior period, won't be processed.
- Revenue lines and COGS recognition will continue to process even after the period is set to Pending Close.
- Manual cost adjustments will continue to be processed even after the period is set to Pending Close.
- If the cost date has moved to the next period (because the cut-off date was in the next period), while transactions were on hold, then when those transactions are processed, the cost date of those transactions will also move to the next period.
- If the next period is open, held transactions may get processed in that next period if the cut-off date is in the next period.
- This feature is based off primary cost books. It isn't supported for ledgerless books.
Key Resources
- Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Materials Management guide, available on the Oracle Help Center.
- Oracle Fusion Cloud SCM: Using Supply Chain Cost Management guide, available on the Oracle Help Center.
Access Requirements
Users who are assigned a configured job role that contains the following privileges can access this feature:
- Create Cost Distributions (CST_CREATE_COST_DISTRIBUTIONS)
- Manage Cost Period (CST_MANAGE_COST_PERIOD)
- Manage Cost Processor Error (CST_MANAGE_COST_PROCESSOR_ERRORS)
- Create Receipt Accounting Distributions (CMR_CREATE_RECEIPT_ACCOUNTING_DISTRIBUTIONS)