Вы находитесь на странице: 1из 28
SAP CCC Publié le 18/03/2014 Identification : GCODINCODIF_OBJECTS-SAN- ENG-B5 SAP Notes Coding of SAP objects

SAP CCC

Publié le 18/03/2014
Publié le 18/03/2014

Identification :

GCODINCODIF_OBJECTS-SAN-

ENG-B5

SAP Notes

Coding of SAP objects

Purpose : Coding of SAP objects

Purpose : Coding of SAP objects

Written by : G. Mauries

Written by : G. Mauries

Service : IMAT/Airbus Operations S.A.S.

Service : IMAT/Airbus Operations S.A.S.

Date

Validated by :

Contacts :

18/03/2014

PG Ranea

G. Mauries

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

Summary of revisions

Revision

Date

Reason for change or modification

A0 V1

24/01/1997

Original document - Written by: Pontier Addition of RE sub-domains: Reportings in all domains for SAP specific programme coding Ensure consistency of domain list and summary table Coding of Streamserve objects Remarks on object coding - quality notice

A0 V2

17/09/2001

A0 V3

05/11/2001

Integration of SAP version 4 changes (essentially, replacement of Matchcode by SearchHelp), coding of grouped, elementary and append search help

A0 V4

10/09/2002

Integration of Tech Data projects

A0 V5

11/10/2002

Integration of Corporate (Central Entity) projects Integration of function groups, functions and message classes

A0 V6

13/10/2002

A0 V7

08/01/2003

Integration of 4.6 for ABAP object, extension of object coding

A0 V8

26/03/2003

Integration of sub-domains HR and coding objects multi-natco

A1

08/04/2003

New codification class of development

A2

23/01/2004

Codification Include for User exit (project A380), new codification for Metrology and Unique Register of security

A3

12/02/2004

Minor evolutions on sub-domains codification

A4

19/05/2004

Adjust new class development for procurement, common class development and codification workflow object.

Add sub-domain RO at the domain P

Add projects codification for customer domain

A5

9/07/2004

Add new class development for reporting, Sub-domain for Tech-Data

A6

10/10/04

Minor evolution on jobs coding for well understanding

A7

22/11/04

Add modul PS codification and sub-domains, add sub-domains for domain Customers services

A8

22/12/04

Add sub-domains for domain Customer Services

A9

11/3/05

Add sub-domain for domain Logistic

B0

14/11/05

The sub-domains for domain Customer Services are not listed anymore : 2 first digits of the Managhas project’s code

B1

22/05/06

Add rules for naming convention of transport orders program ARP

B2

18/12/06

Add sub-domains and Development class for program ARP

B3

17/01/08

Add domain : Quality (Q) and sub-domain RE in Q and S, RE et RT subdomains in C

B4

07/04/08

Add new codification for Finance in the scope of Zephyr Project

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

B5

18/03/2014

Remarks on using search help (help view)

Add new codification for Logical File and Path in Sap Abap Program

Modification chapter 4.1 ES remplaces by SP for spain and BR by UK for United of Kingdom

CONTENTS

1. GENERAL

5

2. LIST OF DOMAINS AND SUBDOMAINS

5

3. DICTIONARY OBJECTS :

9

3.1. TABLES:

9

3.2. VIEWS:

9

3.2.1. STANDARD VIEWS:

9

3.2.2. VIEWS FOR ELEMENTARY SEARCH HELP:

9

3.3. STRUCTURES:

10

3.4. CLUSTER/POOL TABLES:

10

3.5. DATA ELEMENTS:

10

3.6. DOMAINS:

11

3.7. SEARCH HELP:

11

3.7.1. GROUPED SEARCH HELP:

11

3.7.2. ELEMENTARY SEARCH:

11

3.7.3. APPEND SEARCH HELP:

11

3.7.4. SEARCH HELP (Case :old HELP VIEW):

12

3.8. BLOCKING OBJECTS:

12

3.9. TABLE TYPES:

13

3.10.TYPE GROUPS:

13

4. PROGRAMMES:

14

4.1. REPORT:

14

4.2. POOL OF MODULES:

14

4.3. PROGRAMME VARIANTS:

15

4.4. PROGRAMME STATUS:

15

4.5. PROGRAMME DYNPROS:

15

4.6. INCLUDE FOR USER6EXIT IN A FUNCTION sap

15

5. TRANSACTION CODES:

