Global Available To Promise (GATP

)
Please forward comments and questions to jeffery.goulette@oracle.com. Thanks! Before implementing GATP, please see Oracle APS Implementation and Users Guide Release 11i, part number A81009-02.

GATP Decentralized
In a decentralized environment, additional setup and process management is required. The graph below depicts the setup for GATP in a decentralized environment. Data collections are required in a decentralized configuration. mrp_ap_apps_instances, at the source instance, and msc_apps_instances, at the destination instance, are used to store instance setup and instance specific information. Mrp_ap_apps_instances contains source instance information including the database link name that points to the destination server if implemented as decentralized. Msc_apps_instances contains the destination instance specific information as well as the database link that points to each individual source, if implemented in a decentralized mode. Mrp_ap_apps_instances and msc_apps_instances are used in both centralized and decentralized configurations. In a decentralized configuration, the source table MRP_AP_APPS_INSTANCES must contain only one row. Execute the following table to verify this. select instance_id from mrp_ap_apps_instances; This query should return one row as the source can only point to one destination instance.

If ASCP is not being used, use the OM data collection concurrent program. If ASCP is being used, use the ASCP data collection program. If only single level GATP is implemented, the OM data collection is sufficient since there isn't a need to collect BOM and routing data.

Decentralized Application Setup
11i , 11.0.3, 11.0.2 and 10.7 16.1 are valid sources for an 11i GATP destination. Perform the following setup at each source instance to implement GATP in a decentralized environment. Set the following profile options accordingly. • INV: External ATP should be set to GLOBAL. This profile value option is created by the GATP Patch as indicated in the GATP Implementation Guide. This profile option is not needed in 11i. • INV: Capable to Promise should be set to either Enable PL/SQL based ATP without planning output or Enable PL/SQL based ATP with planning output. This should be set at the source and destination instances. • MRP:ATP Database Link should be set to the database link name that points to the destination server. This profile option does not need to be set on the destination instance.

Decentralized Environment Source
Data Collections Using Database Links Source: mrp _ap_apps_instances.a2m_dblink Destination:msc_apps_instances.m2a_dblink

Destination

MRP Tables - SKUs - O/H - S/R 7.3.4/8.0/8.1

Data is collected.

MSC Tables containing statement of supply. 8.1.6

Reservations are pushed back.

Verify the database link: select instance_code, substr(a2m_dblink,1,35), ß This points from the source to the destination substr(m2a_dblink,1,35) ß This points from the destination to the source from msc_apps_instances; Verify the database link at the source: select instance_code, substr(a2m_dblink,1,35), ß This points from the source to the destination substr(m2a_dblink,1,35) ß This points from the destination to the source from mrp_ap_apps_instances; 2

