ABAP Naming Conventions

Hi All,
I'm looking for a document describing ALL basic ABAP Naming Conventions. For example, how to name data types such as tables, structures, predefined ABAP types, and so on. Furthermore, it would be desirable to know how the declaration changes in different contexts - report, form, function module, class, and so on.
Thank you.

Hi,
as I am working as a consultant for lots of companies in last 10 years, I know that there is no such document. Each company has it's own naming conventions and programming guides. The only thing that is common for all companies is: All customer defined stuff starts with a Z or a Y and in case the company registered it's own name space it starts with /<name space/. May be, somebody can send you these guides coming from whatever company.
regards
Siggi

Similar Messages

Webdynpro ABAP Naming Conventions

Hi All
Can any body help me with writing Naming Conventions for development in Webdynpro ABAP. Is there any documentation regarding this........any help will be highly appreciated.
cheers
AJ

I use these that were suggested in the Web Dypro for ABAP book.
View Element     ID Prefix     Example
Business Graphics     BGR_*     BGR_SALES
Button                     BTN_*     BTN_SAVE
ButtonRow                     BTR_*     BTR_DETAILS
Caption                     CPT_*     CPT_COLUMN
DropDownByIndex     DDI_*     DDI_COUNTRY
DropDownByKey     DDK_*     DDK_REGION
FileUpload      FUD_*     FUD_CONTRACT
Group                     GRP_*     GRP_FORM
HorizontalGutter     HOG_*     HOG_ROADMAP
InputField                     INP_*     INP_NAME
InteractiveForm     IFO_*     IFO_CUSTOMS
Label                     LBL_*     LBL_INPUT
LinkToAction     LTA_*     LTA_SEARCH
LinkToURL                     LTU_*     LTU_VENDOR
RadioButton     RBT_*     RBT_MALE
RadioButtonGroupByIndex     RBI_*     RBI_GENDER
RadioButtonGroupByKey     RBK_*     RBK_TYP
RoadMap                     RMP_*     RMP_DIMENSIONS
RoadMapStep     STP_*     STP_DIMENSION
Table                     TBL_*     TBL_ADDRESS
TextEdit                     TXE_*     TXE_INFO
TextView                     TXV_*     TXV_INTRO
TimedTrigger     TTR_*     TTR_NOTIFY
TransparentContainer     TCO_*     TCO_TABLE
Tray                     TRY_*     TRY_FORM
Tree                     TRE_*     TRE_SIMPLE
TeeeNodeType     TNT_*     TNT_FOLDER
TreeItemType     TIT_*     TIT_FILE
ViewContainerUIElement     VCU_*     VCU_ROADMAP
Window                     W_*     W_DEFAULT
View                     V_*     V_DEFAULT
Inbound Plug     IP_*     IP_START
Outbound Plug     OP_*     OP_EXIT
Apologies for the formatting but the table won't paste properly in plain text - only on IE6 here.
Edited by: Ian Stubbings on Jul 3, 2008 12:02 PM

SAP naming conventions: customer DDIC objects, ABAP programming

SAP Note 16466 Customer name range for SAP objects contains the SAP naming conventions for customer DDIC objects. Rule of thumb is that the names reserved for customer objects start with 'Y' or 'Z'. However, this note contains the naming convention for DDIC objects only.
ABAP Code Inspector (transaction SCI) contains the following naming convention for ABAP programming:
- Global types: T_
- Global constants: C_
- Global data: gv_
- Global field-symbols: FS_
- Global parameters: P_
- Global select-options: S_
- Global field-groups: FS_
- Local types: LT_
- Local constants: LC_
- Local data: v_
- Local field-symbols: LFS_
This is the only place I know for ABAP programming naming convention. Does SAP has somewhere else any additional naming convention guidelines for ABAP programming?
Thanks in advance for your help.
Regards,
Jarmo Tuominen

