General presentation

Objective of the application

This application is not really a BW application, but a collection of DSO to provide data to an external tool nammed pVelocity.

pVelocity is a tool which help the Novecare GBU to optimize their Assets.

In BW, we extract the data from RCS and then generate flat files on a WBP folder and it is the pVelocity tool which is transfering the file from BW to pVelo.

IT Learder is now Nathalie Manirakiza in the IS-RtR team

The Tool Leader is in the Novecare GBU.

The reporting coordinator is Sandrine Micollet

 

Usage information

There is around 50 users on pVelocity tool WW, all working in the Novecare GBU.

They are Asset Manager, Industrial manager and also financial controlers.

History

This project was launch using BW as Hub because the pVelocity team was not allowed to extract data directly from RCS (WP1).

It was a kind of shadow project.

Roles & Access

There is no direct usage of the BW infoproviders, so no roles nor authorizations.


Dataflow overview

The data flow is very simple because in the main cases, it re-use existaing DSO which are already loaded for other applications.

Then an abap program generates the files in a text format.

The namming rule for the files is a prefix represented the content of the file, then "–" and then a timestamp, which is the dateTime (YYYMMDDHHMMSS)

File nameFile descriptionBW SourceType of data
CDDistribution Channel0DISTR_CHANText
CDSACD x SAC_CDSAMaster Data
COAREAControlling Area0CO_AREAText
COMPCompanies0COMP_CODEMaster data & Text
CURRExchange rateTCURR tableTransactionnal
IECRAIECRA0G_CWWE01Master Data
MARMMaterial Alternative unit of measureODS_MARMMaster Data
MATNRMaterial

C_MATNR

C_MATPLNT

Master data & text

PBOM

Standard production costODS_PCP1Transactionnal
PLANTPlant0PLANTMaster Data & Text
PRODProduced quantityODS_PP01Transactionnal
PROFITCTRProfit Center0PROFIT_CTRMaster Data & Text
RAWPRaw material costsODS_PCP3Transactionnal
RESOURCEResources Unit priceODS_PCP8Transactionnal
RSALResales of the monthODS_PA06Transactionnal
SADivision0DIVISIONText
SHIPSales of the monthODS_PA06Transactionnal
STDCOSTStandard cost by cost ElementsODS_PCP7Transactionnal
TRANSFERTransfer movement between plantsODS_IC01Transactionnal
TVAPTSales documents item category0ITEM_CATEGText
TVFKTSales billing type0BILL_TYPEText
UOMUnit of MesureT006 tableMaster Data
VALSTRValue StreamC_VALSTRMaster Data & Text
VCStandard Variable costsODS_PCP3Transactionnal
ZSECTGlobal Business UnitC_ZSECTMaster Data & text

 

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Text Files:

The text files are using the text of the info object and the target is to provide the description of some master data to pVelocity.

The structure of them is the following one:

 

CD: This file is given the short descriptions of the Distribution Channel

 

Interface File Field

Source table

Field / Data element

Type

Length

Description

DISTR_CHAN

/BI0/TDISTR_CHAN

/BI0/OIDISTR_CHAN

CHAR

2

Distribution Channel

TXTSH

/BI0/TDISTR_CHAN

RSTXTSH

CHAR

20

Short Description

 

COAREA: This file is given the medium descriptions of the Controlling Area

 

Interface File Field

Source table

Field / Data element

Type

Length

Description

CO_AREA

/BI0/TCO_AREA

/BI0/OICO_AREA

CHAR

4

Controlling area

TXTMD

/BI0/TCO_AREA

RSTXTMD

CHAR

40

Medium Description

 

SA: This file is given the short descriptions of the Division

 

Interface File Field

Source table

Field / Data element

Type

Length

Description

DISTR_CHAN

/BI0/TDIVISION

/BI0/OIDIVISION

CHAR

2

Distribution Channel

TXTSH

/BI0/TDIVISION

RSTXTSH

CHAR

20

Short Description

 

 

TVAPT: This file is given the short descriptions of the Sales document item category

Only English language (=EN) is extracted

Interface File Field

Source table

Field / Data element

Type

Length

Description

LANGU/BI0/TITEM_CATEGLANGULANG1Language key

ITEM_CATEG

/BI0/TITEM_CATEG

/BI0/OIITEM_CATEG

CHAR

4

Sales document item category

TXTSH

/BI0/TITEM_CATEG

RSTXTSH

CHAR

20

Short Description


 

TVFKT: This file is given the short descriptions of the Billing type

Only English language (=EN) is extracted