16

6. DOMAIN MENUS:

16

7. FUNCTIONS:

17

7.1. FUNCTION GROUPS:

17

7.2. FUNCTIONS:

17

8. MESSAGE CLASSES:

18

9. DEVELOPMENT CLASSES:

19

10. OBJECT PROGRAMMES:

20

10.1.CLASSES:

20

10.2.INTERFACES:

20

11. CONTEXTS:

20

12. DIALOGUE MODULES:

21

13. LOGIC DATABASES:

21

14. Logical file and logical path in Abap Program

21

15. PROJECTS (EXTENSIONS):

22

16. SAPSCRIPT:

22

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

16.1.STANDARD TEXTS:

22

16.2.STYLE SHEETS:

22

16.3.FORMS:

22

16.4.STREAMSERVE FORMS:

23

16.5.TEXT OBJECT:

23

16.6.TEXT ID:

23

17. JOB:

24

18. LIS:

24

18.1.ANALYSIS STRUCTURES:

24

18.2.ANALYSES:

25

18.3.INFOSETS AND RATIOS:

25

19. QUERY:

25

20. REPORT PAINTER:

25

21. BW:

25

22. SM30:

25

23. Objects Workflow

26

23.1.objects type

26

23.2.standard task

26

23.3.Model Workflow

26

23.4.Role

26

24. Transport rules for ARP Program

27

24.1.Remarks

27

24.2.Naming convention for transport order

27

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

1. GENERAL Some of the modifications integrated in Version 5 (integration of Central Entity Corporate projects) are related to the system's history: before the integration of Airbus France and Central Entity projects in the same structure, there were two types of coding. In some cases, it would be too costly to change this arrangement, so we sometimes have two types of coding for the same domain or subdomain. When this is the case, we will specify the origin of the coding which will be shown in blue characters).

However, for any new project, it is essential to use the common rules.

2. LIST OF DOMAINS AND SUBDOMAINS

Customer Services domain:

C (modules PP,…)

Sub-domains of the Customer Services domain

The code of the sub-domain is the 2 first digits of the Managhas project’s code. Examples:

8D:

Material – IPC

8I :

Source Management System (SMS)

Exception: for transverse developments and BW the sub-domain is:

ZZ:

RE : reporting except reporting Technical Data RT : reporting Technical Data

All Customer Services sub-domains

Production domain (including the CBN part of spares and commercial):

P (module PP)

List of production subdomains:

DB : Basic data (parts schedules, work process sheets, workstations, CB : Calculation of needs, workload planning GA : Workshop management, order follow-up, labour follow-up MO : Assembly QM : Quality OT : Tooling

MI :

General and industrial resources

RE :

Reportings

)

WB : WBS element (Central Entity coding) MT : Metrology

RU : Unique Register of security RO : Repair Order

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

Logistic domain (including the logistic part of spares and commercial) :

M (module MM)

List of subdomains of the Logistic domain:

DB

:

Basic data (items, suppliers, contracts,

)

AC

:

Purchases, general purchases, orders

RF

:

Receipt of invoices

ST

:

Stock movements

WM : Stores

QM

 

: Quality

OT

:

Tooling

MI

:

General and industrial resources

RE

:

Reportings

SP

:

Spend analysis (Central Entity coding)

PO

:

Purchase Order (Central Entity coding)

TR

: Transit management (tracking + expedition)

EH

: Dangerous material

Finance domain:

F

(module FI)

 

List of subdomains of the Finance domain:

CG

: General Accounting

CF

: Supplier Accounting

CC

: Customer Accounting

CA

: Analytical Accounting (Airbus France coding)

PS

: Investments

CI

:

Fixed assets

TR

: Treasury

GE

: Management control

RE

: Reportings

HB

: Spares - IO

AV

: Subsidiaries

CS

: Consolidation

GD

: Advances / Travel expenses

TV

: VAT

L

(only in the scope of ZEPHYR project)

The list of subdomains (idem list above)

Sales domain (commercial):

S (module SD)

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

List of subdomains of the Sales domain:

VE : Sales DA : Aircraft documentation RE : Reportings

Quality domain :

Remark : In the past, the domain Quality was a sub-domain of others domains (P, M), now we have created a specific domain

Q (module QM) List of subdomains of the Quality domain :

RE : reportings

Human Resources domain :

H (module HR)

List of subdomains of the Human Resources domain:

