ABAP Programming Standards & Naming

Convention

www.atos.net

Issued by:

Atos

ABAP Programming Standards & Naming

Representative

Integrated
Date/ SignatureProject Automation
6th August, 2012 Acceptance:
Date/ Signature:
Version 1.1 / English / 06 Aug 2012

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC

ABAP Programming Standards & Naming Conventions | ntegrated Project

History of Changes

Versio Date of A/M Name Description Reviewed Approved

n No. Change /D* of Changes by by
06/08/20
1.0 A First Draft <Name> <Name>
12

Added Code
20/02/20
2.0 M for CRM and <Name> <Name>
13
SRM

*A = Added, M = Modified, D = Deleted

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 2

. 2
ABAP Programming Standards & Naming Conventions | ntegrated Project

CONTENTS

1 NAMING CONVENTIONS............................................................4
1.1 NAMING CONVENTIONS FOR ABAP DEVELOPMENT
4
1.2 SAP SCRIPTS
8
1.3 SMARTFORMS
9
1.4 PROJECT NAMES FOR ENHANCEMENTS
9
1.5 AUTHORIZATION RULES & PROCEDURES
9
2 NAMING CONVENTIONS............................................................11
2.1 NAMING CONVENTIONS FOR DATA DICTIONARY OBJECTS
11
2.2 MESSAGE ID AND NUMBER
13
2.3 BATCH JOB SCHEDULING
14
2.4 WORKFLOW OBJECTS
15
2.5 TRANSPORT REQUESTS
16
2.6 Country codes
24

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 3

. 3
 ABAP Programming Standards & Naming Conventions | ntegrated Project

Naming Conventions

1.1 Naming Conventions for ABAP Development

Position number 1 2 3 4 5 6-----

Program Object “_” Free meaningful
Description Z Application
type Number text
Example Z V R 001 ‘_’ CREATE_ORDER

 Position 1 is a Z.
 Position 2 represents the SAP module, following SAP standards:

Code Application SAP Description

A AM Asset Management
F FI Finance
G GL General Ledger
H HR-P Human Resources Planning
I PM Plant Maintenace
J PS Project Systems
K CO Cost Accounting
L WM Warehouse Management
M MM Materials Management
P HR-M Human Resourses
Management
Q QM Quality Management
R PP Production Planning
S BC System
V SD Sales and Distribution
C APO Advance Planing &
Optimisation
X Vistex Vistex
T CRM Customer Relationship
Management
D SRM Supplier Relationship
Management

 Position 3 is the ABAP Type:

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 4

. 4
 ABAP Programming Standards & Naming Conventions | ntegrated Project

R Report
I Interface
C Conversion
M Module pool
N Include (used in another program)
K Class
F Forms
W Workflows
Y Webdynpro for ABAP development
E Enhancement
A Authorization Object

 Position 4 is the unique 3 digit object number assigned to the development.

 Position 5 “_”
 Positions 6 onwards are free for the user to assign.
Note 1: when copy of standard programs, same rules up to char 5 but
concatenate the original program name from position 6 onwards
Note 2: For FICO development specify AP and AR at place 6 and 7 where
applicable

1.1.1 Transaction Names

Position number 1 2 3 6-----

Object
Description Z Application Freely Definable
Number
Example Z V 001 CREATE_ORDER

Position 1: ‘Z’
Position 2: Functional field as described in Section 1.1
Position 3: Object Number
Position 4 onwards: Freely definable

Note: Only 4 characters should be used as far as possible.5th character is

optional and should be used only if required.

1.1.2 Dynpros

Custom screen painter dynpro must always be numbered greater than 1000.
XXXXXXXX 9 NNN M
where:XXXXXXXX Module Pool Screen Belongs To
9 Index number to indicate customer-specific Number
NN Free form numeric number
The recommended ranges are:
· 9000 - 9499 for changes to SAP programs

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 5

. 5
 ABAP Programming Standards & Naming Conventions | ntegrated Project

· 9500 - 9999 for custom developments

