Skip Headers

Oracle Global Order Promising Implementation and User's Guide
Release 12.1
Part Number E13378-07
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Setting Up

This chapter covers the following topics:

System Setup

The following section explains the system and database preparation for Oracle Global Order Promising.

The Source instance refers to the database where other enterprise resource planning (ERP) applications, including Oracle Order Management, reside. The Destination instance refers to the database where Oracle Global Order Promising and Oracle Advanced Supply Chain Planning reside.

One Instance Setup

When Oracle Global Order Promising resides on the same instance as the other ERP applications, you must perform the following system setup steps:

One Instance Setup

the picture is described in the document text

  1. Install Patches:

    Context: Perform this step only once.

    Required: Yes

    Install the Oracle Global Order Promising (or ATP) source and destination patches on the same instance. Also, apply the Data Collection patches. The patch numbers can be release-specific. You can find the patch numbers on Oracle Support Metalink, under Top Tech Docs in Advanced Planning and Scheduling, or by contacting Oracle Support.

    Note: Before beginning the installation of the source patch, count all, if any, invalid database objects. If after the patch is installed, the number of invalid objects has increased, then a problem occurred with the patch application.

  2. Run Create APS Partitions Concurrent Program:

    Context: Perform this step only once.

    Required: Yes

    Run Create APS Partitions concurrent program. This step is also part of Oracle Advanced Supply Chain Planning system setup. If you already performed this step as part of Oracle Advanced Supply Chain Planning setup, you do not need to repeat this step.

    Note: This step is not needed unless the profile MSC: Share Plan Partitions is set to No.

  3. Run Create ATP Partitions Request

    Context:Perform this step only once.

    Required:Yes

    Run Create ATP Partitions request. The profile MSC: Share Plan Partitions mustbe set to NO before this request is run.

  4. Run Create Global ATP Flexfields Concurrent Program:

    Context: Run this program on the source instance only if you are on Release 10.7 or Release 11.

    Required: Yes

    The Create Global ATP Flexfields concurrent program creates new flexfield segments to hold ATP data at the item, bills of material, routing, and resource levels.

  5. Define Instance:

    Context: Set up for each source instance.

    Required: Yes

    Under the Order Management User responsibility, go to Scheduling, ATP, and Scheduling Setup. Then, select Instances.

    Application Instances Window

    the picture is described in the document text

  6. Run Create ATP Partitions Concurrent Program:

    Context: Run this concurrent program if you are if upgrading from a previous 11i release.

    Required: Yes.

Two Instances Setup

When Oracle Global Order Promising resides on two instances as the other ERP applications, you must perform the following system setup steps:

Two Instances Setup

the picture is described in the document text

  1. Install Patches:

    Context: Perform this step only once.

    Required: Yes

    Step 1 Install Patches

    Install the Oracle Global Order Promising source patches on the source instance and the Oracle Global Order Promising destination patches on the destination instance. Also, apply the Data Collection patches. The patch numbers can be release specific. You can find the patch numbers from Oracle Support Metalink, under Top Tech Docs in Advanced Planning and Scheduling, or by contacting Oracle Support.

    Note: Before beginning the installation of the source patch, count all, if any, invalid database objects. If after the patch is installed, the number of invalid objects has increased, then there a problem occurred with the patch application.

  2. Create Database Links:

    Context: Perform this step only once.

    Required: Yes

    The database administrator must create two database links: one that points from the source database to the destination database and another that points from the destination database to the source database.

    If you want the source instance to be in the Real Application Clusters (RAC) environment, you must manually create the table MSC_APPS_INSTANCE_NODES with individual database links using sql. This table holds individual database links between the APS instance and each individual Real Application Clusters (RAC) node at the source instance. Load balancing is supported on the source only.

    The table structure for MSC_APPS_INSTANCE_NODES is:

    Field Name Null? Type
    INSTANCE_ID NOT NULL NUMBER
    NODE_ID NOT NULL NUMBER
    M2A_DBLINK - VARCHAR2(128)
    LAST_UPDATE_DATE - DATE
    LATS_UPDATED_BY - NUMBER
    CREATION_DATE - DATE
    CREATED_BY - NUMBER
    LAST_UPDATE_LOGIN - NUMBER
  3. Run Create APS Partition Concurrent Program:

    Context: Perform this step on the instance where Oracle Global Order Promising resides.

    Required: Yes

    Run the Create APS Partitions concurrent program. This step is also part of the Oracle Advanced Supply Chain Planning system setup. If you already performed this step as part of the Oracle Advanced Supply Chain Planning setup, you do not need to repeat this step.

    Note: This step is not needed unless the profile MSC: Share Plan Partitions is set to No.

  4. Run Create Global ATP Flexfields Concurrent Program:

    Context: Run this program on the source instance only if you are on Release 10.7 or Release 11.

    Required: Yes

    The Create Global ATP Flexfields concurrent program creates new flexfield segments to hold ATP data at the item, bills of material, routing, and resource levels.

  5. Define Instance:

    Context: Set up for each source instance. Perform the setup on the destination instance.

    Required: Yes

    Under the Oracle Advanced Supply Chain Planner responsibility, set up the Instances window.

    Note: This Instances window resides on the destination instance.

    Application Instances Window

    the picture is described in the document text

  6. Run Create ATP Partitions Concurrent Program

    Context: Run this concurrent program if you are if upgrading from a previous 11i release.

    Required: Yes.