ß This points from the source to the destination substr(m2a_dblink. 3 .1. use the ASCP data collection program. substr(a2m_dblink.1.1. select instance_id from mrp_ap_apps_instances.35).35). Mrp_ap_apps_instances contains source instance information not including the database link name that points to the destination server since both transaction source data and the GATP destination are contained within one Oracle instance. ß This points from the source to the destination substr(m2a_dblink. Mrp_ap_apps_instances and msc_apps_instances are used in both centralized and decentralized configurations. Msc_apps_instances contains the destination instance specific information not including the database. substr(a2m_dblink. Execute the following table to verify this. Verify the database link at the destination: select instance_code. If ASCP is being used. the OM data collection is sufficient since there isn't a need to collect BOM and routing data.1. The graph below depicts the setup for GATP in a centralized environment. Verify the database link at the source: select instance_code. use the OM data collection concurrent program.GATP Centralized 11i source to 11i destination is the only combination allowed in a centralized GATP implementation. If ASCP is not being used.35) ß This points from the destination to the source from mrp_ap_apps_instances. Data collections are required in a centralized configuration.35) ß This points from the destination to the source from msc_apps_instances. the source table MRP_AP_APPS_INSTANCES must contain only one row as the source can only point to one destination instance. In a centralized configuration. If only single level GATP is implemented.

• INV: Capable to Promise should be set to either Enable PL/SQL based ATP without planning output or Enable PL/SQL based ATP with planning output.SKUs .O/H .Centralized Application Setup Perform the following setup to implement GATP in a centralized environment: • INV: External ATP should be set to None.1 MSC Tables containing statement of supply.3.S/R 7.m2a_dblink Reservations are pushed back. 8. Centralized Environment.6 4 .a2m_dblink Destination:msc_apps_instances. There is more information.4/8.0/8. same Oracle instance Data is collected. Data Collections Using Database Links Source: mrp_ap_apps_instances. • MRP:ATP Database Link should be null since another Oracle instance is not involved in a decentralized configuration. same server.1. MRP Tables .

For example.7 / 11 / 11.7 / 11 / 11. A setting of zero is the lowest priority for commit_point_strength. By setting this value higher on the OLTP instance. Additionally. The statements of supply from both organizations is stored in the APS instance. A servers’s commit point strength is set by the initialization parameter COMMIT_POINT_STRENGTH within the init_<sid>. compared to the APS server. collections are taken from two manufacturing organizations. The range of values is any integer from 0 to 255. the OLTP instance will control the distributed transactions. include the following line in that database’s parameter file: COMMIT_POINT_STRENGTH=200 5 . consider setting the COMMIT_POINT_STRENGTH.5 Source MRP Data APS or Destination Instance Order Management GATP Request Collect Data Complete or Incremental Refresh Using OM or APS Data Collection MSC Supply/Demand tables ODS or PDS Source Instance 2 commit_point_strenght = 1 commit_point_strenght = 0 10.5 Source MRP Data Order Management GATP Request If you are implementing Global Available to Promise is a decentralized environment.In the graph below. Source Instance 1 commit_point_strenght = 1 10. the same two source instances are order management centers in the.ora parameter file. Precedence is given to those distributed transactions possessing a greater commit point. to set the commit point strength of a database to 200. promising or demanding against the combined statement of supply. All transactions must wait their turn in a queue.

does not allow for the collection of BOMS or Routings. as of 11. This makes the calculation of supply chain GATP impossible. With this profile option set to #4 you can utilize supply chain GATP and multi-level ATP. The Planning Data Pull can be executed from within APS instead of collecting data from within OM. • INV: Capable to Promise INV: Capable to Promise determines which data store will be used for ATP check. In 6 . the data will be inserted into the PDS. If several Oracle instances are collected for GATP promising. There must be at least one valid ASCP plan with the ATP box checked.Enable Product Family ATP and CTP. this is not used in 11i 4 .Enable PL/SQL based ATP without Planning Output * * new setting for 11i Global Available to Promise With Planning Output 4 .Enable PL/SQL based ATP with Planning Output * 5 . The PDS is the destination of ASCP plan data. Collecting ATP Supply • The Advanced Planning and Scheduling (APS) Planning Data Pull (PDP) and Order Management (OM) ATP Data Collection are 2 different report-sets with the same Concurrent Programs included in both sets. Production Plan or Distribution Plan/Names. NAV>Manufacturing Plan. The Order Management implementation of data collection.5. all instance data will be stored in the ODS. To learn more about shared plan partitions. this is not used in 11i 2 . please reference the ASCP User’s Guide part number A8100901. ATP rules are used when GATP determines the infinite time fence.Enable ATP.Enable PL/SQL based ATP with Planning Output. These rows have a plan_id = -1 • PDS or Planning Data Store. This profile option can have the following settings: 1 . GATP will assume infinite supply. The ODS is the destination of collected data. this is not used in 11i 3 .Enable Product Family ATP.Source of GATP Information GATP information is derived from: • ODS or Operational Data Store. Implementing shared plan partitions has no direct affect on GATP processing aside from possible performance implications. These rows have a plan_id > -1 A data store is a set of tables used to store data. After a plan has completed successfully. The PDP is used to collect data for the ASCP planning engine and GATP.3.

compile_designator. the source instance id and the organization id. If the demand class is not required. These will be combined into one plan type in the future. 1.compile_designator = '&your_plan_name' and b.organization_id. The PDS rows in the following tables are used. This query will select the source inventory_item_id which is needed for the last query. This query will select the plan_id. If the demand class is supplied. This query will select all of the plans where the item exists. plan name also known as compile designator. simply press return through the demand class prompt. 7 . Select a. substr(item_name. The rows in each of these tables has a plan_id > -1: MSC_SUPPLIES MSC_DEMANDS MSC_RESOURCE_REQUIREMENTS MSC_NET_RESOURCE_AVAIL MSC_INTERORG_SHIP_METHODS MSC_SUPPLIER_CAPACITIES MSC_SUPPLIER_FLEX_FENCES If the GATP process is not returning correct values according to the plan output.plan_id. the plan_id should be the same for the rows returned unless there are multiple plans available. the query may return more than one row. The names form contains a checkbox for ATP. Gatp will pick the plan with lowest plan_id to perform GATP.plan_id = a. select sr_inventory_item_id.organization_code. determine which plan OM is promising against. If this query returns multiple plans there is more than one plan for an item/org/instance/demand class combination. b.sr_instance_id from msc_plans a. Consider unchecking the inventory atp flag of the other plans that may contain the item. msc_plan_organizations b where a.5. In this case however. 30) from msc_system_items where item_name = ‘&your_item_name’ and sr_instance_id = ‘&sr_instance_id’.3 there is a choice between these three different plan types. b. b.plan_id.11. a.

with the profile option set to 5. The rows in each of these tables has a plan_id = -1. Essentially. if defined. This is not the same as in previous versions of Oracle Applications. The names form contains a checkbox for ATP. Several plans can be checked for atp. MRP: ATP Assignment Set – This is used for Order Entry or Order Management at the source instance. In previous versions of Oracle applications. the process is operating under centralized mode. MRP: ATP Database Link – OM will use this database link to access GATP information at the destination pointed to be this database link. As the Advanced Supply Chain Planner. NAV>Manufacturing Plan. If the source transaction data is collected into the GATP database objects in a different Oracle instance . In 11.select from where and and and plan_id msc_atp_plan_sn sr_instance_id = ‘&sr_instance_id’ organization_id = ‘&organization_id’ sr_inventory_item_id = ‘&inventory_item_id’ demand_class = ‘&Your_demand_class’. for the item. ATP rules are used. If the GATP request is launched from the source in a decentralized environment. supply chain GATP or multi-level ATP is not possible. This 8 .4. The rows in MSC_SUPPLIES. Additional GATP Profile Options MRP: Complete Supply Chain ATP – In a future release. MSC_DEMANDS and MSC_SALES_ORDERS from the ODS are used. Global Available to Promise Without Planning Output 5 .the process is operating under decentralized mode. If the source transaction data is collected into the destination GATP database objects contained within the same Oracle instance. Currently in 11.5. These will be combined into one plan type in the future. The only difference being that the collected data represents supply from one or more organizations or instances.Enable PL/SQL based ATP without Planning Output. GATP returns the ATP information for the warehouse ranked as number 1 if the quantity requested cannot be met within any warehouse defined in a sourcing rule for requested item. this profile option will control the visibility of the warehouses within the instance sourcing rule. Consider unchecking the inventory atp flag of the other plans that may contain the item. the user was limited to supply contained within one instance. This profile option is not set in a centralized configuration. With this profile option set to 5.3 there is a choice between these three different plan types.5.even on the same server . you have the same ATP functionality present in previous releases of Oracle Applications. the assignment set indicated here will drive the GATP request. Production Plan or Distribution Plan/Names.

ODS GATP uses sourcing rules to determine if the item can be manufactured in other organizations. However. Sourcing Rules • • Customer / Customer Site global sourcing rule takes precedence if setup and collected. pick source or not will not matter when determining the default ship method. MRP: ATP Debug Mode – If set to YES. INV: External ATP – By setting this to GLOBAL.%. The Ship From organization. Additionally.0. Please reference the end of this document concerning the setup and extraction of the ATP debug file. GATP will use the setting in MRP: ATP Database Link to access the GATP quantities at the destination instance. any global assignment on the source becomes an instance-specific assignment for GATP.7 or 11. then GATP will use the ship method and lead time from the sourcing rule. Sourcing type equal to buy is not effective. GATP will use the instance specific global sourcing rule.7 and 11 only. therefore. the GATP server can be promising for more than one instance. if the default ship method is defined. Assign sourcing rules at the global level on the source and they will be used if there are not specific assignments at the customer/site level available. MSC: ATP Debug Mode – If set to YES. If the GATP server is promising for only one instance then the sourcing rule is by default treated as global.profile must be set. the assignment set indicated here will drive the GATP request. • • 9 . Please reference the end of this document concerning the setup and extraction of the ATP debug file. See intransit leadtimes below for more information regarding default ship methods. collected from the source. If the sourcing rule originates at the source instance. PDS GATP uses buy sourcing for the shipping organizations to generate planned orders. MSC: ATP Assignment Set – ASCP will use this assignment set if populated. GATP will produce a debug file at the source instance. However. Once sourcing rule is involved. that is assigned to an assignment set. GATP will use the sourcing rule since no source is supplied. please set the profile option to MSC: ATP Debug Mode at the destination instance as well since a debug file can be produced at the source and destination instances. as setup in a bill of distribution or global sourcing rule and finally the organization sourcing rule. If this profile option is not populated. If this setting is used in a decentralized environment. If pick source is used. If the GATP request is launched from the destination in a decentralized environment. If this setting is used in a decentralized environment. This is used in 10. please set the profile option to MRP: ATP Debug Mode at the source instance as well since a debug file can be produced at the source and destination instances. GATP will produce a debug file at the destination instance. Sourcing rules can originate at the source instance or the destination instance. The debug file will be written to utl_file_dir. it must be global and assigned to an assignment set at the destination instance. if this profile is set and the source is 10. the profile option INV:Capable to Promise must be set to Global. The debug file will be written to utl_file_dir.

NAV>Setup/Instances. MSC: ATP Assignment Set instructs ASCP to use this specific assignment set when calculating GATP information. If the GATP request is launched from the source. GATP will use the assignment set specific to the instance. Source Instance One Global Sourcing Rule ASSIGNMENT_SET_1 Source Instance Two Global Sourcing Rule ASSIGNMENT_SET_2 Source Instance Three Global Sourcing Rule ASSIGNMENT_SET_3 Collect data into ODS GATP will use the instance specific set: Instance One: ASSIGNMENT_SET_1 Instance Two: ASSIGNMENT_SET_2 Instance Three: ASSIGNMENT_SET_3 10 . At the destination instance. Global sourcing rules assigned to an assignment set at the source. as the Advanced Supply Chain Administrator. In the following example. data is collected from three instances. the assignment set indicated here will drive the GATP request. the assignment set is entered into the specific instance setup row. each instance will have a specific assignment set. GATP will use the assignment set specific to the instance for GATP processing. If the GATP request is launched from the destination. Each instance has a global sourcing rule that is contained within instance specific assignment sets at the source. the assignment set indicated here will drive the GATP request.Global ATP Profile Options Affecting Sourcing Rules MRP: ATP Assignment Set is a source profile option that is used by Order Management to calculate ATP. Each instance specific assignment set will encompass all organizations for that instance. When collections are executed.

No assignment set identified at the destination profile option MSC: ATP Assignment Set. Source Instance One Global Sourcing Rule ASSIGNMENT_SET_1 Collect data into ODS GATP will not have an ASSIGNMENT_SET for this instance. In this example. This will prevent accurate GATP results if the end item is not in stock in a particular warehouse. if the user does not specify the source. 11 . there is a non global sourcing rule assigned to an assignment set at the source. The user will not have visibility to additional warehouse supply. GATP will not have access to a valid assignment set.In the next example. the user will receive 'No Sources'.

Source Instance One Global Sourcing Rule ASSIGNMENT_SET_1 Source Instance Two Global Sourcing Rule ASSIGNMENT_SET_2 Source Instance Three Global Sourcing Rule ASSIGNMENT_SET_3 Collect data into ODS GATP will NOT use the ALL_INSTANCE ASSIGNMENT SET defined at the destination. The assignment set created at the destination instance covers all instances collected. 12 . Assignment set created at the destination and the assignment set name populated in profile option MSC:ATP Assignment Set. Global sourcing rules assigned to an assignment set at the source.This particular setup is NOT recommended.

the user creates a sourcing rule that includes limited organizations from both collected instances. The sourcing rule is assigned to an assignment set called Limited_Instance_Org_Set.The following example assumes that the user is performing the GATP at the source instance: Source Instance One Global Sourcing Rule ASSIGNMENT_SET_1 Source Instance Two Global Sourcing Rule ASSIGNMENT_SET_2 Collect data into ODS MSC: ATP Assignment Set = null At the destination instance. This is designated when setting up the plan name. Execute ASCP Memory Based Planner (MBP) with specific assignment set called Limited_Instance_Org_Set. The plan output in configured according to the Limited_Instance_Org_Set 13 . ASCP data is inserted into the PDS.

See Leadtimes for additional details. This is done for the top level only.pls The GATP program MRPGATPB. Allowing for transactions between the source instance and destination instance. Both centralized and decentralized.5. This logic is only used at the top level of the assembly. the assignment set indicated by the setting in the profile option MRP:ATP Assignment Set will be used for the top level only. MRPGATPB. in decentralized mode. fill in the source organization. then the plan assignment set will be used.PLS represents demand and supply items. the user will receive the ‘no sources’ error message.If the user executes the GATP check without referencing the source organization.3 • Reads from the previously collected item supply and item demand records that are found on the APS server. • Ensures secure allocation of supply to demand MRPGATB performs operations on the following database objects: • msc_system_items • msc_supplies • msc_sales_orders • msc_demands • mrp_atp_details_temp • mrp_atp_schedules_temp 14 . If the GATP process originates at the source instance. ATP rules are used when performing GATP with planning output to arrive at the infinite supply time fence. When performing GATP. This is the main program for GATP as of 11. after that the plan assignment set is used. If the are no sources for the item/organization combination. GATP defaults to the assignment set defined in MSC: ATP Assignment Set since each item/organization combination can be part of a different plan. • Utilizes the multi-threaded capabilities of the Oracle database to process concurrent ATP request efficiently. below the top level the plan assignment set is used for GATP.

Multiple ATP requests within a single order or order line will receive a unique session_id. mrp_atp_details_temp periodically as ATP requests may be abandoned leaving orphaned rows in these tables. Please purge mrp_atp_schedule_temp. The foreign key. Both of these temp entries should be deleted when the user session is terminated. consists of session_id and order_line_id . an entry is inserted into mrp_atp_schedule_temp. associated with mrp_atp_schedule_temp. If the ATP check was successful. the details are recorded in msc_sales_orders. details concerning the GATP check are stored in mrp_atp_details_temp. the ATP information is written to mrp_atp_details_temp.GATP Process As a GATP request is made. mrp_atp_schedule_temp mrp_atp_details_temp record_type = 2 msc_sales_orders PDS based GATP msc_supplies ODS /PDS based GATP msc_demands ODS/PDS based GATP 15 . After the ATP check is complete. Each ATP request receives a new session_id derived from mrp_atp_schedule_temp_s sequence.

BOM_DEPARTMENT_RESOURCES contains resources that may be available to CTP. MRP_ATP_SUPPLY_DEMAND is populated during the execution of the Advanced Supply Chain Planning engine and is used by the Planner’s Workbench. MSC_Available_to_Promise is used when accessing the Horizontal Plan within the Planner’s Workbench. MRP_ATP_SCHEDULE_TEMP: Embodies ATP rows that are going to be checked for ATP. This table is populated during the execution of the Advanced Supply Chain Planning engine. This is used in planning and ATP for the support of flex fence tolerance and support.Tables used in GATP include: MRP_ATP_SCHEDULE_TEMP: Holds GATP results from an active GATP reservation. MRP_ATP_DETAILS_TEMP: Contains GATP data for the user session. MRP_ATP_DETAILS_TEMP: Contains GATP details associated to an active GATP reservation results for Supply/Demand. 16 . MTL_PARAMETERS: Holds the default ATP_RULE_ID. Horizontal GATP and sourcing. BOM_RESOURCE_FLEX_FENCES: stores the time phased capacity tolerance for resources and lines. The ctp_flag indicates if a resource is active for CTP.

PDS Data is used Source Tables: mrp_* so_* Inv Profile = 5. Source Tables: mrp_* so_* Inv Profile = 5. any receipts for stock are created. ODS Data is used. organizations. • When verifying the default ship method from organization to customer / customer site. 17 . we will use the MSC_INTERORG_SHIP_METHODS table based upon the from_organization_id and to_organization_id columns. When verifying the default ship method for organization to organization. sourcing rules. we will use the MSC_INTERORG_SHIP_METHODS table based upon the from_location_id and to_location_id columns. ATP rule. • If items. GATP uses the location with the lowest rownum.GATP Data Flow Data flows into views used by GATP in the following manner: Inv Profile = 4. Database link populated. If multiple locations are found. no Database link populated Source Tables: mrp_* so_* msc_supplies msc_demands msc_resource_requirements msc_net_resource_avail msc_interorg_ship_methods msc_supplier_capacities msc_supplier_flex_fences msc_supplies msc_demands msc_sales_orders msc_supplies msc_demands msc_sales_orders GATP Data Requirements Intransit Leadtime and Trading Partners or Organizations GATP determines intransit leadtime based upon the relationship involved in the transaction. • Organization to/from organization and organization to customer/customer site. deleted or modified or if the shipment methods are modified it is necessary to submit the data collection program before the changes are seen in Order Management. warehouses.

This is setup when the customer is defined. execute the following queries. In our example below. supplier. This is the code that was assigned to the instance at the destination: select instance_code. there are three types of partners. This query is to be used when the transit occurs between organizations. GATP determines the instransit leadtime as follows: 1) Determine that the ship to and ship from are defined in MSC_TRADING_PARTNERS 2) Determine intransit leadtime for trading partners based upon previously collected sourcing rule. Based upon the organization name. This default is required when the transit occurs between an organization and a customer. For defaulting purposes. To find your sr_tp_id and sr_instance_id. 3) If not present. located the appropriate oragnization_id: select substr(name. determine the default shipping method from collected source information within in MSC_INTERORG_SHIP_METHODS. enable_flag from msc_apps_instances. As of 11.30).3. Organization to Organization Execute the following query to determine if the organization trading partner is defined. The first step is to locate the id that points to the collected instance code. The MSC_TRADING_PARTNER_SITES table contains the locations for all collected possible sites.1.5. the intransit leadtime will not be reflected in the Schedule Arrival Date. The next step involves locating the source trading partner id.When attempting to determine the schedule arrival date in an order line. instance/organizations. if the source and destination organizations are not defined properly in MSC_TRADING_PARTNERS_SITES and yet defined within a default ship method. The Schedule Ship Date and Schedule Arrival Date would be the same for the order line. instance_id. we will locate the organization_id at the source. organization_id from HR_ALL_ORGANIZATION_UNITS 18 . customers.

