Purchasing >  Supply >  Enterprise planning  

Display all Hide all

Use this function as a decision-support tool. It provides you with a view of work in progress events based on actual demand. Events can include internal and external orders (customer orders, supplier orders, subcontract orders, transfer orders, work orders), requests, transfers, material requirements and project demand. You produce the forecasts for one site or all sites over a given period directly from the Orders table.

You can can progress selected events directly from the workbench.

The Enterprise planning workbench is an invaluable tool for material buyers and production planners.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

This function is customized to the needs of your organization and your processes. The transaction you select determines the way in which you enter information, and information is displayed and printed.

If only one transaction has been set up you are not offered a choice, the default entry screen is displayed.

Entry screen

Presentation

Filters

Use this section to filter or select events associated with one or a range of products:

  • Site. This field defaults to the production site associated with your user code. Entry of a site code is optional.
  • User. This field defaults to your user code. Selecting a product not directly managed by you is linked to the GPLNFLT - Planner/buyer filter parameter (STO chapter, SCH group).

Start-end range

A number of ranges are displayed.

  • To include all applicable products, leave all the fields blank.
  • To include only selected products, type in the required ranges. Leave the first field blank to include the lowest value or the second field blank to include the highest value. The default requirement end date is obtained from the GPLNHOR - Default planning horizon (chapter STO, group SCH) parameter.

You can restrict the events selected to specific allergens associated with the products.

You can use the Criteria action to enhance the selection criteria applied.

Enterprise planning grid

The columns displayed in the Enterprise planning grid or table and the order in which they are displayed is determined by the selected entry transaction.

Close

 

Fields

The following fields are present on this tab :

Filters

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.

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

Start - end range

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.

Grid WO to process

  • 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

The site associated with the work in progress order.

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.

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.

This field displays the original order site.

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 value 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 budget structure or the project operational (task) 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).

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.

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.

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

Buyer/Planner
Operator in charge of reordering the product for the considered site.
This code is referenced in several scripts, such as the buyer plan, the supplier order entry, etc.

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

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.

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

  • Allergens (field ALGITM)

This field displays the allergen associated with this product. The product category determines the option that appears. This field is available only if the FOA activity code is active.

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

The weight unit.

  • Volume (field LINVOL)

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

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.

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.

Close

 

Action icon

Popup view

Click Popup view from the Actions icon to view the information for this event using the standard screen display mode.

Plan/Initiate or Plan/Order

Click Plan/Initiate or Plan/Order (as available) from the Actions icon to plan and create the request or order.

If you click Plan/Initiate for a work order suggestion (WOS), the system automatically proposes the routing to be used. If the proposed routing is version-managed, the system selects the routing version that is valid on the scheduled start date of the work order. You can type in or select a different version of the product to be released (BOM) and the associated routing, if required. The version you choose must have an Available to use status on the proposed production start date of the work order. If your selected routing version is not consistent with the calculated work order start date, the error "Routing invalid on the date indicated <date>" is written to the System log. The work order is created with a Planned or Firm status, however it is not scheduled. This is because there is an inconsistency between the work order start date and your selected routing version.

Modify, Modify/Initiate or Modify/Order

Click Modify (if available) from the Actions icon to modify the order details.

Click Modify/Initiate (if available) to modify the order details and release the order.

Click Modify/Order (if available) to modify the order details and create the order.

Planning workbench

Click Planning workbench from the Actions icon to view the projected stock movements for the selected product.

Grouping

Click Grouping from the Actions icon to view suggestions and demands for the selected product.

Project, Request or Order no.

Click the purchase request to display more details.

Work order

Click the work order to display more details.

Subcontract order

Click the subcontract order to display more details.

Products by supplier

Click Products by supplier from the Actions icon for a purchase order to view other products assigned to the same supplier. The list of products includes any product with the supplier that is not already displayed in the workbench as well as any records in the ORDERS table that did not fall within the original selection criteria (for example, End date).

