Reporting (Bex / Analysis)

CXXX : Incremental number, where C :
- 9 for Latin America specific object
- 3 for Asia Pacific specific object
- 7 for North America specific object
- 2 for Europe specific objects
Application codes list in the BW Applications page.

Workbooks

Scope	Technical name	Description	Example Technical name	Example description
Core	BW_WBK_ + Application Code +_Cxxx	BW - <Name> (Core Workbook)	BW_WBK_PP_0001	BW - Planning Situation (Core Workbook)
Scope Specific	BW_WBK_ + Application Code + Cxxx	BW - <Name> (<Scope> Specific)	BW_WBK_CATS_9001	BW - CATS Time Sheet (Brazil Specific) BW - CATS Time Sheet (Novecare Specific)

Queries

Type	Technical Name	Description	Example Technical Name	Example Description	Comments
Core Query	BW + _ + QRY + _ + Infoprovider Name + _ + xxxx	BW - <Name> (Core Query)	BW_QRY_CUB_FIAR_0001	BW - Days Overdues (Core Query)
Specific Query	BW + _ + QRY + _ + Infoprovider Name + _ + Cxxx	BW - <Name> (<Scope> Specific)	BW_QRY_CUB_FIAR_9001	BW - Days Overdues (Brazil Specific)	Cxxx where C is a number depending on the zone (see at the top this page)
Query to be approved in prod	BW + _ + QRY + _ + Infoprovider Name + _ + xxxx	BW - <Name> (Development)	BW_QRY_CUB_FIAR_0001	BW - Days Overdues (Development)	If waiting for users to test.
Control Query	BW + _ + QRY + _ + Infoprovider Name + _ + xxxx	BW - <Name> (Ctrl Query)	BW_QRY_CUB_FIAR_0001	BW - Days Overdues (Ctrl Query)
Query for QV	QV_BW + _ + QRY + _ + Infoprovider Name + _ + xxxx	<name> (QV)	QV_BW_QRY_MVIPCO17_0001	BW - PEC&CASH for Capex Dashboard (QV)	For PQ2 query, we will use an acronym for the QV dashboard using the data. (ex QVHR_ZPA_C01_Q0027)
Test Queries	ZTEST + _ + QRY + _ + Infoprovider Name + _ + xxxx	ZTEST - <Name> (Test Query)	ZTEST_QRY_CUB_FIAR_0001	ZTEST - Days Overdues (Test Query)
Query for Broadcast	BW + _ + QRY + _ + Infoprovider Name + _ + xxxx + BCAST	<Name> (Broadcast)	BW_QRY_CUB_FIAR_0001	BW - Days Overdues (Core Query)
Jump query	BW + _ + QRY + _ + Infoprovider Name + _ + xxxx + JUMP	BW - <Name> (Jump query)	BW_QRY_CUB_FIAR_0001Jump	BW - Days Overdues (Jump Query)
Backup Queries	BW + _ + QRY + _ + Infoprovider Name + _ + xxxx+ BCK	BW - <Name> (Backup Query)	BW_QRY_CUB_FIAR_0001BCK	BW - Days Overdues (Backup Query)	Used when for historical reasons a query doesn’t exist in development
Sub query or pre query	BW + _ + QRY + _ + Infoprovider Name + _ + Sxxx	BW - Sub Query <name>	BW_QRY_CUB_FIAR_S001	BW - Sub Query Days Overdues

Specifics rules for QlikView from WBP

1) Copy of the BW core query and rename it with the rules below :

Add QV_<technical name of the existing BW query>

example QV_BW_QRY_CUB001_001

2) Released for OLE DB for OLAP: Yes (option on the query) => Check to be done to be sure that QV can used this query

3) Saved the query on role Competence Centre Role -> folder for the QV project

Specifics rules for QlikView from PQ1

Naming Conversions (PQ1) - Obsolete --> Obsolete (just reference for old name)

Specifics rules for QlikView from PQ2

1) Copy of the BW core query and rename it with the rules below :

Add QVXXX_<technical name of the existing BW query> (XXX = acronym QV project (example SBS etc..))

example QVHR_ZPA_C01_Q0027

2) Released for OLE DB for OLAP: Yes (option on the query) => Check to be done to be sure that QV can used this query

3) Saved the query on role Competence Centre Role -> folder for the QV project

