ABAP/4 DEVELOPMENT STANDARDS

ABAP/4 DEVELOPMENT STANDARDS
These slides covers Object naming standards, ABAP/4 Programming standards and procedures.

These programming standards are intended to aid ABAP/4 programming in the SAP R/3 software development.

Naming standards

SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466).Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’. 

Naming standards

SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466).

Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Following, we will define the standards for the use in this Project.

Program

The following program naming conventions have to be followed for creating ABAP/4 programs, functions, includes and reports.  Refer to Maintaining SAP Standard Objects (section 1.5) if you are modifying an SAP standard object.

Object names will consist of forty characters formatted as follows:

Position	Length	Usage
1	1	‘Y’     Tools and utilities that are not to be migrated to production ‘Z’     Application programs that will be migrated to production
2	2	SAP application area (refer to appendix A) ‘UT” Utilities program
4	1	Program Type           ‘C’      Conversion (temporary)           ‘I’       Interface (any time)           ‘L’      Include           ‘R’      Report           ‘U’      Utility/Other
5	1	Program category: ‘O’     Outbound (Data is sent from SAP)            ‘I’       Inbound (Data is sent to SAP)            ‘N’     Others having no data transfer
6	3	Three digit numeric representation
9	32	Any Characters (if possible, choose a meaningful acronym) Leave this blank if possible.

       Module Pools and Module Pool Includes

       Module pool names will consist of forty characters formatted as follows: 

Position	Length	Usage
1	3	‘SAP’
4	1	‘M’    for screen module pool  ‘D’    for dialog module pool         ‘F’     for subroutine module pool
5	1	‘Y’     indicates a user defined module pool that are not           to be migrated to production ‘Z’     indicates a user defined module pool that are to be migrated to production
6	2	Application area (refer to appendix A)
8	3	Three digit numeric representation
11	30	User defined

The module pool include names will consist of eight characters formatted as follows:

Position	Length	Usage
1	5	Same as positions 4 - 8 in module pool name
6	3	‘TOP’   For data declarations, table definitions Onn for PBO modules Inn    for PAI modules Fnn for subroutines * where nn is an integer between 00 and 99

Function (General) groups and function (general) modules 

Function (General) groups:

Function (General) group names consist of 18 characters formatted as follows:

Position	Length	Usage
1	1	‘Z’
2	2	Application area (refer to appendix A)
4	15	Any character string

Function (General) modules

Function (general) module names consist of a maximum of thirty characters.

Position	Length	Usage
1	2	‘Z’
3	28	Descriptor separated by underscores

Transaction codes

Transaction code names consist of maximum of ten characters formatted as follows:

Position	Length	Usage
1	1	‘Z’
2	2	Application area (refer to appendix A)
4	8	Any character string

Maintaining SAP standard objects

The purpose of this section is to define the naming conventions to be used whenever working with SAP standard objects.

User exits and customer exits should be used whenever possible to enhance standard SAP programs.

If inappropriate user exit exists, the program(s) must be copied and renamed.

For ABAP/4 programs, functions, includes and reports, the first position must be changed to ‘Z’.  For module pools, change the 5^th position to a ‘Z’.

In the event that the above is not possible, include modules must be added to where the customized code has to be called in order to keep the changes in the standard SAP code to a minimum.

If lines have to be taken out, never delete them, just comment them out and mark them right-justified with either the related change request number or your initials and the date.