Installed Base Inquiry - Implementation

Prerequisite

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 :

 DEBR (Intrastat state/region), KAG (Argentinean localization), PBDPO (Payment balance declaration).

Functional

 CCN : Concessions

 CFG : Configurator

 CFOM : Cash forecast management

 CSL : Consolidation

 DEB : EU exchange declaration

 ECC : Product version management

 EORI : EORI identification

 FAS : Asset folder

 FOA : Food allergens

 LTA : Local taxing

 MAXPD : Maximum period (companies)

 NPI : Product design

 PJM : Project management

 PLM : PLM - X3 interface

 PRCSL : Pre-consolidation

 RVM : Routing version management

 SAFT : SAF-T

Sizing

 ANA : No. of analytical dimensions

 BPA : Number of BP addresses

 HHM : Number installations

 NUC : Number of packing units

 REC : Customer sales reps

 SFI : Max. no. entered inv. elts

 STI : Product statistical groups

 STO : Contracts statistical groups

Localization

 KDE : German localization

 KFR : French localization

 KIT : Italian localization

 KPO : Portuguese Localization

 KSP : Spanish localization

 KZA : South-African localization

General parameters

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

Customer Support

 MACBRAUSE (defined at level Folder) : "use of ""brand"" field"

Sequence numbers

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

 MAC : Customer installed base

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

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.

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

Miscellaneous tables

The following miscellaneous tables are used by the function. They must be populated if necessary :

 Miscellaneous table number 408 : Brand

Local menus

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

 Local menu number 2972 : Installation type

Tables used

The following tables are implemented by the function :