Naming convention guidelines for ABAP programming is available in here: [Manage Successful Customer Development|https://websmp206.sap-ag.de/~sapidb/011000358700004444532001E].
Naming Data Types and Objects
The names of data types and objects have the form: <Classifier>_<Data type>_<Descriptor>.
The names of data types and objects have up to 30 characters.
Exceptions: names of input parameters and select options have up to 8 characters, and <Data type> and _ are omitted.
First component: Classifier
T Data type
C Constant
G Global data object
L Local data object
FS Field symbol
P Input parameter
S Select option
P Formal parameter in form
FM Formal parameter in function
Second component: Data Type
<t> Elementary data type, optionally followed by length
C<n> Type C of length <n>
N<l> Type N of length <n>
X<l> Type X of length <n>
D Type D
T Type T
I Type I
P<d> Type P with <d> decimals
F Type F
WA Work area
IT Internal table
Third component: Descriptor
Use meaningful English names. Later, your code may be maintained or analyzed by a programmer or support consultant who is not familiar with another language.
Use only alphanumeric characters (A-Z and 0-9) and separate words with underscores (_). Hyphens are reserved for separating components in structured data types.
Examples:
G_I_COUNTER (global counter)
T_IT_BOOKING_LIST (type for list of bookings)
G_IT_BOOKINGS (global internal table of bookings)
PSMOKER (input parameter for smoker flag: note omission of data type and _ for brevity)
Edited by: Jarmo Tuominen on Feb 21, 2011 2:13 PM

Storage Location Naming Convention without WM!

Dear all
We are facing serious problem in our Storage Location for Raw Material.
We have 4 types of Raw Material Seating (S), Panel (P), Metal (M), Wood (W). And they are all stored under Storage Location: RWSL.
Requirement:
Although we have visual guideline as to which industrial rack will store the type of Material, it is insufficient. We need a more refined storage location down to which BIN of the rack we will put the Raw Material.
Due to limited time and resource, we cannot have WM implemented right now. Thus, we have come out with 2 alternative to overcome this problem:
Alternative 01:
We will use the Fixed Bin field in Storage Data 02 by putting the Bin number assigned to each Rack.
E.g. For Seating material code:SEAT01, we will maintain the Fixed Bin as R12A01/A02, it means this Seating material SEAT01 will be stored at Rack 12, fixed bin A01 or A02.
Question to Alternative 01: Will it cause problem in GR, GR, Transfer Posting and Stock Count?
Alternative 02:
Instead of going into details to put Fixed Bin field in Storage Data 2, we will abandan the existing Storage Location RMSL by introducing new format for Storage Location
Here is the example of Alternative 02:
For raw materials, we will use 4 digits location numbers, consistent with other Storage locations, the 4 digits storage location will start with u201CR _ _ _u201D to represent each location
And,
R _ _ _ is:
R = Raw materials
2nd digit = Division (S= Seating, P =Panel, W=Wood, M=Metal and W=Wood)
3rd digit = Rack Number (A, B, C, Du2026 and etc.)
4th digit = Rack Zone - each rack will broken down into zone, each rack can possibility have 2 to 3 zone. 1 Zone can be 1 colume of the Rack
An example of a possible location and its meaning will be
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1
RPB3 = Raw materials warehouse, Panel Division, Rack B, Zone 3
The challenge of this is that instead of having 1 Raw Material Storage Location like RMSL, we will have a lot more storage locations each for division of Raw material due to the Rack Number we have as well as the Rack Zone.
Question to Alternative 02:
If we use this alternative, will it impact our future implementation of WM? From design wise, is it feasible?
Please advise what is the best approach and the feasible design on it.
Many thanks in advance.
Edited by: Daimos on May 13, 2009 10:15 AM

Hi, here is the Pro and Co of both approaches:
Method 01: Use existing SLOC and add the Storage Bin info
e.g. SLOC: STM1
         Storage Bin: RSC3, where RS = Rack Seating, C3 = column 3
Pro 01:
It will cause less effort as we only need to use LSMW for material master to add in the Storage Bin data for all material of SCM.
Pro 02:
I have tested out that in TCode MIGO, apart from SLOC, the pertaining Storage Bin data also appear. Based on my discuss with Xian Chen, sometimes they use MB1C(GR), MB1A(GI) rather than MIGO due to speed issue, I will need to check the field status if can have Storage Bin field APPEAR, if can, it will solve the problem
Con 01:
The Storage Bin information will only appear in MMBE (Stock Overview) but will not appear in the standard SAP Inventory Report (e.g. MB52 Warehouse Stock). To view it from SAP Inventory Report, we may need to customize the standard report to show the new field Storage Bin. It needs Abap effort.
Con 02:
We must have a very good naming convention for Storage Bin. And again, in the above example, if a material is put in SLOC STM1 at Storage Bin RA A1 or C4, it will set a very rigid rule in the future if we need to change it, as I fear that one the Storage Bin has been used up. It will not allow us to change (need to do testing to find out)
Con 03:
Do we have the time to define all the Storage Bin for each SLOC? Operation wise, the store personnel needs to design it
Method 02: Use the new SLOC
Pro 01:
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1. More organized. Easy to tell the material is at which Rack and which Zone of the Rack.
Assumption:
01. we must not have too many rack for one Seating division and also not too many Zone for each
      Division, else it will cause confusion
02. 1 material should stick to 1 Rack 1 zone as much as possible, else later the PP consultant will
     have hard to to perform GI due to too many SLOC assigned to a material.
Pro 02:
In report wise, we are able to show the SLOC in inventory report. No need to enhance the existing inventory report as we do not use Storage Bin.
Con 01:
If there are too many SLOC creation due to it. It may cause problem for PP perform GI as too many selection available for a material. This can be avoided if stick to the General Rule that one material is tied with one SLOC.
Edited by: Daimos on May 16, 2009 5:07 AM

Variable naming conventions

Hi all,
I come from a mostly JAVA background. Big emphasis in that arena on encapsulation and modularization of code to help facilitate ease of maintenance and reuse...in theory I sometimes struggle with variable naming conventions within my ABAP code because I'm not all together certain there are any. In C or C++ I might use a derivation of Hungarian notation to name varaibles...and in JAVA I might observe certain object oriented rules regarding varaible naming...I find myself using a combination of those two protocols in my ABAP code. Does anyone have any suggestions for how I might name global and lcoal variables within my code?
regards,
Mat

Hi,
Please check this links perhaps they may help.
http://help.sap.com/saphelp_nw04/helpdata/en/92/c2b084bc1d11d2958700a0c94260a5/content.htm
https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0b1f547a11d189600000e829fbbd/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73
http://web.mit.edu/sapr3/dev/newdevstand.html
Regards,
Ferry Lianto

Checking naming convention of internal tables in code inspector

Can anyone please explain how in the code inspector can I check names of internal tables (like it_) that I use in a report program ? I know that I can specify it_ in Programming Convention -> Naming Convention->Program Global -> Data but this entry is not specific to internal tables as it also applies to variables and work areas. Apart from this is there any entry I can maintain in the Extended Naming Conventions for Programs(introduced in ECC 6.0)? Kindly reply at the earliest.

Hi,
Check these links for implementing the custom conventions in the code inspector
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/nw/how%20to%20build%20a%20new%20check%20for%20the%20code%20inspector
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/evaluating%20the%20quality%20of%20your%20abap%20programs%20and%20other%20repository%20objects%20with%20the%20code%20inspector
hope it helps you.
Thanks!

Best practices in Internal table naming convention GT , GS , LT , LS ??

Hi Gurus,
 Are GT_ , GS_ , LT_ , LS_ --- the Best practices in Internal table naming convention ????
 I have seen this naming convetions adhered in standard programs .
 What each one of the below signify
 GT_ , GS_ , LT_ , LS_ ???????
Regards
Jaman
Message was edited by:
 ABAP Techie

Hello
I use the following naming conventions:
- G = global variable
- L = local variable
- T = internal table
- S = structure
- D = field
That's how the combinations look like:
- GT_ITAB = global itab
- GS_STRUC = global structure
- GD_FIELD = global field
- LT_ITAB = local itab
- LS_STRUC = local structure
- LD_FIELD = local field
Function module parameters have to stick to the following rules:
- I = importing
- E = exporting
- [C = changing -> never used]
- IT_ITAB = imported table type (itab)
- IS_STRUC = imported structure
- ID_FIELD = imported field
- ET_ITAB = exported table type (itab)
- ES_STRUC = exported structure
- ED_FIELD = exported field
Depending on their semantics TABLES parameters look like:
- IT_ITAB = imported data
- ET_ITAB = exported data
- XT_ITAB = changing data (import & export)
Here are the conventions for FORM routine parameters:
- UT_ITAB = using itab (data are usually treated like constants; no changes will be transfer - although possible - to the calling program)
- CT_ITAB = changing itab (if it is semantically an exporting itab then one of the very
first statements in the routine is: REFRESH ct_itab. )
- US_STRUCT
- UD_FIELD
- CS_STRUCT
- CS_FIELD
Conventions for class/interface parameters:
- IT_ITAB = importing table type
- IS_STRUC = importing structure
- ID_FIELD = importing field
- ET_ITAB = exporting table type
- ES_STRUC = exporting structure
- ED_FIELD = exporting field
- RT_ITAB = returning table type
- RS_STRUC = returning structure
- RD_FIELD = returning field
Conventions for class/interface attributes:
- MT_ITAB = table type
- MS_STRUC = structure
- MD_FIELD = field
- MC_CONST = constant
Question: Are there any advantages of such elaborated naming conventions?
My answer to this question is: Yes, definitively.
I believe that the advantage of semantically differentiating TABLES parameters of function modules is quite obvious:
CALL FUNCTION 'Z_BAD_NAMING'
 TABLES
 itab1 = ...
 itab2 = ...
 itab3 = ... .
CALL FUNCTION 'Z_GOOD_NAMING'
 TABLES
 it_itab1 = ...
 et_itab2 = ...
 xt_itab3 = ... .
I also believe that my naming conventions clearly enhance readability and maintainability of my programs.
Regards
Uwe

How to create new check for SELECT* , Naming conventions etc..

Hi all,
   I would like have a solution for the below checks are possible or not in ABAP - CODE INSPECTOR. If possible can you please give me the solution..
a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
b). Custom naming conventions.
c). to check if further modularization can be done in the program,
d). also the coding standards.
PLEASE help me , i am struck with it for long time in getting the solution...

