Multi-level planning

• 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.

• 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.

• 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.

• 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.

• 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.
  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".

• Report (field IMPFLG)

Activation/deactivation of the print.

• Printer (field PRT)

Printer code.

• field PECFLG

This is the selection indicator.

• Lev. (field LEVEL)

• field PLNTYP

• Product (field ITMREF)

• Description (field ITMDES1)

• Major version (field ECCVALMAJ)

This field indicates which version of this product applies. 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.

This field is not populated if the product code defined in the Product field is not version managed.

• Minor version (field ECCVALMIN)

This field indicates which minor version of this product applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

This field is not populated if the product code defined in the Product field is not version managed.

• 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 this transaction 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 this transaction should you decide to do so.

• Planned quantity (field EXTQTY)

This field displays the planned quantity. The quantity is expressed in the stock unit.

• STK (field STU)

• Available quantity (field AVASTO)

• Available at date (field DISSTO)

• First availability (field FIRAVADAT)

• Start date (field STRDAT)

This field identifies the planned start date of the order.

• End date (field ENDDAT)

This field identifies the planned end date of the order.

• BOM code (field BOMALT)

Several BOMs can be defined for a single product reference.
They can be distinguished via the code, entered on two numbers.

The various BOM codes can be used to manage different product structures according to their use context such as:

• MRP calculation,
• sales order entry,
• manufacturing/production.

This field can be left empty (value = 0) to enable manual entry of the components. In this case, only the component is loaded.

• BOM type (field BOMALTTYP)

The code type is used to draw the distinction between the BOMs intended for sales use, those used for manufacturing and those used for sub-contracting.
The specialization of alternative BOM by site as well validation in "MRP", "MPS", "Costing" and "Manufacturing" is only possible for the alternative BOM type "production".

• Routing (field ROUNUM)

This routing code describes a particular sequence of shop floor processes for a particular product. That is, the sequence of operations and tools that are used in a particular routing.

The routing code is a product code which can be the reference for a manufactured product or a generic reference (parent routing) linked to multiple products.

• 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).

• Major version (field ROUECCMAJ)

This field indicates which major version of this routing applies. Major versions indicate that there has been a significant change to the original or previous major routing, that is, the 'form, fit or function' has changed.

• Minor version (field ROUECCMIN)

This field indicates which minor version of this routing applies. Minor versions indicate that there have been minor changes to the routing or schedule, or significant fixes applied to a specific major version.

• Lot (field LOT)

Reference of the lot to be loaded for the produced quantity.

• Order description (field MFGDES)

This is a free-format description field.

• Contract (field POHIND)

• Contract no. (field POHNUM)

Each order has its own order number. It is used to identify it.

If the order sequence number is to be manually assigned, the user must also enter an order number. Where the order number sequence assignment is automatic, a number will be assigned at the end of the creation.

When you copy a purchase order and its order date is different from the current date, a messages suggests that you recalculate the prices and discounts according to the new order date.

• Supplier (field BPSNUM)

Enter the supplier at the origin of the receipt. The selection lists specific to the intersite and intercompany orders and deliveries available for receipt are filered to those related to the entered supplier.

From the Selection icon, you can:

• select a supplier from the list of active suppliers.
• access, based on your authorizations, the supplier record, and create a new supplier if necessary.

• Project (field PJT)

• PUR (field PUU)

• Qty expected PU (field PUUPECQTY)

• PUR-STK conv. (field PUUSTUCOE)

• Management mode (field MGTCOD)

• 1st provision (field FIRRELDAT)

Start date of the first reorder in the list of orders to generate. This date corresponds to the earliest start date of the selected lines, but it can be modified.
Modifying this date can be done to shift the dates of all the orders and trigger a recalculation of all the components.

• Requested availability demand‚e (field AVADAT)

This non modifiable field displays the availability date requested at launch.

• Theoretical availability (field ANADAT)

This non modifiable field displays the theoretical availability date calculated by the system: the latest end date of the selectedlines.