The amounts entered in the On order field are written as a Purchase order suggestion (POS) to the ORDERS table and immediately display when returning to the Enterprise planning or Grouping workbench. This includes records that do not meet the original selection criteria. You can also select and specify quantities to add to the existing workbench suggestions.

Stock

Click Stock from the Actions icon to view one of the following:

Allocate

Click Allocate from the Actions icon to allocate the selected component. Global allocation does not specify the details of the stock (location, lot) to be consumed. Global allocation simply increments the reserved stock for the component and decreases its available stock. At the time of the effective consumption of the materials, the system transforms the global allocation into a detailed allocation.

Manual allocations

Click Manual allocations from the Actions icon to manually allocate the selected component. A screen is displayed summarizing all the lines from which allocations (lot, sublot, version, serial number, location) can be selected.

If the component is already allocated, the allocated lines are displayed. You can modify this selection or delete the allocations by clicking the Clear action.

If the material has not been allocated, or you have deleted the allocations, the system can perform the allocation for you. Click the Proposal action. You can specify a preferred lot, location or status. The system displays the lines selected for allocation. You can modify these selections if required.

 You can only allocate individual serial numbers if the Serial number management flag on the component record is set to 'Received/Issued'. If the Serial number management flag on the component record is set to 'Global Received/Issued' you can only select the lot from which the serial numbers are to be allocated.

 Requesting a global allocation of all components does not affect manually allocated components.

Scheduling

Click Scheduling from the Actions icon for a production order to schedule the order.

A target completion date (field Initial objective) is displayed. This field is initialized by the required completion date defined in the field End date on the order. This date is for information only. Although it can be amended it does not affect the scheduling calculations. The number of days to or since the target completion date is also displayed (field Advance/delay). This figure is calculated at the time of display.

The scheduling process schedules the operations in the defined routing, and if specified, routing version. It also calculates the production start date if backward (upstream) scheduling has been defined.

 The routing version, if defined, must be at status 'Available to use' on the production start date, if scheduling changes the production start date this might cause an inconsistency with the selected version. The Scheduling flag will remain at status 'Not scheduled'. You must either change the routing version or reschedule this work order before you can continue. Please refer to the field Major version on the routing for further information.

Once the scheduling information is correctly set you can use the planning workbench to reschedule, deschedule or mark specific operations to be scheduled. Scheduling sets the start and end dates for the operations according to their productive and non-productive setting and operation times.

The sequence of operations follows the defined numbering sequence.

A Graph action is available when this work order is scheduled to view the operation details in a graphical format.

A Load action is available to view the work center load in a graphical format.

Available Stock

Click Available stock from the Actions icon to project the available and available to promise stock for this product at this site in periods of days, weeks or months.

Associated orders zoom

Click Associated orders zoom from the Actions icon for a production or subcontract order to view the material requirements, or in-progress subcontract requirements, associated with the selected product. By selecting a line, you can view the projected stock movements for the selected product.

Component availability by date

Click Component availability by date from the Actions icon for a production order to display an overview of projected stock movements for the components of the selected parent product (BOM). If there is a gap between available to promise stock and required stock the system suggests the first date of availability of the component. The following actions are available from the Actions icon on the component lines:

  • Projected stock. Click this action to view the projected stock movements for a specific component at one or all sites.
  • Available stock. Click this action to project the available and available to promise stock for a specific component at this site in periods of days, weeks or months.
Component availability

Click Component availability from the Actions icon for a production order to display an overview of projected stock movements for the components of the selected parent product (BOM). You can then click Projected stock from the Actions icon to view the projected stock movements for a specific component at one or all sites.

Shipments

Click Shipments from the Actions icon for a purchase order to view a summary of the expected shipments, including the expected receipt dates and quantities, for the selected product.

 

Close

 

Processing events (in summary)

 The type of order determines the options available from the Actions icon.