When creating custom selection screens for database access program dynpros, use
the range 050 - 900. Dynpros for alternative selection screens can be identified by a
number, less than 1000. The initial screen for a table access program is 1000.

1.1.3 ABAP/4 Module Pool

Module pools, which are used when developing custom transactions, are also ABAP
programs. They are identified by the format:

Module pools commonly use INCLUDE routines for shared structures: for example:
Name of the pool program: ZVM001_XXXXX

Include of the pool program for the « PAI »: ZVM001_XXI01, ZVM001_XXI02…

Include of the pool program for the « PBO »: ZVM001_XXO01, ZVM001_XXO02…

Include of the pool program for the « FORM »: ZVM001_XXF01, ZVM001_XXF02…

Include of the pool program for the « TOP »: ZVM001_XXTOP

1.1.4 Function Modules / Group

Function modules are groups of common routines used in an ABAP/4 program(s).
The naming conven tion is as follows:
Position number 1 2 3 4 5 6-----
Program Object “_” Free meaningful
Description Z Application
type Number text
Example Z V F/G 001 CREATE_ORDER

Position 1: ‘Z’
Position 2: Functional field as described in Section 2.1
Position 3: ‘F’ for Function Module and ‘G’ for Function Group
Position 4: Object Number
Position 5: ‘_’
Position 6 onwards: Freely definable and descriptive text

1.1.5 Authorization Groups

Certain development classes will be reserved for global development done in the
regions. The intent is to facilitate easier handling of objects when
transporting/maintaining systems.
Development classes are formed via the template ZAXX where 'a' is the application,
'XX' is freeform. For global development use XX=00. The Basis groups should always
create development Classes. Module Experts and SAP consultants should never
create a development class. This way we ensure uniqueness.

1.1.6 Report Writer Module Names

The Report Writer is designed to provide summary information from multiple
application components. The Report Writer selects the data you request and then
presents it in the format you require. Using combinations of functions such as sets,

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 6

. 6
 ABAP Programming Standards & Naming Conventions | ntegrated Project

variables, formulas, cells, and key figures, you can create reports to meet your
specific needs.

1.1.7 Reports

Position number 1 2 3 4 5 6-----

Program Object “_” Free meaningful
Description Z Application
type Number text
Example Z V R 001 CREATE_ORDER

Position 1: ‘Z’
Position 2: Functional field as described in Section 2.1
Position 3: ‘R’
Position 4: Object Number
Position 5: ‘_’
Position 6 onwards: Freely definable and descriptive text

1.1.7.1 For copying the Standard SAP Program

Position 1: ‘Z’
Position 2: Functional field (Section 2.1)
Position 3: Program type (Section 2.3)
Position 4: Object Number
Position 5: ‘_’
Position 6 to n: Name of the SAP standard program.
Example: ZVM001_SAPMV60A

1.2 SAP Scripts

 Must be 17 characters long as a maximum.

 Position 1 is Z.
 Position 2 refers to the SAP Module.
 Position 3 refers development type which is “F”
 Positions 4-6 is Development ID:
 Position 7 is “_”
 Positions 8 to 17 are free for the user to assign.
Preferably Transaction codes e.g. F150 for dunning & language code is form is
only in one language
Example:
Position number 1 2 3 4 5 6-----
Developm Object “_” Free meaningful
Description Z Application
ent type Number text
Example Z V F 001 CREATE_ORDER
ZVF001_XXXXX

Standard texts (transaction SO10) codification

Z_<Form name>_<Description>_<Counter>
Where:

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 7

. 7
 ABAP Programming Standards & Naming Conventions | ntegrated Project

<Form name> is the Standard Form name

<Description> semantics
Counter (incremented number for the form)
Note: when copy of standard FORMS, just append Z and Development ID
before the original name.
Example: Standard Form: XXXX then Z001XXXX.
When calling a subroutine in an include program the name of the
INCLUDE program should having the sapscript form name .refer
section 1.1, the “free text” position 6 onwards should have form
name.