RH : Général HR Inter & general reporting. HC : Head count OR : Organisation CA : Career management PA : Payroll TR : training CQ : Compentences & Qualification RE : Recruitment MO : Mobility PE : personnal dadabase HD : Hazardous material AC : Accounting

TI : Time managment

ME : Medical HT : Trainees UT : HR Utilities

Transversal modul PS

W (module PS)

List of subdomains :

DB : data base WB : WBS working breakdown structure OR : order RE : restitution ZZ : other

Analytical accounting domain (Central Entity coding) :

K (module CO)

List of subdomains of the Analytical Accounting domain (Central Entity coding):

BP : Business Planning CS : Consolidation EC : EC Reporting

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

CT : Cost Center Controlling CU : Cost Unit Controlling OR : Orders RP : Repository

System, procedure, general tool domain:

Z (all domains)

List of subdomains relating to systems, procedures, general tools:

ZZ :

General technical tools

ST :

Standard documentation

AR : Archiving RE : Reportings MG : Migration (Central Entity coding)

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

3. DICTIONARY OBJECTS :

3.1. TABLES:

16 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!D! !_!_!SAP domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!T! !_!_!_!_!_!_!Free on remaining positions

Example

!Z!D!P!G!A!T!8!0!N!_!_!_!_!_!_!_!

3.2. VIEWS:

3.2.1. STANDARD VIEWS:

16 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!D! !_!_! SAP domain on 1 !_!_!_! SAP subdomain on 2 !_!_!_!_!_!V! !_!_!_!_!_!_! Free on remaining positions

Example

!Z!D!P!G!A!V!0!0!_!_!_!_!_!_!_!_!

3.2.2. VIEWS FOR ELEMENTARY SEARCH HELP:

16 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

!Z!

!_!D! !_!_! SAP domain on 1 !_!_!_! SAP subdomain on 2 !_!_!_!_!_!V! !_!_!_!_!_!_!_!(Underscore)

!_!_!_!_!_!_!_!Name of elementary search help

© AIRBUS FRANCE OIAM – 2014

SAP Note

page 9/28

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

Example

!Z!D!F!C!A!V!_!Z!K!A!R!T!0!_!_!_!

3.3. STRUCTURES:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!D! !_!_!SAP domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!S! !_!_!_!_!_!_!Free on remaining positions

Example

!Z!D!P!G!A!S!8!0!N!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.4. CLUSTER/POOL TABLES:

10 positions.

!_!_!_!_!_!_!_!_!_!_! !Z! !_!D! !_!_!SAP domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!T! !_!_!_!_!_!_!Free on remaining positions

Example

!Z!D!P!G!A!T!0!0!_!_!

3.5. DATA ELEMENTS:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!P!O!I!N!T!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

3.6. DOMAINS:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!P!O!I!N!T!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.7. SEARCH HELP:

3.7.1.GROUPED SEARCH HELP:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!Free on remaining positions

Example

!Z!P!0!1!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.7.2. ELEMENTARY SEARCH:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Name of grouped search help!

!

!Sequential number on 1 position

Example

!Z!P!0!1!0!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.7.3. APPEND SEARCH HELP:

The purpose of this type of SEARCH HELP is simply to be included in a GROUPED SEARCH HELP under SAP.

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

!Z!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

!_!A! !_!_!Named of SAP grouped search help

Example

!Z!A!K!A!R!T!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.7.4. SEARCH HELP (Case :old HELP VIEW):

Remarks : The help views have been removed by SAP at the time of migration V3 to V4. The help views have been replaced by search help. The codification below has been defined only for the period of migration V3 to V4. Now this codification has not to use. For the codification of search help, you must refer to the chapter 3.7.1, 3.7.2, 3.7.3.

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Table name!

!

!_!H!V!

Example

!Z!D!P!G!A!T!8!5!N!_!H!V!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.8. BLOCKING OBJECTS:

16 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !E! !_!Z! !_!_!Table name

Example

!E!Z!Z!D!P!G!A!T!8!0!N!_!_!_!_!_!

or

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !E! !_!Table name

Example

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

!E!Z!D!P!G!A!T!8!0!N!_!_!_!_!_!_!

3.9. TABLE TYPES:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!M!A!T!N!R!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

3.10. TYPE GROUPS:

5 positions.

!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!P!O!I!N!T!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

4.

PROGRAMMES:

