1.

Naming Standards

The naming convention recommendations vary depending on the type of BW object, except for the first position of the technical names. All descriptions should be as meaningful, yet concise, as possible. Position 1 Alpha character which represents the source of the object B = Superuser developed object (query objects only) Y = Temporary test object (candidate for deletion) Z = BW team developed object and all BW Roles 0 = SAP standard delivered business content

1.2

BW Objects

The following table identifies each of the BW objects and associated naming conventions. An example is also provided of the technical name. In addition to the technical name, there is a long description, which is freeform and is what the end-user sees and thus should be meaningful to all users. Object InfoAreas Max Size 30 Position 1 2+ InfoCubes 9 1 2-5 6 7 8-9 InfoObject Catalog 30 1 2-6 7 8-10 11+ InfoObjects 10 1 2+ Application Components 30 1 2-6 7 8+ Value Meaning 0MMPUR BSC Examples Purchasing Scorecard

B,Y,0 Source Identifier Functional area. If no functional area exists, then use freeform. B,Y,0 Source Identifier Functional area (variable length - may be 4 characters max) use all or part of the InfoArea name. _ Underscore C Cube Numerical (in sequence) beginning with 01 B,Y,0 Source Identifier Functional areause entire InfoArea name _ Underscore CHA Characteristic KYF Key Figure

0CCA_C01 standard BCCA_C01 extended BSCFI_C01 custom

0MMPUR_CHA01 BSC_KYF01

Numerical (in sequence) beginning with 01 B,Y,0 BCUST_ID Source Identifier Freeform, but note that if using an SAP provided object as reference, just replace the first position (0) and keep the remainder of the name. Also, do NOT use technical field names from a source system. Instead, make the object name as English-like as possible. B,Y 0MM Source Identifier 0MM-IO Functional area BSC_IO _ Underscore IO for master data only

1 InfoSources

B,Y,0-9

Source Identifier

2LIS_02_S012

Page 1 of 3

Object (transaction data only)

Max Size 30

Position 2-6 7 8+

Value

Meaning

Examples 0FI_AP_1 BLIS_02_S012 BSC_01

Functional areause entire Application Component name _ Underscore Numerical (in sequence) beginning with 01. If the data source is an LIS InfoStructure, follow the convention used in the example B,Y _ Freeform Source Identifier Underscore

Source Systems

10

1 2 3+

B_FLATFILE B_LEGACY Y_TEST

BW Variables

Hierarchies (internal to BW)

30

Note: if R/3 is the source system the technical name is assigned by BW and consists of the environment and client (i.e., PC1_001) B,Y,Z,0 0QCUST1 1 Source Identifier C,F,H, BCDCUST1 2 Variable Type: N,T Characteristic BCCCUST1 Formula Hierarchy Hierarchy Node Text C,D,R, 3 Processing by: S,U Customer exit Default value Replacement path SAP exit User entry 4+ Freeform, but note that if using an SAP provided variable as reference, just replace the first position (0) and keep the remainder of the name. B,Y B0CUSTOMER_H01 1 Source Identifier BBCUST_ID_H01 2-11 InfoObject technical name _ 12 Underscore H 13 Hierarchy 14+ 2 digit sequential number - beginning with 01 1 2-10 11 12 13+ B,S,Y,Z Source Identifier InfoCube technical name _ Underscore Q Query 4 digit sequential number - beginning with 0001 B,Y,Z Source Identifier InfoCube technical name _ Underscore S Structure 3 digit sequential number - beginning with 001 B,Y,Z,0 Source Identifier 0PUR_C001_Q0003 B0PUR_C01_Q0001 BBSCR_C01_Q0001 Z0PUR_C01_Q0099 SBSCR_C01_Q0002 1 Query names MUST be unique within all of BW. Use S in 1st position for SEM-only queries. 0PUR_C01_S001 B0PUR_C01_S001 ZBSCR_C01_S007 Structures and templates MUST be unique within all of BW 0TOTUSQTAVG

Queries 1

30

Query Structures And Templates

30

1 2-10 11 5 6+ 1

Calculated and

30

Page 2 of 3

Object Restricted Key Figures Development Class

Max Size

Position 2+

Value Freeform Z BW, SEM

Meaning

Examples B_AVG_SALES Z_AVG_SALES ZBW (R/3) ZBWA (BW Admin. WB) Queries: ZFIN Fin. Analysis ZPRO Procurement ZPRJ Projects ZPVR Vol & Rev ZRSV - Reserves Costs and Allocations TRANS / Full Cost Center ATTR / Init. Delta Cost Element TEXT / Delta ZCCA_C01_L0001

30

1 2-4

Source Identifier SAP Module

InfoPackage

30

1-30

Flat File & Logical File Name *Note that length of InfoCube Technical Name may vary.
1

15

1 2- 10 11 12 - 15

Developers cannot control the InfoPackage technical name (i.e. ZPAK). However, the description should encompass the functional nature of the data being extracted, whether it is transactional, master data, texts, or hierarchies, and whether it is a Full, Initialize Delta, or Delta load. Z Required by BW InfoCube L #### InfoCube Technical Name Indicator for Logical File Name Number sequence

the naming conventions for queries cannot be enforced since queries can be defined in the production environment. Query definition is controlled via security access to the transaction for defining/creating queries. There are no naming conventions for workbooks as they are created by end-users who execute the query and can save the workbook to either their Favorites or to Roles to which they are authorized. They must also be unique within Favorites and Roles.

Page 3 of 3