Troubleshoot Setup Problems in Order Promising
Get details about some troubles and ways to resolve them.
Trouble |
Shoot |
---|---|
The Create Order page typically displays a status for on-hand availability for each order line.
But I see a message instead.
This message indicates that there might a problem with a sourcing rule, assignment set, or ATP rule. |
If you already set up a global sourcing rule but you still get
|
The on-hand status for an order line on the Create Order page doesn't match what I have in inventory. Order promising uses sourcing rules, ATP rules, supply data, and details from the order to confirm stock levels when you add an order line. You must make sure your rules include the organizations that have on-hand availability. |
|
I can't find the item, inventory organization, or other reference data when I create my order promising rule. You must make sure this data is available to the order promising server. |
|
Extract Global Order Promising Replay Data
Use the Extract Global Order Promising Replay Data scheduled process to help troubleshoot problems that come up when you schedule a sales order, such as when you check availability, automatically schedule a sales order, promise an order again after collecting data, override a scheduled date, and so on. For example:
- Promising uses supply to promise a sales order but some other demand already consumed that supply.
- Promising can't accurately promise a sales order because there's isn't enough information about the demand, or some aspect about the demand exceeds predefined limits.
- Some other technical problem happens. We can use this scheduled process to help trace the conditions that cause the problem.
Try it.
- Go to the Order Promising work area, click Tasks > Order Promising Options, then make sure the Generate Replay Data Set option contains a check mark.
- Do the steps that cause the problem.
- Go to the scheduled processes work area, then run the Extract Global Order Promising
Replay Data scheduled process.
Use these parameters to filter the data that the scheduled process will look at.
Parameter Description Request Type Select the type of request that you need to troubleshoot. -
RepromiseScheduleSalesOrders
CheckAvailability
AutoSchedule
ScheduleSalesOrders
Request Date Select the date when Promising received the request to promise the item that you're troubleshooting. The scheduled process filters the dates that you can select according to the value that you set in the Request Type parameter.
Assume you check availability on June 1 2023 and on June 5 2023, and you set the Request Type to CheckAvailability. You can set Request Date to 2023-06-01 or 2023-06-05. For details, see Check Availability.
Requested-by User Select the user who made the request. The scheduled process filters the users that you can select according to the person who did the request.
Assume Diane Cho checks availability on June 1 2023 and June Tsai checks availability on June 5 2023. If you set the Request Type to CheckAvailability, and if you set the Request Date to 2023-06-01, then you can set the Requested-by User only to Diane Cho.
If the user runs the request from the Order Management work area, then Order Management might not send the user's name but instead send a generic value to Promising. If this happens, then set Requested-by User to that generic value.
Sales Order Number Select the number that identifies the sales order that you need to troubleshoot. The scheduled process filters the order numbers that you can select according to the values that you set in Request Type, Request Date, and Requested-by User.
Assume Diane Cho requests availability for sales order 76546 and for sales order 76546 on June 1. If you set Request Type to CheckAvailability, Request Date to 2023-06-01, and Requested-by User to Diane Cho, then you can set Sales Order Number to 76546 or 76546.
Replay Key Select a value that uniquely identifies the request to promise an item. The scheduled process filters the values that you can select.
If an application sends the same request to promise an item more than one time, then Promising uses a unique, sequential value to identify each request. Select the highest value to troubleshoot the most recent request.
All parameters are required.
-
- Notice that the scheduled process creates the GOPReplay_replayKey zip file. It includes the ReplayHeader_replayKey csv file and the ReplayData_replayKey csv file.
- Remove the check mark from the Generate Replay Data Set option on the Order Promising Options page. You must disable this option before proceeding. Leaving it enabled over a longer period of time might affect performance in your deployment.
- Save the GOPReplay_replayKey zip file to your hard drive, then send it to your Oracle product team for analysis.
- Work with your Oracle product team to resolve the problem.
For important details, see Guidelines for Using Scheduled Processes in Order Management and Extract Global Order Promising Replay Data.