Interface File Field

Source table

Field / Data element

Type

Length

Description

LANGU/BI0/TBILL_TYPELANGULANG1Language key

BILL_TYPE

/BI0/TBILL_TYPE

/BI0/OIBILL_TYPE

CHAR

4

Billing type

TXTSH

/BI0/TBILL_TYPE

RSTXTSH

CHAR

20

Short Description

 

Master Data files:

CDSA: This file will provide the attributes and text of the CDxSA master data. This master data is used as the less level of the organizationnal sales structure.

Selected description is in English (/BIC/TC_CDSA  LANGU = “E”).

If English description is not available, then French description is to be selected (/BIC/TC_CDSA LANGU = “F”).

 

 

Interface File Field

Source table

Field / Data element

Type

Length

Description

DIVISION

/BIC/PC_CDSA

/BI0/OIDIVISION

CHAR

2

Division

C_CDSA

/BIC/PC_CDSA

/BIC/C_CDSA

/BIC/OIC_CDSA

CHAR

2

Distribution Channel

G_CWWE01

/BIC/PC_CDSA

BI0/OIG_CWWE01

CHAR

10

IECRA

C_PFCTR1

/BIC/PC_CDSA

/BIC/C_PFCTR1

/BIC/OIC_PFCTR1

CHAR

20

1 - Global Business Unit

TXTMD

/BIC/TC_CDSA

RSTXTMD

CHAR

40

Medium Description

 


COMP: This file will provide the attributes and text of the Company master data. This master data is used to do the geographical grouping.


 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

COMP_CODE

/BI0/PCOMP_CODE

/BI0/OICOMP_CODE

CHAR

4

Company code

 

TXTMD

/BI0/TCOMP_CODE

RSTXTMD

CHAR

40

Medium description

Description starts wit “ZZZZ” for inactive companies

COMPANY

/BI0/PCOMP_CODE

/BI0/OICOMPANY

CHAR

4

Company

 

COUNTRY

/BI0/PCOMP_CODE

/BI0/OICOUNTRY

CHAR

3

Country key

 

CURRENCY

/BI0/PCOMP_CODE

/BI0/OICURRENCY

CHAR

5

Currency key

 

C_ZONE

/BI0/PCOMP_CODE

/BIC/C_ZONE

/BIC/OIC_ZONE

CHAR

2

Magnitude Geographie/Zone

 

C_STAT_SL

/BIC/C_STAT_SL

/BIC/OIC_STAT_SL

CHAR

4

Status of Trading Partner (Accnt doc)

1=Integrated company

2=Equity Company

3=Other company or Proportionally Integrated

C_FGPTOB

/BI0/PCOMP_CODE

/BIC/C_FGPTOB /BIC/OIC_FGPTOB

CHAR

1

Flag for Obsolete Object

 

CO_AREA

/BI0/PCOMP_CODE

/BI0/OICO_AREA

CHAR

4

Controlling area

 

 


IECRA: This file will provide the attributes and text of the IECRA master data. This master data is used as the second less level of the organizationnal sales structure, as a grouping of CDxSA.

Selected description is in English (/BI0/TG_CWWE01 LANGU = “E”).

If English description is not available, then French description is to be selected (/BI0/TG_CWWE01 LANGU = “F”).


 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

G_CWWE01

/BI0/PG_CWWE01

/BI0/OIG_CWWE01

CHAR

10

IECRA

 Key

TXTSH

/BI0/TG_CWWE01

RSTXTSH

CHAR

20

Sort Description

 

C_PFCTR1

/BI0/PG_CWWE01

/BIC/C_PFCTR1 /BIC/OIC_PFCTR1

CHAR

20

1 - Global Business Unit

For information/reference

 


MARM: This file will provide by material, the different conversion rate to the alternative unit of measure.

Interface File Field

Source table

Field / Data element

Type

Length

Description

 

C_MATNR

ODS_MARM

C_MATNR

CHAR

18

Material number

 

MEINH

ODS_MARM

U_MEINH

CHAR

3

Alternative unit of measure

 

UMREZ

ODS_MARM

K_UMREZ

DEC

9

Numerator for conversion

 

UMRENODS_MARMK_UMRENDEC9Denominator for conversion 


MATNR: This table provides the relationship between C_MATNR and DIVISION. A C_MATNR belongs to only one DIVISION (SA). This table will be used to update/replace the DIVISON in SHIP.txt and RSAL.txt.

Selected description is in English (/BIC/TC_MATNR LANGU = “E”).

