Configurator scenarios - Implementation
Prerequisite
Activity codes
The following activity codes (sorted by type) may have an impact on the way the function operates :
Functional
CFG :
Configurator
Sizing
CFC :
Max. no. config. components
CFO :
Max. no. config. operations
CFQ :
Config. max. question no.
CFS :
Config. scenario tab lines
General setups
The following general parameters may change the way the function is working :
Inventory
CFGADV (defined at level Folder) : Advanced config functions
CFGINI (defined at level Site) : Procedure to select scenario
CFGSSC (defined at level Folder) : Multi-level configurator
CFGUPD (defined at level Folder) : Configurator in update mode
Authorizations
This function is object managed. The creation, modification, and deletion operations can be activated or deactivated for a given user. Filters by roles can also be associated with this function.
As data is linked to a site, a filter per site can be activated.
A filter by access code is performed, based on the field named ACSCOD. If an acess code is given, the inquiry and modification rights are granted according to the reading and writing rights associated with the code of the current user in their function profile.
Miscellaneous prerequisites
The setup of a scenario is likely to use all the elements listed below, which must have been previously defined:
Product selection and options / variants windows
Simple calculation tables and Two dimension calculation tables
Notes on the general setups CFGADV, CFGINI and CFGSSC:
CFGADV : This is used to activate the advanced configurator functions when set to yes:
Calculate costs
Establish the links with the X3 tables
Establish the X3 entry points from the scenarios
Setup of multi-level data in a scenario
CFGINI : Scenario selection procedure. This is used to specify which is the procedure to be run to determine the scenario to be launched depending on the context. The same procedure describes all the master scenario choices of the system.
CFGSSC : Authorizes or not the use of sub-scenarios in a scenario.
Tables used
The following tables are implemented by the function :
|
Table |
Table description |
|---|---|
|
ACTIV [ACV] |
|
|
ATABLE [ATB] |
|
|
ATABZON [ATZ] |
Field dictionary |
|
ATEXTE [ATX] |
Dictionary messages |
|
ATEXTRA [AXX] |
Texts to translate |
|
BOM [BOH] |
Header BOMS |
|
BOMD [BOD] |
Detail BOMs |
|
CBLOB [CBB] |
Special folders |
|
CFGABQ [CAB] |
|
|
CFGMAC [CFM] |
|
|
CFGOPTVAR [COV] |
Options / variants |
|
CFGQST [CQU] |
|
|
CFGSCE [CSC] |
Configurator scenarios |
|
CFGSCELIN [CSL] |
Configurator scenario lines |
|
CFGSEL [CSE] |
|
|
CFGSHA [CSH] |
|
|
ITMCATEG [ITG] |
|
|
ITMFACILIT [ITF] |
|
|
ITMMASTER [ITM] |
|
|
ITMMVT [ITV] |
Product-site totals |
|
ITMSALES [ITS] |
|
|
ROUOPE [ROO] |
Routing - operations |
|
ROUOPESTD [ROT] |
|
|
ROUSCD [ROS] |
Routing - scheduling operation |
|
ROUTING [ROH] |
Routings - header |
|
TABCTL [TCT] |
|
|
TABLINCFG [TLP] |