the check for a default shipping method can proceed if the organization ship to and ship from are not defined in your sourcing rules. enable_flag from msc_apps_instances. First.1. The next step involves locating the organization id(s) that are involved in the shipment transaction. a valid shipment method is required in the MSC_INTERORG_SHIP_METHOD table. select the data that will be used to locate the default ship method currently being used for your organizations. ß 3 = instance/organization If the above query returns a row. continue the investigation into the default shipping method between the organizations. At the destination.select sr_tp_site_id from msc_trading_partner_sites where sr_tp_id = 207 ß organization_id from above query and sr_instance_id = 2 ß instance_id from the first query and partner_type = 3. GATP will pickup the intransit leadtime from the sourcing rule. If the sourcing rules do not contain the relationship between ship from / ship to organizations the default intransit leadtime will be used during scheduling activities. if a shipment method is not present in the sourcing rule. issue the following query: select instance_code. instance_id. It is advised that one default ship method with intransit leadtime be defined in the MSC_INTERORG_SHIP_METHOD table between organizations. • • If the source organization is populated during the GATP check. If ‘pick source’ is entered for the source during the GATP check. the sourcing rule will be used to determine the intransit lead time and shipment method. organization_id from HR_ALL_ORGANIZATION_UNITS 19 . If the default ship method is not present in MSC_INTERORG_SHIP_METHOD. At the source: select substr(name. In this case. GATP will not be able to calculate the correct ship method and delivery leadtime. • Having determined that the organizations are in MSC_TRADING_PARTNER_SITES.30).

