Troubleshooting

This chapter covers the following topics:

Troubleshooting

This section provides a detailed explanation on Oracle Global Order Promising:

Troubleshooting

The following are error messages Oracle Global Order Promising users may receive, and how to troubleshoot these messages.

Note: The lookup codes are passed from the Oracle Global Order Promising API to the calling module, which displays the error messages to the users.

ATP Based on Collected Data Errors

Error Message Code Message Received When To Resolve this Message
Try ATP again later. 130 The complete / target collection or sales order collection is running. Wait until so_tbl_status in msc_apps_instances is set to Null or 0.
Summary Concurrent program is running. Try ATP later. 160 The Load Summary Based on Collected Data concurrent program is running in complete refresh mode, and ATP is offline. Wait until the Load Summary Based on Collected Data concurrent program completes successfully.
Invalid ATP rule or No ATP rule defined. 57 A valid ATP rule is not assigned to the item or the organization. Assign a valid ATP Rule to the item or the organization level. Run collections to collect the new item definition and organization setup.
Unable to meet the request quantity. 52 The infinite time fence is not defined in the ATP Rule, and Oracle Global Order Promising cannot find the entire requested quantity within the Manufacturing calendar of the organization. Define the infinite time fence in the ATP Rule or ensure that sufficient supply is available for the item within the calendar limits.
Unable to find a calendar date. 47

  • The calendar is not assigned to that organization.

  • The order request date is outside of the calendar.

  • The calendar is not built, not collected, or collected.

 Do one of the following:

  • Assign the calendar to the organization.

  • Extend the length of time on the calendar.

  • Build the calendar.
No APS instance defined. Set APS instance and run collections. 140 The instance for Oracle Global Order Promising is not defined in the Advanced Planning and Scheduling server. Define the instance to collect the data to the APS server. For details, see: System Setup.
Wrong Check ATP setup for product family item and member item. 180 Member items for a product family item have Check ATP set to Material, if the product family item has Check ATP set to Material. However, when the requested member item has Check ATP set to None, this error occurs. Set the Check ATP attribute to Material for the member item that failed with that product family.
One of the group elements or mandatory components failed. 19 Lines in a ship or arrival set receive this error when any line in the set has an error. For example, in a three line ship set where one line has the error Plan not Found, the other two lines get this error message. Correct the error for the line item that has an error message other than this error message. Then the entire ship or arrival set will not fail.
ATP has detected invalid objects. Contact your system admin. 220 Some ATP packages are invalid. Contact your database administrator. This error typically relate to applying the correct patch.
ATP processing error. 23 - Contact your system administrator to investigate the problem.
INV: Capable to Promise must be same at source and destination. 230 The profile INV: Capable to Promise is set differently at the source than at the destination. Set the profile INV: Capable to Promise to the same value in both the source and destination instances.
Cannot meet request date or latest acceptable date 53 Scheduling fails because the demand cannot be satisfied for the latest acceptable date, but the demand can be satisfied at a later date. Excess supply is required for this item.
ATP not applicable. 61 Item is not ATP capable. No action is needed unless the item should be ATP-capable.
No Sources. 80 Sourcing is not defined for that customer. Thus, Oracle Global Order Promising cannot select the shipping organization in the ATP Assignment Set. Globally define all organization sourcing rules and assign them to the appropriate levels for that customer in the ATP Assignment Set. Note that Bills of Distribution and local sourcing rules are not applicable.
This item is not collected. Please run Data Collection. 85 An ATP-capable able item was not collected. Run collections to collect the item.
No Assignment Set. 90 Both the MRP: ATP Assignment Set at source and destination are null. Define at least one assignment set. You must do this when you want Oracle Global Order Promising to recommend a shipping warehouse.

ATP Based on Planning Data Errors

Error Message Code Message Received When To Resolve this Message
Plan not found. 120 For Standard Items, this error is generated only when the plan is running or has errored out.
For the Multi-Level, Multi-Org ATO Model:

  • The plan that contains the model is not ATP-capable.

  • The model is not included in any ATP-capable plan.

  • The plan is running or has errored out.

 For Standard Items, the plan that contains the item is running or has errored out. Try ATP after the plan run has completed successfully
