Buyer's Planning - Implementation

Prerequisites

Activity codes

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

Dependent activity codes

These codes are never entered in folder management, because their value is calculated :

 PP1 (Purchase charge / discount 1), PP2 (Purchase charge / discount 2), PP3 (Purchase charge / discount 3), PP4 (Purchase charge / discount 4), PP5 (Purchase charge / discount 5), PP6 (Purchase charge / discount 6), PP7 (Purchase charge / discount 7), PP8 (Purchase charge / discount 8), PP9 (Purchase charge / discount 9), SI1 (Product statistical group 1), SI2 (Product statistical group 2), SI3 (Product statistical group 3), SI4 (Product statistical group 4), SI5 (Product statistical group 5).

Functional

 DEB : EU exchange declaration

 ECC : Product version management

 GDD : Operating budgets

 MMS : MMS interface - X3

 PJM : Project management

 PTX : Regional taxes

 SMI : Integrale migration

Sizing

 ANA : No. of analytical dimensions

 POI : Work plan lines maximum

 PPR : Max purchasing charge/discount

 STI : Product statistical groups

 STS : Purchasing statistical groups

Localization

 KUK : Localization united kingdom

General parameters

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

Purchase

 BUYFLT (defined at level Site) : Filter by buyer

 DACMANPUR (defined at level Site) : Default price reason - manual

 DEFITMKND (defined at level User) : Default service type

 EXTRCPDAT (defined at level Company) : Minimum receipt date

 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

 PURCMM (defined at level Site) : Update budget - commitments

 PURCMMDAT (defined at level Site) : Commitment date

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

 PURGRUDIS (defined at level Site) : Invoke group pricing

 PURREN (defined at level Site) : Require price reasons

 PURRND (defined at level Site) : Round unit price

 PURTEXORD (defined at level Site) : Order text position

 UPDPRIPUR (defined at level Site) : Default price reason - base

Budgeting

 BUDAMT (defined at level Site) : Budget control by amount

 BUDCMM (defined at level Site) : Include commitments

 BUDCNTCMM (defined at level Site) : Commitment control type

 BUDCTLPOH (defined at level Site) : Complete PO budget control

 BUDCTLPOL (defined at level Site) : PO line budget control

 BUDPRCAMT (defined at level Site) : % tolerance - amount

 BUDPRCQTY (defined at level Site) : % tolerance - quantity

 BUDQTY (defined at level Site) : Budget control by quantity

 BUDTYPCUR (defined at level Site) : Budget conversion rate type

Sales

 DIRORDCTL (defined at level Company) : Back-to-back if credit exceeded

Sequence Numbers

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

 POH : Purchase Order

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

Accounting interface

Default dimensions

The default dimensions sections assignment is performed through the following codes :

(defined at level Company)

 POI (All companies ) : Buyer plan

 POID (All companies ) : PO Workbench detail

 POW (All companies ) : Automatic PO creation

Authorizations

This function is object managed. The creation, modification, anddeletion operations can be activated or deactivated for a given user.Filters by rolescan also be associated with this function.

As data is linked to a site, a filter per site can be activated.

Miscellaneous prerequisites

Accounting interface

Default dimensions

If analytical accounting is managed, it is necessary to define how to initialize the analytical dimensions in the order header and lines.

This definition is made via the POI parameter codes for the header and POID for the lines, with the aid of the "Default dimensions" option (see the Default dimensions documentation). These parameter codes are supplied with the installation and they can be adapted to fit requirements.

Note: During the loading of the analytical dimensions in the buyer's plan, whether or not purchase requests are taken into account, if the analytical axes are not entered, then they will automatically loaded with the default dimensions.

In the case of a back-to-back order, the default dimension codes POW and POID are used if necessary to recover the analytical dimensions of the sales order header (POW) and/or the sales order line (POID) via the intermediary of the Original document setup line.

Automatic journals

If you choose to perform a budget control and/or manage commitments in orders, it is necessary to identify accounting codes to be used and their nature.

This identification is made via the PORD STOP parameter code with the help of the "Automatic journals" option (see the Automatic journals documentation). This parameter code is supplied upon installation and the user may adapt it to fit their own requirements.

Other conditions

Structure code

This code is used to determine the sales conditions managed at the level of each line of the order in the form of the different Discount and charges fields. The number and type of fields managed and thus the structure of the line can vary from one supplier to another: it is therefore necessary to associate a structure code with each supplier. This association is completed at the level of the supplier record. A default structure code is supplied upon software installation. This structure code is programmed to be blank in order to make it possible to immediately associate a structure code with each supplier created without additional entry. It is possible to create as many structure codes as required (see the Price list structure documentation).

Product

It is mandatory that the ordered products be referenced in the Product record. This referencing can be made before any use of the function or during the creation of an order if the user has the required authorizations.

Tables used

The following tables are implemented by the function :