execute the following queries. If the specific organization to customer transit is not defined in the sourcing rules. the intransit leadtime will be chosen from the collected sourcing rules. Organization to Customer If the transit occurs between organization and customer. ship_method msc_interorg_ship_methods plan_id = -1 ß this represents the ODS from_organization_id = ‘&from_org_id’ sr_instance_id = ‘&from_instance_id’ to_organization_id = ‘&to_org_id’ sr_instance_id2 = ‘&to_instance_id’ default_flag = 1. the default ship method will be used. The first query will extract the correct instance_id. ship_method msc_interorg_ship_methods plan_id = -1 from_organization_id = ‘&from_org_id’ sr_instance_id = ‘&from_instance_id’ to_organization_id = ‘&to_org_id’ sr_instance_id2 = ‘&to_instance_id’. Sourcing rules would not be used in this case. To verify the association required to access the default shipping method. Please turn the default flag on for the ship method. The second query will extract the partner_id based upon the location_id and organization combination. Query 2 select from where and and and and intransit_time. If there is not a default ship method for the customer and ship from location. If query 1 returns no data and query 2 returns data. At least one default ship method with intransit leadtime should be defined in the MSC_INTERORG_SHIP_METHOD table between organization and customer. If the combination of the customer and ship from organization is located in MSC_LOCATION_ASSOCIATIONS.Query 1 Select from where and and and and and intransit_time. the GATP will receive the 20 . the default ship method can be chosen from MSC_INTERORG_SHIP_METHODS. collect the source data and attempt the process again. it means that the default ship method is not specified.