If English description is not available, then French description is to be selected (/BIC/TC_MATNR LANGU = “F”).

The size of data can be restricted by selecting only materials belonging to Novecare and Silica CGU by testing of C_PFCTR1 from C_MATPLNT:

  • Novecare : ZSECT00011
  • Silica :  ZSECT00067

Then updated DIVISION will permit updating of IECRA and GBU for the key CDSA in these files.


 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

C_MATNR

/BIC/PC_MATNR

/BIC/C_MATNR

/BIC/OIC_MATNR

CHAR

18

Material code

key

TXTMD

/BIC/TC_MATNR

RSTXTMD

CHAR

40

Medium Description

 

BASE_UOM

/BIC/PC_MATNR

/BI0/OIBASE_UOM

CHAR

3

Base Unit of Measure

 

BASIC_MATL

/BIC/PC_MATNR

/BI0/OIBASIC_MATL

CHAR

14

Basic material (basic constituent of a material)

 

DIVISION

/BIC/PC_MATNR

/BI0/OIDIVISION

CHAR

2

Division (SA)

 

C_PFCTR1

/BIC/PC_MATPLNT

/BIC/C_PFCTR1 /BIC/OIC_PFCTR1

CHAR

20

1 - Global Business Unit

 

G_CWWE01

/BIC/PC_MATPLNT

/BI0/OIG_CWWE01

CHAR

10

IECRA

 

C_VALSTR

/BIC/PC_MATPLNT

/BIC/C_VALSTR /BIC/OIC_VALSTR

CHAR

10

Value Stream

 

C_PROD

/BIC/PC_MATNR

/BIC/C_PROD  /BIC/OIC_PROD

CHAR

18

Commercial Product

 

CO_AREA

/BIC/PC_MATNR

/BI0/OICO_AREA

CHAR

4

Controlling area

 

PROFIT_CTR

/BIC/PC_MATNR

/BI0/OIPROFIT_CTR

CHAR

10

Profit Center

 

UNIT_DIM

/BIC/PC_MATNR

UNIT_DIM

UNIT

3

Profit Center

 

UNIT_OF_WT

/BIC/PC_MATNR

/BI0/OIUNIT_OF_WT

UNIT

3

Weight unit

 

VOLUME

/BIC/PC_MATNR

/BI0/OIVOLUME

QUAN

17

Volume

 

VOLUMEUNIT

/BIC/PC_MATNR

/BI0/OIVOLUMEUNIT

UNIT

3

Volume unit

 

DEL_FLAG

/BIC/PC_MATNR

/BI0/OIDEL_FLAG

CHAR

1

Deletion flag for all material data of a plant

 

C_MATGRP

BIC/PC_MATPLNT

/BIC/C_MATGRP

/BIC/OIC_MATGRP

CHAR

10

Enterprise Material Grouping

 

C_MATSGRP

BIC/PC_MATPLNT

/BIC/C_MATSGRP /BIC/OIC_MATSGRP

CHAR

10

Enterprise Material Sub Grouping

 

 

PLANT: PLANT file provides the complete plant list and its correspondent description, zone, Distribution Channel, Controlling Area and etc.

 The controlling area is not provided in the monthly extract files. So Controlling Area Code will be updated from this file based on plant because each plant has only one Controlling Area Code.

Plant’s short description is a substring of medium description, without the company name an separation character.

For not active plants, short description = complete medium description starting with “ZZZZ”, unchanged.

Examples from table ‘/BI0/TPLANT’:

Remarks: The program P_Velocity is executed only with a list of plant which are included in the Variant => Data loading chapter.  

 

 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

PLANT

/BI0/PPLANT

/BI0/OIPLANT

CHAR

4

Plant

Plant is the key.

TXTMD

/BI0/TPLANT

RSTXTMD

CHAR

40

Medium Description

 

TXTSD








  

CHAR

40

Short Description







Calculated, substring from RSTXTMD, starting after the special separation character (/, 6…)

Ex.: 3865 / Melle -> Melle

TXTSD=TXTMD form “ZZZZ” plants

COUNTRY

/BI0/PPLANT

/BI0/OICOUNTRY

CHAR

3

Country key

 

C_ZONE

/BI0/PPLANT

/BIC/C_ZONE

/BIC/OIC_ZONE

CHAR

2

Magnitude Geography/Zone

 

DISTR_CHAN

/BI0/PPLANT

/BI0/OIDISTR_CHAN

CHAR

2

Distribution Channel

 

FACTCAL_ID

/BI0/PPLANT

/BI0/OIFACTCAL_ID

CHAR

2