Other Reporting Objects

Object Type	Technical Name Rule	Example Technical Name
Restricted Key Figure	BW_ RKF_ + Infoprovider Name+ _ + xxxx	BW_RKF_CUB_FIAR_0001
Calculated Key Figure	BW _CKF_ + Infoprovider Name + _ + xxxx	BW_CKF_CUB_FIAR_0001
Structure	STR_ + InfoProvider + _X	STR_0SUPPLIER_0001
View	VW_ + InfoProvider + _ + xxxx	WV_0WORKCENTER_0001
Variable	V_ + InfoObjet +_ + xxxx	V_0PROFIT_CTR_0001 same for attribut of navigation V_0COMP_CODE_C_AUTHMA_001 or V_C_COMPCDE_C_AUTHMA_001 (about the same object C_AUTHMA but the settings could be differents so need to precise) For the description : In () add the nature of the variable Authorization check = (Auth check) or selection option, optional (Select option, optional) With ou without input when we have the case. Auth Scope on PM Order (Auth without input)
Variable Formula	VF_ + InfoObjet + _ + xxxx	VF_0CALDAY_0001

Particular case for Variables :

During the creation of the variable, the system can refuse the technical name. 2 possibilities :

The technical name already exists for this info-object: it is enough to increment the 'x'.
The technical name is already to use by another info-object, of which the 7 first characters are identical. In this case, to take only the first 6 characters (after suppression of the prefixes '0' or 'C_') and to add an additional figure in front of the 'final x'.

Example :

Info - object	Info-object technical name	Variables name
CRM marketing element(campaign and marketing plan)	0CRM_MKTELM	CRM_MKT0
CRM marketing element (PSP R/3 element)	0CRM_MKTELE	CRM_MK10

Bapi & exists for variables :

How to Using ABAP Class instead of include ZXRSRU01

Workbench Objects

See list of Module Codes :

SAP FI Module- FI stands for Financial Accounting

SAP CO Module- CO stands for Controlling

SAP PS Module – and PS is Project Systems

SAP HR Module – HR stands for Human Resources

SAP PM Module – where Plant Maintenance is the PM

SAP MM Module – MM is Materials Management -

SAP QM Module - QM stands for Quality Management

SAP PP Module – PP is Production Planning

SAP SD Module – SD is Sales and Distribution

SAP BW Module – where BW stands for Business (Data) Warehouse

SAP EC Module – where EC stands for Enterprise Controlling

SAP TR Module – where TR stands for Treasury

SAP IM Module – where IM stands for Investment Management

SAP – IS where IS stands for Industries specific solution

SAP – Basis

SAP – ABAP

SAP – Cross Application Components

SAP – CRM where CRM stands for Customer Relationship Management

SAP – SCM where SCM stands for Supply Chain Management

SAP – PLM where PLM stands for Product LifeCycle Management

SAP – SRM where SRM stands for Supplier Relationship Management

SAP – CS where CS stands for Customer Service

SAP – SEM where SEM stands for STRATEGIC ENTERPRISE MANAGEMENT

SAP – RE where RE stands for Real Estate

In the following table, obsolete objets are highlighted in yellow and should not be used for new developments

Objt	Object Type	Technical name	Max size	Description	Exemple/Comment
INFO AREA	(level 0 : main functional module)	IA_mm		"Linked with the notion of the content + Business stream or Project : IA_mmff or IA_mmff_<lsa level> mm = primary module (FI, MM, HR) or MD for Master data ff = functional area (minus hyphens i.e. CO-PA use CO) example : IA_FI and IA_FI_PROPA or by application "
	(level 1 : sub functional module)	IA_mm_ff
	(level n : n sub functional module))	IA_mm_ff_ff_ff_ff....
	(Last level : technical level))	IA_<level n>_MD IA_<leveln>_HARMONISATION IA_<level n>_PROPAGATION IA_<level n>_ACQUISITION IA_<leveln>_BUSINESS_TRANSF IA_<level n>_REPORTING IA_<level n>_VIRTUAL IA_<level n>_CORPORATE
INFOOBJET	CATALOGUE CARATERISTIQUE	IOCC_
	CATALOGUE RATIO	IOCK_
	Characteristic	C_xxxxxxx	9	free description example Material plant (C_MATPLNT)
	Key Figures	K_xxxxxxx	9
