ABAP Naming Standards

ABAP/4 Naming Standards CVS IT
This document details the ABAP Development Workbench Naming Standards that will be utilized by application developers o !"S #T$ #t has
been signed o and is included as a part o Pro%ect !harter under Pro%ect &anagement Standards
Page 1 of 52 Customized Version For ISPAT Industries Limited
Sign '
Date Name Signature
Change Log
Date Version Author Change Description
Reviewed By
Date Name
Table of Contents
Sr.
No.
Toi! Page No.
( #ntroduction )
* Standard SAP Naming !onventions )
+ Application ,ierarchy )
) Development !lass )
- Business .ngineering 'b%ects /
/ Dictionary 'b%ects /
0 ABAP Programs (*
1 2unctions (/
3 !lass 4ibrary (1
(5 ABAP Types and 'b%ects *(
(( Te6t .lements *0
(* Screens *1
(+ 78# #nterace *3
() Transactions +5
(- 4ogical Database +(
(/ S.T97.T Parameter #ds +*
(0 Area &enus +*
(1 &essages ++
(3 Test !ases +)
*5 ABAP :ueries and 8ser 7roups +)
*( Authorization 'b%ects +/
** Batch ;ob Names +0
*+ BD! Session +1
*) !hange <e=uest Description +1
*- Documentation +3
*/ .vents +3
*0 #nbound 2iles )5
*1 Non>ABAP Programs )5
*3 'utbound 2iles )(
+5 SAPScript )(
+( T"A<" .ntries )+
+* 2ield e6its? )+
++ !ustomer .nhancements @ .nhancement Pro%ects ))
+) Appendi6 A @ SAP Application ,ierarchy )-
" #ntrod$!tion
The naming standards described in this document have been developed by !"S #T team or use by their ABAP9) Programmers$ The same standards shall be used by the
ABAP9) programmers o !"S #T and 78TPA during the implementation o the 7rand Te6$ The aim o these standards is to easily identiy the unction or content o a
customized ob%ect and hence should be employed or each ob%ect created or modiied$ #n the case where a naming standard does not e6ist or a re=uired ob%ectA a standard
should be developed$ 'nce this has been doneA the new standard should be added to this documentA and all other users inormed o the update$ 4ikewiseA i an e6isting
standard proves insuicientA then this problem should be raised and resolved$
Standard SAP Naming Conventions
Development ob%ects can be categorized as independent or globalA an ob%ect that has instance and client wide visibilityA or dependent or localA an ob%ect that e6ists within an
independent ob%ect$ As an e6ampleA an ABAP program is an independent ob%ect and has visibility in all clients in a SAP instance where as program te6t elementsA data ields
and subroutines are dependent ob%ects with only local visibility$
The ollowing conventions should be ollowed in all cases e6cept where e6plicitly stated?
($ #ndependent ob%ectsA such as data dictionary ob%ectsA programsA area menus?
BPermanentC !ustomized 'b%ects > The name should begin with the character BDCA ollowed by the SAP application area identiication Esee Appendi6 A @ SAP
Application ,ierarchyF
BTemporaryC !ustomized 'b%ects > The name should begin with the character BGCA ollowed by the developerCs initials$
*$ Dependent ob%ectsA such as program te6t elementsA data ieldsA subroutines?
!ustomized SAP 'b%ects > The name should begin with the character BDC to distinguish it rom SAP code$
!ustomer or custom ob%ects @ &eaningul name$
Ali!ation %ierar!hy
SAPCs Application hierarchy can be viewed in the primary screen o the 'b%ect Navigator Etransaction code S.15FA or ound in Appendi6 A @ SAP Application ,ierarchy o this
document$ Please make note o this hierarchy as it is the top>level organizational element in the development workbench and is a critical component o the naming
standards$
&eveloment Class
<elated development ob%ects are grouped together in a development class$ The assignment o an ob%ect to a class is entered in the ob%ect directory Etable TAD#<F$ The class
determines the transport layer that deines the transport attributes o an ob%ect$
Whenever a development workbench ob%ect is createdA you are prompted to assign it to a development class$ The class chosen should describe the area the ob%ect belongs
to$
The ollowing naming convention is imposed by SAP?
SAP Standard ob%ects use class names starting with A>S or 8>H$ !ustomer ob%ects cannot be added to these classes$ !hanged ob%ects are recorded in the
Workbench 'rganizer and can be transported$
!ustom developedA permanentA ob%ects use class names starting with G or D$ New or changed ob%ects are recorded in the Workbench 'rganizer and can be
transported$
!ustom developedA private testA ob%ects use class names starting with T$ New or changed ob%ects may be recorded in the Workbench 'rganizerA i you choose
this option when creating the development class$ 'b%ects cannot be transportedA unless they have been included in a transport re=uest$
!ustom developed local ob%ects use class names starting with I$ New or changed ob%ects are not recorded in the Workbench 'rganizer and cannot be
transported$
<eserved Namespace$ 4ike other <epository ob%ectsA development classes can belong to a prei6 namespace i the relevant Namespace is installed in your <9+
System$ Development class begins with a namespace prei6 enclosed in slashes E9F$ #n a development class o this type you can create ob%ects that belong to
the same prei6 namespace$ !hanges to the ob%ects are recorded in the Workbench 'rganizer and can be transportedA i you have conigured the <9+ System
appropriately$
"." C$stom &eveloment Classes
When creating a development classA you will be prompted to provide?
Development class name? up to +5 characters ollowing the standard below$
Short Te6t? @ up to /5 characters o descriptive te6t
Transport 4ayer? > choose the appropriate layer rom the ield look>up table$
Person <esponsible? > 8ser #D o the developer or development team lead responsible or all ob%ects in the development class$
Sotware !omponent? > choose the appropriate sotware component name rom the ield look>up table$
Application !omponent? > choose the appropriate application component rom the ield look>up table$
4ink to workbench organizer? > optional or BTCA private test development classes$
Naming Standard
Position Description Values Meaning
( !ustom #ndicator D !ustomized Development !lass
*>) Application Area E*>+ charactersF 2#A SDA #PSA etc$ SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
Separator BJC Separator
Sui6 'b%ect types
D."
DD#!
!'N2#7
!lassiied the types o ob%ects in the application area?
D." @ Development ob%ects such as ABAPA ABAP :ueryA SAPS!<#PTA etc$
DD#! @ Data Dictionary ob%ectsA such as tableA viewA structureA search helpA etc$
!'N2#7 @ !oniguration data
.6ample? D#PSJD."@Development ob%ects o Public Sector !omponent custom development class
B$siness 'ngineering (b)e!ts
Within the 'b%ect Navigator or Development !lassesA this is the irst ob%ect type entry$ #t is the domain o the Business .ngineers or Worklow conigurations$ Should
you as a developer be working on a custom development EunctionA reportA programA BAP#A transactionA or dialog moduleF re=uested by business engineeringA the
custom development ob%ect name is re=uired in the Worklow 'b%ect &ethod description$
Naming conventions or worklow ob%ects are not within the scope o this document$
&i!tionary (b)e!ts
".* &ata Base Tables
A table deinition in the ABAP Dictionary contains the ollowing components?
Table fields deine the ield names and data types o the ields contained in the table
Foreign keys deine the relationships between the table and other tables$
Technical settings control how the table should be created in the database$
Indexes to speed up data selectionA secondary inde6es can be created or the table
There are three types o database tables in the ABAP Dictionary?
Transparent tables: a physical table deinition e6ists on the database or the deinition stored in the ABAP Dictionary$
Pooled Tables: are used to store control data such as conigurationA screen se=uencesA program parametersA etcF$ Several pooled tables are then combined into
a table pool$ The table pool corresponds to a physical table on the database$
Cluster Tables: contain continuous te6t such as documentation$ Several cluster tables are combined to orm a table cluster that corresponds to a physical table
on the database$
($*$( !ustom Data Base Tables
Table names can be up to (/ characters in long$
Naming Standard
( !ustom #ndicator D !ustomized Table
Application Area E->1 charactersF SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 8ni=ue description E(5 characters ma6F alphanumeric Distinguishes this table rom others or the same application area$
.6ample
DSDJS4SJT'J4.7!G > !ustom table or Sales interace with a 4.7A!G system$
The customer can modiy SAP tables with append structures and customizing includes$ This kind o modiication ensures that the customer enhancements are
automatically merged with the new versions o the SAP tables when there is a release upgrade$
($*$* !ustom ATAB Tables ET3aaaaaF
SAP still supports the creation o customer tables in the BT3C series$ BTC type tables are traditionally coniguration tables using table pool ATABA although SAP has
now largely converted these tables to transparent tables or perormance reasons$
Should a custom BTC table be re=uiredA ollow the naming convention below$
Naming Standard
(>* !ustom #ndicator T3 !ustomized BTC Table
Application Area E->1 charactersF SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 8ni=ue description E(5 characters ma6F alphanumeric Distinguishes this table rom others or the same application area$
.6ample
T3SDJS4SJ#NT<2A! > !ustom coniguration table or Sales interaces$
($*$+ Tables > #nde6
!ustomized inde6es$
Naming Standard
( !ustom #ndicator D !ustomized #nde6
*>+ 8ni=ue #dentiier 55>DD 8ni=uely identiies the inde6
.6ample
D5( > #nde6 D5(
".+ ,iews
A view is a logical view or representation o one or more tables$ The view itsel is not actually stored on the databaseK instead it is derived rom the reerence tableEsF
ields$
A view deinition in the ABAP Dictionary contains the ollowing components?
Tables / join conditions that identiy the tables used in the view and the common ields in the tables which are used to link entries rom the related tables$ A
logical operator E.:A N.A 7TA 4TA etcF is used to complete the %oin condition$
View fields deine the table ield names contained in the view$
election Conditions that allow the =ualiying o data accessible to the view$
($+$( !ustom "iews
"iew names can be up to (/ characters in long$
Naming Standard
( !ustom #ndicator D !ustom created "iew
* "iew Type , ,elp "iew
D Database "iew
P Pro%ection "iew
S Structure "iew
! !ustomizing "iew
+ Separator J 8nderscore
)>(/ Primary Table Name or modiied table name Esee noteF Primary table Primary Table used in the "iew
Note? ,elp views must have the irst 0 characters o their name uni=ue$
.6ample
DSJA(55 > A structure view o an Assets Accounting table
".4 Table Tyes
A table type describes the structure and unctional attributes o an internal table in ABAP$
($)$( !ustom Table Types
The table type name has a ma6imum length o +5 characters$
Naming Standard
* Application Area E->1 charactersF SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 8ni=ue description E*) characters ma6F alphanumeric Distinguishes this table type rom others or the same application area$
.6ample
D2#JA<J5( > !ustom table type to hold Accounts <eceivable types
Page of 52 Customized Version For ISPAT Industries Limited
".- Str$!t$res
A structure deinition in the ABAP Dictionary contains components that may be ields Edata elementsFA orA #N!48D. or APP.ND structures$
($-$( !ustom Structures
The structure name has a ma6imum length o +5 charactersA howeverA i you want to use the structure as an include in a transparent table at a later timeA the
component names may not be longer than (/ characters$
Naming Standard
Sui6 8ni=ue description
E*) characters ma6A (5 i used as an includeF
alphanumeric Distinguishes this structure rom others or the same application area$
.6ample
D2#JA<J'".<D8.J#N"'#!.S > !ustom structure or Accounts <eceivable
".. &ata 'lements
Data elements have no structure$ They describe the business unctions EdescriptionA long nameA medium nameA short nameF o variables or ieldsA and inherit their
technical deinition rom a Domain or <eerence Type$ A reerence type may itsel have the attributes o a data elementA structure or table type$
($/$( !ustom Data .lements
Wherever possibleA an e6isting SAP Data .lement should be used$
# you must create a custom oneA data elements have a ma6imum length o +5 characters$ They must begin with a BGC or BDC to distinguish them rom SAP data
elements$
Naming Standard
( !ustom #ndicator D !ustomized data element
*>+5 8ni=ue description alphanumeric A meaningul name describing the data element
.6ample
D4'ANJN8&B.< > 4oan Number data element$
Page ! of 52 Customized Version For ISPAT Industries Limited
"./ &omains
A domain describes the technical attributes o a table ieldA including data type and ield length$ They are normally reerenced by many data elementsA which allows
or consistency across development ob%ects in use o the ield$
($0$( !ustom Domain
Wherever possibleA an e6isting SAP Domain should be used$
Domains have a ma6imum length o +5 characters$ As SAP uses all letters o the alphabetA including BGC and BDCA they must begin with a BDDC to distinguish them
rom SAP domains$
Naming Standard
(>* !ustom #ndicator DD !ustomized domain
+>+5 8ni=ue description alphanumeric A meaningul name describing the domain
.6ample
DD'4DJ!8ST'&.<JN8&B.< > domain or legacy system customer number$
".0 Sear!h %el
Search help is an ob%ect o the ABAP Dictionary with which screen input help E2) helpF can be deined$ Search helps replace matchcode unctionality rom release )$5
on$
Two types o search help are supported?
Elementary Search Help deines the standard low o an input help?
- where does the data displayed in the hit list come rom Eselection methodF
- what inormation should be displayed in the dialog bo6 or value selection and in the hit list Esearch help parametersF
- what ield contents can be taken into account or hit list selections and which values in the hit list can be returned to the screen ields Esearch help parametersF
- what dialog steps should be e6ecuted in the input help Edialog behaviorF
Collective Search Help combines several elementary search helps$ The user can thus choose one o several alternative search paths with collective search help$
($1$( !ustom Search ,elp
Search ,elp names have a ma6imum length o +5 characters$ 2ollowing the standard SAP conventionA customer deined search helps must begin with a BGC or
BDC$
Naming Standard
Page 1" of 52 Customized Version For ISPAT Industries Limited
( !ustom #ndicator D !ustomized search help
*>+5 8ni=ue description alphanumeric 2ield name or domain or which the help applies$
.6ample
DJDD'4DJ!8ST'&.<JN8&B.< @ Search help or legacy system customer number$
".1 Lo!2 (b)e!ts
The <9+ System synchronizes simultaneous access o several users to the same data records with a lock mechanism$ When interactive transactions are programmedA
locks are set and released by calling unction modules Esee 2unction &odules or 4ock <e=uestsF$ These unction modules are automatically generated rom the
deinition o lock ob%ects in the ABAP Dictionary$
($3$( !ustom 4ock 'b%ects
4ock 'b%ect names have a ma6imum length o (/ characters$ 2ollowing the standard SAP conventionA customer deined search helps must begin with a BGC or
BDC$
Naming Standard
( Prei6 . Prei6 o a lock ob%ect
*>() 8ni=ue description Alphanumeric and BJC Table or development ob%ect or which the lock applies$
(- Separator BJC Separator
(/ 4ock mode .
S
H
. @ .6clusiveA cumulative
S @ Shared
H @ .6clusiveA not cumulative
.6ample
.A(55JH > A non>cumulative e6clusive lock ob%ect or an Assets Accounting table$
"."3 Tyes 4ro$s
Type groups deine single elements or structures or Table TypesA or collections o elementsA structures and9 or table types$
($(5$( !ustom Type 7roups
Type 7roup names have a ma6imum length o - characters$ 2ollowing the standard SAP conventionA customer deined search helps must begin with a BGC or BDC$
Naming Standard
( !ustom #ndicator D !ustom Developed Type 7roup
* Application ,ierarchy EabbreviatedA *>+ characters onlyF SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
sui6 8ni=ue #dentiier 55>DD 8ni=uely identiies the inde6
.6ample
D2#A< > !ustom type to hold Accounts <eceivable types
"."" 5at!h Code
&atchcodes were replaced with search helps starting with <elease )$5$ 8se search helps to assign an input help to a ield$
.6isting matchcodes were automatically converted to search helps$ A matchcode ob%ect is hereby converted to a collective search help with the same name$ .ach
matchcode #D o the matchcode ob%ect is converted to an elementary search help with the same name and assigned to the collective search help created rom the
matchcode ob%ect$ Newly created matchcodes will also be automatically converted$
ABAP Programs
"."* '6e!$table Reorts and Programs
($(*$( !ustom Developed ABAPs
ABAP report and program names must be uni=ueA as theyA like other development ob%ectsA are client independent$ Newly developed custom ABAP reports or
programsA e6cluding unction modules and module poolsA must begin with the letter BDC or BGC$ This character separates custom developed ABAPs rom SAP
ABAPs$ The other characters indicate the unctional area and program unction$ The ABAP name can be up to )5 characters in length$
Naming Standard
( !ustom #ndicator D !ustom Developed ABAP Program 9 <eport
* Program type Alphanumeric < @ <eport
! @ !onversion
# @ #nbound #nterace
' @ 'utbound #nterace
& @ &odule Pool
S @ Subroutine Pool
+>0 Application Area Alphanumeric and BJC SAP Application AreaA reer to Appendix A SAP Application Hierarchy
sui6 Descriptive Te6t Alphanumeric and BJC ABAP unction
.6ample
D<&&JP8<J4#STJ'P.NJP'S > !ustom report programA listing open purchase orders$
($(*$* Standard SAP ABAPs
#t is not recommended that Standard SAP ABAPs be directly modiied$ # they are to be modiiedA make a copy o the programA saving it as a new custom
program ollowing the naming standards described above$
.6ample
<&5/.455 >>>>>L DJ<&5/.455
($(*$+ Programmer WorkA Temporary ABAPs
These naming conventions distinguish utility and work ABAPs that programmers use during development and analysis$ These ABAPs are ever to be transported
to a Production instanceA they must be renamed using !ustom Developed ABAPs standard$
Naming Standard
( !ustom #ndicator G !ustom Developed ABAP Program 9 <eport not or transport
*>) Programmers #nitials alphabetic
->)5 Descriptive Te6t Alphanumeric and BJC
.6ample
G<D;JPPJ'<D.<SJW#T,J'P.NJP'S > Programmer <D;Cs work ABAP$
($(*$) "ariants
"ariants are associated with e6ecutable ABAP programs$ A program may have multiple variants$ The variant name may be () characters long and must be
uni=ue or an ABAP program$
Naming Standard
(>() 8ni=ue variant identiier Alphanumeric and BJC !onsistent with the M8ni=ue %ob identiierN component o the Batch ;ob Name$
.6ample
2'<.!ASTJ!,.!O
"."+ #NCL7&' Program
An include program is used to deine common data ob%ects and9or logic which may be incorporated in many other programs by reerence via the ABAP command
B#N!48D. Preport nameLC$
The naming standard used or custom developed #N!48D.s is the same as that or custom developed e6ecutable reports and programsA see !ustom Developed ABAPsA
with the ollowing suices?
T'P !ontains the report name and any data declaration
T55 @ THH Additional data declarations
255 @ 2HH !ontains all logics and subroutines o the program
.6ample
D<&&JP8<JP'J<.P'<T#N7JT'P > !ustom include or &aterials &anagementA PurchasingA Purchase 'rder report program D<&&JP8<JP'J<.P'<T#N7
"."4 5od$le Pool Programs
&odule pools Ealso known as Dialog &odulesF are associated with transaction screen low$ The programs consist o data deinitionsA &'D84. 9 .ND&'D84. coding
blocksA and subroutines$ These program elements may be ound directly in the program orA using the traditional approachA as #N!48D. programs within the module
pool program$
The traditional module pool programs are prei6ed with the characters BSAP&C and make up about *-Q o the module pools delivered with the SAP system$
&odule pool program names are a ma6imum o )5 characters in lengthA +- i you use the traditional naming convention$
#t is recommended that SAPCs traditional naming standard be used or module pool programs$ This standard calls or the program name to be prei6ed with BSAP&C and
the -th character to be a BGC or BDC or custom module pools$ The remaining +- characters describe the application area and purpose$ Should you choose not to used
this standardA then the naming standard is the same as that or custom developed e6ecutable reports and programsA see !ustom Developed ABAPs
Naming Standard
(>) Prei6 BSAP&C &odule Pool prei6
- !ustom #ndicator D !ustomized &odule Pool
/ Application Area E->1 charactersF Alphanumeric and BJC SAP Application AreaA reer to Appendix A SAP Application Hierarchy
Sui6 Descriptive Te6t Alphanumeric and BJC &odule Pool purpose
.6ample
SAP&D2#JAPJPAG&.NTS > &odule Pool or 2inancial AccountingA Accounts Payable Payments
When you create a new module pool select the BWith T'P #N!4C option$ The system automatically creates the main program containing the T'P include$
($()$( &odule Pool #ncludes
The include names used in module poolsA begin with B&C ollowed by the name o the module pool and conclude with?
BT'PC or the T'P include where tables and data used by the module pool is deined$
B,66C or user "alue <e=uest E,elpF modules$
B'66C or PB' EProcess Beore 'utputF modules$
B#66C or PA# EProcess Ater #nputF modules
B266C or subroutines called rom the modules$
.6ample
#ncludes or &odule Pool SAP&D2#JAPJPAG&.NTS?
&D2#JAPJPAG&.NTST'P
&D2#JAPJPAG&.NTS,5(
&D2#JAPJPAG&.NTS'5(
&D2#JAPJPAG&.NTS#5(
&D2#JAPJPAG&.NTS25(
"."- 8$n!tion 4ro$s
2unction groupsA type 2 programs are containers or unction modulesA and cannot be started using by entering their name directly$ 2unction modules are special
procedures that you can call rom other ABAP programs$ They can be started by a transaction code i they are constructed with screen low supportA similar to &odule
pools A type & programs$
<eer to 2unctions or the naming conventions or 2unction 7roupsA 2unction PoolsA 2unction &odules and their components$
".". S$bro$tine Pools
Subroutine poolsA type S programs are not e6ecutableA you cannot start them using a transaction code or by entering the program name$ #nsteadA they are containers
or common subroutinesA which you can call e6ternally rom other ABAP programs$ They cannot contain screens$
The naming standard used or custom developed Subroutine Pools is the same as that or custom developed e6ecutable reports and programsA see !ustom Developed
ABAPs$
.6ample
DS&&JP8< > !ustom subroutine pool or &aterials &anagementA Purchasing
"."/ #nterfa!e Pools
#nterace pools or interace deinitions are Type ; programs$ Gou cannot start type ; programs using a transaction code or by entering the program name$ They are
containers or global interaces in ABAP 'b%ects$
The !lass Builder tool in the ABAP Workbench is used to create interace deinitions$ <eer to the section 3 on the !lass 4ibrary or naming conventions used in
interace pools$
"."0 Class Pools
!lass pools or class deinitions are type O programs$ Gou cannot start type O programs using a transaction code or by entering the program name$ They are containers
or global classes in ABAP 'b%ects$
The !lass Builder tool in the ABAP Workbench is used to create class deinitions$ <eer to the section 3 on the !lass 4ibrary or naming conventions used in class pools$
8$n!tions
2unction modules are ABAP routines that are stored in a central unction library$ They are routines that support common unctions and may be used by many applications
system>wide$ 2unction &odules are contained in 2unction 7roups$
4ike orm routinesA unction modules encapsulate common program codeA and provide an interace or data e6change that acilitates the passing o import and e6port
parameters and tables$ ,oweverA unlike orm routinesA unction modules have their own memory area and do not share the memory o the calling ABAPA unless it is part o
the same unction group$
"."1 C$stom 8$n!tion 4ro$s
2unction group names are reely deinable up to a ma6imum length o */ alphanumeric characters$ The normal naming conventions or the irst character also apply to
unction groups$ BAC through BHC is reserved or SAP developmentA with BGC and BDC or customer use$
Naming Standard
( !ustom #ndicator D !ustomized 2unction 7roup
* Application Area E->1 charactersF Alphanumeric and BJC SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 Descriptive Te6t Alphanumeric and BJC
.6ample
D2#JAPJPAG&.NTS > 2unction 7roup or 2inancial AccountingA Accounts Payable Payments
When you create a new unction group the system automatically creates a main program called a 2unction PoolA containing two includes$ The name o the 2unction Pool
is assigned by the system$ #t is made up o the prei6 SAP4 ollowed by the unction group name$
.6ample
The unction pool name or unction group D2#JAPJPAG&.NTS will be SAP4D2#JAPJPAG&.NTS$
".*3 8$n!tion Pool #n!l$des
The include namesA automatically created with the unction poolA begin with B4C ollowed by the name o the unction groupA and conclude with B8HHC or BT'PC or the
T'P include$ The T'P include contains global data declarations that are used by all o the unction modules in the unction group$
The 8HH include identiies the unction modules within the group$ #t is generated and maintained through the 2unction BuilderA you should never maintain it manually$
.6ample
#ncludes or unction SAP4D2#JAPJPAG&.NTS are?
4D2#JAPJPAG&.NTST'P and 4D2#JAPJPAG&.NTS8HH
There may also be user deined includes in the unction pool or common routines o the 2unction 7roup$ These ollow the same naming convention but will be sui6ed
with B2nnC or 2'<& routinesA B#nnC or PA# &odulesA or B'nnC or PB' &odulesA where BnnC is a se=uential number starting at 5($
.6ample
2'<&A PA# and PA' include names are?
4D2#JAPJPAG&.NTS25(A4D2#JAPJPAG&.NTS#5(A and 4D2#JAPJPAG&.NTS'5(
".*" 8$n!tion 5od$le
The 2unction &odule name may be up to +5 characters long and should be describe the unction being perormed$ When a unction module is createdA a new include
entry is automatically made in the B8HHC include Edescribed aboveF$ The entry has the same ormat as described or the B8HHC includeA however the sui6 is changed to
B8nnC where BnnC is a se=uential number starting at 5($
Naming Standard
( !ustom #ndicator D !ustomized 2unction &odule
* Separator BJC
+>+5 2reely deinable te6t alphanumeric Purpose o unction module
.6ample
DJ!A4!84AT.JSP4#TJPAG&.NT
is the unction module to calculate split payments$
The include statement in program 4D2#JAPJPAG&.NTS8HH will be #N!48D. 4D2#JAPJPAG&.NTS85($ MDJ!A4!84AT.JSP4#TJPAG&.NT
Class Library
Through the !lass BuilderA a tool within the ABAP WorkbenchA you may createA deineA and test global ABAP classes and interaces$ The ollowing naming convention has
been deined by SAP or use within the SAP namespace$ # you do not observe the naming conventions or ob%ect types Eclasses and interacesFA conlicts will occur when the
system creates persistent classesA since it will be unable to generate the necessary co>classes$
".** Namesa!e for Comonents
A single namespace within a class is shared by?
All components o the class itsel EattributesA methodsA eventsA constructorsA interacesA internal data types in the classA and aliasesF$
All public and protected components o the superclasses o the class$
&ethod implementation has a local namespace$ The names o the local variables can obscure those o class components$
".*+ Naming Convention
The naming convention has been kept as general as possible to avoid adversely inluencing the naming o ob%ects$
As with other development ob%ectsA it is important to maintain a distinction between SAP ob%ects and !ustomer ob%ects$ 2ollowing the standard conventionA the BDJC
characters will be used to maintain this distinction between SAP and customer classes and interaces$ 4ocal classes and interaces do not need to ollow this
convention$
".*4 4eneral Remar2s
When you choose names or development ob%ectsA you should?
8se .nglish names
8se glossary terms when possible 2or e6ampleA D!4J!'&PANGJ!'D. instead o D!4JB8O<S
#n compound namesA use the underscore character EJF as a separator$ Since names are not case>sensitiveA this is the only character that you can use to separate
names$
Names should describe the actionA not the implementation o the action$ .6ample? P<#NTJ<.!TAN74.A not <.!TAN74.JT'JSP''4
".*- Conventions for (b)e!t Tyes
!lass and interace names in the class library belong to the same namespace as data elementsA tablesA structuresA and types$ They are maintained centrally in table
TAD#< and have a ma6imum length o +5 characters$
Class in the class library
D!4JPclass nameL
The class name should be made up o singular nouns$
D!4JP!'&PANGJ!'D.A D!4J7.N.<A4J4.D7.<JA!!'8NT
Interfaces in the class library D#2JPinterace nameL
The same naming convention applies to interaces as to classes$
D#2JSTAT8SJ&ANA7.&ANT
D#2J!,.!O.<
ocal classes in programs
!recommen"ation#
4!4JPclass nameL
The class name should be made up o singular nouns$
4!4JT<..J&ANA7.&.NT
ocal interfaces in programs
!recommen"ation#
4#2JPinterace nameL
The sane naming convention applies to interaces as to classes$
4#2JP<#NT.<
".*. Conventions for Comonents
!omponents o global classes and interaces may be used by only one class orA by the deining class and itCs subclasses$ AdditionallyA methods and events may be used
by all classes$ #n cases where the component is to be used by many classesA the usual naming standardA BDJC should be used to maintain distinction between SAP and
!ustomer ob%ects$
Metho" name
Pmethod nameL
&ethod names should begin with a verb?
4ocal method e6ample? 7.TJSTAT8SA
7lobal method e6ample? DJ!<.AT.J'<D.<
Events
Pevent nameL
.vent names should have the orm
PnounLJPparticipleL?
4ocal event e6ample? B8TT'NJP8S,.D
7lobal event e6ample? DJ!'&PANGJ!'D.J!,AN7.D
ocal type "efinitions $ithin a class
!recommen"ation#
TGJPtype nameL
TGJ#NT.<NA4JTGP.A TGJT<..J4#ST
Data "efinitions !variables#
Pvariable nameL
When you name variables within a class E!4ASS>DATA or DATAFA avoid using verbs at the
beginning o the name Eto avoid conlicts with method namesF$
4#N.J!'8NTA &A<OJP<#NT.DA &A<OJ!,AN7.DA STAT8S
Data "efinitions !constants#
!recommen"ation#
!'JPconstant nameL
!'J&AHJ4#N.A !'JD.2A84TJSTAT8SA !'JD.2A84TJW#DT,A !'J&AHJ<'WS
<ecommended naming conventions are not compulsory$ ,oweverA i you use prei6es or these class and interace namesA you should use those listed above$
Page 1! of 52 Customized Version For ISPAT Industries Limited
".*/ Con!rete 5ethod &es!ritions
Attribute access
SE%&'attribute name() *E%&'attribute name(
&ethods that access attributes o any kind should be preaced with 7.TJ or S.TJ$
7.TJSTAT8S Elocal methodF S.TJDJ8S.J!'8NT Eglobal methodF
Event han"ler metho"s
+N&'event name(
&ethods that handle events should begin with 'NA ollowed by the name o the event that they handle$
'NJB8TT'NJP8S,.D Elocal methodF 'NJDJB8TT'NJP8S,.D Eglobal methodF
Metho"s that perform type conversions AS&'ne$ type(
ASJST<#N7 Elocal methodF ASJDJ#S'!'D. Eglobal methodF
Metho"s that return a ,oolean value
These methods may not return any e6ceptions$
<ecommendation? 8se SPA!. and RHR to
represent alse and true respectively$
IS&'a"-ective(
#SJ'P.N Elocal methodF
#SJDJ'P.N Eglobal methodF
Chec. metho"s
CHEC/&'ob-ective(
!,.!OJA8T,'<#DAT#'N Elocal methodF
!,.!OJDJP<'!.SSJDAT. Eglobal methodF
".*0 Lo!al Conventions 9ithin 5ethods
($*1$( 2or Parameters
Parameters are regarded rom the point o view o the method that implements them$ As these are not shared with other classesA no customer speciic naming
convention is needed$
IMP+0%IN* parameters IM&'parameter name(
E1P+0%IN* parameters E1&'parameter name(
CHAN*IN* parameters CH&'parameter name(
0ES2% 0E&'result(
($*1$* 2or .6ceptions
The ollowing table contains a series o possible e6ception names that can also be used generically Eor e6ampleA N'TJ2'8ND could also be used as
DAT.JN'TJ2'8NDF
E1CEP%I+N Meaning
A!T#'NJN'TJS8PP'<T.D The re=uested action or unction code is not supported$
!AN!.44.D
# a method uses a dialog to ind out what has to be dome Eor e6ampleA a list o choicesFA and the user chooses
S!ancelSA you can set this e6ception$
.H#ST#N7 A new ob%ect that you want to create already e6ists in the database$
2A#4.D The method could not be e6ecuted because o the current environment$
$$$J2A#4.D Part o the method could not be completed because o the current environment$ .6ample 'P.NJ2A#4.D
2'<.#7NJ4'!O Data is locked by another user$
#N!'NS#ST.NT 'b%ect data in the database is inconsistent$
$$$J#N!'NS#ST.NT The component data or T o an ob%ect in the database is inconsistent$
#N"A4#D The ob%ect data entered is incorrect Eor e6ampleA company code does not e6istF$
$$$J#N"A4#D The component data entered or an ob%ect is incorrect$ !ompare N'TJ:8A4#2#.D$
#NT.<NA4J.<<'< 4ast resort$ 'nly use this e6ception i you cannot be more precise about the nature o the error$
N'TJA8T,'<#D.D The user does not have the re=uired authorization$
N'TJ!8ST'&#D.D The ob%ect re=uested is not correctly customized$
$$$JN'TJ!8ST'&#D.D The component T o the re=uested ob%ect is not correctly customized$
N'TJ2'8ND 8nable to ind the re=uested ob%ect$
$$$JN'TJ2'8ND 8nable to ind component T o the re=uested ob%ect$
N'TJ:8A4#2#.D The combination o input parameters is insuicient to run the method$ !ompare #N"A4#D$
$$$JN'TJ:8A4#2#.D 'ne parameter o the method is not =ualiied$
N8&B.<J.<<'< .rror assigning a number$
SGST.&J.<<'< This e6ception is set i the Basis system returns an une6pected error message$
* ABAP Tyes and (b)e!ts
ABAP distinguishes between types and ob%ects$ Types are descriptions that do not occupy memory$ 'b%ects are instances o typesA and do occupy their own memory space$
A type describes the technical attributes o all o the ob%ects with that type$
ABAP types orm a hierarchy$ 'b%ects in ABAP relect the same hierarchy$
Types and 'b%ects are deined to the ABAP via declaration statements that are the irst part o an ABAP program or processing blockA e6cluding dialog modules and events
where they are disallowed$
7lobal declarations are used to declare ob%ectsA classes and selection screens or the ABAP program and all internal processing blocks Edialog and unction modulesA
methodsA eventsA or subroutinesF$
4ocal declarations are used to declare ob%ects within a processing block Eunction modulesA methodsA or subroutinesF$
*." 4eneral Standards for the &e!laration of ABAP Tyes and (b)e!ts
The names o ob%ects and types must consist o the characters MA > DNA M5 @ 3N and MJN and must begin with an alphabetic character$
Data ob%ect names should be meaningul$ Names should describe the ob%ect the ield representsA itCs use andA where possibleA reerence a dictionary ield name or the
ield type attributes$ The use o .nglish terms is recommended or selection screen ields Ee6ample? SJ8S.<#D 4#O. BOP2>8SNA& instead o SJ8SNA& 4#O. BOP2>
8SNA&F$
Naming conventions used or data ob%ects are consistent with SAPCs naming convention or !4ASS>DATA ob%ectsA see section (5 !lass 4ibrary$
While long ield namesA up to +5 charactersA are supported or most ield typesA keep names as short as possibleA without losing their meaning$
*.* &ata Tyes and (b)e!ts &e!laration
The ABAP statements used to declare data types and ob%ects EieldsF include?
!'NSTANTS > deinition o simple ields or structures that are staticA having predeinedA unchanging values in the program$
!4ASS>DATA > To declare static variables within classes$
DATA @ deinition o simple ieldsA structured data ob%ectsA internal tables and shared data areas in the program or processing block$
2#.4D>7<'8PS @ deines a dynamic work area in the program where ields rom dierent sources may be gathered$ The #NS.<T statement deines which ields
belong to the ield>group at runtime$
2#.4D>SG&B'4S @ deinition o a symbolic ield in the program or processing block$ The value and type o the ield is determined at runtime with the ASS#7N
statement$
<AN7.S > deines an internal table with the same structure as in S.4.!T>'PT#'NSA but without linking it to a selection screen$
STAT#!S @ similar to !'NSTANTS but used or the deinition o local variables in a subroutine or unction module$
TAB4.S @ creates a database tableA view or structure work area in the program or processing block$ !annot be used in ABAP 'b%ects
(
TGP.S @ deines reerence variables or data types or ob%ect types whose content is dynamically determined at runtime$
NOTE !" #$#P %bjects are the object&oriented extension of #$#P"
*$*$( "ariables
Data ob%ects declared by BDATACA B!4ASS>DATAC and B<AN7.SC all into the broad category o data variables$ They allow you to store changeable data under a
particular name within the memory area o a program$ #n their declarationA they are deined as one o the eight elementary types in ABAP$
2i6ed>4ength .lementary Types include?
2our character types?
!haracter E!FA Numeric character ENFA Date EDFA and Time ETF$
'ne he6adecimal type?
Byte ield EHF$
Three numeric types?
#nteger E#FA 2loating>point number E2F and Packed number EPF$
"ariable>4ength .lementary Types include?
There are two predeined types in ABAP with variable length?
ST<#N7 or character strings
HST<#N7 or byte strings
"ariables are used or a variety o purposesA including accumulatorsA countersA lagsA variable length stringsA work areasA etc$
Naming Standard
When you name variables use meaningul names indicating the purpose o the ield$ Within the !4ASS B8#4D.<A avoid using verbs at the beginning o the
name Eto avoid conlicts with method namesF$
(>+5 Name Alphanumeric and BJC "ariable name 9 usage
.6ample
8PDAT.JSTAT8S > 8PDAT. status lag
4#N.J!'8NT > 4#N. counter
4ASTJ'<D.<JN'> 4AST '<D.< N8&B.< work area
!'STJT'TA4 > !'ST total
#NP8TJT.HT > i6ed length #NP8T te6t
4ASTJ8PDTJT#&. > 4AST 8PDAT. T#&.
N+%E3 This naming convention applies to all variablesA e6cept 2ield Strings and #nternal Tables$ Speciic naming conventions or these variablesA as
well asA other ABAP Types and 'b%ects ollow$
*$*$* !onstants
ABAP keywordsA B!'NSTANTSC or BSTAT#!SC are used to declare constants$ !onsistent with the !4ASS>DATA naming standardsA constants should be prei6ed
with the characters B!'JC$
Naming Standard
( !onstant #dentiier ! !onstant #dentiier
* Separator BJC
+>1 !onstant 4abel Alphanumeric and BJC !onstant 4abel
.6ample
!J!.NT8<G > !onstant or B!enturyC
*$*$+ 2ield>7roups
The sort header is always named ,.AD.<A while other ield>groups are reely deinable$
Naming Standard
(>+5 Name Alphanumeric and BJC 2ield>group name
.6ample
'<D.<J#T.&S > 2ield>7roup or '<D.< #T.&S
*$*$) 2ield Strings
2ield strings may be o type !A character string or type HA byte string$ They are similar to their counter>part data types ! or HA e6cept that they are variable
length ields$
Naming Standard
(>+ #dentiier STJ String #dentiier
)>+5 Name Alphanumeric and BJC String name
.6ample
STJ#NP8TJT.HT > String B#NP8TJT.HTC
*$*$- 2ield>Symbols
2ield>Symbols are a distinct ield type in ABAP and must be enclosed with the BPC and BLC Eless than and greater thanF characters$ While they are distinctA it is
recommended that the ield>symbol name be based on the naming standard or the ield type it represents$
Naming Standard
( 4ess than character P Beginning o 2ield>symbol Name
* Name E*1 characters ma6imumF Alphanumeric and BJC 2ield>Symbol Name
Sui6 7reater than character L .nd o 2ield>symbol Name
.6ample
PSTJ#NP8TJT.HTL > 2ield>Symbol or #NP8TJT.HT type string$
PTGJT.HTL > 2ield>Symbol or T.HT where the type is determined at run>time
*$*$/ #nternal Tables
Naming Standard
(>* #dentiier #J #nternal Table #dentiier
+>+5 Name Alphanumeric and BJC Table Name
.6ample
#J74P!A > #nternal table or database table 74P!A
#J7.N.<A4J.BJ2#.B @ #nternal table or table 7.N.<A4J.BJ2#.B
*$*$0 Tables
The database tablesA structures or views reerenced by the BTAB4.SC ABAP keyword must e6ist and be activated in the ABAP Data Dictionary$ Naming standards
or these ob%ects are discussed in section / Dictionary 'b%ects$
*$*$1 Types
Gou can build comple6 structures in ABAP with the BTGP.SC keyword$
Naming Standard
(>+ #dentiier TGJ Type #dentiier
)>+5 Name Alphanumeric and BJC Type name
.6ample
TGJP.<S'NN.4J#N2' > a TGP.S deinition or personnel inormation which could reerence Data Dictionary structures or name ElastA irstA middleFA
address Ehouse noA streetA cityA stateA D#PFA Phone NumberA SSNA etc$
*.+ (b)e!ts Tyes &e!laration
The ABAP statements used to declare ob%ect types include?
!4ASS 9 .ND!4ASS @ declaration and implementation o a !4ASS in ABAP 'b%ects in the program$
D.2#N. 9 .ND>'2>D.2#N#T#'N @ deinition o a macro$
#NT.<2A!. 9 .ND#NT.<2A!. @ deines an interace in ABAP 'b%ects in a program$
&.T,'D 9 .ND&.T,'D @ implementation o a &.T,'D in a !4ASS in ABAP 'b%ects in the program$
*$+$( ABAP 'b%ects in ABAP 'b%ect 'riented Programming
<eer to section 3 !lass 4ibrary or naming conventions or ABAP 'b%ect !4ASSesA #NT.<2A!.s and &.T,'Ds$
*.4 Sele!tion S!reen
The ABAP statements used to declare selection screens include?
PA<A&.T.<S @ deines program selection screen parameters$
S.4.!T>'PT#'NS @ deines program selection screen variables or database tables accessed by the program$
S.4.!T#'NJS!<..N @ is used to customize the selection screen by the addition o commentsA push buttons and the grouping o S.4.!T>'PT#'NS and
PA<A&.T.<S$
*$)$( Parameters
Parameters are used in .6ecutable ABAP ProgramsA type ( programs$ Their names are limited to 1 characters$
Naming Standard EParametersF
(>* #dentiier PJ Parameter #dentiier
+>1 Parameter 4abel Alphanumeric and BJC Parameter 4abel
.6amples
PJBSTGP 4#O. .OO'>BSTGP > Parameter or Purchasing Document !ategory
PJ<D.ST 4#O. 7.N.<A4J.BJ2#.B>4'7D.STJ,TTP @ Parameter or <2! Destination in 7eneral !ustomizing Table or .lectronic Banking
*$)$* Select>'ptions
Select>'ptions are used in .6ecutable ABAP ProgramsA type ( programs$ Their names are limited to 1 characters$
Naming Standard ESelect 'ptionsF
(>* #dentiier SJ Select>'ption #dentiier
+>1 Name Alphanumeric and BJC Select>'ption 4abel
.6ample
SJ"ND<N' 2'< .OO'>4#2N< @ Select>'ption or "endorCs Account Number
*.- 5a!ros
The ABAP statements D.2#N. 9 .ND>'2>D.2#N#T#'N are used to declare macros$ While macros are still supported in ABAPA you should use subroutines E2'<&s or
28N!T#'NsF as these are ully supported by all the ABAP Workbench tools$
Naming Standard
(>* &acro #dentiier mJ &acro #dentiier
+>*5 &acro 4abel Alphanumeric and BJC &acro label
.6ample
&J2'<&ATJ8S.<J&.SSA7. > &acro B2'<&ATJ8S.<J&.SSA7.C
Te6t 'lements
Te6t elements allow you to create language>independent programs$ Any te6t that the program sends to the screen can be stored as a te6t element in a te6t pool$ Dierent
te6t pools can be created or dierent languages$ When a te6t element is changed or translatedA there is no need to change the actual program code$
*.. Te6t Symbols
A te6t symbol is a named data ob%ect in an ABAP program$ #t is generated when you start the program rom the te6ts deined in the te6t pool o the program$ #t
always has the data type ! and may have a ma6imum length o (+* characters$
A three>character #D identiies each te6t symbol$ Te6t symbols are reerenced in the ABAP using the orm T.HT>PtidL where PtidL is the + character te6t
identiication$ #n custom designed programsA te6t symbols may be any + character stringA howeverA should you customize an SAP ABAP programA you should only use
te6t symbols in the 355 number range or prei6 them with the BDC customized ob%ect indicator$
Naming Standard
(>+ #dentiier alphanumeric Te6t #d
.6ample
(*+ > Te6t symbol B(*+C in a custom program
(*) @ Te6t symbol B(*)C in a customized SAP program
D5( @ Te6t symbol BD5(C in a customized SAP program
*./ Sele!tion Te6ts
Selection te6ts allow you to replace the standard te6ts ESelect>'ption or Parameter ield namesF that appear ne6t to input ields on selection screens with te6t
elements$ Gou can either use a short te6t deined in the ABAP Dictionary or create your own te6ts$
Naming Standard
The selection te6t name is inherited rom the Select>'ption or Parameter ield name in the ABAP program$
.6ample
PJ8S.<#D > selection te6t name or Selection Screen Parameter BPJ8S.<#DC$
SJP4ANT > selection te6t name or Selection Screen Select>'ption BSJP4ANTC$
*.0 List %eadings
When you create a print or screen list in a programA you have the option to create your own list and column headings$ 4ist and column headings are ree ormat te6t
whose content is at the discretion o the designer 9 developer$
S!reens
Screens are the most common method o user dialog used in ABAP programs$ They are deined in the Screen PainterA and can be deined or any e6ecutableA module pool or
unction pool program$
Screen numbers must be uni=ue within the program and can be any )>digit number greater than 5$ The number (555 is reserved or table screens and report selection
screens$ #nitial screens o transactions are oten given a number whose last three digits are (55 Eor e6ampleA +(55F$
!ustom screens within a SAP module pool must use screen numbers above 3555$ All other numbers are reserved or SAP$
Naming Standard
(>) Screen Number 3555>3333 !ustom Screen number$ Screen numbers per program should be incremented by (5$
.6ample
3555 > Screen number 3555 or an SAP program
5(55 > Screen number (55 or a customer developed program
47# #nterfa!e
*.1 47# Stat$s
A 78# Status is an independent component o an ABAP programA created using the &enu Painter$ The 78# status describes the range o unctions available to the user
on a screen$ .ach unction has an associated unction code and logic contained in the P<'!.SS A2T.<#NP8T EPA#F or P<'!.SS 'N ,.4P><.:8.ST or P<'!.SS 'N
"A48.><.:8.ST modules$
78# Status names may be up to *5 characters long and must be uni=ue within the program$ Should you have to create a customized 78# Status or a SAP programA
prei6 the status name with the BDC customized indicator$
Naming Standard
(>*5 78# Status Name 3555>3333 !ustom 78# Status name$ Start with a BDC when adding a custom 78# Status to an SAP program$
.6ample
4#STJS,'W @ 78# Status B4#STJS,'WC or a custom program 9screen$
DJ4#STJS,'W @ 78# Status BDJ4#STJS,'WC or a customized SAP program 9screen$
*."3 47# Title
A 78# Title is an independent component o an ABAP programA created using the &enu Painter$ #t contains a te6t lineA up to /5 characters longA which is displayed in
the window header line$
78# Title names may be up to *5 characters long and must be uni=ue within the program$ Should you have to create a customized 78# Title or a SAP programA prei6
the status name with the BDC customized indicator$
Naming Standard
(>*5 78# Title Name 3555>3333 !ustom 78# title name$ Start with a BDC when adding a custom 78# Status to an SAP
program$
.6ample
4#STJS,'W @ 78# Title B4#STJS,'WC or a custom program 9screen$
DJ4#STJS,'W @ 78# Title BDJ4#STJS,'WC or a customized SAP program 9screen$
Transa!tions
A transaction covers a logical process in the <9+ system$ 2rom the point o the user it represents a sel>contained unit o work$ Gou can maintain transaction codes using the
ABAP Workbench 'b%ect Navigator or by choosing Development 'ther tools Transactions rom the SAP .asy Access menu or by using the Transaction &aintenance
transaction ES.3+F$
When creating a transactionA you must irst input the new transaction code and a short te6t description or the transaction$ Then you must choose the type o transaction
rom the BStart 'b%ectC list in the !reate Transaction Screen$ .ach transaction is associated with a development classA which is inherited rom the program called by the
transaction$ AdditionallyA you can protect the transaction against unauthorized use$ To do thisA enter the name o an authorization ob%ect in the corresponding ield$
To enter values or the ields o the authorization ob%ectA choose "alues$
*."" &ialog Transa!tion
#n a dialog transactionA the low o the program is determined by a se=uence o screens$ 2or Dialog TransactionsA will be prompted to provide the program nameA initial
screen number and authorization ob%ect and values$
*."* Reort Transa!tion
#n a report transactionA you use a transaction code to start an e6ecutable program Etype (F$ Gou will be prompted to provide the program nameA initial screen number
and authorization ob%ect and values$ 2or <eport TransactionsA the initial screen is the report selection screen$
*."+ (( :Class 5ethod; Transa!tion
TbdT re=uires development access
*."4 ,ariant Transa!tion
Transaction variants allow you to preset values or ields in a transactionA set ield attributesA or hide entire screens$ #n the SAP <eerence #&7A you can create
transaction variants by choosing Basis !omponents Application Personalization Tailoring o Application Transactions !onigure Transaction><elated Display "alues or
2ields ETransaction S,D5F$
To deine a variantA enter the name o the transaction and the name o the variant$ Gou can then use the new transaction code to start the special variant o the
transaction$
*."- Parameter Transa!tion
Parameter transactions allow you to pre>assign values to ields on the initial screen o a transaction$
'nce you have entered a transaction code and short descriptionA choose transaction type Transaction with parameters EParameter transactionF$ .nter the UUUU tbd Gou
can hide the initial screen o a parameter transaction i you have speciied values or all o its ields$
*.". C$stom Transa!tion Names
Transactions are deined by transaction codesA which are *5 characters long$
Naming Standard
( Type D !ustomized 'b%ect
* Application Area E- to 1 charactersF Alphanumeric and BJC SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
sui6 8ni=ue #dentiier Alphanumeric and BJC Descriptive te6t
.6ample
D!SJA7J4A8N!,JS!,.D > Transaction or !ustomer ServiceA Service AgreementsA 4aunch Schedules
Logi!al &atabase
4ogical database names can be up to *5 characters long$ !ustom logical databases must be distinct rom SAP delivered ones$ The standard naming convention o prei6ing
the name with a BDC is used$ This is ollowed by the SAP Application Area and a uni=ue identiier$
Naming Standard
( !ustom #ndicator D !ustomized 4ogical Database
* Application Area E->1 charactersF Alphanumeric and BJC SAP Application AreaA reer to Appendix A SAP Application Hierarchy
Sui6 8ni=ue #dentiier Alphanumeric and BJC 8ni=ueA descriptive te6t
.6ample
D4.JW&T<ANS2<'<D<S > 4ogical Database or 4ogistics .6ecution Warehouse &anagement Transer 'rders
*."/ C$stomer Sele!tion ,iews
4ogical databases are delivered with a SAP STANDA<D selection view$ These views deine the tables and ields supported or the logical databaseA and which are
automatically included in the ABAP report selection screen when a logical database is identiied in the ABAP report attributes$ 8sing logical data bases with its selection
view and the 7.T Ptable nameL unctionality o ABAP relieves the programmer rom having to code speciic S.4.!T statements to obtain related data$
!ustomers may create a custom view or a logical database$ The origin o the view must be B!8SC and the name o the view must be BSTANDA<DC$
Note that only two selection views are allowed per logical databaseA the SAP STANDA<D one and the customerA !8S STANDA<D one$ AlsoA note that i a customer
speciic view e6ists it will be used instead o the SAP view$
S'T/4'T Parameter #ds
7.T9S.T parameter #ds reerence dynamic memory assigned to each logged on user$ They are associated with re=uently used data ields in SAP dialogs Esuch as !ompany
!odeF and are used to store and retrieve predeined values rom the user proile or the most recently used values$
!ustom S.T97.T Parameter #ds may be created and associated with dialog screen ields$ The name may be up to *5 characters long and ollows the ollows the customized
ob%ect naming conventionA beginning with a BGC or BDC and ollowed by descriptive te6t$
Naming Standard
( !ustom #ndicator D !ustomized indicator
.6ample
DDDJ&#SS#'NJN8&B.< @ 7.T 9 S.T Parameter #D
Area 5en$s
!8A E!ommon 8ser AccessF area menus o previous releases are converted to tree navigation in <elease )$/A$ The menu contents are automatically copied into a new data
structure in 8pgrade to <elease )$/A or higher$ Gou can edit Area &enus with a new maintenance interace EArea &enu maintenance transaction? S.)+F$
Area menu names may be up to +5 characters long and should ollow the customized ob%ect naming conventionA beginning with a BDC and ollowed by the application area
and descriptive te6t$
Naming Standard
* Application Area E->1 charactersF Alphanumeric and BJC SAP Application AreaA reer to Appendix A SAP Application Hierarchy
.6ample
D!AJTS>T#&.J<.P'<T#N7 @ Area menus or !ross>Application Time <eporting unctions
5essages
8ser and system messages used during program or report processing are organized in SAP by &essage !lass and &essage Number$ Transaction S.3( is used to create and
maintain these &essage !lasses and &essages$
*."0 5essage Classes
&essages !lasses group user and system messages by speciic application$ A total o 333 messages can be created per message class$ A message class nameA
application area can be up to *5 characters long$ !ustom message classes start with a BDC$
Naming Standard
( !ustom #ndicator D !ustomized &essage !lass
*>) Application Area E*>+ charactersF SAP Application AreaA reer to Appendix A SAP Application Hierarchy
.6ample
D2# !ustom &essage !lass or 2inancial
*."1 5essage N$mbers
The standard SAP &essages should not be changed and should be used whenever possible$ Additional messages can be added starting at 355 within a SAP message
class$ When added to a custom message classA the number may be range between 55( and 333$
Naming Standard
(>+ Number <ange 55(>333 &essage Number
.6ample
355
7eneral use recommendations?
.ach message class should have a generic message classA consisting o ) substitution variablesA BVCs only$ This corresponds to the ) optional BW#T,C parameters
o the ABAP &.SSA7. statement$
4eave some gaps in the number range when creating new messages such that messages o similar topics can be grouped together$ Suggest using a gap o (55$
Test Cases
!ustomer created test cases ollow the general customized ob%ect>naming standard$ The +5>character name begins with a BGC or BDC and is ollowed by descriptive te6t$
Naming Standard
.6ample
D&&JP8<J!<.AT.JP'J2<'&J&<P @ test procedure or the !<.AT. o a P' rom an &<P re=uirement$
ABAP <$eries and 7ser 4ro$s
ABAP =ueries are geared towards end>user computing and allow users without any knowledge o the ABAP programming environment to create and run their own reports$
ABAP =ueries are created and numbered within 8ser 7roups which are associated with 2unctional Areas97roups$
*.*3 7ser 4ro$s
8ser 7roups group a number o similar users together or the purpose o creating and running ABAP =ueries$ 8ser 7roups are named according to the SAP or
!ustomer application area$ They have a (*>character application area ield and a +5>character description ield$
Naming Standard
4iel" Values Meaning
8ser 7roup Name Alphanumeric and BJC 2ully =ualiied SAP Application AreaA rom the Application ,ierarchy as seen in the ob%ect Navigator$ &ay be the same
as the application area used in the 2unctional Area name$
8ser 7roup Te6t Alphanumeric &eaningul nameA meant to describe the task area o the user group
.6ample
2#JAPJAPJPT > 2# Accounts Payable Payments user group$
*.*" 8$n!tional Areas
A unctional area is a special view o a logical databaseA tableA view or se=uential ile$ They are a prere=uisite or creating ABAP :ueries$
When you create a unctional areaA you will be prompted or?
2unctional Area Name is a *)>character name identiying the ully =ualiied SAP Application Area as seen in the 'b%ect Navigator display o the SAP
Application ,ierarchy$
Title or description o the 2unctional AreaA up to /+ characters
Authorization 7roup ollowing the !"S #T SAP Security and Authorization Policy$
2i6ed Point Arithmetic !heckbo6 must be checked i decimal precision is needed in the =ueries$
Data Source$ Gou must determine the data source or the unctional area$ #t can be a logical database orA a tableA view or structure$
# you choose a functional area $ith logical "atabaseA the logical database name must be provided$ 'ptionallyA you may also provide the selection screen
version i you do not want the standard version deined or the logical database$
# you choose functional area $ithout logical "atabaseA speciy the data dictionary tableA structure or view name and describe the retrieval method$ A
program generated or the unctional area does retrievals based on the settings in the window bo6 or unctional areas without logical databases$ The
ollowing combinations are possible?
Database +b-ect %ype 0etrieval +ption
Database Table Direct <ead
Database "iew Direct <ead i only one table in view$ Table ;oin i multiple tables in view$
Structure Se=uential Dataset Epath and ilenameF$
Note? The program name is proposed by the system and does not need to be changed$
Naming Standard
( 2unctional Area Name Alphanumeric and BJC 2ully =ualiied SAP Application AreaA rom the Application ,ierarchy
Sui6 'ptional te6t Alphanumeric and BJC 'ptional te6t to provide distinction between overlapping unctional areas
.6ample
2#JAPJAPJPT J&S2! > 2unctional Area or 2inancial Accounting Accounts Payable Basic 2unctionsA Payment Transactions at &arshal Space 2light !enter
2ollowing is the 2unctional Area deinition screen or this e6ample$
*$*($( 2unctional 7roups
The unctional group is a sub>ob%ect o the unctional area$ #t identiies ields contained in the database ob%ect Elogical databaseA tableA view or structureF that
are eligible or use in =ueries$ 'nce the unctional area is createdA you must deine a unctional group or groups$ Note that these ields cannot be shared among
groups$
2unctional groups are created in the B!hange 2unctional Area B transaction$ They have a *>character name and a *) character short description$
Naming Standard
2unctional 7roup #D Alphanumeric * character group identiication
2unctional 7roup Te6t Alphanumeric &eaningul name o the 2unctional 7roup
.6ample
(5 Payee #normation group
*5 Payer #normation group
+5 Processing Data group
)5 Payment Detail group
*.** ABAP <$eries
ABAP :ueries are customer named within each 8ser 7roup$ Gou can use up to () characters to describe the =uery$ &eaningul names are recommended$
Naming Standard
:uery Name Alphanumeric and BJC 8ni=ue descriptive name within the 8ser 7roup
:uery Title Alphanumeric &eaningul title o the ABAP :uery
.6ample
"ND<JPAGSJ2P "endor Payments by 2iscal Period
A$thori=ation (b)e!ts
An authorization ob%ect combines up to (5 authorization ields that are checked using the AND connective$ !ustomized authorization ob%ects are re=uired when
applying non>standard authorizations to SAP unctionsA or applying security to customized unctions$
An authorization ob%ect name is up to (5 characters long
Naming Standard
( !ustom #ndicator D !ustom Developed 'b%ect
sui6 8ni=ue id alphanumeric
.6ample
DPSJ!A2555 > Pro%ect SystemsA Payments 'b%ect 555
Bat!h >ob Names
Batch %obs include programs and reports that are e6ecuted as part o a scheduled batch run$ The batch %ob name may be up to +* characters long$
Naming Standard
( !ustom developed D !onstant
* 2re=uency EScheduleF D Daily
W Weekly
& &onthly
: :uarterly
G Gearly
' 'ther > Special dependencies
A Ad>hoc > 'ne time
! !onversions
+ Separator J
) Application area SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy
This ield varies in length rom - to 1 characters Ee$g$ 2#>APA #S>PS>2&F
Sui6 ( Separator J
Sui6 * 8ni=ue %ob identiier alphanumeric A description o the %obCs purpose$ 8p to () characters may be used$
Spaces should not be used as these will be suppressedA use underscores instead Emay not start or end
with underscoresF$ This identiier is also used or the batch %ob variant name$
*0 Separator J
*1>+5 Batch type code <PT !reates a <eport
BD! 7enerates a BD! session
8PD 8pdates DatabaseEsF
.HT .6tracts inormation
.6ample
D'J&&JP8<J2'<.!ASTJ!,.!OJBD!
This %ob? > #s custom developed EalwaysF
> #s e6ecuted periodically but variable
> #s part o the Purchasing unctional area
> #s used in the 2orecast !heck process
> #s a BD! session generator Eno database updatesF
B&C Session
BD! session names do not have to be uni=ue$ .nd users may be re=uired to run BD! sessions so it is important the naming convention is ollowed$
A BD! session name can be up to (* characters long$
Naming Standard
( Application Area SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy This ield varies in length
rom - to 1 characters Ee$g$ 2#>APA #S>PS>2&F
sui6 2ree 2orm 5>D )>0 characters to provide uni=ueness within application area
.6ample
2#>A&JAS5* > A BD! session or the Asset &anagement change transaction$
Change Re?$est &es!rition
A change re=uest description may be up to /5 characters in length$ 2urther detail can be put in the long te6t associated with the re=uest$
Naming Standard
Position Description Possible
Values
Meanings
( Application Area SAP Application AreaA reer to Appendi6 A @ SAP Application ,ierarchy This ield varies in
length rom - to 1 characters Ee$g$ 2#>APA #S>PS>2&F
Sui6 ( !olon ?
Sui6 * Description o the
!hange <e=uest$
alphanumeric 2ree te6t$ #nclude reerence to?
> implementation pro%ect phase
> change management number ES#<F
.6ample
PGJ8S? WP(/S< > !onig$ or Payroll <elease (
&o!$mentation
.ach custom development is e6pected to have a well>documented history rom problem or needs identiication through unctional designA technical designA programming
and testing$ These documentation and procedure standards are addressed in B"ocument to be name"5 managed by 6Change Management system to be name"57
'vents
SAP events are used to establish a dependency between two processesA e$g$ an e6ternal system initiates a SAP event Evia SAP."T <emote 2unction !allF to start a
scheduled SAP %ob to read a ile %ust transerred$ .vent names may be up to +5 characters long$
Naming Standard
( !ustom #ndicator D !ustomized .vent
* Application area E->1 charactersF SAP Application areaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 Description Description
.6ample
D2#JB4JBANOJD4'AD > A custom event identiying that a download ile is available rom a bank$
#nbo$nd 8iles
#nbound iles are iles that contain data read by ABAP programs$
Naming Standard
( !ustom #ndicator D !ustomized 2ile
G Temporary 2ile
* Application area E->1 charactersF SAP Application areaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 ( 8ni=ue identiier Descriptive name
Sui6 * 2ile type e6tension $DAT
.6ample
DSDJB#4JSGST.&H$DAT > !ontains update data or Sales Billing rom System H$
Non@ABAP Programs
This includes all command iles and non>SAP programs that may be called by SAP Eor customizedF unctions$ 8se the naming convention or .6ecutable ABAP <eports and
Programs unless you are restricted to short names$ 2or short names use the ollowing standard$
Naming Standard Eshort program name spaceF
( !ustom #ndicator D
G
!ustom Developed
Temporary
* Application hierarchy
E*>+ charactersF
SAP Application ,ierarchyA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 ( 2unction <
.
"
!
#
4
'
'nline <eports
Batch .6tract
8pdate
!onversion
#nterace
#nclude
'ther
Sui6 * Program Name9Number 8ni=ue #dentiier
.6ample
D2#<!4ST > !ustomA non>ABAP 2inancial <eport named !4ST
($tbo$nd 8iles
'utbound iles include all iles that are createdA or are written to by ABAP or non>ABAP programs$
Naming Standard
( !ustom indicator D !ustom DevelopedA Permanent
G Temporary
* Application area
E->1 charactersF
SAP Application areaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 ( 8ni=ue identiier Descriptive name
Sui6 * 2ile type e6tension $DAT
.6ample
D#SJPSJB8D7.TJ*55*$DAT > !ontains B8D7.T data e6tract or the Public Sector$
SAPS!rit
*.*+ Layo$t Set
4ayout sets deine what the pages in a te6t should look likeA and then edits the te6t accordingly or output to screen or printer$ 4ayout set names can be up to (/
characters long$
Naming Standard
( !ustom #ndicator D !ustom #ndicator
* Application Area E->1 charactersF SAP Application areaA reer to Appendi6 A @ SAP Application ,ierarchy
Sui6 Descriptive #dentiier Alphanumeric and BJC
.6ample? DA<J!<S7<#D > SAP 4ayout or Accounts <eceivable named !<S7<#D
*.*4 Standard Te6t #&
Te6t #Ds are deined in the #&7 in the application area they are associated withA and stored in table TTH#D$ # you must create a new #DA ollow the naming convention
below to ensure no overlap with SAP deined Te6t #Ds$
Naming Standard
( !ustom #ndicator D !ustomized Te6t #D
*>) 8ni=ue #dentiier alphanumeric 8ni=ue #dentiier
.6ample? D55( > Te6t #D D55(
*.*- Standard Te6t Name
This is the uni=uely identiying name o a standard te6t$ #t can be up to 05 characters long but should be kept to ewer than +5 characters as that are all that is
displayed in the maintenance screen$
Naming Standard
( !ustom #ndicator D !ustomized Te6t Name
*>+5 8ni=ue #dentiier Alphanumeric and special characters e6cept BAC and BWC 8ni=ue #dentiier
.6ample
DJ!"S #TJ!'N2#D.NT#A4#TGJT.<&S > Te6t Name
*.*. Styles
Deines a type o style sheet containing character and paragraph ormatting inormation$ The style name can be up to 1 characters long
Naming Standard
( !ustom #ndicator D !ustomer pro%ect
* Application areaA condensed Ee6clude
underscoresF E)>/ charactersF
SAP Application areaA reer to Appendi6 A @ SAP Application
,ierarchy
sui6 8ni=ue identiier alphanumeric
.6ample
D&&P8<5( > !ustomized Style 5( in &aterials &anagement Purchasing
T,AR, 'ntries
The table T"A<" contains entries reerenced by variants$ !ustomized entries can be madeA enabling variable parameters 9 selection options to be used in variants$
Naming Standard
( !ustom #ndicator D #dentiies as custom developed
* "ariable type P or S Parameter or Selection "ariable
+>+5 Descriptive name alphanumeric
.6ample
DP.NDJ'2J&'NT, > A parameter variable or the end o month$
8ield e6itsA
*.*/ 8ield e6itsA definition
2ield e6its must ollow the convention? 2#.4DJ.H#TJ66666 where 66666 is the name o the associated data element$
.ach ield e6it should be assigned to speciic programs and screens$ 7et using technical help$
.ach ield e6it application should be speciied as a separate unction group$ &ultiple versions o ield e6it will ollow the standard SAP convention o
2#.4DJ.H#TJ66666J(9*9+9) etc$ This enables each ield e6it unction module to be application speciic$
*.*0 8ield e6itsA donBts
As o +$52A you cannot issue the ollowing commands rom a ield e6it?
&.SSA7. W9# $$$$$$ Emessage . and S are okF
!A44 S!<..N9D#A4'79T<ANSA!T#'N
S8B&#T
!'&&#T9<'44BA!O W'<O
ST'P
<.;.!T
.H#T 2<'& ST.P4''P
!'&&8N#!AT#'N <.!.#".
#n additionA ield e6its cannot be used or check bo6es$ These are deemed to be graphical elements and have no input9output status$ These values may be accessible
in a user e6it$
C$stomer 'nhan!ements C 'nhan!ement Pro)e!ts
SAP has anticipated certain customer re=uirements or enhancements to the SAP standard system$ These potential enhancements are at pre>planned locations within dialog
EscreenF or program logic$ They allow the customer to modiy predeinedA empty or unused programsA screens or screen unction codes$
8sing customer e6its is preerred over options to modiy SAP code or create custom transactions as the upward compatibility is guaranteed by SAP$ This is because %umps to
e6its are predeined in the standard sotware and the validity o the call interace are both retainedA even in uture release upgrades$
!ustomer enhancement pro%ect names are 1 characters long and may be used by SAP$
Naming Standard
( !ustom #ndicator D !ustomer pro%ect
* Application areaA condensed Ee6clude underscore SAP Application areaA reer to Appendi6 A @ SAP Application ,ierarchy
charactersF E)>/ charactersF
sui6 8ni=ue identiier alphanumeric
.6ample
D4'&D&&5 > &aterial master data customer enhancement pro%ect
*.*1 C$stomer '6its
All user e6its start with .H#T$ The programmer locates the user e6it that is applicable and alters the speciied #N!48D. or 28N!T#'N module$ Beore a user e6it can be
activatedA an enhancement pro%ect must be speciiedA itCs associated ob%ects deined and then the pro%ect is activated to implement the e6it$
Aendi6 A C SAP Ali!ation %ierar!hy
The ollowing list is rom the SAP Application ,ierarchy as seen in the 'b%ect Navigator$ The hyphens B>B in the 'b%ect Navigator have been replaced with underscores BJC to
comply with SAPCs development ob%ect naming standard$
Application Hierarchy 8 Description Application 8 Description
A! Accounting > 7eneral
A!J#NT Accounting #nterace
B! Basis !omponents
B!J!ST !lient9Server Technology
B!J!8S !ustomizing
B!JN.T Network #nrastructure
B!JABA ABAP <untime .nvironment
B!JS<" Basis Services 9 !ommunication #nteraces
B!J!!& !omputing !enter &anagement System
B!J#NS #nstallation Tools
B!J8P7 8pgrade > 7eneral
B!J!TS !hange V Transport System
B!J'P 'perating System Platorms
B!JDB Database #nteraceA Database Platorms
B!J2.S 2ront>end Services
B!JDWB ABAP Workbench
B!JD'! Documentation and Translation Tools
B!JS.! Security
B!J!# !omponent #ntegration 9 #nstallation Windows !omponents
B!JB&T Business &anagement
B!J&#D &iddleware
B!J!AT !ATT !omputer Aided Test Tool
B!J<<< <eady>to><un <9+
B!JBW SAP Business #normation Warehouse .6tractors
!A !ross>Application !omponents
!AJD&S Document &anagement System
!AJ!4 !lassiication System
!AJ!AD !AD #ntegration
!AJB2A Business 2ramework Architecture
!AJBP SAP Business Partner
!AJ7T2 7eneral Application 2unctions
!AJ.D# #Doc #nteraces or .D#
!AJ!AT !omputer Aided Test Tool Applications
!AJ'#W 'pen #normation Warehouse
!AJTS Time Sheet
!AJA<! Archiving
!AJ!8S 7lobal 'rganization !ustomizing
!' !ontrolling
!'J'& 'verhead !ost !ontrolling
!'JP! Product !ost !ontrolling
!'JPA Proitability Analysis
!S !ustomer Service
!SJBD Basic Data
!SJ#B #nstalled Base &anagement
!SJA7 Service Agreements
!SJ!# !ustomer #nteraction
!SJ!& !all &anagement
!SJS. Service Processing
!SJBS Billing and Settlement
!SJ#S #normation System
.! .nterprise !ontrolling
.!JP!A Proit !enter Accounting
.!JBP Business Planning
.!J!S !onsolidation
.!J.#S .6ecutive #normation System
.,S .nvironment &anagement
.,SJSA2 Product Saety
.,SJD7P Dangerous 7oods &anagement
.,SJ,.A 'ccupational ,ealth
2# 2inancial Accounting
2#J74 7eneral 4edger Accounting
2#J4! !onsolidation
2#JAP Accounts Payable
2#JA< Accounts <eceivable
2#JB4 Bank Accounting
2#JAA Asset Accounting
2#JS4 Special Purpose 4edger
2#J2& 2unds &anagement
2#JT" Travel &anagement
#& #nvestment &anagement
#&J2A !apital #nvestments
#SJ&P
E&PSF
&ill products
#SJ&PJUU &ill Products
4. 4ogistics .6ecution
4.J#DW Decentralized W&S integration
4.JW& Warehouse &anagement
4.JS,P Shipping
4.JT<A Transportation
4' 4ogistics > 7eneral
4'J&D 4ogistics Basic Data
4'JPD& Product Data &anagement
4'JB& Batches
4'JP< 2orecast
4'J"! "ariant !oniguration
4'J.!, .ngineering !hange &anagement
4'J4#S 4ogistics #normation System E4#SF
4'J&DS &erchandise Distribution
4'JS!# Supply !hain Planning #nteraces ES!P#F
4'JS<S #ntegration SAP <etail Store
4'JAD& Additional &anagement
4'J<#S <etail #normation System E<#SF
4'J&AP &erchandise and Assortment Planning
4'JT#& Scheduling
4'JAB Agency Business E7lobal TradeF
&& &aterials &anagement
&&J!BP !onsumption>Based Planning
&&JP8< Purchasing
&&JS<" .6ternal Services &anagement
&&J#& #nventory &anagement
&&J#" #nvoice "eriication
&&J#S #normation System
&&J.D# .lectronic Data #nterchange
PA Personnel &anagement
PAJ<! <ecruitment
PAJPA Personnel Administration
PAJBN Beneits
PAJP2 Pension Schemes
PAJ#S ,< #normation Systems
PAJPD Personnel Development
PAJ'S 'rganizational Structure
PAJ!& !ompensation &anagement
PAJP& ,uman <esource 2unds and Position &anagement
PAJ.S .mployee Sel>Service
PAJ&A ,< &anagerRs Desktop
PAJT" Travel &anagement Esee 2inancial Acctg >L Travel &anagementF
P. Training and .vent &anagement
P.J#N #ntegration
P.JP< Training and .vent Preparation
P.J'2 Business .vent !atalog
P.JDA Day>to>Day Activities
P.J<A <ecurring Activities
P.J<. #normation &enu
P.J<P4 <oom <eservation &anagement
P& Plant &aintenance
P&J.:& Technical 'b%ects
P&JP<& Preventive &aintenance
P&JW'! &aintenance 'rder &anagement
P&JP<' &aintenance Pro%ects
P&J#S #normation System
PP Production Planning and !ontrol
PPJBD Basic Data
PPJS'P Sales and 'perations Planning
PPJ&P &aster Planning
PPJ!<P !apacity <e=uirements Planning
PPJ&<P &aterial <e=uirements Planning
PPJS2! Production 'rders
PPJOAB OANBAN
PPJ<.& <epetitive &anuacturing
PPJAT' Assembly Processing
PPJP# Production Planning or Process #ndustries
PPJPD! Plant Data !ollection
PPJ24W 2low &anuacturing
PPJ#S #normation System
PS Pro%ect System
PSJST Structures
PSJD'! Document
PSJ!'S !osts
PSJ<." <evenues and .arnings
PSJ!A2 Payments
PSJDAT Dates
PSJ!<P <esources
PSJ&AT &aterial
PSJ!'N !onirmation
PSJS#& Simulation
PSJ".< "ersions
PSJP<7 Progress
PSJW24 SAP Business Worklow !onnection
PSJ#S #normation System
PT Personnel Time &anagement
PTJWS Work Schedule
PTJSP Shit Planning
PTJ." Time .valuation
PTJ#N #ntegration with 'ther Applications
PTJ#S #normation System
PTJT4 Tools
:& :uality &anagement
:&JPT :uality Planning
:&J#& :uality #nspection
:&J:! :uality !ontrol
:&J!A :uality !ertiicates
:&J:N :uality Notiications
:&J#T Test .=uipment &anagement
SD Sales and Distribution
SDJ&D &aster Data
SDJB2 Basic 2unctions
SDJS4S Sales
SDJ2T 2oreign Trade
SDJB#4 Billing
SDJ!AS Sales Support
SDJ#S #normation System
SDJ.D# .lectronic Data #nterchange
SDJP'S P'S #nterace
S" Service
S"JASA Accelerated SAP
T< Treasury
T<J!& !ash &anagement
T<J!B !ash Budget &anagement
T<JT& Treasury &anagement
T<J4' 4oans
T<J&<& <isk &anagement
DD 78TPA !ustom Application
DDJUUU Description o custom application

ABAP Naming Standards

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ABAP Naming Standards

Încărcat de

Drepturi de autor:

Formate disponibile

ABAP/4 Naming Standards CVS IT

S-ar putea să vă placă și