For the Multi-Level, Multi-Org ATO Model:

  • Make the plan ATP-capable and run the Analyze Plan Partitions concurrent program.

  • Define and run the plan to successful completion.

  • Try ATP after plan has run successfully.
Plan not found. ATP is calculated using collected data. 150 If standard items are not found in any ATP-capable plan, use collected data to find availability. No action is needed. If you expect the item should have a plan, make sure that the plan is ATP-capable and has been run successfully.
Run ATP Post Plan Processing concurrent program. 200 The ATP Post Plan Processing concurrent program has not been run for the ATP-capable plan. Run the ATP Post Plan Processing concurrent program. If you are not using demand priority based Allocated ATP or Summary Based ATP, make sure the related profile is set correctly.
Summary Concurrent program is running. Try ATP later. 160 The ATP Post Plan Processing concurrent program is still running. Wait until the ATP Post Plan Processing concurrent program has finished running.
MRP: Default Assignment Set sourcing not in sync with ATP Plan. 240 Only applicable for multi-level, multi-org ATO models: the sourcing defined for the model in the assignment set assigned to the profile MRP: Default Assignment Set is not the same as the sourcing defined in the assignment set used in the ATP plan. Only applicable for multi-level, multi-org ATO models: ensure that the ATO model has the same sourcing and is the same in the two assignment sets is used in profile and plan.
Unable to find a calendar date. 47 One of the following conditions occurs:

  • The calendar is not assigned to that organization.

  • The order request date is outside of the calendar.

  • The calendar is not built, nor collected, or both.

 Do one of the following:

  • Assign the calendar to the organization.

  • Extend the length of time on the calendar.

  • Build the calendar.
No APS instance defined. Set APS instance and run collections. 140 The instance for Oracle Global Order Promising has not be is not defined in the Advanced Planning and Scheduling server. Define the instance to collect the data to the APS server. For details, see: System Setup.
Wrong Check ATP setup for product family item and member item. 180 Member items for a product family item have Check ATP set to Material, if the product family item has Check ATP set to Material. However, when the requested member item has Check ATP set to None, this error occurs. Set the Check ATP attribute to Material for the member item that failed with that product family.
One of the group elements or mandatory components failed. 19 Lines in a ship or arrival set receive this error when any line in the set has an error. For example, in a three line ship set where one line has the error Plan not Found, then the other two lines get this error message. Correct the error for the line item that has an error message other than this error message. Then the entire ship or arrival set will not fail.
ATP has detected invalid objects. Contact your system administrator. 220 Some ATP packages are invalid. Contact your database administrator. This erroris typically related to applying the correct patch.
ATP processing error. 23 One of several possible errors occurred. Contact your system administrator to investigate the problem.
INV: Capable to Promise must be same at source and destination. 230 The profile INV: Capable to Promise is set differently at the source than at the destination. Set the profile INV: Capable to Promise to the same value in both the source and destination instances.
Unable to meet the latest acceptable date. 53 The scheduling fails because the demand cannot be satisfied for the latest acceptable date, but the demand can be satisfied at a later date. Excess supply is required for this item.
ATP not applicable. 61 Item is not ATP-capable. No action is needed unless the item should be ATP-capable.
No Sources. 80 Sourcing is not defined for that customer. Thus, Oracle Global Order Promising cannot select the shipping organization in the ATP Assignment Set. Globally, define all organization sourcing rules and assign them to the appropriate levels for that customer in the ATP Assignment Set. Note that Bills of Distribution and local sourcing rules are not applicable.
This item is not collected. Please run Data Collection. 85 An ATP-capable item was not notcollected. Run collections to collect the item.
No Assignment Set. 90 Both the MRP: ATP Assignment Set at source and destination are null. Define at least one assignment set. You must do this when you want Oracle Global Order Promising to recommend a shipping warehouse.
Options selected have exclusive sources. 350 Two or more options needed to build a configuration can only be sourced from different organizations. Review option-specific sourcing rules defined for your options to ensure that the configuration can be manufactured in at least one source.
No valid source for this configuration. 310 There option-specific sourcing rules do not match the sourcing rules for the model. Review the sources rules for the model and the option specific sourcing rules to ensure that at least one model sourcing rule can build this configuration.
Failure during ATP Match process. 320 A failure occurred when attempting to match your order to existing configurations. -

