How the Order Orchestration and Order Promising Processes Use the Collected Planning Data
You perform data collections to populate the planning data repository. In addition to being used by Supply Chain Planning processes, the collected data is used by Oracle Order Management order orchestration processes and by Oracle Global Order Promising processes.
Data Collections
You must perform data collections to populate the planning data repository, also called the order orchestration and planning data repository, with data from the Oracle source system or from a completely external source system. When you load data from an external source system, use the XLSM files to organize your data in the required format and then convert the data into CSV files. You can then upload the CSV files to the planning data repository.
Order Orchestration
Order orchestration processes use some reference data directly from the planning data repository. You must perform data collections for the order orchestration reference entities even if you are not using the Supply Chain Planning work areas.
Before collecting data from your Oracle source system, you must define at least one organization for the source system. After you have set up at least one organization, you must update the organization list on the Manage Planning Source Systems page and then enable at least one of the organizations for collections. If you have not enabled any organization, then the collections process ends with an error.
Order Promising
The Global Order Promising processes use an in-memory copy of the data from the planning data repository. When order orchestration processes send a scheduling request or a check availability request to Oracle Global Order Promising, the order promising processes use the data stored in main memory to determine the response to send back to order orchestration. You must refresh the Global Order Promising data store after every collections so that the main memory always reflect the current.