You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 68 Next »

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

ScopeTechnical nameDescriptionExample Technical nameExample description
CoreBW_WBK_ + Application Code +_CxxxBW - <Name> (Core Workbook)BW_WBK_PP_0001BW - Planning Situation (Core Workbook)
Scope SpecificBW_WBK_ + Application Code + CxxxBW - <Name> (<Scope> Specific)BW_WBK_CATS_9001BW - CATS Time Sheet (Brazil Specific)
BW - CATS Time Sheet (Novecare Specific)

Queries

TypeTechnical NameDescriptionExample Technical NameExample DescriptionComments
Core QueryBW + _ + QRY + _ + Infoprovider Name + _ + xxxxBW - <Name> (Core Query)BW_QRY_CUB_FIAR_0001BW - Days Overdues  (Core Query) 
Specific QueryBW + _ + QRY + _ + Infoprovider Name + _ + CxxxBW - <Name> (<Scope> Specific)BW_QRY_CUB_FIAR_9001BW - 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 prodBW + _ + QRY + _ + Infoprovider Name + _ + xxxxBW - <Name> (Development)BW_QRY_CUB_FIAR_0001BW - Days Overdues  (Development) If waiting for users to test.
Control QueryBW + _ + QRY + _ + Infoprovider Name + _ + xxxxBW - <Name> (Ctrl Query)BW_QRY_CUB_FIAR_0001BW - Days Overdues  (Ctrl Query) 
Query for QVQV_BW + _ + QRY + _ + Infoprovider Name + _ + xxxx<name> (QV)QV_BW_QRY_MVIPCO17_0001BW - 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 QueriesZTEST + _ + QRY + _ + Infoprovider Name + _ + xxxxZTEST - <Name> (Test Query)ZTEST_QRY_CUB_FIAR_0001ZTEST - Days Overdues (Test Query) 
Query for BroadcastBW + _ + QRY + _ + Infoprovider Name + _ + xxxx + BCAST<Name> (Broadcast)BW_QRY_CUB_FIAR_0001BW - Days Overdues  (Core Query) 
Jump queryBW + _ + QRY + _ + Infoprovider Name + _ + xxxx + JUMPBW - <Name> (Jump query)BW_QRY_CUB_FIAR_0001JumpBW - Days Overdues  (Jump Query) 
Backup QueriesBW + _ + QRY + _ + Infoprovider Name + _ + xxxx+ BCKBW - <Name> (Backup Query)BW_QRY_CUB_FIAR_0001BCKBW - 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_S001BW - 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 TypeTechnical Name RuleExample Technical Name
Restricted Key FigureBW_ RKF_ + Infoprovider Name+ _ + xxxxBW_RKF_CUB_FIAR_0001
Calculated Key FigureBW _CKF_ + Infoprovider Name + _ + xxxxBW_CKF_CUB_FIAR_0001
StructureSTR_ + InfoProvider + _XSTR_0SUPPLIER_0001
ViewVW_ + InfoProvider + _ + xxxxWV_0WORKCENTER_0001
VariableV_ + 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 FormulaVF_ + InfoObjet + _ + xxxxVF_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 - objectInfo-object technical nameVariables name
CRM marketing element(campaign and marketing plan)0CRM_MKTELMCRM_MKT0
CRM marketing element (PSP R/3 element)0CRM_MKTELECRM_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
Objt Object TypeTechnical nameMax sizeDescriptionExemple/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
   
