Enterprise planning

• Site (field FCY)

The site at which work in progress is to be displayed.

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

• User (field PLANNER)

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

• From product (field ITMREFSTR)

Filter for results within a range of product codes. For a single product, enter the same product code in the From/start product and To/end product fields.

• Allergens (field ALGS)

Select the allergen code(s) to be used in the matching processing.

• From requirement end date (field ENDDATSTR)

Filter for results within a range of requirement dates. For a single requirement date, enter the same date in the From requirement end date and To requirement end date fields.

Observe loading times.

• WIP status (field WIPSTA)

This field displays the current status (work in progress) of the order. The status might be Suggested, Planned or Firm.

• Order type (field WIPTYP)

This field displays the type of order that is currently work in progress.

• Order (field WIPTYPSTA)

This field displays as a 3-character code, the type of order that is currently work in progress plus the current status of the order.

The first two characters = the order type; the third character (S (Suggested), P (Planned) or F (Firm)) = the status of the order. For example, POP means ‘Purchase Order Planned’, SOF means ‘Sales Order Firm’.

'In progress' events display a greater than ('>') symbol after the code; Intersite events display '~' after the code. For example, a firm purchase order (POF) that has been partially received is shown as: 'POF>'.

• Entry (field VCRNUM)

The document type, the document number and the document line number are used to identify the origin of the stock movement:

• Supplier receipt
• Customer delivery
• Work order
• Receipt movement

• Site (field STOFCY)

The site associated with the work in progress order.

• Product (field ITMREF)

Reference of the product for which the transaction needs to be carried out. It must be defined for the selected site.

• Start date (field STRDAT)

This field identifies the associated order date or planned production start date for the order.

• End date (field ENDDAT)

This field identifies the associated end or required completion date for the order. Where an order only has a single order date, this date is the same as the order date.

• 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 this work in progress 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 progressing a transaction should you decide to do so.

• Remaining qty. (field RMNEXTQTY)

This field displays the remaining (outstanding) quantity required to complete the order.

• STK (field STU)

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

• Requirement date (field REQDAT)

This field displays the requirement (demand) date.

• Original obj. (field OBJDAT)

The date displayed in this field is initialized to the end date of the order at the time of its creation. It serves to provide a comparison with the actual end date of the order when evaluating whether the order was completed early, as scheduled or late.

• Early/Late (field ELFLG)

The number of Early or Late days is calculated by the system depending on the initial objective date and the current date.
If the difference is positive, the order is early. If the difference is negative, the order is late.

• Message (field XMRPMES)

The system generates a replanning message based on the requirement calculation.

• MRP date (field MRPDAT)

End date of the order, calculated during an analysis with rescheduling.

• MRP qty. (field MRPQTY)

Quantity calculated during an analysis with rescheduling.

• Planned qty. (field EXTQTY)

This field contains the quantity of the product to be released, expressed in the stock unit.

• Allocated qty. (field ALLQTY)

This field displays the quantity allocated to the order line.

• Shortage (field SHTQTY)

If there is not enough stock to complete the order line, this field displays the shortage quantity.

• Assigned qty. (field MTOQTY)

The quantity entered in this field is a linking value between the sales orders and the purchase orders (or work orders).

• Total completed qty. (field CPLQTY)

This field displays the total completed quantity, including the rejected quantity, expressed in the operation unit.

• Product description (field ITMDES1)

This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line.

• Original site (field ORIFCY)

This field displays the original order site.

• Project (field PJT)

This field displays the associated project code. The content can be one of the following:

• A project code
• A project code and a project budget code
• A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'.

To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

• BP (field BPRNUM)

This field displays the code of the Business partner (customer/supplier) associated with the order.

• Priority (field PIO)

This field displays the delivery priority (Normal, Urgent, Very urgent) for the order.

• Product source (field FMI)

This field indicates how the goods required for the order line will be managed.

• Normal. As a normal order, from stock.
• With a back-to-back order:

Direct back-to-back order. A purchase order is generated. The supplier will deliver the product directly to the customer.

Receipt direct order. A purchase order is generated. The purchasing department receives the goods and delivers the product to the customer.

Work order. A work order is generated. The product will be manufactured specifically for the customer. The customer code will be copied to the work order release line.

