Grouping workbench
Use this function to view suggestions and actual demand for a product, and to select some of the records as the basis for a new order.
You can access this function from the Enterprise planning workbench (FUNGBENCHA) and the product Planning workbench (FUNDBENCHA).
Prerequisites
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 how 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
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.
- 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 parameter (STO chapter, SCH group).
You can restrict the orders selected to a specific freight container.
You can use the Criteria action to enhance the selection criteria applied.
Requirement list table
The columns displayed in the Requirement list table and the order in which they are displayed is determined by the selected entry transaction.
If the selected transaction defines a "planner" role, the requirements extracted are comprised of the following:
Production planner | Subcontract planner |
Work order suggestions (proposed by default) | Subcontract suggestions (proposed by default) |
Planned work orders (proposed by default) | Planned subcontract orders (proposed by default) |
Customer orders | Customer orders |
Material requirements | Material requirements |
Transfer requests | Service requirements |
Transfer requests |
If the selected transaction defines a "buyer" role, the requirements extracted are comprised of the following:
Buyer | Internal buyer (intersite) | External buyer (purchasing) |
Purchase suggestions (proposed by default) | Transfer replenishment suggestions (proposed by default) | Purchase suggestions (proposed by default) |
Purchase requests (proposed by default) | Planned transfer orders (proposed by default) | Customer orders |
Customer orders | Customer orders | Material requirements |
Material requirements | Material requirements | Transfer requests |
Transfer requests | Transfer requests | |
Subcontract requirements (proposed by default) |
If the grouping is for a Buyer or Internal material buyer role, it is possible, for the relevant supplier and project code, to attach a valid contract for the product, and to generate a planned or firm shipment request. A warning to adjust the quantities to be accounted for, where a contract exists for the selected product is displayed.
The system accounts for all selected orders up to the remaining quantity by default, regardless of the role selected.
For each order, use the Pick check box and the Include all/Exclude all actions to select or clear the selection of orders to be processed (initialized to zero or to the remaining quantity of the withdrawn quantity field).
Once all the work in progress (WIP) orders to be grouped (processed) have been selected, along with the quantities that should be considered for each of them, click the Generate action to create an order based on the selections, up to the sum of the quantities considered. The quantity remains modifiable.
The nature of the generated order depends on the role assigned to the transaction on which the grouping is based (planned or firm work order, planned or firm subcontract order, purchase request, planned or firm transfer replenishment order).
The elements processed can be either reduced or deleted.
A work order or subcontract order covering sales orders or production or subcontract requests increments the Quantity taken into account at release field of these orders.
The manufacturing release is performed according to a release transaction dedicated to the automatic release. This transaction is based on the Enterprise planning workbench transaction in process or, in its absence, on the MFGMTSNUM - Automatic WO transaction parameter (STO chapter, MIS group). The scheduling mode corresponds to the mode defined in the automatic release transaction and cannot be modified.
The subcontract release is performed according to a release transaction dedicated to the automatic release. This transaction is based on the grouping transaction in process or, in its absence, on the SCOPTRNUM - Automatic EO transaction parameter (STO chapter, MIS group).
Planned or firm purchase orders are created according to the following groupings:
- One firm delivery request is generated for each planned delivery request.
- One firm purchase order by supplier.
- One order line by product/project.
In order to save a log of the requirements taken into account, a planned work order (WOP) coming from a grouping is of the type WOP* and can no longer be the object of a grouping of a planned order.
For a product-site whose assignment rule is set up with the back-to-back method (1 to 1) and taken into account in real time: the customer orders or transfer requests in progress that have the value Stock
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. |
Start - end range
From product (field ITMREFSTR) |
Filter for results within a range of product codes. For a single product, enter the same product code in the From/start product and To/end product fields. |
From BP (field BPRNUMSTR) |
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. |
Freight container capacity
Container (field TCTRNUM) |
Select the container that you want to use. It can simply be a "freight container" type. |
Weight (field WEICAP) |
This field displays the total weight capacity of the selected freight container(s). If a container is not selected, you can enter a weight without having to manage containers. |
No. of containers (field TCTRQTY) |
Use this field to specify how many freight containers you want to use. |
Volume (field VOLCAP) |
This field displays the total volume capacity of the selected freight container(s). If a container is not selected, you can enter a volume without having to manage containers. |
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. |
field TCTRWEU |
The weight unit. |
Volume (field VOLAVL) |
This is field displays the available volume for a container when the total volume of selected lines in the workbench do not equal zero. |
field TCTRVOU |
This non-modifiable field displays the volume unit defined for the freight container. |
Cost
Minimum order (field ORDMINAMT) |
Filter for results within a range of order values. For the lowest order value, expressed in the folder currency, enter the tax exclusive amount in the Minimum order field. |
Maximum order (field ORDMAXAMT) |
Filter for results within a range of order values. For the maximum order amount, expressed in the folder currency, enter the tax exclusive amount in the Maximum order field. |
field ORDCUR |
This is the folder currency. |
Selected
Cost (field TOTCOST) |
This field represents the cost multiplied by the ordered quantity. |
field TOTCUR |
Amount expressed in the selected transaction currency. |
Grid Requirement list
Pick (field FIE) |
Select this check box to select this line. |
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:
|
Entry type (field VCRTYP) |
This field displays the reason for the order or the resulting order type. |
Product (field ITMREF) |
Reference of the product for which the transaction needs to be carried out. It must be defined for the selected site. |
Site (field STOFCY) |
The site associated with the work in progress order. |
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. |
STK (field STU) |
This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc. |
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. |
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). |
Qty. taken in STK (field PECQTY) |
Selected quantity, expressed in physical stock units. |
Purchase site (field POHFCY) |
Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.). |
Contract (field POHIND) |
Contract no. (field POHNUM) |
Supplier (field BPSNUM) |
Code identifying the supplier. For suggestions in the results table generated for purchase order suggestions and subcontract order suggestions by an MRP processing run (FUNMRP/FUNMRPG), MRP will have used a product-supplier selection hierarchy to determine the preferred (default) supplier by site. You can change this default supplier manually. Where MRP failed to nominate a supplier you must select the supplier manually.
When selecting a supplier manually by clicking either the selection icon, or the Actions icon in the Supplier field (BPSNUM):
Before you can transfer a purchase order suggestion to a firm purchase order you must allocate a supplier manually if the MRP processing |
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. |
Total actual quantity (field CPLQTY) |
This field displays the total completed quantity, including the rejected quantity, expressed in the operation unit. |
Description 1 (field ITMDES1) |
This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line. |
Original site (field ORIFCY) |
This field displays the original order site. |
Project (field PJT) |
This field displays the associated project code. The content can be one of the following:
If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'. To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure). |
BP (field BPRNUM) |
This field displays the code of the Business partner (customer/supplier) associated with the order. |
Priority (field PIO) |
This field displays the delivery priority (Normal, Urgent, Very urgent) for the order. |
Product source (field FMI) |
This field indicates how the goods required for the order line will be managed.
|
Source type (field VCRTYPORI) |
This field identifies the reason for the order. |
Original document (field VCRNUMORI) |
This field identifies the number of the source document or order. |
Origin line (field VCRLINORI) |
This field identifies the associated line on the source document or order. |
Source seq. (field VCRSEQORI) |
This field identifies the sequence number of this component in the source parent product. |
Source product (field ITMREFORI) |
This field displays the original product code. This product code describes what is referred to as a 'Bill of Materials' or a 'BOM'. A BOM contains structured information for making and costing a product. It defines the components that make up a product, and given this, the cost of the product. |
BOM code (field BOMALT) |
Multiple bills of materials (BOMs) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products this includes restriction of the BOM to a specific site and to specific areas of functionality (for costing or for capacity planning). |
Operation number (field BOMOPE) |
The components can be linked to a particular operations in a production route, according to the manufacturing requirements. |
Planner/Appro. (field PLANNER2) |
Operator in charge of performing the production planning or product ordering. |
Buyer (field BUY) |
Enter or select the code of the operator responsible for reordering the product on the selected site. This code is referenced in several scripts, such as the buyer’s plan, the supplier order entry, etc. |
Net price (field NETPRI) |
This field displays the Net price for this order. Select the order from the Actions icon to view the order details. |
Currency (field CUR) |
This field corresponds to the currency of the order, delivery or invoice. |
Requirement date (field REQDAT) |
This field displays the requirement (demand) date. |
PUR (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 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.
|
Qty. taken in PUR (field PUUPECQTY) |
Selected quantity, expressed in physical stock units. |
PUR-STK conv. (field PUUSTUCOE) |
Conversion factor used to calculate the quantity in stock units from a quantity entered in purchase units: Quantity in STK = Qty in PUR * conversion factor. This conversion factor can be accessed if the Purchase unit field (PUU) has been entered, and has a value different from the stock unit. It can be initialized using the conversion factor table if the combination exists. |
Source (field ORI) |
This field identifies the origin of the order. |
Document units (field UOM) |
This field displays the unit of measure (volume or mass) of the product on the associated order. |
Weight (field LINWEI) |
This field represents the total weight multiplied by the quantity ordered. |
Weight unit (field LINWEU) |
The weight unit. |
Volume (field LINVOL) |
This field represents the total quantity ordered multiplied by the total volume. |
Volume unit (field LINVOU) |
Code of the unit in which the package volume is given. |
Cost (field LINAMT) |
This field displays the order line amount excluding tax, expressed in the transaction currency. |
Popup view | ||||||||||||||||||||
Click Popup view from the Actions icon to view the information for this event using the standard screen display mode. |
||||||||||||||||||||
Include/Exclude | ||||||||||||||||||||
Click Include/Exclude from the Actions icon to select (include) or clear (exclude) this order line. |
||||||||||||||||||||
Split | ||||||||||||||||||||
Field descriptions
Block number 1
Block number 3
|
Click Split from the Actions icon to apportion an order line across multiple suppliers. This action is only available for purchase suggestions.
By default, the system distributes the order equally between all suppliers of the product. You can amend the proposed suppliers and quantities, as required.
Click Stock from the Actions icon to view the inventory levels for the selected product, by site.
Click Management data from the Actions icon to view the management data and reorder rules for this product.
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 function. 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.
Click Product usage from the Actions icon to view a three-year history of product usage by month, where the current month is determined by the system date. The following product movement elements display based on total consumption and do not necessarily represent sales history.
- Freight container
- Weight
- Volume
- Load
- Minimum order
- Maximum order
- Free freight threshold
You can use these elements as references and controls. The totals are updated based on elements you select in the workbench.
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 Shortage field). |
|
Brown |
Last element processed/modified. |
Specific actions
Click the Search action to load the table (grid) with the orders to be processed, according to the entered selection criteria. You can delete selected lines (click Delete from the Actions icon) and add new lines to the grid. The maximum number of lines available is defined in the selected entry transaction. |
Click the Criteria action to access additional selection criteria.
Filters by order type: Use these check boxes to select the orders that must be taken into account in the projections.
Filters on suggestions: Use these radio buttons to specify whether to display MPS suggestions and/or MRP suggestions in the projections. 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.
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. |
Formula (field FORMULE) |
Enter, select, or build a format calculation expression using the formula editor. A warning message is displayed if a reference is made to tables not used in the context or to unknown variables. |
Start - end range
From product (field ITMREFSTR) |
Filter for results within a range of product codes. For a single product, enter the same product code in the From/start product and To/end product fields. |
From BP (field BPRNUMSTR) |
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. |
Project start: (field PJTSTR) |
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".
|
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. |
Category Start: (field TCLCODSTR) |
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. |
field TSICODSTR |
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. |
Filters
Suggested reorder (field POS) |
Filter for results within purchase suggestions. |
Suggestion filter (field MRPFLG) |
This flag is used to filter the suggestions based on their origin. |
Reorder planned (field POP) |
Filter for results within planned purchase orders. |
Customer orders (field SOF) |
Filter for results within customer orders. |
Subcontracts firm (field EOF) |
Filter for results within firm subcontract orders. |
Production materials (field MWF) |
Filter for results within reserved materials. |
Transfer requirements (field TPF) |
Filter for results within firm intersite requests. |
Display
Sort order (field SRTCOD) |
Select the sort criteria to be applied to the display. |
Click Include all to select all valid order lines. |
Click Exclude all to clear all selected order lines. |
Click Generate to generate an order from the selected orders. The System log provides details of the generated order number and products processed. |
Barre de menus
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 Grouping workbench function. The messages created through the journal generation are listed in the corresponding documentation (Work order, Orders - Purchasing and Sales, Delivery request, etc.)
XXX is the exclusive planner of this product.This message is displayed if you try to access a product that another planner is responsible for, and the GPLNFLT - Planner/buyer filter parameter (SOT chapter, SCH group) is set to Exclusive filter.
This message is displayed during a purchase order in back-to-back order when the following conditions are met:
- The PURCTLPRI0 - Purchase Price existence control parameter (ACH chapter, PRI group) is set to Control.
- The product has no price:
- The system has not found a purchase price list for the back-to-back order supplier.
- No purchase base price is entered on the product record.
- The product has no standard cost, or the PURPRICE - Price by default standard cost parameter (ACH chapter, PRI group) is set to No.