Requirement-type (demand) orders: SO Sales order, TP Intersite (Transfer) requirement, MW Material requirement, or MS Subcontracted material requirement.

The last modified or created order line is highlighted in the grid.

Order type

Actions icon

Description of the suggested action

Resulting order

All types
First 2 characters=order type;
3rd character=order status (S (Suggested), P (Planned) or F (Firm))

Modify

 

Modify the suggestion, request, order.

No change to order type:
xxS remains as xxS
xxP remains as xxP
xxF remains as xxF

Purchased

Request

 

Coverage of a requirement with a purchase request

POP

Purchase order planned (or purchase request)

Purchased

Order

Coverage of a requirement with a firm purchase order via a contract or not

POF

Purchased

Intersite

Coverage of a requirement with a planned or firm intersite order request

TRP
TRF

Manufactured

Plan

 

Coverage of a requirement with a planned production (work) order

(If the user is only authorized by the transaction to handle planned orders)

WOP

Manufactured

Release

Coverage of a requirement with a firm production (work) order

(If the user is only authorized by the transaction to handle planned orders)

WOF

Manufactured

Plan/Initiate

Coverage of the requirement with a planned or firm work order

(If the user is authorized by the transaction to handle planned and firm orders)

WOP
WOF

Subcontracted

Plan

 

Coverage of a requirement with a planned subcontract order

Coverage of a requirement with a planned subcontracted service

(If the user is only authorized by the transaction to handle planned orders)

EOP



SCP

Subcontracted

Release

Coverage of a requirement with a firm subcontract order

Coverage of a requirement with a firm subcontracted service

(If the user is only authorized by the transaction to handle planned orders)

EOF


SCF

Subcontracted

Plan/Initiate

Coverage of a requirement with a planned or firm subcontract order

Coverage of a requirement with a planned or firm subcontracted service

(If the user is authorized by the transaction to handle planned and firm orders)

EOP
EOF


SCP
SCF

Actioning Purchase orders

Fields

The following fields are included in this window :

Block number 1

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.

Block number 2

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

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.

Block number 3

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

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.

Request/order

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

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

  • purchase unit defined at the level of the unit product record,
  • purchase unit linked to the supplier.

The purchase unit cannot be modified.

This unit is used as the default value when entering an order, subcontract order or receipt, with the supplier unit suggested in priority when the product-supplier record exists.
The purchase units are accessible depending on the type of category.
SEEINFO Upon invoicing of a product, the product PUR is used.

  • STK quantity (field QTYSTU)

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

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

Block number 5

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.

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 value 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 budget structure or the project operational (task) 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.

Cost

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

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

Container capacity

Select the Freight container you wish to use. The choice of the container determines the maximum weight and volume you can carry.

  • No. of containers (field TCTRQTY)

Use this field to specify how many containers you will use.

  • Weight (field WEICAP)

This field displays the total weight capacity for the selected container or containers. 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 for the selected container or containers. If a container is not selected, you can enter a volume without having to manage containers.

Selected

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

Available

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

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.

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

Grid

  • field SELIND

Click this check box to select this line.

  • Contract no. (field POHNUM)

 

 

  • Validity start date (field STRDAT)

 

  • Validity end date (field ENDDAT)

 

 

  • Location reference (field USEPLC2)

 

 

Close



You can modify the requested receipt date, as well as the quantity.

The main supplier is proposed by default, but you can modify the supplier.

If there are order contracts for this product, the list of these contracts is displayed. You need to select a contract to place an order using an order contract.

If a signature circuit has been set up, the signature circuit is applied when you work on a PO or a POF. When viewing a specific order, click Signers to view signature details.

Actioning Sales orders

Fields

The following fields are included in this window :

Block number 1

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.

Block number 2

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

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.

Block number 3

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

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.

Request/order

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

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

  • purchase unit defined at the level of the unit product record,
  • purchase unit linked to the supplier.

The purchase unit cannot be modified.

