1. 1. ASCP Training Manual Author: Creation Date: Last Updated: Document Ref: Version: Approvals:
2. 2. Document Control Change Record Date Author Version Change Reference Reviewers Name Position Distribution Copy No. Name Location 1 2 3 4 2 MSAT Internal Page 7
3. 3. Table of Contents Document Control......................................................................................2 Introduction................................................................................................5 Intended audience.......................................................................................................5 List of attendees..........................................................................................................5 Related training materials...........................................................................................5 Log onto Oracle Applications....................................................................................5 Overview of Oracle Advanced Planning....................................................6 APS data flow.............................................................................................................6 Planning cycle............................................................................................................7 Source Data Setups.....................................................................................7 Setup inventory item attributes...................................................................................7 MPS/MRP planning attributes.................................................................................11 Lead times attributes................................................................................................17 Shipping, Receiving, Carrier, and Supplier Capacity Calendars.............................18 Workday Calendar....................................................................................................19 Setup resource and department.................................................................................19 Setup routing............................................................................................................19 Setup supply chain....................................................................................................20 Order management...................................................................................................28 Data Collection.........................................................................................28 Scope of data collection...........................................................................................28 Data collection methods...........................................................................................28 Run data collection...................................................................................................30 Define an ASCP plan................................................................................33 ASCP plan classes....................................................................................................33 ASCP plan types.......................................................................................................34 Define a plan name...................................................................................................35 Set plan options........................................................................................................35 Launch a plan...........................................................................................................47 Copy a plan...............................................................................................................47 Planner Workbench..................................................................................48 Plan Navigator..........................................................................................................49 Supply chain structure..............................................................................................50 Supply chain plan result analysis.............................................................................56 Supply chain plan executions...................................................................................65 Personal and public queries......................................................................................67 Simulation net change re-plan..................................................................68 Simulate changes......................................................................................................68 Simulation modes.....................................................................................................71 3 MSAT Internal Page 7
4. 4. Running net change replan simulations....................................................................71 Reports......................................................................................................76 Plan comparison report.............................................................................................76 Plan detail report......................................................................................................76 Audit information reports.........................................................................................76 Practicing labs..........................................................................................77 FAQ..........................................................................................................77 1. What calendar quarterly type does ASCP support?.............................................77 2. How are planning buckets and horizon calculated?.............................................77 3. How do I know which days are workdays, which day is week start date and which is period start date?........................................................................................78 4. What lead-times can you define in Oracle Applications?....................................79 5. What lead times may be used by ASCP?.............................................................81 6. How are lead times used by ASCP in planned order date calculation?...............81 7. How does ASCP calculate supply dates?.............................................................84 8. How can I release sales order from ASCP workbench?.......................................84 9. Why do the Supply window and Resource Requirements window show different start and end date/time of a planned order?..............................................................84 Appendix Constraint based planning........................................................86 Constraint types........................................................................................................86 Set constraints for different plan types.....................................................................87 Rules used in constrained plans................................................................................87 4 MSAT Internal Page 7
5. 5. Introduction Intended audience This document is prepared as an introductory training material for the end users of Oracle APPS 11i. It covers the basic skills needed for using Oracle Advanced Supply Chain Planning. It is customized for the manufacturing environment. Users whose role involves any of the following should attend this training. Material planning Capacity planning Supply chain planning Manufacturing execution Oracle Applications support List of attendees Name Org Role Date Trained Date Certified Related training materials Inventory management and material transaction in discrete manufacturing is discussed in Inventory Training Manual Product manufacturing process is covered in Routing Training Manual Product structure is covered in BOM Training Manual For discrete jobs, please refer to WIP Training Manual For sourcing and supplier constraint setups, please refer to Purchasing Training Manual Log onto Oracle Applications 1. Enter URL of Oracle Applications home page to your browser: http:// 2. Enter in your user ID and password 5 MSAT Internal Page 7
6. 6. 3. Choose Advanced Supply Chain Planner responsibility (you may have a customized responsibility with a different name assigned to you. Check with your instructor about which responsibility you should use) Overview of Oracle Advanced Planning APS data flow The diagram below illustrates major information flows between the components of the Oracle Advanced Planning and the rest of Oracle Applications. 6 MSAT Internal Page 7
7. 7. Planning cycle The general process that occurs during a planning cycle is shown in the figure below. The flow demonstrates the key features of Oracle ASCP that a typical planner would use in the course of her/his work. Source Data Setups Setup inventory item attributes There are several item attributes especially important to planning. Set them up properly to ensure desired planning results. For item setup in general, please refer to Inventory Training Manual. Navigation path: Inventory>Items>Master Items>General Planning (T) 7 MSAT Internal Page 7
8. 8. Or Inventory>Items>Organization Items>General Planning (T) Refer to the table below for the setup of each attribute. Attribute Valid values Purpose Comment Setup Make or Buy Make, Buy Determine whether the item is manufactured internally or purchased You cannot change this value if open orders exist for the item. Planner Planner Id Assign material planner to plan this item If an item is vendor managed, you must enter a planner for the item. Inventory Planning Method Not Planned, Min-Max, Reorder Point Assign planning method to the item Min-Max: define a minimum quantity on hand. Reorder when this quantity is reached. Also define a maximum onhand quantity that you do not want to exceed. Reorder point: reorder point is calculated based on the planning information you define for this item. Min-Max Minimum Quantity Enter the quantity minimum for minmax planning. If an item is minmax planned, the Min Max Planning Report suggests a new order when quantity drops to the min max minimum. Min-Max Maximum Quantity Enter the quantity maximum for minmax planning. If an item is minmax planned, the Min Max Planning Report suggests an order that brings onhand up to the minmax maximum. 8 MSAT Internal Page 7
9. 9. Attribute Valid values Purpose Comment Setup Order Quantity Minimum Enter the minimum order quantity or repetitive rate. Use this to define an order quantity below which it is unprofitable to build or purchase the item. Planning uses this to modify planned order quantities or repetitive daily rates. For discrete items, when net requirements fall short of the minimum order quantity, planning suggests the minimum order quantity. Order Quantity Maximum Enter the maximum order quantity or repetitive rate of the item. Planning uses this to modify the size of planned order quantities or repetitive daily rates. For discrete items, when net requirements exceed the maximum order quantity, planning suggests the maximum order quantity. Cost Order Enter the fixed cost associated with placing an order of any quantity. Cost Carrying % Enter the percentage used to calculate the annual carrying cost. This is the percentage of the unit cost that represents internal cost to stock one unit for one year. Source Type Inventory , Supplier, Sub Inventory Assign replenishment source type Inventory: Fill requests by creating internal requisitions that become internal sales orders, pulling stock from existing inventory. Supplier: Fill requests by creating purchase requisitions that become purchase orders, procuring the item from a supplier. Subinventory: Fill requests by creating move order requisitions that become move orders, pulling stock from an existing sub inventory. If you are using Supplier Scheduling, it is generally recommended that this field be left blank. Otherwise, it could override your sourcing rules. Source Organization Optionally enter the organization from which an internal requisition draws the item. This applies only when Inventory is the replenishment source type. 9 MSAT Internal Page 7
10. 10. Attribute Valid values Purpose Comment Setup Source Subinventor y Enter the sub inventory within the source organization from which an internal requisition draws the item. This applies only when Inventory or Subinventory is the replenishment source, and only when you specify a source organization. Safety Stock Method Select an option to plan use of fixed or dynamically calculated safety stock quantities. Used to direct safety stock calculation method when Oracle Inventory Optimization is NOT activated. For MRP/MPS planned items, you must set the Inventory Planning Method attribute to Not planned, then choose the MRP planned percent option here. Safety Stock Bucket Days Enter the number of days to dynamically calculate safety stock quantities. The planning process multiplies the Safety Stock Percent by the average gross requirements and divides by the number of days you enter here. Used by planning modules only. Safety Stock Percent Enter the percent to dynamically calculate safety stock quantities for the item. The planning multiplies this percent by the average gross requirements and divides by the Safety Stock Bucket Days. The planning process uses this attribute when you set Safety Stock to MRP planned percent. Used by planning modules only. Fixed Order Quantity Enter the quantity used to modify the size of planned order quantities or repetitive daily rates. When net requirements fall short of the fixed order quantity, the planning suggests the fixed order quantity. When net requirements exceed the fixed order quantity, the planning suggests multiple orders with the fixed order quantity. For discrete items, use this attribute to define a fixed production or purchasing quantity. Used by planning modules only. Fixed Days Supply Enter the number of days used to modify the size and timing of planned order quantities. The planning suggests planned order quantities that cover net requirements for the period defined by this value. The planning suggests one planned order for each period. Used by planning modules only. Fixed Lot Multiplier Enter the fixed lot multiple quantity or repetitive rate (units per day). Planning uses this to modify the size of planned order quantities or repetitive daily rates. When net requirements fall short of the fixed lot size multiplier quantity, planning suggests a single order for the fixed lot size multiplier quantity. When net requirements exceed the fixed lot size multiplier quantity, planning suggests a single order that is a multiple of the fixed lot size multiplier. 10 MSAT Internal Page 7
11. 11. MPS/MRP planning attributes Navigation path: Inventory>Items>Master Items>General Planning (T) Refer to the table below for the setup of each attribute. 11 MSAT Internal Page 7
12. 12. Attribute Valid values Purpose Comment Setup Planning Method Not Planned, MRP planning, MPS planning, MRP/DRP Planned, MPS/DRP Planned, DRP Planned Select the option that Planning uses to decide when to plan the item Not Planned: The item does not require longterm planning of material requirements. Choose this option for high volume and/or low cost items that do not warrant the administrative overhead of planning; typically dependent demand items. You cannot use this option unless the Pick Components attribute is checked. MRP planning: Choose this option for noncritical items that do not require manual planning control, typically dependent demand items. MPS planning: You master schedule the item and require manual planning control. Choose this option for items with independent demand, items that are critical to your business, or items that control critical resources. MRP/DRP Planned: Choose this option when you want both MRP and DRP planning for the item. MPS/DRP Planned: Choose this option when you want both MRP and DRP planning for the item. DRP Planned: Choose this option when you have multiple organizations for which you do Distribution Requirements Planning for the item. Forecast Control Consume, Consume and derive, None Select an option to determine the types of demand you place for the item. This guides the key processes of twolevel master scheduling: forecast explosion, forecast consumption, planning, production relief, and shipment relief. This is appropriate only for items that are models, option classes, options, or mandatory components of models and option classes. Consume: forecast demand directly, rather than by exploding forecast demand. Consume and derive: forecast demand directly, explode forecast demand, or use a combination of both methods. None: place sales order demand but do not forecast demand. 12 MSAT Internal Page 7
13. 13. Attribute Valid values Purpose Comment Setup Exception Set Enter the name of the planning exception set that groups together the sensitivity controls and exception time periods for item level planning exceptions for the item. The itemlevel planning exceptions include: overcommitted, shortage, excess, and repetitive variance. The planning process uses this attribute to decide when to raise planning exceptions for the item. Create Supply Indicates if supply can be suggested for this item. Critical Component If selected, flags the item as a critical component for MPS and DRP planning. This allows you to plan master scheduled items with respect to only critical component and their material resource constraints. Pegging Soft Pegging, End Assembly Pegging, End Assembly/ Soft Pegging, Hard Pegging, End Assembly/ Hard Pegging, None Enter the pegging option. Soft Pegging: allocates supply to demand based on the Reservation Level option set in the Plan options. End Assembly Pegging: traces the 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. End Assembly/ Soft Pegging: Choose this option for both soft pegging and end assembly pegging. Hard Pegging: allocates supply to demand based on the Reservation Level option set in the Plan options. This pegs supply to demand and demand to supply by project at all levels of a bill of material. This allows you to pre allocate supply to demand and generate planned orders based on the plan level options. End Assembly/ Hard Pegging: Choose this option for both hard pegging and end assembly pegging. None: disables project material allocation, end assembly pegging, and full pegging. Planned Inventory Point Indicates if the item is an Inventory Point item. This means that material can be stored at the item level without losing materials or quality characteristics. Inventory Points generally point to major stocking phases in the manufacturing cycle. 13 MSAT Internal Page 7
14. 14. Attribute Valid values Purpose Comment Setup Shrinkage Rate Enter a factor that represents the average amount of material expected to lose during manufacturing or in storage. The planning process inflates demand to compensate for this expected loss. Round Order Quantities 1 Indicate whether the planning process uses decimal or whole number values when calculating planned order quantities or repetitive rates. When this option is checked, decimal values round up (never down) to the next whole number. The planning process carries any excess quantities and rates forward into subsequent periods as additional supply. Acceptable Early Days 2 Enter the number of days before which the planning process will not reschedule orders. The planning process only suggests rescheduling out if the new calculated order date is later than the original order due date plus the acceptable early days; the new calculated order does not violate the order of current scheduled receipts. This applies to discrete items only. Calculate ATP 3 Indicate whether to calculate and print available to promise (ATP) on the Planning Detail Report. On the Planning Detail Report, ATP is calculated as ATP = Planned production committed demand Reduce MPS 4 None, Past Due, Demand Time Fence, Planning time Fence Decide when to reduce master production schedule (MPS) quantities to zero. None: Do not reduce order quantities on the MPS. Past Due: Reduce order quantities on MPS entries to zero when the entry is past due. Demand Time Fence: Reduce order quantities on MPS entries to zero when the due date moves inside the demand time fence. Planning time Fence: Reduce order quantities on MPS entries to zero when the due date moves inside the planning time fence. 14 MSAT Internal Page 7
15. 15. Attribute Valid values Purpose Comment Setup Planning Time Fence Days 5 Cumulative mfg. lead time, Cumulative total lead time, Total lead time, User defined Determine a point in time inside which certain restrictions on planning recommendations apply. Planning calculates the planning time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value entered here. Cumulative mfg. lead time: The cumulative manufacturing lead time for the item. Cumulative total lead time: The total manufacturing lead time for the item. Total lead time: The total lead time for the item. Userdefined: The value you enter for Planning Time Fence Days. Demand Time Fence Days Cumulative mfg. lead time, Cumulative total lead time, Total lead time, User defined Determine a point in time inside which the planning process ignores forecast demand and considers only sales order demand when calculating gross requirements. Used to reduce the risk of carrying excess inventory. Planning also uses the demand time fence when loading master schedules. The demand time fence is calculated as the start date of the master schedule load plus the value entered. Calculate the demand time fence as the plan date (or the next workday if the plan is generated on a non workday) plus: Cumulative mfg. lead time: The cumulative manufacturing lead time for the item. Cumulative total lead time: The total manufacturing lead time for the item. Total lead time: The total lead time for the item. Userdefined: The value you enter for Planning Time Fence Days. 15 MSAT Internal Page 7
16. 16. Attribute Valid values Purpose Comment Setup Release Time Fence Days 6 Cumulative mfg. lead time, Cumulative total lead time, Total lead time, User defined, Do not auto release, Do not release (Kanban) Determine a point in time inside which planned orders for discretely planned items are automatically released as WIP jobs or purchase requisitions. No material availability check is performed before WIP jobs are released. Calculate the release time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value entered here. Cumulative mfg. lead time: The cumulative manufacturing lead time for the item. Cumulative total lead time: The total manufacturing lead time for the item. Total lead time: The total lead time for the item. Userdefined: The value you enter for Planning Time Fence Days. Do not autorelease: The item cannot be autoreleased. Do not release (Kanban): For Kanban items prevent release of planned orders manually or automatically. Substitution Window Cumulative mfg. lead time Cumulative total lead time Total lead time User-defined Calculates until what time a substitute can be considered for an item. Cumulative mfg. lead time: The cumulative manufacturing lead time for the item. Cumulative total lead time: The total manufacturing lead time for the item. Total lead time: The total lead time for the item. User-defined: The value you enter. Note: 1. In ASCP, this flag is not only used to round planned order quantity, but also used to schedule resource utilization for assembly. For assembly, when Round Order Quantity is checked, it means one resource unit can only work on one unit of the assembly item. For instance, Work order quantity: 8 Assigned resource units: 3 Resource usage: 1 hour/unit item Job duration: 3 hours (Round Order Quantity checked) 2 and 2/3 hours (Round Order Quantity unchecked) 2. Set this attribute to reduce plan nervousness and eliminate minor reschedule recommendations, especially when it is cheaper to build and carry excess inventory for a short time than it is to reschedule an order. 3. ATP calculated by the planning process is not related to ATP information calculated and maintained by Oracle Inventory. As such, planning ATP does not consider ATP rules from the Available to Promise Rule window, and is not related to the ATP information displayed in the View Item Available to Promise Information window in Oracle Inventory module. 4. If Oracle Work in Process and Oracle Purchasing are installed, you get automatic production relief when you create a discrete job, purchase requisition, or purchase 16 MSAT Internal Page 7
17. 17. order. In this case, you would typically set this attribute to None. If you do not have automatic production relief, you may select one of the options to reduce MPS quantities and avoid overstating your supply. 5. This feature reduces short-term fluctuations in the plan output. The planning time fence (PTF) helps Oracle ASCP generate a stable supply chain plan for manufacturing shops and helps companies to honor contractual commitments with external suppliers. PTF is a time parameter associated with an organization-item. ASCP functionality associated with PTF can be summarized as follows: Oracle ASCP does not create any new planned orders with start dates within PTF. Oracle ASCP does not Reschedule In any orders into the PTF. Orders within PTF are Rescheduled Out based on a profile option setting. Oracle ASCP does not suggest any changes for firm orders and orders pegged to firm orders. Excess and Shortage exceptions are generated within the time fence. If you select the Enforce Demand Due Dates option, Oracle ASCP may violate the PTF. 6. The planned orders must meet the following autorelease criteria: The new due date lies within the autorelease time fence The lead time is not compressed The orders are for standard items (will not release models, option classes, and planning items) The orders are not for Kanban items The orders are for DRP planned items in a DRP plan, MPS planned items in an MPS plan, or MRP planned items in an MRP plan The release time fence option is defined as anything other than Do not auto release, Do not release (Kanban), or null DRP, MPS, and MRP plans must be run with the Memorybased Planning Engine Lead times attributes Navigation path: Inventory>Items>Master Items>General Planning (T) 17 MSAT Internal Page 7
18. 18. Refer to the table below for the setup of each attribute. Attribute Purpose Comment Setup Preprocessing Enter the days you must add to purchasing or manufacturing lead time to place an order. Processing Enter the days required to procure or manufacture an item. For manufactured assemblies, processing days equals manufacturing lead time. Postprocessing Enter the days required to receive a purchased item into inventory from the initial supplier receipt. Cannot enter a value if the Make or Buy attribute is set to Make. Fixed Enter the days required to make an assembly independent of order quantity, such as setup or teardown time. Variable Enter the time to produce one additional unit of an assembly. Total lead time is variable lead time multiplied by order quantity, plus fixed lead time. Cumulative Manufacturing Enter the manufacturing lead time of an assembly (in days) plus the largest adjusted cumulative manufacturing lead time of its components. Purchased items have no cumulative manufacturing lead time. This attribute can be calculated and updated by rolling up cumulative lead times with Oracle Bills of Material. Cumulative Total Enter the total lead time of the assembly plus the largest adjusted cumulative total lead time of its components This attribute can be calculated and updated by rolling up cumulative lead times with Oracle Bills of Material. Lead Time Lot Size Enter the quantity used to compute processing lead time (as well as fixed and variable lead times). The default value is the items standard lot size or, if a standard lot size is not defined, the default is 1. Shipping, Receiving, Carrier, and Supplier Capacity Calendars Oracle ASCP plans supply chain activities according to various calendars. Manufacturing, supplier, and customer facilities may be able to make, ship or receive goods only on specific days. Oracle ASCP plans each type of supply or demand considering the working and non working days in the appropriate set of calendars. It considers the following calendars while planning and scheduling: Organization-Supplier shipping calendar Organization-Customer receiving calendar Carrier calendar Supplier capacity calendar Manufacturing Calendar Shipping Calendar The shipping calendar indicates the valid working days for shipment activities originating from suppliers and organizations. The planning engine does not recommend a shipment out from those facilities if the date is a non-working day. The planning engine adjusts the shipment date if the current shipment date is a non- 18 MSAT Internal Page 7
19. 19. working day. The planning engine considers the working days and times when generating recommended transfers as part of the planning process. The planning engine uses processing lead time to calculate the dock date during the planning and scheduling process. Then it uses shipping calendars to calculate valid ship date (dock date - intransit lead time) after the planning and scheduling process completes. Receiving Calendar The receiving calendar governs the receiving activities at the organizations or customer sites that receive goods. The planning engine allows organizations to receive shipments only on a working day. If the current shipment arrival date is a non- working day according to the receiving calendar, the planning engine defers the receipt of the shipment until the next (or previous) working day. When generating planned transfers between these two facilities, the planning engine assigns dock dates on these planned transfers based on the receiving calendar of the organization. Receiving calendars can also vary by combination of carrier and service level. You need to specify valid receiving calendars for organizations and customers at the carrier and service levels. Carrier Calendar The carrier calendar indicates the working and non-working days and times for material that is intransit using different means of transport. For example, certain methods of shipment such as parcel carriers may not work on weekends. This may cause the transit time to be stretched over the weekends. The planning engine needs to consider these non-working times of various transportation modes that are modeled in the supply chain. The carrier calendar indicates the operating calendar of the carrier or the service. It does not indicate the pickup or delivery dates of the carrier. Supplier Capacity Calendar The supplier capacity calendar governs how supplier capacity is accumulated over a period of time. Supplier capacity is only accumulated on the working days according to the supplier capacity calendar. The supplier capacity calendar also governs how the supplier processing lead time is calculated. Workday Calendar Please refer to Routing Training Manual for workday calendar setups. Setup resource and department Please refer to Routing Training Manual for resource and department setups. Setup routing 19 MSAT Internal Page 7
20. 20. Please refer to Routing Training Manual for routing setups. Setup supply chain For more information on supplier base setups, please refer to the Purchasing Training Manual. Approved Supplier List Approved supplier list is a controlled repository of information that links items and commodities to suppliers and supplier sites that provide them to a specific ship-to organization or to the entire enterprise. Navigation path: Purchasing>Supply Base>Approved Supplier List Refer to the table below for the setup of attributes relevant to planning. Attribute Valid values Comment Setup Status Approved, Debarred, New ASCP only consider Approved and not Disabled suppliers Disabled Global? Yes, No ASCP only plans PO for suppliers with Global = Yes Supplier planning constraints Enhance sourcing provides the ability to model flexible supplier capacity. Navigation path: Purchasing>Supply Base>Approved Supplier List>Attributes (B)> Planning Constraints (T) 20 MSAT Internal Page 7
21. 21. Refer to the table below for the setup of attributes relevant to planning. Attribute Comment Setup Processing Lead Time This supplier-item attribute overrides the organization item attribute for processing lead time Supplier Capacity Calendar 1 Planning adjusts planned order release date so that deliveries occur on the valid delivery date that coincides with the due date or the closest valid delivery date that occurs prior to the due date. This calendar is independent of your workday calendar. Order Modifiers These supplier-item attributes override the organization item attributes for order modifiers. Capacity This supplier-item attribute represents supplier item daily capacity in the purchasing UOM. Tolerance Fence 2 Use the Tolerance% and Days Advance Notice attributes together to state by what percentage a supplier can change capacity if given a number of days advance notice. Note: 1. If no calendar is defined and assigned to the supplier-item, planning will assume all days are acceptable for receiving. 2. You can make multiple entries to represent the percentage change in capacity allowed with different days of advance notices. Delivery calendar Set up delivery calendar the same way as setting up workday calendar. Refer to Routing Training Manual on how to setup calendars. The delivery calendar is used to establish valid delivery days by supplier, item, and organization. ASCP will offset planned purchase order release dates by the number of days in Processing Lead Time plus the number of days necessary to cause the delivery to your dock to occur on a valid delivery day. 21 MSAT Internal Page 7
22. 22. If no delivery calendar is defined and assigned to the supplier-item, planning will assume all days are acceptable for receiving. Shipping methods Navigation path: Inventory>Setup>Organization>Shipping Methods This form is used to set up a valid list of values for shipping method field. Inter-organizations shipping networks Shipping networks define transportation links form on organization to other organizations. If traffic flows in both directions, from organization A to organization B, and from organization B to organization A, you need to define one entry for each direction. ASCP uses transportation capacity entered on the Shipping Networks form for each inter-organization link as transportation constraint. Navigation path: Inventory>Setup>Organization>Shipping Networks 22 MSAT Internal Page 7
23. 23. Assign shipping methods to shipping network: Navigation path: Inventory>Setup>Organization>Shipping Networks>Tools (M) >Shipping Methods Use this window to enter transportation capacity, too. Inter-location shipping networks Use the Inter-Location Transit Times form to model shipping networks and capacities between supplier locations and inventory organizations, and between inventory organizations and customer locations. You can also designate a particular shipping method as default method in a shipping network. Navigation path: Inventory>Setup>Organization>Inter-Location Transit Times Note: this form is used to model transportation time and capacities between external sites and inventory organizations. If you use the Inter-Location Transit Times form to enter transit times and transportation capacities between inventory organizations in your enterprise, ASCP will ignore that information. 23 MSAT Internal Page 7
24. 24. Sourcing rules Supply chain complexity is modeled by sourcing rules, bills of distribution, and assignment sets. Taken together, these forms specify how material is supplied, manufactured, and transferred across the supply chain. But they will not model where the materials will be sent. In this sense, bill of distribution is a misnomer. When the sourcing rules and bills of distribution are created, items are not specified anywhere on the definition forms. These are only descriptions of the means HOW items are replenished. The defined sourcing rules and bills of distribution can later be assigned to any items or group of items. Assignment sets are used to associate items with sourcing rules and bills of distribution. Note: Sourcing rules and BODs can be defined at the source instances or at the APS instance, or at both places. The Assignment Set of a specific plan will govern which rules are used by that plan. However, sourcing rules and bills of distribution that cross instances must be set up on the APS instance. Navigation path: Supply Chain Planner>Sourcing>Sourcing Rules Refer to the table below for the setup of attributes relevant to planning. Attribute Valid values Comment Setup Type Transfer From, Make At, Buy From Transfer From: Transfer between internal organizations, enter source organization in the Org column. When it is selected, Supplier and Supplier Site are disabled. Make At: Make at an internal organization, enter manufacturing organization in the Org column. When it is selected, Supplier and Supplier Site are disabled. Buy From: Purchase from an external enterprise, enter Supplier and Supplier Site. When it is selected, the Org column is disabled. Allocation% 1 The total allocation percentage for all sources within a rank must add up to exactly 100. Planned order is split among the sources according to their allocation percentages. 24 MSAT Internal Page 7
25. 25. Attribute Valid values Comment Setup Rank 1 The sources with the highest rank (lowest number) have the highest priority in allocations. When sources of the highest rank have no more capacity, allocation goes to sources in the next highest rank, and so on. Planning Active Checked, unchecked You cannot apply sourcing rules and bills of distribution (make them Planning Active) until the sum of the allocation percentages equals 100. All Orgs Checked, unchecked Checked: This sourcing rule can apply to all organizations. Org Checked, unchecked Checked: This sourcing rule can apply to one organization. Note: 1 in constraint based planning; sources with the highest rank have the highest priority. In optimized planning, sources with the lowest penalty adjusted cost have the highest priority in allocation. Timephasing in a sourcing rule determines when each group of shipping method ship org combinations is in effect. Assignment sets Once you have defined your sourcing rules, you must assign them to particular items and/or organizations to make them functional. These assignments are grouped together in assignment sets. This is where various sourcing strategies define a particular supply chain network. Each assignment set represents a selection of organizations and/or items you want planned. To influence the planning process, you must include an assignment set in your plan options. In an assignment set, you can assign your sourcing rules at different levels, as follows: Item-Instance-Organization Category-Instance-Organization Category-Instance Item-Instance Instance-Organization Instance These levels allow you to assign a replenishment rule to as many or as few items as possible. For example, a category of items could be defined as packaging material, and a sourcing rule that identifies the suppliers could be assigned to this category. The planning uses a sourcing assignment hierarchy to determine the actual source of a specific item. In the preceding list of assignment levels, the levels are listed from specific to general. Specific sourcing assignment overrides general assignment, i.e., rows above override rows below. For instance, Item-Organization overrides Item. Navigation path: Supply Chain Planner>Sourcing>Assign Sourcing Rule/BOD 25 MSAT Internal Page 7
26. 26. 1. Enter an assignment set name and description. 2. Select an Assigned To type See: Assignment Hierarchy 3. Enter an organization name, if the Assigned To type requires one. 4. Enter the name of the customer to which you want to assign a sourcing rule or bill of distribution. 5. Enter the specific site to which you want to assign a sourcing rule or bill of distribution. 6. Enter an Item/Category if you selected Item or Item-Org as the Assign To type. 7. Enter the sourcing rule or bill of distribution as the Type. 8. Enter the name of the sourcing rule or bill of distribution Note: 1 not every item in a bill of material needs to be listed in an assignment set. Items that are made and consumed at same organization need not to be assigned to an assignment set. Assignment Hierarchy The assignment hierarchy of sourcing rules and bills distribution is listed in the following table, rows below override rows above them. Columns on the right override columns on the left. 26 MSAT Internal Page 7
27. 27. Note: A global sourcing rule has an unspecified receiving organization. Bills of distribution are global. Since not all assignment types are valid for both sourcing rules and bills of distribution, the effect of the Sourcing Rules vs. Bill of Distribution Assignments table is illustrated in a linear hierarchy in the following table. The rows below override rows above them. Note: use assignment set hierarchy to simplify the modeling and maintaining sourcing relationships. For example, when a plant buys all items belonging to a category such as fasteners from Supplier A, create a sourcing rule and assign it to this item category. At a later day, you decide to source one of the fasteners from Supplier B. You then 27 MSAT Internal Page 7
28. 28. create another rule to source from Supplier B and assign this rule to that specific fastener. The detail-to-general hierarchy directs the specific fastener to be sourced from Supplier B, while all other fasteners still from Supplier A. Create the minimum number of sourcing rules and keep the assignment sets as simple as possible. Rather than create and assign a rule to each item, you can assign a default rule to an organization, another default rule to a category. Assign a rule to an individual item/organization only to deal with exceptions. Order management Most modules in Oracle Manufacturing do not interact directly with Oracle Order Management. These modules use sales order information through the supply/demand portion of Oracle Inventory. In Oracle Applications 11i, sales orders are visible to the supply/demand portion of Oracle Inventory only after they are scheduled. Use the Schedule Order process to create sales order information in Inventory. The scheduled sales orders will become demand in supply chain planning. Data Collection Scope of data collection Oracle ASCP uses data maintained in the source (transactional) ERP modules. Data collection programs capture a snapshot of the source data, and copy that snapshot to the planning instance. The planning engine then performs multi-organization planning and scheduling calculations. The results of the planning process, such as planned orders, are published back to the transaction ERP modules for execution. The table below summarizes the data collected into planning instance from the source instances. Source Module Data to be Collected Order Management Sales order demands, Customers, Price lists Purchasing Approved supplier list, Supplier capacity, Scheduled PO receipts Inventory Operating units, Sub inventories, Organizations, Planners, Buyers, Product families, Items, On hand quantities Bills of material Bills of material, Resources, Routings, Operations, Workday calendars Work in Process Scheduled work orders, Material transactions, Resource transactions Cost Standard costs MRP/Supply Chain Planning Forecasts, Master demand schedules, Sourcing rules/Bills if distributions, Assignment sets, Delivery schedules Note: If Oracle Demand Planning is installed and integrated with ASCP, its output is directly visible to ASCP as planning inputs. Data collection methods Collecting data can take a significant amount of time compared to the time for the overall planning cycle. Choose the collection method best suit for you needs. There are three collection methods: 28 MSAT Internal Page 7
29. 29. The Complete Refresh method clears all transaction data for all business entities from the planning server (for the source instance being collected), and then copies over information about the user-selected entities. This method can be time consuming. The Net Change Refresh method copies only incremental changes to business entities to the planning server (and is thus faster), but is supported mainly for demand and supply business entities. The Targeted Refresh method clears transaction data for only the user- selected business entities from the planning server, and then copies the entity information over from the transaction instance. Information about non-selected entities remains intact on the planning server. All planning business entities are supported by Targeted Refresh collections. Continuous collections process: The continuous collections process is an automated process of data collection that efficiently synchronizes the data on the planning server by looking up the sources. If you opt for continuous collections, the system automatically determines the type of collection that needs to be run on entities selected by you. The continuous collections process collects data from the sources with the least user intervention. The Continuous Collections concurrent program performs continuous collections. Continuous collections is not covered in this training. Use Complete Refresh the first time you perform collections from a source instance to the planning server. You may also wish to use complete refresh collections after a significant proportion of the setup data in your transaction system has been altered, and you would like to make a fresh copy of all source instance business entities (items, bills of material, sourcing rules, resources, and so on) on the planning server. You typically collect all business entities in a Complete Refresh Collection. Use Complete Refresh only when it is necessary. Use Net Change Refresh if you would like to update the supply and demand picture on the planning server as quickly as possible, and the incremental changes to supply and demand in the source instance since the last collection have not been extensive relative to the existing (already collected) body of supply and demand information. In this case, Net Change Refresh is the fastest way to achieve the desired update of the planning server operational data store, because it copies over from the source instance only the incremental changes in supply and demand since the last collection. Use Targeted Refresh if you would like to update the planning server information for some (but not all) business entities, and some of these entities fall outside the category of supply and demand entities supported by Net Change Refresh. For example, to update the planning server with a newly rebuilt manufacturing calendar, you would run Targeted Refresh collections for just the calendar business entity. Data on the planning server about all other business entities would remain unaffected by this collection. Also use Targeted Refresh (in lieu of Net Change Refresh) to bring over the latest picture of supply and demand to the planning server in cases when the incremental changes to supply and demand on the source instance since the last collection are very extensive. In this case, the update mechanism employed by Targeted Refresh collections (wholesale deletion followed by rebuilding of data on the planning server) is faster than the mechanism employed by Net Change Refresh collections (incremental insertions into existing data on the planning server). 29 MSAT Internal Page 7
30. 30. Run data collection Navigation path: Advanced Supply Chain Planner>Collections>Oracle Systems> Standard Collection 1. Tab to the Parameters field, Planning Data Pull Parameters form appears 30 MSAT Internal Page 7
31. 31. 2. Select individual parameter as explained in the table below, then click on OK Parameter Values Instance Source instance code from list of values. Collection Group You can decide to collect data from All enabled organizations or only form the current organization Number of Workers 1 One or greater. Increase this number to increase the number of computational resources devoted to the Planning Data Pull process. This allows you to specify the number of workers for the Data Pull, which can now be different from the number of workers specified for the ODS load process. Timeout (Minutes) 1 The maximum amount of time you would like to allocate to the Planning Data Pull process. If the Planning Data Pull process has not completed within this amount of time, it will be terminated with an error. Purge Previously Collected Data Yes (default) or No. Setting this to Yes wipes out all data in the APS planning server operational data store associated with the selected source instance as the first step in the collections process. If you set this to Yes, the only allowable collection method is Complete Refresh. If you set this to No, the allowable collection methods are Targeted Refresh and Net Change. Collection Method 2 Complete Refresh/Targeted Refresh/Net Change Refresh. See the explanation in the Data collection methods section of this manual 31 MSAT Internal Page 7
32. 32. Parameter Values Analyze Staging Tables Yes or No (default). Set this to Yes periodically to re-compute database access statistics on the APS staging tables. This speeds up the subsequent Planning ODS Load process. Business objects The remaining parameters in the Planning Data Pull Parameters are a list of business objects. Selecting Yes for an entity means collecting the information for that entity over from the source instance. Selecting No for an entity means collecting no information for that entity over from the source instance. This is useful when you know there are only changes on limited objects. Note: 1. Consult with your system administrator and DBA on the values of these parameters, for they affect the performance of the data collection process. 2. Collecting information for Resource Availability and Sourcing History takes a significant amount of time. Collect this information only when really necessary. 3. Open the Parameters form for Planning ODS Load 4. Select individual parameter as explained in the table below, then click on OK Parameter Values Instance Source instance code from list of values. Timeout (Minutes) 1 The maximum amount of time you would like to allocate to the Planning Data Pull process. If the Planning Data Pull process has not completed within this amount of time, it will be terminated with an error. Number of Workers 1 One or greater. Increase this number to increase the number of computational resources devoted to the Planning Data Pull process. This allows you to specify the number of workers for the Data Pull, which can now be different from the number of workers specified for the ODS load process. Recalculate Resource Availability This defaults to the value (Yes or No) that you set for the Resources Availability business entity in the Planning Data Pull Parameters window. The value that you set here is the one that actually determines whether resources availability is collected or not. 32 MSAT Internal Page 7
33. 33. Parameter Values Recalculate Sourcing History This defaults to the value (Yes or No) that you set for the Sourcing History business entity in the Planning Data Pull Parameters window. The value that you set here is the one that actually determines whether sourcing history is collected or not. If you select Yes, then ASCP will collect all new sourcing history not already on the planning server in the time range [(today - x months) through (today)] from the source transaction system. The number x is given by the value that you set for the profile option MSC: Sourcing History Start Date Offset (in months). During planning, ASCP will use the total cumulative sourcing history on the planning server in addition to the planned sourcing in the plan to determine whether sourcing percentages in sourcing rules are being respected or not. Purge Sourcing History Valid values are Yes and No (default). If you select Yes, then all sourcing history present on the planning server will be deleted before the collection process commences. Note: 1. Consult with your system administrator and DBA on the values of these parameters, for they affect the performance of the data collection process. 5. Submit the data collection request set Define an ASCP plan ASCP plan classes Oracle ASCP offers the following plan classes. Unconstrained Resource Constrained Material Constrained Material and Resource Constrained Optimized These classes are discusses in the table below. Plan Class Planning Horizon Goals Scenario Unconstrained Long Term Future How much resource capacity and material availability do I need to arrange in order to satisfy all anticipated demand in a timely manner? Decisions can be made on Resource acquisition/disposition and supplier sourcing to address the exceptions. Resource Constrained Long Term Future How much material availability do I need to arrange in order to satisfy all anticipated demand in a timely manner? Difficult to change resource capacity, but increased outsourcing is an option. Decisions can be made on supplier sourcing to address the exceptions. Material Constrained Long Term Future How much resource capacity do I need to arrange in order to satisfy all anticipated demand in a timely manner? Difficult to change material availability but internal resource acquisition/disposition is an option. Decisions can be made on Resource acquisition/disposition to address the exceptions. 33 MSAT Internal Page 7
34. 34. Plan Class Planning Horizon Goals Scenario Material and Resource Constrained Near Term Future Generate a feasible plan that respects material, resource, distribution, and transportation constraints. Impossible to overcome material and resource constraints and therefore must respect them in order to generate a feasible supply chain plan. Optimized Near Term Future Generate an optimized and executable plan based on plan objectives and material, resource, and transportation constraints. Impossible to overcome material and resource constraints and therefore must respect them in order to generate a feasible supply chain plan. Note: Oracle ASCP lets you prioritize how you enforce Capacity Constraints or Demand Due Dates. Whichever constraint takes precedence over the other is the hard constraint; and the other is the soft constraint. You must choose one and only one type of constraint. If you choose to enforce Demand Due Dates (setting Demand Due Dates as a hard constraint), then primary resources are used and loaded to capacity to satisfy demand due dates. The system also evaluates alternate resources if additional capacity is required. If there is insufficient capacity to meet demand due dates, the primary resource is overloaded. The choice of whether to use an alternate resource or overload capacity depends on cost considerations if optimization is selected. Oracle ASCP returns exception messages if capacity is overloaded. If you choose to enforce Capacity Constraints (setting Capacity Constraints as a hard constraint), then resources are loaded to their limit to satisfy demand (if required). Unsatisfied demand is pushed into the future. In this case, Oracle ASCP returns late replenishment exception messages. ASCP plan types There three types of ASCP plans. Production Plan, equivalent to traditional MPS (master production plan) Manufacturing Plan, equivalent to traditional MRP (Materila requirement plan) Master Plan MPP (Master Production scheduler) Each creates time-phased planned orders that satisfy independent and dependent demand while seeking to respect material and resource constraints. These three types of plans need to be used in conjunction with the MPS/MRP Planning Type item attribute that is set for each item. Possible values for this attribute are: MRP Planning MPS Planning MRP/MPP Planned MPS/MPP Planned MPP Planned 34 MSAT Internal Page 7
35. 35. Each ASCP plan type will include a subset of items in its planning process. The items included depend upon the plan type and the items the MRP Planning Type attribute. Define a plan name Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names 1. Enter a unique plan name. 2. Enter Description for the plan. 3. Check ATP if this plan is used for global order promising. 4. Check Production if it is a production plan. In a production plan, planned orders can be automatically released within their release time fence. 5. Check Notifications. If this is checked, exception message notifications workflow for the plan is enabled. 6. Select a Plan Type. Valid values are Manufacturing Plan, Production Plan, and Master Plan. This setting interacts with the MPS/MRP Planning method item attribute to determine which subset of the items that pass the condition imposed by the Planned Items parameter are planned. 7. If you want to make this plan not visible as input into other plans, or want to purge the plan enter an Inactive Date. Set plan options Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names >Plan Options (B) 35 MSAT Internal Page 7
36. 36. Main tab Use the information in the following table to specify parameters on the Main tab. Parameter Description Comment Setup Assignment Set The assignment set that holds the sourcing rules and bills of distribution that define the rules for material flow within your supply chain. Demand Priority Rule When ASCP does detailed scheduling, it schedules demands one by one. The rule specified here dictates the order in which demands will be considered during detailed scheduling, and thus which demands will get the first opportunities to take up available materials and resource capacities. Overwrite1 Overwrite planned orders. Append Planned Orders1 Appends new planned orders to current plan. Planned Items2 This parameter and the next one, Planning Method, control the items that are planned in the supply chain plan. An item must satisfy conditions imposed by both parameters before being included in the supply chain plan. Material Scheduling Method Choose from Operation Start Date or Order Start Date scheduling methods. If you choose Operation Start Date, material is scheduled to arrive at the start of the operation for which it is required. If you choose Order Start Date, material is scheduled to arrive at the start of the order for which it is required. Order State Date is usually an earlier date than the Operation Start Date and therefore this selection represents the more conservative planning logic of the two options. 36 MSAT Internal Page 7
37. 37. Parameter Description Comment Setup End Item Substitution Set If Decision Rules tabbed region > Use End Item Substitutions selected, select a substitution set. These are defined in the Planning Details - Substitute window discussed. You can use a set of substitution relationships to be effective for a given plan by selecting the substitution set as an option for the plan. This allows you to run simulations of possible substitutions and evaluate performance indicators given possible future substitutions. Schedule By Set this option to instruct the planning engine to: Plan supplies based on sales order line request, promise, or schedule dates for either ship or arrival Consume forecasts based on sales order line request, promise, or schedule dates. You must provide forecast dates that match your choice of this plan option; for example, if you select Promise Ship date for this plan option, make sure your forecast dates are in terms of promise ship dates. If you do not specify plan option Demand Priority Rule and have not specified a default demand priority rule (in the Define Priority Ruled form), the planning engine uses the value of this plan option as the demand priority rule. Select one of the following sales order line dates: Schedule Ship Date Schedule Arrival Date Request Ship Date Request Arrival Date Promise Ship Date Promise Arrival Date The default is Schedule Ship Date. Demand Class If you want to limit a production plan to a demand class, enter it. This field is active only for a Production Plan/MPS schedule. Move Jobs to PIP Check this option if you want to generate planned order supply even in the absence of demand in order to ensure that inventory is held on the manufacturing floor only for items designated as Planned Inventory Points. Display Key Performance Indicators Check this option to calculate key performance indicators for the plan. Demand Time Fence Control Check this option to enforce demand time fence control. Demand time fence is an item attribute Planning Time Fence Control Check this option to enforce planning time fence control. Planning time fence is an item attribute Lot for Lot Check this option to force the creation of a separate supply for each demand. This prevents the creation of aggregate supplies that satisfy multiple demands. Order quantity modifiers such as Minimum Lot Size and Fixed Lot Multiple override this option Include Critical Components Select this plan option to instruct the planning engine to plan considering critical components. Depending on the plan type and the planning item types, the planning engine may plan critical components and not plan other components or components of those components. To mark an item as a critical component, select its item attribute Critical Component. 37 MSAT Internal Page 7
38. 38. Parameter Description Comment Setup Do Not Spread Forecast The planning engine should use forecast entries as they exist for planning. Spread Forecast Evenly The planning engine should spread aggregate forecast demand evenly across the daily buckets from the workday calendar. Forecast Distribution Assignment Set Select a forecast distribution assignment set for the global forecasting process. The forecast distribution assignment set contains global sourcing rules used to distribute global forecasts over multiple inventory organizations: The rules to distribute sales orders are in plan option Assignment Set. Consume by Forecast Bucket The forecast consumption process does not search outside of the consumption bucket for forecasts and sales orders except in daily buckets. Explode Forecast Select this plan option to instruct the planning engine to explode forecasts as follows during the consumption process: - Product family forecasts to product family member item forecasts - Model forecasts to other model, option class, and item forecasts. This option applies to forecasts with forecast control Consume and derive. Clear this plan option if you have arranged for this explosion to occur in the source instance or in Oracle Demand Planning before the planning run. Backward Days If you are bringing in unconsumed forecast scenarios from Oracle Demand Planning as demand schedules into Oracle ASCP and would like to do forecast consumption inside ASCP (as opposed to bringing in pre- consumed forecasts contained in master demand schedules as demand schedules into Oracle ASCP), then set the forecasts consumption backward days parameter here. This parameter allows a sales order demand to consume forecast demand even if the forecast demand is up to the specified number of days earlier than the sales order demand. This parameter applies only to Oracle Demand Planning scenarios that are used as demand schedules in Oracle ASCP plans. Forward Days This parameter allows a sales order demand to consume forecast demand even if the forecast demand is up to the specified number of days later than the sales order demand. Enable Pegging Check this option to calculate pegging information. Oracle ASCP traces supply information for an item to its corresponding end demand details, which you can then view in a graphical display. Peg Supplies by Demand Priority Check this option to calculate pegging so that on-hand and firm supplies are pegged to demands in demand priority order (as defined by you in a priority rule) within the time period set by the profile option MSO: Firm Supply Allocation Window (days). Do not check it. Instead, set profile option MSC: Use FIFO Pegging to Yes. 38 MSAT Internal Page 7
39. 39. Parameter Description Comment Setup Pegging Reservation Level Choose a reservation level: Planning Group, Project, Project-Task, or None. Do not use Pegging Hard Pegging Level Choose a hard pegging level: Project, Project-Task, or None. Do not use Forecast Consumption Backward Days If you are bringing in unconsumed forecast scenarios from Oracle Demand Planning as demand schedules into Oracle ASCP and would like to do forecast consumption inside ASCP (as opposed to bringing in pre- consumed forecasts contained in master demand schedules as demand schedules into Oracle ASCP), then set the forecasts consumption backward days parameter here. This parameter allows a sales order demand to consume forecast demand even if the forecast demand is up to the specified number of days earlier than the sales order demand. This parameter applies only to Oracle Demand Planning scenarios that are used as demand schedules in Oracle ASCP plans. Forecast Consumption Forward Days This parameter allows a sales order demand to consume forecast demand even if the forecast demand is up to the specified number of days later than the sales order demand. Do not use Note: 1. Overwrite and Append Planned Orders work together to limit how the planning process reacts to firm planned orders and to stabilize the short-term material plan. When you launch the planning process, you generate new planned orders to meet your net requirements. Since you can firm DRP, MPS, or MRP planned orders, you may not want the planning process to overwrite any firm planned orders. See the table below for more information. Overwrite Append Planned Orders Effects All The planning process overwrites all entries, planned and firm planned, from the current material plan. None The planning process does not overwrite any firm planned orders. It does, however, overwrite any suggested planned orders that are not firm. Outside planning time fence The planning process overwrites all entries from the current plan, planned and firm planned, outside the planning time fence, and overwrites only planned orders inside the planning time fence. It does not overwrite any firm planned orders within the planning time fence. The planning time fence can be different for each item, so the planning process looks at the planning time fence for each item when choosing what to delete. Planning time fence is an item attribute defined in Inventory Unchecked The planning process does not append any planned orders to the current plan. Additional demand does not cause planned order recommendations. Instead, the projected quantity on hand may go negative in response to demand that was not met by a suggested planned order. 39 MSAT Internal Page 7
40. 40. Overwrite Append Planned Orders Effects Checked The planning process appends additional planned orders after the last entry on the current material plan to meet any additional demand. The Overwrite and Append Planned Orders options work in combinations, as described below. All Checked Select this option to create a new material requirements plan for the plan name you specify, deleting all previous planned and firm planned orders while regenerating new planned orders. You can use this combination the first time you run your plan or if you want your plan to reflect all sources of new demand. Outside planning time fence Checked This option allows you to create an extension to the current material requirements plan, delete planned and firm planned orders outside the planning time fence and delete all planned entries inside the planning time fence for each item. The planning process creates (appends) new planned orders after the planning time fence date. In this case, since you are overwriting after the planning time fence, you are also appending new planned orders after that date. Use this combination to stabilize the shortterm plan and allow the longterm plan to react to new sources of demand. If an item has no time fence specified and this option is chosen, all planned and firm planned orders are overwritten. The effect is the same as Overwrite All and Append Planned Orders checked. None Checked When you choose not to overwrite an existing plan, the planning process does not overwrite existing firm planned orders, but deletes any suggested planned orders. The planning process then creates (appends) new planned orders after the planning time fence date. Use this to firm shortterm sections of your material requirements plan. You can extend the plan horizon without altering existing firm planned orders. None Unchecked The planning process does not overwrite existing firm planned entries, but deletes any suggested planned orders. In addition, it does not append additional demand to the end of the plan. Instead, it reports the instances where the material requirements plan is out of balance with the master demand schedule, and allows you to solve these problems by manipulating the plan manually. In this case, the projected quantity on hand would go negative since no planned orders were suggested to meet the additional demand. The material planner can use online inquiries and reports with exception messages to identify material shortages. This gives maximum control to the material planner. Note: 2. Planned Items, Planning Method and Items attribute MRP/MPS Planning method work together to select items in the plan. The following table lists the three controls that together determine which items are planned in a supply chain plan, and the possible values for each control. Planned Items value Plan type Planned Items in the plan All planned items Master Plan All items in the planned organizations having MRP/MPS Planning Method attribute value of MPP planning MRP and MPP planning MPS and MPP planning Plus: MRP planned and MPS planned items that are in between the above items in the bills of material. All items in the input schedules. 40 MSAT Internal Page 7
41. 41. Planned Items value Plan type Planned Items in the plan All planned items Production Plan All items in the planned organizations having MRP/MPS Planning Method attribute value of MPS planning MPS and MPP planning Plus: MRP planned and MRP/MPP planned items that are in between the above items in the bills of material. All items in the input schedules. All planned items Manufacturing Plan All items in the planned organizations except those having MRP/MPS Planning Method of Not Planned Demand schedule items only Master Plan All items in the input demand schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MPP planning MRP and MPP planning MPS and MPP planning Plus: MPS and MRP planned items that are in between the above items in the bills of material Demand schedule items only Production Plan All items in the input demand schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MPS planning MPS and MPP planning Demand schedule items only Manufacturing Plan All items in the input demand schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MRP planning MRP and MPP planning Supply schedule items only Master Plan All items in the input supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MPP planning MRP and MPP planning MPS and MPP planning Plus: MPS and MRP planned items that are in between the above items in the bills of material Supply schedule items only Production Plan All items in the input supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MRP planning MRP and MPP planning Supply schedule items only Manufacturing Plan All items in the input supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MPS planning MPS and MPP planning Demand and Supply schedule items Master Plan All items in the input demand and supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MPP planning MRP and MPP planning MPS and MPP planning Plus: MPS and MRP planned items that are in between the above items in the bills of material 41 MSAT Internal Page 7
42. 42. Planned Items value Plan type Planned Items in the plan Demand and Supply schedule items Production Plan All items in the input demand and supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MPS planning MPS and MPP planning Plus: MPS and MRP planned items that are in between the above items in the bills of material Demand and Supply schedule items Manufacturing Plan All items in the input demand and supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of: MRP planning MRP and MPP planning Aggregation tab Use the information in the following table to specify parameters on the Aggregation tab. Parameter Description Setup Start Date This is a view-only field, whose value equals the start date of the plan if the plan has already been run. Otherwise, it defaults to the system date. End Date Shows the calculated end date for your plan. This is a view-only field, calculated based on the bucket sizes you specify Bucket Size Specify bucket size in days, weeks, and periods. Items Choose aggregation at item level or product family level. Resources Choose resource aggregation at individual level or aggregate level. Routings Choose aggregation level at individual routing or bill of resources level. Minutes Bucket Size Specify the bucket size in minutes for the Days planning period. Hours Bucket Size Specify the bucket size in hours for the Days planning period. Days Bucket Size Specify the bucket size in days for the Days planning period. 42 MSAT Internal Page 7
43. 43. Organization tab Use the information in the following table to set parameters on the Organizations tab. Parameter Description Note Setup Global Demand Schedules Select the names of Oracle Demand Planning scenarios that drive this plan. You can select demand- planning scenarios that do not reference an organization (organization dimension set to All Organization). Ship To Consumption Level Select a forecast consumption level for the Oracle Demand Planning scenario. The global forecasting process consumes forecast entries that have Ship To value the same as this plan option. You can select: - Customer - Customer Site - Zone - Customer Zone - Demand Class - Item The choices in the list of values changes depending on the published level of the scenario. Org The plans organization. Description Description of the owning organization. Net WIP Select to consider discrete jobs and other production orders as supply in the planning demand/supply netting process. Net Reservations If checked, ASCP generates pegging of on-hand supply to sales orders that matches the reservations recorded in the source transaction system. 43 MSAT Internal Page 7
44. 44. Parameter Description Note Setup Net Purchasing Select to consider purchase orders, purchase requisitions, in-transit shipments and other non-production order scheduled receipts as supply in the planning demand/supply netting process. This option covers all scheduled receipts not covered by the Net WIP option. Plan Safety Stock Select to consider plan safety stock demand and supply in the planning demand/supply netting process. Include Sales Order1 Select to invoke forecast consumption within ASCP for the selected organization. Check this if the demand schedules for the organization are unconsumed forecasts. Uncheck this if the demand schedules for the organization are consumed forecasts plus sales orders in the form of master demand schedules Bill of Resource Select Bill of Resources from the list of values if one of the Routings is set to BOR on Aggregation tab. Simulation Set Select a Simulation Set from the list of values. A simulation set is a set of adjustments to the base availability calendar of a resource, and is defined via the Oracle Bills of Materials Department Resources form. You can define different simulation sets to model different availability scenarios (for example, the base availability calendar could reflect 5-day operations; simulation set 1 could reflect working 6 days/week for a certain period; simulation set 2 could reflect working 7 days/week for a certain period). The simulation set that you select is applied to all resources within the organization. Demand Schedules2 Select the name of your demand schedule/forecast/plan. Ship To Consumption Level See above See above Interplant If selected, the planning engine uses only interorganization orders and demands from interorganization planned orders. If cleared, the planning engine uses demands from all planned orders. Supply Schedules Select the name of your supply schedule for each organization. Subinventory Netting Opens the Subinventory Netting window. 44 MSAT Internal Page 7
45. 45. Note: 1. Users can collect forecasts into the APS planning server. Optionally, they can choose to consume forecasts by sales orders when they run ASCP plans. Forecasts are consumed if the Include Sales Order check box in the Organizations tab of the Plan Options window is checked. For multilevel ATO items, forecasts are consumed at all levels if the forecast explosion has occurred in the source instance prior to the collection. If you are not using forecast, uncheck this check box. 2. The plan for one organization can be used as a demand (or demand schedule) for the plan of another organization. Constraint tab Use the information in the following table to specify parameters on the Constraints tab. Parameter Description Setup Constrained Plan If selected, Enforce Demand Due Dates is selected, all fields in the tabbed region are updateable with all constraints defaulted to Yes. The default is cleared. You cannot set all Resource Constraints and Material Constraints to No. If you set any Resource Constraints to Yes, you cannot clear Calculate Resource Requirements. Enforce Demand Due Dates Check this option if you want demand due dates to be your hard constraint (that is, respected in lieu of material and resource capacity constraints, if there is conflict). Enforce Capacity Constraints Check this option if you want material and resource capacity constraints to be respected in lieu of demand due date constraints. Start Date Displays the start date for each bucket type. Buckets Displays the number of buckets of this bucket type. Resource Constraints Select Yes to consider resource constraints for the bucket. Supplier Capacity Constraints Select Yes to consider supplier capacity constraints. 45 MSAT Internal Page 7
46. 46. Parameter Description Setup Enforce Purchasing Lead-time Constraints Select this plan option to instruct the planning engine to constrain the plan by purchased item lead times (item attributes or approved supplier list). Clear it to instruct the planning engine never to miss a demand due date because of a purchased item lead time. Scheduling Specify whether to enable detailed scheduling. Minutes Bucket Size (in Days) Size Specify the bucket size in minutes for the Days planning period. Hours Bucket Size (in Days) Specify the bucket size in hours for the Days planning period. Days Bucket Size (in Days) Specify the bucket size in days for the Days planning period. Calculate Resource Requirements If selected, the program will calculate resource capacity utilization. Planned Resources Select All Resources or Bottleneck Resources. If you have defined bottleneck resource groups in Oracle Bills of Material and you want to detail schedule only the bottleneck resources, select Bottleneck Resources and enter a Bottleneck Resource Group. Bottleneck Resource Group If you have defined bottleneck resource groups in Oracle Bills of Material and you want to detail schedule only the bottleneck resources, select its name. Decision Rules tab Use the information in the following table to specify parameters on the Decision Rules tab. Parameter Description Setup Use End Item Substitution If selected, use end item substitute prior to creating new planned orders. If cleared, use only the demanded item. Enter the End Item Substitution Set in the Main tabbed region. Use Alternate Resources If selected, use primary resource and use alternate resource only if necessary. If cleared, use only primary resources. Use Substitute Components If selected, use primary components and use substitute components only if necessary. If cleared, use only primary components only. 46 MSAT Internal Page 7
47. 47. Parameter Description Setup Use Alternate BOM/Routing If selected, use primary routings and use alternates only if necessary. If cleared, use only primary bills of material and routings. Use Alternate Sources If selected, use primary sources and use alternate sources only if necessary. If cleared, use primary sources only. The planning engine does not use alternate sources (rank 2 or higher) as a sources of supply. Launch a plan Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names> Launch Plan (B) For an ASCP plan, accept the defaults on the request parameters form and click on OK then submit the request. Copy a plan Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names>Copy Plan (B) 47 MSAT Internal Page 7
48. 48. 1. Enter a Name for the new plan 2. Enter Description, optionally 3. Select or clear ATP, Production, and Notification as you would if you are creating a new plan on the Plan Names form. 4. If you want to copy only the plan options from one plan to another of a different plan type, select Copy Plan Options Only 5. Plan Type defaults to the plan type of the source plan and you cannot change it if you want to copy all plan information. 6. Click on OK Planner Workbench The Planner Workbench is the primary work area for analysis of the plan and actions taken based on plan recommendations Multi-window format Ability to have several screen open at the same time Strong navigational interactions between different workbench windows Context passed between windows using right clicks or buttons Ability to see data at detailed and summary levels and drill down/up from one to the other Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Workbench 48 MSAT Internal Page 7
49. 49. Plans tab displays the entities associated with the plan in a hierarchical fashion (user can select the drill down hierarchy) Queries tab displays only those entities within the plan that the user wants to focus on (as pre-defined by the user) Plan Navigator Displays list of plans defined under the organization (Note: The plan although defined in one organization could still be a multi-org plan) View Plans by o Actions o Organizations o Item o Resources o Projects o Suppliers Variety of Right-Click navigations possible from each node (or use of Shortcut buttons at the bottom of the navigator) List of Item Categories displayed is based on Tools Preferences Other Category Set 49 MSAT Internal Page 7
50. 50. Supply chain structure Supply Chain Structure Items and Item Details Right Click on Item (in Navigator) > Items Key data displayed include Lead Times and Order Quantities Variety of other planning related item attributes available for display through Folder functionality Items window is a launching pad to more detailed structural information on the item Supply Chain Bill o Displays Sourcing and BOM structure for the item o Can also show the Reverse BOM I.e. the end items where a component is used Sources o Displays Sourcing (other orgs or Suppliers) from which the Item is sourced from o Shows relative allocation percentages or ranks o Supplier Information: Lead Times, Costs, time varying capacities and flex fences Destinations o Displays Destinations (other orgs) to which this item is shipped to 50 MSAT Internal Page 7
51. 51. Where Used: The items in the next level up in the bill of material that use this item as a component Components: The components defined in this items bill of material (primary and alternates) Co-Products: If the process that produces this item also produces other products, those are displayed here Routing Operations: The operations within the routings (primary and alternate) that are used to produce this item Safety Stock: Prescribed safety stock targets for this item. This screen only shows safety stock defined in the Source ERP as quantity (It does not show safety stock input from IO or the target dynamically calculated by the plan based on safety stock days of supply) Substitutes: If this item is sold as an end item, the valid substitutes that can be offered to a customer requesting this item Inventory Levels: Not used by ASCP Item: Destination: Where Used: 51 MSAT Internal Page 7
52. 52. Components: Routing Operations and Resources: 52 MSAT Internal Page 7
53. 53. Supply Chain: Supply Chain Structure Resources Right Click on Resource (in Navigator) > Resources Displays information about the resource Department, Type, Cost etc. Items Shows the items made on this resource Availability o Summary: Displays summary of resource availability at the planning time bucket level o Detail: Shows the shift level capacity for the selected day. Also allows for update of resource availability 53 MSAT Internal Page 7
54. 54. Gantt Chart Shows graphical view of activities planned on the resource Requirements Shows Forms based view of activities planned on the resource Gantt Chart: Availability: 54 MSAT Internal Page 7
55. 55. Availability > Details: Requirements: 55 MSAT Internal Page 7
56. 56. Supply chain plan result analysis Open Planner workbench Review KPIs Review Exceptions From the context of an exception analyze planning results Make changes to the plan Re-run the plan with the user changes Review results Select orders for release to execution system Release orders Create simulation plans to simulate what-if scenarios Supply Chain Planning Results Exceptions Summary Right Click Exceptions > Summary (sensitive to the level in the tree at which right click is performed) Displays Exceptions as various types classified into groups Shows the count of exceptions by group, type Can Save a version of the Exception messages prior to running a simulation re-plan Can have all exception groups pre-expanded (Tools > Preferences > Other) Supply Chain Planning Results Exceptions Details Double Click on any exception type to open up Exception Details 56 MSAT Internal Page 7
57. 57. Show details of the planning exception Example: Late Replenishment for Forecast. Key information o Item o Org o Order Number o Customer o Demand Due Date o Days Late Folder/Find and Sort capability Navigation to related entities: Items and Supply/Demand Navigation to cause analysis o Related Exceptions o Gantt Chart Action Taken: Mark the exception once action is taken Supply Chain Planning Results Related Exceptions Right Click From Exception Details > Related Exceptions Certain Classes of Planning Exceptions have Related Exceptions (when the Related Exceptions pop up menu enabled) o Late Replenishment for Sales Orders/Forecasts o Sales Order / Forecast at Risk o Sales Order / Forecast at Risk due to Resource/Material Shortage Related exceptions point to root causes Show the cause effect across multiple levels in the supply chain structure Root causes could be o Resource capacity shortages o Material capacity shortages o Lead Times 57 MSAT Internal Page 7
58. 58. Supply Chain Planning Results Horizontal Plan There are 4 types of Horizontal Plans 1. Material Plan: Classical Planner spreadsheet showing supplies and demands and projected available balances at the planning bucket level 2. Resource Capacity: View of Resource hours available versus used along with capacity utilization % information 3. Supplier Capacity: Shows Supplier capacity (available versus used) by planning time bucket and tracks the cumulative available at any point in time 4. Transportation Capacity: Shows the capacity available versus used for transportation resources Navigation to the horizontal plan is possible either from the navigator tree or from other windows where the relevant context is available such as Item, Resource or Supplier Users can control via preference sets o T