• Source type (field VCRTYPORI)

This field identifies the reason for the order.

• Original document (field VCRNUMORI)

This field identifies the number of the source document or order.

• Origin line (field VCRLINORI)

This field identifies the associated line on the source document or order.

• Source seq. (field VCRSEQORI)

This field identifies the sequence number of this component in the source parent product.

• Source product (field ITMREFORI)

This field displays the original product code. 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.

• BOM code (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).

• Operation (field BOMOPE)

The components can be linked to a particular operations in a production route, according to the manufacturing requirements.

• Source (field ORI)

This field identifies the origin of the order.

• Planner/Appro. (field PLANNER2)

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

• Buyer (field BUY)

• Optimized (field OPTFLG)

This field indicates if the order has been optimized in the scheduling.

• Net price (field NETPRI)

This field displays the Net price for this order. Select the order from the Actions icon to view the order details.

• Currency (field CUR)

This field corresponds to the currency of the order, delivery or invoice.

• WO description (field MFGDES)

Non modifiable field displaying the description of the transaction.

• Document units (field UOM)

This field displays the unit of measure (volume or mass) of the product on the associated order.

• Allergens (field ALGITM)

This field is subject to the FOA - Food allergens activity code. It displays the allergen associated with this product. The product category determines the options available.

• If this is a manufactured product, you cannot edit this field because it displays the allergen codes based on the allergen rollup function performed for the parent product. The rollup explodes the BOM/recipe and collects all unique allergen codes. This can be useful if there are concerns about the results, or if the information is up to date.
• If this product is a purchased product, you can edit this field based on the allergen selection function. You can select multiple items per product.
  

• Weight (field LINWEI)

This field represents the total weight multiplied by the quantity ordered.

• Weight unit (field LINWEU)

The weight unit.

• Volume (field LINVOL)

This field represents the total quantity ordered multiplied by the total volume.

• Volume unit (field LINVOU)

Code of the unit in which the package volume is given.
This unit has already been defined in the Units table.

• Cost (field LINAMT)

This field displays the order line amount excluding tax, expressed in the transaction currency.

• Currency (field LINAMTCUR)

This field displays the transaction currency of the order line.

• Entry type (field VCRTYP)

This field displays the reason for the order or the resulting order type.

• STK qty. being deliv. (field SHIQTYSTU)

This field displays the shipped quantity expressed in the stock unit.

• Order site (field PSHFCY)

Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.).
This field is mandatory. It is initialized by default by the purchase site associated with your function profile.
You can modify this code by selecting a code from the list of authorized sites.

• Entry type (field XVCRTYP)

This field displays the reason for the order or the resulting order type.

• Entry (field VCRNUM)

The document type, the document number and the document line number are used to identify the origin of the stock movement:

• Supplier receipt
• Customer delivery
• Work order
• Receipt movement

• field VCRLIN

This field identifies the associated line on the source document or order.

• BP (field BPRNUM)

This field displays the code of the Business partner (customer/supplier) associated with the order.

• Product source (field FMI)

This field indicates how the goods required for the order line will be managed.

• Normal. As a normal order, from stock.
• With a back-to-back order:

Direct back-to-back order. A purchase order is generated. The supplier will deliver the product directly to the customer.

Receipt direct order. A purchase order is generated. The purchasing department receives the goods and delivers the product to the customer.

Work order. A work order is generated. The product will be manufactured specifically for the customer. The customer code will be copied to the work order release line.

• Receiving site (field STOFCY)

This field displays the site where the goods must be delivered by the supplier. It is initialized by the order site if it is also a storage site.
This receipt site must belong to the same legal company as the requesting site for a purchase order or the order site in case of an order.
In the case of a purchase request or an order for a product managed in stock:

• the receipt site must be a warehouse,
• the product reference must be defined for this receiving site.

• Product (field ITMREF)

Reference of the product for which the transaction needs to be carried out. It must be defined for the selected site.

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

• Requested date (field EXTRCPDAT)

Requested receipt date.
A control is applied to this date based on the unavailability periods of the receipt site. When the site is unavailable on this date, a message is displayed and you need to enter another date.

This date is used to initialize the theoretical order date.