This unit is used as the default value when entering an order, subcontract order or receipt, with the supplier unit suggested in priority when the product-supplier record exists.
The purchase units are accessible depending on the type of category.
SEEINFO Upon invoicing of a product, the product PUR is used.

  • STK quantity (field QTYSTU)

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

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

Block number 5

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.

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 value 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 budget structure or the project operational (task) 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.

Cost

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

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

Container capacity

Select the Freight container you wish to use. The choice of the container determines the maximum weight and volume you can carry.

  • No. of containers (field TCTRQTY)

Use this field to specify how many containers you will use.

  • Weight (field WEICAP)

This field displays the total weight capacity for the selected container or containers. 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 for the selected container or containers. If a container is not selected, you can enter a volume without having to manage containers.

Selected

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

Available

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

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.

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

Grid

  • field SELIND

Click this check box to select this line.

  • Contract no. (field POHNUM)

 

 

  • Validity start date (field STRDAT)

 

  • Validity end date (field ENDDAT)

 

 

  • Location reference (field USEPLC2)

 

 

Close



The main supplier is proposed by default, but you can modify the supplier.

If there are order contracts for this product, the list of these contracts is displayed. You need to select a contract to place an order using an order contract.

Actioning Work orders

Fields

The following fields are included in this window :

Identification

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.

Source

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

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

  • field BPRDES

Business partner name.

Block number 3

The site associated with the work in progress order.

  • Loss % (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.

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.

Planning

  • Planned quantity (field EXTQTY2)

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

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.

Process

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

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 (mother routing) linked to multiple products.

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.

Block number 7

  • WO description (field MFGDES)

Non modifiable field displaying the description of the transaction.

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 value 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 budget structure or the project operational (task) 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).

Progress

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

Close



An entry transaction defined specifically for automatic generation (field Transaction reserved for automatic generation is selected) must be specified in parameter MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS).

Order release (via the Initate then the Release action) from this function uses the entry transaction defined for automatic order generation (field Transaction reserved for automatic generation is selected) specified in parameter MFGMTSNUM - Automatic WO transaction (chapter STO, group MIS). The scheduling mode corresponds to the mode defined in the automatic release transaction and cannot be modified.

Actioning Subcontract orders

Fields

The following fields are included in this window :

Block number 1

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.

Block number 2

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

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.

Block number 3

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

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.

Request/order

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

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

  • purchase unit defined at the level of the unit product record,
  • purchase unit linked to the supplier.

The purchase unit cannot be modified.

This unit is used as the default value when entering an order, subcontract order or receipt, with the supplier unit suggested in priority when the product-supplier record exists.
The purchase units are accessible depending on the type of category.
SEEINFO Upon invoicing of a product, the product PUR is used.

  • STK quantity (field QTYSTU)

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

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

Block number 5

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.

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 value 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 budget structure or the project operational (task) 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.

Cost

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

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

Container capacity

Select the Freight container you wish to use. The choice of the container determines the maximum weight and volume you can carry.

  • No. of containers (field TCTRQTY)

Use this field to specify how many containers you will use.

  • Weight (field WEICAP)

This field displays the total weight capacity for the selected container or containers. 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 for the selected container or containers. If a container is not selected, you can enter a volume without having to manage containers.

Selected

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

Available

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

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.

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

Grid

  • field SELIND

Click this check box to select this line.

  • Contract no. (field POHNUM)

 

 

  • Validity start date (field STRDAT)

 

  • Validity end date (field ENDDAT)

 

 

  • Location reference (field USEPLC2)

 

 

Close



An entry transaction defined specifically for automatic generation (field Transaction reserved for automatic generation is selected) must be specified in parameter SCOPTRNUM - Automatic EO transaction (chapter STO, group MIS).

Order release (via the Initate then the Release action) from this function uses the entry transaction defined for automatic order generation (field Transaction reserved for automatic generation is selected) specified in parameter SCOPTRNUM - Automatic EO transaction (chapter STO, group MIS).