enable_flag from msc_apps_instances.1. Query 2 select substr(name. Query 3 select from where and location_id msc_location_associations sr_instance_id = '&Source_instance' partner_id = (select tp_id from msc_tp_id_lid where exists (select customer_id from ra_customers where customer_name = '&Your_customer_name' and customer_id = msc_tp_id_lid. sr_instance_id. Query 3 will select the location_id required for query 4. instance_id. organization_id from HR_ALL_ORGANIZATION_UNITS. sr_instance_id2. Query 4 select from_location_id. to_location_id. 21 .10) from msc_interorg_ship_methods where to_location_id = '&location_id' and from_location_id = '&Your_shipping_organization'. Query 4 will return the default ship methods setup between the organization and customer / customer site. substr(ship_method.sr_tp_id and status = 'A') and partner_type = 2 and sr_instance_id = '&&source_instance').30). Query 1 select instance_code.1.messages ‘No sources found’.

plan_id.compile_designator. however the GATP rule is used as well to determine the infinite time fence. organization_id from HR_ALL_ORGANIZATION_UNITS This query will return the plan_id: Select a. it is determined that a level of the bill of materials does not have atp_components_flag set to yes. the plan options are used.sr_instance_id from msc_plans a. msc_plan_organizations b where a. to be executed at the source. must be populated: ATP Flag .30). 22 . The profile option INV: Capable to Promise must be set to 4. the following two columns in MTL_SYSTEMS_ITEMS.organization_code. b. the ATP check will not proceed further down that leg of the bill.compile_designator = '&your_plan_name' and b.organization_id.Is the Item GATP Eligible? Item Atp_rules are used if the GATP is against the ODS. GATP With Planning Output.1. This query will return the instance id: select instance_code. will return your organization id: select substr(name. If the GATP is against the PDS.plan_id = a. at the source.ATP_FLAG ATP Components Flag . For an item to participate in GATP. execute the following queries. If.plan_id.ATP_COMPONENTS_FLAG is used for the PDS only. during supply chain GATP. This flag is defaulted to NO when GATP is implemented without planning output as multi-level GATP is not applicable. To verify the eligibility of collected data to participate in GATP. This query. enable_flag from msc_apps_instances. b. a. b. instance_id.

atp_components_flag msc_system_items plan_id = ‘&plan_id’ ß This plan_id would be –1 for ODS organization_id = ‘&organization_id’ sr_instance_id = ‘&instance_id’ sr_inventory_item_id = ‘source_inventory_item_id’ Both flags should return 'Y' to participate in Mutilevel GATP. This query will return the atp setup for the item: select from where and and and atp_flag. plan cutoff date. After the infinite time fence. The leadtime is derived as follows: item/organization setting. cumulative manufacturing lead time. What is the ATP rule for the item? First. total leadtime. select sr_inventory_item_id. substr(item_name. GATP assumes infinite supply. rerun collection and rern the plan. There are four choices for leadtime: cumulative total leadtime. If not. 30) from msc_system_items where item_name = ‘&your_item_name’ and sr_instance_id = ‘&sr_instance_id’. The infinite time fence setting for the item is used if ATP rule is not set. Is the atp_flag = ‘Y’ and the atp_components_flag = 'N'. then GATP will verify material only for the item in single level GATP mode. The infinite supply time fence is defined as part of the atp rule and the atp rule is assigned at the item/org level or the organization level.This query will select the source inventory_item_id which is needed for the last query. user defined time fence. organization default setting. 1. Leadtime for GATP It is important to determine the leadtime that will be used to arrive at the latest produceable time fence for calculating GATP supply. please correct the item setup at the source. run the following SQL to extract details needed to determine which lead time is being used for the ATP check: 23 .

item_name. select the information that we are looking for: select atp_flag. preprocessing_lead_time. If the profile option. organization_id. skip this query and enter –1 for the next query when prompted for the plan_id. from msc_system_items where item_name = '&your_item_name'. If the atp_rule_id for the item is not empty. full_lead_time. postprocessing_lead_time from msc_system_items where plan_id = ‘&plan_id’ and sr_instance_id = '&instance_id_from_query_above' and organization_id = '&organization_id' and sr_inventory_item_id = '&your_inventory_item_id’ In the query above. select plan_id from msc_plans where compile_designator = '&your_compile_designator' Now. atp_components_flag. execute the following query: select infinite_supply_fence_code from msc_atp_rules where rule_id = '&atp_rule_id_from_above' and sr_instance_id = '&instance_id_from_query_above'. we selected the atp_rule_id. This is the three letter code that was used to setup the instance for collection. atp_rule_id. INV:Capable to Promise is set to GATP Without Planning Output. 24 .Select instance_id from msc_apps_instances where instance_code = ‘&your_three_letter_code’. This is populated at the source item entry form. select sr_inventory_item_id. The following query is not needed if you are promising available supply against the ODS.

cumulative_total_lead_time 2 .infinite_supply_fence_code values: 1 .infinite_supply_time_fence This should return a non zero value. GATP concludes that the item has infinite supply.cum_manufacturing_lead_time 3 . 2.status from user_objects where object_name = 'MSC_ATP_PLAN_SN' OBJECT_NAME OBJECT_TYPE STATUS ---------------------------. 4 . for the item empty.-------------------------------MSC_ATP_PLAN_SN TABLE VALID MSC_ATP_PLAN_SN UNDEFINED INVALID alter snapshot MSC_ATP_PLAN_SN compile.order_sch_wb has been changed. Is the ATP snapshot valid? select object_name.preprocessing_lead_time + full_lead_time + postprocessing_lead_time. retrieve the DEFAULT_ATP_RULE_ID from the organization that has been collected: select from where and and default_atp_rule_id msc_trading_partners sr_tp_id = ‘&organization_id’ sr_instance_id = ‘&instance_id’ partner_type = 3.object_Type. The form does not allow to do an inquiry. zero indicates sysdate or today. select infinate_supply_fence_code from msc_atp_rules where sr_instance_id = ‘&instance_id’ GATP Diagnostics 1. The query below determines the lead times used for the instance. If the result is zero. 25 . While trying to do perform a query on the ATP inquiry screen. you receive the following error message "signature of package apps. Verify the item leadtime setup as indicated by the results of the above query. If the ATP_RULE_ID.

Perform the following query to determine the status of your instance: select instance_code. GATP is not available. investigating the log file pertaining to the previous execution and relaunching the collection. as verified by NAV>View>Requests. The so_tbl_status of the instance_code that is being promised against must be equal to 1. the message ‘ATP not available’ is displayed. When performing a complete refresh with or without sales orders.1. commit. status from all_objects where object_name = '%ORDER_SCH_WB%' The object should now be valid. reset the value of SO_TBL_STATUS. If so_tbl_status is equal to 2 and data collections are executing. see note. This message appears when a data collection is executing for the instance. This is not the case when performing an incremental refresh. ATP is not available until the completion of data collection. the last collections attempt ended with error and needs to be repaired. so_tbl_status from msc_apps_instances. When attempting a GATP action. Set to 1 by executing the following sql: update msc_apps_instances set so_tbl_status = 1 where instance_code = '&your_instance_code'. If the data collections are not currently executing. To repair the st_status column after failed data collection. 26 . If it is equal to 2 and collections are not running. Recompile the package body. This will require resetting the st_status flag in msc_apps_instances.FRM-40735 WHEN-BUTTON-PRESSED trigger raised unhandled exceptionORA-04062 ORA-04062 signature of packageapps.146016. ALTER PACKAGE ORDER_SCH_WB compile body Run the following script: select object_type. 3.order_sch_wb has been changed.

GATP will return zero. If there is not an ATP rule set at the item or organization level. b) New customers need to be entered at the source and the data collection needs to be submitted. ATP quantity is returned as zero. The result will resemble the following: VALUE ----------------------------------------------------------------------/usr/tmp/. /temp 27 . GATP returns zero for the quantity. a) Review the global sourcing rule and assignment set for the customer/customer site. ensure that the ctp_flag is set in MSC_DEPARTMENT_RESOURCES. d) Verify that the ATP_FLAG in MSC_BOM_COMPONENTS for the correct plan_id is activated. This must be performed at the source and destination instances if GATP is implemented in a decentralized mode: SELECT VALUE FROM V$PARAMETER WHERE NAME = 'utl_file_dir'. 6. Producing a GATP debug file. b) Verify that the ATP rule has been set for the item within MSC_SYSTEM_ITEMS. The infinite time fence is derived from the atp rule. f) For resources. e) Verify that the plan has the ATP checkbox activated on the Names Form. the GATP process checks backward for a valid workday making the demand late. When performing supply chain ATP. b) Check the MRP: ATP Database Link and test the link 7. 9. 8. Set the ATP_COMPONENTS_FLAG to N for purchased items. Multiple levels are not displayed. a) Determine if the utl_file_dir is set correctly. /usr/. a) Multi level GATP is performed only when implementing GATP with planning output. If the ATP check is made on a non-working date. 5. c) Verify that the ATP_FLAG and ATP_COMPONENTS_FLAG are set to Y in MSC_SYSTEM_ITEMS for correct plan_id. the message ‘No Source Found’ appears. GATP cannot determine the correct supply/demand to perform netting.4. a) Check the INV: Capable to Promise profile option setting. In this scenario.

