Reintegration plan

• Site (field FCY)

The production site from which the work orders are to be selected.

The production site defined on the user record is displayed by default but can be amended.

• Issue start date (field WENDDATD)

Use this field to filter the orders to be loaded.

Observe loading times.

• Date fin sortie (field WENDDATF)

• Filter (field FILTMAT)

Use this field to filter the records to be tracked. Select one of the following values:

• All
• Closed
• Not closed

• Warehouse (field WRHE)

The presence of this field is subject to the activity code WRH.

It represents the movement warehouse for all order lines.

• It can be modified if it is defined as enterable in the entry transaction.
  If it is entered, it serves as a filter for stock detail line selection.
  If it is not entered, the warehouse defined by default for this type of movement in the product-site record will serve as a filter for the selection.
• It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory.
  To manage multiple warehouses on the lines the entry transaction must be set up so that it can be entered. The selection of a single product line distributed over multiple warehouses is available by clicking Enter detailed quantites from the Actions icon.
  If a single product line is distributed over multiple warehouses, the corresponding fields display the '$' character.

The warehouse entered on the line has priority over the warehouse entered in the header.

• Work order (field WMFGNUMD)

Filter for results within a range of work orders. For a single work order, enter the same work order number in the from/start Work order and to/end Work order fields.

• Operation (field WOPENUMD)

Filter for results within a range of operation sequence numbers. For a single operation sequence number, enter the same sequence number in the from/start Operation and to/end Operation fields.

• Released product (field WITMRELD)

Filter for results within a range of finished products (BOMs). For a single bill of materials (BOM), enter the same product code in the from/start Released product and to/end Released product fields.

• BOM (field WBOMNUMD)

Filter for results within a range of bills of materials (BOMs). For a single BOM, enter the same product code in the from/start BOM and to/end BOM fields.

• Code (field WBOMALTD)

Filter for results within a range of bills of materials (BOM) codes. Multiple bills of materials (BOMs) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products this includes restriction of the BOM to a specific site and to specific areas of functionality (for costing or for capacity planning).

For a single BOM code, enter the same sequence number in the from/start Code and to/end Code fields.

• Material (field WITMREFD)

Filter for results within a range of materials (components). For a single component, enter the same product in the from/start Material and to/end Material fields.

• Date (field IPTDAT)

This is the date which is used when posting the movement. It defaults to today's date but can be changed to an earlier date, if the selected date is in an open period in the accounting calendar.

You cannot enter a date later than today's date.

• Pick (field PECFLG)

Click this check box to select this line.

• Material type (field MATTYP)

• Order no. (field MFGNUM)

This field displays the work order number.

• BOM (field BOMNUM)

This product code describes what is referred to as a "Bill of Materials" or a "BOM". A BOM contains structured information for making and costing a product. It defines the components that make up a product, and given this, the cost of the product.

The BOM code matches the product code.

• Material (field ITMREF)

This field indicates the ID of the component product.

• Major version (field ECCVALMAJ)

This field indicates which version of this component (material) 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 component code defined in the Component or Material field is not version managed.

• Minor version (field ECCVALMIN)

This field indicates which minor version of this component (material) 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 component code defined in the Component or Material field is not version managed.

• Alternative (field BOMALT)

Multiple bills of materials (BOMs) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products this includes restriction of the BOM to a specific site and to specific areas of functionality (for costing or for capacity planning).

• Source (field ITMTYP)

• STK (field STU)

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.

• Consumed qty. (field USEQTY)

This field displays the used quantity and cannot be modified.

• Unit (field PCU)

It is possible to specify a packing unit by supplier.
The product can have several packing units:

• the packing units entered in the table of the product record ( Units tab). They are proposed during stock transaction entry.
  The number of packing units that can be entered is linked to the NUC activity code.
• a packing unit linked to the supplier ( Product-supplier record).
• two customer packing units ( Product-customer record). They can be used as sales units in order entry.

Only packing type units form the units of measure table can be chosen.

• Coefficient (field PCUSTUCOE)

The PAC-STK conversion factor is used to calculate the quantity in stock unit from a quantity entered in packing unit: Qty in STK = Qty in PAC * coeff .
This coefficient can be accessed if the packing unit has been entered, and has a value different from the stock unit. It can be initialized using the conversion factor table if the combination exists.

• Qty to be reintegrated (field REIQTYPCU)

Use this field to define the quantity of this component to reintegrate or return to stock.