Color assignment rules

Color

Requirement

Resource

 Green

The requirement is covered in full (by an assignment or an allocation).

The full quantity of the resource is used for an assignment with one or many requirements.

 Light green

The requirement is covered in part (by an assignment or an allocation).

The full quantity of the resource is used for an assignment with one or many requirements.

 Pink

The requirement is subject to a shortage of stock (see field Shortage).

 Brown

Last element processed/modified.

 

Action panel

Click the Search action to load the table (grid) with events that meet the entered selection criteria.

The maximum number of lines available is defined in the selected entry transaction.

The following fields are included on the window opened through this button :

Selection criteria

  • Active memo (field MEMO)

You use a memo code to save the criteria applied to an entry screen. Use this field to find out if a memo code has already been saved for the current screen values.

Use the following buttons to manage memos:

Recall: Recall a previously defined and saved memo.

Memo: Save the current values of the screen in a memo file with a code to be specified.

Del. Memo: Delete a previously saved memo.

If a memo named STD (standard) is associated with the screen, it is loaded when opening the function.

Enter, select, or build a format calculation expression using the formula editor.
This formula, created using sections of the WIP, product and product/site tables, is applied within the framework of the search in addition to the entered selections.

SEEINFO A warning message is displayed if a reference is made to tables not used in the context or to unknown variables.

Start - end range

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.

Filter for results within a range of Business partners (BPs). For a single Business partner (customer/supplier), enter the same BP code in the From/start BP and To/end BP fields.

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

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

If the value 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 budget structure or the project operational (task) 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).

  • From entry (field VCRNUMSTR)

Filter for results within a range of document numbers. For a single document, enter the same document number in the From/start entry and To/end entry fields.

  • From original document (field VCRORISTR)

Filter for results within a range of source documents. For a single source document, enter the same document reference in the from/start Original document and to/end Original document fields.

  • Start date (field STRDATSTR)

Filter for results within a range of dates. For a single day, enter the same date in the Start date and End date fields. You can leave the Start date field blank to search all records to date.

Filter for results within a range of categories. For a single category, enter the same category in the Start/from category and To/end category fields.

Filter for results within a range of statistical groups. For a single statistical group, enter the same group code in the Start/from group n and To/end group n (where n is a number) fields.

Suggestion filter

  • Suggestion filter (field MRPFLG)

This flag is used to filter the suggestions based on their origin.

Change request

  • field CCMFLG

Use this flag to filter the results to rows that are associated with a change request:

No
Ignore rows associated with a change request

Yes
Display only those rows that are associated with a change request

All
Display all rows

Display

  • Sort order (field SRTCOD)

Select the sort criteria to be applied to the display.

Close

Click the Criteria action to access additional selection criteria. You can filter the products to be processed by order and project, and modify the sort order.

Suggestions filter. Use these radio buttons to specify whether to display MPS suggestions and/or MRP suggestions. By default, all suggestions are displayed.

You can save one or several sets of criteria using the Memo action. You can recall these using the Recall action or delete them using the Delete memo action.

The following fields are included on the window opened through this button :

Block number 1

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.

Block number 2

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

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.

Request/order

The supplier is initialized by default to the first supplier in the list of suppliers available for the product but it remains available for entry. The supplier code entered must fulfill certain conditions: be active and not of prospect type.

This field offers several possibilities. The user can:

  • directly enter the supplier code whose existence is checked in the Suppliers file,
  • click the quick Supplier selection from the Actionsicon to do the following:
      • select a supplier from the file,
      • create, according to the user's access rights, a supplier in the file,
      • view the notes linked to the supplier,
      • view the list of the last order prices.

When the entered supplier is a Miscellaneouscustomer, a window automatically opens for the entry of the address. When the entered supplier is a Normalsupplier, you can view and potentially modify the address from the Actionsicon, as soon as the supplier code has been entered.

