Supply Chain Planning processes ensure that demands for materials and resources are met on time. This requires close collaboration between an organization's project management system and its supply chain. Supply Chain Planning processes can bridge these two functions.
Demands for items required by project activities, or items that must be delivered to as part of a project contract need to be sent to the supply chain planning system from the project management system.
The supply chain planning system determines when these items will be available and sends these dates back to the project management system.
You can enable this functionality with an integration between Oracle Advanced Supply Chain Planning (the Supply Chain Planning system) and Primavera P6 (the Project Management system). A work breakdown structure is created and maintained in Primavera P6. Activities at the lowest level in the work breakdown structure represent the steps required to meet a project's deliverables. Some of these activities have associated material requirements which need to be communicated to the supply chain planning system as demands.
Other activities in the work breakdown structure can track end item deliverables manufactured in the supply chain. Demand for these end item deliverables also need to be communicated from the project plan to the supply chain planning system. Demand for end item deliverables originating from Primavera P6 should also be reconciled against sales orders for end item deliverables in the project's accounting and execution system, for example;
Oracle EBS Project Accounting
Oracle EBS Order Management
The supply chain planning process plans for supplies to meet the project's demands. Constraints in the supply chain as well as the hard pegged versus soft pegged nature of different items results in supplies being planned for different dates and quantities. This supply information must then be exported to the Primavera P6 project plan. This process can have the following benefits:
Increased efficiency in the supply chain management and project management processes
Reduced inventory and supply chain costs
Improved time fulfillment of project deliverables
Demands for materials originating from the Primavera P6 project plan are converted into a master demand schedule that can be used for the supply chain planning process with ASCP. For additional details on the mapping of projects, activities and material resource assignments in Primavera P6 to the demands in ASCP, refer to the Oracle VCP chapter in the Primavera Gateway Implementation and User Guide.
ASCP collects sales orders from the Order Management system. This enables you to plan for:
Sales order demands
Demand communicated from a Primavera P6 master demand schedule
The integration between ASCP and Primavera P6 makes the following assumptions about sales orders:
Demands are managed in Primavera P6 or in Order Management but not both.
When a sales order is booked in Order Management, the item should no longer be marked as a demand item in the Primavera P6 project plan.
The integration between ASCP and Primavera P6 makes the following assumptions about master data:
Items, organizations and item-organization combinations communicated from Primavera P6 to ASCP are existing items or organizations in the source ERP system and are marked as Planned Items.
The Project number and Task number associated with the demands communicated from Primavera P6 to ASCP are existing Project numbers or Task numbers in the source ERP system.
ASCP uses the ERP source system as the system of record for Items, Organizations, Projects and Tasks (demand from Primavera P6 must have a valid Item, Organization, Project or Task defined in the ERP system).
You can create demand schedules in ASCP from projects in Primavera P6 that include any of the following:
One demand schedule per project
One demand schedule for all projects within a specified level in the Enterprise Project Structure as defined in Primavera P6
One demand schedule for all projects within the Enterprise Project Structure as defined in Primavera P6
When an integration flow is launched in Primavera Gateway, all demands that belong to the specified Demand Schedule Name are removed from the ASCP operational data store and replaced with a fresh snapshot of the demands extracted from Primavera P6.
Primavera Gateway enables the exporting of project level demands from Primavera P6 to ASCP. When the Demand Flow business process is invoked in Primavera Gateway, projects in Primavera P6 (including activities and material resource assignments) are transformed to a set of demands. This set of demands is part of a master demand schedule that can be incorporated into an ASCP plan.
For additional mapping details between ASCP and Primavera P6 refer to the Oracle VCP Provider chapter in the Primavera Gateway Implementation and User Guide
When the export process from Primavera P6 to ASCP is complete, create the supply chain plan in ASCP to meet the project demands as follows:
The ASCP Plan options should be configured to include the MDS names exported from Primavera P6 as input demand schedules at for the appropriate organizations. This is a one-time setup step.
The ASCP Plan should be run to generate supplies to meet the Primavera P6 material and sales order demands. This happens during every planning cycle.
To enable project level planning in ASCP, follow these steps before running a plan:
Ensure that item pegging attributes are set to either soft-pegged or hard-pegged, according to functional requirements.
Set the plan options Reservation Level and Hard Pegging Level, according to functional requirements.
Set the MSC: Attribute Based Netting profile option to Yes.
In ASCP Plan Options, specify the Master Demand schedule created by the integration process as an input demand schedule.
Primavera Gateway enables the exporting of supply dates and order numbers from ASCP to Primavera P6. When the Supply Flow business process is invoked in Primavera Gateway, supply details are exported from the ASCP plan and the Primavera P6 project plan is updated accordingly. The three modes of supply feedback are as follows:
Demand level supply feedback only
Supply availability information for the demand is exported from ASCP to Primavera P6 for the following attributes only:
Supply Availability Date: The date on which supply is available to meet demand
Supply Order Type: The order type of the supply that meets the demand
Supply Order Number: The order number of the supply that meets the demand
Note: If there are multiple finished good supplies that peg to a demand, the most recent supply is used to publish the Supply Order Type and Order Number Information to Primavera P6.
Detailed Supply feedback for demand that originated in Primavera P6
Supply details at the finished good level and the lower levels in the bill of material are included in the feedback from ASCP to Primavera P6. There are three sub-options within this option:
Option A – Include supply feedback for all items
Option B – Include supply feedback for hard pegged items only
Option C – Include supply feedback for the specified Category or Category Set only
Detailed Supply feedback for demand that did not originate in Primavera P6.
Supply information is sent from ASCP to Primavera P6 for demands that did not originate in Primavera P6, such as sales orders and forecasts.
For additional mapping details between ASCP and Primavera P6 refer to the Oracle VCP Provider chapter in the Primavera Gateway Implementation and User Guide.
The following supply attributes are included when publishing detailed supply feedback from ASCP to Primavera P6:
| Attribute | Description |
| End_Pegged_Demand_Activity_ID | The Activity ID of the end demand pegged to this supply. For non Primavera demands, this is set to NULL. |
| End_Pegged_Demand_Order_Number | The Demand Order number of the end demand pegged to this supply. |
| Order_Type | The order type of the supply. For example, On Hand, Work Order, Planned Order. |
| Order_Number | The order number of the supply. |
| Order_Date | The date on which the supply order is placed or planned to be placed. For purchase orders, this is the PO creation date. |
| Start_Date | The date on which the supply order is to start (applies primarily to manufacturing orders). |
| Actual_Start_Date | If a manufacturing work order has already started, this date indicates the actual start date. |
| Ship_Date | The date on which the supply order is planned to ship (applies to Inter organization shipments). |
| Dock_Date | The date on which a supply order arrives at the receiving dock (applies to purchase orders and inter organization shipments). |
| Due_Date | The due date of the supply, the date on which the supply is available for use to meet demands. |
| Updated_Arrival_Date | The arrival date for supplies as updated by Oracle Transportation management. |
| Item | The item that is supplied. |
| Organization: | The organization corresponding to the supply. |
| Quantity | The quantity of the supply. |
| Project Number | The project number to which this supply is pegged. |
| Task Number | The task number to which this supply is pegged. |