• PUR quantity (field QTYPUU)

Specify the quantity of the product to be ordered in the purchasing unit.

• field PUU

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• STK quantity (field QTYSTU)

Specify the quantity of the product to be ordered in the stock unit.

• field STU

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

• Supplier (field BPSNUM)

Code identifying the supplier.

For suggestions in the results table generated for purchase order suggestions and subcontract order suggestions by an MRP processing run (FUNMRP/FUNMRPG), MRP will have used a product-supplier selection hierarchy to determine the preferred (default) supplier by site. You can change this default supplier manually. Where MRP failed to nominate a supplier you must select the supplier manually.

When selecting a supplier manually by clicking either the selection icon, or the Actions icon in the Supplier field (BPSNUM):

• If theITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) is set toMandatory, you can only select from the list of suppliers defined for the product-site record that are not currently "blocked".
  A Product-site suppliers action is available from the Actions icon; theProduct suppliers actionis not available for selection.
• If the ITMBPS - Supplier referencing parameter (ACH chapter, REF group) is set to Mandatory, you can only select from the list of suppliers defined for the product record that are not currently "blocked".
• If both ITMBPSFCY and ITMBPS are set to Optional or Not used, you can select from the complete list of suppliers in the Suppliers table (BPSUPPLIER).

Before you can transfer a purchase order suggestion to a firm purchase order you must allocate a supplier manually if the MRP processing run fails to allocate the default supplier.

• Project (field PJT)

This field displays the associated project code. The content can be one of the following:

• A project code
• A project code and a project budget code
• A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'.

To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

• Location reference (field USEPLC)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Total cost (field TOTCOST)

This field represents the cost multiplied by the ordered quantity.

• Maximum order (field ORDMAXAMT)

This field displays the maximum order amount defined for the supplier in the folder currency. This amount is not stored and does not prevent you from saving.

The field identifies the total purchase order amount needed to receive free freight. It is a display-only field and does not restrict POS creation.

• field TOTCUR

This field corresponds to the currency of the order, delivery or invoice.

• Container (field TCTRNUM)

Select the container that you want to use. It can simply be a "freight container" type.
The choice of the container determines the maximum weight and volume you can ship.

• No. of containers (field TCTRQTY)

Use this field to specify how many freight containers you want to use.

• Weight (field WEICAP)

This field displays the total weight capacity of the selected freight container(s). If a container is not selected, you can enter a weight without having to manage containers.

• Volume (field VOLCAP)

This field displays the total volume capacity of the selected freight container(s). If a container is not selected, you can enter a volume without having to manage containers.

• Weight (field WEITOT)

This field represents the total weight multiplied by the quantity ordered.

• Volume (field VOLTOT)

This field represents the total quantity ordered multiplied by the total volume.

• Weight (field WEIAVL)

This is field displays the available weight for a container when the total weight of selected lines in the workbench do not equal zero.

• field TCTRWEU

The weight unit.

• Volume (field VOLAVL)

This is field displays the available volume for a container when the total volume of selected lines in the workbench do not equal zero.

• field TCTRVOU

This non-modifiable field displays the volume unit defined for the freight container.

• field SELIND

Select this check box to select this line.

• Contract no. (field POHNUM)

• Supplier (field BPSNUM2)

• Validity start date (field STRDAT)

This field identifies the associated order date or planned production start date for the order.

• Validity end date (field ENDDAT)

This field identifies the associated end or required completion date for the order. Where an order only has a single order date, this date is the same as the order date.

• Purchase unit (field PUU2)

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• Location reference (field USEPLC2)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Purchase site (field PURFCY)

• Order site (field PSHFCY)

Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.).
This field is mandatory. It is initialized by default by the purchase site associated with your function profile.
You can modify this code by selecting a code from the list of authorized sites.

• Entry type (field XVCRTYP)

This field displays the reason for the order or the resulting order type.

• Entry (field VCRNUM)

The document type, the document number and the document line number are used to identify the origin of the stock movement:

• Supplier receipt
• Customer delivery
• Work order
• Receipt movement

• field VCRLIN

This field identifies the associated line on the source document or order.

• BP (field BPRNUM)

This field displays the code of the Business partner (customer/supplier) associated with the order.