4.1. REPORT:

30 positions usable on 40 (SAP constraint).

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!P! !_!_!SAP domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!Programme technical function on 1 !_!_!_!_!_!_!Free on remaining positions with a minimum of 2

Technical functions:

B

:Batch input

R

:Reporting, provision of data(for or outside SAP)

T

:Simple transaction

I :Include

Z :Other

Example

!Z!P!P!G!A!R!0!0!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Remark : For projects multi-natco, and in order to differentiate the specific objects to be made in each entity, a naming convention is defined, identifying the entities :

DE for Germany SP for Spain FR for French UK for Great Britain

This naming is in the free place with _ before

Example : ZPHPAR_FR

4.2. POOL OF MODULES:

30 positions usable on 40(SAP constraint).

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !S!A!P!M! !_!_!_!_!Z! !_!_!_!_!_!Free on remaining positions with a minimum of 3

Example

!S!A!P!M!Z!0!0!1!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

4.3. PROGRAMME VARIANTS:

14 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Free

Example

!S!E!L!E!C!T!_!A!L!L!_!_!_!_!

4.4. PROGRAMME STATUS:

20 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Free

Example

!S!T!A!T!U!T!_!0!1!0!0!_!_!_!_!_!_!_!_!_!

4.5. PROGRAMME DYNPROS:

4 positions.

!_!_!_!_! Free but numerical

Example

!0!1!0!0!

4.6. INCLUDE FOR USER6EXIT IN A FUNCTION sap

Includes for user exit follow same rules than reports.(cf 3.1).

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

In some cases we have to create several subincludes linked to the same "master" include. For them we can use the same root and add at the end an underscore followed by a numeric suffix (2 characters).

30 positions usable on 40(SAP constraint).

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

!Z!

!_!P!

!_!_!SAP Domain on 1 !_!_!_!SAP Subdomain on 2 !_!_!_!_!_!I! ("include" function) !_!_!_!_!_!_!Free on remaining positions with 2 characters at minimum

!_! Numeric suffix on 2

Example Sub-include

!Z!P!P!C!B!I!0!2!_!0!1!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

5. TRANSACTION CODES:

20 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!Free on remaining positions with a minimum of 2

Example

!Z!P!0!0!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

6. DOMAIN MENUS:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!Free on remaining positions with a minimum of 2

Example

!Z!P!0!2!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

7.

FUNCTIONS:

7.1. FUNCTION GROUPS:

26 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!SAP subdomain on 2 !_!_!_!_!Free on remaining positions

Example

!Z!P!Q!M!_!C!O!R!P!O!R!A!T!E!_!_!_!_!_!_!_!_!_!_!_!_!

or

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!Free on 2 positions only(consequence of 3.1)

Example

!Z!P!0!2!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

7.2. FUNCTIONS:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!_!(underscore imposed by SAP) !_!_!Free on remaining positions

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

Example

!Z!_!S!E!N!D!_!M!S!G!_!T!O!_!M!E!S!S!A!P!P!L!I!_!_!_!_!_!_!_!

8. MESSAGE CLASSES:

20 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!SAP subdomain on 2 !_!_!_!_!Free on remaining positions

Example

!Z!P!Q!M!0!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

or

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!Free on 1 position only(consequence of 3.1)

Example

!Z!M!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

9. DEVELOPMENT CLASSES:

Rules to be respected are the following ones during the initialization and the implementation(positioning) of a new landscape system inter-natco

- Creation of specific classes of development for every domain integrated into this new landscape system

- Existence of a common class of development for objects not sensitives " transverses "or multi-domain : ZZ01

- Existence of development class for “sensitives” objects ex : APPEND on standard

These objects are managed by entity : Support and

tables, User-exit Services

: ZCOMMON

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

!Z!

List of classes of dévelopment :

- ZQUALITY

- ZASSEMBLY

- ZELEMENTS_PARTS

- ZLOGISTIC

- ZJIGS_AND_TOOLS

- ZPROCUREMENT

- ZSALES

- ZFINANCIAL

- ZHUMAN_RESSOURCES

- ZCUSTOMER_SERVICES

- ZDOCUMENTATION

- ZREPORTING (for the commons tools specifics of domain Reporting)

- ZZ01 : development class for objects not sensitives multi-domains

- ZCOMMON : development class for objects sensitives

Remarks :

- For the systems already in place, it was decided to keep the adopted codification even if this one does not correspond to that presented above.

- For some specific needs, and to protect developments from projects developers within same domain, additional development classes could be created in the future by OIBS with following format Zxxxxxxxxxx_yyyyy where xxxxxxxxxxx is the domain (ex:

ASSEMBLY) and yyyyy the project name (ex: IDMS scanning). This has to be exceptional.

Exceptions :

ZAGE_IDMS (objects come system xDA) ZFINANCIAL_EDI (objects GE implemented in Fr)

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

The packages (former development classes ) used for ARP are :

ZCOMMON

Package for common and sensitive objects

ZUNIF_PLANNING

Package for project : Unified planning objects

ZENG_MANUF_PREP

Package for project : Engineering Manufacturing and Preparation objects

ZSUPPLY

Package for project : Supply chain / Procurement / Logistics objects

ZINDUS

Package for project : Industrial Processes

ZINDUS_QUALITY

Package for project : Quality objects

ZMDATA

Package for project : Master Data objects

ZFINANCIAL

Package for project : Financial processes objects

ZRFID

Package for project : RFID objects

ZREPORTING

Package for project : reporting objects

These classes are in accordance with the differents projects of ARP.

10. OBJECT PROGRAMMES:

10.1. CLASSES:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!C!L! !_!_!_!_!(Underscore) !_!_!_!_!Free on remaining positions

Example

!Z!C!L!_!A!V!I!O!N!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

10.2. INTERFACES:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!I!F! !_!_!_!_!(Underscore) !_!_!_!_!Free on remaining positions

Example

!Z!I!F!_!C!O!U!N!T!E!R!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

11. CONTEXTS:

20 positions.

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!SAP subdomain on 2 !_!_!_!_!Free on remaining positions

Example

!Z!P!G!A!_!R!E!A!D!_!M!A!T!N!R!_!_!_!_!_!

12. DIALOGUE MODULES:

30 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!SAP subdomain on 2 .!_!_!_!_!Free on remaining positions

Example

!Z!P!G!A!_!U!P!D!T!_!A!U!F!N!R!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

13. LOGIC DATABASES:

20 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!SAP subdomain on 2 !_!_!_!_!Free on remaining positions

Example

!Z!P!G!A!_!O!R!D!E!R!_!_!_!_!_!_!_!_!_!_!

14. Logical file and logical path in Abap Program

Remark : This chapter concerns only the codification of logical FTP file and path. For some information on FTP Architecture and Conventions, you must see the sapnote :

GFTPNARCHITECTURE_CONVENTION

30 positions

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!SAP domain on 1 !_!_!_! Underscore

!_!_!_!pppp !_!_!_!_!_!_!_!_!Underscore !_!_!_!_!_!_!_!_!F or P

pppp: Code du projet

F : in the case Logical File, P : in the case Logical Path

© AIRBUS FRANCE OIAM – 2014

SAP Note

page 21/28

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

!_!_!_!_!_!_!_!_!_!free

ex : ZP_TP04_F_filenamex Production

codification du fichier logique : filenamex, projet : TP04, du domaine

15. PROJECTS (EXTENSIONS):

8 positions.

!_!_!_!_!_!_!_!_! !P!R!O!J! !_!_!_!_!_!(Underscore) !_!_!_!_!_!Free on remaining positions - name of SAP module recommended

Example

!P!R!O!J!_!P!P!_!

16. SAPSCRIPT:

16.1. STANDARD TEXTS:

32 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!_!L!O!G!O!_!A!I!R!B!U!S!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

16.2. STYLE SHEETS:

8 positions.

!_!_!_!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!S!T!Y!L!E!0!_!

16.3. FORMS:

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

16 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Z! !_!S! !_!_!SAP domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!F! !_!_!_!_!_!_!Free on remaining positions

Example

!Z!S!P!G!A!F!_!O!R!D!E!R!_!_!_!_!

16.4. STREAMSERVE FORMS:

16 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !Y! !_!Name of SAP form from position 2

Example !Z!S!P!G!A!F!_!O!R!D!E!R!_!_!_!_! (SAP)

!Y!S!P!G!A!F!_!O!R!D!E!R!_!_!_!_! (STREAMSERVE)

16.5. TEXT OBJECT:

10 positions.

!_!_!_!_!_!_!_!_!_!_! !Z! !_!Free on remaining positions

Example

!Z!T!X!T!_!_!_!_!_!_!

16.6. TEXT ID:

4 positions.

!_!_!_!_! !Z! !_!SAP subdomain on 2 !_!_!_!Free on remaining positions

Example

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

17.

!Z!Q!M!1!

JOB:

32 positions.

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !J! !_!SAP domain on 1 !_!_!SAP subdomain on 2 !_!_!_!_!Free on remaining positions

Example

!J!P!C!B!_!M!R!P!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

or for Corporate Systems

!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_! !J! !_!SAP domain on 1 !_!_!SAP subdomain on 2 !_!_!_!_!Entity on 1 !_!_!_!_!_!_!(underscore) !_!_!_!_!_!_!Free on remaining positions

Example

!J!F!B!P!H!_!J!O!B!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!_!

List of entities

A

Airbus France

B

Airbus GIE

R

ATR

H

Airbus Headquarters(Corporate /Central Entity)

Z

Airbus Germany

S

Airbus Spain

K

Airbus UK

Remark : for the new landscapes (PEA, PEM, PBA), a new codification is presented in the Sapnote : ARP_SCHEDULING_REQ_USAGE

18. LIS:

18.1. ANALYSIS STRUCTURES:

8 positions.

!_!_!_!_!_!_!_!_!

!Z!

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

!_!SAP subdomain on 2 !_!_!_! LIS application code on 2 (standard SAP coding) !_!_!_!_!_!Free on remaining positions

The standard SAP structures start with the letter S.

18.2. ANALYSES:

4 positions.

!_!_!_!_! !Z! !_!Free on remaining positions

18.3. INFOSETS AND RATIOS:

8 positions.

!_!_!_!_!_!_!_!_! !Infoset domain or ratio on 1 !_!Infoset subdomain or ratio on 1 !_!_!P! !_!_!_!Type of infoset or ratio on 1 (T for steering) !_!_!_!_!Free on remaining positions

19.

QUERY:

See Sapnote : QueryNUSE, GQUERY_AIDE, GUTIL_QUERY

20.

REPORT PAINTER:

See Sapnote RPAINTER01n.doc

21.

BW:

See Sapnote BWNAMING_OBJECTS

22.

SM30:

See Sapnote : GTRANSAC_SM30

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

23. Objects Workflow

23.1. objects type

Code on 10 positions

!_!_!_!_!_!_!_!_!_!_!

!Z! !_!name standard object if specific extension

23.2. standard task

Code on 12 positions

!_!_!_!_!_!_!_!_!_!_! _!_!

!Z!

!_!T! !_!_!SAP Domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!free on remaining positions

Designation on 40 positions

free

23.3. Model Workflow

Code on 12 positions

!_!_!_!_!_!_!_!_!_!_! _!_!

!Z!

!_!W! !_!_!SAP Domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!free on remaining positions

Designation on 40 positions

free

23.4. Role Code on 12 positions

!_!_!_!_!_!_!_!_!_!_! _!_!

!Z!

!_!R! !_!_!SAP Domain on 1 !_!_!_!SAP subdomain on 2 !_!_!_!_!_!free on remaining positions

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5

Designation on 40 positions

free

24. Transport rules for ARP Program

24.1. Remarks

These rules concern only the scope : ARP Program

24.2. Naming convention for transport order

To be able to manage transport order in ARP SAP landscape, it is crucial to define a naming convention to clearly identify which process team and which customizer is the owner of any transport order.

Naming convention for the field “short description” keeping in mind that the identifier of the requests and tasks beneath are automatically generated by the system.

Short description= <RRR>-<D><TT>- Short description of the content.

RRR = ARP Release (R10, R11, R20,

D = Domain

TT = SubDomain

Short description of the content = Short and significant description. For example :

etc.)

o

“Materiel Customization”

o

“bug fix 256 on order creation”

!_!_!_!RRR=ARP Release (R10, R11, R20,….,etc) !_!_!_!_!SAP Domain on 1 !_!_!_!_!_!_!SAP subdomain on 2 !_!_!_!_!_!_!Free on remaining positions e.g. “Materiel Customization”

Example of an order:

Transport of Material Customization for release R1.1 :

With

o

Domain Logistic : M

o

Sub Domain : Basic data : DB

R11-MDB-Material Customization

Coding of SAP objects

Identification : GCODINCODIF_OBJECTS-

SAN-ENG-B5