'. From this screen after the ATP Inquiry is completed. Site level or User level. INSTR(value.In the field click on the LOV and select SESSION_ID. $ cd /usr/tmp $ ls -ld drwxrwxrwx 2 root other 2425 Dec 25 22:30 Also make sure the following SQL script returns something other than '*'. Note the Session_id. This will return you a value in the Value field. Site level or User level. SELECT LTRIM(RTRIM(SUBSTR(value.'. * will not function correctly for GATP purposes.1)+1))) FILE_DIR FROM v$parameter WHERE name= 'utl_file_dir' FILE_DIR ----------------------------------------------------------------------/usr/tmp The $APPLPTMP environment variable should be set to a directory the directory returned from the above SQL.-1. While '*' is a valid setting in the utl_file_dir list. This comes up with a Examine Field and Variable Values window .Ensure that the directories returned from the above SQL possess the appropriate privileges. Click on Help-->Diagnostics-->Examine. b) MSC: ATP Debug Mode set to Yes at the destination instance. d) Responsibility --> Advanced Supply Chain Planner Navigation -->ATP-->Atp Inquiry Enter the ATP inquiry and click on the ATP results After the ATP result is shown close the ATP result window and come back to ATP criteria screen. c) MRP: ATP Debug Mode set to Yes at the source instance if GATP is implemented in a decentralized mode. 28 .

