Scribd
Upload
80 views5 pages

ABAP Naming Standards Guide

The document outlines ABAP programming standards including adding a header to all programs with details like object ID, program title, and description. It also specifies naming conventions where application areas like Basis, CO, FI etc. should correspond to the area being worked on. Program and transaction codes should follow these standards for improved performance and maintenance.

Uploaded by

vasamraja1
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
80 views5 pages

ABAP Naming Standards Guide

The document outlines ABAP programming standards including adding a header to all programs with details like object ID, program title, and description. It also specifies naming conventions where application areas like Basis, CO, FI etc. should correspond to the area being worked on. Program and transaction codes should follow these standards for improved performance and maintenance.

Uploaded by

vasamraja1
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

ABAP Programming / Naming Standards

Following are the performance standards need to be following in writing ABAP programs:

For all ABAP Programs / Transaction Codes


Add the below header at the beginning of Every ABAP program
************************************************************************
* OBJECT ID :
* PROGRAM TITLE :
* MODULE :
* PROGRAM TYPE :
* INPUT :
* OUTPUT :
* CREATED BY :
* CREATION DATE :
*-----------------------------------------------------------------------
------------------------------------
* DESCRIPTION :
*
*
*
************************************************************************
* Modification history:
*
------------------------------------------------------------------------
----------------------------------
* DATE |User ID |TS Ver | Transport Request | Description
*
------------------------------------------------------------------------
----------------------------------
*
************************************************************************
Naming conventions to be followed:
Other Objects
Application area corresponds to the application area you are working like 

B - Basis       C - CO      F- FI         W -  PM    

S – SD / SAM     M – MM/Supply    

You might also like