Naming principles system naming principles
The system is named after three to four English letters, the first code is a standard or custom identification code, and the following few yards are meaningful English abbreviations.
(System code) format:
AXX Standard System Module
GXX with Taiwan related rules adjustment module
CXX Custom-made module
Description
XX is the system abbreviation code
Example:
AIM Material Master file (Item Master), inventory (Inventory Management) management system
ASM Systems basic Data Management (System Management)
Programming (program) naming principles
1. Main file name
Format:
SSSP999
Description
SSS is the system designator (to be represented in lowercase letters)
P is the program type
i 维护作业 r 报表作业m 目录选单 s 参数设定p 批次处理 t 交易处理q 查询作业 u 辅助工具
999 for the Job code
- When using the job code, the first code represents the processing phase, such as: 0 for parameter setting, 1 for basic data maintenance. The second to third code is the serial number.
- If the program contains more than one secondary function or sub-screen, you can add a fourth code to indicate the subordinate information (screen or program) that belongs to the main program.
Example:
AIMI100:
AIM: Material main file system code
I: Job type is maintenance job
100: Job Code
aimi1001 (The job code consists of the four yards): This program name represents the sub-file of program aimi100
Outside the column:
For example, in the Azz System Management code, the program naming principle does not follow this way.
Nomenclature: Named according to [program use file name] or [two aspects of program use]
2. Additional file name
Additional file names are divided into three categories: 4GL original program section, screen format, other formats
(1). 4GL Original Program section
4GL: Original Program
42m: The target program after the original program is compiled
42R: Target program that can be run after connection
(2). Screen format
4fd:form Designer uses the screen file
Per: Convert the 4fd file into a picture control file via the Gsform tool
42F: Compile the completed screen file data
(3). Other formats
SCH: Archive Reference content
Rep
Shared programs (program) naming principles
A shared program is a function that is universally available in TipTop GP, which is a function that only some subsystems can use.
Format:
Cl_xxxxxxx
Description
Cl_: Indicates that the program is a shared program (Common Library)
XXXXXXX: At least one character, up to 17 characters (because of each maintenance job entry limit). The name must have a representative meaning, you can add "_" to the partition.
Example:
Cl_err: Used to display error messages
Cl_null: Checks whether the input value is empty
Where the shared program resides:
Placed in the $top/lib directory of the TipTop GP system, grouped by the different categories of extensions.
Sub-Program naming principles
Sub-Program:
In the process of development, will be limited in part of the program, the common use of the function of independent, and also written a program.
Sub-Program features:
Easy to maintain, correct, save development time.
Sub-Program Categories:
- General sub-procedures;
- Query sub-procedures;
1. General sub-procedures
Format:
S_xxxxxxx
Description
S_: Indicates that the program is a general purpose subroutine (SubFunction)
XXXXXXX: Up to 18 characters with a minimum of 1 characters. It needs to be named in a meaningful way. such as: English abbreviations and so on.
Example:
S_upimg for the inventory system, update the Img_file sub-program.
General sub-Program storage location:
Placed in the $top/sub directory of the TipTop GP system, classified according to the extension.
2, Query sub-program
Format:
Q_xxxxxxx
Description
Q_: Indicates that the program is a query class (queries) subroutine
XXXXXXX: Up to 18 characters with a minimum of 1 characters. It needs to be named in a meaningful way, mostly by the name of the database table (table name) you want to query.
Note: If the database table name is already in use, you can add a serial number later to identify the difference in the order.
Example:
Q_ima for material Parts data query
Where to find the sub-program to store:
Placed in the $top/qry directory in the TipTop GP system, categorized by extension.
Attention:
Query subroutine naming can not conflict with the "Dynamic Query subroutine" name, if there is a conflict on the name, then the subsequent logon data or system management, there will be unpredictable difficulties and error conditions occur
Actual Operation guide:
Writing a simple query subroutine is not recommended to write your own program, you can refer to the "Azz System Management" Module Squadron "P_qry" Introduction. Self-defined "dynamic Query subroutine", fill out the related to query the table, field data can be used, more self-written query subroutine simple, in the subsequent management is also more convenient.
3, the general sub-program and the difference between shared programs
Same point:
- The characteristics of common use of multiple programs;
- With the characteristics of easy maintenance, correct and save development time;
Different points:
- Shared program "CL_XXXXXXX" each subsystem (module) can be applied;
- The General subroutine "S_xxxxxxx" is only for one or a few subsystems (modules);
function naming principle
function (Functioin):
Part of a program that has an independent nature and is capable of providing special functions.
Format:
Xxxx_yy
Description
Xxxx_: For the program code abbreviation, more than the system (module) code after 4 yards representation
YY: The function description for the function
Example:
I100_a new function for this job
The following function functions are included in the program:
Attention:
Under the same main program name, you cannot use the same function name to avoid unexpected errors in the program's connection or at run-time.
Variable naming principles
According to the characteristics of the variables appearing and used in the program, the variables can be divided into general variables, regional variables, transfer parameters and screen variables.
1. Global variables (global varibles)
Format:
G_xxxxxxx
Description
G_: Indicates that the variable has integrity (Gobal)
XXXXXXX: The name of the variable
Example:
G_gui_type to define the style of the GUI for which
The location of the global variable definition:
The whole variable is defined in the entirety variable file, which is $top/config/top.global.
2. Regional variables (Local varible)
Format:
L_xxxxxxx
Description
L_: Indicates that the variable has a culture (Local) and is only valid with a function.
XXXXXXX: For meaningful names, please name them in a meaningful way.
3. Transitivity parameters (Parameter varlables)
Format:
P_xxxxxxx
Description
P_: Indicates that the variable has transitivity (parameter)
XXXXXXX: For variable names, name them in a meaningful way.
4. Screen variable (varlables)
Format:
S_xxxxxxx
Description
S_: Indicates that the variable is a screen variable
XXXXXXX: For variable names, name them in a meaningful way.
Scope of Use:
Screen variables are used in multiple columns in a single file (screens varlables)
Attention:
Screen variables (screens) are named in fields to facilitate comparison with fields. Also, only programs that use a multi-column array are defined in this way.
database table naming principles
The table name length is named from 3 to 4 English characters, different systems, with different table name usage sections, and it is recommended that you first understand the table names range of the system's original startup before opening the new table.
1. Table name (table)
Format:
Xxx_file
Customized (Customer-specific) Table naming format:
Tc_xxx_file
Description
XXX: 2 yards to 4 yards, in lowercase English characters (can contain numbers) named.
_file: A fixed word, expressed as a table.
Example:
Aim_file for the material main file
Gef_file for sales Document Nature document
Attention:
Before opening the new form, the relevant data and use methods of the form should be registered in the "P_ZTA Records maintenance operation" to be incorporated into the management.
2. Field Name
Format:
XXX99
Custom (Customer-specific) field naming format:
(1). The naming principle for adding custom fields to a custom form:
Format:
tc_xxx99
Example:
Custom fields under Tc_ima_file: tc_ima001, tc_ima002 .....
(2). The naming principle for adding custom fields to a standard table:
Format:
ta_xxx99
Example:
Custom fields under Ima_file: ta_ima001, ta_ima002 ....
Description
XXX: The name of the Xxx_file is the same as the name of the XXX.
99: for 2 yards serial number, if the serial number can be expanded to 3 to 4 yards.
Example:
Zz32 is the field in the table Zz_file.
Attention:
Before opening a new field, you must register the relevant data and use method of the form in the "P_zta file architecture trimming record Maintenance job" and start to be included in the management.
3. Index name
Format:
Xxx_01
Customized (custom) index naming format:
Tic_xxx_01
Example:
The custom index under the Ima_file table is tic_ima_01.
Description
XXX: The name of the Xxx_file is the same as the name of the XXX.
01: Serial number for 2 yards.
Example:
ZZ_01 is the unique index code in Zz_file.
Attention:
Before opening the new index, the relevant data and usage methods of the form should be registered in the "P_zta Records maintenance work" to be included in the management.
4. Storing the schema files stored in the TipTop system (Sch files)
Format:
Xxx_file.sch
Description
This is the file name of the system in which the table exists
XXX: The name of the Xxx_file is the same as the name of the XXX.
Example:
Ima_file.sch is the schema file name for the main file of the material.
Directory Configuration
1. TipTop Directory Configuration
2. config directory configuration
Reference Download: http://download.csdn.net/download/wahaa591/8796431
Ii. TipTop naming principles and directory configuration-tiptop GP ERP two Novice development tutorial