DSO	LSA level : Data Acquisition Layer	DAmmffxx	8	DSO / (or start by DSO (direct update) /)	Should not be used anymore for new dataflows on BW7.5 on Hana
	LSA level : Propagation layer	DPmmffdd	8	DSO / (or start by DSO (direct update) /)
	LSA level : Corporate memory	DCmmffdd	8	DSO / (or start by DSO (direct update) /)	(mm = Module ff = functional xx = 2 digits) Example DBFIAR01 if module > 2 characters we keep only the functional module example : module FSCM and functionnal module CLM so the technical is DBCLM01
	LSA level : Business Transformation layer	DBmmffdd	8	DSO / (or start by DSO (direct update) /)	(mm = Module ff = functional xx = 2 digits)
ADSO	LSA++ level : Acquisition layer	AAmmffdd	8		(mm = Module ff = functional xx = 2 digits)
	LSA++ level : Propagation layer	APmmffdd	8		(mm = Module ff = functional xx = 2 digits)
	LSA++ level : Corporate memory	ACmmffdd	8		(mm = Module ff = functional xx = 2 digits)
	LSA++ level : Business Transformation layer	ABmmffdd	8		(mm = Module ff = functional xx = 2 digits)
OPEN ODS View	Open ODS view	OOmmffdd	8		(mm = Module ff = functional xx = 2 digits)
INFOCUBE	Reporting level	CRmmffdd	8		Should not be used anymore for new dataflows on BW7.5 on Hana
MULTIPROVIDER	Virtual level	MVmmffdd	8		Should not be used anymore for new dataflows on BW7.5 on Hana
VIRTUAL PROVIDER	Virtual level	VVmmffdd	8
Composite Provider	Virtual level	CPmmffdd	8
INFOSET	Propagation level	IFPmmffdd	9		Should not be used anymore for new dataflows on BW7.5 on Hana
	Business Transf level	IFBmmffdd	9
	Reporting level	IFRmmffdd	9
	Virtual level	IFVmmffdd	9
Infosource	Harmonisation level	IH_mmff_dd			Mandatory
	Propagation level	IP_mmff_dd
	Business level	IB_mmff_dd
	Reporting level	IR_mmff_dd
	INFOSOURCE	IFS_mmff_dd
DATASOURCE	DATASOURCE	DTS_mmff_dd			DTS_mmff_dd or DTS_<name of the table or view used>
INFOPACKAGE	INFOPACKAGE	<generate by the system>		IP: <datasource name> <system> - <loading mode : Full, Delta, Init w/o or Init with data)	IP: 0FI_AR_4 Acetow - Delta
DTP	DATA TRANSFERT PROCESS	<generate by the system>		DTP: <generated name by system with renaming of system (Rhodia, Acetow, Solvay ...)>--<loading mode : Full, Delta, Init w/o or Init with data)>	DTP: 0DPM_0 / Acetow -> DPDM04 - Full DTP: 0CLM_BPARTNER (CICC) -> DPCLM03 - Full
TRANSFORMATION	TRANSFORMATION	<generate by the system>		TRSF: <generated name by system>
Update Rules	Update Rules (dev 3.x no more used for new dev only Transformation)			RMAJ:
Transfert Rules	Transfert Rules (dev 3.x no more used for new dev only Transformation)			RTRF:
Open Hub Destination	OpenHub level	OH_<name of the projet>dd (with 2 digits at the end)	9	OH : <Name of the project & free comment>	ID : OH_MDM01 Description : OH : Extraction for MDM based on the infocube CUB_FIAP1
APPLI COMPONENT	(level 0 : main functional module)	ZAPCO_mm		Same architecture as Info Area
APPLI COMPONENT	(level 1 : sub functional module)	ZAPCO_mm_ff
APPLI COMPONENT	(level n : n sub functional module))	ZAPCO_mm_ff_ff_ff_ff....
APPLI COMPONENT	(Last level : technical level))	ZAPCO_<level n>_MD ZAPCO_<leveln>_HARMONISATION ZAPCO_<level n>_PROPAGATION ZAPCO_<level n>_ACQUISITION ZAPCO_<level n>_BUSINESS_TRANSF ZAPCO_<level n>_REPORTING ZAPCO_<level n>_VIRTUAL ZAPCO_<level n>_CORPORATE ZAPCO_<level n>_OPENHUB
EVENT	SM64 - background Events	Z_EVT_<free namming xxxx>		In the description please add maximum of documentation where this event is used
HANA PACKAGES	LEVEL 0	SOL		Package hierachy is made in mirror of the infoarea structure Root package where all Solvay's specific objets are developped
	LEVEL 1 (main functional module)	SOL.mm		mm = primary module (FI, MM, HR) or MD for Master data
	(level 2 : sub functional module)	SOL.mm.ff		ff = functional area (minus hyphens i.e. CO-PA use CO) example : IA_FI and IA_FI_PROPA or by application
	(level n : n sub functional module))	SOL.mm.ff. ... .ff
	Last level : technical level	SOL.mm.ff. … .ff.MD SOL.mm.ff. … .ff.ACQ SOL.mm.ff. … .ff.VIRT		Master data RAW data acquisition Virtual Layer	To store data loaded directly to Hana To store Hana views used in the modelisation
