SAP Note 16466 - Customer name range for SAP objects

Symptom:

Customers define their own objects. These objects may only be created under names that are not used by SAP.
Note: The naming conventions described in this Note are only planned for user-defined objects, that is, customer developments. For objects that are to be supplied to third parties, the concept of prefix name spaces for preventing name collisions is available as of Release 4.0 (also see Notes 84282 and 105132); the concept of partner projects is available in 3.* Releases (also see Note 39524).

Reason and Prerequisites

It is essential that you always adhere to the SAP naming conventions. Serious problems may otherwise result during the next upgrade (the upgrade overwrites customer objects).

Solution
Rule of thumb: The names reserved for customer objects start with 'Y' or 'Z'. Any additional subdivision (for example, 'Y'= headquarters, 'Z'= local offices) is up to the customer.
Note: as of Release 4.0A the maximum length of object names for some object types is extended. In the following table both the old and the new name lengths for these object types are given in column 3 (in the form old/new maximum lengths).
-----------------------------------------------------------------------
|Transp. |Length | |As of
Object |object |of name| Customer name range |Rel.
| |3.*/4.*| |
--------------------------|---------|-------|---------------------|----
Application log | | | |
Object | - - | 4/20 | Y* Z* |3.0A
Subobject | - - | 10/20 | Y* Z* |3.0A
Authorization/ | | | |
Authorization profile | | 12 | NO underscore |
| | | at 2nd position |
| | |Following characters can
| | | cause problems: # |
Authorization object |R3TR SUSO| 10 | Y* Z* |
Auth. object class |R3TR SUSC| 4 | Y* Z* |
Prof. Generator Default |R3TR SUSP| 10 | all except S* and J* |3.1G
Allocation Transaction | | | |
to authorization object |R3TR SUSK| 4/- | as transactions |3.1G
BSP application |R3TR WAPA| 30 | Y* Z* |6.10
BOMs |LIMU COMM| 10/20| Y* Z* |
CATT procedure |R3TR SCAT| 8/30 | Y* Z* |3.0C
Change document object |R3OB CHDO| 10 | Y_* Z_* |
|R3OB CHDO| 15 | Y_* Z_* |4.6A
|R3TR CHDO| 15 | Y_* Z_* |6.10
Class (ABAP objects) |R3TR CLAS| 30 | Y* Z* |4.5A
Code pages |R3TR SPCS| 4 | 9000 9999 |
Codepage segments |R3TR SPCS| 5 | 9* Y* Z* |6.10
(see also Note 534720)
Context |R3TR CNTX| 20 | Y* Z* |4.5A
Data element |R3TR DTEL| 10/30| Y* Z* |
Development class/package |R3TR DEVC| 4/30 | Y* Z* |
(see also 'Note on DataDictionary objects' at the end of this note)
Dialog module |R3TR DIAL| 30 | Y* Z* RP_9* |
| | | RH_INFOTYP_P9* |3.0E
Documentation modules: | | | |
General text (TX) |R3TR DOCT| 28 | Y* Z* |
Book chapter (CHAP) |R3TR DSYS| 20 | Y* Z* |
Notes (NOTE) |R3TR DSYS| 26 | Y* Z* |3.0A
Main chapter (BOOK) |R3TR DSYS| 20 | Y* Z* |
Chap. of Impl. Guide |R3TR DSYS| 20 | Y* Z* |
Descript. of Test Run |R3TR DSYS| 20 | Y* Z* |
Release notes |R3TR DOCV| 20 | Y* Z* |
Authorization object |R3TR DOCV| 10 | like the object name |
Authorization profile |R3TR DOCV| 12 | like the profile name|
Structure |R3TR DSYO| 12 | Y* Z* |
Text in dialog (DT) |R3TR DOCV| 28 | Y* Z* |
Domain |R3TR DOMA| 10/30| Y* Z* |
Extension |R3TR SMOD| 8 | Y* Z* |3.0C
Extension project |R3TR CMOD| 8 | * |3.0F
Function library | | | |
Function modules | - - | 30 | Y_* Z_* |
User exit funct. module |R3TR FUGS| 4/26 | XZ* |3.0C
User exit funct. module | | | |
(customer-specific) |R3TR FUGS| 4/26 | * |3.0C
Function group |R3TR FUGR| 4/26 | Y* Z* |
IDoc development | | | |
Segment type | - - | 7/27 | Z1* |3.0A
Segment name | - - | 10/30| Z2* |3.0
Logical message | - - | 6/30| Y* Z* |3.0
Basic IDoc Type |R3TR IDOC| 8/30| Y* Z* |3.0A
Extension type |R3TR IDOC| 8/30| * |3.0A
IDoc Type (only in 3.0) | - -| 8/--| Y* Z* |3.0A
Info type number | - - | 4 | 9000 ... 9999 |
Interface (ABAP objects) |R3TR INTF| 30 | Y* Z* |4.5A
LIS | | | |
Event |R3TR MCEV| 2 | Y* Z* |3.0D
Units |R3TR MCUN| 2 | Y* Z* |3.0D
Lock object |R3TR ENQU|10/16 | EY* EZ* |
Logical database |R3TR LDBA| 3/20 | Y* Z* |
Maint. and transport obj. |R3TR TOBJ|10/30 | Y* Z* |3.0C
Matchcode | | | |
Object |R3TR MCOB| 4 | Y* Z* |
ID for matchcode object |R3TR MCID| 1 | 0 ... 9 |
(no restrictions for IDs for your own matchcode objects)
Menu |R3TR PROG| 4/20 | Y* Z* |
|R3TR PROG| 4/20 | +* |3.0A
Message ID |R3TR MSAG| 2/20 | Y* Z* |
Message number SAP | - - | 3 | 900 ... 999 |
ID (no restrictions for message numbers for your own IDs)
Module pool dialog |R3TR PROG| 8/30 | SAPDY* SAPDZ* |
INCLUDES |R3TR PROG| 8/30 | DY* DZ* |
Module pool info type |R3TR PROG| 8/30 | MP9* |
INCLUDES |R3TR PROG| 8/30 | MP9* |
Module pool screen |R3TR PROG| 8/30 | SAPMY* SAPMZ* |
INCLUDES |R3TR PROG| 8/30 | MY* MZ* |
Module pool subroutine |R3TR PROG| 8/30 | SAPFY* SAPFZ* |
INCLUDES |R3TR PROG| 8/30 | FY* FZ* |
Module pool update task |R3TR PROG| 8/30 | SAPUY* SAPUZ* |
INCLUDES |R3TR PROG| 8/30 | UY* UZ* |
Number range object |R3OB NROB| 10 | Y* Z* |
|R3TR NROB| 10 | Y* Z* |6.10
OTR concept of a package |R3TR SOTR| 32 | Y* Z* |6.10
|R3TR SOTS| 32 | Y* Z* |6.10
Pool/Cluster name |R3TR SQLT| 10 | Y* Z* |
Printer macro | - - | | Y* Z* 9* |2.1G
(see also 'Note on DataDictionary objects' at the end of this note)
Relation ID (cluster ID) | - - | 2 | see Note 212246 |
Report |R3TR PROG| 8/30 | Y* Z* |
Report class | - - | 4 | 0* 9* |
Report variant | | | |
globally transportable | - - | 14 | X* CUS&* |3.0A
locally transportable | - - | 14 | Y* |3.0A
not transportable | - - | 14 | Z* |3.0A
Report Writer | | | |
Reports |R3OB REWR| 8 |first position not |1.0A
|R3TR REWR| |numeric (0 ... 9) |6.10
Report groups |R3OB REWR| 4 |first position not |1.0A
|R3TR REWR| |numeric (0 ... 9) |6.10
Libraries |R3OB REWR| 3 |first position not |1.0A
|R3TR REWR| |numeric (0 ... 9) |6.10
Standard layout |R3OB REWR| 7 |first position not |1.0A
|R3TR REWR| |numeric (0 ... 9) |6.10
R/3 Analyzer | | | |
Identifiers | - - | 20 | Y* Z* |3.0A
SAPscript | | | |
Layout set |R3TR FORM| 16 | Y* Z* |
Style |R3TR STYL| 8 | Y* Z* |
Standard texts ID | - - | 4 | Y* Z* |2.1A
Standard texts name | - - | 32 | Y* Z* |2.1A
Screen number SAP prog. | - - | 4 | 9000 ... 9999 |
(no restrictions with your own programs)
Search help |R3TR SHLP| 30 | Y* Z* |4.0A
Set |R3TR SETS| 12 |first position not |1.0A
| | |numeric |
SPA/GPA parameter |R3TR PARA| 3/20 | Y* Z* |
Spool | | | |
Device type |R3TR PRIN| 8 | Y* Z* |
Font families | - - | 8 | Y* Z* |2.1A
System barcodes | - - | 8 | Y* Z* |2.1A
Page format | - - | 8 | Y* Z* |2.1A
Format type | - - | 16 | Y* Z* |2.1A
Standard role |R3TR PDAC| 8 | 9* |3.0A
Standard task |R3TR PDAC| 8 | 9* |3.0A
SYSLOG message | | | |
Application area |R3TR SYAG| 2 | Y* Z* |
Table | | | |
(POOL, CLUSTER, TRANSP, |R3TR TABL|10/10 | Y* Z* T9* P9*|
INTTAB) | |10/16 | PA9* PB9* |3.0A
| |10/30 | PS9* |3.0A
| | | HRP9* HRT9* HRI9* |3.0E
| | | PT9* |3.0E
(see also 'Note on DataDictionary objects' at the end of this note)
Table field SAP table | - - |10/16 | YY* ZZ* |3.0A
Table index SAP table | - - | 3 | Y* Z* |3.0A
(No name restriction for fields and indexes of user-defined tables,
that is, those fulfilling the naming conventions mentioned above.
However, see 'Notes on table fields' at the end of this Note.)
(name length for tables/fields/indices/structures:
-pool/cluster tables additional max. 10-digit
-transp. tables and field names belonging to them up to 16-digit,
also other database objects (for example, database views)
-structure max. 30-digit)
Table type |R3TR TTYP| 30 | Y* Z* |4.0A
(see also 'Note on DataDictionary objects' at the end of this note)
Transaction code |R3TR TRAN| 4/20 | Y* Z* | |R3TR TRAN| 4/20 | +* |2.2G
Type group (ABAP/4) |R3TR TYPE| 5 | Y* Z* |3.0A
UDM | | | |
Entity |R3TR UENO|10/26 | Y* Z* |3.0A
Data model |R3TR UDMO|10/26 | Y* Z* |3.0A
View |R3TR VIEW|10/16 | Y* Z* |
Help view |R3TR VIEW|10/16 | H_Y* H_Z* |
(see also 'Note on DataDictionary objects' at the end of this note)
View cluster |R3TR VCLS|10/30 | Y* Z* |3.0C
View maintenance data | | | |
View contents | - - | - |reserved in TRESC |3.0A
Table contents | - - | - |reserved in TRESC |3.0A
Web Dynpro |R3TR WDYN| 30 | Y* Z* |6.30
Workflow object types |R3TR SOBJ| 10 | Y* Z* |
Note:
Some SAP objects appear to violate this naming convention. These objects were defined before the naming conventions were introduced. For reasons of compatibility we decided not to change these objects. The names of these objects (domains, data elements and tables) are listed in Table TDKZ. These objects cannot be used by customers.
Notes on table fields:
No database systems allow specified reserved words as field names for tables. Consequently, the R/3 ABAP Dictionary does not allow these reserved words for field names of database tables either.

Note on DataDictionary objects: Since release 4.0, data elements (R3TR DTEL), table types (R3TR TTYP), tables (R3TR TABL), views (R3TR VIEW), and pool/cluster names (R3TR SQLT) have been managed in one table. The names reserved in tables (and views) are therefore always interpreted as belonging to the customer name range also for the other object types. Since each possible name can be assigned only once (for all object types), however, you should use only the name ranges specified for the individual object types.