• Product source (field FMI)

This field indicates how the goods required for the order line will be managed.

• Normal. As a normal order, from stock.
• With a back-to-back order:

Direct back-to-back order. A purchase order is generated. The supplier will deliver the product directly to the customer.

Receipt direct order. A purchase order is generated. The purchasing department receives the goods and delivers the product to the customer.

Work order. A work order is generated. The product will be manufactured specifically for the customer. The customer code will be copied to the work order release line.

• Receiving site (field STOFCY)

This field displays the site where the goods must be delivered by the supplier. It is initialized by the order site if it is also a storage site.
This receipt site must belong to the same legal company as the requesting site for a purchase order or the order site in case of an order.
In the case of a purchase request or an order for a product managed in stock:

• the receipt site must be a warehouse,
• the product reference must be defined for this receiving site.

• Product (field ITMREF)

Reference of the product for which the transaction needs to be carried out. It must be defined for the selected site.

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

• Requested date (field EXTRCPDAT)

Requested receipt date.
A control is applied to this date based on the unavailability periods of the receipt site. When the site is unavailable on this date, a message is displayed and you need to enter another date.

This date is used to initialize the theoretical order date.

• PUR quantity (field QTYPUU)

Specify the quantity of the product to be ordered in the purchasing unit.

• field PUU

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• STK quantity (field QTYSTU)

Specify the quantity of the product to be ordered in the stock unit.

• field STU

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

• Supplier (field BPSNUM)

Code identifying the supplier.

For suggestions in the results table generated for purchase order suggestions and subcontract order suggestions by an MRP processing run (FUNMRP/FUNMRPG), MRP will have used a product-supplier selection hierarchy to determine the preferred (default) supplier by site. You can change this default supplier manually. Where MRP failed to nominate a supplier you must select the supplier manually.

When selecting a supplier manually by clicking either the selection icon, or the Actions icon in the Supplier field (BPSNUM):

• If theITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) is set toMandatory, you can only select from the list of suppliers defined for the product-site record that are not currently "blocked".
  A Product-site suppliers action is available from the Actions icon; theProduct suppliers actionis not available for selection.
• If the ITMBPS - Supplier referencing parameter (ACH chapter, REF group) is set to Mandatory, you can only select from the list of suppliers defined for the product record that are not currently "blocked".
• If both ITMBPSFCY and ITMBPS are set to Optional or Not used, you can select from the complete list of suppliers in the Suppliers table (BPSUPPLIER).

Before you can transfer a purchase order suggestion to a firm purchase order you must allocate a supplier manually if the MRP processing run fails to allocate the default supplier.

• Project (field PJT)

This field displays the associated project code. The content can be one of the following:

• A project code
• A project code and a project budget code
• A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'.

To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

• Location reference (field USEPLC)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Total cost (field TOTCOST)

This field represents the cost multiplied by the ordered quantity.

• Maximum order (field ORDMAXAMT)

This field displays the maximum order amount defined for the supplier in the folder currency. This amount is not stored and does not prevent you from saving.

The field identifies the total purchase order amount needed to receive free freight. It is a display-only field and does not restrict POS creation.

• field TOTCUR

This field corresponds to the currency of the order, delivery or invoice.

• Container (field TCTRNUM)

Select the container that you want to use. It can simply be a "freight container" type.
The choice of the container determines the maximum weight and volume you can ship.

• No. of containers (field TCTRQTY)

Use this field to specify how many freight containers you want to use.

• Weight (field WEICAP)

This field displays the total weight capacity of the selected freight container(s). If a container is not selected, you can enter a weight without having to manage containers.

• Volume (field VOLCAP)

This field displays the total volume capacity of the selected freight container(s). If a container is not selected, you can enter a volume without having to manage containers.

• Weight (field WEITOT)

This field represents the total weight multiplied by the quantity ordered.

• Volume (field VOLTOT)

This field represents the total quantity ordered multiplied by the total volume.

• Weight (field WEIAVL)

This is field displays the available weight for a container when the total weight of selected lines in the workbench do not equal zero.

• field TCTRWEU

The weight unit.

• Volume (field VOLAVL)

This is field displays the available volume for a container when the total volume of selected lines in the workbench do not equal zero.