Following the entry of the supplier, different messages can be displayed in the following cases:

  • When the supplier is declared to be on hold. This message can be blocking or a simple warning according to the value given to the dispute code in the supplier record.
  • When the product is not referenced at this supplier. This message can be blocking or constitute a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) parameter.
  • When the order for the product is blocked for this supplier. This message can be blocking or a simple warning according to the value given to the blocking code in the product record.
  • When the supplier's purchase unit is different from the entered unit, a message is displayed and so you can decide whether to perform a conversion.

If the supplier is modified and its units are different from those of the former supplier, the message "Do you want to order in US ?" is displayed. This enables the user to avoid any price setting inconsistency and keep a coherent order unit for the supplier.

  • If the answer is Yes, the order unit is readjusted into stock unit.
  • If the answer is No, the quantities are readjusted keeping the supplier's units.

In order duplication, changing suppliers is not authorized.

Inter-company specificities: Within the framework of an inter-site or inter-company order, the supplier needs to be declared as being of the inter-site type and the site associated with this supplier must be a sales site (it defines the sales site in the mirror sales contract). The purchase site at the source of the order must determine an inter-site customer so as to define the ship-to customer on the corresponding sales order.

When the supplier is identified as being an inter-site supplier, the inter-site flag of the order is automatically selected. If the site associated with the supplier belongs to another company than the purchase site of the order, the inter-company flag is also selected.

A warning message can be displayed in this context if the customer linked to the purchase site is blocked. The generated sales order displays a blocked status. The inter-site orders are not themselves concerned with this operation. No WIP is managed for internal flows.

Use this field to link the purchase of this product with a specific project.