• QTY reint STK (field REIQTY)

This field displays the quantity of this component to be reintegrated or returned to stock.

• Quantity type (field TYPQTY)

• Closed (field CLEFLG)

Use this field to specify whether the line must be closed or not ('Yes'/'No').

• Warehouse (field WRH)

The presence of this field is subject to the activity code WRH.
It defaults to the value of the warehouse specified in the header.

• This field can be modified if it is defined as available for entry at the level of the entry transaction.
  When this field is entered, it is used as a filter for stock detail line selection and cannot be modified.
  When this field is not entered, the warehouse defined by default for this type of movement in the product-site record is used as the selection filter.
• It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory and the warehouse cannot be entered either on the document lines or on the stock detail lines.
  To manage multiple warehouses on the lines, the entry must be set up at the entry transaction level. The selection of a single product line distributed over multiple warehouses is available by clicking Enter detailed quantites from the Actions icon.
  If a single product line is distributed over multiple warehouses, the corresponding fields display the '$' character.

The warehouse entered on the line has priority over the warehouse entered in the header.

• Status (field STA)

The stock status is used to define if a product is:

• A: Accepted
• Q: Pending Quality Control
• R: Rejected.
  A sub-status composed of two alphanumerical characters is used to further define the status.
  For instance:
• RD: Rejected products to be destroyed
• SR: Supplier return

The status assigned to the stock receipt is enterable. It depends partly on the product management rule (see "Management" tab in the product category to which the current product belongs) for the movement type "Miscellaneous Receipt" and for the movement code defined by the transaction if it exists. A default status can be set up on the management rule.

Moreover, if the product is managed with modifiable quality control (see the Product record, Supplier tab, Quality section), the system necessarily offers the receipt of stock with a status type Q*, but the user is free to enter the stock with the status A* or R*, according to which is authorized by the management rule.

Finally, if the product is managed with non-modifiable quality control, the system necessarily offers the entry in stock with the status type Q*, but the user cannot change the status to A* or R*.

In all cases, the list of statuses authorized by combining the management rule and the quality control management method for the product is available using the right button on the status field.

Additionally, it is possible to enter the same receipt note line using several different statuses. To do this, it is necessary to detail the line in the window entitled "Quantity detail entry": this window opens automatically if stock information is missing from the line entry. When this is not the case, it is necessary to open it using the right button on the receipt note line.
If a receipt line is distributed on several different statuses, the character $ will be displayed on the Status area of the document line.

• Locn. type (field LOCTYP)

Location types are used to codify warehouse locations according to storage characteristics such as their dimensions, authorized statuses and technical constraints.

They are associated with the products by site (or the products by warehouse when warehouses are managed): you can thus geographically group the products that share similar characteristics.
The location type of the product is suggested by default. It can be modified if it is defined as available for entry at the level of the entry transaction.

When warehouses are managed, entry of a location type is only permitted if at least one location is linked to the entered type and warehouse.

• Dstn. location (field LOC)

The storage location is automatically displayed based on the location type, if specified. Otherwise, the location taken into account is by default the location defined in the Product-warehouse, if the warehouses are managed, or else the location defined in the product-site record.
This value can later be modified.

When the warehouses are managed, only a location linked to the specified warehouse can be entered.

• Lot (field LOT)

This field indicates the lot linked to the stock movement.

• No. of sublots (field NBSLO)

This field contains the number of sub-lots concerned by the stock transaction.

• Sublot (field SLO)

Sub-lot concerned by the stock transaction.

• Ending sublot (field SLOF)

This field indicates the last sub-lot on which the stock movement is applied.

• Starting serial number (field SERNUM)

Serial number for which the movement will be carried out.

• Ending serial number (field SERNUMF)

This field contains the end serial number.

• Identifier 1 (field PALNUM)

Use this field to enter additional information, if necessary.

• Identifier 2 (field CTRNUM)

• Movement description (field MVTDES)

Free text that will be written in the stock journal for each movement of the return line. This information can also be modified in the Stock detail window.

• Date of movement (field WIPTDAT)

• Stock withdrawal (field STOCODL)

• Description (field ITMDES1)

This is the description from the product record.

• Requirement date (field RETDAT)

• field CCE1

The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.

In creation mode, if no order line has been entered and the project code is modified, analytical dimensions are reset based on the setup of the default dimensions.

In creation mode, as in modification mode, if an order line has been entered and the project code is modified, analytical dimensions are not reset.