Code: pp mmm s f xx o y cc z
Characters | Description |
pp | package code |
mmm | module code |
s | submodule code |
f | function code |
xx | sequence number 1 |
o | type of process |
y | session sequence number; when more than one session is present for the same main table, this sequence number can be used to define the different sessions, starting with 0 |
cc | customization type |
z | sequence number 2 |
The possible values for z are: 1-9. In case of more than nine forms continue with the characters a-z.
Code: pp mmm n xxx o ccc y
Characters | Description |
pp | package code |
mmm | module code |
n | level |
xxx | sequence number 1 |
o | type of process |
ccc | customization type |
y | sequence number 2 |
The possible values for the are 1-9. For the general menu and for submenus the level n is 0.
Code: pp mmm xxxxx ccc
Characters | Description |
pp | package code |
mmm | module code |
xxxxx | sequence number |
ccc | customization type |
Sequence x can have the values 0 – 9.
The principle of the SCS for menus is: sequential numbering
Limitations:
- Main-menus: maximum 9 per module, but basically unlimited.
- Sub-menus: maximum 9 per level
- Maximum number of levels: 5 (which exceeds the GUI limitations)
whwmd00000000 | (package menu; for the module code take e.g. masterdata) | |||||
whwmd10000000 | (main menu) | |||||
whwmd11000000 | (submenu) | |||||
whwmd12000000 | ||||||
whwmd13000000 | ||||||
whwmd14000000 | ||||||
whwmd15000000 | ||||||
whwmd15100000 | (submenu) | |||||
whwmd15200000 | ||||||
whwmd15210000 | ||||||
whwmd15220000 | ||||||
whwmd15230000 | ||||||
whwmd15231000 | ||||||
whwmd15232000 | ||||||
whwmd15240000 | ||||||
| | ||||||
whwmd15290000 | ||||||
whwmd15300000 | ||||||
| | ||||||
whwmd15900000 | ||||||
whwmd16000000 | ||||||
| | ||||||
whwmd19000000 | ||||||
whwmd 2 0000000 | (main menu) | |||||
whwmd21000000 | ||||||
whwmd22000000 | ||||||
etc. | ||||||
wh inp1 0000000 | ||||||
whinp110000000 | ||||||
etc. |
Code: pp mmm s f xx g y z cc
Characters | Description |
pp | package code |
mmm | module code |
s | submodule code |
f | function code |
xx | sequence number 1 |
g | report group |
y | sequence number 2 in the report group |
z | session sequence number; when more than one session is present for the same main table, this sequence number can be used to define the different sessions, starting with 0 |
cc | customization type |
Possible values for report group g, and sequence number 2, y, are 1-9. If there are more than 9 report groups or reports in a group continue with the characters a-z. If the same report is reused with another session, the report group and sequence number 2 in the group do not have to comply with this coding standard.
The function code f for reports in the Service Pack Transition (SPT) module is always 9. The combined sequences s and xx must be the sequence number of the related SPT session or SPT dll. Type of process is always ‘m’.
pp | mmm | s | f | xx | g | y | z | cc |
tc | ibd | 0 | 4 | 01 | 1 | 1 | 0 | 00 |
wh | wmd | 2 | 4 | 30 | 2 | 1 | 0 | 00 |
Table descriptions are visible to the end user. Therefore table descriptions must be consistent (also across application packages).
Code: pp mmm s xx
Characters | Description |
pp | package code |
mmm | module code |
s | submodule code (only when numeric) |
xx | sequence number |
New tables in the released releases that are being defined as modifications to the standard package (customized software) must be defined under submodule 9. For tables it is not possible to use the submodule codes c, l, b, d, j or o.
Ranges for Customization Types:
Customization Type | Range |
C | 901 – 935 |
L | 936 – 950 |
B | 951 – 965 |
D | 966 – 980 |
J | 981 – 985 |
O | 986 – 995 |
Existing tables retain their own codes when they are modified.
pp | mmm | s | xx |
wh | wmd | 2 | 10 |
tf | acp | 1 | 04 |
The standards for table fields consist of such elements as the field sequence, the standard label, and defaults.
The sequence of the fields in the table is used by the session generator and in Easy SQL displays. For this reason it is essential that the field sequencing in the table is correct. The following must be taken into account:
- Primary key fields must be in the proper sequence at the top of the table.
- Fields that logically belong together must also follow each other on the table. For example:
- Order Quantity and Order Unit
- Amount and Currency
- Item and Project
- Text fields and combined fields must be at the bottom of the table.
The table field label serves as the basic label for form prompts. It must therefore be representative for a label in a single-occurrence session.
When creating a record, fields must be filled with standard constants, if possible. A default constant must be defined for enum fields. Where applicable, the same applies to other types of fields.
Index descriptions are displayed in forms after selecting the Sort By option from the View Menu.
The following rules apply:
- The index description consists of the table field descriptions in the correct index sequence, divided by commas (,).
- Fields that are used at the end of an index to make it unique do not have to be included in the index description.
- Avoid duplicate keys.
Code: pp mmm s xx.dddd.c
Characters | Description |
pp | package code |
mmm | module code |
s | submodule code (only when numeric) |
xx | sequence number |
dddd | mnemonic |
c | short customization type |
For standard software the second period punctuation mark and the customization type are omitted. Avoid undesirable letter combinations in mnemonics .
The first three characters of mnemonics of combined table fields must be cmb. The fourth character is alphabetically incremented starting from a.
pp | mmm | s | xx | dddd | c |
wh | wmd | 2 | 10 | cwar | |
td | pur | 4 | 02 | orno | |
ti | rou | 0 | 10 | cmba |
pp | mmm | s | xx | dddd | c |
wh | ina | 5 | 10 | ref_key | |
td | pur | 4 | 02 | calc.r | |
ti | rou | 0 | 04 | cmba1 |
Code: ppmmm.dddd.c
Characters | Description |
pp | package code |
mmm | module code |
dddd | mnemonic |
c | short customization type |
For domains which are not module specific the module code and first period punctuation mark can be omitted.
For standard software the second period and the customization type are omitted.
pp | mmm | . | dddd | . | c |
cp | com | . | diru | ||
tc | ccap | ||||
wh | inh | . | cdls |
pp | mmm | . | dddd | . | c |
ts | acm | . | 1401.01 | ||
ti | asc | . | analysis |
Code: pp mmm s f xx [oycc]
Characters | Description |
pp | package code |
mmm | module code |
s | submodule code |
f | function code |
xx | sequence number |
o | type of process |
y | script sequence number; if more than one session is present for the same main table, this sequence number can be used to define the different scripts |
cc | customization type |
The function code f for script/objects in the Service Pack Transition (SPT) module is always 9. The combined sequences s and xx must be the sequence number of the related SPT session. Type of process is always ‘m’.
pp | mmm | s | f | xx | o | y | cc |
ts | cfg | 2 | 2 | 10 | |||
ti | cst | 0 | 1 | 01 | m | 0 | 00 |
ti | cst | 0 | 1 | 01 | s | 0 | 00 |
tp | est | 2 | 8 | 10 | |||
tp | est | 2 | 8 | 10 | m | 1 | 00 |
wh | spt | 0 | 9 | 01 | m | 0 | 00 |
pp | mmm | s | f | xx | o | y | cc |
ts | cfg | 2 | 2 | 10 | . | 1 | |
wh | wmd | 4 | 1 | 00 | . | 0 | 1 |