Project MRP is one of a series of features in Oracle Applications designed to support companies that manufacture products for projects or contracts. Known as Project Manufacturing, it is a solution that combines Oracle Projects with Oracle's manufacturing applications to provide robust project tracking, billing and budgeting, along with support for hybrid manufacturing methodologies.
Project MRP allows you to plan in a project or contract environment by segmenting all sources of supply and demand by project. This allows the planning process to identify components as shared or project specific, track existing inventories by project, and provide visibility to all supply and demand associated with a project.
Project MRP is completely integrated with Oracle Projects, to offer a comprehensive project manufacturing solution, but it can also work in isolation to support Seiban manufacturing methods.
With Project MRP, you can:
include project or Seiban numbers and task references in forecast, MPS, and MDS entries
load, copy, or merge forecast, MPS, and MDS entries with project or Seiban numbers and task references recognize and allocate supply according to project or Seiban numbers and task references combine project and Seiban related supply and demand with nonproject and nonSeiban related supply and demand in the same plan or schedule perform netting by planning groups, project or Seiban, and tasks generate planned orders with project or Seiban number and task references execute a plan (in the Planner Workbench) by project, Seiban, and task link sales order lines, production orders, and purchase orders to projects, Seibans, and tasks, allocate onhand inventory to projects, and issue inventory to projects
perform net change simulation in a project environment
create a payback transaction as a supply for the lending project, and a demand for the borrowing project – and view these transactions in the Planner Workbench use model/unit effectivity to create demand and generate planned orders with unit number specified
See also:
Establishing a Project MRP Environment
Viewing Onhand Quantities in a Project
Model/Unit Effectivity, Oracle Project Manufacturing Implementation Manual
Borrow Payback, Oracle Project Manufacturing User's Guide
Project MRP is part of the overall solution offered by Project Manufacturing. If you want you employ all the features offered by Project Manufacturing, you must define project parameters in Oracle Projects, Oracle Inventory, and Oracle MRP.
If you are working in a Seiban manufacturing environment, you do not need to include Oracle Projects in your setup tasks.
The setup tasks in Oracle Projects are:
Define projects and tasks in Oracle Projects. This phase is not necessary in a Seiban environment.
Setup tasks in Oracle Inventory
Define organization level project parameters.
Define subinventories.
Define item attributes.
Setup tasks in Oracle MRP
Define planning group lookups.
Associate a project to a planning group.
Define Seiban numbers (optional).
These setup steps are not necessary if you are using Seiban numbers only.
To define a project
Navigate to the Projects, Templates Summary window.
To complete this task, refer to Creating a New Project from a Project Template or an Existing Project, Oracle Projects User's Guide.
See also:
Overview of Project MRP
Setting Up Project MRP in Oracle Inventory
Defining Planning Group Lookups
To define project information in organization parameters
Navigate to the Project Manufacturing Parameters window.
Choose the General tabbed region.
Check Enable Project Reference.
Select a project control level (the project control level determines the level at which the organization is allowed to control its project activity):
Project: You will be able to associate demand and supply records with project references, as well as plan at the project level. Task references will be disabled in all windows.
Task: You will be able to associate demand and supply records with project and task references, as well as plan at the project level.
See: Defining Default Inventory Parameters, Oracle Inventory User's Guide for defining additional organization parameters.
To define project information in subinventories
Navigate to the Master Item window.
Enter a unique alphanumeric name.
Select the Item Subinventories window from the Tools menu.
In the Planning tabbed region, place your cursor in the Locator field to display the Stock Locators parameter window.
Enter a project/Seiban number and, if appropriate, a task reference. See: Defining Stock Locators, Oracle Inventory User's Guide.
Save your work.
To define project information in item attributes
Navigate to the Master Item window.
Choose the MPS/MRP Planning tabbed region.
Select a pegging level:
Soft Pegging:The planning process will allocate supply for a project–task (or Seiban) to demand for the project–task (or Seiban), according to the Reservation Level set in the plan level options.
All reservations of supply to demand records is for a single item. Common, nonproject supply is used to satisfy project demand. For a soft pegged item, excess project supply (or common supply) is always available to another project's demand.
No project references will be attached to planned orders issued to soft pegged items.
You can also generate a graphical pegging display in a nonproject environment, for plans with pegging enabled.
End Assembly Pegging:Also known as Where Used, this option traces the Pegging end assembly the item is pegged to at the top of the bill of material. Even if you do not select end assembly pegging, you can still calculate and view end assemblies online.
You can also generate a graphical pegging display in a nonproject environment, for plans with pegging enabled.
End Assembly/ Soft Pegging :Choose this option for both soft pegging and end assembly pegging.
You can also generate a pegging display in a nonproject environment, for plans with full pegging enabled.
Hard Pegging: The planning process will allocate supply for a project–task (or Seiban) to demand for the project–task (or Seiban), according to the Reservation Level set in the plan level options.
A hard pegged item will not have access to common, nonproject supply. Excess supply from one project can only be shared among projects in the same planning group, provided reservation level is set at planning group.
Project references are attached to planned orders for hard pegged items.
You can also generate a graphical pegging display in a project environment, for plans with full pegging enabled.
End Assembly/ Hard Pegging:Choose this option for both hard pegging and end assembly pegging.
You can also generate a graphical pegging display in a project environment, for plans with full pegging enabled.
None: This option disables project material allocation, end assembly pegging, and graphics in full pegging.
See: Defining Items, Oracle Inventory User's Guide for defining additional item attributes. See: Viewing Pegged Supply and Demand for information on full pegging.
See also:
Overview of Project MRP
Setting Up Project MRP in Oracle Projects
Defining Planning Group Lookups
Defining Planning Group Lookups
Planning groups allow you to establish a relationship between two or more projects or Seibans by associating them with a single planning group. Projects and Seibans within the planning group can share supply, depending upon the reservation level set in the plan level options.
To define planning group lookups
Navigate to the Planning Group Lookups window.
Place the cursor in the Code field, choose New from the File menu.
Enter a unique alphanumeric code.
Enter a meaning and description.
Enter a start date, and optionally and end date to restrict the effectivity of the Lookup.
Check Enabled to activate the Lookup
Save your work.
See also:
Reviewing or Adding Project MRP Plan Options:
Setting Up Project MRP in Oracle Projects
Setting Up Project MRP in Oracle Inventory
After establishing a project MRP environment, you must define an DRP, MPS, or MRP name. See: Defining MRP Names
To review or add Project MRP plan options
Navigate to the Plan Options window.
Query a plan name.
Check Pegging. This will optionally allow you to set a Reservation Level and a Hard Pegging Level when in a projects environment. (It will also allow you to generate a graphical pegging display, if the pegging attribute for your item is not set to None)
In the Pegging region, set a Reservation Level and (optionally) a Hard Pegging Level.
Reservation Level: Determine how the planning process will pre–allocate project/Seiban supply to project/Seiban demand. This will control only those items whose item attributes have been set to Soft Pegging, End Assembly/Soft Pegging, Hard Pegging, or End Assembly/Hard Pegging.
Planning Group: Reserve project–specific supply and demand at the planning group level. Supply for one project can be reserved against demand from another project, if both projects belong to the same planning group. Excess common supply can be allocated to project demand for hard and soft pegged items.
if reservation level is project supply from due project, it cannot be given a demand from another project. Only soft pegged items excess project supply can be allocated to other projects.
Task: Reserve supply for a project–task against demand for the same project–task only.
None: The planning process does not operate in a project manufacturing environment.
Hard Pegging Level: For hard pegged items, determine if project references will be added to planned orders. This will control only those items whose item attributes have been set to Hard Pegging or End Assembly/Hard Pegging. Suggested planned orders for such items will be assigned at one of the following levels.
Project: Attach the project number to which the planned order is hard pegged.
Project-task: Attach the project and task number to which the planned order is hard pegged.
None: Do not add project/task references to planned orders.
See: Reviewing or Adding Plan Options for additional plan options.
Save your work.
See also:
Overview of Project MRP
Setting Up Project MRP in Oracle Project Manufacturing
Launching a Project MRP Plan
Before launching, insure that project demand is loaded into your MDS via forecast consumption entries and sales orders, or choose MRP/DRP/MPS plans with firm planned orders.
After establishing a project MRP environment and adding your Project MRP plan options, perform the following tasks before setting plan level options:
Enter forecast entries with project/Seiban numbers and task references, or load/copy/merge a forecast with project/Seiban numbers and task references. See: Defining a Forecast, or Copying/Merging Forecasts
Enter schedule entries with project/Seiban numbers and task references, or load/copy/merge a schedule with project/Seiban numbers and task references. See: Defining Schedule Entries Manually, or Loading a Master Schedule from an Internal Source.
Setting up Project MRP in Oracle Project Manufacturing involves the following steps:
Defining Seiban Number, Oracle Project Manufacturing User's Guide
Assigning Project Parameters, Oracle Project Manufacturing User's Guide
Project MRP planning logic differs from the regular MRP planning logic primarily in the way it determines what supply is available to satisfy demand. It also differs in the way it assigns any suggested planned orders that result from the planning process.
Instead of simply considering existing inventories and scheduled receipts when netting supply against demand, the project MRP planning logic goes through a process of pre–allocation: Before netting supply against demand, the planning process analyses the project/Seiban numbers (along with the item attributes, project parameters, and plan level options you have set), to determine what supply is available for meeting project/Seiban demand. Supply and demand that is not specific to any project/Seiban is defined as common supply. The project MRP planning logic treats common supply or demand as a “null” project/Seiban.
In order for Project MRP planning logic to work, you must set the pegging item attribute on the items to one of the following values: soft pegging, end assembly/soft pegging, hard pegging, or end assembly/hard pegging.
The following table compares the logic in regular MRP and project MRP:
| Regular MRP | Project MRP |
|---|---|
| Explode bill of materials | Explode bill of materials |
| Snapshot of inventory, supply, and demand | Snapshot of inventory, supply, and demand |
| -- | Pre-allocate supply to projects and seibans |
| Net supply against demand | Net supply against demand and assign planned orders to projects and seibans |
In the following diagram, the item is an MRP–planned component used in two projects and in the common supply.
During the pre–allocation phase of netting, the planning engine divides the supply for the item by project. In Period 1, the demand from project 2 (P2) is 100. Since there is an onhand quantity of 25 for P2 and no scheduled receipts, there is still demand for P2 of 75. The planning engine cannot apply excess from any other source to meet this demand, the planning engine looks for the available supply for P2 and finds it in Period 2. This supply is rescheduled in to Period 1. This scheduled receipt is also used to satisfy the P2 demand of 500 in Period 2.
Once again, the planning engine can only apply the excess P2 supply to P2 demand. The last P2 demand is in Period 3 (for 300), consuming the excess of 25 from Period 2 and leaving a net requirement of 275, which the planning engine converts into planned orders.
Because the item is hard pegged, and the hard pegging level (from the plan options) is set to project, the P2 project reference is added to the suggested planned order.
In this diagram:
Item pegging: Hard pegging
Reservation level: Project
Hard pegging level: Project
On hand (common supply): 5
On hand (P1): 10
On hand (P2): 25
| Entity | Period 1 | Period 2 | Period 3 |
|---|---|---|---|
| Demand | 200 (P1) 100 (P2) 400 (common) |
150 (P1) 500 (P2) |
300 (P2) |
| Scheduled receipts | 265 (P1) | 600 (P2) | 600 (common) |
| Planned orders | -- | 75 (P1) | 275 (P2) |
| Projected available | 75 (P1) -75 (P2) -395 (common) |
0 (P1) 25 (P2) 395 (common) |
0 (P1) 0 (P2) 205 (common) |
In the following diagram, the item is an MRP–planned component used in two projects and in the common supply.
During the pre–allocation phase of netting, the planning engine divides the supply for the item by project (common is treated as project). Period 1 has a common demand of 400. The net demand after applying the common onhand is 395 in Period 1. The scheduled receipts in Period 3 are allocated to this demand. There is no more common demand to be met.
Project P1 has an excess of 75 in Period 1 (scheduled receipts plus the onhand quantity, minus P1 demand). This is used to partially satisfy the P1 demand of 150 in Period 2. This leaves an unmet demand of 75 in period 2 for project P1. There is no supply available. Unlike the hard pegging example, the planning process can use other excess supply in this period to meet this remaining demand. Therefore, the excess supply of common in Period 3 is allocated to this demand.
Item 7004 is a soft pegged item, it can use excess supply available in common or other projects to meet this demand. It allocates the excess supply from 600 common to this demand.
For project P2 the demand in period 1 is 100. Since there is an onhand quantity of 25 for P2 and no scheduled receipts in this period, there is still a demand of 75 for P2. To meet this demand, the planning engine looks for more P2 supply, which it finds in period 2. This supply of 600 is allocated to the demand of P2 in period 1. This supply also takes care of the demand for 500 for project P2 in period 2. The available 25 in project P2 at the end of period 2 are pegged to the P2 demand of 300 in period 3. This leaves a demand of 275 for project P2 in period 3. As there is no P2 supply, and the item is a soft pegged item, it uses the excess 130 in common supply. There is still a shortage of 145. The planning engine then creates a planned order for 145. Since item 7004 is soft pegged, this planned order will not carry any project references.
Note: Project references on scheduled receipts of soft pegged items must be entered manually.
See also Project References, Oracle Project Manufacturing User's Guide.
In this diagram:
Item pegging: Soft pegging
Reservation level: Project
Hard pegging level: Project
On hand (common supply): 5
On hand (P1): 10
On hand (P2): 25
| Entity | Period 1 | Period 2 | Period 3 |
|---|---|---|---|
| Demand | 200 (P1) 100 (P2) 400 (common) |
150 (P1) 500 (P2) |
300 (P2) |
| Scheduled receipts | 265 (P1) | 600 (P2) | 600 (common) |
| Planned orders | -- | 75 (P1) | 145 |
| Projected available | 75 (P1) -75 (P2) -395 (common) |
-75 (P1) 25 (P2) 395 (common) |
0 (P1) 0 (P2) 0 (common) |
By combining the item pegging attribute with the plan options reservation and hard pegging levels, you can exercise a high degree of control over how the planning process pre–allocates supply for an item. The table below summarizes the possible combinations and types of behavior you can enforce:
| Reservation Level | Hard Pegging Level | Item Pegging Attribute | Netting Behavior |
|---|---|---|---|
| Planning Group | Project | Hard Pegging | Reserve supply at planning group level, excess common supply used for project demand, and create planned orders at project level |
| Planning Group | Project-Task | Hard Pegging | Reserve supply at planning group level, excess common supply used for project demand, and create planned orders at project-task level |
| Planning Group | None | Hard Pegging | Reserve supply at planning group level, excess common supply used for project demand, and create planned orders without project references |
| Project | Project | Hard Pegging | Reserve supply at project-task level, create planned orders at project level |
| Project | Project-Task | Hard Pegging | Reserve supply at project-task level, create planned orders at project-task level |
| Project | None | Hard Pegging | Reserve supply at project-task level, create planned orders without project references |
| Project-Task | Project | Hard Pegging | Reserve supply at project-task level, create planned orders at project level |
| Project-Task | Project-Task | Hard Pegging | Reserve supply at project-task level, create planned orders at project level |
| Project-Task | None | Hard Pegging | Reserve supply at project-task level, create planned orders without project references |
| Planning Group Project Project-Task |
<any value> | Soft Pegging | Reserve supply at project level, create planned orders without project references |
| None | Hard Pegging | No reservations, full pegging |
Excess Supply
| Item Attribute | Allocation of Excess Supply |
|---|---|
| Hard Pegging or End Assembly/Hard Pegging | Planning logic ignores excess in common supplies and project- and seiban-specific supplies during the netting routine |
| Soft Pegging or End Assembly/Soft Pegging | Planning logic considers excess in common supplies and project- and seiban-specific supplies during the netting routine |