Planning 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

 ITMBPS (defined at level Site) : Supplier referencing

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

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

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

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

 GPLNHOR (defined at level Site) : Default planning horizon

 MFGMTSNUM (defined at level Site) : Automatic WO transaction

 SCOPTRNUM (defined at level Site) : Automatic EO transaction

Sequence numbers

The sequence numbers used to number the documents managed by this function are :

 MFG : Work orders

 MFG : Work orders

 PSH : Purchase Request

 POH : Purchase Order

 POC : Purchase Contract Order

 POC : Purchase Contract Order

 SCO : Subcontract order

The sequence number assignment function defines the sequence number which is used

Authorizations

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

The following options can be activated or deactivated for each user :

 Allocations

 Manual allocations

 Scheduling

 Multi-level planning

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.

Other prerequisites

Tables to be completed

The following tables are used by the function. Their content must be updated if necessary :

Tables used

The following tables are implemented by the function :