• field TCTRVOU

This non-modifiable field displays the volume unit defined for the freight container.

• field SELIND

Select this check box to select this line.

• Contract no. (field POHNUM)

• Supplier (field BPSNUM2)

• Validity start date (field STRDAT)

This field identifies the associated order date or planned production start date for the order.

• Validity end date (field ENDDAT)

This field identifies the associated end or required completion date for the order. Where an order only has a single order date, this date is the same as the order date.

• Purchase unit (field PUU2)

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• Location reference (field USEPLC2)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Purchase site (field PURFCY)

• Original site (field ORIFCY)

This field displays the original order site.

• Type (field XWIPTYP)

This field displays the type of order that is currently work in progress.

• Order status (field XWIPSTA)

This field displays the current status (work in progress) of the order. The status might be Suggested, Planned or Firm.

• field XMESS

The system generates a replanning message based on the requirement calculation.

• Number (field VCRNUM)

The document type, the document number and the document line number are used to identify the origin of the stock movement:

• Supplier receipt
• Customer delivery
• Work order
• Receipt movement

• field VCRLIN

This field identifies the associated line on the source document or order.

• Entry type (field XVCRTYPORI)

This field identifies the reason for the order.

• Entry (field VCRNUMORI)

This field identifies the number of the source document or order.

• field VCRLINORI

This field identifies the associated line on the source document or order.

• BP (field BPRNUM)

This field displays the code of the Business partner (customer/supplier) associated with the order.

• field BPRDES

Business Partner company name.

• Storage site (field STOFCY)

The site associated with the work in progress order.

• Shrinkage % (field SHR)

The loss percentage corresponds to the production or storage loss.

The production loss corresponds to the totaled loss generated for each routing operation.

This percentage is taken into account in the material requirements planning and in the work order management. it is used to calculate the quantity to be reordered to obtain the quantity to cover the requirement.

• Product (field ITMREF)

Reference of the product for which the transaction needs to be carried out. It must be defined for the selected site.

• Description (field ITMDES1)

This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line.

• Major version (field ECCVALMAJ)

Use this field to indicate which major 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the product code defined in the Product field is not version managed.

• Minor version (field ECCVALMIN)

Use this field to indicate 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the product code defined in the Product field is not version managed.

• Lot (field LOT)

This field indicates the lot linked to the stock movement.

• Lead-time (+QC) (field AVAOFS)

Number of days corresponding to:

• the reorder lead-time for a purchased product,
• To the manufacturing lead-time for a finished or semi-finished product.

It is in general fixed for a given lot size, and is used to calculate the start date for the MRP suggestions.

• Planned quantity (field EXTQTY2)

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

• field STU2

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

• Start date (field STRDAT2)

This field identifies the planned or actual production start date of the work order.

• field LABEL

Use this field to define the scheduling method for this work order. Select one of the following:

• Backward. With 'backward', or upstream scheduling the system calculates the production start date (field Start date) from the end or required completion date (field End date).
• Forward. With 'forward', or downstream scheduling the system calculates the required completion date (field End date) from the defined production start date (field Start date).

These calculations rely on the production lead time, reduction factor and economic quantity defined on the product-site record.

The transaction you select determines if this field is available for entry.

• End date (field ENDDAT2)

This field identifies the end or required completion date for this work order.

• BOM code (field BOMALT2)

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

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

• WO description (field MFGDES)

Non modifiable field displaying the description of the transaction.

• Project (field PJT)

This field displays the associated project code. The content can be one of the following:

• A project code
• A project code and a project budget code
• A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'.

To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

• Initial objective (field OBJDAT)

The date displayed in this field is initialized to the end date of the order at the time of its creation. It serves to provide a comparison with the actual end date of the order when evaluating whether the order was completed early, as scheduled or late.

• Allocation status (field XALLSTA)

The Allocation (materials), Scheduling and Status fields display a status for this work order. These fields are updated automatically by the system.

The current status, or progress of this work order is displayed in the Scheduling and Status fields. Selected combinations to note are as follows:

