Data Transformations Overview
The following section will detail some reasoning behind different transformations in the PR connector and what should be considered when implementing. The transformations should be run in the order of the prefix and in the order that follows.
Note
For job 0.0 it should only be run once on installation and does not need to be included in the regular schedule.
Local Job: 1.0 - Purchase-to-Pay - Extractions
Please see Appendix 6.2 - Table Requirements for the list of table requirements for the extractions.
Local Job: 2.0 - Purchase-to-Pay - Transformations
Create Table: Currency Conversion
This transformation is used to transform the TCURR and TCURF tables into an appropriate format for currency conversion throughout the other transformations.
Create Table: _CEL_P2P_ACTIVITIES [Activity Table]
This transformation is used to create a view from the PO activities table. The most essential activities in this eventlog for this data model are the Create Purchase Order Item and Record Goods Receipt, as this allows us to determine the POs that have been fulfilled.
View: P2P_EKKO
P2P_EKKO transformation contains all the data related to the Purchase Document Header. It also contains information like the associated Purchasing Organization (EKORG), Company Codes (BUKRS), Purchasing Document Type (BSART), Record Creation Date (AEDAT), and Purchasing Document Date (BEDAT) of a Purchasing Document, among other data fields.
View: P2P_EKPO
The P2P_EKPO transformation contains all the data related to Purchase Document Items.
It also contains information like the associated Material Group (MATKL), Plant (WERKS), and Net Order Value (NETWR) of a PO item, among other data fields.
View: P2P_LFA1
This transformation brings the generic LFA1 (Vendor Master) from the local job, excluding all the vendors/suppliers with no POs on the EKKO table and casting many fields with a date syntax.