Create Inventory Transactions
Use the Create Inventory Transactions scheduled process to process pending and stuck inventory transactions.
When to Use
Use the Create Inventory Transactions process to process pending and stuck inventory transactions. For example, you can process the pending and stuck transactions by providing the Transaction Header ID as an input parameter. You can find the Transaction Header ID on the Manage Pending Transactions page.
Privileges Required
- Create Inventory Transaction Process (INV_CREATE_INVENTORY_TRANSACTION_PROCESS_PRIV)
Specifications
Review the following before setting up this scheduled process:
Specification | Description |
---|---|
Job Type | Ad hoc job Scheduled |
Frequency | As required. |
Time of Day | Any time. |
Duration | Runtime of this process varies based on the number of inventory transactions and type of inventory transactions requiring processing. For example, inventory transactions for lot and serial controlled items can take more processing time. |
Compatibility | There should be only one instance of the Create Inventory Transactions process running at any one time. |
Parameters
Parameter | Optional or Required | Description | Parameter Values | Special Combinations Required | Notes |
---|---|---|---|---|---|
Transaction Header ID | Required | Enter the inventory transaction header ID. |
Transaction header ID |
None | 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 display in the process log file.
- You can manage pending transactions by navigating to the Manage Pending Transactions page. For additional details, please see the Manage Pending Transactions topic in the Oracle Fusion Cloud SCM: Using Inventory Management guide.
- When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, and Release Process as provided by the Scheduled Processes work area.
- It's recommended to periodically purge inventory interface transactions in error to keep the number of interface transactions below 1000.
- Ensure logging isn’t enabled. For example, Application Framework logging shouldn’t be enabled.