1.3 SmartForms

 Must be 30 characters long as a maximum.

 Position 1 is Z.
 Position 2 refers to the SAP Module.
 Position 3 refers development type which is “F”
 Positions 4-6 is Development ID:
 Position 7 is “_”
 Positions 8 to 30 are free for the user to assign.
Preferably Transaction codes e.g. F150 for dunning & language code is form is
only in one language
Example:
Position number 1 2 3 4 5 6-----
Developm Object “_” Free meaningful
Description Z Application
ent type Number text
Example Z V F 001 CREATE_ORDER
ZVF001_XXXXX

Smartform: Z<application>F<Development ID>_ Description>

Smart Styles: Z<application>F<Development ID>_ Description>

1.4 Enhancements

1.4.1 Enhancements using SMOD/CMOD

Project Name: Z<application>E<Development ID>_ Description>

1.4.2 Enhancements using User Exits

Use implicit enhancement available under each routine.
Enhancement Name: Z<application>E<Development ID>_ Description>

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 8

. 8
 ABAP Programming Standards & Naming Conventions | ntegrated Project

Include all the coding inside a separate INCLUDE.

Example:
>>>>INSIDE THE EHNACEMENT<<<<<
INCLUDE Z<application>E<Development ID>_ Description>
>>>>END OF ENHANCEMENT<<<<<<<

1.4.3 Enhancements using BADI (New/Old)

BADI Name: Z<application>E<Development ID>_ Description>

1.5 ABAP Webdynpro Application

Webdynpro Component Name: Z<application>Y<Development ID>_ Description>

1.6 Workflows

 Workflow template name would come from the number range.

 Bespoke Business Object Name: Z<application><Development ID>_ Description>
o When copying the Standard, remove the prefix “BUS” and suffix the copied
one with the last four digits.
o Example: For standard BUS2015, naming would ZM001_2015.

1.7 Authorization Rules & Procedures

This section specifies the standards for ABAP/4 and Table authorizations.

Authority Checks for ABAP/4 Programs

Why we need to assign an Authorization Group to an ABAP/4 program?

An Authorization Group assigned to an ABAP/4 program, controls who is authorized to

change or execute it.

How do I assign an Authorization Group to an ABAP/4 program?

You can assign an Authorization Group to an ABAP/4 program in the attributes screen.

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 9

. 9
ABAP Programming Standards & Naming Conventions | ntegrated Project

Why do we need Authority Check's in ABAP/4 programs?

Authority Check statements are useful for further restriction on the execution of the
program. E.g. the execution of a report can be limited to a specific company code,
depending on the profile that was assigned to the user.

How do I include Authority Checks into Programs?

An ABAP/4 program makes authority checks using the AUTHORITY-CHECK statement:

AUTHORITY-CHECK OBJECT <authorization object>

ID <authority-field 1> FIELD <field-value 1>
ID <authority-field 2 > FIELD <field-value 2>
...
ID <authority-field n> FIELD <field-value n>

The OBJECT parameter specifies the authorization object.

The ID parameter specifies an authorization field (in the authorization object).
The FIELD parameter specifies a value for the authorization field.

The AUTHORITY-CHECK statement searches the user's master record for authorizations
corresponding to the authorization object specified in the statement. This means
searching through all profiles in the master record, since the user could have more than
one authorization for the given authorization object.

To pass the authority check, the user must have at least one authorization specifying all
the values given in the AUTHORITY-CHECK statement. If so, the system sets the return
code SY-SUBRC to 0, and your program can allow the user to continue working. In all
other cases, you must prevent the user from proceeding or accessing the data.

Authority Checks for Tables

Why do we need Authority Check's for Tables?

We need this kind of Authority to limit the number of users who can maintain tables.

How do I do that?

The table TDDAT defines the link between a table and an authorization group. Those
authorization groups are defined in table TBRG. The related object is S_TABU_DIS.

Creating bespoke authorization object.

Could be 10 characters long.

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 10