> a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
> b). Custom naming conventions.
> c). to check if further modularization can be done in the program,
> d). also the coding standards.
the code inspector allows the creation of new checks, you should consult the documentation how to do it.
The main problem of the code inspector are hits, which are actually no problem. And I think this is a problem with your checks:
+ SELECT* this is no performance problem, only in cases when the table is really wide then a field list makes sense, i.e your check
   will find a lot of false hits
+ LOOP without field strings ... you mean fs =field symbols, same as with SELECT *
+ FOR ALL ENTRIES IN SELECT STATEMENT   ???? FOR ALL ENTRIES is fine
+ Custom naming conventions ... hmmm be more precise, I think it can be hard
+ to check if further modularization can be done in the program,
    before you want to program can you please explain how you check manually .... I would be interested
+ also the coding standards.   .... what is that?

SAP Naming Conventions for DB Data Files

Hi Everyone!
We are about to install a SAP ECC 6.0 SR3 ABAP on Windows Server 2008 (R2) & SQL Server 2008 SP1 and we want to name the DB data files as follows:
<sid>DB_Data_001.MDF/NDF
Do you see any problem with this or think this could lead to a problem in the future?
We were unable to find a SAP note or SAP recommendation about this, we only found SAP Note 27428 but itu2019s for Oracle.
Thanks in advance!
Best Regards,
Nicolas

Hi Nicolas,
I thought about all corners where this could possibly lead to a problem (e.g. monitoring, DB13, ...) but couldn't think of a single report or transaction where this would cause problems.
To the database itself the names of the files do not matter at all and in the SAP transactions the datafiles are only read to display them in monitoring transactions like DB02 or RZ20. These transaction do not expect a certain naming convention so I don't see anything that would count against using different filenames.
Regards,
Beate Grötschnig

Code Inspector - Naming conventions &mExtended Naming conventions for Progs

Hi experts,
I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
importing parameter : I[:type:]_
exporting parameter : E[:type:]_
changing parameter : C[:type:]_
tables parameter : T[:type:]_
but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
importing parameter : P_*
exporting parameter : P_*
changing parameter : P_*
tables parameter : P_*
I felt, while defining the function too, its better to have beginning with I_, E_, C_ or T_ instead of P_
is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
appreciate the opinions from experienced abap developers.
thanks,
Madhu_1980

Frank,
Thanks for your answer.
But what about Entity Objects, View Objects, View Links, and Application Modules.
I would like my developers to have an easy way to name them and also find them via intellisense.
So I was thinking in naming them the following way :
Entity Objects :
EO_Employee
EO_Department
View Objects :
VO_Employees
VO_Departments
View Links :
VL_EmployeesToDepartments
Application Module :
AM_HRService
However the use of "_" is not so "Java naming oriented".
So other alternatives would be:
1. take the "_" :
1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
2. Use the prefix at the end, but this way I loose the intellisense feature I want:
ex: EmployeeEO
Which naming approach are you using for big projects ?
Thanks,
Claudio.

Implementing Transport Naming convention with the help of BAdIs (Urgent)

Hi Gurus,
We need to implement Transport Naming convention in our landscape.
Transport request should follow the following naming conventions and to enable this we have to enable some necessary BAdIs?
Scenario would be like this....!
Customization
LC-<Track>-<Description> (Non Transportable Request)
<Module>-<Track>-<Configuration Type>-<Change No>-<Description of the Customisation.>
ABAP Developments
AB-<Track>-<Configuration Type>-<Development No>-<Description of the Development>
OSS Notes
BC-<Track>-OSS#<OSS Note No>-<Version>-<Patch Number>-<Process Team>-<Note Description>
Authorization
BA-<Track>-<Version>-<Authorisation Description>
Details :
Track : 01 u2013 Hot fixing, 02 u2013 Implementation, 03 u2013 BIW / EP, 04 u2013 Support
Module : SAP Module (FI, CO, MM, SD, PP, etc..)
Configuration Type : I u2013 Initial Configuration, R u2013 Change due to TPR or Additional Functionality
Change No / Development No : Unique no to trance the base documentation
Please suggest .....................!
Which are the necessary BAdIs needs to be enabled and what other configuration needs to be done.
If anybody has any document please provide.
Thanks in advance..............!!!
Regards,
Jai Sach

Hello,
SPRO --> SAP NetWeaver --> Application Server -->
System administration --> Change & Transport domain
--> BADI -->Business Add-In when Editing Requests
IF_EX_CTS_REQUEST_CHECK~CHECK_BEFORE_CREATION
Happy Tony

Web Dynpro for ABAP Naming Convension & Guide line

Hi, everyone.
I have a plan to implement Web Application as WDA(Web Dynpro for ABAP). but I don't know how can I give a name to Windows or Views or Custom controllers.
If you have a naming convension or guid line document,
Could you share the document with me? ^^

As Rich said, there are no official naming conventions. Nonetheless, a few things have become quite popular, such as:
- adding wnd_ in front of window names as they share the same namespace with views
- adding m_ in front of member variables of controllers
- adding s_ in front of supply methods and using the name of the node afterwards
- adding lbl_ in front of labels and using the name of the labelled ui element afterwards like "lbl_customer" and "customer"
Some developers also add certain prefixes to view elements to distinguish between them.
Regarding the names of components, there is one thing that you should not do: Start them with WD_ or WDR_ as both are somehow preserved. The same is true for entities within a component, although there checks in place that prevent you from doing that.
Best regards,
Thomas

What are the naming conventions we should follow while creating an object

hi
what are the naming conventions we should follow while creating an object in ABAP dictionary, i.e while creating zee table.

Hi,
Namespaces and Naming Conventions
SAP has reserved name ranges for customer objects and SAP objects. Use these customer name ranges to make sure that your objects are not overwritten by SAP objects during the import of corrections or an upgrade.
This documentation lists the customer name ranges for the different system objects.
Only use the customer name ranges. If you do not keep to the name ranges for customer objects you may lose your development objects.
SAP delivers a few system objects with names that fall within the customer name range. These objects already existed when the customer name range was extended from YY/ZZ to Y/Z. These objects are listed in table TDKZ.
Regards

Naming Conventions of Web Dynpro Wizard

Hello everyone,
is it possible to change the naming conventions of the coding generated by the web dynpro wizard?
According to our internal naming conventions object references (type ref to) are to be named LR_name, but the wizard is calling them LO_name.
Thanks in advance and best regards,
Alej

The templates/code fragments used by the wizard for generation are in the class CL_WDY_RG_FRAGMENT_TOOL, which in turn navigates down to local classes in the WDY_RG_CODE_TEMPALTES Function Group. For instanace the Context code fragements are in the local class LCL_COMPLEX_FRAGMENTS of this function group.
The fragements aren't in reusabe or customer maintable templates unfortuetely. They are built with CONCATENATE statements in these local classes. Newer developments (like the ABAP Code Completion in 7.02) use the ABAP Template Language (ATL) and have a tool to maintain these templates directly. However for the WD Code Wizard, you would have to use the Enhancement Framework or Modification Assistant to adjust the concatenate statements in the local classes.

Naming Conventions for Workflow

Hello,
does anybody have a document for Naming Conventions for Workflow.
I found nothing the last hour.
Thanks in advance for any help ...
Stefanie