Factory Calendar ID

 

LOC_CURRCY

/BI0/PPLANT

/BI0/OILOC_CURRCY

CUKY

5

Local currency

 

PURCH_ORG

/BI0/PPLANT

/BI0/OIPURCH_ORG

CHAR

4

RCS / Purchase Organisation

 

REGION

/BI0/PPLANT

/BI0/OIREGION

CHAR

5

Region (State, Province, County)

 

SALESORG

/BI0/PPLANT

/BI0/OISALESORG

CHAR

4

Sales Organization

 

C_SITE

/BI0/PPLANT

/BIC/C_SITE

/BIC/OIC_SITE

CHAR

5

Geography / Geographic site

 

COMP_CODE

/BI0/PPLANT

/BI0/OICOMP_CODE

CHAR

4

Company code

 

C_OPE_ENT

/BI0/PPLANT

/BIC/C_OPE_ENT

/BIC/OIC_OPE_ENT

CHAR

2

Operating Enterprise

 

CO_AREA

/BI0/PPLANT

/BI0/OICO_AREA

CHAR

4

Controlling area

Each plant has only one Controlling Area code.

C_FGPTOB

/BI0/PPLANT

/BIC/C_FGPTOB

/BIC/OIC_FGPTOB

CHAR

1

Flag for Obsolete Object

 

C_CPCRCY

/BI0/PPLANT

/BIC/C_CPCRCY

/BIC/OIC_CPCRCY

CHAR

5

Currency of the Company

 

 

PROFITCTR: This file provides GBU and values stream info based on a concatenated key Controlling Area + Profit Centre. It will be used to update GBU value.

 Profit Center is associated to plant + material.

 Selected description is in English (/BI0/TPROFIT_CTR LANGU = “E”).

 If English description is not available, then French description is to be selected (/BI0/TPROFIT_CTR LANGU = “F”).

 

 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

CO_AREA

/BI0/PPROFIT_CTR

/BI0/OICO_AREA

CHAR

4

Controlling area

 Key

PROFIT_CTR

/BI0/PPROFIT_CTR

/BI0/OIPROFIT_CTR

CHAR

10

Profit Center

 Key

TXTSH

/BI0/TPROFIT_CTR

RSTXTSH

CHAR

20

Short description

 

TXTMD

/BI0/TPROFIT_CTR

RSTXTMD

CHAR

40

Medium description

 

DATETO

/BI0/TPROFIT_CTR

RSDATETO

DATS

8

Valid-to date

 

C_VALSTR

/BI0/PPROFIT_CTR

/BIC/C_VALSTR

/BIC/OIC_VALSTR

CHAR

10

Value Stream

 

C_ZSECT

/BI0/PPROFIT_CTR

/BIC/C_ZSECT

/BIC/OIC_ZSECT

CHAR

20

Global Business Unit

 

C_PFCTR1

/BI0/PPROFIT_CTR

/BIC/C_PFCTR1

/BIC/OIC_PFCTR1

CHAR

20

1 - Global Business Unit

For information / reference

G_CWWE01

/BI0/PPROFIT_CTR

/BI0/OIG_CWWE01

CHAR

10

IECRA

 

C_TVALSTR

/BI0/PPROFIT_CTR

/BIC/C_TVALSTR

/BIC/OIC_TVALSTR

CHAR

4

Technology Value Stream

 

PLANT

/BI0/PPROFIT_CTR

/BI0/OIPLANT

CHAR

4

Plant

 

COMP_CODE

/BI0/PPROFIT_CTR

/BI0/OICOMP_CODE

CHAR

4

Company code

 

C_OPE_ENT

/BI0/PPROFIT_CTR

/BIC/C_OPE_ENT

/BIC/OIC_OPE_ENT

CHAR

20

Operating Enterprise

 

 

UOM:



 

table

field

description

example1

example2

T006

MANDT

Client

110

110

T006

MSEHI

Int. meas. unit

LB

TOZ

T006

 

 

 

 

T006

KZEX3

3-char.ext.unit

X

X

T006

KZEX6

6-char.ext.unit

X

X

T006

ANDEC

Decimal.pl.rnd.

3

0

T006

KZKEH

Commercial unit

X

X

T006

KZWOB

Value bsd cmmt

 

 

T006

KZ1EH

(1) unit

 

 

T006

KZ2EH

(2) unit

 

 

T006

DIMID

Dimension

MASS

MASS

T006

ZAEHL

Numerator

24445

311035

T006

NENNR

Denominator

53892

10

T006

EXP10

Exponent

0