Calculation views	Calculation views	CV_mm_<description>		mm = module	the description gives information about the calculation view content
Decision table	Decision table	DECT_mm_<Description>

Transport Order

Let Solman decide of the description except for some SAP system w/o Solman

Example GUDSIS or Solman itself

In this case the namming is :

BW/<e-ticket number from freshdesk>/<ddd>/<free description>

the ddd = 3 digits

example BW/FR45698/001/ Add new infocube for Solman reporting or BW/FR45698/00/ Add new query)

Below the link for the customization of Datasources : BAPI instead CMOD

Process Chain

Types Codes

TYPE	Description
META	All Types of Data
TD	Transactional Data
MD	Master Data
HIER	Hierarchy
TXT	Texts
BRC	Broadcast

Frequency Codes

Frequency	Description
Y	Year
M	Month
W	Week
D	Day
H	Hour
nM	every n Month
nW	every n Week
nD	every n Day
nH	every n Hour
T	Trigger
ADH	Ad-Hoc

OBJET	Technical name	Comment
Display Component	DICO + _ + PC + _ + Module + _ + project (you create sub-display component as below for example : Warning : see wiki page about the release of display component https://wiki.solvay.com/x/8aKYAQ	Example : DICO_PC_QM_BUSINESS
PROCESS CHAIN	PC_Application_number_2digits or PC_project_number_2digits or PC_generaltopics_number_2digits	eg. PC_FI_AP_01 or PC_WISE_01
PROCESS CHAIN Description	Application: TYPE - Frequency - Free	eg. FIAP: TD - D -xxx
Start Process	START_PROCESS CHAIN	START_SD_TD_001
ABAP Program	APGR_<technical name of the program>_<2digits>
Decision Between Multiple Alternatives	DCS_<free text + 2 digits>
Enhanced Decision using forms	EDCS_<free text + 2 digits>
Delete Index	DIX_<technical name of the infoprovider>_<2 digits>	we need to create 1 by 1 (one kind of this process by infocube)
Generate Index	GIX_<technical name of the infoprovider>_<2 digits>	we need to create 1 by 1 (one kind of this process by infocube)
Construct Database Statistics	STAT_<technical name of the infoprovider + 2 digits for the percentage of the compression> example : STAT_CUB_PS004_10	we need to create 1 by 1 (one kind of this process by infocube) description example : Stats CUB_PS004 10%
Roll Up of Filled Aggregates/BIA Indexes	RUA_<technical name of the infoprovider>_<2 digits>
Initial Activation and Filling of SAP Hana/ BWA Indexes	IAF_BIA_<technical name of the infoprovider>_<2 digits>
Compression of the InfoCube	COMP_<technical name of the infoprovider>_<2 digits>	we need to create 1 by 1 (one kind of this process by infocube)
Activate DataStore Object Data	ACT_<technical name of the infoprovider> or <technical name of the infoprovider>_ACTIVATE_+<2digit if multi activation are mandatories> (Standard code generated by SAP)_<2 digits>
Deletion of Data target	DEL_DATA_<technical name of the infoprovider>_<2 digits>
Attribute Change Run	ACR_<free text linked with the process chain + 2 digits>
Deletion of request from PSA	For mono Datasource on InfoProvider : DEL_PSA_<Technical name of the datasource>_<source system> For multi Datasources on InfoProvider : DEL_PSA_<InfoProvider Name + 2 digit>	Eg (Mono DS) technical name : DEL_PSA_0COSTCENTER_ATTRPF1020 description :DEL_PSA_0COSTCENTER_ATTR_PF1_020 Eg (Multi DS) DEL_PSA_0SERVICE_01 For Multi Datasources on the same infoProvider only 5 parallel deletions are allowed
Delete Overlapping Requests from InfoCube	DEL_OVERLAP_<XXX = 3 digits 001....999>_<technical name of the infoprovider>
Interrupt Process	ITRP_EVENT_<2 digit> for Event ITRP_DRCT_SCHD_<2 digit> for Direct Scheduling	For description please add the detail of the frequency or the process chain which launch the event Eg. Wait Chain PC_<FREE> or ... or PC_<FREE> Eg. Wait 09.00 AM (French Time) each day
Deletion of request from Change Log tables	DEL_CHG_LOG_<InfoProvider Name + 2 digit> OR DEL_CHG_LOG_<Process Chain ID>	Eg: DEL_CHG_LOG_ODS_PA06_01 Eg: DEL_CHG_LOG_PC_FIGL_01 (Multiple del.)
Program deletion BWA indexes	DEL_BWA_<InfoProvider Name + 2 digit>	DEL_BWA_CUB_PP02_01 (in the process we can use the program RSDDTREX_INDEX_DELETE) Variant for program RSDDTREX_INDEX_DELETE must be named ZDEL_<InfoProvider Name>
Program create BWA indexes	CREATE_BWA_<InfoProvider Name + 2 digit>	CREATE_BWA_CUB_PP02_01 (in the process we can use the program RSDDTREX_BIA_ACTIVATE_FILL) Variant for program RSDDTREX_BIA_ACTIVATE_FILL must be named ZACT_<InfoProvider Name>
Message	MSG_<OK KO ALWAYS>_<free text about the process so maybe the name of the local process chain the technical name>	Example : MSG_OK_RCS_FA_KPI
OS Command	OS_CMD_<PROJECT>_<NAME>	Example: ZOS_CMD_PCM_RUN

Program ABAP for BW

ZBW_<technical name> description in English mandatory

For the program to delete the data inside infocube (select deletion) : transaction DELETE_FACTS

Abap code

ABAP object	Technical name	Example Technical Name
Type	T_
Internal table standard	ITB_
Internal table HASHED	ITB_H_
Internal table SORTED	ITB_S_
Structure	S_
Variable	V_
Field Symbol	<FS_xxxx>

Broadcasts

OBJET to broadcast	Technical name	Example Technical Name	Example Description
Workbook	BW + _ + WB + _ + Domain + _ + xxxx	BW_WB_FIAR_0001	BW_WB_FIAR_TJADOT0001
Query	BW + _ + QRY + _ + Domain + _ + xxxx	BW_QRY_FIAR_0001	BW_QRY_FIAR_TJADOT0001
WAD	BW + _ + WAD + _ + Domain + _ + xxxx	BW_WAD_FIAR_0001	BW_WAD_FIAR_TJADOT0001

Distribution list (SO23 or SO15)

Decision approved (March, 21th 2018) meeting BI team & CGI team :

One distribution list created / Stream (RTR, I&P, OTC, P2P and BW) only IT people + BI Team + CGI team could be integrated in the distribution list for the user :

ISPP
Or query based on master data C_BWAPP BW Application Char (need to add special process inside the process to indicate 25% 50% 75% 100% of loading and to be check by anyone for Solvay Domaine in ISSP web page)

Some new distribution list could be created for specific project with some peoples but need to review 2 or 3 times per year.

Important : Reminder : the distribution is not possible to transport it (not find how) so have to be done on WBD and redo on all the systems and after the contents of DL are only managed system by system.

Naming convention :

OBJET

Technical name

Example Technical Name

Example Description

Distribution list

DL_<free text max 3 characters>_<3 digits>

DL_RTR_001

DL_RTR_002

Distribution for RTR process chain

Distribution list for P&L process chain

Folder for Distribution list

= technical name of the distribution list

ISSP link

http://issp.solvay.com/issp/home/home.do?request_locale=fr_FR

Report → Loading Status

Page tree

BW Naming Conventions