Skip to main content

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  z...

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 5th 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.

Comments

Popular posts from this blog

How to Create SAP ABAP Query Using SQ01 Step by Step Guide

How to Create SAP ABAP Query Using SQ01 Step by Step. You can create ABAP query objects ,if they are not exist in the SAP system. You can create SAP query without  ABAP programming knowledge. ABAP Query provides users with a variety of ways to define and create different types of  reports , such as  Basic Lists ,  Stats , and  Sorted Lists . ABAP query consists of four elements: Queries InfoSets Groups Translation query Queries The query component is used by end users for Queries. You can create queries, change and queries executed. Transaction  SQ01. Trnslation component / QUERY Many texts to define queries, InfoSets and user groups are generated. These texts are displayed in the language we choose to access the SAP system. We can compare the text or languages ​​that use this component. InfoSets InfoSets are the views of the Special Data Sources. An InfoSet Describes the fields of a data source that can be reported in the q...

BADI in SAP ABAP Step by Step

BADI in SAP ABAP Step by Step BAdI Acronym of Business Add Ins As a customer outsider, it helps BAdI to improve SAP functionality. Why is BADI? Unlike previous improvement methods, BADI continues the approach aimed at re-use objectives. BADI can be used in a number of times that these standard evaluation techniques can only be used once. For example, if you are upgrading a custom project, you can not map the extension on other custom projects. In order to overcome this disadvantage, SAP provided a new evaluation technique called BADI. Code of transaction for BADI definition: SE18 When you create a BAdI definition, you create a class interface automatically and you can define the methods in the interface. The application of the methods can be made in SE19 transactions. When created BAD, they are generated automatically: An interface with 'IF_EX_' is inserted between the first and second characters of the BAdi name Class classified as 'CL_EX_' inserted betwee...

ALV Field Catalog in SAP ABAP

ALV Field Catalog in SAP ABAP Field Catalog Field catalog is an internal table which is used to pass a list of fields to display in ALV report, we can set different properties to fields that will be display in ALV output. Type Group It is a data dictionary object which contains all the reusable user-defined types. Example for a type group is SLIS, which contains all the user-defined types for developing ALV reports. TYPE-POOLS is a keyword which is used to assign the type-group to a ALV report . Syntax : TYPE-POOLS SLIS . DATA : <IT_FCAT> TYPE SLIS_T_FIELDCAT_ALV . "INTERNAL TABLE FOR FIELD CATALOG DATA : <WA_FCAT> TYPE SLIS_FIELDCAT_ALV . " WORK AREA FOR FIELD CATLOG Field catalog types Field catalog: Field catalog is a format description of the display area. There are three procedures to build a FIELD CATALOG. 1. Automatic field catalog. 2. Semi-automatic field catalog. 3. Manual field catalog. Automatic field catalog. If the list structure has ...