Grouping workbench - Implementation

Prerequisites

Activity codes

The following activity codes (sorted by type) may have an impact on the way the function operates :

 CCM : Change control management

 ECC : Product version management

General parameters

The following general parameters may change the way the function is working :

Purchase

 BUYFLT (defined at level Site) : Filter by buyer

 EXTRCPDAT (defined at level Company) : Minimum receipt date

 ITMBPS (defined at level Site) : Supplier referencing

 ITMBPSFCY (defined at level Site) : Supplier-site referencing

 PGENICO (defined at level Site) : Inter-site requirements

 POHMINAMT (defined at level User) : Order min amount control

 POHMINQTY (defined at level User) : Minimum order qty control

 PURCTLPRI0 (defined at level Site) : Purchase price existence control

 PURGRUDIS (defined at level Site) : Invoke group pricing

 PURPRICE (defined at level Company) : Price by default standard cost

Manufacturing

 CMPUSBCTR (defined at level Folder) : Usable component control

 CUMMAT (defined at level Company) : Material accumulation mode

 RELUPD (defined at level Site) : Upgrade upon execution

Inventory

 GPLNFLT (defined at level Folder) : Planner/buyer filter

 MFGMTSNUM (defined at level Site) : Automatic WO transaction

 SCOPTRNUM (defined at level Site) : Automatic EO transaction

Authorizations

An authorization can be granted for this function to limit the processes to a company or a site.

Entry transactions

This function is managed with entry transactions which can be set up.

A standard transaction is suggested when installing the software. A setup function is used to modify this standard transaction or create new personalized transactions. This setup essentially exists to specify some functional characteristics of the transaction and display as well as the default loading for certain fields.

It is also used to define:

• the role of the user for whom the transaction is intended: production planner, material buyer (internal or external) as well as the actions authorized for this type of user.
• the data to be displayed for each of these events,
• the grouping transactions are provided with an access code. 

Tables used

The following tables are implemented by the function :