. 10
ABAP Programming Standards & Naming Conventions | ntegrated Project

Authorization Object: Z<application>A<Development ID>_ Description>

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 11

. 11
 ABAP Programming Standards & Naming Conventions | ntegrated Project

2 Naming Conventions

2.1 Naming Conventions For Data Dictionary

Objects
D Development Class
T Table
DE Data Element
DO Domain
HP Search Help
S Structure
TY Table type
V View
Z<Module Name><DDic Type>_XXXXX

2.2 Message Id and Number

Error messages in custom developments should use a message ID that begins with
“Z” followed by the application letter. All messages should be as general as possible
with the detail transferred via “&” symbols in the message.

2.2.1 Message Id

Z<module code>M_XXXX

2.2.2 Message Number

9 NN (3 Characters)

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 12

. 12
 ABAP Programming Standards & Naming Conventions | ntegrated Project

Where: 9 Identifies customer developments

NN Free form numeric number

When including messages for programs that do not require multi-lingual messages,
use the general ID 38 message 001 and the WITH clause to enter the message.

2.3 Batch Job Scheduling

2.3.1 User Id Setup

User Id: M CC PROD_BTCH (12 Chars)

Password: none

2.3.2 Job Standards

There are 6 scenarios, which will be explored, each having a different job name.

2.3.3 Basic Format

M_CC PPPP_TTTT_XX...X (32 Chars)

2.3.4 ABAP - Single Report (Single Step)

M_CC PPPP_AAAAAAAA_ TTTT_XX...X (32 Chars)

2.3.5 ABAP - Single Report with BDC Session Release

M_CC PPPP_ AAAAAAAA_BDC_TTTT_ XX...X (32 Chars)

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 13

. 13
 ABAP Programming Standards & Naming Conventions | ntegrated Project

2.3.6 Queue Names

M_CC PPPP_ QQQQQQ_TTTT_ XX...X (32 Chars)

2.3.7 Interfaces

M_CC PPPP_ INTERFACE_TTTT_ XX...X (32 Chars)

2.3.8 Scheduled Submission of SAP Transactions

M_CC PPPP_ DDDD_TTTT_ XX...X (32 Chars)

Where: M Application Code identifier

CC Country Code
PPPP Plant Code (If relevant)
AAAAAAAA ABAP Name
QQQQQQ Data flow of the queue via CPIC (First 3 characters Indicate
sending system, the last 3 characters indicate the receiving system)
INTERFACE Constant Denoting that this is an Interface
DDDD Transaction
TTTT Scheduled Times
And XX...X Free form up to the max Number of characters

2.4 Workflow Objects

1) Parameters of methods in a Business objects should be declared as per
naming convention of local
variables in abaps (GV_xxxxx/GT_yyyyy_zzz ). Declaration of variables
should be in CAPS. Tasks
will inherit the method parameter names and the Workflow will inherit
from task.

2) WF container elements should be decalred as WF_

3) Each method/attribute code block should have a program block attached.

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 14

. 14
 ABAP Programming Standards & Naming Conventions | ntegrated Project

4) Each method/attribute should have its own change history section.

2.5 Transport Requests

Structure:
F_G_10_01_[Process-ID] [IMG Activity Description]

F_G_10_01_[Change Request Number] [Process-ID] [IMG

Activity Description]

 F is fixed
 G is for Global, as L is for Local Roll Outs
 10 is for roll out , where 10 if for Global, 20 is for Europe, 30 is for
Americas, 40 is for Asia Pacific
 01 indicated applicability – 01 for multiple countries, unique 2
character identifier for single country applicability (eg. UK, FR, US,
PR…) – see defined country list for all countries
 Change Request Number is the internally generated project change
request number (5 characters)
 Process-ID would be (e.g.) PP-01-01 and provides the direct link to the
Functional Specification (FS) (header only, no indication of which
requirement specifically is met by the content)
 Meaningful description

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 15

. 15
ABAP Programming Standards & Naming Conventions | ntegrated Project

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 16

. 16
 ABAP Programming Standards & Naming Conventions | ntegrated Project

2.5.1 Code presentation and comments

The heading of the ABAP code must contain this information:

 The author name and user-id.

 The title of the ABAP.
 The date of cretion.
 A short functional description.
 A log list of changes with:
 The user-id,
 The date of change,
 A short description of the change.

Comments in the body of the code are only required if they help the understanding
of the processing.

Example :

*******************************************************************
**
* PROGRAM ID : Zxxxxxx Copy of:XXXXXXXXX
* TITLE : xx
* FO contact : XXXXXXXFUNCTIONAL CONTACTXXXXXXx
* CREATE DATE : OCT-03-2007
* AUTHOR : Name & T-Number
* Project No. : Tracker Ticket number e.g FI-07-00-TS-001
*------------------------------------------------------------------
-*
* DESCRIPTION :
Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
* xxxxxxxxxxxxxxxxx .
*------------------------------------------------------------------
-*
* CHANGE HISTORY
*------------------------------------------------------------------
-*
* DATE | NAME | DESCRIPTION |
Reference
*------------------------------------------------------------------
-*
* MON.DD.YYYY| Tx99999 | Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
XYZDDMMMYY

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 17

. 17
ABAP Programming Standards & Naming Conventions | ntegrated Project

* | | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |

* | | Tracker Ticket No: XXXXx |

* | | Transport No. |

*-------------------------------------------------------------------*

* MON.DD.YYYY| Tx99999 | Xxxxxxxxxxxxxxxxxxxxxxxxxxxxx |

ABCDDMMMYY
* | | xxxxxxxxxxxxxxxxxxx |
* | | Tracker Ticket No: XXXXx |

* | | Transport No. |

*******************************************************************
**

The above header block must be added to all programs, including INCLUDES.

The reference is used to identify the changed lines into the ABAP code. The format
of this reference is:

XYZDDMMMYY

Where: XYZ 3-Character Short name of Developer

DD 2-Digit date
MMM 3-Character Month Name
YY 2-Digit Year

The reference must be placed in any changed line during the change of an
existing ABAP.

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 18

. 18
 ABAP Programming Standards & Naming Conventions | ntegrated Project

2.5.2 Naming convention for internal data objects

To improve the readability of the ABAP code, it is required to use rules to specify the names of the internal data

objects. Depending on the type of data objects, use the following prefix codes.

Type Prefix Example

Parameters P_ PARAMETERS:
P_BUKRS LIKE T001-BUKRS.
Select-options S_ SELECTION-OPTIONS:
S_BELNR FOR BKPF-BELNR.
Ranges R_ RANGE:
R_WERKS FOR T001W-WERKS.
Types TY_ TYPES : Begin of TY_XXX,
(Define all Types as <Fields>
global in TOP Include) End of TY_XXXX.
Work fields ( Global) GS_ DATA: GS_CNT TYPE TY_XXX.

Work fields (Local ) LS_ DATA: LS_CNT TYPE TY_XXX.

Table Type TT_ TYPES: TT_XXX TYPE STANDARD TABLE OF

TY_YYY.
(Define all table types
as global in TOP
Include)
Field groups FG_ FIELD-GROUPS:
HEADER,
FG_LINE.
Internal table (Global). GT_ DATA: GT_T001 TYPE STANDARD TABLE OF
T001.

Internal table (Local) LT_ DATA: BEGIN OF T_MATNR OCCURS 0,

MATNR(8) TYPE C,
END OF TMATNR.

OR

DATA: BEGIN OF T_MXXXX OCCURS 0.

INCLUDE STRUCTURE T001.
DATA: MATNR(8) TYPE C ,
END OF T_MXXXX.

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 19

. 19
 ABAP Programming Standards & Naming Conventions | ntegrated Project

Constants C_ CONSTANTS: C_NBDAYS TYPE I VALUE 7.

(Define all constants
as global in TOP
Include)
Field Symbols (Global) <LS_> Field-Symbols: <LS_monat>

Field Symbols (Local) <GS_> Field-Symbols: <GS_monat>

Class (local) LCL_ CLASS LCL_XXX DEFINATION.

Class Object (Global) GO_ DATA: GO_XX TYPR REF OF LCL_YYY

Class Object (Local) LO_ DATA: LO_XX TYPR REF OF LCL_YYY

Formal Table PT_ PT_<original name>

parameters within
FORM’s
Function Module xxxxx. : object
Export description (as possible
variable E_xxxxx the standard name)

xxxxx. : object
Import description (as possible
variable I_xxxxx the standard name)

xxxxx. : object
Changing description (as possible
variable C_xxxxx the standard name)

xxxxx. : object
Export ES_xxxx description (as possible
structure x the standard name)

xxxxx. : object
Import IS_xxxx description (as possible
structure x the standard name)

xxxxx. : object
Changing CS_xxxx description (as possible
structure x the standard name)

xxxxx. : object
Export ET_xxxx description (as possible
table x the standard name)

xxxxx : object description

Import IT_xxxx (as possible the standard
table x name)

2.5.3 Coding sequence

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 20
. 20
ABAP Programming Standards & Naming Conventions | ntegrated Project

All the code elements must be coded in the following defined sequence to help find the coding elements in the

ABAP’s. The sequence is:

Use PATTERN ZREPORT_TEMPLATE created in client XXX.

REPORT declaration.

INCLUDES declaration.

TABLES declaration.

TYPE-POOLS

TYPE declarations

CONSTANTS declaration.

DATA Work field’s definition.

DATA Structure definition.

DATA Internal table definition from existing tables with INCLUDE

STRUCTURE statements.

DATA Other internal table definition.

RANGES definition.

FIELD-GROUPS definition.

FIELD-SYMBOLS definition.

PARAMETERS and SELECT-OPTIONS definition (sequence depends on

the screen layout).

INITIALIZATION event.

AT SELECTION-SCREEN ON VALUE-REQUEST FOR <field>

AT SELECTION-SCREEN ON HELP-REQUEST FOR <field>

AT SELECTION SCREEN ON specific field.

AT SELECTION SCREEN ON block.

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 21

. 21
ABAP Programming Standards & Naming Conventions | ntegrated Project

AT SELECTION-SCREEN OUTPUT.

AT SELECTION-SCREEN.

START-OF-SELECTION.

GET segment (sequence depend on the logical database structure. GET

segment LATE comes after).

END-OF-SELECTION.

TOP-OF-PAGE.

END-OF-PAGE.

AT LINE-SELECTION.

AT USER-COMMAND .

AT PFnn.

MODULE coding.

FORM coding (in sequence of call in the events or other forms).

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 22

. 22
 ABAP Programming Standards & Naming Conventions | ntegrated Project

2.6 Country codes

ISO Country ISO Country ISO Country

Code Code Code
AL Albania CO Columbia GE Georgia
AM Armenia CR Costa Rica GF French Guinea
AN Dutch Antilles CU Cuba GH Ghana
AO Angola CV Cape Verde Is. GI Gibraltar
AQ Antarctica CX Christmas Island GL Greenland
AR Argentina CY Cyprus GM Gambia
AS Samoa, American CZ Tschechien GN Guinea
AT Austria DE Germany GP Guadeloupe
AU Australia DJ Djibouti GQ Equatorial Gui.
AW Aruba DK Denmark EL Greece
AZ Aserbaidjan DM Dominica GT Guatemala
BA Bosnia-Herz. DO Dominican Rep. GU Guam
BB Barbados DZ Algeria GW Guinea-Bissau
BD Bangladesh EC Ecuador GY Guyana
BE Belgium EE Ecuador HK Hong Kong
BF Burkina-Faso EG Egypt HN Honduras
BG Bulgaria ES Spain HR Croatia
BH Bahrain ET Ethiopia HT Haiti
BI Burundi FI Finland HU Hungary
BJ Benin FJ Fiji ID Indonesia
BM Bermuda FK Falkland Islands IE Ireland
BN Brunei Dar-es-S FM Micronesia IL Israel
BO Bolivia FO Faroe Islands IN India
BR Brazil FR France IQ Iraq
BS Bahamas GA Gabon IR Iran
BT Bhutan GB Great Britain IS Iceland
BV Bhutan GD Grenada IT Italy
BW Botswana GE Georgia JM Jamaica
BY White Russia GF French Guinea JO Jordan
BZ Belize GH Ghana JP Japan
CC Coconut Islands GI Gibraltar KE Kenya
CF Central Afr. Rep GL Greenland KG Kirghizstan
CG Congo GM Gambia KH Cambodia

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 23

