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. In Stock Out of Stock Low Inventory But I see a message instead. `No Data was Retrieved` This message indicates that there might a problem with a sourcing rule, assignment set, or ATP rule.	Create a sourcing rule and an assignment set. Create a global sourcing rule that uses the Transfer From source type. Create an assignment set and set its assignment level to Global, Item, or Category. Don't set it to Organization, Item and Organization, or Category and Organization. Assign your global sourcing rule to the assignment set. For details, see Source Your Supply Chain. Create an ATP rule. Create an ATP rule and set its promising mode to Supply Chain Availability Search. Select Search Components And Resources. Set the supply type to On Hand. Assign the ATP rule to your item or your organization. For details, see the chapter that starts with Assignments and Rules. Enable the MSP_DEFAULT_ASSIGNMENT_SET profile option at the site level. Use the assignment set that you created earlier in this procedure. See Manage Promising Profiles. If you don't have the privilege, send a request to enable the profile option. Send it to the administrator who manages setup tasks in order promising. Run the Refresh and Start the Order Promising Server scheduled process. If you already set up a global sourcing rule but you still get `No Data was Retrieved`, try this: Make sure you set the assignment level in your assignment set to Global, Item, or Category. If you set the assignment level to Item Category, then make sure you control that catalog at the master level, and that you assign that category.
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.	Make sure the assignment set has a sourcing rule. Make sure the assignment level for the sourcing rule doesn't include the value Organization. Make sure the sourcing rule includes the source organizations that might have on-hand availability. Collect data for the on-hand supply. Use the Supplies and Demands area of the Plan Inputs page to make sure you collected supply data.
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.	Collect data. Use the Plan Inputs page or the Maintain Supply Network Model page to verify that you collected data. Review the collected data on the Review Collected Order Reference Data page in the Setup and Maintenance work area.

Trouble

Shoot

The Create Order page typically displays a status for on-hand availability for each order line.

In Stock
Out of Stock
Low Inventory

But I see a message instead.

No Data was Retrieved

This message indicates that there might a problem with a sourcing rule, assignment set, or ATP rule.

Create a sourcing rule and an assignment set.
1. Create a global sourcing rule that uses the Transfer From source type.
2. Create an assignment set and set its assignment level to Global, Item, or Category. Don't set it to Organization, Item and Organization, or Category and Organization.
3. Assign your global sourcing rule to the assignment set.
  
  For details, see Source Your Supply Chain.
Create an ATP rule.
1. Create an ATP rule and set its promising mode to Supply Chain Availability Search.
2. Select Search Components And Resources.
3. Set the supply type to On Hand.
4. Assign the ATP rule to your item or your organization.
  
  For details, see the chapter that starts with Assignments and Rules.
Enable the MSP_DEFAULT_ASSIGNMENT_SET profile option at the site level. Use the assignment set that you created earlier in this procedure. See Manage Promising Profiles.

If you don't have the privilege, send a request to enable the profile option. Send it to the administrator who manages setup tasks in order promising.
Run the Refresh and Start the Order Promising Server scheduled process.

If you already set up a global sourcing rule but you still get No Data was Retrieved, try this:

Make sure you set the assignment level in your assignment set to Global, Item, or Category.
If you set the assignment level to Item Category, then make sure you control that catalog at the master level, and that you assign that category.

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.

Make sure the assignment set has a sourcing rule.
Make sure the assignment level for the sourcing rule doesn't include the value Organization.
Make sure the sourcing rule includes the source organizations that might have on-hand availability.
Collect data for the on-hand supply.
Use the Supplies and Demands area of the Plan Inputs page to make sure you collected supply data.

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.

Collect data.
Use the Plan Inputs page or the Maintain Supply Network Model page to verify that you collected data.
Review the collected data on the Review Collected Order Reference Data page in the Setup and Maintenance work area.

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.

Note: Run this scheduled process only when your Oracle product team asks you to run it or when you create a service request for Global Order Promising.

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 mumber 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.

More Help

For more help, see: