Use this function to identify orders associated with a specific assembly (BOM) at a specific location (site) and to generate those orders directly from the information displayed.

You can filter the results to be displayed by many factors. These include references (the source document for 'firm' sales orders), a range of product categories for subassemblies (semi-finished goods) and components, and even a specific business partner.

The results of the planning run include the stock levels. You can use this information to include or exclude orders individually or en masse, before generating the orders.

 The process is not recorded on sales orders. You must, therefore, take care not to duplicate the process.

 

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Multi-level planning function displays an initial screen into which you enter your selection (or filtering) criteria and a screen that displays the results of planning run.

Entry screen

You use this screen to enter your selection (or filtering) criteria.

Block number 1

Site (field MFGFCY)

By default, the production site (or the storage site for a folder without the manufacturing module) associated with the user is suggested.
It can be modified with another site authorized for the operator, depending on the authorizations of the latter.
It must be a purchase and storage site if the type of the product-site is "Subcontract". Else, it must be a production site.
User (field PLANNER)

Operator in charge of performing the production planning or product ordering.

By default, this field is filled with the user code. This code is used to filter the products which the user can interact with by using the general parameter GPLNFLT - Planner/buyer filter (chapter STO, group SCH).
Product (field ITMREF)

This field specifies the reference of the product to to process.

This is the product at the head of the BOM, "Manufacturing" or "Subcontract", depending on the suggestion type of the product-site.
Major version (field ECCVALMAJ)

The current version of this product is displayed:

  • Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed.
  • Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

You can type in, or select a different version of this product, if required. This field is not available for entry if the product code defined in the Product field is not version managed.
Minor version (field ECCVALMIN)
Change request (field CRID)

This field displays a change request ID if this product, or the specific version or revision of this product is associated with an 'active' change request. An active change request is a change request at the planning or implementation stage of the processing cycle. A warning icon is displayed adjacent this field.

If a warning icon is displayed you should consider delaying creating or generating transactions for this product until the change request identified is closed. At that point a change to this product will have either been seen through to its conclusion and the change delivered, or the change request rejected. You will not, however, be prevented from creating or generating a transaction should you decide to do so.

Planning

Status (field MFGSTA)

This field specifies the status of the order to generate: "Planned" or "Firm".
Planned quantity (field EXTQTY)

This field displays the planned quantity. The quantity is expressed in the stock unit.
Start date (field STRDAT)

This field specifies the planned start date of the work order or subcontract order.
End date (field ENDDAT)

This field specifies the planned end date of the work order or subcontract order.

Process

BOM code (field BOMALT)

Specifying this field is mandatory.
If the suggestion type of the product-site is "Subcontract", the type of the BOM code must be "Subcontract".
Else, the type of the BOM code must be "Manufacturing".

Routing (field ROUNUM)

The routing is used to describe the product manufacturing process.
The routing identifier is a product reference which can be the reference of a manufactured product, or a generic reference (mother routing) linked to several products.

If the suggestion type of the product-site is "Subcontract", the routing and routing code are not to be specified.
Major version (field ROUECCMAJ)

The current version of this routing is displayed:

  • Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed.
  • Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

You can type in, or select a different version of this routing, if required. This field is not available for entry if the displayed routing code is not version managed.
Minor version (field ROUECCMIN)
Routing code (field ROUALT)

Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning).

If the suggestion type of the product-site is "Subcontract", the routing and routing code are not to be specified.
Lead time (field LTICOD)

This field indicates whether the start/end dates of the work orders, and receipt dates of the purchase orders and subcontract orders, must be calculated according to the lead-times specified for each product, or according to the times of the routings (with scheduling simulation).
In the case where the automatic work order transaction expects a scheduling, a warning messages is triggered if the user has requested a launch based on the product lead-times.
Lead-time (+QC) (field AVAOFS)

  • If the suggestion type of the product-site is "Subcontract", the lead-time indicated is initialized by the sales lead-time of the product-site.
    This lead-time is updated after entering the BOM code, with the subcontract service lead-time of the BOM.
  • Else, the lead-time indicated is the production and quality control lead-time.

Block number 4

Order description (field MFGDES)

