2011
Dr Bjarne Berg
Raj Vuppala
[SAP-BW OBJECTS NAMING STANDARDS ]
The Purpose of this document is to provide naming standards for all BW object types.
Version 1.1
SAP-BW Objects Naming Standards
The Purpose of this document is to provide naming standards for all custom BW object types created
during development to meet business requirements.
Note: Use available Business Content or Standard BW Objects as much as possible; can
change/modify/append the existing Standard InfoCubes to meet business requirement.
Business Area Identifiers
The objective of Business area identifier is to map 3 char to its relevant business function/group/area.
Reference to HD Smith
3 CharIdentifier
SLS
CTG
PSC
MKT
PUR
FIN
ACT
AUD
HRS
Business Function/ Business Area
IFT
Information Technology
Sales
Category Management
Prescription Products
Marketing
Purchasing
Finance
Accounting
Audit
Human Resource
Custom Objects
All custom objects start with “Z”.
All Local objects ($tmp) start with “Y”, however advised to clean local objects in the development
system after prototype etc.
Technical Name Syntax: ‘Z’+ ‘3char Business area Identifier’ +’_’+’Object type’
Position #
1
2-4
5
6
Custom object
Z (always)
SLS or CTG (3char Business Identifier, refer above
table)
‘-‘ (underscore)
Refer respective Object type
Last changed on 6/30/11
Page 1
Version 1.1
SAP-BW Objects Naming Standards
InfoArea
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
30
Position 1 will be Z (always)
Position 2 to 4 will beBusiness Function/ Business
Area identifier (for e.g.SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 to7 will be IA (always)
Position 7 onwards – Freeform (for e.g. SLS_OPR,
SLS_MKT etc.)
60
Freeform Business relevant description (need to
follow recommended Abbreviations, Punctuation,
terminology etc.)
Examples:
Technical Name
ZSLS_IA_SLS_OPR
0FMCO
Description
HD Smith Sales Operations InfoArea
Financial Management & Controlling (Business
content example)
MultiProvider
Technical Name
Max Length
Prefix
Last changed on 6/30/11
20
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “M” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
etc.)
Page 2
Version 1.1
Description
Max Length
Prefix
SAP-BW Objects Naming Standards
60
Freeform Business relevant description(need to
follow recommended Abbreviations, Punctuation,
Terminology etc.)
Examples:
Technical Name
ZSLS_M01
0FC_MP21
Description
HD Smith Sales Operations Multiprovider
Payments (Business content example)
InfoCube
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
20
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “C” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
etc.)
60
Freeform Business relevant description ((need to
follow recommended Abbreviations, Punctuation,
terminology etc.)
Examples:
Technical Name
ZSLS_C01
0FC_C21
Last changed on 6/30/11
Description
HD Smith Sales Operations Infocube
Payments (Business content example)
Page 3
Version 1.1
SAP-BW Objects Naming Standards
InfoSet
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “I” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
etc.)
60
Freeform Business relevant description (need to
follow recommended Abbreviations, Punctuation,
terminology etc.)
Examples:
Technical Name
ZSLS_I01
0FC_IS01
Description
HD Smith Sales Operations Infoset
Business Partner Payment (Business content
example)
Datastore Objects (DSO)
Write-Optimized DSO
Note: Write-Optimized DSO for High Volume datasource e.g. Material Movements.
Technical Name
Max Length
Prefix
Last changed on 6/30/11
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “W” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
Page 4
Version 1.1
SAP-BW Objects Naming Standards
etc.)
Description
Max Length
Prefix
60
Freeform Business relevant description (need to
follow recommended Abbreviations, Punctuation,
terminology etc.)
Examples:
Technical Name
ZSLS_W01
Description
HD Smith Sales Operations DSO-Level1
(Business content example)
Standard DSO
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “O” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
etc.)
60
Freeform Business relevant description (need to
follow recommended Abbreviations, Punctuation,
terminology etc.)
Examples:
Technical Name
ZSLS_O01
0FC_DS21
Last changed on 6/30/11
Description
HD Smith Sales Operations DSO
Payments (Business content example)
Page 5
Version 1.1
SAP-BW Objects Naming Standards
VirtualProvider
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “V” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
etc.)
60
Freeform Business relevant description
Examples:
Technical Name
ZSLS_V01
Description
HD Smith Sales Operations VirtualCube
(Business content example)
Remotecubes
Technical Name
Max Length
Prefix
Last changed on 6/30/11
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area identifier (for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 will be “R” (always)
Position 7 will be 2 digits numeric number (always
it should be incremental number for e.g. 01, 02, 03
etc.)
Page 6
Version 1.1
Description
Max Length
Prefix
SAP-BW Objects Naming Standards
60
Freeform Business relevant description
Examples:
Technical Name
ZSLS_R01
Description
HD Smith Sales Operations VirtualCube
(Business content example)
Query
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area (max 3 Char, for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 to 25 will beBusiness relevant
abbreviated characters (for e.g. SALES, MKT, FIN,
HR etc.)
Note: From Position 6 based on the business
requirement, length can be anywhere between min
3 chars to max 19 chars.
Position 26 will be “_” (always underscore symbol)
Position 27 will be “Q” (always)
Position 28 to 30 will be 3 digits numeric value
(always it should be incremental number for e.g.
001, 002, 003 etc.)
60
Business relevant description (need to follow
recommended Abbreviations, Punctuation,
terminology etc.)
Examples:
Technical Name
Description
ZSLS_MKT_EXPENSES_Q001 HDS- Marketing Expenses Report
(Business content example)
Last changed on 6/30/11
Page 7
Version 1.1
SAP-BW Objects Naming Standards
InfoObject Catalog
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
30
Position 1 will be Z (always)
Position 2 to 4 will be Business Function/ Business
Area (max 3 Char, for e.g. SLS, PUR etc.)
Position 5 will be “_” (always underscore symbol)
Position 6 to 9 will be either CHAR or KFY
Position 10 will be “_” (always underscore symbol)
Position 27 will be “CATALOG” (always)
60
Freeform Business relevant description
Examples:
Technical Name
ZSLS_CHAR_CATALOG
ZSLS_KFYG_CATALOG
0FICA_CHA01
0FICA_KYF01
Last changed on 6/30/11
Description
HDS- Sales Characteristics Catalog
HDS- Sales Key Figures Catalog
FI-CA Attributes(Business content example)
FI-CA: Key Figures (Business content example)
Page 8
Version 1.1
SAP-BW Objects Naming Standards
InfoObjects
Chatacteristics - InfoObjects
When creating custom Characteristics Infoobject
Last 3 char identifier
Last 3 Char- Identifier
_DT
_ID
_NO
_DE
_AD
_CD
_IN
_NM
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
Meaning
For Dates (e.g. Document
date, Submission date etc.)
For ID (e.g. Customer ID, Doc
ID etc.)
For Number (e.g. Document
number etc.)
For Description
For Address
For Code (Multivalues Master
data e.g. Material Group etc.)
For Indicator (2 values only,
e.g. Y or N)
For Name
14
Position 1 will be Z (always)
Position 2 to 11 will be Freeform Business relevant
abbreviated characters
Position 12 will be “_” (always underscore symbol)
Position 13 to 14 will be 2 digits char identifier
(refer above table)
60
Freeform Business relevant description, always try
to make this short being meaningful.
Examples:
Technical Name
ZCUST_ID
ZSUBMSN_DT
0FC_REC_NR
Last changed on 6/30/11
Description
Customer ID
Submission date
Record Number (Business content example)
Page 9
Version 1.1
SAP-BW Objects Naming Standards
Key Figures - InfoObjects
When creating custom Key Figures Infoobject
Last 3 char identifier
Last 3 CharIdentifier
_AM
_RT
_NO
Meaning
For Amount (e.g. Sales Amount,
Price etc.)
For Rates (e.g. Sales %, Variance
% etc.)
For Number (e.g. Document
number etc.)
Technical Name
Max Length
Prefix
Description
Max Length
Prefix
14
Position 1 will be Z (always)
Position 2 to 11 will be Freeform Business relevant
abbreviated characters
Position 12 will be “_” (always underscore symbol)
Position 13 to 14 will be 2 digits char identifier
(refer above table)
60
Freeform Business relevant description, always try
to make this short being meaningful.
Examples:
Technical Name
ZSALES_AM
ZVARIANCE_RT
0FC_TO_PAY
Last changed on 6/30/11
Description
Sales Amount
Sales Variance Rate
Payment Amount (Business content example)
Page 10
Download

SAP-BW Objects Naming Standards v1.1