Naming Conventions Of Abap Developments.docx

Naming Conventions of ABAP Developments 

All custom ABAP program names should follow the naming standards stated below.



Each ABAP program should adhere to the ABAP internal naming conventions set forth in this document.

Standard naming conventions are in place and should be used at all times as detailed below for both tables, structures and ABAP etc:Z (1)

Type (1)

Proc1 (2)

Req Num (2)

Underscore (1)

Brief Desc (23)

Z (character number 1): Custom ABAP programs need to begin with ‘Z’. Types (character number 2): This will be used to mention the type of ABAP program. Possible values are as follows: N : Include T : Table S : Structure R : Report C : Conversions for legacy data upload I : Interface M : Module Pool for Dialogs L : Layout Set/Form Proc1 (characters 3 and 4): This will be used to mention the main SAP module. FI : Financial Accounting CO: Controlling MM : Materials Management SD : Sales and Distribution PP: Production Planning PM: Plant Maintenance PS: Project Systems CS: Customer Service GN : General This will be derived from character 3 and 4 of the Functional specification. Req Num (character 5, 6): The ‘Requirement Number’ will be the running serial number within a SAP Module. The SAP Module and the requirement number together will help as an index in collation all development objects such as Functional specification, Technical specification, Unit test Plan, ABAP development objects – program/tables/etc. Underscore (character 7): The ‘_’ symbol will be defined as separator. Brief Desc (characters 8 - 30): Characters 8 – 30 can be used to briefly describe the functionality. This can also be used to distinguish several objects of the same type for a common worklist item, such as multiple structures used for the same dialog module.

Examples: ZCMM19_material upload – Conversion program for uploading material masters in materials management module. ZSMM23_01_Pur_history, ZSMM23_02_Pur_history – 2 number structures developed for definition of field catalogs for ALV report program to show purchasing history. These structures are created for requirement number 23 within the main SAP Module in the main ABAP development worklist. Project Policy on Standard SAP changes To be determined, and included in this document later in the next version.