Assignment workbench

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

• Selection formula (field FORMULE)

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.

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

• Ignore pending issues (field WAICOD)

Click this check box if pending (suspended) issues are to be excluded from the stock projections.

• Include the stock under QC (field CTLCOD)

Click this check box if stock in quality control (at status 'Q') is to be included in the stock projections.

Product-site > Stock tab

• Ignore previous lost sales (field SOSCOD)

Click this check box if sales provisions where the date precedes the current date are to be excluded from the stock projections.

• Apply loss % (field SHRFLG)

Click this check box if production suggestions must be increased by the loss (shrinkage) percentage for the product-site and if quantities remaining from work orders in progress must be decreased by this same percentage.

Loss percentage corresponds to production or storage loss.

Production loss corresponds to the total losses generated by each routing operation.

• Suggestion filter (field MRPFLG)

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

• Sort order (field SRTCOD)

Select the sort criteria to be applied to the display.

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

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

• Supplier (field BPSNUM)

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.

• Project (field PJT)

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.

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

• field STU

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

• field SELIND

Click this check box to select this line.

• Contract no. (field POHNUM)

• Supplier (field BPSNUM2)

• Valid from (field STRDAT)

• Valid to (field ENDDAT)

• Purchase unit (field PUU2)

• Location reference (field USEPLC2)

• Purchase site (field PURFCY)

• Production site (field STOFCY)

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

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

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

• Project (field PJT)

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.

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

• End date (field ENDDAT2)

This field identifies the planned end date of the 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 (mother 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).

• Order site (field POHFCY)

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.

• Receiving site (field PRHFCY)

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)

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.

• Project (field PJT)

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.

• PUR quantity (field QTYPUU2)

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

• field PUU2

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

• field STU2

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.

• Supplier (field BPRNUM2)

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.

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