Use this screen to turn planned orders generated by the MRP process into manufacturing orders, purchase requisitions, and transfer reservations/requests. Use it to select and group planned orders using user-definable criteria, apply lot-sizing rules as necessary, generate the orders, and delete the original planned orders that were processed. Inventory on-order, on-requisition, reserved, and owed quantities are also updated when the orders/requisitions/reservations are generated. You have the option of generating a trial-run report (or on-screen preview) of the objects that would be created. These same reports will be used to produce a log of all objects generated by the process.
The basic process flow when generating these manufacturing orders, requisitions, and transfer reservations is as follows:
You can run the MRP process to generate planned orders based on independent and calculated demand as well as current inventory and scheduled supply orders. MRP generates planned orders where the current supply is insufficient to meet the demand requirements for that part. Costpoint Material Requirements Planning will also create an action message for each planned order generated to alert planners that the planned order must be created.
You can select and modify planned orders using either of two maintenance applications: the Manage Detailed Part Schedule or the Manage MRP Action Messages screens. You can use either application to modify the date and quantity information, manually assign the planned order an ID, and select planned orders for firming or releasing. If you do modify planned orders in this step, be sure to run the Firm Material Requirements Planning Planned Orders application for these planned orders before you next run MRP, which will generally delete all existing planned orders and re-create them as necessary.
You can then run this process for those planned orders selected in step 2 or for all planned orders within given selection criteria. The results of this process will be purchase requisitions, manufacturing orders, and inventory transfer reservations/requests.
You can then modify these manufacturing orders, requisitions, and reservations in their respective maintenance screens.
Selection of planned orders for firming or releasing will depend on the screen criteria entered when running the process. In order to be included, the planned order will have to meet all the criteria specified on the main screen. Selection criteria include Planner, Warehouse, Netting Group, Project, Part, Order, and Order Date Cutoff. You can also specify whether to include only those planned orders that were marked for firming/releasing or to include all planned orders.
There will be one requisition line, MO allocation, or transfer reservation line generated for each selected planned order. The planned orders are then grouped (according to guidelines established by various settings) and order quantities adjusted to minimize the affect of minimum/multiple lot sizes. A planned-order group consists of one or more planned orders that will be included in the same requisition, MO, or reservation header. The planned orders are first separated by Order Type (Make or Buy).
Costpoint will generate a manufacturing order for each unique occurrence of the order ID. Planned orders with the same order ID will be grouped together. For all Make (manufactured) planned orders without an order ID specified, those with the same part/revision, warehouse, planner, MRP planning code, and BOM configuration will be grouped together, provided the combination of orders is allowed. Planned orders that have been specified as "not combinable" are not combined with any other planned order. (To make a planned order combinable, select the Combine Orders check box for the planned order in the Planned Order subtask of the Manage MRP Actions Messages screen or in the Planned Order Supply subtask of the Manage Detailed Part Schedule screen.)
If multiple project allocations are not permitted in manufacturing orders (in the Configure Production Control Settings screen), planned orders also need to have the same inventory abbreviation in order to be eligible for grouping. If multiple project allocations are permitted in manufacturing orders, the grouping of planned orders will depend on the associated inventory project's project planning option code (in the Manage Inventory Projects screen in Costpoint Inventory) and manufacturing order allocations setting (in the MO Allocations Across Projects group box in the Manage Inventory Projects screen in Costpoint Inventory). Both of these codes need to be favorable for planned orders to be grouped together.
Grouping possibilities for various project planning option codes are as follows:
Project — Planned orders can be grouped together only if the associated inventory project is the same.
Top-Level Project — Planned orders can be grouped together only if the associated inventory project has the same top-level project.
Netting Group — Planned orders can be grouped together only if the associated inventory project has the same netting group.
All Projects — Planned orders can be grouped together regardless of their associated inventory project or netting group.
Grouping possibilities for various manufacturing order allocation codes (as set in the Manage Inventory Projects screen) are as follows:
MO Allocation "Not Allowed with other Projects" — Planned orders can be grouped together only if the associated inventory project is the same.
MO Allocation "Within Same Top-Level Project" — Planned orders can be grouped together only if the associated inventory project has the same top-level project.
MO Allocation "Within Same Netting Group" — Planned orders can be grouped together only if the associated inventory project has the same netting group.
MO Allocation "Allowed with other Projects" — Planned orders can be grouped together regardless of their associated inventory project or netting group.
A requisition will be generated for each unique occurrence of the order ID (specified in the Manage Detailed Part Schedule screen). Planned orders with the same order ID will be grouped together.
For all Buy (purchased) planned orders without an order ID specified, grouping will take place according to the requisition grouping selected in the Configure Purchase Requisition Settings screen in Costpoint Procurement Planning, provided combination of orders is allowed. Various grouping possibilities are by item, buyer, commodity code, planner, project, netting group, and order reference.
Planned orders that have been specified as '"not combinable"' are not combined with any other planned order, but will be turned into one-line requisitions. (To make a planned order combinable, select the Combine Orders check box for the planned order in the Planned Order subtask of the Manage MRP Actions Messages screen or in the Planned Order Supply subtask of the Manage Detailed Part Schedule screen.) Planned orders with different BOM configuration IDs will also not be grouped together.
If you assign approval processes by Project/Account/Organization (in the Configure Purchase Requisition Settings screen in Costpoint Procurement Planning), grouping will also take the inventory project into consideration. For instance, if the requisition grouping is by item, each item number will have its own requisition. If the requisition grouping is by item, but requisition approval processes are assigned by Project/Account/Organization, each item/project combination will have its own requisition. If the planned order does not have the requisition grouping criteria value (order reference), the planned order is not grouped with any other planned orders. Also, if the Requisition option is selected in the Approval Level group box in the Configure Purchase Requisition Settings screen in Costpoint Procurement Planning, and Requisition Approval Process Assignment is Manual, grouping is not done if the planned orders have different approval process codes.
The program will generate a reservation for each unique occurrence of the order ID (specified in the Manage Detailed Part Schedule screen). Planned orders with the same order ID will be grouped together.
For all transfer reservation planned orders without an order ID specified, grouping will take place for planned orders that have the same warehouse and from and to inventory abbreviations, provided the combination of orders is allowed. Planned orders that have been specified as '"not combinable"' are not combined with any other planned order. (To make a planned order combinable, select the Combine Orders check box for the planned order in the Planned Order subtask of the Manage MRP Actions Messages screen or in the Planned Order Supply subtask of the Manage Detail Part Schedule screen.)
For each Make and Buy planned-order group (including planned orders not grouped with any others), quantities are adjusted to conform to specified minimum/maximum/multiple lot size restrictions as per the Order Policy group box in the Planning subtask of the Manage Parts screen in Costpoint Product Definition. Lot size restrictions never apply to transfer reservation planned orders, nor to scheduled receipts for which you override the lot-sizing rules.
Period Order Policy
If the Policy type is Period in the Planning subtask of the Manage Parts screen in Costpoint Product Definition, planned orders within the same work period will be grouped together, sorted in ascending order. (The work period will be defined in terms of calendar days or shop days, depending on the Lead Time Calculation group box in the Configure Production Control Settings screen.)
For example, five planned orders are grouped together with due dates of 1/1/03, 1/5/03, 1/18/03, 2/1/03, 3/4/03. Assuming that the shop calendar is not used and the part has a Policy Type of Period and a period-days number of 30, this group of planned orders will be broken into three manufacturing orders, with a due date of 1/1/03 (which will include the quantities from the second and third planned orders), 2/1/03, and 3/4/03.
Minimum/Multiple Lot Size Policy
For parts with a Policy Type of Min/Mult Lot Size in the Planning subtask of the Manage Parts screen, and if the extra quantities of Make parts are not to be ignored (Minimum Lot Size Allocation-Make field in the Configure Material Requirements Planning Settings screen), Costpoint adjusts the sum of the grouped planned orders to meet the minimum/multiple quantities specified for the part. If this quantity is less than the minimum quantity or is not evenly divisible by the multiple quantity (if not zero), the order quantity is increased to meet both requirements.
If the extra quantities of Make parts are to be allocated, the extra quantity is allocated proportionately to the other planned orders in the group. This is accomplished by dividing the order quantity by the total order quantity and the percentage applied to the extra quantity. If the quantity cannot be evenly divided by whole number, the remainder is allocated to the order with the earliest due date and the lowest project ID.
If the extra quantities of Make parts are to be allocated to common stock, the extra quantity is allocated to the common stock Inv Abbrev for the part (Planning subtask of the Manage Parts screen in Costpoint Product Definition). If that value is not available or the inventory abbreviation is inactive, the Default Common Stock Inv Abbrev from the Configure Production Control Settings screen in Costpoint Production Control will be used.
Max Lot Size
For parts with a Policy Type not that is not Min/Mult Lot Size in the Planning subtask of the Manage Parts screen, if the Max lot size specified is greater than zero and the sum of the order quantities is greater than the maximum quantity, the planned orders in the group are sorted by due dates and regrouped into two or more groups to prevent the maximum quantity from being exceeded. Planned orders are not split unless the quantity of an individual planned order is greater than the maximum quantity itself. If a given planned order takes the proposed manufacturing order quantity past the maximum, the entire planned order is split into the next group. If the order quantity itself is greater than the maximum, the order is split up into maximum size lots (with any remainder allocated to a separate planned order group).
Period Order Policy
If the Policy Type is Period in the Planning subtask of the Manage Parts screen, planned orders for the same part within the same work period will be assigned the same due date. The work period will be defined in terms of calendar days or shop days, depending on the Lead Time Calculation group box in the Configure Production Control Settings screen.
For example, five planned orders are grouped together with the due dates of 1/1/03, 1/5/03, 1/18/03, 2/1/03, and 3/4/03. Assuming that the shop calendar is not used and the part has a Policy Type of Period and a period-days number of 30, the due dates for the orders will be modified. The due dates of this group, 1/5/03 and 1/18/03, will be changed to 1/1/03.
Minimum/Multiple Lot Size Policy
For each part in a planned order group with a Policy Type of Min/Mult Lot Size in the Planning subtask of the Manage Parts screen, if the extra quantities of Buy parts are not to be ignored (Minimum Lot Size Allocation-Buy field in the Configure Material Requirements Planning Settings screen), the sum of the grouped planned orders is adjusted to meet the minimum/multiple quantities specified for the part. If this quantity is less than the minimum quantity or is not evenly divisible by the multiple quantity (if not zero), the order quantity is increased to meet both requirements.
If the extra quantities of Buy parts are to be allocated, the extra quantity is allocated proportionately to the other planned orders in the group having the same part. The program does this by dividing the order quantity by the total order quantity and applying the percentage to the extra quantity. If the quantity cannot be evenly divided by a whole number, the remainder is allocated to the order with the earliest due date and the lowest project ID.
If the extra quantities of Buy parts are to be allocated to common stock, the extra quantity is allocated to the common stock Inv Abbrev for the part (from the Planning subtask of the Manage Parts screen). If that value is not available or the inventory abbreviation is inactive, the Default Common Stock Inv Abbrev from the Configure Production Control Settings screen will be used.
Max Lot Size
If the order quantity on an individual planned order is greater than the maximum quantity, the order is split up into maximum size lots (with any remainder allocated to a separate planned order within the same group).
When validating planned orders, if there are conditions that prevent the generation of requisitions, manufacturing orders, and reservations, the system generates an exception report listing the planned orders with errors. Costpoint checks for the following error conditions:
The order ID provided for the planned order (Make type) is a duplicate of an existing manufacturing order ID.
The order ID provided for the planned order (Buy type) is a duplicate of an existing requisition number.
The order ID provided for a transfer reservation planned order is a duplicate of an existing reservation ID for the warehouse/reservation combination.
The same order ID is provided for more than one planned order (Make type), but the orders are for different inventory projects, and one of the inventory projects does not allow MO allocations with other projects (the Not Allowed with Other Projects option is selected in the Manage Inventory Projects screen).
The same order ID is provided for more than one planned order (Make type), but they are for different netting groups, and one of the inventory projects does not allow MO allocations with projects having a different netting group (the Within Same Netting Group option is selected in the Manage Inventory Projects screen).
The same order ID is provided for more than one planned order (Make type), but they are for different top-level projects, and one of the inventory projects does not allow MO allocations with projects having a different top-level project. (the Within Same Top-Level Project option is selected in the Manage Inventory Projects screen).
The same order ID is provided for more than one planned order (Make type), but they are for different inventory projects, and one of the inventory projects has an MRP Project Planning Option code of Project-No CS or Project-CS (as specified in the Manage Inventory Projects screen). (You can group planned orders together only if the associated inventory project is the same.)
The same order ID is provided for more than one planned order (Make type), but they are for different inventory projects, and one of the inventory projects has an MRP Project Planning Option code of Top-Level Project-No CS or Top-Level Project-CS. (You can group planned orders together if the associated inventory project has the same top-level project).
The same order ID is provided for more than one planned order (Make type), but they are for different inventory projects, and one of the inventory projects has an MRP Project Planning Option code of Netting Group-No CS or Netting Group-CS. (You can group planned orders together if the associated inventory project has the same netting group).
The same order ID is provided for more than one planned order (Make type) with different inventory abbreviations, while multiple allocation manufacturing orders are not allowed in the Configure Production Control Settings screen (the Allow Multiple Inv Abbrev Build-To Allocations for MOs check box is cleared).
A manufacturing order will be created for each planned order group.
If you do not enter a starting MO ID, the normal system assignment process selected in the configure Production Control Settings screen is used, using the default build-to inventory abbreviation or warehouse. If you enter a starting MO ID, it will be used as the basis for assigning IDs to created manufacturing orders. If you manually enter an order ID (in the Manage Detailed Part Schedule or Manage MRP Action Messages screens), it will be used as the MO ID.
When more than one planned order is being combined onto one MO, the earliest of each type of date (order, as-of, due, planned release, planned shop) is used. MO allocations are created with the quantities combined for planned orders having the same inventory abbreviation. If there is a mix of firm planned and released selections, the MO is assigned a status of "Firm Planned."
The build quantity is the sum of the open quantity in the planned order group (adjusted by lot-size rules as necessary). This determines the quantities for requirements and reservations generated.
If more than one inventory abbreviation is included in a planned order group, the first planned order (using due date sequence) inventory abbreviation with an account type of A' as the build-to inventory abbreviation is used as the build-to inventory abbreviation for the MO. If none of the planned order inventory abbreviations have an account type of A, the first (using due date sequence) planned order's inventory abbreviation is used as the build-to inventory abbreviation for the MO. In the latter case, the inventory abbreviation of that planned order will also determine the MO ID (if assigned by inventory project), along with effective dates and order reference information
The build-to inventory abbreviation also determines the inventory abbreviations for the subassembly, raw material, and common stock (if the MRP planning code allows it - see Special Topic MRP-1) associated with requirements for the MO. If the subassembly or raw material inventory abbreviation is unavailable, the build-to inventory abbreviation is used instead. If the common stock inventory abbreviation is unavailable or inactive, the Default Common Stock Inv Abbrev from the Configure Production Control Settings screen is used instead.
The status of the MO is based on whether the selected planned order was designated as F (Firm) or R (Released) in the Select field of the Manage Detailed Part Schedule or Manage MRP Action Messages screens. If this field had been left blank, the MO status will depend on the selection made (for all planned orders) in the Firm Material Requirements Planning Planned Orders screen. If there is a mix of firmed and released planned order selections in a group, the MO is assigned a status of Firm Planned.
MOs created with a status of Released will allow Issue and Subcontract charges. Timesheet charges will be allowed only if you selected the Allow Auto-Update MO status In-Shop check box in the Configure Production Control Settings screen. MOs created with a status of Firm Planned will not have any charges allowed.
For each MO, the text codes associated with the part/project (and having a where-used type of Traveler and/or Assembly Sheet) are used. If the MO is for more than one project, all projects included in the planned order group are checked.
The process of generating requirements for a MO is similar to that in Costpoint Production Control. During the MO generation process, the system calculates total requirements by exploding through all the bill of material levels of the end part. A generated MO will have material requirements based on only one level of explosion, except in the case of a phantom part for which explosion is done as an additional step. If the Make part does not have a BOM, requirements are not generated. Any time requirements are generated, an inventory reservation is also created. The reservation number assigned is the same as the MO ID (if you selected the Set Reservation ID to MO Number check box in the Configure Production Control Settings screen). Otherwise, the reservation number will be based on the Starting Reservation number entered in Options group box of the Firm Material Requirements Planning Planned Orders screen. If that is also unavailable, then the reservation number will be based on the last reservation ID for the warehouse.
Costpoint uses the build-to inventory abbreviation of the assembly to check if any inventory abbreviation peggings exist for the corresponding components. If an exact match is found, the pegged inventory abbreviation and associated project is used for the requirements.
If a match does not exist, there are various scenarios. If the component is a common stock part and the selected build-to project allows common inventory projects, the inventory abbreviation will be based on the one entered in the Planning subtask of the Manage Parts screen. If that is unavailable or inactive, then the build-to project's common stock inventory abbreviation is used. If that is also unavailable or inactive, the Default Common Stock Inv Abbrev from the Configure Production Control Settings screen is used. In each case, the project for the requirement will be the one associated with the inventory abbreviation.
If the component is a Buy part and the common stock part criteria cannot be met, the build-to inventory abbreviation is used to determine the default raw material inventory abbreviation and associated project. If the component is a Make part and the common stock part criteria cannot be met, the build-to inventory abbreviation is used to determine the default subassembly inventory abbreviation and associated project. If none of the above conditions are met, or no inventory abbreviation codes can be found for the components, the selected build-to inventory abbreviation and associated project are used.
When generating MOs, Costpoint automatically generates routings for the end part and all Make parts below it, if the routing number is loaded for the end part. The supplied end part routing is used for the end part MO, but any other routings below that top part use the routing designated as Primary (in the Release Routings screen of Costpoint Routings). If a primary routing does not exist for the part, no routing will be loaded. Alternate operations are not included on a routing.
A requisition header is generated for each planned order group. A separate requisition line is created for each part/inventory abbreviation/due date combination in the planned order group. Within a requisition, requisition lines are sorted and numbered by part number, revision, due date, project. The requisition generation process follows the same basic logic found in the requisition generation process in the Material Requirements Report, Sales Order Requisition generation, and the Inventory Reorder processes.
The Requisitioner/Requestor entered in the Options group box of the Firm Material Requirements Planning Planned Orders screen is used as the requisitioner in the requisition header. In the Generate group box, if you selected the Use Planner Employee check box, the requisitioner will be the same as the planner from the group's first planned order's planner ID. The organization and telephone number associated with the employee ID for the requisitioner are used in the requisitions.
The requisition header will have a project and associated project abbreviation only if all the requisition lines are for the same project.
The ship ID associated with the warehouse is used to determine the ship ID for all requisition lines generated. If that is unavailable, the default ship ID from the Configure Purchasing Settings screen in Costpoint Purchasing is used.
The buyer ID for the requisition lines is based on the buyer in the planned order. The requisition header will have a buyer assigned only if all the requisition lines have the same buyer.
The quantity in the requisition lines is expressed in the part's order unit of measure. If the part's order unit of measure is different from the inventory unit of measure, planned order quantities are converted to the order unit of measure using the conversion tables in the U/M Conversions subtask of Manage Parts screen. Or, if such a conversion does not exist, use the Autoload button of the Units of Measure subtask of the Manage Parts screen.
Generated requisition lines have a default preferred vendor, if established in the Assign Vendors to Items screen in Costpoint Product Definition for the requisitioned parts.
If the part in the requisition line has an existing open blanket purchase order line with a purchase agreement code of S or A, the generated requisitions will also have a Suggested Blanket PO defaulted in (equal to the corresponding PO ID) as the source for the part. If the purchase agreement code is equal to A, Costpoint automatically processes the generated requisition and assigns it to the blanket purchase order. If the requisition unit of measure is different from that of the blanket purchase order, the requisition quantities are converted to the PO unit of measure. If no conversion factors are available, such assignments do not occur. If the purchase agreement code is equal to S, Costpoitn suggests a blanket PO only for the requisitions but does not automatically create it. Period of performance, lead time, and minimum quantity criteria must be met before the system can suggest a blanket order or assign the requisition to a blanket purchase order.
Costpoint uses the cost type with the lowest sequence number, excluding zero (from the Manage Purchase Requisition Cost Types screen in Costpoint Procurement Planning). Possible types are IL (Item Last Cost), IS (Item Standard Cost), IR (Item Reference Cost), PL (Project/Item Last Cost), PS (Project/Item Standard Cost), and PR (Project/Item Reference Cost). If that total cost is not zero, it is loaded into the Est Unit Cost field. If it equals zero, or the correct row cannot be found, the cost value for the type with the next lowest sequence number is used. The selected value determines the cost type. An estimated unit cost of zero is loaded if no cost types apply. If the order's unit of measure is different from the inventory unit of measure, unit costs are adjusted to account for the conversion factor. Whether the requisition line is taxable or not depends on the Default Taxable Status group box in the Configure Purchasing Settings screen. (If you have selected the Use Item Type Default option, it will depend on whether parts are set up as taxable in the Configure Product Definition Settings screen in Costpoint Product Definition). If you have selected the Auto Calculate Sales/VAT Tax check box in the Configure Purchasing Settings screen, the tax for taxable parts is calculated using the requisition line ship ID's sales tax code for the warehouse.
The approval process assignment is determined in the Requisition Approval group box in the Configure Purchase Requisition Settings screen. The Approval Level determines whether the approval process is to be assigned at the requisition header or line level. The option you select in the Process Assignments group box determines the default settings for the approval:
No Approval Required — There is no default approval process.
Global — The default is the Approval Process code from the Configure Purchase Requisition Settings screen.
Manual — The default is the approval process from the planned order. If that is unavailable or invalid, Req Approval Process Code from the Manage Inventory Projects screen is used. If that does not exist, the Approval Process code from the Configure Purchase Requisition Settings screen defaults in. If that is also non-existent, a requisition can be created, but the status will always be Pending,=" forcing you to add an approval process for each requisition and submit it for approval.
Proj/Acct/Org — The default is the requisition approval process that is linked to the project associated with the inventory abbreviation that is used for the generated requisitions. Such a link is set up in the Link Project subtask of the Manage Purchase Requisition Approval Processes screen in Costpoint Procurement Planning. If such a project link does not exist, the default is the requisition approval process that is linked to the account/organization associated with the inventory abbreviation that is used for the generated requisitions. Such a link is set up in the Link Acct/Org subtask of the Manage Purchase Requisition Approval Processes screen.
Item Type — The default is the requisition approval process that is linked to an item type of Part. Such a link is set up in the Manage Purchase Requisition Approval Processes screen.
Initial Status
The initial status of the requisitions or requisition lines depends on the Select code assigned to the planned order in the Manage Detailed Part Schedule or Manage MRP Action Messages screens. The initial status will be Pending if the planned order has a Select code of F, or an approval process is required but could not be assigned. The status will be In-Approval if the planned order has a Select code of R. The status will be Approved if you select R but the assigned approval process does not have any approval titles with an Approval Type of Electronic or Both, as selected in the Manage Purchase Requisition Approval Titles screen in Costpoint Procurement Planning. The initial status will also be Approved if you select R and the No Approval Required option is selected in the Purchase Requisition Settings screen. The approval date on the requisition line will be the date when the requisition was generated (if approved). If there is a mix of firmed and released selections in the planned order group, all the requisition lines are assigned a status of Pending. If you are approving by requisition lines and a given requisition has a combination of in-approval and approved lines, the requisition header status is changed to In-Approval.
For each requisition line, text codes associated with the part/project (and having a where-used type of Purchasing and/or Requisitions) will be used.
For each requisition line, if the requisitioned part is an assembly and you did not select the Stop Explosion check box for the planned order in the Component subtask of the Release Manufacturing Bills of Material in Costpoint Bills of Material, Costpoint calculates component requirements by exploding through the bill of material levels. Requirements are based on only one level of explosion, except in the case of a phantom part for which explosion is done as an additional step. Anytime a requirement is identified, a PO reservation line is created. The warehouse corresponding to the requisition line is used to auto-assign the reservation ID.
Costpoint uses the build-to inventory abbreviation of the assembly to check whether any inventory abbreviation peggings exist for the corresponding components. If it finds an exact match, it uses the pegged inventory abbreviation and associated project for the requirements.
If a match does not exist, there are various scenarios. If the component is a common stock part and the selected build-to project allows common inventory projects, the inventory abbreviation will be based on the one entered in the Planning subtask of the Manage Parts screen. If that is unavailable or inactive, the build-to project's common stock inventory abbreviation is used. If that is also unavailable or inactive, the Default Common Stock Inv Abbrev from the Configure Production Control Settings screen is used. In each case, the project for the requirement will be the one associated with the inventory abbreviation.
If the component is a Buy part, and the common stock part criteria cannot be met, the build-to inventory abbreviation is used to determine the default raw material inventory abbreviation and its associated project. If the component is a Make part, and the common stock part criteria cannot be met, the build-to inventory abbreviation is used to determine the default subassembly inventory abbreviation and its associated project. If none of the above conditions are met, or no inventory abbreviation codes can be found for the components, the selected build-to inventory abbreviation and associated project are used.
The system creates a separate reservation for each planned order group. If planned orders share the same part key, due date, and from and to inventory abbreviations, the quantities are combined on one reservation line. Otherwise, each planned order becomes a separate reservation line.
If you have supplied the Requisitioner/Requestor employee ID in the Options group box of the Firm Material Requirements Planning Planned Orders screen, that ID will be used as the requisitioner in the Requisition header. If you selected the Use Planner Employee check box as the requestor, the planner associated with the first planned order in the group will be used as the requestor.
If one or more of the planned orders in the groups is selected for firming, an inventory request is generated. If all the planned orders are selected for release, an inventory reservation is created.
The need date for the reservation line is the planned order's due date, and the need date of the reservation header is the earliest planned order due date.