1.Naming Conversion:
4.7.4 Table
Index
SAP has reserved name ranges for all custom objects. These name
ranges must be used to ensure that custom objects will not be overwritten by
SAP objects during the import of a new maintenance level or release upgrade.
The naming conventions covered in this section support the SAP standards and in
many cases add to them. These standards are meant as a guide to ensure
consistency in development and modification.
Objects are reserved for your use in the following manner:
- Locate the object you wish to reserve.
- Determine what the fixed part of the name must be. For instance, the first three characters of an ABAP/4 name have precisely defined meanings.
- Use SAP Utilities to determine which objects have been defined already using the fixed portion of the name.
- Based on this list and the standards for the object, determine a value for the unique identifier portion of the name.
- Create the appropriate object with the object name chosen.
2.Document Format :
Object Name : Sap R/3 Requirements :
This section describes the development standards for the project.
At a minimum, this will match SAP standards. Typically the project standards
will build upon SAP requirements to create a more meaningful name of the
customized object. This section may also state the reasoning behind the
additional naming conventions.
3.Functional Descriptors:
Most object names will have a Position to denote the SAP module
related to the object being developed.
This is known as the Functional Descriptor. This should relate to the area within SAP
that the program is being developed for.
This may or may not be related to the Project Team that requested the
object.
To find the appropriate SAP module it may be helpful to look at
similar SAP objects to find its related application component. This can be found looking at the Development
Class assigned to an object. Drill down
on the Development Class to see its application component. Or use SE81 to browse the Application
Hierarchy.
Functional Descriptor
|
SAP Module
|
Description
|
A
|
Advanced Planner
and Optimizer –
|
|
B
|
BW
|
SAP Business
Information Warehouse
|
C
|
CO
|
Controlling
|
C
|
IM
|
Investment
Management
|
F
|
AC
|
Accounting - General
|
F
|
FI
|
Financial
Accounting
|
H
|
PA
|
Personnel
Management
|
H
|
PE
|
Training and
Event Management
|
H
|
PT
|
Personnel Time
Management
|
H
|
PY
|
Payroll
|
L
|
LE
|
Logistics
Execution
|
L
|
LO
|
Logistics -
General
|
M
|
MM
|
Materials
Management
|
P
|
PM
|
Plant Maintenance
|
P
|
PP
|
Production
Planning and Control
|
Q
|
QM
|
Quality
Management
|
S
|
CS
|
Customer Service
|
S
|
SD
|
Sales and
Distribution
|
U
|
BC
|
Basis Components
|
X
|
CA
|
Cross-Application
Components
|
Z
|
Programmer work
ABAP
|
ABAP/4 REPORT PROGRAMS
Within the SAP environment the name of an ABAP report or program
must be unique. In R/3, ABAP reports are not client specific. An ABAP developed
in one client is available and useable in all other clients. The first three
characters of the ABAP name convey what application area it is relevant to and
what it does.
The naming standards for ABAP/4 Report programs are divided in 2
categories:
·
Custom Developed
·
Programmer’s Work ABAP
Custom Developed ABAP/4 Reports
A custom developed ABAP/4 Report programs is a new development.
SAP R/3 Requirements:
Custom developed ABAP/4 Report programs should be between 8 and 30 characters long
and start with Y or Z. SAP delivered ABAP/4 reports begin
with an R.
Standards:
The following naming convention for ABAP/4 Reports will be
invaluable when using data dictionary searches. For instance, all reports
written relate Warehouse Management Interface Programs by specifying ZLI*.
Format:
Z
|
X
|
x
|
xxxxx
|
xxxxxx
|
|
|
|
|
|
|
|
|
Optional
|
|
|
|
|
|
|
Unique Identifier
|
|
|
|
|
|
Program Type
|
||
|
|
Functional Descriptor
|
|||
Custom Indicator
|
||||
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom Indicator
|
Z
|
Custom Developed ABAP/4 Report
|
2
|
Functional Descriptor
|
See Functional Descriptor Section
|
|
3
|
Program
|
R
|
Report
|
Type
|
I
|
Inbound Interface
|
|
O
|
Outbound Interface
|
||
C
|
Conversion
|
||
E
|
Enhancement
|
||
D
|
Data Warehouse
|
||
K
|
Clone
|
||
N
|
New Development, Bolt-On
|
||
P
|
Print
|
||
S
|
System Maintenance
|
||
T
|
Data Dictionary Maintenance
|
||
U
|
User Exit/Validation Subroutine
|
||
4-8
|
Unique Identifier
|
000-ZZZ
|
Unique Identifier within the system. If necessary, use
positions in the Unique Identifier to further differentiate ABAP
development. Example: Position 4 could
be a project indicator.
|
9-30
|
Optional
|
Further descriptors such as ‘_TOP’ for a reports data
statements
|
Example: ZMR00010
1.1 Programmer Work ABAPs
The naming conventions in this section help distinguish utility
and work ABAPs that programmers use during development and analysis. If these
ABAPs are ever to be transported to a Production instance, they should be
renamed using Custom Developed Naming
Conventions.
Standard Format:
ZZ
|
xxx
|
xxx...xxx
|
|
|
|
|
Free form
|
|
|
Programmer’s Initials
|
|
Identifier
|
||
Position
|
Description
|
Values
|
Meaning
|
1
|
Identifier
|
Z
|
Custom Developed ABAP/4 Report
|
2
|
Functional Descriptor
|
Z
|
Identifies as a Programmer’s work ABAP
|
3-5
|
Programmer’s Initial
|
Initial’s of the responsible programmer
|
|
6-30
|
Free Form
|
000-ZZZ
|
Descriptive to the programmer
|
Example: ZZEJP001
This is a programmer’s personal ABAP. The programmer’s initials
are EJP.
1.2 ABAP Includes
Includes use the same naming standards as reports.
1.3 BDC SESSION
SAP R/3 Requirements:
A BDC session name may be a maximum of 12 characters long..
Standard:
Naming convention for BDC sessions will vary depending on the
needs of a customer. In many cases, the naming conventions for BDC sessions
need to be worked in conjunction with the Security Administrator.
Considerations:
·
BDC session names do not require unique names.
Standard Format:
Z
|
xxxx
|
x
|
x
|
xxxxx
|
|
|
|
|
|
|
|
|
Open
|
|
|
|
|
|
|
Program Type
|
|
|
|
|
|
Functional Indicator
|
||
|
|
Transaction Code
|
|||
User Defined
|
||||
Position
|
Description
|
Values
|
Meaning
|
1
|
Identifier
|
Z
|
User Defined BDC Session
|
2-5
|
Transaction Code
|
Can be longer than 4 if necessary
|
|
6
|
Functional Descriptor
|
See Functional Descriptor Section
|
|
7
|
Program Type
|
C,I, O, E
|
Conversions, Interface, Enhancement, etc
|
8-12
|
Open
|
Example: ZVA02SI00001
·
BDC Session to run VA02 for inbound interface.
2. BUSINESS ADD-IN (BAdI)
SAP R/3 Requirements:
Implementation Names
must start with Z and may be a maximum of 30 characters long..
Standard:
Name should begin with
‘Z_’. The remaining characters are open. Remaining characters should denote the
purpose of the BAdI or the Definition used.
Format:
Z
|
_
|
Xxxxxx
|
|
|
|
|
Open
|
|
|
Separator
|
|
User
Defined
|
||
Position
|
Description
|
Values
|
Meaning
|
1
|
Identifier
|
Z
|
User
Defined Class
|
2
|
Separator
|
_
|
Separator
|
3-30
|
Open
|
Descriptive
Name
|
Example: Z_CKML_COST_SPLIT
BAdI implementation for
CKML_COST_SPLIT.
3. CLASS / INTERFACE
SAP R/3 Requirements:
A Class or Interface
name may be a maximum of 30
characters long..
Standard:
Name should begin with Z_
followed by CL for Class or IF for Interface, followed by
Underscore ‘_’. The remaining characters
are open.
Considerations:
Class names for BAdI's are generated by SAP.
Format:
Z
|
_CL_
_IF_
|
x
|
xxxxxx
|
|
|
|
|
|
|
Open
|
|
|
|
|
Functional
Indicator
|
|
|
|
Class
or Interface
|
||
User
Defined
|
|||
Position
|
Description
|
Values
|
Meaning
|
1
|
Identifier
|
Z
|
User
Defined Class
|
2-5
|
Class
or Interface Indicator
|
_CL_
|
Class
|
_IF_
|
Interface
|
||
6
|
Functional
Descriptor
|
See
Functional Descriptor Section
|
|
7-30
|
Open
|
Descriptive
Name
|
Example: Z_CL_MMATERIAL_HANDLING
Custom Class for
Material handling.
4. DATA DICTIONARY
4.1 Data Elements
SAP R/3 Requirements:
Data element names must begin with a Z or Y, can be a maximum of 30 characters long and must be unique within a database instance.
Standard:
Where possible, use the same name as the domain associated with
the data element. If there is a conflict, name the data element in a meaningful
manner. SAP does create Data Elements that begin with a Z, so custom Data Elements should begin with ZZ.
Data element names should have a maximum of 8 characters. SAP generated programs or functions may use this dictionary object definition for
SELECT-OPTIONS and PARAMETERs, which may be up to 8
characters long.
Format:
ZZ
|
Xxxxxx
|
|
|
DDIC name identifier
|
Identifier
|
|
Position
|
Description
|
Values
|
Meaning
|
1-2
|
Type
|
ZZ
|
Always
ZZ
|
3-8
|
DDIC
name identifier
|
Open
|
A
meaningful name describing the data element
|
Example: ZZOBJTNM
This data element identifies object names.
4.2 Data Element Supplements
SAP R/3 Requirements:
Data Element Supplements must begin with a 9, can be a maximum of 4 characters long.
Standard:
Begin Supplement with 9.
Format:
9
|
Xxx
|
|
|
DDIC name identifier
|
Identifier
|
|
Position
|
Description
|
Values
|
Meaning
|
1
|
User
Defined
|
9
|
Always
9
|
2-4
|
Unique
ID
|
000-999
|
Numeric
value
|
Example: 9777
4.3 Domains
SAP R/3 Requirements:
Domain names and must begin with a Z or Y, can be a maximum
of 30 characters long and must be
unique within a database instance.
Standard:
Where possible, use an existing Domain. If that is not possible,
name the Domain in a meaningful manner.
Domain names should have a maximum of 10 characters.
Format:
ZZ
|
xxxxxxxx
|
|
|
DDIC name identifier
|
Custom Identifier
|
|
Position
|
Description
|
Values
|
Meaning
|
1-2
|
Custom
Identifier
|
ZZ
|
Always
ZZ
|
3-10
|
DDIC
name identifier
|
Open
|
A
meaningful name describing the data element
|
Example: ZOBJTNM
This domain identifies object names
4.4 Lock Object
SAP R/3 Requirements:
When creating a Lock Object, the file name must begin with EY or EZ and can be a maximum of 16
characters long.
Standard Format:
EZ_
|
Xxxx
|
|
|
Primary
Table
|
Custom
Identifier
|
|
Position
|
Description
|
Values
|
Meaning
|
1-2
|
Custom
Identifier
|
EZ
|
Custom
developed Lock Object
|
3-10
|
Primary
Table
|
X(8)
|
The
name of the primary table entered in the primary table field of the Lock
Object create screen
|
Example: EZ_ZA100
4.5 Search Help
Formerly known as Matchcode Objects. Typically created to provide custom ‘F4’
functionality. Custom Elementary Search
Helps can be included within SAP Collective Search Helps as an Append Search
Help to add custom Search Helps to standard transactions.
SAP R/3 Requirements:
Custom Search Helps must begin with a Z or Y and can be up to 10
characters long.
Standards:
Use the SAP Search Helps when possible, otherwise create a custom
Search Help.
Format:
Z
|
x
|
xxxxxxxxxx
|
|
|
|
|
Unique
Identifiers
|
|
|
Functional
Area
|
|
Custom
Identifier
|
||
Position
|
Description
|
Values
|
Meaning
|
1
|
Type
|
Z
|
Custom developed
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3-10
|
Unique Identifiers
|
00-ZZ
|
Uniquely identifies the Search Help
|
Example: ZMQMEL_HU
Matchcode for Custom
Table ZMQMEL_HU
4.6 Pools/Clusters
SAP R/3 Requirements:
A pool or cluster name must begin with Z or Y and can be a
maximum of 10 characters long.
Standards:
The naming standard insures that pool/cluster will be unique and
won’t interfere with any SAP defined pools/clusters. Use the same convention as Transparent
tables.
Note: This should be
discouraged.
4.7 Tables
4.7.1 Table Names - Transparent and Cluster
SAP R/3 Requirements:
User tables may begin with ‘Z’,
‘Y’, or ‘T9’ and can be a
maximum of 16 characters long.
Standard Format:
Each custom Table should begin with a Z followed by the Functional Descriptor to which it most closely fits. The remaining
characters can be a description.
Table names should not exceed 7 characters. If all 10 characters
are used, SAP generated programs will have difficulty because of generated
fields and indexes.
Format:
Z
|
x
|
xxxxxxxxxx
|
|
|
|
|
Unique
Identifiers
|
|
|
Functional
Descriptor
|
|
Custom
Identifier
|
||
Position
|
Description
|
Values
|
Meaning
|
1
|
Type
|
Z
|
Custom Table
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3-10
|
Unique Identifier
|
Alpha/numeric Description
|
Example: ZMQMEL_HU
Custom table related to QMEL.
4.7.2 Table Names - ATAB
SAP R/3 Requirements:
User tables must begin with ‘Z’,
‘Y’, or ‘T9’ and can be a
maximum of 16 characters long.
Standard Format:
SAP uses table ATAB for its own purposes and it is not
recommended that customers use it for their own customized pooled tables. However, if adding new tables to the ATAB
pooled table becomes necessary, a maximum of 5 characters must be used. The first character of the table must be a
‘T’ to indicate that it is an ATAB table.
The second character must a ‘9’ to identify the ATAB table as a client
(non-SAP supplied) table. The remaining
three characters are open.
Each custom Table defined to ATAB should begin with a T9 followed
by a unique identifier.
IT IS NOT RECOMMENDED TO CREATE ATAB TABLES.
Format:
Position
|
Description
|
Values
|
Meaning
|
|
1-2
|
Type
|
T9
|
Identifies as Custom ATAB
|
|
3-5
|
Unique
Identifier
|
000-ZZZ
|
Alpha/Numeric Description
|
|
Example: T9100
Custom table defined to
ATAB
4.7.3 Table Fields
SAP R/3 Requirements:
User fields can be up to 16 characters long and must be unique
within a table definition.
Standards:
·
Where possible, use the same name as the data
element associated with this field. If multiple fields in the table use the
same data element, name these fields in a meaningful manner.
·
Where possible, use an existing SAP data
element.
·
Do not use spaces or special characters in a
table field name.
Format:
Position
|
Description
|
Values
|
Meaning
|
1-10
|
Identifier
|
X(10)
|
Description identifying fields
|
Example: LOANNUM
This would denote the loan number field.
4.7.4 Table
Index
Standards:
Begin with a Z and have a maximum length of 3 characters.
Standard Format:
Z
|
Xx
|
|
|
Open
|
Custom
Identifier
|
|
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom
Identifier
|
Z
|
Custom
Index
|
2-3
|
Open
|
4.8 Type Group
SAP R/3 Requirements:
User-defined TYPE may be up to 5 characters long and must begin
with a Z.
Standard Format:
Type Pools are defined with transaction SE11, begin with a Z and
are 5 characters long. TYPE-POOL should be associated with a particular
functional area.
Z
|
X
|
xxx
|
|
|
|
|
Unique
identifier
|
|
|
Functional
Descriptor
|
|
Custom
Indicator
|
||
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom Indicator
|
Z
|
Custom Indicator
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3-5
|
Unique Identifier
|
0-Z
|
Unique identifier
|
Example: ZF001
Custom Type to hold financial TYPEs.
4.9 Structure
SAP R/3 Requirements:
A Structure name may be up to 30 characters long and must begin
with Z or Y.
Standards:
The use of underscores
‘_’ is encouraged to improve readability.
Keep the name as short and descriptive as possible. Use SAP generated names for Append Structures
where appropriate (ZA followed by SAP table name).
Format:
Z
|
x
|
_S_
|
xxxxxxxx
|
|
|
|
|
|
|
Unique
Identifiers
|
|
|
|
|
Structure
Identifier
|
|
|
|
Functional
Descriptor
|
||
Custom
Identifier
|
|||
Position
|
Description
|
Values
|
Meaning
|
1
|
Type
|
Z
|
Custom Structure
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3-30
|
Unique Identifier
|
Alpha/numeric Description
|
Example: ZS_S_VBAP
Custom structure related to VBAP.
Table Types
SAP R/3 Requirements:
A Table Type may be up to 30 characters long and must begin with
Z or Y.
Standards:
The use of underscores
‘_’ is encouraged to improve readability.
Keep the name as short and descriptive as possible.
Format:
Z
|
x
|
_T_
|
xxxxxxxx
|
|
|
|
|
|
|
Unique
Identifiers
|
|
|
|
|
Table
Type Identifier
|
|
|
|
Functional
Descriptor
|
||
Custom
Identifier
|
|||
Position
|
Description
|
Values
|
Meaning
|
1
|
Type
|
Z
|
Custom Structure
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3-5
|
Table Type Indicator
|
_T_
|
Indicates this is a Table Type
|
3-10
|
Unique Identifier
|
Open
|
Alpha/numeric Description
|
Example: ZS_T_VBAP
Custom Table Type related to VBAP.
VIEWS
SAP R/3 Requirements:
A View must begin with ‘Z’
or ‘Y’ may be a maximum of 16 characters long.
Standard Format:
Custom Views should begin with a ZV followed by the View Type and a separator. The remaining fields should be used to
identify the primary table for the view.
Z
|
V
|
X
|
_
|
xxxxxxx
|
|
|
|
|
|
|
|
|
Primary
Table name
|
|
|
|
|
|
|
Separator
|
|
|
|
|
|
View
Type
|
||
|
|
View
|
|||
Custom
View Identifier
|
||||
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom View Identifier
|
Z
|
Custom created View
|
2
|
View Indicator
|
V
|
Indicates View
|
3
|
View Type
|
H
|
Help View
|
D
|
Database View
|
||
P
|
Projection View
|
||
C
|
Customizing View
|
||
4
|
Separator
|
_
|
Underscore
|
5-10
|
Primary Table Name
|
primary table
|
Primary Table used in the View
|
Example: ZVD_ZFACH
Custom database view with primary table ZFACH
DEVELOPMENT CLASSES
Development class is used in the Correction/Transport system. It
is used to group all objects that are related to the same development to ensure
they are corrected and transported together. Each development class has an
assigned integration system and an assigned consolidation system for
transports.
SAP R/3 Requirements:
Class names must begin with
Z or a Y and can be a maximum of 4
characters long.
Standards:
With careful attention to naming, development standards can serve
to identify a related group of SAP objects. For example, an inbound interface
process may consist of many custom developed SAP objects all of which may or
may not interact in an obvious manner. If this process to change, it would be
simple to determine the entire group of objects that were created for this
process if they belonged to the same development class, thus facilitating quick
impact assessment when changing one of the objects. Development Classes should
be created by the System Administrator with input from the analyst when a
design specification package is being assembled. Any additional developments that relate
directly to the process should fall under the same development class.
Standard Format:
Z
|
x
|
x
|
9
|
|
|
|
|
|
|
|
Open
|
|
|
|
|
|
Dev Class Type
|
||
|
|
Functional Indicator
|
|||
User Defined
|
||||
Position
|
Description
|
Values
|
Meaning
|
1
|
Identifier
|
Z
|
User Defined BDC Session
|
2
|
Functional Descriptor
|
See Functional Descriptor Section
|
|
3
|
Dev Class Type
|
R
|
Reports
|
I
|
Interfaces
|
||
C
|
Conversions
|
||
E
|
Enhancements
|
||
4
|
Open
|
1-9
|
Number 1 - 9
|
Example: ZSR1
Development Class for Sales Reports
DIALOG MODULE
The use of Dialog Modules is not recommended.
Modularization should be done using Function Modules only.
Dialog Program
SAP R/3 Requirements:
Custom Dialog module pools begin with ‘SAPDY’ or ‘SAPDZ’ and can
be a maximum of 8 characters long. The module pool has a program attribute of
‘M’.
Standard:
The name has to begin with SAPD. The fifth character must be a Z.
Format:
SAPDZ
|
x
|
Xx
|
|
|
|
|
Unique
Identifier
|
|
|
Functional
Descriptor
|
|
Identifier
|
||
Position
|
Description
|
Values
|
Meaning
|
|
1-5
|
Identifier
|
SAPDZ
|
Custom Module Pool for Dialog
|
|
6
|
Functional
Descriptor
|
See Functional Descriptor Section
|
||
7-8
|
Unique identifier
|
00-ZZ
|
two digit alpha-numeric to uniquely identify
|
|
Example: SAPDZM01
Module Pool Dialog for Materials Management.
Dialog Include
SAP R/3 Requirements:
Custom Dialog module pools Includes begin with ‘DY’ or ‘DZ’ and
can be a maximum of 30 characters
long. The module pool dialog Include has a program attribute of ‘I’.
Standard:
INCLUDES for dialog programs have to begin with the last 5
characters of the module pool name. It
should then be followed by a three-digit identifier.
Format:
DZxxx
|
xxx
|
|
|
Include
identifier
|
Indicates
as custom Dialog Module pool Include
|
|
Position
|
Description
|
Values
|
Meaning
|
1-5
|
Identifier
|
DZxxx
|
Identifies as custom Module Pool include. Last 5 characters of module pool name.
|
6-8
|
Include Identifier
|
TOP
|
Data Fields
|
Ixx
|
Screen Input, where nn
is a two-digit alpha-numeric
|
||
Oxx
|
Output, where nn
is a two-digit alpha-numeric
|
||
Fxx
|
Forms, where nn
is a two-digit alpha-numeric
|
Example: DZM01I01
PAI Include for Dialog module SAPDZM01
MODULE POOL for Screens
An ABAP/4 module pool is a group of ABAP/4 programs that accesses
common processing modules, checks and processes user inputs during a
transaction. The module pool is also a means of linking all the associated
screens, menus and function keys of the interface as a transaction.
Unlike an ABAP/4 program, a module pool consists entirely of
‘Include’ programs. These Includes contain the appropriate processing logic.
Include programs have a program attribute type of ‘I’.
Module Pool Program
SAP R/3 Requirements:
Custom module pools begin with ‘SAPMY’ or ‘SAPMZ’ and can be a
maximum of 30 characters long. The module pool has a program attribute
of ‘M’.
Standard:
Screen module pool names should begin with SAPMZ followed by a 1 character functional descriptor. The last 3 digits of the name should be a
unique alphanumeric identifier. Includes form module pools should be generated
by SAP and the name generated should not be changed.
Format:
SAPMZ
|
x
|
Xx
|
|
|
|
|
Unique
Identifier
|
|
|
Functional
Descriptor
|
|
Identifier
|
||
Position
|
Description
|
Values
|
Meaning
|
|
1-5
|
Identifier
|
SAPMZ
|
Custom Module Pool for Dialog
|
|
6
|
Functional
Descriptor
|
See Functional Descriptor Section
|
||
7-8
|
Unique identifier
|
00-ZZ
|
two digit alpha-numeric to uniquely identify
|
|
Example: SAPMZP01
Dialog program for manual label request.
Module Pool Include
SAP R/3 Requirements:
Custom Dialog module pools Includes begin with ‘MY’ or ‘MZ’ and
can be a maximum of 8 characters long.
The module pool dialog Include has a program attribute of ‘I’.
Standard:
INCLUDES for dialog programs have to begin with the last 5
characters of the module pool name. It
should then be followed by a three-digit identifier.
Format:
MZxxx
|
Xxx
|
|
|
Include
identifier
|
Indicates
as custom Dialog Module pool Include
|
|
Position
|
Description
|
Values
|
Meaning
|
1-5
|
Identifier
|
MZxxx
|
Identifies as custom Module Pool include. Last 5 characters of module pool name.
|
6-8
|
Include Identifier
|
TOP
|
Data Fields
|
Ixx
|
Screen Input, where nn
is a two-digit alpha-numeric
|
||
Oxx
|
Output, where nn
is a two-digit alpha-numeric
|
||
Fxx
|
Forms, where nn
is a two-digit alpha-numeric
|
Example: MZP01TOP
Global Data for Module Pool SAPMZP01
TRANSACTION CODES
SAP R/3 Requirements:
Custom transaction code may be 20 characters and should begin
with a Z, Y, or + (+ for area menus).
Standards:
Starting the transaction code with a Z followed by the application type¸ program type and a
numeric sequence number insures that the transaction code will be unique and
won’t interfere with existing SAP code.
Format:
Standard Format:
Z
|
x
|
x
|
xxxx
|
|
|
|
|
|
|
Unique
Identifier
|
|
|
|
|
Program
Type
|
|
|
|
Functional
Descriptor
|
||
Customer
Transaction
|
|||
Position
|
Description
|
Values
|
Meaning
|
1
|
Type
|
Z
|
Custom Transaction
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3
|
Program Type
|
R
|
Report
|
I
|
Interface
|
||
C
|
Conversion
|
||
E
|
Enhancement
|
||
N
|
New Development, Bolt-on
|
||
4-20
|
Unique Identifier
|
00-ZZ
|
Unique alpha-numeric sequence
|
Example: ZSR101
Custom Sales Report.
SMARTFORM / SAPSCRIPT
1.1 Smartforms
SAP R/3 Requirements:
Smartform names must begin with ‘Z’ or ‘Y’ and can be a
maximum of 30 characters long.
Standards:
Name should begin with
‘Z’. When copying an Smartform, keep
same name following Zx_.
Format:
Z
|
x
|
_
|
x(27)
|
|
|
|
|
|
|
|
Descriptive Identifier
|
|
|
|
|
|
always underscore
|
||
|
|
Functional Descriptor
|
|||
Custom Indicator
|
||||
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom Indicator
|
Z
|
Custom Indicator
|
2
|
Functional Descriptor
|
See Functional Descriptor Section
|
|
3
|
Separator
|
_
|
always underscore
|
4-30
|
Descriptive Identifier
|
SAP Layout set name
|
Example: ZM_LB_BIL_INVOIC
1.2 Layout Set
SAP R/3 Requirements:
SAPscript Form names must begin with ‘Z’ or ‘Y’ and can be a
maximum of 16 characters long.
Standards:
Name should begin with
‘Z’. When copying an SAP form, keep same
name following Zx_.
Format:
Z
|
x
|
_
|
x(13)
|
|
|
|
|
|
|
|
Descriptive Identifier
|
|
|
|
|
|
always underscore
|
||
|
|
Functional Descriptor
|
|||
Custom Indicator
|
||||
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom Indicator
|
Z
|
Custom Indicator
|
2
|
Functional
Descriptor
|
See Functional Descriptor Section
|
|
3
|
Separator
|
_
|
always underscore
|
4-16
|
Descriptive Identifier
|
SAP Layout set name
|
Example: ZM_MEDRUCK
1.3 Standard Text ID
SAP R/3 Requirements:
SAPscript Standard text ID names must begin with ‘Z’ or ‘Y’ and can be a maximum of 4
characters long
Standard Format:
Z
|
Xxx
|
|
|
Unique Identifier
|
Custom Indicator
|
|
Position
|
Description
|
Values
|
Meaning
|
1
|
Custom Indicator
|
Z
|
Identifies as custom developed
|
2-4
|
Unique Identifier
|
00-99, AA-ZZ
|
Unique Identifier
|
1.4 Standard Text Name
SAP R/3 Requirements:
SAPscript Standard text names must begin with ‘Z’ or ‘Y’ and can be a maximum of 70 characters long.
Standard Format:
Z
|
_
|
X(30)
|
|
|
|
|
freely definable description
|
|
|
Always underscore
|
|
Custom Indicator
|
||
Position
|
Description
|
Values
|
Meaning
|
|
1
|
Custom Indicator
|
Z
|
Identifies as custom developed
|
|
2
|
Separator
|
_
|
always underscore
|
|
3-30
|
freely definable
|
00-99, AA-ZZ
|
Unique Identifier
|
|
1.5 Styles
SAP R/3 Requirements:
SAPscript Style names must begin with ‘Z_ ‘ or ‘Y_’ and can be
a maximum of 8 characters long.
Standard Format:
Z_
|
x(6)
|
|
|
freely definable
|
Custom Indicator
|
|
Position
|
Description
|
Values
|
Meaning
|
1-2
|
Custom Indicator
|
Z_
|
Identifies as custom developed
|
2-4
|
freely definable
|
00-99, AA-ZZ
|
Unique Identifier
|
No comments:
Post a Comment