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

Compare with Current View Page History

« Previous Version 6 Next »

  

General presentation

This page provides all the technical and detailed documentation concerning the ITC (Invoice to Cash FIAR) application in BW, including :

  • General overview of the dataflow
  • Query, Workbook, Webtemplate and broadcasts documentation
  • Maintenance operations : necessary manual updates of master data.

Objective of this application is to provide an unique reporting tool for Credit Management team.

Systems involved

  • Rhodia ERP WP1

  • Solvay ERP PF1 (020)

  • CICC ERP PI1

  • Acetow ERP RHO

  • PRS ERP PF1 (050)

PRS Source system

We load some master data from PRS system (PF1_050).
With this some source system, we can be sure to have an unique code for companies, customers and vendors.

In RCS and Acetow, the link between ERP and PRS is managed in tables ZZR_T001_MAP (company), KNA1 (customer) and LFA1 (vendor).

For Solvay and CICC, the PRS code is the same than ERP code.

PRS master data are stored in dedicated info objects: C_COMPPRS, C_CUSTPRS and C_VENDPRS.

We also have dedicated info objects from the ERP with the ERP system and code and the PRS attributes: C_COMPCDE, C_CUSTID and C_VENDID.
At the beginning  we used C_COMPPRS, C_CUSTPRS and C_VENDPRS in the info providers in order to use their attributes but due to poor data quality we had too oftenly the case of missing link in the ERP between ERP and PRS codes. That's why we decided to replicate PRS attributes in C_COMPCDE, C_CUSTID and C_VENDID info objects.

Dataflow in BW

Business rules

+Net due date management:

The net due date is managed at the document item level and is calculated in the ERP. A new net due date managed manually has been set in each system.
It's available in ZZF_BSEG table.

For each system we created a new data source based on this table and a dedicated DSO (DPFIWC01 to 04).
In BW, there is a direct loading between Net due date DSO and Business layer DSO and also a look-up between Propagation and Business layers to read DPFIWC DSO.

+Reclassification of Sub-Activity C_SUBACT2:

In the ERP, when a profit center or a business area is set, it's not possible to modify it later.
In order to resolve that issue, mecanisms have been created in the ERP.

In WP1

Documents can be modified in ZWFAT205 table (transaction ZWFAT205).
In the example below, document has been modified with a different profit center:

This table is loaded in DSO_FI11 in BW and data are updated in Business layer DSO.

In PF1 and PI1

In PI1 system, the mecanism is different and is not managed document by document, like in WP1.
It's done in PI1 (for PI1 and PF1) through data source ZZFCM_BU_EXCEPTIONS_NEW.

This table is loaded in DBFIWC01 DSO in BW.

Between Propagation and Business layers, we read this DSO to determine the new business area.

For example, document for company code 0005 and business area 3240, the new business area will be 8500.

+Rhodia legacy rules:

Initial loading was done from existing DSO ODSFIAP1 and not from WP1 system due to archived document not loadable anymore.

A split of data is done between propagation and business DSO (DPFIAP01 and DBFIAP01), in the start routine inside program z_start__dpfiap01__dbfiap01.

The split is also done in WP1 system, in ZWFAT123 table. This table is filled in WP1 when the data source 0FI_AP_4 is launched. The data are retrieved in ODS_FIWC.

+Solvay legacy rules:

A split of data is done between propagation and business DSO (DPFIAP02 and DBFIAP02) but the mecanism and the logic is much more simple.

We split data using DPFIGL02 DSO (FIGL data) for document with reference procedure RMRP (Invoice receipt) with detail by material, plant, purchase order number and item.

We calculate the item's quote part in FIGL and apply this quote part on amount from FIAP document. For the last splitted item, amount is the total amount minus the sum of other splitted lines.

For CICC, there isn't specific rule.

+Acetow legacy rules:

The same split that Solvay legacy is done.

FIGL fata flow

+Common rules:

In business layer, we filter to keep posting on account types S (G/L Account) and M (Materials)

+Rhodia legacy rules:

We continue to use ODSFIGL3. This DSO is very huge so it would have been to long to load other DSO and it would be to heavy in WBP system.

A split of data is done between propagation and business DSO (ODSFIGL1 and ODSFIGL3), in the start routine of the transformation.

The split is also done in WP1 system, in ZWFAT143 table. This table is filled in WP1 when the data source 0FI_GL_4 is launched. The data are retrieved in ODSFIGL2.

+Data initialization:

For Solvay and CICC systems, initialization was done using PQ1 system. We made this choice for performance reasons.

FIGL-AR fata flow

No specific rules.

FIGL-AP fata flow

No specific rules.

FIGL-IM fata flow

  • New master data C_MATPNT3

    • Technical object

    • Based on MBEW table

    • Attributes Valuation class, company code, GL account

    • To “correct” accounting from SAP systems : to have same BFC GBU account allocation as in SAP Logistic (could be different from allocation in Accounting)

  • Need to split FIGL-IM in two silos

    • Silo S with accounting on G/L account => based on postings

    • Silo M with accounting on Material => based on C_MATPNT3

      • 2014 and after only

  • Snapshot at 31.12.2013

    • Impossible to load full history

+Rhodia legacy rules:

Snapshot was made at 31.12.2013 from CUB_IC001

+Solvay legacy rules:

Snapshot was made at 31.12.2013 from PQ1.

+Acetow legacy rules:

Snapshot was made at 31.12.2013 with flat files from RHO system.

We tried to use standard data sources 2LIS_03_BX, BF and UM to make an initialization at 31.12.2013.
Initialization with 2LIS_03_BX worked but we failed with the other data sources. 

Reporting

Workbooks

All the reporting is available throught workbooks in the role "WCAP - Working Capital Solvay Group" ZR_RCS_CA_M41

There are 2 sub-folders, 1 for GBU usage and 1 for Accounting and BFC usage.
All workbooks are based on the same info providers. 

Currency conversion

We use same conversion rate as Working Capital.

Authorization objects

There isn't authorization objects. It was requested by the project team

Data loading

+During closing period (last day of the month and 4 fist working days):

  • WP1 data are loaded 7 times a day: 6am, 10am, 12am, 2pm, 4pm, 6pm and 10pm (french time)
  • PF1, PI1 and RHO systems are loaded 3 times a day: 6am, 12am and 6pm (french time)

+Outside closing period:

  • All systems are loaded 3 times a day: 6am, 12am and 6pm (french time)
  • No labels