• 'Not scheduled' and 'Pending'. The work order is awaiting scheduling. It cannot be submitted for scheduling in Production Scheduler, Sage X3 Web Scheduling or in any web scheduling solution developed by an ISV (independent software vendor).
• 'Scheduled' and 'Pending'. The work order is scheduled but has not actually been submitted for scheduling.
• 'Scheduled' and 'Being optimized'. The work order is being scheduled (has been submitted for scheduling). At these statuses you cannot modify the work order.
• 'Optimized' and 'Pending'. The work order operations have been optimized by the scheduler.

The work order allocation values are defined in Local menu 336.
The scheduling status values are defined in Local menu 335.
The work order status values are defined in Local menu 339.

 For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

 Production Scheduler only applies to on-premises instances of Sage X3. The Generic finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.

• Scheduling status (field XSCDFLG)

The Allocation (materials), Scheduling and Status fields display a status for this work order. These fields are updated automatically by the system.

The current status, or progress of this work order is displayed in the Scheduling and Status fields. Selected combinations to note are as follows:

• 'Not scheduled' and 'Pending'. The work order is awaiting scheduling. It cannot be submitted for scheduling in Production Scheduler, Sage X3 Web Scheduling or in any web scheduling solution developed by an ISV (independent software vendor).
• 'Scheduled' and 'Pending'. The work order is scheduled but has not actually been submitted for scheduling.
• 'Scheduled' and 'Being optimized'. The work order is being scheduled (has been submitted for scheduling). At these statuses you cannot modify the work order.
• 'Optimized' and 'Pending'. The work order operations have been optimized by the scheduler.

The work order allocation values are defined in Local menu 336.
The scheduling status values are defined in Local menu 335.
The work order status values are defined in Local menu 339.

 For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

 Production Scheduler only applies to on-premises instances of Sage X3. The Generic finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.

• Advance/Delay (field ELFLG)

The number of Early or Late days is calculated by the system depending on the initial objective date and the current date.
If the difference is positive, the order is early. If the difference is negative, the order is late.

• field JOUR1

The purchasing leads are always expressed in calendar days.

• Status (field XMFGTRKFLG)

The Allocation (materials), Scheduling and Status fields display a status for this work order. These fields are updated automatically by the system.

The current status, or progress of this work order is displayed in the Scheduling and Status fields. Selected combinations to note are as follows:

• 'Not scheduled' and 'Pending'. The work order is awaiting scheduling. It cannot be submitted for scheduling in Production Scheduler, Sage X3 Web Scheduling or in any web scheduling solution developed by an ISV (independent software vendor).
• 'Scheduled' and 'Pending'. The work order is scheduled but has not actually been submitted for scheduling.
• 'Scheduled' and 'Being optimized'. The work order is being scheduled (has been submitted for scheduling). At these statuses you cannot modify the work order.
• 'Optimized' and 'Pending'. The work order operations have been optimized by the scheduler.

The work order allocation values are defined in Local menu 336.
The scheduling status values are defined in Local menu 335.
The work order status values are defined in Local menu 339.

 For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

 Production Scheduler only applies to on-premises instances of Sage X3. The Generic finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.

• Order site (field PSHFCY)

Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.).
This field is mandatory. It is initialized by default by the purchase site associated with your function profile.
You can modify this code by selecting a code from the list of authorized sites.

• Entry type (field XVCRTYP)

This field displays the reason for the order or the resulting order type.

• Entry (field VCRNUM)

The document type, the document number and the document line number are used to identify the origin of the stock movement:

• Supplier receipt
• Customer delivery
• Work order
• Receipt movement

• field VCRLIN

This field identifies the associated line on the source document or order.

• BP (field BPRNUM)

This field displays the code of the Business partner (customer/supplier) associated with the order.

• Product source (field FMI)

This field indicates how the goods required for the order line will be managed.

• Normal. As a normal order, from stock.
• With a back-to-back order:

Direct back-to-back order. A purchase order is generated. The supplier will deliver the product directly to the customer.

Receipt direct order. A purchase order is generated. The purchasing department receives the goods and delivers the product to the customer.

Work order. A work order is generated. The product will be manufactured specifically for the customer. The customer code will be copied to the work order release line.

• Receiving site (field STOFCY)

