100% found this document useful (1 vote)
1K views

Sap Naming Conventions

This document outlines SAP naming conventions for various objects, including the object name, maximum length, and acceptable customer name ranges. It provides naming guidelines for over 70 different types of objects in SAP systems, such as transactions, reports, tables, forms, and more. The naming conventions are intended to help customers standardize their naming to follow SAP best practices and avoid naming conflicts.

Uploaded by

api-27403075
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
1K views

Sap Naming Conventions

This document outlines SAP naming conventions for various objects, including the object name, maximum length, and acceptable customer name ranges. It provides naming guidelines for over 70 different types of objects in SAP systems, such as transactions, reports, tables, forms, and more. The naming conventions are intended to help customers standardize their naming to follow SAP best practices and avoid naming conflicts.

Uploaded by

api-27403075
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP Naming Conventions

Object Length Customer Name Range


Application log 4 Y* Z*
Object 10 Y* Z*
Subobject
Authorization/authorization profile 12 No "_" in second position
Authorization object 10 Y* Z*
Authorization object class 4 Y* Z*
Authorization object group 30 Y* Z*
CATT procedure 30 Y* Z*
Change document object 10 Y* Z*
Class 30 Y* Z**
(underscore permitted)
Code page 4 9000-9999
Data element 30 Y* Z*
Development class 30 Y* Z*
Dialog module 30 Y* Z* RP_9*
RH_INFOTYP_P9*
Documentation module 10 Like object name
Authorization object 12 Like object name
Authorization profile 20 Y* Z*
Chapter in a structure (CHAP) 20 Y* Z*
Description of a CATT procedure 28 Y* Z*
Dialog text 28 Y* Z*
General text (TX) 20 Y* Z*
Implementation Guide chapter 20 Y* Z*
Main chapter in a structure (BOOK) 26 Y* Z*
Note on chapter in a structure (NOTE) 20 Y* Z*
Release Notes 12 Y* Z*
Structure Y* Z*
Domain 30 Y* Z*
Enhancement 8 Y* Z*
Enhancement project 8 *
Enterprise Data Model (EDM) 10 Y* Z*
Data model 10 Y* Z*
Entity 10 Y* Z*
Function Builder 30 Y_* Z_*
Function module 26 Y* Z*
Function group 4 XZ*
User exit function module 4 *
User exit function module (customer-specific)
Object Length Customer Name Range
IDoc development 27 Z1*
Segment type 30 Z2*
Segment name 30 Y* Z*
Basic IDoc type 30 *
Enhancement type 30 *
Logical message
Info type number 4 9000 - 9999
Interface 30 Y* Z**
(underscore permitted)
LIS (Logistics Information System) 2 Y* Z*
Event 2 Y* Z*
Unit
Lock object 16 EY* EZ*
Logical database 20 Y* Z*
Maintenance and transport object 31 Y* Z*
Matchcode 1 0-9
Matchcode ID 4 Y* Z*
Matchcode object
Menu 20 Y* Z* +*
Message 20 Y* Z*
Message ID 3 900 - 999
Message number
Module pool 30 SAPDY* SAPDZ*
Module pool for dialog 30 DY* DZ*
INCLUDES 8/40 SAPMY* SAPMZ*
Module pool for screens 30 MY* MZ*
INCLUDES 30 MP9*
Module pool for info types 30 MP9*
INCLUDES 30 SAPFY* SAPFZ*
Module pool for subroutines 30 FY* FZ*
INCLUDES 30 SAPUY* SAPUZ*
Module pool for update program 30 UY* UZ*
INCLUDES
Number range document object 10 Y* Z*
Pool name/cluster name 10 Y* Z*
Printer macro - Y* Z* 9*
R/3 Analyzer: Identifier 20 Y* Z*
Relation ID 2 Y* Z*
Report 30 Y* Z*
Report category 4 Y* Z*
Object Length Customer Name Range
Report variant 14 X* CUS&*
Transportable, global 14 Y*
Transportable, local 1 Z*
Not transportable
Report Writer 8 1st place not numeric (0-9)
Report 4 1st place not numeric (0-9)
Report group 3 1st place not numeric (0-9)
Library 7 1st place not numeric (0-9)
Standard layout
SAPscript 16 Y* Z*
Form 4 Y* Z*
Standard text ID 32 Y* Z*
Standard text name 8 Y* Z*
Style
Screen 4 9000 - 9999
If the screen does not belong
to a module
Set 12 1st place not numeric
SPA/GPA parameter 20 Y* Z*
Spool 16 Y* Z*
Layout type 8 Y* Z*
Font family 8 Y* Z*
Device type 8 Y* Z*
Page format 8 Y* Z*
System barcode
Standard role 8 9*
Standard task 8 9*
Structures/structure fields 30 Y* Z*
SYSLOG message ID 2 Y* Z*
Table 10 Y* Z* T9* P9* PA9* PB9*
Pool and cluster tables 16/30 PS9* PT9* HRT9* HRP9*
Transparent tables 16 HRI9*
Table field YY* ZZ* (if possible in append)
Y* Z*
Transaction code 20 Y* Z* +*
Type (ABAP) 5 Y* Z*
View 16/30 Y* Z*
Help view 16/30 H_Y* H_Z*
View cluster 30 Y* Z*
Object Length Customer Name Range
View maintenance data - reserved in TRESC
View content - reserved in TRESC
Table content
Workflow object type 10 Y* Z*

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy