Prerequisites

Activity codes

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

Bullet point  CCM :  Change control management

Bullet point  ECC :  Product version management

General parameters

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

Purchase

Bullet point  BUYFLT (defined at level Site) : Filter by buyer

Bullet point  EXTRCPDAT (defined at level Company) : Minimum receipt date

Bullet point  ITMBPS (defined at level Site) : Supplier referencing

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

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

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

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

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

Bullet point  PURGRUDIS (defined at level Site) : Invoke group pricing

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

Manufacturing

Bullet point  CMPUSBCTR (defined at level Folder) : Usable component control

Bullet point  CUMMAT (defined at level Company) : Material accumulation mode

Bullet point  RELUPD (defined at level Site) : Upgrade upon execution

Inventory

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

Bullet point  MFGMTSNUM (defined at level Site) : Automatic WO transaction

Bullet point  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 :

Table

Table description

ITMFACILIT [ITF]

Products-sites

ITMMASTER [ITM]

Products

ORDERS [ORD]

WIP