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 Leader is now Nathalie Manirakiza in the IS-RtR team

The Tool Leader is in the Novecare GBU.

Old link to google doc about Pvelocity :

https://drive.google.com/drive/folders/1OUYHvBX3YNYTALY1QXgslrtjfZBEyX40

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)

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

Transactionnal data:

CURR: Exchange rate

Select all occurrences in table TCURR with KURST = M and create a file

To use the exchange rate proceed : inform the FCURR and TCURR and valid date from .

If the valid date is not informed in the file, use the exchange rate of the last date less than the date informed.

PBOM: Standard production cost

The file is generated from the ODS_PCP1 DSO. In addition to the variant, there is no specific selection.

This file is used today in P_Velocity interface in order to inform the standard cost of the product  produced in the month. (ZBW_KEKO_CKIS)

 For byproducts/co-products the OI_MENGE  is negative

PROD: Produced quantity

The file is generated from the ODS_PP01 DSO. In addition to the variant, there is no specific selection.

RAWP: Raw material price

The file is generated from the ODS_PCP3 DSO. In addition to the variant, there is no specific selection.

RESOURCE: Resources Unit price

The file is generated from the ODS_PCP8 DSO. In addition to the variant, there is no specific selection.

Obtain the resource identification OBJID in table CRHD selecting the occurrences by :

• • • OBJTY = A
    • VERWE = 0008 or 0009
    • WERKS = informed ( all plants of Z028 CA )

With the OBJID read table CRCO in order to obtain the cost center / activity :

Select every occurrence of OBJID with CA/cost center / activity   not equal spaces.

For each occurrence selected of CRCO , read table CSSL with fields KOKRS , KOSTL, LSTAR and  GJAHR = year informed ( reference date ) , in order to obtain the OBJNR.

Finally, with OBJNR , GJAHR and VERSN = 0 , obtain the unit price in table COST.  

The prices and unit price are informed by month with the Controlling area currency ( in Z028 = USD ).

RSAL: Resales of the month

The file is generated from the ODS_PA06 DSO.

This file is used today in the P_Velocity interface in order to inform the resales in the month.

  This file was created for Mustang version , selection :

  IF VAL_CLASS=Z130 or  if ITEM_CATEG=(TAS or TASG or TAB ) => file RSAL otherwise file     SHIP.

SHIP: Sales of the month

The file is generated from the ODS_PA06 DSO.

This file will contain only the sales without the resales since they will be in the new RSAL file.

Conceptual information for P-Velocity : Identification of freight costs in the late differentiation flow : select PSTYV =TAPS , and qty = 0.   ( not select qty # zero ).

  PLANT – is the distribution plant. 

  Plant Code from the PRCTR (1 st four characters) – is the plant where the transaction will be grouped under for profit analysis and the plant code showed in the plant-list in the pV. This is also the plant code to link with the PBOM

Here the list  of sales document item category  table TVAPT ( 341 items ) :

Here the list of sales billing type table (92 items ):

STDCOST: Standard cost by cost Elements

The file is generated from the ODS_PCP7 DSO.

This file is used to provide the split of COGS in raw material cost, variable utilities , fix utilities , labor , maintenance , toll manufacturing, overhead and depreciation.

The cost elements of the material represents the split of  the cost of raw materials , intermediates products , utilities and fixed costs and depreciation consumed until this production phase.  

In order to obtain the cogs split by cost element , the link with the table SHIP and RSAL need to be done by : cocode / shipping plant / material code.

Do not forget to convert the standard cost estimate calculated by production lot size to the standard cost by qty sold.

For billing type IV the cost is informed in the SHIP file only ( the inter company cost is composed by standard cost + management fees + freight costs which are informed in the pricing procedure ).

For item category TAS the cost is informed in the RSAL file only ( the origin is the price purchase ).

Use always the fields KST001 , 3,  5 , 7 , 9 , 11 , 13 , 15 , 17.

Mapping of the KSTxxx item to the P&L rows

TRANSFER: Transfer movement between plants

The file is generated from the ODS_PCP8 DSO is used to analyse the flow of products between plants.

The extraction will take in to account the MM movements detailed in the next steps and theirs reverse movements :

• INTRACO:
  • for the month informed ( use for select the documents in MKBF) , select the transfer movements in table MSEG : 301, 302, 303, 351, 641, 642, 647, 648, 671, 672, 677, 678, 833, 861, 862 with XAUTO = space
  INTERCO:
  • For the month informed ( use for select the documents in MKBF) , select the next movements in table MSEG , considering all the occurrences with the same material document code : 645, 646, 675, 676  

( for every one there are 2 occurrences with the same material document number : 645 + 101 , 646 + 102 , 675 + 161 , 676 + 162 , 643 +101 , 673+ 161 , 644 + 674, 102 + 162  )

Save the table with the movements :

For Intraco :

• when the debit/credit = H : werks is the sending plant and umwrk is the receiving plant
• when the debit/credit = S : werks is the receiving plant and umwrk is the sending plant

For Interco :

• Work with the 2 occurrences with the same material document number :
  • Mov 645,  675 , 101, 161 and their reverses 646, 676, 102, 162 :
  • when the debit/credit = H : werks is the sending plant  
  • when the debit/credit = S : werks is the receiving plant 
  Work with the 2 occurrences with the same purchase order / item  number :
  • Mov 643,  101 , 673, 161 and their reverses 644, 674, 102, 162 :
  • when the debit/credit = H : werks is the sending plant  
  • when the debit/credit = S : werks is the receiving plant  

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:

• PROD file from ODS_PP01 used in the Production reporting application
• PBOM file from ODS_PCP1 used in the CO-PC (Cost production) reporting
• RAWP  file from ODS_PCP3 used in the CO-PC (Cost production) reporting
• SHIP and RSAL files from ODS_PA06 used in the RCS KPIs dashboard
• STDCOST file from ODS_PCP7 used in the integrated margin solution
• RESSOURCE file from ODS_PCP8 used in the integrated margin solution
• TRANSFER file from ODS_IC01 used in the stock and working Capital applications

MMSTA: Material Status

The file is generated from the C_MATPLNT will display the status of the Material with respective to plant.

.1. Leading zeros are removed only from the “MAT PLANT” column

Structure of the file:

Data loadings

Info providers and objects loaded

Info providers which are loaded are shared with other applications.

Once they are loaded, the big abap report Z_PVELOCITY is launched 3 times with the 3 different variant to generate 3 set of files for the 3 different periods.

Files generated

The files which are generated are for the current month, the previous month and even month -2 in order to have all the cost corrections.

The specific folder is visible in AL11 transaction and is /exploit/BW/CIS

There is 3 processes which will launch the same abap report (Z_PVELOCITY) with 3 different variants:

• Z_NOVE_PER
• Z_NOVE_PER-1
• Z_NOVE_PER-2

Loading frequency

There is a dedicated process chain to load specific data or to update the target where we need to genrerate the files and it generated the file launching a big abap report.

The process chain is launched once a month, the second working day at 07:00 CET.

Reporting

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

Planned Evolution

Nothing is planned as evolution

Maintenance

This application is not requested a lot of maintenance, it is stable.

Once a year, we have to delete the historical files because they are consuming space in the folder.