INFOOBJETCATALOGUE CARATERISTIQUEIOCC_   
CATALOGUE RATIOIOCK_   
CharacteristicC_xxxxxxx9free description example Material plant (C_MATPLNT) 
Key FiguresK_xxxxxxx9  
DSOLSA level : Data Acquisition LayerDAmmffxx8DSO / (or start by DSO (direct update) /) 
LSA level : Propagation layerDPmmffdd8DSO / (or start by DSO (direct update) /) 
LSA level : Corporate memoryDCmmffdd8DSO / (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 layerDBmmffdd8DSO / (or start by DSO (direct update) /) 
INFOCUBEReporting levelCRmmffdd8  
MULTIPROVIDERVirtual levelMVmmffdd8  
VIRTUAL PROVIDERVirtual levelVVmmffdd8  
Composite ProviderVirtual levelCPmmffdd

8

  
INFOSETPropagation levelIFPmmffdd9  
Business Transf levelIFBmmffdd9  
Reporting levelIFRmmffdd9 

 

Virtual levelIFVmmffdd9  

Infosource

Harmonisation levelIH_mmff_dd  Mandatory
Propagation levelIP_mmff_dd   
Business levelIB_mmff_dd   
Reporting levelIR_mmff_dd   
INFOSOURCEIFS_mmff_dd   
DATASOURCEDATASOURCEDTS_mmff_dd  DTS_mmff_dd or DTS_<name of the table or view used>
INFOPACKAGEINFOPACKAGE<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
DTPDATA 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
TRANSFORMATIONTRANSFORMATION<generate by the system> TRSF: <generated name by system> 
Update RulesUpdate Rules (dev 3.x no more used for new dev only Transformation)  RMAJ: 
Transfert RulesTransfert Rules (dev 3.x no more used for new dev only Transformation)  RTRF: 
Open Hub DestinationOpenHub levelOH_<name of the projet>dd (with 2 digits at the end)9OH : <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
  

 

 

 

EVENTSM64 - background EventsZ_EVT_<free namming xxxx> In the description please add maximum of documentation where this event is used 

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
METAAll Types of Data
TDTransactional Data
MDMaster Data
HIERHierarchy
TXTTexts
BRCBroadcast

Frequency Codes

Frequency Description
YYear
MMonth
WWeek
DDay
HHour
nMevery n Month
nWevery n Week
nDevery n Day
nHevery n Hour
TTrigger
ADHAd-Hoc
OBJETTechnical nameComment
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 CHAINPC_Application_number_2digits or PC_project_number_2digits or PC_generaltopics_number_2digitseg. PC_FI_AP_01 or PC_WISE_01
PROCESS CHAIN DescriptionApplication: TYPE - Frequency - Freeeg. FIAP: TD - D -xxx
Start ProcessSTART_PROCESS CHAINSTART_SD_TD_001
ABAP ProgramAPGR_<technical name of the program>_<2digits> 
Decision Between Multiple AlternativesDCS_<free text + 2 digits> 
Enhanced Decision using formsEDCS_<free text + 2 digits> 
Delete IndexDIX_<technical name of the infoprovider>_<2 digits>we need to create 1 by 1 (one kind of this process by infocube)
Generate IndexGIX_<technical name of the infoprovider>_<2 digits>we need to create 1 by 1 (one kind of this process by infocube)
Construct Database StatisticsSTAT_<technical name of the infoprovider + 2 digits for the percentage of the compression> example : STAT_CUB_PS004_10we 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 IndexesRUA_<technical name of the infoprovider>_<2 digits> 
Initial Activation and Filling of SAP Hana/ BWA IndexesIAF_BIA_<technical name of the infoprovider>_<2 digits> 
Compression of the InfoCubeCOMP_<technical name of the infoprovider>_<2 digits>we need to create 1 by 1 (one kind of this process by infocube)
Activate DataStore Object DataACT_<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 targetDEL_DATA_<technical name of the infoprovider>_<2 digits> 
Attribute Change RunACR_<free text linked with the process chain + 2 digits> 
Deletion of request from PSAFor 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 InfoCubeDEL_OVERLAP_<XXX = 3 digits 001....999>_<technical name of the infoprovider> 
Interrupt ProcessITRP_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 tablesDEL_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 indexesDEL_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 indexesCREATE_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>

MessageMSG_<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 CommandOS_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 objectTechnical nameExample Technical Name
TypeT_ 
Internal table standardITB_ 
Internal table HASHEDITB_H_ 
Internal table SORTEDITB_S_ 
StructureS_ 
VariableV_ 
Field Symbol<FS_xxxx> 

Broadcasts

OBJET to broadcastTechnical nameExample Technical NameExample Description
WorkbookBW + _ + WB + _ + Domain + _ + xxxxBW_WB_FIAR_0001BW_WB_FIAR_TJADOT0001
QueryBW + _ + QRY + _ + Domain + _ + xxxxBW_QRY_FIAR_0001BW_QRY_FIAR_TJADOT0001
WADBW + _ + WAD + _ + Domain + _ + xxxxBW_WAD_FIAR_0001BW_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 :

OBJETTechnical nameExample Technical NameExample Description
Distribution listDL_<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

 

 

 

 

 

  • No labels