Functional Setup for ATP Based on Collected Data

The following section explains the functional setup steps for ATP Based on Collected Data.

ATP Based on Collected Data Setup Flow

The diagram below provides a pictorial view of the ATP Based on Collected Data setup steps.

the picture is described in the document text

  1. Check ATP item attribute:

    Context: Perform this step for every item.

    Required: Yes

    Oracle Global Order Promising (GOP) uses this flag to determine whether to use the supply of this item to promise demand. Set the Check ATP Flag item attribute to either:

    The Material and Resource option and the Resource only option are not currently supported.

    For details on defining item attributes, see Defining Item Attributes in Oracle Inventory User's Guide.

  2. ATP Rules

    Context: Every item that can be available to promise must have an ATP Rule assigned. An ATP Rule can be used for multiple items.

    Required: Yes

    You must define ATP Rules. An ATP Rule indicates the ATP options. Each ATP Rule is a combination of time fence options, supply sources, and demand sources to use during the ATP Inquiry.

    To define an ATP Rule:

    1. Navigate to the Rules section in Inventory setup, and find Available-To-Promise.

      the picture is described in the document text

    2. Enter a unique name and a description for the ATP Rule.

      • Oracle Global Order Promising always performs Backward Consumption, regardless of the setting.

      • Oracle Global Order Promising always performs Forward Consumption, regardless of the setting.

      • Oracle Global Order Promising always performs Accumulation, regardless of the setting.

    3. You can use Past Due Supply and Demand Days fields to limit supply and demand using past due dates. Either enter the number of days to limit the past-due demand and supply or leave blank for the inclusion of all the past due supply and demand. When calculating the ATP quantity of an item, Oracle Global Order Promising does not consider any demand or supply source before these dates.

    4. The Infinite Supply Time Fence specifies the end of your ATP horizon. ATP considers any demand that falls beyond this time fence as available. This value appears in the ATP Details window as 10,000,000 available on the horizon date. The four options are:

      • Cumulative total lead time: The total lead time of an assembly plus the largest adjusted cumulative total lead time of its components.

      • Cumulative manufacturing lead time: The manufacturing lead time of an assembly. This value may also include and add to the previous lead time, the largest adjusted cumulative manufacturing lead time of its components. This condition only occurs for ATO items.

      • Total lead time: The sum of the pre-processing, processing, and post-processing lead times of the item.

      • Defining your demand classes enables Demand Class ATP.

        User-defined time fence: The lead time that you specify in the Days field.

    5. The ATP by Demand Class indicates whether to calculate ATP based on defined demand classes. Demand classes allow you to segregate scheduled demand into user-defined groups. If you choose to calculate ATP based on defined demand classes, then the following Supply Source options are not available:

      • On-hand available

      • Inter-org transfers

      • Purchase orders

      • Internal and supplier requisitions

        Defining you demand classes enables Demand Class ATP.

        For details, see Demand Class ATP.

    6. Select the Demand and Supply Sources to use in ATP calculations. When you use ATP based on the collected data, then supply and demand are specified in the ATP rules.

      The possible supply sources are:

      • Discrete Master Production Schedule (MPS)

      • Repetitive MPS

      • Discrete Work-In-Process (WIP)

      • Repetitive WIP

      • Non-standard WIP

      • Available QOH

      • Internal requisitions

      • Vendor requisitions

      • Purchase orders

      • Intransit shipments

      • User-defined supply

        You control which sources are selected for consideration for the availability requests. You use the On-Hand Available check box to choose whether to include the available on-hand quantity as a source of supply. Typically, make-to-order and assemble-to-order manufacturing environments do not use the available on-hand quantity as a source of supply. Oracle Global Order Promising designates a supply period as beginning on a scheduled supply date and ending the day before the next scheduled supply date. A supply period covers several days or can be a minimum of one day in duration. If supply occurs on a non-work day, the ATP calculation considers that supply as belonging to the next work day. If multiple supply events occur on the same day, then the ATP process sums the supplies.

        The possible demand sources are:

      • Sales orders

      • Internal orders

      • Discrete WIP demand

      • Repetitive WIP demand

    7. Save your work.

    Example

    The following example explains how Oracle Global Order Promising performs Backward Consumption, Forward Consumption, and Accumulation when calculating the quantities available to promise.

    Assume supply and existing demand as follows:

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 -35 0 -25
    1. Calculate net availability for each bucket as follows: Net = Supply - Demand.

      Day 1 Day 2 Day 3 Day 4
      Supply 20 10 20 20
      Demand 0 -35 0 -25
      Net 20 -25 20 -5
    2. For each negative Net value, perform backward consumption and forward consumption until no negative values appear.

    3. On Day 2, Net = –25. Consume backward. On Day 1, 20 are available to cover the partial shortage. Availability on Day 1 becomes 0.

      Day 1 Day 2 Day 3 Day 4
      Supply 20 10 20 20
      Demand 0 -35 0 -25
      Net 20 -25 20 -5
      Backward 0 -5 20 -5
    4. After consuming the 20 units backward, supply is still 5 short on Day 2. Consume forward. On Day 3, 20 units are available to cover the shortage, - 5 on Day 2. Availability on Day 3 becomes 15.

      Day 1 Day 2 Day 3 Day 4
      Supply 20 10 20 20
      Demand 0 -35 0 -25
      Net 20 -25 20 -5
      Forward 0 0 15 -5
    5. Day 2 no longer has a shortage. On Day 4, a shortage of 5 occurs. Consume backward. On Day 3, 15 are available to cover the shortage. Availability on Day 3 becomes 10.

      Day 1 Day 2 Day 3 Day 4
      Supply 20 10 20 20
      Demand 0 -35 0 -25
      Net 20 -25 20 -5
      Backward 0 0 10 0
    6. Accumulate the above result starting from Day 1.

      Day 1 Day 2 Day 3 Day 4
      Supply 20 10 20 20
      Demand 0 -35 0 -25
      Net 20 -25 20 -5
      Cum 0 0 10 10

      The cumulative quantity on each day is the quantity available to promise for that day.

  3. Profile INV: Capable to Promise

    Context: Perform this step only once.

    Required: Yes

    When Oracle Global Order Promising is deployed without Oracle Advanced Supply Chain Planning, ATP is based on collected, transactional data. You set this profile to ATP Based on Collected Data.

  4. MSC: Enable ATP Summary Mode Profile

    Context: Perform this step only once.

    Required: Optional

    Oracle Global Order Promising response times can be improved by means of a summary approach that stores summary supply and demand information.

    Set this profile to Yes to use the summary approach. You may only set this profile to Yes when Oracle Global Order Promising is on the same instance as other ERP applications.

    The summary process is accomplished through a concurrent program that is automatically launched through Data Collection. For a detailed explanation on ATP summary approach, see Improved ATP Performance.

  5. Transit Lead Time

    Context: Ongoing maintenance.

    Required: Optional

    If a transit lead time exists between your shipping warehouse and your customer, then you must define the lead time for each shipping method using the Transit Times form in Oracle Shipping. You define your shipping network from most specific to least specific at the following levels:

    Transit Times Window

    the picture is described in the document text

    According to the a given shipping method on an ATP request, Oracle Global Order Promising searches for the shipping method in the three levels listed previously from the most specific to the least specific. If it finds the shipping method in a particular level, it use the lead time associated with the shipping method to calculate the scheduled arrival date for an order. If the shipping method is not specified at any level, Oracle Global Order Promising uses the default shipping method and its lead time in any level you define, from the most specific to the least specific.

    For example, you define a shipping lane from your shipping organization to a specific customer location with a shipping method of GROUND, which has a lead time of 3 days. You also define a shipping lane from your shipping organization to a region, where the previous customer resides. This lane has GROUND as a valid shipping method and a lead time of 2 days. On a sales order to this customer using the GROUND shipping method, Oracle Global Order Promising uses 3 days for the transit lead time.

    Before you set up transit times between locations, you should set up shipping methods and a default shipping location as the shipping organization. Optionally, you can set up an internal location and its association with the customer's ship-to address, regions and zones.

    Note: In the Transit Time window, you can setup region-to-region lead time for a ship method. However, Global Order Promising only considers location-to-region transit lead time for a ship method to account for the transit lead time between a shipping organization and a customer's location.

    For detailed setup instructions on Regions, Zones, and Transit Times, see Regions and Zones in Oracle Shipping Execution User's Guide.

  6. Single-Level Supply Chain ATP

    Context: Perform this step when you want to use Single-Level Supply Chain ATP.

    Required: Function specific for Single-Level Supply Chain ATP.

    When multiple shipping organizations are available to fulfill customer orders, Oracle Global Order Promising recommends the desired shipping organization based on sourcing rules that you define.

    For detailed instructions, see Single-Level Supply Chain ATP.

  7. Configuration ATP

    Context: Perform this step when you want to use Configuration ATP.

    Required: Function specific for Configuration ATP.

    Oracle Global Order Promising enables you to promise orders for items used in Configure-To-Order environments.

    For detailed instructions, see Configuration ATP.

  8. Product Family ATP

    Context: Perform this step when you want to use Product Family ATP.

    Required: Function specific for Product Family ATP.

    Oracle Global Order Promising enables you to promise orders at the aggregate level based on product family item supply.

    For detailed instructions, see Product Family ATP.

  9. Demand Class ATP

    Context: Perform this step when you want to use Demand Class ATP.

    Required: Function specific for Demand Class ATP.

    Oracle Global Order Promising lets you promise orders for a specific demand class based on a predetermined supply statement for the same demand class.

    For detailed instructions, see Demand Class ATP.

  10. Audit Statement Report

    Context: Perform this step when you want to check for errors.

    Required: Optional, but strongly recommended.

    The Audit Statement Report concurrent program checks for common data setup errors that can lead to collection or plan failures or incorrect ATP results. You should run this program to validate the ATP setup before you initiate an ATP Inquiry.

    You may run the report for any of the following report areas:

    You can control the level of detail of the resulting audit report. The supported levels of detail are:

  11. Data Collection

    Context: Ongoing

    Required: Yes

    Data Collection is a process that pulls data from source instances into an area called the Operational Data Store (ODS) in Oracle Global Order Promising. Oracle Global Order Promising uses the data in ODS for order promising. When the source data changes, you need to run collections to bring the changes into the ODS so that the ATP result reflects the changes. Source data includes items, ATP Rules, on-hand quantity, WIP jobs, and purchase orders.

    To run data collection without Oracle Advanced Supply Chain Planning, sign on using the Oracle Order Management responsibility, and select ATP Data Collection.

    Currently, the ATP Data Collection concurrent program contains only the following parameters:

    The following table describes the data that ATP Data Collection collects. It also indicates which data entity is supported by the Net Change Refresh mode. When you create a new data entity or update an existing data entity that is not supported by Net Change Refresh, you must run a compete refresh to obtain the new information.

    Data Entity Supported by Net Change Refresh
    ATP Rules No
    Calendars No
    Demand Class No
    Items Yes
    Master Production Schedule Yes
    On Hand Yes
    Purchase Requisitions / Orders Yes
    Sales Orders Yes
    Sourcing Rules No
    Subinventories No
    Trading Partners (Customers) No
    Units of Measure No
    Work-In-Process Yes