. 23
 ABAP Programming Standards & Naming Conventions | ntegrated Project

ISO Country ISO Country ISO Country

Code Code Code
CH Switzerland GN Guinea KI Kiribati
CI Ivory Coast FO Faroe Islands KM Comoro Is.
CK Cook Islands FR France KN St.Chr., Nevis
CL Chile GA Gabon KP North Korea
CM Cameroon GB Great Britain KR South Korea
CN China GD Grenada KW Kuwait
KY Cayman Islands PA Panama TV Tuvalu
KZ Kazakhstan PE Peru TW Taiwan
LA Laos PF Fren. Polynesia TZ Tanzania
LB Lebanon PG Papua Nw UA Ukraine
Guinea
LC St. Lucia PH Philippines UG Uganda
LI Liechtenstein PK Pakistan UM Minor Outl.Ins.
LK Sri Lanka PL Poland US United States
LR Liberia PM St.Pier, Miquel. UY Uruguay
LS Lesotho PR Puerto Rico UZ Uzbekistan
LT Lithuania PT Portugal VA Vatikanstadt
LU Luxembourg PW Palau VC St. Vincent
LV Latvia PY Paraguay VE Venezuela
LY Libya QA Qatar VG Brit.Virgin
Islands
MA Morocco RE Reunion VI US Virgin
Islands
MC Monaco RO Romania VN Vietnam
MD Moldavia RU Russian Fed. VU Vanuatu
MG Madagascar RW Rwanda WF Wallis, Futuna
MH Marshall island SA Saudi Arabia WS Western Samoa
ML Mali SB Solomon Islands YE North Yemen
MM Mali SC Seychelles YU Yugoslavia
MN Mongolia SD Sudan ZA South Africa
MO Macau SE Sweden ZM Zambia
MP North Mariana SG Singapore ZR Zaire
MQ Martinique SH St. Helena ZW Zimbabwe
MR Mauritania SI Slovenia
MS Montserrat SJ Slovenia
MT Malta SK Slowakei
MU Mauritius SL Sierra Leone
MV Maldives SM San Marino

Prepared for Dubai Refreshments Company by Atos Origin FZ LLC 24

. 24
 ABAP Programming Standards & Naming Conventions | ntegrated Project

ISO Country ISO Country ISO Country

Code Code Code
MW Malawi SN Senegal
MX Mexico SO Somalia
MY Malaysia SR Suriname
MZ Mozambique ST S.Tome, Principe
NA Namibia SV El Salvador
NC New Caledonia SY Syria
NE Nigeria SZ Swaziland
NF Norfolk Island TC Turks&Caicos Is
NG Nigeria TD Chad
NI Nicaragua TG Togo
NL Netherlands TH Thailand
NO Norway TJ Tadjikistan
NP Nepal TM Turkmenistan
NR Nauru TN Tunisia
NU Niue TP Tonga
NZ New Zealand TR Turkey
OM Oman TT Trinidad, Tobago

Contact people for this Project Charter:

www.atos.net Atos Origin FZ LLC

UAE
All rights reserved..
Atos Origin FZ LLC
The
Prepared for Dubai Refreshments Company by Atos Origin FZGalleries,
LLC Sheikh Zayed Road 25
. 25 Downtown Jebel Ali
PO Box 500437
Dubai, UAE