Note: For both ATP Based on Collected Data and Planning Data tables, each customer has only one table to use.

Other Data Errors

Error When Error Occurs To Resolve this Message
Collection Process Fails. The collections process fails due to invalid state of msc_atp_plan_sn snapshot. Set the following event in the init.ora file to:
EVENT = 32333 trace name context forever, level 8
ATP performance is slow. - Do the following:

  • Set the profile MRP: Calculate Supply Demand to No on both the source and destination.

  • Set the profile MSC: ATP Debug Mode to None on both the source and destination.

  • Apply the latest ATP patch.

  • Run the Purge ATP Temp Table concurrent program to delete the temporary data (supply, demand, horizontal plan, pegging) for each ATP transaction. This concurrent program purges the temporary data according to the age of the data you specify for deletion. You should run this program daily or even hourly if your ATP transaction volume is high.

    Parameter of the concurrent program:

    Age of Entry (in hours): Specify the age of the data you want to delete. For example, if you enter 1, this program will delete any data that is more than 1 hour old.
Some past due sales orders, supplies, or demands are not included in the ATP. - For ATP based on collected data, check the ATP Rule assigned to the item:

  • From the collection workbench, verify that the sales orders, supplies, and demands in question are collected to the destination.

  • To verify that an ATP Rule exists for the item.

  • To verify the values for Past Due Days supply and demand attributes in the ATP Rule. If values exist, ATP only considers the past-due demand and supply for that many days.


For example, for a 5-day Past Due Demand, ATP only considers the past due demand that falsl under the last 5 working days before the sysdate. To consider all past due demand, these fields should be left blank.
For ATP based on planned data, check the ATP Rule assigned to the item:

  • From the collection workbench to verify that the sales orders, supplies, and demands in question are collected to the destination.

  • From the planners workbench to verify that the sales orders are included in the plan. If they are not, investigate why the sales orders are not included in the plan.
Some supplies and demands are missing. When a sales order is not present in ATP supply and demand details, and the supply is not present in ATP supply and demand details. Check if this supply and demand is visible in the Collections Workbench:

  • If ATP is based on planning output, check if this supply and demand is in the plan.

  • If certain purchase orders or work orders are missing, make sure Planning Manager is up and running if the profile MRP: Consume MPS is set to Yes.

  • If the on-hand quantity from a certain subinventory is missing, check if that subinventory is ATP-capable when ATP is based on collected data.


If supply or demand records are missing, run the SQL query (for Error 11: some supplies and demands are missing) to determine if collection was successful in bringing the supply and demand from the source to the destination.
Subscript Beyond Count. Internal error. Contact your system administrator or contact Oracle Support to investigate the problem.
Delivery Lead Time Not Calculated. For Lead Time set between the customer location and the source organization's location:

  • The internal location is not created for the customer site.

  • Intransit Lead times are not specified for the Ship method between Orgs Ship From and the specified internal location.


For lead time set between customer ship-to site location, customer region, or customer zone:

  • The intransit lead time is not defined between the region or zone to which the customer ship- to location belongs and the source organization's location. No lead time exists at the region or zone level where the customer's ship-to site falls under a specific region or zone.

 For Lead Time set between the customer location and the source organization's location:

  • Create an internal location in the Organization and associate the Customer's Ship to location with it.

  • Define the Intransit Lead times between the Organization's Ship From and this internal location. Also make sure that one of the available ship methods is selected as the default ship method.


For lead time set between customer ship-to site location, customer region, or customer zone:

  • Define the intransit lead time between the region or zone to which the customer ship to site belongs and the source organization's location. Ensure that one of the available ship methods is selected as the default ship method.

Debugging

ATP Debug File

The ATP debug file contains process information that helps facilitate ATP debugging whenever logging a tar or bug. In a Standalone Planning Server Configuration, ATP produces one ATP debug file. In an Integrated Planning Server Configuration, ATP produces one ATP debug file at the source and one ATP debug file at the destination.