Type in, or select from the Projects table, 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 value 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 budget structure or the project operational (task) 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 are no separator characters, the link is 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 separator characters after the project code indicates the link type is a budget code (the link is 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.

Line

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

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

  • purchase unit defined at the level of the unit product record,
  • purchase unit linked to the supplier.

The purchase unit cannot be modified.

This unit is used as the default value when entering an order, subcontract order or receipt, with the supplier unit suggested in priority when the product-supplier record exists.
The purchase units are accessible depending on the type of category.
SEEINFO Upon invoicing of a product, the product PUR is used.

  • STK quantity (field QTYSTU)

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

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

Grid

  • field SELIND

Click this check box to select this line.

  • Contract no. (field POHNUM)

 

 

  • Valid from (field STRDAT)

 

  • Valid to (field ENDDAT)

 

 

  • Location reference (field USEPLC2)

 

 

Close

Click the Supply action to create a purchase request, a delivery request, or a purchase order.

The delivery request or the purchase order can be inter-site or inter-company depending on the selected supplier.

You can use the Suggest action to create suggested procurement orders.

The following fields are included on the window opened through this button :

Block number 1

Production site This is initialized by default with the normal production site for the user.

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.

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

Use this field to link production of this product with a specific project.

Type in, or select from the Projects table, 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 value 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 budget structure or the project operational (task) 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 are no separator characters, the link is 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 separator characters after the project code indicates the link type is a budget code (the link is to the project budget structure).

  • Loss % (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.

Planning

  • STK quantity (field EXTQTY2)

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

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 start date of the Work Order.

  • End date (field ENDDAT2)

This field identifies the planned end date of the Work Order.


Process

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

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 (mother routing) linked to multiple products.

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

Close

Click the Manufacturing action to create a work order (firm or planned).

You can use the Suggest action to create suggested procurement orders.

The following fields are included on the window opened through this button :

Block number 1

The order site is a mandatory field. By default, it is fed with the order site associated to the user. It can be modified by another site authorized for the operator, depending on their authorizations.

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

This field indicates the references of the product to process.

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

Use this field to link the purchase of this product with a specific project.

Type in, or select from the Projects table, 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 value 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 budget structure or the project operational (task) 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 are no separator characters, the link is 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 separator characters after the project code indicates the link type is a budget code (the link is to the project budget structure).

  • Purchase lead time (field AVAOFS)

For purchasing
This is the number of calendar days, corresponding to:

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

This information is used for the calculation of net requirements only in order to calculate the start date of sub-contract operation suggestions when the product does not have a product-site record.

For an order direct creation or a purchase request
The reorder lead-time is used to calculate the planned receipt date when no lead-time can be determined from the price lists or product-site record.
This lead-time is also used in the MRP calculation to calculate the requirement start date.

  • Quality ctrl. lead time (field QUALTI)

The quality control lead-time (in number of days) is used in MRP: It is inserted between the requirement date and the suggestion end date to take into account the time necessary to carry out the quality control.

Planning

  • PUR quantity (field QTYPUU2)

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

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

  • purchase unit defined at the level of the unit product record,
  • purchase unit linked to the supplier.

The purchase unit cannot be modified.

This unit is used as the default value when entering an order, subcontract order or receipt, with the supplier unit suggested in priority when the product-supplier record exists.
The purchase units are accessible depending on the type of category.
SEEINFO Upon invoicing of a product, the product PUR is used.

  • STK quantity (field EXTQTY2)

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

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

  • Order date (field STRDAT2)

The order date is initialized to the current date and can be modified (only in creation mode). The modification of this date during the creation leads to the display of a message offering the possibility to update the prices and potential discounts calculated for the order lines already entered. This modification also leads to the update of the expected receipt date of the order lines for which no requirement has been consumed.

  • Receipt date (field ENDDAT2)

This field displays the date on which the requirement arises.

Subcontract

Enter the BP code or use the Lookup tool to search from the BP table.

  • field ZBETCPY

Use this parameter to define if the inter-company nature of the document must be displayed or not.
Inter-company documents are used for exchanges between sites belonging to different legal companies.
Reminder:

A inter-company document is considered as such if it meets the following criteria:

  • The recipient business partner is defined as a site: this BP is set to inter-site at the level of the BP record and linked to a site.
  • This site linked to the recipient BP belongs to a different legal company than the original site of the document.

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

Close

Click the Subcontract action to create a subcontract order.

Click the Planning workbench to open the Planning workbench of the product.

Click the Grouping workbench to group the requirements using the Grouping workbench.

Click this action to access the Purchase request (POP) or Purchase order (POF) function.

Click this action to access the selected contract (TRP/TRF).

Click this action to access the inquiry of the product-site record for the selected product.

For a production-type or subcontract-type order, click this action to open a screen that displays all the MWx material requirements, or MSx subcontract requirements, associated with the selected product. By selecting a line, you can drill down to the corresponding product workbench.

Load details: You can drill down to the load inquiry associated with the selected WIP.

For a production or subcontract type coverage, click this action to access a grid that displays all the necessary materials and the gap between the available to promise stock and the necessary stock.

For a production or subcontract type coverage, click this action to access a grid that displays all the necessary materials and the gap between the available to promise stock and the necessary stock, and the requirement date for each component. For a negative gap, the system defaults to the first availability date.

Menu bar

Option / Transaction

Click the Transaction action to view the format of this entry transaction.

Error messages

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

The messages listed below are those that are specific to the enterprise workbench function. The messages created through journal generation are listed in the corresponding documentations (WO management, PO management, shipment requests etc.).

The end range is prior to the start range

Control message on entry of selections by range.

XXX is the exclusive planner of this product.

It means that the GPLNFLT - Planner/buyer filter general parameter (SOT chapter, SCH group) is set to Yes exclusive and the user is trying to access a product under the responsibility of a different planner.

The production lead-time for this product implies a shipment delay. Continue?

If a work order is created by taking a requirement into account, and if the earliest production end date is later than the requirement objective date.

Order no. XXX Not converted No pricing

This message is displayed during a purchase order in back-to-back orders when the following conditions are met:

Tables used

SEEREFERTTO Refer to documentation Implementation