6-

T006

ADDKO

Additive const.

0

0

T006

EXPON

fl. pt. exp.

0

0

T006

DECAN

Decimal places

0

0

T006

ISOCODE

ISO code

LBR

APZ

T006

PRIMARY

Primary code

X

X

T006

TEMP UNIT

Temperature un.

 

 

T006

FAMUNIT

Un.of meas.fam.

 

 

T006

PRESS UNIT

Pressure Unit

 

 

T006

MSEH3

Commercial

LB

TOZ

T006

MSEH6

Technical

lb

TOZ

T006

MSEHT

Meas. unit text

US pound

Troy ounce

T006

MSEHL

Unit text

US pound

Troy ounce

 

 

table

field

description

example

T006D

MANDT

Client

110

T006D

DIMID

Dimension

MASS

T006D

LENG

Length

0

T006D

MASS

Mass

1

T006D

TIMEX

Time

0

T006D

ECURR

elec. current

0

T006D

TEMP

Temperature

0

T006D

MOLQU

Mole quantity

0

T006D

LIGHT

Luminous intensity

0

T006D

MSSIE

SI unit

KG

T006D

TEMP DEP

Temperature-Depend.

 

T006D

PRESS DEP

Pressure-Dependent

 

T006D

TXDIM

Dimension text

Mass

 


Conceptual information :

To use those tables inform the dimension and the unit of measure that you need to convert in T006:

Example1 : mass / LB

In this example, 1 lb = 24445/53893 = 0,453 kg

Example2= mass/TOZ

In this example, 1 toz = 311035/10000000 = 0,031 kg

The base of unit of measure defined in the System International ( kg ) is obtained in the table T006D.



VALSTR: This file will provide the aatributes and text of the Value Stream.

 Selected description is in English (/BI0/TPROFIT_CTR LANGU = “E”).

 If English description is not available, then French description is to be selected (/BI0/TPROFIT_CTR LANGU = “F”).


 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

C_VALSTR

/BIC/PC_VALSTR

/BIC/OIC_VALSTR

CHAR

10

Value Stream

 Key

TXTSH

/BIC/TC_VALSTR

RSTXTSH

CHAR

20

Short Description

 

TXTMD

/BIC/TC_VALSTR

RSTXTMD

CHAR

40

Medium Description

 

C_TVALSTR

/BIC/PC_VALSTR

/BIC/C_TVALSTR

/BIC/OIC_TVALSTR

CHAR

4

Technology Value Stream

 

PLANT

/BIC/PC_VALSTR

/BI0/OIPLANT

CHAR

4

Plant

 

C_PFCTR1

/BIC/PC_VALSTR

/BIC/OIC_PFCTR1

CHAR

20

1 - Global Business Unit

 

CURRENCY

/BIC/PC_VALSTR

/BI0/OICURRENCY

CUKY

5

Currency key

 

C_TYPEVS

/BIC/PC_VALSTR

/BIC/C_TYPEVS

/BIC/OIC_TYPEVS

CHAR

20

Value Stream Type

 

C_GEOSITE

/BIC/PC_VALSTR

/BIC/C_GEOSITE

/BIC/OIC_GEOSITE

CHAR

20

Value Stream Geographical site

 

 

ZSECT: This file will provide the description and attributes of the Global Business Unit

 Selected description is in English (/BIC/TC_ZSECT LANGU = “E”).

 If English description is not available, then French description is to be selected (/BIC/TC_ZSECT LANGU = “F”).


 

Interface File Field

Source table

Field / Data element

Type

Length

Description

Comment

C_ZSECT

/BIC/PC_ZSECT

/BIC/C_ZSECT

/BIC/OIC_ZSECT

CHAR

20

Global Business Unit

 

TXTMD

/BIC/TC_ZSECT

RSTXTMD

CHAR

40

Medium description

 

C_FGPTOB

/BIC/PC_ZSECT

/BIC/C_FGPTOB

/BIC/OIC_FGPTOB

CHAR

1

Flag for Obsolete Object

 

 

Transactionnal data:


Dependencies with other applications

Of course this application is very dependant of the others, because it uses a lot of DSO which already loaded by other applications.

Master data and texts are shared with all the other application.

Here are the dependance of the other applications:

 

Data loadings

Info providers and objects loaded

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

 

Key FigureEstimation
~ Average Process Chain Runtime 
~ Average nb of rows loaded per load 
~ Total nb of rows loaded (if full) 
~ Average Runtime for 10k lines 

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

No direct reporting on this application, just a hub to generate flat files

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016