Functional Setup for ATP Based on Planning Output

This section explains the functional setup steps for using Oracle Global Order Promising with Oracle Advanced Supply Chain Planning. This functionality is also referred to as ATP (Available-To-Promise) Based on Planning Output.

ATP Based on Planning Output Setup Flow

  1. Check ATP and Component ATP item attributes

    Context: Perform this step for every item.

    Required: Yes

    You can set the Check ATP item attribute to:

    You can set the Component ATP item attribute to:

    Oracle Global Order Promising does not use the Check ATP field on the bill of material. To check or not check the ATP of components, use the appropriate item attribute setting of Component ATP that matches your business need.

    You might not want to check ATP because:

    See Multi-Level Supply Chain ATP for an example of the item attribute setting.

  2. ATP Rule

    Context: Every item that is available-to-promise must have an ATP Rule assigned. An ATP Rule can be used for multiple items.

    Required: Optional

    When Oracle Global Order Promising is based on Oracle Advanced Supply Chain Planning output, you only need to define the infinite supply time fence option in an ATP Rule.

    If you do not associate an ATP Rule to an available-to-promise item, then Oracle Global Order Promising assumes that the infinite time fence is equal to the planning horizon.

    You must set up the ATP Rule for an available-to-promise resource either at the resource level or the organization level.

    To define an ATP Rule:

    Navigate to Inventory Setup and find Available-To-Promise Rules.

    ATP Rules Window

    the picture is described in the document text

    1. Enter a unique name and description for the ATP Rule.

      • Oracle Global Order Promising always performs Backward Consumption, regardless of the setting.

        • Oracle Global Order Promising always performs Forward Consumption, regardless of the setting.

        • Oracle Global Order Promising always performs Accumulation, regardless of the setting.

    2. Oracle Global Order Promising honors all the past due supply and demand quantities that are honored by the Oracle Advanced Supply Chain Planning plan. You do not need to specify a value here.

    3. The Infinite Supply Time Fence specifies the end of your ATP horizon. ATP considers any demand that falls beyond this time fence as available. This value appears in the ATP Details window as 10,000,000 available on the horizon date. If you do not specify a value, Oracle Global Order Promising uses the plan horizon as the infinite time fence. The four options are:

      • Cumulative total lead time: The total lead time of an assembly plus the largest adjusted cumulative total lead time of its components.

      • Cumulative manufacturing lead time: The manufacturing lead time of an assembly. It may also include and add to the previous lead time, the largest adjusted cumulative manufacturing lead time of its components. This functionality only occurs for ATO items.

      • Total lead time: The sum of the pre-processing, processing, and post-processing lead times of the item.

      • User-defined time fence: The lead time that you specify in the Days field.

    4. ATP by Demand Class: Indicate whether to calculate ATP based on defined demand classes. Demand classes allow you to segregate scheduled demand into user-defined groups. If you choose to calculate ATP based on defined demand classes, then the following Supply Source options are not available:

      • On-hand available

      • Inter-org transfers

      • Purchase orders

      • Internal and supplier requisitions

      This is to enable Demand Class ATP.

      For Demand and Supply Sources: When you use ATP based on the planning output, Oracle Global Order Promising honors all of the supply and demand quantities in the Oracle Advanced Supply Chain Planning plan. You do not need to make a selection here.

    5. Save your work.

    Example

    The following example explains how Oracle Global Order Promising performs Backward Consumption, Forward Consumption, and Accumulation when calculating ATP quantities.

    Assume supply and demand as follows:

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 –35 0 -25

    Step 1: Calculate net availability for each bucket as follows. Net = Supply – Demand

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 –35 0 –25
    Net 20 –25 20 –5

    Step 2: For each negative Net value, perform backward consumption and forward consumption until no negative values appear.

    Step 2.1: On Day 2, Net = –25. Consume backward. On Day 1, 20 are available to cover a partial shortage. Availability on Day 1 becomes 0.

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 –35 0 –25
    Net 20 –25 20 –5
    Backward 0 –5 20 –5

    Step 2.2: After consuming the 20 units backward, Day 2 is still 5 short. Consume forward. On Day 3, 20 units are available to cover the shortage (–5). Availability on Day 3 becomes 15.

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 –35 0 –25
    Net 20 –25 20 –5
    Forward 0 0 15 –5

    Step 2.3: Day 2 no longer has a shortage. On Day 4, a shortage of 5 occurs. Consume backward. On Day 3, 15 are available to cover the shortage. Availability on Day 3 becomes 10.

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 –35 0 –25
    Net 20 –25 20 –5
    Backward 0 0 10 0

    Step 3: Accumulate the above result starting from Day 1.

    Day 1 Day 2 Day 3 Day 4
    Supply 20 10 20 20
    Demand 0 –35 0 –25
    Net 20 –25 20 –5
    Cum 0 0 10 10

    The cumulative quantity on each day is the quantity available to promise for that day.

  3. Profile INV: Capable to Promise

    Context: Perform this step on the source and destination instances.

    Required: Yes

    Set this profile to ATP/CTP Based on Planning Data on both the source and destination instances.

  4. Profile MSC: Enable ATP Summary Mode

    Context: Perform this step only once on the destination instance.

    Required: Optional

    Oracle Global Order Promising response times improve with a summary approach that stores summary supply and demand information. Set this profile to Yes to use the summary approach.

    For a detailed explanation of ATP Summary approach, see Improved ATP Performance Based on Summarized Data.

  5. Transit Lead Time

    Context: Ongoing maintenance

    Required: Optional

    If there is transit lead time between your shipping warehouse and customer, you need to define the lead time for each shipping method using the Transit Times form in Oracle Shipping. You define shipping lead times from the most specific to the least specific at the following levels:

    If there is a transit lead time between the supplier and the receiving warehouse, you need to define the lead time for each shipping method at the following levels:

    Transit Times Window

    the picture is described in the document text

    Given a shipping method on an ATP request, Oracle Global Order Promising will search for the shipping method in the three levels listed previously from most specific to least specific. If it finds the shipping method in a particular level, it will use the lead time associated with the shipping method to calculate the scheduled arrival date for an order. If the specified shipping method is not specified at any level, Oracle Global Order Promising will use the default shipping method and its lead time in any level you define, from most specific to least specific.

    For example, you define shipping lane from your shipping organization to a specific customer location with shipping method of GROUND that has a lead time of 3 days. You also define a shipping lane from your shipping organization to a region where the previous customer resides. This lane has GROUND as a valid shipping method, and a lead time of 2 days. On a sales order to this customer using GROUND shipping method, Oracle Global Order Promising uses 3 days for the transit lead time.

    Before you set up transit times between the locations, you need to have set up shipping methods and a default shipping location as the shipping organization. Optionally, you can set up an internal location and its association with the customers ship-to address, regions and zones.

    For detailed instructions, see Transit Times in Oracle Shipping Execution User's Guide.

  6. Multi-Level Supply Chain ATP

    Context: Perform this step for Multi-Level Supply Chain ATP.

    Required: Optional

    Oracle Global Order Promising enables you to promise demand based on the sourcing rule you define for any number of shipping organizations. If the supply is not sufficient, Oracle Global Order Promising “explodes” the supply chain bills of material to find additional component and resource supplies to promise.

    For detailed instructions, see Multi-Level Supply Chain ATP.

  7. Configuration ATP

    Required: Function specific for Configuration ATP

    Oracle Global Order Promising enables you to promise orders for those items used in Configure-To-Order environments.

    For detailed instructions, see Configuration ATP.

  8. Product Family ATP

    Required: Function specific for Product Family ATP

    Oracle Global Order Promising enables you to promise orders at aggregate level based on product family item supply.

    For detailed instructions, see Product Family ATP.

  9. Allocated ATP

    Required: Function specific for Allocated ATP

    Oracle Global Order Promising lets you allocate scarce supply to different sales channels or customers, and promise orders based on allocated supply.

    For detailed instructions, see Allocated ATP.

    Note: The Allocated ATP functionality includes allocation by demand priority. This functionality is a preferred alternative to using the Demand Class ATP functionality, which is also available for ATP Based on Planning Output.

  10. Audit Statement Report

    Required: Optional, but strongly recommended

    The Audit Statement Report concurrent program checks for common data setup errors that may lead to collection or plan failures, or incorrect ATP results. You run this program to validate the ATP setup before you initiate an ATP inquiry.

    You can run the report for any of the following report areas:

    You control the level of detail of the resulting audit report. The supported levels of detail are:

  11. Run Collections

    Context: Ongoing

    Required: Yes

    Data Collection is a process that pulls data from source instances into an area called the Operational Data Store (ODS) in Oracle Global Order Promising and Oracle Advanced Supply Chain Planning. An ASCP plan is run based on the collected data. The output of an ASCP plan is used for order promising. It is typical that you run Collections before you rerun your ASCP plan.

    Also, you need to be logged on using the Advanced Supply Chain Planner responsibility.

    For more information on data collection, see Running Collections in Oracle Advanced Planning and Scheduling Implementation and User's Guide.

  12. ASCP Plan

    Context: As needed

    Required: Yes

    You need to identify a particular plan for ATP by selecting the Check ATP flag in the plan definition window in Oracle Advanced Supply Chain Planning.

    For detailed instructions, see Setting Plan Options in Oracle Advanced Planning and Scheduling Implementation and User's Guide.

  13. Run Plan

    Context: Ongoing

    Required: Yes