This function is used to assign orders (needs and resources) among themselves. For instance, a purchase order can be assigned to a material need and a work order can be assigned to a sales order.

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.

The type of viewed orders depends on the product workbench transaction that is being used.
The assignments performed in this function correspond to orders in progress.

The requirements calculation is based on the quantity not assigned at resource or requirement level.

When header criteria have been entered, the displayed orders can be assigned or not by double-clicking or right-clicking on the cells in the grids. Icons symbolize the various actions that are carried out or are available. The orders, whether assigned or not, are distributed among the two grids, based on their status.

The main screen is subdivided into three parts:

Filtres/Reference

This area of the screen is used to enter the various filters prior to loading the orders ('Site', 'Product', etc.).

Projected stock

The grid obtained after entering header information makes it possible to inquire orders.

  • A double click in column 1 makes it possible to include/exclude orders in, and from, the assignment workbench.
    FUNMLINK_Selection.gif: this icon means that the order has been selected.

  • Icon FUNMLINK_OrdreAffecte.gif displayed in column 2 means that, for the time being, the resources is not assigned to the need (or conversely).
    A double click on this icon makes it possible to assign the resource to the need (or conversely) and to load the assignement grid.
  • Icon FUNMLINK_04.jpg is displayed in column 2 when there is a back-to-back production order or a back-to-back order on receipt.

Assignment(s)

The grid lists assigned orders.
A double click on the icon makes it possible FUNMLINK_OrdreNonAffecte.gif to deassign the resource from the need (or conversely).

Color codes in the grids

There is a color code assigned to the lines:

  • dark green: assigned orders,
  • light green: partly assigned orders,
  • white: deassigned orders.

Tab Entry screen

Filters

Site (field FCY)

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

The site defined on the user record is displayed by default but can be amended.
User (field PLANNER)

Operator in charge of performing the production planning or product ordering.
End date (field MSTDAT)

Use this field to filter the orders to be loaded.

SEEWARNING Observe loading times.

Reference

Product (field ITMREF)

This field specifies the reference of the product to to process.
Major version (field IECCVALMAJ)

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

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.
Stock unit (field STU)

This field can only be displayed and it cannot be modified.
Change request (field ICRID)

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 work in progress transactions for this product until the change request identified is closed. At that point a change to this product will have either been seen through to its conclusion and the change delivered, or the change request rejected. You will not, however, be prevented from progressing a transaction should you decide to do so.
Safety stock (field SAFSTO)

This field can only be displayed and it cannot be modified.
field XPTODIR
Shrinkage % (field SHR)

This field can only be displayed and it cannot be modified.
EOQ (field REOMINQTY)

Grid Projected stock

field PECFLG
field ICOLINK
WIP status (field WIPSTA)
Order type (field WIPTYP)
Order (field WIPTYPSTA)
Entry (field VCRNUM)
Start date (field STRDAT)
End date (field ENDDAT)
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.
field CRFLG
Remaining qty. (field RMNEXTQTY)
Expected stock (field EXTSTO)
Original obj. (field OBJDAT)
Early/Late (field ELFLG)
Requirement date (field REQDAT)
Message (field XMRPMES)
MRP date (field MRPDAT)
MRP quantity (field MRPQTY)
Planned quantity (field EXTQTY)
Allocated qty. (field ALLQTY)
Shortage (field SHTQTY)
Total actual quantity (field CPLQTY)
Quantity assigned (field MTOQTY)
Original site (field ORIFCY)
Project (field PJT)
BP (field BPRNUM)
Priority (field PIO)
Product source (field FMI)
Source type (field VCRTYPORI)
Original document (field VCRNUMORI)
Origin line (field VCRLINORI)
Source seq. (field VCRSEQORI)
Source product (field ITMREFORI)
BOM code (field BOMALT)
Operation (field BOMOPE)
Source (field ORI)
Planner/Appro. (field PLANNER2)
Buyer (field BUY)
Optimized (field OPTFLG)
Net price (field NETPRI)
Currency (field CUR)
WO description (field MFGDES)
Document units (field UOM)
Entry type (field VCRTYP)

