Create Receipt Accounting Distributions
Use the Create Receipt Accounting Distributions scheduled process to create pairs of debit and credit accounting entries for receipt accrual transactions, receipt delivery and putaway transactions, landed costs, interorganization transfer receipt transactions, and accounts payable transactions for receipts.
The receipt accounting distributions are staged within the Receipt Accounting sub-ledger and only posted to General Ledge after you run the Create Accounting process.
When to Use
You are encouraged to run this process on a daily cadence, maybe more than once per day. Your optimal cadence will depend on the trade offs between the use of compute resources and human effort to run and monitor multiple processes against the business need to see up to date accounting and reporting information.
Privileges Required
- Create Receipt Accounting Distributions (CMR_CREATE_RECEIPT_ACCOUNTING_DISTRIBUTIONS)
Specifications
| Specification | Description |
|---|---|
| Job Type | Ad hoc job Scheduled |
| Frequency | You are encouraged to schedule the process to run at least once per day. The process can be run more than once per day, but you should avoid scheduling processes more often than necessary for your business purposes. Avoid scheduling the process on a frequency that might overlap. Allow for a lag between the end of each scheduled process and the start of the next scheduled process. |
| Time of Day | Any time. You can choose any time of day such as at the end of the workday, after the end of shifts, after peak physical transaction activity, or during a lull in physical transaction activity. Another perspective can be to schedule the process to complete in time for regular business decision points, such as before the morning reporting recap of the prior day business. |
| Duration | Runtime of this process will vary based on the number of inventory and manufacturing transactions and type of transactions. |
| Compatibility | The process is designed to automatically detect incompatibilities and will gracefully branch around the incompatibility, log errors, and exit when necessary. Nonetheless, it is highly recommended to schedule the processes in such a way as to avoid overlapping process runs. |
Parameters
| Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required | Notes |
|---|---|---|---|---|---|
| Bill to Business Unit | Optional | You can run the process for a specific Bill to Business Unit or for all Bill to Business Units. If you schedule the process without selecting a Bill to Business Unit, the application intelligently processes the data for only those profit centre business units of the Bill to Business Unit to which you have data access and have pending transactions to be processed. | Bill to Business Unit name | N/A | If you don't have data access to the selected Bill to Business Unit, the process ends with Warning status. |
| Commit Limit | Optional | Use the commit limit to fine tune the size of processing sets. The default setting is sufficient for most typical cases. | Number | N/A | N/A |
| Number of Worker Processes | Optional | You can change the number of workers to fine tune performance. The default setting is sufficient for most situations. | Number | N/A | N/A |
Troubleshooting Information
-
You can view the status of the process in the Scheduled Processes work area.
-
Error and warning messages encountered while running the process are displayed in the process log file.
-
When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, Release Process as provided by the Scheduled Processes work area.
-
To run the process, you must have data access to the appropriate Business Unit and the Inventory Organization must be assigned to the Cost Organization. If you don't have data access to the selected Cost Organization, the process ends with a Warning status.