Showing posts with label standard software coding in BAAN ERP. Show all posts
Showing posts with label standard software coding in BAAN ERP. Show all posts

Coding of labels in BAAN ERP

For standard software or software derived from the standard, the short customization type is omitted in the coding of labels. There are three different types of labels, each with a specific coding standard:
Type 1
Labels with a label description that is uniquely related to a table field are coded based on the table field.
Code: kkmmmsvv.dddd.hvc
kk package code
mmm module code
s submodule code
vv sequence number
dddd mnemonic
h short customization type
vc variant code

In this figure no variant code is used. However, if a variant code had been used, the label code could have been tiitm001.item.01


Type 2
Labels that are not related to a table field and yet are specific to one or more sessions are coded based on the session code.
Code: kkmmmjxxxx.vv.h
kk package code
mmm module code
j s in order to group labels in the label file
sfvv same as session code, namely:
s submodule code
f function code
vv sequence number
vv sequence number
h short customization type


Type 3
Labels for general terms are coded based on a logical code.
Code: kkmmm.dddddddd.hvc
kk package code
mmm module code
dddddddd logical description
h short customization type
vc variant code
For new labels as a result of modifications to the standard, the first of the dddddddd positions should contain one of the following customization types:
o own development by customer
c customization by dealer
l localization
j junior (compact version)
d dealer-specific version
b business-specific version


In Figure no variant code is used. However, if a variant code had been used, the label code could have been: tcgen.compname.01.

Variant code
The variant code vc is used to keep track of the different variants of the same label. Labels with different variant codes refer to the same term, however, they are different in appearance. Different variants could be:
a description (initial capital only)
a description (lowercase)
a description (uppercase)
a description in between brackets (for example, [], (), {})



Coding of functions in BAAN ERP


Code: kkmmmvvvv
kk package code
mmm module code
vvvv sequence number
For new functions resulting from modifications to the standard, the first of the vvvv positions should contain one of the following customization types:
o own development by customer
c customization by dealer
l localization
j junior (compact version)
d dealer-specific version
b business-specific version
The functions defined by means of an include statement should start with this coding followed by a short description for the function.

Coding of questions in BAAN ERP


Code: kkmmmvvvvv.h
kk package code
mmm module code
vvvvv sequence number
h short customization type
In the coding of questions for standard software or software derived from the standard, the . and the short customization are omitted.


Coding of messages in BAAN ERP


Code: kkmmmxvvvv.h
kk package code
mmm module code
x type, namely:
t reference
d domain
s general
u referential update
r referential delete
l layout (message used in menus/forms/report layouts)
vvvv sequence number
h short customization type
For reference messages (type t), the first 3 digits of the sequence number refer to the table number to which the reference message belongs.
Layout messages (type l) should indicate the alignment, starting position, and total number of positions available for the message. This information is useful for software maintenance and translation.

Coding of domains in BAAN ERP


Code: kkmmm.dddd.h
kk package code
mmm module code
dddd mnemonic
h short customization type


For standard software the second . and the customization type are omitted. It is advised to avoid undesirable letter combinations in mnemonics (this should be checked for all primary languages!)
The first character of the mnemonics of combined table fields is c. The remaining three characters are numerical increments starting from 001. 
In the example in Figure , plmm stands for the planning method for MPS Orders.





Coding of reports in BAAN ERP


Code: kkmmmsfvvbchhh
kk package code
mmm module code
s submodule code
f function code
vv sequence number 1
b report group
c sequence number 2 within the report group
hhh customization type


The possible values for the report group (b) and sequence number 2 (c) are 1 through 9. If there are more than 9 report groups or reports within a group, the characters a through z are used. If the same report is used for another session, the report group and sequence number 2 in the group do not have to comply with this coding standard.




In Figure the submodule code, the function code, and sequence number 1 are coded similar to the coding of sessions. Accordingly, the submodule code and sequence number 1 together are the same as the table number.

Coding of program scripts in BAAN ERP


Code: kkmmmsfvv
kk package code
mmm module code
s submodule code
f function code
vv sequence number
The coding of program scripts is based entirely on the coding of tables. The only difference is that, for program scripts, the function code similar to the coding of sessions.
Figure shows an example of a program script code that indicates the process type of a session, namely the tiitm0101 program script that is used by the maintain session of the tiitm001 table.





Coding of menus in BAAN ERP


Code: kkmmmnvvvphhhc
kk package code
mmm module code
n level
vvv sequence number 1
p process type
hhh customization type
c sequence number 2
For the general menu as well as the submenus, the level (n) is 0.The possible values for sequence number 2 (c) are 1 through 9.

Coding of forms in BAAN ERP


Code: kkmmmsfvvphhhc
kk package code
mmm module code
s submodule code
f function code
vv sequence number 1
p process type
hhh customization type
c sequence number 2
For standard software forms or forms that are derived from the standard, the session code to which the form belongs is fully incorporated in the form code. To code the forms, the session code is simply extended with an additional sequence number.




Figure shows an example of a form code based on the tiitm0101m000 session code.
The possible values for the sequence number 2 c are 1-9. In case of more then 9 forms continue with the characters a-z.

Coding of software components


All software components belong to a particular package VRC. The coding of the software components together with the VRC codes make every software component unique. Since some software components can be maintained by language and by package VRC, for example messages, they also need to be linked to a certain language to code them uniquely. The following software components are linked to a language:

  • forms
  • menus
  • reports
  • messages
  • questions
  • labels
1) Coding of sessions
Code: kkmmmsfvvp000
kk package code
mmm module code
s submodule code
f function code
vv sequence number
p process type
hhh customization type (only 000 for sessions)
For sessions, the customization type is always 000. The vv sequence number is not subjected to strict standards.For standard software sessions or sessions derived from the standard software, the submodule code and the sequence number together are similar to the table number.
Example

The submodule code is only used for the coding of sessions that are newly-developed modifications that are not derived from the existing standard.

2) Coding of tables
Code: kkmmmsvv
kk package code
mmm module code
s submodule code (only numeric)
vv sequence number

Tables that are newly-developed modifications to the standard package (customized software) must be defined as follows: the submodule codes c, l, b, d, j, and o cannot be used, instead the numeric value 9 is used extended by the sequence number. 
As a result, the ranges for the customization types are:
Ranges for customization types:
c 901 - 935
l 936 - 950
b 951 - 965
d 966 - 980
j 981 - 985
o 986 - 995
Figure shows an example of the code of a standard software table. If existing tables are modified, they retain their original codes because the customized tables are part of different package VRCs and, therefore, are uniquely coded.




Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More