Grid Assignment(s)

field ICOUNLINK
Order (field XTYP1)

This field can only be displayed and it cannot be modified.
Entry (field VCRNUM1)

This field can only be displayed and it cannot be modified.
Type (field XVCRTYP1)
Assigned qty. (field LIKQTY1)

This field indicates the quantity allocated to the selected order.
By default, the system displays the maximum quantity available.
This quantity can be modified.

Rest (field AVAQTY1)

This field can only be displayed and it cannot be modified.
End date (field ENDDAT1)
Forced (field FRCFLG)
Message (field XMESS1)

This field can only be displayed and it cannot be modified.
Status (field XTRKFLG)
Progress (field XPROGRESS)
BP (field BPRNUM1)
Document units (field UOM1)
Assignment

This button is used to assign the order.

Plan/Order
Plan/Execute
Planner/Sub-contractor
Document
Instantaneous availability
Provisional availability
Loads
Assignment
Manual assignment
Scheduling
Tunnel to associated WIP
Deletion

This function is used to delete the assignment linked to the order.

Force assignment

This function is used to allocate an assignment to the order, by forcing the proposal issued by the system.

Action panel

Search

This button is used to start the search for assigned orders based on the product entered in the header.

Block number 1

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.

Block number 2

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

Request/order

Supplier (field BPSNUM)

To enter the supplier, enter the supplier code or click the Actions icon to:

  • Select a supplier in the file.
  • Select a supplier from the list of suppliers available for the product-site.
  • Select a back-to-back supplier from the list of back-to-back suppliers available for the product-site, in the case of a back-to-back product.
  • 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.

This supplier cannot be defined as a ‘Prospect’ and must be ‘Active’.

When the supplier entered is of the Miscellaneous type, a window automatically opens for the address to be entered. 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.

After entering or modifying the supplier, the following messages may display:

  • When the supplier is declared to be on hold. This can be a blocking message or a simple warning according to the value given to the dispute code in the Supplier record.

  • When the order for the product is blocked for this supplier, or for this supplier on this particular receiving site. This can be a blocking message or a simple warning according to the value of the blocking code in the Product-Supplier or Product-Site record.
  • When the product is not referenced by this supplier. This message can be blocking or a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) general parameter.
  • When the receipt product-site is not referenced by this supplier. This can be a blocking message or a simple warning according to the value of the ITMBPSFCY - Supplier site referencing parameter. If this message is blocking, you can still proceed with your entry but the Receiving site field must be set as available for entry for the entry transaction. In this case, the Receiving site field is emptied. You must then enter a site where the product-supplier is referenced, or for which the ITMBPSFCY - Supplier-site referencing parameter is not defined as blocking.
    This control does not apply to inter-site orders.
  • When the supplier purchase unit is different from the entered unit, a message is displayed and 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 consistent 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 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 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.

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 combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

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

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

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

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

Grid

field SELIND

Select this check box to select this line.
Contract no. (field POHNUM)
Supplier (field BPSNUM2)
Valid from (field STRDAT)

This field identifies the associated order date or planned production start date for the order.
Valid to (field ENDDAT)

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

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

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

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

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

SEEINFO 
Location reference (field USEPLC2)

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

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

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

Purchase site (field PURFCY)

Block number 1

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 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).
Shrinkage % (field SHR)

The loss percentage corresponds to the production or storage loss.

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

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

Planning

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.

    Process

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

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

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

    Block number 1

    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.
    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.
    Product (field ITMREF)

    This field specifies the reference of the product to 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 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).
    Purchase lead time (field AVAOFS)

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

    • The order 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.
    field PUU2

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

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

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

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

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

    Subcontract

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