Import Count Sequences
Use the Import Count Sequences scheduled process to import an external application's count sequence records to process them in Oracle Fusion Cloud Inventory Management using the Cycle Count Open Interface.
Run this scheduled process if your company uses Oracle Fusion Cloud Applications, but your company's inventory organizations are managed by a third-party warehouse that uses a different system. For example, a Warehouse Manager can update a cycle count in Oracle Inventory Management with count sequences for items managed by a third-party warehouse.
The intention of this process is to make sure you insert the data (through data loading scheduled processes) into Oracle Inventory Management’s interface tables and then invoke the Import Count Sequences scheduled process to process them. Once processed, you can use the Cycle Count pages, to review the adjustments posted.
When to Use
Use the Import Count Sequences scheduled process when you’re executing a cycle count in Oracle Inventory Management based on items managed by a third-party warehouse. The third party provides the count sequences that are imported into Oracle Inventory Management.
INV_MATERIAL_TXNS_TEMP
table, you must run the Manage Inventory
Transactions scheduled process manually to process the cycle count
adjustments.Privileges Required
- Import Cycle Count Sequences (INV_IMPORT_COUNT_SEQUENCE)
Specifications
Specification | Description |
---|---|
Job Type | Ad hoc job. |
Frequency | Once for every third-party warehouse defined in the cycle count. |
Time of Day | If it’s a high-volume scheduled process, you might want to run the process during an off shift, so it doesn’t compete with other processes. |
Duration | Duration can vary based on the number of items at the third party. |
Compatibility | There should be only one instance of the job running at any time, and there’s no current functional need to run multiple instances of this process simultaneously. |
Parameters
Parameter | Optional or Required | Description | Parameter Values | Special Combinations Required | Notes |
---|---|---|---|---|---|
Organization | Required | The organization importing the count sequences. | Organization | None | N/A |
Cycle Count | Required | Name of the cycle count. |
Cycle count |
None | N/A |
Number of Child Processes | Optional | If the number of records inserted into the interface tables are huge, this parameter can be used to break the records into sets and launch multiple child jobs which can run in parallel to process all those records. The default value is 1. | Number | None | N/A |
Commit Point | Optional | Within each child job, you can define a number for which commit
happens. For example, if there are 10,000 records in the interface to be processed and we have used 2 child processes, each one will try to process 5000 each. We can commit the records for every 1000 records. In this case, the Commit Point will be 1000. |
Number | None | N/A |
Delete Processed Records | Optional | Use this parameter to decide if the successfully processed interface records should be deleted. | Yes No |
None | N/A |
Troubleshooting Information
- When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, and Release Process as provided by the Scheduled Processes work area.