Professional Documents
Culture Documents
BR.100AMRP MASTER
SCHEDULING MRP APPLICATION
SETUP
<Company Long Name>
<Subject>
Author: <Author>
Creation Date: June 7, 1999
Last Updated: June 7, 1999
Document Ref: <Document Reference Number>
Version: DRAFT 1A
Approvals:
<Approver 1>
<Approver 2>
BR.100Amrp Master Scheduling MRP Application Setup Doc Ref: <Document Reference Number>
June 7, 1999
Document Control
Change Record
6
Reviewers
Name Position
Distribution
Note To Holders:
If you receive an electronic copy of this document and print it out, please write your
name on the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.
Contents
Document Control.....................................................................................................................
Workflow Set Up Responsibility Due Date QA Responsibility QA Due Date Signature Approval
SubWorkflow Name
MRP Setup
Workflow Set Up Responsibility Due Date QA Responsibility QA Due Date Signature Approval
SubWorkflow Name
Inventory>Setup>Planners
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define and update material Planners or planning entities.
<Planners>
Planner Name Description Employee Code Email Address Inactive Date
Planning>Setup>Parameters
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this region to define and update the execution default Parameters for Oracle Master Scheduling/MRP.
<Planning Parameters>
Snapshot Lock Tables Default ABC Assignment Group
Execution Defaults:
Planned Item
Planning>Setup>Planning Manager
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to start the concurrent manager named the Planning Manager. One of the main jobs of the Planning Manager is to keep the
MTL_DEMAND table updated.
Planning>Setup>Exception Set
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this region to define or update the Planning Exception sets for Oracle Master Scheduling/MRP.
Sensitivity Controls:
Excess Quantity
Repetitive Variance
Over Utilized
Under Utilized
Shortage Exceptions
Excess Exceptions
Overpromised Exceptions
Planning>Setup>Demand Class
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to establish Quick Codes for Demand Classes. Demand Classes are Marketing channels that can be used for forecasting and
planning. This is a QuickCode form and should come seeded with Demand Class type.
<Demand Classes>
Code Meaning Description Start Date End Date Enabled?
Setup>Product Families
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the members of Product Families and their allocation percent of forecasts. Product Families are defined in INV: Master
<Product Family>
Product Family Item Description Member Item Description Planning % Effective From Effective To Inactive On
Planning>Forecasts>Sets
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to establish independent Forecast demand. Sets comprise of Forecast Names, which comprise of the Items forecasted and their
detailed Forecast entries.
<Forecast Sets>
Set Name Set Description Bucket Type Default Level Inactive On Consume Outliner % Forward Days Backward Days
<Forecast Names>
F/C Name F/C Description Inactive On Demand Class Customer
Planning>MDS>Names
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Master Demand Schedule Names. A MDS is a statement of shipments and can be loaded from Sales Orders, Forecasts,
Inter-org transfers, or spares entries.
Planning>MPS>Names
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Master Production Plan Names for both Production Schedules and Simulation plans.
Planning>MRP>Names
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the Names for Material Requirement Plans.
Planning>Kanban>Names
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the Names for Kanban plans. Kanbans are defined in INV: Master Items with Release field set to Kanban. A Pull
Sequence is defined to replenish Kanban Locations and establish order modifiers. A Kanban plan will calculate kanban lot sizes per location based on
Demand Type and Demand horizon. Pull Sequences are established in either Inventory or Flow Manufacturing responsibilities.
Planning>MPS>Options
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the processing Options for Master Production Schedules.
<Plan Options>
Plan (Plan) Type
Overwrite
Planned Items
Pegging:
Pegging (Yes)
Reservation Level
Subinventory Netting
<Subinventory Nettng>
Name Description Net
Planning>MRP>Options
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the processing Options for Material Requirement Plans.
<Plan Options>
Plan (Plan) Type
Overwrite
Plan Capacity
Bill of Resource
Simulation Set
Pegging:
Pegging (Yes)
Reservation Level
Planned Items
Subinventory Netting
<Subinventory Nettng>
Name Description Net
Planning>Reports>SRS
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to run the Audit Information Report and verify planning data.
<Submit Requests>
Type
Name
Parameters
Style
Printer
Run Options:
Resubmit
From
To Start
Save Output
End Resubmission
Submission History:
Open Issues
Closed Issues