As an example. 11. or 'Resources only' depending on what kind of availability check ATP is to perform.for material and capacity (resources) c) N . If the source instance is 10. In 11i.0. then the the item's 'ATP Components' in M2 should be set to either 'Materials only'. I will be updating this doc and resending when complete.7 or 11. set item attributes for each item in the bill Check ATP a) Y . then the value is stored in a descriptive flexfield of MTL_SYSTEM_ITEMS. For multi level GATP check. If the desire is to satisfy the atp request by building the item in M2. 10. Please see Metalink concerning the production of an OE Debug file. the value of the atp_flag and atp_components_flag are stored in MTL_SYSTEM_ITEMS at the source instance. GATP and 10. but instead of the ATP inquiry. Perform all of the steps as indicated above. locate the debug logfile created by the ATP inquiry with the following filename.for material only b) C . Additionally. check the atp flag at bill level and or ctp flag at department resources level accordingly.The above performs an ATP Inquiry. e) cd to /usr/tmp (or your particular directory). such as the sql required to find the flex field and the setting of these switches.none Ensure that the BOM has the ATP flag set as well. if the item needs to be transferred from M2 to M1. Check the source and destination instances if operating in a decentralized mode. perform the scheduling activity. then the item attribute 'ATP Components' in M1 should be set to 'Materials Only'. it may be required that an ATP schedule activity needs to be performed.% Please Note: I am adding more to this point. or 'Materials and Resources'.7 or 11. session -SESSION_ID that was generated during step d.0. 29 .