Hi,
I am sending you naming convention which we followed in our project.
Workflow Template & Standard Task:
SAP/R3 Limitations:
Workflow Template & Standard Task names are limited to 12 bytes.
Standard:
Bytes 1-3 of the Workflow Template & Standard Task (see following table) are intended to give an overview of general information regarding the Workflow Template & Standard Task.
Characters 4-12 of the name should be chosen to impart some idea of the Workflow Template & Standard Tasku2019s use and/or contents. (The portion of the Workflow Template & Standard Task name that forms the unique identifier may, or may not, contain underscores characters to enhance Workflow Template & Standard Task name readability.)
Position Description Sample Values Sample Meanings
1 Table system life Z/Y Permanent/Temporary
2 Application Type * See Application Designators (Appendix B)
3 OPCO/Region * See OpCo Initial Chart (Appendix A)
4-12 Unique identifier text Unique identifier; may include underscores
Example: ZS7_IDEL9 (I:-Inbound, DEL: - OILDEL 9:- Original)
Business Object:
SAP/R3 Limitations:
Business Object names are limited to 10 bytes.
Standard:
Bytes 1-3 of the Business Object (see following table) are intended to give an overview of general information regarding the Business Object.
Characters 4-12 of the name should be chosen to impart some idea of the Business Objectu2019s use and/or contents. (The portion of the Business Object name that forms the unique identifier may, or may not, contain underscores characters to enhance Business Object name readability.)
Position Description Sample Values Sample Meanings
1 Table system life Z
Y Permanent
Temporary
2 Application Type * See Application Designators (Appendix B)
3 OPCO/Region * See OpCo Initial Chart (Appendix A)
4-12 Unique identifier text Unique identifier; may include underscores
Example: ZS7_OILDEL (Business Object for OILDEL Message Type)
Methods
Method names should begin with a verb:
Examples: GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
For Parameters:
IMPORTING parameters IM_<parameter name>
EXPORTING parameters EX_<parameter name>
CHANGING parameters CH_<parameter name>
RESULT RE_<result>
Events
Event names should have the form
<noun>_<participle>:
Examples: BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
Note: There is no specific naming convention for Container Variables in workflow & for Key Fields & Attributes in Business Object. These variables name should be chosen to impart some idea of the variablesu2019 use and/or contents.
Appendix A
ABAP Programming Standards: OpCo/Region Initial Chart
Old # Company Name Proposed # Accounting Location
98 Common A San Ramon
95 FSC B San Ramon
80 Chevron Chemical Company C San Ramon
89 Chevron USA-Downstream & General D Walnut Creek
75 Chevron Real Estate Management E San Francisco
76 Chevron Information Technology Company F San Ramon
77 Gulf Oil Great Britain G London
85 Corporation (Acct. by Corp.) H San Francisco
83 Chevron International Oil company J San Ramon
87 Chevron U. K. Limited K England
86 Corporation (Acct. - Local Office) L Various
96 P&M Coal & Mining Company M Denver
94 Corporation (New York) N New York
90 Chevron Pipeline Company P San Ramon
79 Chevron Canada Resources, Ltd. R Calgary
92 Chevron Shipping Company S San Francisco
81 Chevron Petroleum & Tech Co. T Houston
91 Chevron USA Upstream U Concord
78 Chevron Canada, Ltd. V Vancouver
93 CUSA Warren Petroleum W Tulsa
84 Chevron Overseas Petroleum, Inc. X San Ramon
88 Chevron Research & Tech. Company Y Richmond
- Corp. GLX Common validations Z San Ramon
- PCA 3 San Ramon
- Tax 4 San Ramon
- Audit 5 San Ramon
- Asia-Pacific 6 Global
- Africa 7 Global
- Latin America 8 Global
Appendix B
ABAP Programming Standards: Application Designators
A Assets Accounting
C PPC
D DASS (control station)
E RIVA/IS-Oil
F Financial Accounting (incl. Joint Venture)
G General Ledger
H Human Resources Planning
I Plant Maintenance
J Publishing
K Cost Accounting
L Inventory Management
M Materials Management
N Hospital
O unassigned
P Human Resources
Q QSS (Quality assurance)
R PRA (Prod & Revenue Acctg)
S Basis
T Projects
U Enterprise Data Model
V Sales
W MMS (Merchandise mgt. System)
X unassigned
Y Customer head office
Z Customer branch
<inappropriate content removed by moderator>
Thanks
Yogesh Sharma
Edited by: Mike Pokraka on Jul 2, 2008 10:34 AM

ABAP Naming Conventions

Similar Messages

Maybe you are looking for