If specified, the description will be applied to all the work orders and subcontract orders generated.
BP (field BPCNUM)

If specified, the BP will be applied to all the work orders, purchase orders and subcontract orders generated.
Project (field PJT)

When specified, the project code will be applied on all the work orders, purchase orders and subcontract orders generated, except for the purchase orders linked to a contract, for which the project code used is that of the contract.
Original document (field VCRNUMORI)

If specified, the number of the requirement source document will be applied to all the work orders, purchase orders and subcontract orders generated.

Semifinished

Category (field TCLCODSTR)

These fields constitute a filter for the BOM levels to process. It is thus possible to specify the BOM sub-levels to precess by applying a filter on the product category: only the products of the split BOM whose category is included in the range entered.
Management mode (field MGTCOD)

These fields constitute a filter for the BOM levels to process. It is thus possible to specify the BOM sub-levels to precess by applying a filter on the management mode: only the products of the split BOM whose management mode is the one selected will be filtered.
Ctrl stock avail. allocation (field STODISFLG)

If activated, this indicator is used to control the level of available stock before launching the reorder, in order to avoid overstock situations. When this control is performed, a reorder request is made only for the products which are out of stock. Otherwise the reorder will be requested irrespective of stock being available or not.
SEEINFO  The control of the level of available stock is performed only in the case when the order line of the launched product has been "Assigned" or "Allocated".

WO documents

Report (field IMPFLG)

Activation/deactivation of the print.
Printer (field PRT)

Printer code.

Results screen

The Results screen displays the results of the BOM explosion. It displays the products and components through each level of the selected assembly (BOM) that it is proposing to create planned or firm work orders for. Each sublevel processed takes into account the filters defined in the selection screen.

If the BOM is versioned, the exploded BOM displays the version (major or major+minor) defined in the selection screen. Each subassembly or component displays the version appropriate to the version of the BOM defined in the selection screen.

You can create (or generate) work orders for all selected suggestions. The data required to create the work orders is complete and correct.

Suggestions that are not checked (that display the product code in red) contain incomplete data. You must complete or correct the required data before you can create the work orders. Data to consider is as follows:

  • Work orders:
    • The dates must be valid (it is possible, however, to let the system generate a work order start date).
    • If the BOM is versioned, the displayed BOM version must be consistent with the calculated start date (field Start date).
    • If the routing is versioned, the displayed routing version must be consistent with the calculated start date.
  • Subcontract orders. The supplier record must exist.
  • Purchase orders. At least one of the following must be specified:
    • The contract number (you can view the list of existing contracts for the product from the Actions icon).
    • The supplier. A preferred supplier is displayed, if known. You can amend the supplier. You must specify a supplier if you are creating a firm order.

 Each line is only a suggestion. No work orders have been created at this point. You can can still modify or complete these suggestions manually.

 To prevent the generation of a proposed order, even if it is complete, simply clear the check box.

 You must define at least one entry transaction which is dedicated to the automatic work order generation functions (to support the release of order plans). The transaction code must be attached to the general stock parameter MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS).

Block number 4

Sort by level

Click Sort by level from the Actions icon to reorder the proposed orders by assembly (BOM) level.
Sort by sequence

Click Sort by sequence from the Actions icon to reorder the proposed orders by sequence.
Stock management data

Click Stock management data from the Actions icon to view the management data and reorder rules for this product.
Planning workbench

Click Planning workbench from the Actions icon to view the planning workbench for this product.
BOM window

Click BOM window from the Actions icon to view details of a selected assembly (BOM) and the components that make up the assembly.

Specific actions

Click the Reinitialize action to restore the data to the original results of the planning run.

Click Include all to select all valid product lines.

Click Exclude all to clear all selected product lines.

Click Generate to generate planned or firm (as specified on the selection screen) work orders and purchase orders from the selected product lines. The System log provides details of the generated order numbers and products processed.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

The release transaction includes automatic scheduling. Continue on the basis of the product lead times?

This message is displayed if the process includes a calculation of the dates using the lead-times entered at the product level while the automatic release transaction associated with the process includes scheduling of the generated work orders.

Tables used

SEEREFERTTO Refer to documentation Implementation