This field displays the site where the goods must be delivered by the supplier. It is initialized by the order site if it is also a storage site.
This receipt site must belong to the same legal company as the requesting site for a purchase order or the order site in case of an order.
In the case of a purchase request or an order for a product managed in stock:

• the receipt site must be a warehouse,
• the product reference must be defined for this receiving site.

• Product (field ITMREF)

Reference of the product for which the transaction needs to be carried out. It must be defined for the selected site.

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

• Requested date (field EXTRCPDAT)

Requested receipt date.
A control is applied to this date based on the unavailability periods of the receipt site. When the site is unavailable on this date, a message is displayed and you need to enter another date.

This date is used to initialize the theoretical order date.

• PUR quantity (field QTYPUU)

Specify the quantity of the product to be ordered in the purchasing unit.

• field PUU

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• STK quantity (field QTYSTU)

Specify the quantity of the product to be ordered in the stock unit.

• field STU

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

• Supplier (field BPSNUM)

Code identifying the supplier.

For suggestions in the results table generated for purchase order suggestions and subcontract order suggestions by an MRP processing run (FUNMRP/FUNMRPG), MRP will have used a product-supplier selection hierarchy to determine the preferred (default) supplier by site. You can change this default supplier manually. Where MRP failed to nominate a supplier you must select the supplier manually.

When selecting a supplier manually by clicking either the selection icon, or the Actions icon in the Supplier field (BPSNUM):

• If theITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) is set toMandatory, you can only select from the list of suppliers defined for the product-site record that are not currently "blocked".
  A Product-site suppliers action is available from the Actions icon; theProduct suppliers actionis not available for selection.
• If the ITMBPS - Supplier referencing parameter (ACH chapter, REF group) is set to Mandatory, you can only select from the list of suppliers defined for the product record that are not currently "blocked".
• If both ITMBPSFCY and ITMBPS are set to Optional or Not used, you can select from the complete list of suppliers in the Suppliers table (BPSUPPLIER).

Before you can transfer a purchase order suggestion to a firm purchase order you must allocate a supplier manually if the MRP processing run fails to allocate the default supplier.

• Project (field PJT)

This field displays the associated project code. The content can be one of the following:

• A project code
• A project code and a project budget code
• A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'.

To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

• Location reference (field USEPLC)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Total cost (field TOTCOST)

This field represents the cost multiplied by the ordered quantity.

• Maximum order (field ORDMAXAMT)

This field displays the maximum order amount defined for the supplier in the folder currency. This amount is not stored and does not prevent you from saving.

The field identifies the total purchase order amount needed to receive free freight. It is a display-only field and does not restrict POS creation.

• field TOTCUR

This field corresponds to the currency of the order, delivery or invoice.

• Container (field TCTRNUM)

Select the container that you want to use. It can simply be a "freight container" type.
The choice of the container determines the maximum weight and volume you can ship.

• No. of containers (field TCTRQTY)

Use this field to specify how many freight containers you want to use.

• Weight (field WEICAP)

This field displays the total weight capacity of the selected freight container(s). If a container is not selected, you can enter a weight without having to manage containers.

• Volume (field VOLCAP)

This field displays the total volume capacity of the selected freight container(s). If a container is not selected, you can enter a volume without having to manage containers.

• Weight (field WEITOT)

This field represents the total weight multiplied by the quantity ordered.

• Volume (field VOLTOT)

This field represents the total quantity ordered multiplied by the total volume.

• Weight (field WEIAVL)

This is field displays the available weight for a container when the total weight of selected lines in the workbench do not equal zero.

• field TCTRWEU

The weight unit.

• Volume (field VOLAVL)

This is field displays the available volume for a container when the total volume of selected lines in the workbench do not equal zero.

• field TCTRVOU

This non-modifiable field displays the volume unit defined for the freight container.

• field SELIND

Select this check box to select this line.

• Contract no. (field POHNUM)

• Supplier (field BPSNUM2)

• Validity start date (field STRDAT)

This field identifies the associated order date or planned production start date for the order.

• Validity end date (field ENDDAT)

This field identifies the associated end or required completion date for the order. Where an order only has a single order date, this date is the same as the order date.

• Purchase unit (field PUU2)

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• Location reference (field USEPLC2)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Purchase site (field PURFCY)