Requests - 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).

Functional

 DEB : EU exchange declaration

 ECC : Product version management

 GDD : Operating budgets

 MMS : MMS interface - X3

 PJM : Project management

 PTX : Regional taxes

Sizing

 ANA : No. of analytical dimensions

 PPR : Max purchasing charge/discount

 PSH : Purchase request lines maximum

 STI : Product statistical groups

 STS : Purchasing statistical groups

General parameters

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

Purchase

 APPPSH (defined at level Company) : Manage signatures - PRs

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

 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

 PSHAPPCLE (defined at level Company) : Close puch req if signature refused

 PSHAPPHEA (defined at level Company) : Signature on purch req header

 PSHCMMLEV (defined at level Site) : Release pre-commitments

 PSHINIACC (defined at level Company) : PR account initialization

 PSHINIBPS (defined at level Company) : PR supplier initialization

 PSHPRTORD (defined at level Company) : Partial order purchase request

 PSHVLT (defined at level Site) : PR line valuation

 PURCHGTYP (defined at level Company) : Purchase module rate type

 PURCMMPRP (defined at level Site) : Update budget - precommitments

 PURCMMTAX (defined at level Site) : Commitment type

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

 PURVACBPR (defined at level Site) : Default tax rule

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

Budgeting

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

 BUDCMMPRP (defined at level Site) : Include precommitments

 BUDCNTPRP (defined at level Site) : Precommitment control type

 BUDCTLPSH (defined at level Site) : Complete PR budget control

 BUDCTLPSL (defined at level Site) : PR 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

 BUP1 (defined at level Site) : Controlled budget 1

 BUP2 (defined at level Site) : Controlled budget 2

 BUP3 (defined at level Site) : Controlled budget 3

 BUP4 (defined at level Site) : Controlled budget 4

 BUP5 (defined at level Site) : Controlled budget 5

 BUP6 (defined at level Site) : Controlled budget 6

 BUP7 (defined at level Site) : Controlled budget 7

 BUP8 (defined at level Site) : Controlled budget 8

 BUP9 (defined at level Site) : Controlled budget 9

Accounting

 CONTROLDAS (defined at level Company) : DAS2 parameter control

Common Data

 CTLOPPCOD (defined at level Folder) : Project code control

 PJTSNGDOC (defined at level Company) : Single-project document

Accounting interface

Default dimensions

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

(defined at level Company)

 PSM (All companies ) : PO auto generation

 PSD (All companies ) : Purchase request line

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.

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

 Close

 Generation

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.

Linked workflow rules

The following rules are active when the APPPSH parameter authorizes the Management of signatures upon purchase request:

• PSHSIG: PR signature management
• PSHSIGVAL: PR signature
• PSHSIGREJ: PR rejection
• PSHSIGNOT: PR signature notification
• PSHSIGNCR: Notification of PR rule absence
• PSHSIGCAN: PR signature cancellation

Tables used

The following tables are implemented by the function :