To Produce an ATP Debug File for a Standalone Planning Server Configuration:

  1. Set the profile MSC: ATP Debug Mode to Debug Only at the user level of the source instance.

  2. Run the following query to find the location where the ATP debug file is created:

    select ltrim(rtrim(value))

    from

    (select value from v$parameter2

    where name='utl_file_dir'

    order by rownum desc)

    where rownum <2;

    Ensure that the query returned no * values at the end of utl_file_dir value. Also, ensure that this directory is writable.

  3. Run the ATP Inquiry for the item.

  4. When the test case is complete, pick latest session file from the location determined in the first step.

  5. Upload the debug:.

    • Complete Steps 1 to 4 on both the source and destination instance.

    • Set profile MSC: ATP Debug Mode back to None at the appropriate site level after generating the debug file. If the profile option is not set back to None, then the ATP performance degrades.

To Produce an ATP Debug File for an Integrated Planning Server Configuration:

  1. At the instance where the query is performed, set the profile MSC: ATP Debug Mode to Debug Only at the user level.

  2. Run the following query to find the location where the ATP debug file is created:

    select ltrim(rtrim(value))

    from

    (select value from v$parameter2

    where name='utl_file_dir'

    order by rownum desc)

    where rownum <2;

    Ensure that the query returned no * values at the end of utl_file_dir value. Also, ensure that this directory is writable.

  3. Run the ATP Inquiry for the item.

  4. Pick the latest session file from the location determined in the first step, when the test case is complete.

Debugging Areas

People commonly debug the following areas to ensure that the basic setup and ATP calculations are correct.

Oracle Global Order Promising Architecture

Oracle Global Order Promising Database Links

SQL Queries

Note: Your organization's database administrator should be the person designated to run these SQL Scripts.

A basic understanding of the architecture of Oracle Global Order Promising is helpful. The following notes may also be helpful:

Basic Queries

The basic queries below retrieve item and plan information to start diagnosis of an item problem:

From the Source instance, the following gives you:

The following query gives you:

From the destination, the two following queries should produce results to allow for most of the various variables:

Data Error SQL Queries

These SQL queries address the ATP Based on Collected Data Errors and the Other Data Errors from the Troubleshooting section.

Error 47: Unable to find a calendar date.

Two possible issues:

Error 57: Invalid ATP Rule or No ATP Rule defined.

Select

nvl(msi.atp_rule_id, tp.default_atp_rule_id) atp_rule_id

from

msc_system_items msi,

msc_trading_partners tp

where

msi.sr_inventory_item_id = &Source_Inventory_item_id

and msi.sr_instance_id = &Instance_id

and msi.organization_id = &Organization_id

and plan_id = -1

and tp.sr_instance_id = msi.sr_instance_id

and tp.sr_tp_id = msi.organization_id

and tp.partner_type = 3;

Use

&Source_Inventory_item_id = source inventory item id

&Instance_id = instance id of the source instance

&Organization_id = organization id of the sourcing organization

Error Code 85: This item is not collected. Please run Data Collection.

Select

item_name,

atp_flag,

atp_components_flag

from

msc_system_items

where

sr_inventory_item_id = &Source_Inventory_item_id

and sr_instance_id = &Instance_id

and plan_id = -1;

Error 120: Plan not found.

Execute the following query:

Then:

Note: If the above query does not return any data, then:

Error 140: No APS instance defined. Set APS instance and run collections.

Run the following queries on the source instance:

Error 220: ATP has detected invalid objects. Contact your system admin.

The following query provides some of the possible invalid objects in the database:

Then:

Error 230: INV: Capable To Promise must be same at source and destination.

Run the following queries on both source and destination:

Other Data Error: Some past due sales orders, supplies, or demands are not included in the ATP.

Select

rule_name,

past_due_demand_cutoff_fence,

past_due_supply_cutoff_fence,

include_sales_orders,

include_purchase_orders,

include_discrete_wip_receipts,

include_nonstd_wip_receipts,

include_discrete_mps,

include_rep_mps,

include_rep_wip_receipts

from

msc_atp_rules

where

rule_id = &ATP_Rule_id

and sr_instance_id = &Instance_id;

Use

&ATP_Rule_id = rule id determined using query in the section above

&Instance_id = instance id of the source instance

Note: For any supply and demand types that have values returned as 1, ATP only considers the past due demand and supply for that many days.

For example: for Past Due Demand Days of 5 days, ATP only considers past due demands that fall under the sysdate of 5 days. To consider all past due demands, these fields should be left blank.