The new wiki link for this data flow is here:
Technical Documentation - Procurement - SPRINT report
Please update the new doc there and no longer here.
Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO
Name of project or main leader for the application + reporting coodinator
SPRINT stands for Solvay Purchasing Reporting INTelligence
SPRINT is a project launched early 2014, with the main purpose to build and deliver a reporting application to cover both the Purchasing and the PtP reporting needs.
It is hosted in WBP server, collecting information from PF1-050 (PRS), PF1-020 (Solvay legacy ERP), WP1-400 (Rhodia legacy ERP) and RHO-020 (Acetow ERP).
SPRINT application is available for the two “family” of users
each one having a dedicated Menu in WBP with the respective queries.
The Sprint reporting is also including queries based on following projects :
Tool Leader + IT leader of the application:
Reporting Coordinator : Duarte Costa (Lisbon)
Purchasing & Supply Chain Solutions Coordinator : Karin WEIGEL-JUNG (Lyon)
Purchasing Data and P-t-P Interface Manager : Sylvie Severini (Bruxelles)
Purchasing and Supply Chain Excellence / Quality Leader : Cécilia Allain (Lyon)
Contact on ECC side for MM => Henri OLLIVIER
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
SPRINT is a project launched early 2014. The roadmap of the project has been sliding in time and at the current date (January 2016) the Purchasing solution has been live for 9 months (first deployment made in March 2015 for APAC users, second deployment made in April 2015 for NAM users, third deployment between May and June 2015 for EMEA users and forth deployment in June 2015 for LAM users); the SBS PtP solution is partially deployed since June 2015.
One of the major objectives of the project is to have and maintain a reporting solution that is kept simple, meaning, that unlike what happened with GSV (where more than 80 queries exist due to multiple copies made for each user request), the aim for SPRINT is to keep the number of queries limited.
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Menu Code | Role application | Role Description | Explanation | Link queries |
|---|---|---|---|---|
| ZR_RCS_CA_M04 | ZR_RCS_SPRINT2_A01 | SPRINT - Purchasing | Role menu ZR_RCS_CA_M04 uses application role ZR_RCS_SPRINT2_A01 linked to IA_PUR_SPRINT* Authorization Object ZBI_SPRINT2 / Authorization on zone, GBU, Plant, Company Code. | |
| ZR_RCS_CA_M31 | ZR_RCS_SPRINT2_A01 | SPRINT - SBS - PTP | Role menu ZR_RCS_CA_M31 uses application role ZR_RCS_SPRINT2_A01 linked to IA_PUR_SPRINT* Authorization Object ZBI_SPRINT2 / Authorization on zone, GBU, Plant, Company Code. | Link |
| ZR_RCS_CA_M54 | ZBI_RCS_SC_A01 | SPRINT - Supplier Credit | Role menu ZR_RCS_CA_M54 uses application role ZBI_RCS_SC_A01 linked to IA_PUR_SC_* Authorization Object ZBI_SPRNT_SC / Authorization only on Company Code. | |
| ZR_RCS_CA_M59 | ZBI_RCS_VBF_A01 | Sprint - Value Based Fee | Role menu ZR_RCS_CA_M59 uses application role ZBI_RCS_VBF_A01, linked to IA_PUR_VBF_* | |
| ZR_RCS_CA_M62 | ZR_RCS_SPRINT2_A01 | Sprint - Value Creation | Role menu ZR_RCS_CA_M62 uses application role ZR_RCS_SPRINT2_A01, linked to IA_PUR_SPRINT_VC*. | |
| ZR_RCS_CA_M042 | ZR_RCS_SPRINT2_A01 | SPRINT - Purchasing Data | Role menu ZR_RCS_CA_M042 uses application role ZR_RCS_SPRINT2_A01 linked to IA_PUR_SPRINT* (only in wbd for the moment) | |
| ? | ? | ? | ? linked to IA_PUR_SPRINT_VWF* |
NB : The role menu ZR_RCS_ALL_MENU "Role composite with all role Menu and perimeters" gives access to all role menu. When asking for a new role menu, do not forget it is added to that one.
NB: ZR_RCS_SPRINT_A01 & ZR_RCS_SPRINT_A02 are obsolete
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Zone (C_PZONE) | ZR_*_CA_P11 Authorizations exist on this object, but all users have access to all (role ZR_TOUT2_CA_P11), this authorization on Zone is abandoned. NB: ZR_TOUT_CA_P11 is obsolete |
GBU (C_SUBACT2__CPFCTR1_2) | ZR_*_CA_P05 |
| Plant (C_PLANT) | ZR_*_CA_P02 ZR_7866_CA_P02 => Plant 7866 - Chalampé (ex 7027) - (Cie ZFR9) ZR_TOUT_CA_P02 => All Plants "Solvay" |
| Company Code (C_COMPCDE) | ZR_*_CA_P01 ZR_ZFR9_CA_P01 => BUTACHIMIE - ( ZFR9) (ex 0560) ZR_TOUT_CA_P01 => All Companies "Solvay" |
See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I
Technical dataflow : SPRINT - Technical Data Flow.pptx https://drive.google.com/file/d/1RRcSkxXHQa0o-lufIyriZW0zVpBSF21V/view
See also SPRINT Dataflow https://drive.google.com/file/d/1HAOEcKFoPxUN-GOEpGOh3fkAdj7Cx-_eIg4I5pMvZNY/view
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
https://drive.google.com/drive/folders/1xSTPzNUz5Ai8qLCxI6Baqyps95YC5T-4
Exemple of dataflow overview :
Directory 01. Data Mapping https://drive.google.com/drive/folders/1jzgxsU7G2I3iM5gnvKcKbNeyZwIJI-iP
https://drive.google.com/file/d/11D3zE-u8gb8O__TMAFU_eQrz47tNenNz9lDM3TtXMmI/view
https://drive.google.com/file/d/1-PBxI44Ok6r1U0vdsWKzzWwS5ienVVtsZD8B9GRGA9A/view
This rule concerns only Solvay vendors (from PF1) P*, which are employees not existing in PRS.
These vendors are partly created in Solvay PF1 and it is then not possible to set Class = 'X' in Solvay PF1.
For those vendors, the class has to be set to 'X' in BW.
The intervall of vendor is managed in Global Filter (C_GLBFILT). Currently P000000000 to PZZZZZZZZZ
All realigned material group are existing on Solvay, descriptions are then filled from PF1 only. Only english description are required.
Terms of Payment on SAP side are managed into 2 tables. TVZBT for sales (customers), T052U for purchasing (vendor).
Payment terms can be common. On BW there is only one object for Payment Terms. T052U has to be loaded first. The description of common terms will be then TVZBT's one.
Note that keys are differents, no matters, the last description is kept.
Payment terms can be find at different level
Different objects are used Sprint vs DPO, but values are the same.
(xxxx) means it comes from ECC table xxxx, othervise it is in the document itself
| SPRINT | DPO | |
|---|---|---|
| Vendor / Company Code view (LFB1) | C_VENDCOM__0PMNTTRMS | C_VENDCOM__C_PMNTTRM |
| Vendor / Purchasing view 1 (LFM1) | C_VENDPRG__C_PMNTTRM | C_VENDPRG__C_PMNTTRM |
| Vendor / Purchasing view 2 (LFM2) | C_PO_ITM__C_PMNTRM2 | C_VENPRG2__C_PMNTTRM |
| In Purchase Order (PO) | C_PO_ITM__C_PMNTTRM | C_PO_ITM__C_PMNTTRM |
| In Accounting Document (DOCT) | C_PMNTTRM | C_PMNTTRM |
SPRINT - Data Mapping - Read Soft https://drive.google.com/file/d/1HHvjZIL3L8BJAkKQe6fx5o_RqrAuNA8tMS2Y-c2Sfk8/view
There are some differences between rhodia and solavy data flow.
For exemple, in function module of extractor ZFM_BW_COCKPIT_THDR, in WP1 (Rhodia), the date of rejection (ZWDATE_REJECT) is recovered in table /cockpit/thdr.
It's not the case in PF1 (Sokvay), here ZWDATE_REJECT get the date in /COCKPIT/THDR-CH_TIMESTAMP when STATUS = 13 (this rule will may be applied in Rhodia in the future).
In bw, in transformation between dso DP_RDSF and DB_RDSF, some fields like accounting doc number, posting date, controlling area... come from FIAP.
For Rhodia side, we used DSO DBFIAP01 to take data. For Solvay we used two dso: DPFIAP02 and DB_FIAP2.
Infopackages for datasources, are in delta mode. THe delata is based on change date (the change date is also implemented when it's a creation of cockpit document).
This rule concerns only RCS & Solvay FIAP data (transformation between DBFIAP01/2 et DB_FIAP1/2). Acetow is not concerned.
The Settlement rules (table COBRB) are loaded every days by another application (RCS : Dso DSRCOBRB / Solvay : Dso DSSCOBRB).
Reuse of rule between ODS_PMEN to DBFICS02.
Case WBS element is already determined for the FIAP record => keep it, no further determination.
Case WBS element is empty and CO order is filled => read settlement rules
First check is a previous determination has been done (lookup on Dso)
=> If yes, take the WBS element stored
=> if no, read settlement rules
The check is done to avoid dupplicates as the WBS element is part of the key, and settlment rules can be changed even for the past.
NB: the check can be skip for performance purpose essentielly (case of an initialization for example) => Flag in Global Filter SPRINT/DB_FIAP1 or DB_FIAP2/ put Y in low value and Y. Do not forget to put it back to N afterwards.
NB : In case of a reload of the DSO, the first WBS Element determination is lost, as the DSO is previously is empted. The WBS Element will be the one correcponding to the current settlement rules
To see Settlement rules on ECC side :
-> use transaction KO03 with Co Order 000010528547 (for WP1)
-> button 'Settlement rule'
How COBRB table is read
=> Read only line Category WBS
=> Use firstly Settlement Type 'PER', then, if not found or out of validity, use 'GES'
=> Use firstly the higher % Settlement percentage rate
Since 2020, with projects S3 and co$ta, the Segmentation rule was changed.
Until then it was based on Vendor Segmentation: Domain and Segment come from 1. domain/segment of the Vendor if assigned; if not, 2. domain/segment of the Creditor if assigned; if not, 3. domain/segment of the PO Material Group; Exceptions: if the domain of the Creditor is "LO - Logistic (8)" and domain of the Vendor is different, take domain/segment of the Creditor.
With S3 and co$ta it was changed to focus on Material Group Segmentation.
There are two kind of rules, simplified and complete.
The simplified rules, based on the rules below, determine only the Segment and the Domain.
The simplified rules are determined in the following transformations:
The complete rules, based on the rules below, determine the Segment, the Domain, the Cost Sub-Package, the Cost Package and the Cost Macro Package.
The complete rules are determined in the following transformations:
Loadings
There is a daily loading for the following transformations that works in delta mode:
The segmentation is redetermined every Sunday. There is a weekly loading for the following transformations that works in full mode with two abap filters in the data transfer process that determine the source system and the period that is current year and previous three years (see global filter C_GLBFILT / SPRINT / SEGMENTAT):
C_MAT_GRP (Material Group) through WEBDYNPRO ZWD_FILE_C_MAT_GRP_SEGT.
The webdynpro ZWD_FILE_C_MAT_GRP_SEGT loads into C_MAT_GRP the following master data fields:
The source system of the above webdynpro is an excel file that is moved into the folder “/usr/sap/tmp/C_MAT_GRP_SEG.csv” of the transaction AL11 and from there into C_MAT_GRP.
There are two daily loadings, from Monday to Friday:
Organization (P), C_ORG attribute of 2 Function, C_FUNCT_2.
C_ORG is a non-navigation attribute of C_FUNCT_2.
and such Master Data is used in order to determine C_ORG into the two DSOs DB_FIAP1 and DB_FIAP2.
That Master Data is loaded through PC_FILE Data Source on a Business request and triggered by the Process Chain PC_SPEND_S3_01.
The description of C_ORG comes from two different Data Sources, from WP1_400 for the GBU description and from PC_FILE for the Organization (P).
The schedule of the loading from WP1_400 is 7 times per day excluded the weekend and it is triggered by the Process Chain FREQUENTLY_LOAD_MD.
The schedule of the loading from the PC_FILE is on a Business request and triggered by the Process Chain PC_SPEND_S3_01.
C_ORG is used into the following objects.
Into the two following Transformations
it is mapped in the Rule Routine
based on the following Business Rules:
If C_SUBACT2__CPFCTR1_2 <> “CB” - -> C_ORG = C_SUBACT2__CPFCTR1_2
Else
If C_SUBACT2__CPFCTR1_2 = “CB” And C_CALRCC__C_FUNCT_2 Is Empty - -> C_ORG = C_SUBACT2__CPFCTR1_2
Else
If C_SUBACT2__CPFCTR1_2 = “CB” And C_CALRCC__C_FUNCT_2 Is Not Empty --> C_ORG = C_FUNCT_2__C_ORG
Into the two following Transformations
it is mapped one by one.
In the Multiprovider MV_SPD01 it is identified with the two cubes CR_PUAP1 and CR_PUAP2.
The loading of the Master Data of C_FCUNCT_2 and of the Description of C_ORG, based on a Business request, is triggered by the Process Chain PC_SPEND_S3_01.
Specific procedure for the historical re-loading of the Organization (P).
After having run the Process Chain PC_SPEND_S3_01 it needs to re-determine C_ORG into SPRINT flow, meaning into DB_FIAP1 à CR_PUAP1 and into DB_FIAP2 à CR_PUAP2.
The complete procedure to re-load all is the following.
When receiving the Freshdesk ticket from the Business, you have to save the two files (one for C_FUNCT_2 attributes and one for C_ORG descriptions) in your local computer.
The two files have to have the following layout:
C_FUNCT_2 attributes
C_ORG text
Then into the two following InfoPackages
catch the two files saved during the previous step.
Then, run manually the Process Chain PC_SPEND_S3_01.
Once the Process Chain is finished, perform the following manual steps:
For SPRINT Rhodia
For SPRINT Solvay
Lead Time https://drive.google.com/file/d/1ZfGsiEaeqtCqopI306Om2MwlLsp13SN6/view
In end routine of transformations for DSOs "FIAP for SPRINT" Rhodia and Solvay (DB_FIAP1 & DB_FIAP2) from splitted DSOs, there is abap code to calculate the compliance flag and eventually the delta value between payment term reference and payment term.
There is also specific transformations to reload only the compliance flag, compliance value and terms of payment key reference. These transformations can be used for historical reloading.
To understand the rules and abap code, see this diagram:
Link: https://drive.google.com/file/d/1IEfF0ttJvvHxy5YKZ3VeMUJFFjw1Uf4a/view
The material group can be found at different places:
Caution: In case of C_PO_ITM manual data reloading via DTS_BW_PO_ITM, you MUST run also the Logistic Table and Restatement loadings.
1) Reloaded data via DTS_BW_PO_ITM;
2) Logistic Tables: Run C_PO_ITM → C_PO_ITM for the same documents reloaded in the STEP 1;
3) Restatement: Extract the full PSA from DTS_BW_GPS_EKPOREST and load RSDS DTS_BW_GPS_EKPOREST (Source System) -> IOBJ C_PO_ITM.
Usage of ECC tables:
Logistic Tables
https://drive.google.com/file/d/15EKoJ6OIzcSUmTrTCKjii1HGZLPr429k3_xGG692Qq4/view
Restatement Tables
https://drive.google.com/file/d/1YNvzNO3w0tAu9MbJdX9VIYYY-XEHD6x1WsVkH4Glzoo/view
Important : The Material Group in schedule line and FIAP Dsos & Cubes is partly false.
Currently Core & QV queries is using C_MAT_GRP from FIAP or Schedule lines. It has to be changed with C_PO_ITM attribut when Business validates it.
Field to store the Material Group value before the Logistic Tables and Restatement processes.
During the Logistic Tables logic (Transformation TRSF : C_PO_ITM -> C_PO_ITM) if the Material Group (C_MAT_GRP) has a new value defined, the Original Material Group will receive the previous Material Group (C_MAT_GRP) value.
The same occurs during the Restatement processing (Transformations: RSDS DTS_BW_GPS_EKPOREST (Source System)) -> IOBJ C_PO_ITM).
The conversion rate used in reports is CAR3.
Routine CTK_CAR3
It concerns DSOs DB_MAGR1/2/3 for Agreements, DB_MMAT1/2/3 for Materials, DB_MVEN1/2/3/4 for Vendors
DataSources are based on Infosets
Example DTS_CHANGEDOCUMENT_ART => documentation https://drive.google.com/file/d/1eo5gmIhlkehpMIbrWCFvyQVgbbvaPhiX/view
There is data flow to retreive changes on Purchasing Info Record:
Here is the documentation:
https://drive.google.com/open?id=0B6PYA70dIrclamRxbFlnTll4RXc
| Object | Datasources RCS | Abap Prog RCS | Datasources Solvay/Acetow | Abap Prog Solvay/Acetow | |
|---|---|---|---|---|---|
| Material | DTS_CHANGEDOCUMENT_ART | ZBW_MM_ART_CHANGEDOC | DTS_BW_CHG_MAT | ZPGR_BW_CHG_MAT | |
| Agreements | DTS_CHANGEDOCUMENT_CTT | ZBW_MM_CTT_CHANGEDOC | DTS_BW_CHG_AGR | ZPGR_BW_CHG_AGR | |
| Vendor | DTS_CHANGEDOCUMENT_VEN | ZBW_MM_VEN_CHANGEDOC | DTS_BW_CHG_VEN | ZPGR_BW_CHG_VEN | |
| Purchasing Info Record | DTS_BW_PIR_CHANGEDOC | ZFM_BW_PIR_CHANGEDOC (function module) | DTS_BW_PIR_CHANGEDOC | ZFM_BW_PIR_CHANGEDOC (function module) |
Web Dynpro are used for integration of some masterdata informations :
Users are then autonomous to update BW masterdata (creation of flat file / check of the flat file / upload of the flat file / status of the execution of the associated process chain)
Web dynpro documentation is available in following directory: https://drive.google.com/drive/folders/1JHeLUAE_Js_OBgEjaE6BkUHBJ4mHw3YM
The flat files to load have to follow rules to be uploaded into BW. See https://drive.google.com/file/d/15vd01-rTmtbvfAAJ93HJ9g0t_trLXa28J61U5xvETq8/view
The user interface is available in Solia portal.
See user documentation https://drive.google.com/file/d/1hXc4s5sITM6PcX86qKQiyj-LbbIjJ64_2jhJBL18ROs/view
Currently, only Sylvie Sévérini has the access. The technical team do not have access. Tests have to be done via SE80.
Contact person for any issue on Portal / Sprint menu : Reiner Hellstern (person who has replaced José Cervera)
Documentation to make transport in java portal: How to release/transport Webdynpro on the Java portals
Good to know: For Sprint, in java portal, the name of web dynpro are changed, there are the prefix "SPRINT -" before the name.
To change the name in java portal, it's on propriety of Iview and Workset (it's the same manipulation for both):
Then, go clic on "All" to have all proprieties and search propreity called "Name".
Or search directly the propriety with the research bar.
When you are in the propriety, you can add the prefix.
Loadings are managed via process chains, launched on event (See Process Chain paragraph)
Example: PC_C_VENDID_SEG / event PC_C_VENDID_SEG
| Description | BW masterdata impacted | Fields impacted | Webdynpro |
|---|---|---|---|
| Integration Material Group Segment | C_MAT_GRP | Source system (Key) Material group (Key) Material Group Purchasing (Obsolete) Segment code Costs Macro-Package Costs Package Costs Sub-Package | ZWD_FILE_C_MAT_GRP_SEGT |
| Integration Material Product | C_MATNR2 | Source system (Key) Material (Key) Product (PUR) Value Chain (PUR) First Used Date Material Attribute 1 (PUR) Material Attribute 2 (PUR) | ZWD_FILE_C_MATNR2_PROD |
| Integration Plant Site | C_PLANT | Source system (Key) Plant (Key) Purchasing site Authorization Scope | ZWD_FILE_C_PLANT_SITE |
| Integration Purchasing Scope | C_COMPPRS | PRS Company code (Key) Purchasing Scope | ZWD_FILE_C_COMPPRS_PSCOPE |
| Integration Vendor Segment | C_VENDID | Source system (Key) Vendor number (Key) (Obsolete) DUNS - Domestic Ultimate Segment code Class Segmentation approval date Segmentation approval user | ZWD_FILE_C_VENDID_SEGT |
| Integration Value Chain (PUR) Text | C_PRODGRP_TXT | Value Chain (PUR) (Key) Medium description | ZWD_FILE_PRODGRP_TEXT |
| Integration Product Text | C_PURPROD_TXT | Product (PUR) (Key) Medium description | ZWD_FILE_PURPROD_TEXT |
| Integration Purchasing Scope Text | C_PSCOPE_TXT | Purchasing scopte (Key) Short description | ZWD_FILE_PSCOPE_TEXT |
| Integration Material Text attr 1 (PUR) | C_MAT_AT1 | Material Attribute 1 (PUR) (Key) Medium description | ZWD_FILE_C_MAT_AT1_TEXT |
| Integration Material Text attr 2 (PUR) | C_MAT_AT2 | Material Attribute 2 (PUR) (Key) Medium description | ZWD_FILE_C_MAT_AT2_TEXT |
| Integration Vendor Attributes (PUR) | C_VENDID | Source system (Key) Vendor number (Key) Vendor Attribute 1 (PUR) Vendor Attribute 2 (PUR) | ZWD_FILE_C_VENDID_ATTR |
| Integration Vendor Text attr 1 (PUR) | C_VND_AT1 | Vendor Attribute 1 (PUR) (Key) Medium description | ZWD_FILE_C_VND_AT1_TEXT |
| Integration Vendor Text attr 2 (PUR) | C_VND_AT2 | Vendor Attribute 2 (PUR) (Key) Medium description | ZWD_FILE_C_VND_AT2_TEXT |
| Integration Payment terms Attributes (PUR) | C_PMNTTRM | Source system (Key) Term of payment key (Key) Payment term attribute 1 (PUR) Payment term attribute 2 (PUR) | ZWD_FILE_C_PMNTTRM_ATTR |
| Integration Payment term attr 1 Text (PUR) | C_PMT_AT1 | Payment term attribute 1 (PUR) (Key) Long description | ZWD_FILE_C_PMT_AT1_TEXT |
| Integration Payment term attr 2 Text (PUR) | C_PMT_AT2 | Payment term attribute 1 (PUR) (Key) Long description | ZWD_FILE_C_PMT_AT2_TEXT |
| File Integration Site text | C_SITE_TXT | Site Key Language key Site txt | ZWD_FILE_C_SITE_TEXT |
| File Integration Vendor country | C_VENDID | Source System Key Vendid Key country | ZWD_FILE_C_VENDID_COUNTRY |
| File Integration Plant text | C_PLANT_TXT | Source System Key Plant Key Plant Txt | ZWD_FILE_C_PLANT_TEXT |
| File Integration vendid text | C_VENDID_TXT | Source System Key Vendid Key Vendid Txt | ZWD_FILE_C_VENDID_TEXT |
| File Integration company code text (cytec src system) | C_COMPCDE_TXT | Source System Key Company code Key Company code Txt | ZWD_FILE_C_COMPCDE_TEXT |
| File Integration company code Auth scp + PRS (Cytec system) | C_COMPCDE | Source System Key Company code Key PRS Company code Authorization Scope | ZWD_FILE_C_CMPCDE_PRS_AUT |
| File Integration Material Text | C_MATNR2_TXT | Source System Key Material Key Material Key (Text) | ZWD_FILE_C_MATNR2_TEXT |
| File Integration material group text | C_MAT_GRP_TEXT | Source System Key Material Group Key Material Key (Text) | ZWD_FILE_C_MAT_GRP_TEXT |
| File Integration DSO Company Code (Site Restated (P)) | DPCOMPCD (dso) | Source System Key Company code Key Site Restated (P) Key | ZWD_FILE_DPCOMPCD |
When web dynpro ZWD_FILE_C_VENDID_SEGT is used, in transformation TRSF : DTS_C_VENDID_SEG -> C_VENDID (WebDynpro), in start routine there is a verification:
If the vendor has a correpondance in master data vendor PRS, no update is possible and attributes have to manage in PRS. So the records isn't updated.
To get the url corresponding to the WebDynpro...
SE80
Caution Few KeyFigure are in "Summation" mode in transformations : for PO Schedule lines DSOs (DB_PUSL1/2/3), for PO History DSOs (DB_PUHD1/2/3)
In the cope of Power of 2 project, the VBF data flow and program was duplicated, a new data flow and transaction for SCO were created, the original data flow / transaction (above) are for ECO data.
We applied a physical segregation in some transformations.
To activate the segregation, in master data global filter a variable need to be activated:
If in global filter field C_LOW = YES,
Few DSOs are shared with FI :
The following objects have been developed:
New Objects | Existing Objects (to be replaced by the new ones) | ||
Type | Name | Type | Name |
aDSO | “Consignment Withdrawals (Rhodia)” [ABMMPUCS1] | DSO | “Consignment Withdrawals (Rhodia)” [DB_PUCS1] |
aDSO | “Consignment Withdrawals (Solvay)” [ABMMPUCS2] | DSO | “Consignment Withdrawals (Solvay)” [DB_PUCS2] |
aDSO | “MM CYTEC : Material Management (PC_FILE)” [ABMMCY01] | DSO | “MM CYTEC : Material Managment (PC_FILE)” [DBMMCY01] |
aDSO | “PO : Historical Data (Rhodia)” [ABPOPUHD1] | DSO | “PO : Historical Data (Rhodia)” [DB_PUHD1] |
aDSO | “PO : Historical Data (Solvay)” [ABPOPUHD2] | DSO | “PO : Historical Data (Solvay)” [DB_PUHD2] |
Composite Provider | “SPRINT - PO/Spend Analysis” [CPPURSPD01] | MultiProvider | “SPRINT - PO/Spend Analysis” [MV_SPD01] |
Queries | “SPRINT - PUR: Spend (MM) (Core Query)” [BW_QRY_CPPURSPD01_0001] [QV_ BW_QRY_CPPURSPD01_0001] [DI_ BW_QRY_CPPURSPD01_0001] | Query | “SPRINT - PUR: Spend (MM) (Core Query)” [BW_QRY_MV_SPD01_0025] |
A high-level overview of the Data Flows is provided in the diagram depicted below:
The Composite Provider “SPRINT – PO/Spend Analysis” is fed from five newly developed Advanced DSOs which provide information regarding Consignments, PO Historical Data and CYTEC MM:
The aDSO “Consignment Withdrawals (Rhodia)” is loaded from the Propagation Layer DSO DP_PUCS1:
The aDSO “Consignment Withdrawals (Solvay)” receives information from the Propagation Layer DSO DP_PUCS2:
The aDSO “MM CYTEC: Material Management (PC_FILE)” is populated from the Propagation Layer DSO DPMMCY01:
The aDSO “PO: Historical Data (Rhodia)” is mainly loaded from the Propagation Layer DSO DP_PUHD1. There is also a self-reflective data flow and a third transformation for loading history data from DB_PUHD1 DSO.
The aDSO “PO: Historical Data (Solvay)” is mainly loaded from the Propagation Layer DSO DP_PUHD2. There is also a self-reflective data flow and a third transformation for loading history data from DB_PUHD2 DSO.
At present, the newly created Advanced DSOs are being loaded through the following process chains in WBP:
Furthermore, the following process chains have been modified in WBD, in order to prepare them for future transport:
Upon business confirmation, these chains may be transported to Production, in conjunction with the decommissioning of the objects of the legacy data flow (i.e. DSOs DB_PUCS1, DB_PUCS2, DBMMCY01, DB_PUHD1 and DB_PUHD2, MultiProvider MV_SPD01, Query BW_QRY_MV_SPD01_0025, etc.).
See Global Filters (C_GLBFILT) part, it is possible to hold loadings from one or several souce systems.
SPRINT / ACETOW or PRS or RHODIA or SOLVAY
| Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| SPRINT: Daily Loading | PC_SPRINT_DAILY | MAIN |
| Not iso with WBD one. Avoid transport |
| SPRINT : Domain / Segment (Global) | PC_SPRINT_TR_DS1 | MAIN |
| |
| PUNCH : Global Process Chain | PC_PUNCH_GLOBAL | MAIN |
| |
| Process Chain for Shopping Cart - Main | PC_SRM_SC_ATTR | MAIN |
| Launch SRM7 |
| Process chain for performance reporting (Value Creation) | PC_PUPE_04 | MAIN |
| Load file "ConvergenceToBW.csv" from server directory /exploit/BW/BOZAR |
| CYTEC: Process chain transactional data full | PC_CYTEC_TR_FULL | MAIN | Launched by event PC_CYTEC_TR_FULL (triggered by transaction ZBW_CYTEC_SPD) | |
| CYTEC MM: Transactionnal data Cytec MM Full | PC_CYTEC_MM_TR_FULL | MAIN | Launched by event Z_EVT_PC_CYTEC_MM_TR_FULL (triggered by transaction ZBW_CYTEC_SPD) |
| Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| SPRINT : Propagation (Rhodia) | PC_SPRINT_TR_P1 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT : Propagation (Solvay) | PC_SPRINT_TR_P2 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT : Propagation (Acetow) | PC_SPRINT_TR_P3 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT: Business Layer (Rhodia) | PC_SPRINT_TR_B1 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT: Business Layer (Solvay) | PC_SPRINT_TR_B2 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT: Business Layer (Acetow) | PC_SPRINT_TR_B3 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT: Business Layer (PRS) | PC_SPRINT_TR_B4 | sub chain | OK. Aligned DEV/QAS/PROD | |
| SPRINT Reporting Layer (Rhodia) | PC_SPRINT_TR_R1 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT Reporting Layer (Solvay) | PC_SPRINT_TR_R2 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT Reporting Layer (Acetow) | PC_SPRINT_TR_R3 | sub chain | Not iso with WBD one. Avoid transport | |
| SPRINT : Domain / Segment (Business Layer) | PC_SPRINT_TR_DS2 | sub chain | Not iso with WBD one. Avoid transport caution : direct scheduling on WBP | |
| SPRINT : Domain / Segment (Reporting Layer) | PC_SPRINT_TR_DS3 | sub chain | Not iso with WBD one. Avoid transport caution : direct scheduling on WBP | |
| PUNCH : Master Data Attributes | PC_PUNCH_MD_ATTR | sub chain | ||
| PUNCH : Master Data Texts | PC_PUNCH_MD_TEXTS | sub chain | ||
| PUNCH : Business Layer (Rhodia) | PC_PUNCH_TR_B1 | sub chain | Caution : the Propa Layer (Rhodia) is done in PCH QM_DAILY_TRANS | |
| PUNCH : Reporting Layer (Rhodia) | PC_PUNCH_TR_R1 | sub chain | ||
| PUNCH : Propagation layer (Solvay) | PC_PUNCH_TR_P2 | sub chain | ||
| PUNCH : Business Layer (Solvay) | PC_PUNCH_TR_B2 | sub chain | ||
| PUNCH : Reporting Layer (Solvay) | PC_PUNCH_TR_R2 | sub chain | ||
| PUNCH : PSA and Change Log Deletion | PC_PUNCH_PSA_CHG_LOG_DEL | sub chain | ||
| Process Chain for Shopping Cart SRM7 - Main | PC_SRM7_SC_ATTR | sub chain | ||
| Process chain SRM7 Master data | ZPC_SRM7_MASTER_DATA2 | sub chain | ||
| SRM: Global Chain | PC_SRM_001 | sub chain | ||
| SRM: MD ATTR - D - 001 | PC_SRM_MD_ATTR_001 | sub chain | under SRM: Global Chain | |
| SRM: MD TXT - D - 001 | PC_SRM_MD_TXT_001 | sub chain | under SRM: Global Chain | |
| SRM: TD - D - 003 | PC_SRM_003 | sub chain | under SRM: Global Chain | |
| CYTEC: Process chain transactional data propagation | PC_CYTEC_TR_P1 | sub chain | ||
| CYTEC: Process chain transactional data business | PC_CYTEC_TR_B1 | sub chain | ||
| CYTEC: Process chain transactional data reporting | PC_CYTEC_TR_R1 | sub chain | ||
| CYTEC MM: Transactional data Cytec MM propagation | PC_CYTEC_MM_TR_P1 | sub chain | ||
| CYTEC MM: Transactionnal data Cytec MM Business | PC_CYTEC_MM_TR_B1 | sub chain | ||
| CYTEC MM: Transactionnal data Cytec MM Reporting | PC_CYTEC_MM_TR_R1 | sub chain |
| Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| PC : Company PRS - Purchasing Scope | PC_C_COMPPRS_PSCOPE | flat file upload | On demand via Solia | Event PC_C_COMPPRS_PSCOPE |
| PC : Material Group Segmentation | PC_C_MAT_GRP_SEG | flat file upload | On demand via Solia | Event PC_C_MAT_GRP_SEG |
| PC : Material Product Code | PC_C_MATNR2_PROD | flat file upload | On demand via Solia | Event PC_C_MATNR2_PROD |
| PC : Plant Site | PC_C_PLANT_SITE | flat file upload | On demand via Solia | Event PC_C_PLANT_SITE |
| PC : Product Group Text | PC_C_PURPROD_TXT | flat file upload | On demand via Solia | Event PC_C_PURPROD_TXT |
| PC : Purchasing Scope Text | PC_C_PSCOPE_TXT | flat file upload | On demand via Solia | Event PC_C_PSCOPE_TXT |
| PC : Vendor Segmentation | PC_C_VENDID_SEG | flat file upload | On demand via Solia | Event PC_C_VENDID_SEG |
| PC : Vendid country | PC_C_VENDID_COUNTRY | flat file upload | On demand | Event PC_C_VENDID_COUNTRY |
| PC : Plant text (for Cytec source system) | PC_C_PLANT_CYTEC_TXT | flat file upload | On demand | Event PC_C_PLANT_CYTEC_TXT |
| PC: VENDID text (for Cytec source system) | PC_C_VENDID_CYTEC_TXT | flat file upload | On demand | Event PC_C_VENDID_CYTEC_TXT |
| PC: COPMPCDE text (for Cytec source system) | PC_C_COMPCDE_CYTEC_TXT | flat file upload | On demand | Event PC_C_COMPCDE_TEXT |
| PC: Company code cytec authorization scope & PRS attributes | PC_C_COMPCDE_AUTH_PRS | flat file upload | On demand | Event PC_C_COMPCDE_AUTH_PRS |
| PC: DSO DPCOMPCD Company Code Purchasing Attributes | PC_DPCOMPCD_01 | flat file upload | On demand | Event Z_EVT_PC_DPCOMPCD_01 |
| SPRINT: Master Data Material group text | PC_C_MAT_GRP_CYTEC_TXT | flat file upload | On demand | Event Z_EVT_PC_C_MAT_GRP_CYTEC_TXT |
| SPRINT: Master Data - Material Text | ZWD_FILE_C_MATNR2_TEXT | flat file upload | On demand | Event Z_EVT_PC_C_MATNR2_CYTEC_TXT |
| Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| S3: Reporting Tool | PC_SPEND_S3_01 | Flat File Upload | On a Business request | Run manually |
Process Chain PC_SPRINT_DAILY runs daily, Sunday night to thursday night, around 5am.
Process Chain PC_SPRINT_TR_DS1 runs weekly on sundays at 12am
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | Daily Main Process Chain lasts around 2 hours 1/2 Weekly Process Chain lasts around 1 hour |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
No historisation in place.
For FIAP/FIGL, current year + 3 previous ones are requested
For Po Schedule lines, schedule lines frim 01/01/2013 are available
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
SPRINT training & SPRINT presentation
https://drive.google.com/a/solvay.com/folderview?id=0B5Ivsv4WTtUbVktFZlNVRkNYU1k&usp=sharing
List the most important and complex queries only with a link to the documentation
No Broadcast implemented
Give the list and explanation on the known, not-solved, bugs.
Variable (TVARVC)
| Variable | Explanation |
|---|---|
LOGSYS_A , LOGSYS_R, LOGSYS_S A= Acetow, R=Rhodia, S=Solvay | Bex variable V_LOGSYS_0007 used to fill query prompt => SE24 ZCL_BIU001_V_0LOGSYS_0007 |
Global Filters (C_GLBFILT)
| Stream | Rule | Explanation |
|---|---|---|
| SPRINT | DB_FIAP1 DB_FIAP2 | Variable used in transformation (start routine) between DBFIAP01/2 => DB_FIAP1/2. Aim : skip the DSO DB_FIAP1/2 lookup. In case of a reloading of FIAP, this look-up in not usefull. To optimize loading time, set the filter to Y. Do not forget to put it back to N afterwards. |
| SPRINT | SEGMENTAT | Variable used in DTP filter to define the number of year to consider for segmentation redetermination DSOs : DB_FIAP1/2/3 + DB_PUHD1/2/3 + DB_PUSL1/2/3 |
| SPRINT | CLASS_X | Variable used in transformation to load Vendor number from DataSource 0VENDOR_ATTR / Solvay currently : interval P000000000 and PZZZZZZZZZ |
| SPRINT | ACETOW RHODIA SOLVAY PRS | Theses variables are used in Process Chains. After the loading of the attributes of the master data, there is a decision (one by source system) to launch or not the loading of the transactionnal data |
| FIAP | DOC_TYP_4 | Variable used in query BW_QRY_MV_SPD01_0008 in selection screen. A huge list of values are taking into account. This variable reach limit of number of ligne to display in a selection screen in Analyzis if you put the variable "Ready for Input" Example of values : 18 + 19 + 23 + 24 + 43 + 44 + 48 + 49 + 53 + 54 + 63.... |
| FIAP | PREV_YEAR | Nb prev years for period DTP DSO DB_FIAP* -> DB_FIAP* OLD!! Obsolete : has been replaced by variable SPRINT / SEGMENTAT |
| SPRINT | C_PURRQI | DTS_BW_PR_CHANGEDOC --> MD_C_PURRQI init => Value = Y If value = Y, it means we want to re-init the masterdata C_PURRQI, the current Release Date has to be replaced. If value = N, it means it is normal process, the current Release do not have to be changed to keep the initial one. |
| SPRINT | CR_PUAP3 | Variable used in start routine between ODS DB_FIAP3 and cube CR_PUAP3 to not taking into account one company code |
| SPRINT | 0AC_DOC_NO | Exclusion doc FIAP FIGL: src_syst/ac_doc/year/compcde/item |
| SPRINT | DB_FIAP3 | Exclusion of company code in start routine of DB_FIAP3 |
| SPRINT | WEBDYNPRO | SPRINT: TIME ALLOWED FOR WEB DYNPRO LOADING |
| SPRINT | C_VND_AT1 | Value of c_vnd_at1 used by default for new entries in master data c_vendid (see transformations of master data) |
| BOZAR | BFC_VBF | Exclusion BFC 0001 for calc of VBF in DB_BOCAL |
| BOZAR | C_BUSLINE | Exclusion of business line in start routine dso DBPUPE02 |
| BOZAR | DATE_PERF | Select data after year to not have multi year in DBPUPE02 (201412) |
| BOZAR | PROGRAM | Select data with program to exclude on DSO DBPUPE02 (Supply Chain Excellence) |
| BOZAR | %VBF | Default percentage VBF in transformation DB_BOCAL → DB_BOCAL (cases where %VBF per domain not filled in filters) (4.5) |
| BOZAR | I%VBF | Default %VBF in trf DB_BOCAL -> DB_BOCAL when I%VBF is empty (cases where I%VBF per domain not filled in filters) (5) |
FIAP for SPRINT Dsos (CR_PUAP1/2/3), and Cubes (CR_PUAP1/2/3) have been reloaded several times since project golive.
At least Sprint needs: current year + 3 previous ones.
Example 2016 => 2016 + 2013 to 2015
See ModOp SPRINT reloadings https://drive.google.com/file/d/1mcse4gg1zrU6J0g_TailnWUJYPkmbm5Fl8VSEIaq0rc/view
Caution :
Test Queries to check data Sprint vs WC + common DSOs :
Data can be check a company code level. Make sur all the demand in common split DSO are loaded into Sprint Dsos/Cubes and WC Cubes
On DB_FIAP DSO, during the delta loading (from DBFIAP* to DB_FIAP*) if the material code (C_MATNR2) is empty, we take the material from master data C_PO_ITEM.
In transformation TRSF : DBFIAP04 -> DB_FIAP3 (Acetow), in start routine with help of master data global filter (C_GLBFILT, Stream SPRINT, Rule DB_FIAP3) we delete data with company code 7315 with posting date before 01.05.2017.
In transformation between ODS DBFIAP* and DB_FIAP* we define the several status of payment. It's a little bit complicated to understand, is why we have one document to resume the rules:
https://drive.google.com/file/d/1M0AbEM5ptK_qTziwj88Z_vy0KMFTWuXCG7v8itC5EWM/view
New sources was added in Sprint FIAP flow: DBFIAP05, DBFIAP06 and DBFIAP07.
The goal of these new sources it's to update if necessary some information like clearing date or clearing doc (take into account clearing from factoring dso and not only fiap dso).
For more detail, check this documentation:
https://drive.google.com/file/d/1voS1QF_wu84RFjOpqDqFPX0ddUgWzY6UQLW8ABhn4Ig/view
This procedure should only be applied if the purchasing data team has requested it (Sylvie Severini or Yi Ting Kuo) by ticket.
There are some exclusions in transformations (start routines) between DSO DBFIAP01 / 02 / 04 to DB_FIAP1 / 2 / 3 (FIAP line Item Splitted -> FIAP for Sprint).
Exclusion is also made in expert routine in transformations from DSO FIAP : Line Item Splitted - Factoring Level 2 and DSO FIAP for Sprint.
The goal is exclude several acounting documents with inconsistent values. For that, abap code will be read master data global filter with attributes:
In field "Low" of master data, values must be entered in format : source system/accounting document number/item number/year/company code
Example:
With that, abap code will remove from source package rows with these informations.
You can find impacts on queries on the file below:
https://drive.google.com/file/d/1Stem0UEeHcBhF1snbsakNV-ciQ5ogeATLwExuebaeNw/view
It may be necessary to exclude new documents.
To do that, it's necessary to now the source system / document / item number / year / company code and update master data global filter.
Then, make a selective deletion on fiap cube and dso on accounting document / company code / year (it's not possible to delete only accounting document concerned because item number isn't available in cube fiap).
When selective deletion is done, reload data on DSO Sprint with DTP with same filters used for selective deletion.
All data will be recovered, except documents on master data global filter (for some item number).
When Sprint FIAP DSO is reload, launch delta dtp to reload SPRINT FIAP cube.
For more detail, check this documentation:
https://drive.google.com/file/d/1o98yNBZKk2VIY0d3vw0bMfmY7TuwfqkOghC6nLLPQWQ/view
This procedure should only be applied if the purchasing data team has requested it (Sylvie Severini or Yi Ting Kuo) by ticket.
There are some exclusions in transformations (start routine) between DSO FIAP : AP from FIGL: Line Items - Level 2 and Cubes: FIGL for SPRINT.
The goal is exclude several acounting documents with inconsistent values. For that, abap code will be read master data global filter with attributes:
In field "Low" of master data, values must be entered in format : source system/accounting document number/item number/year/company code
Example:
With that, abap code will remove from source package rows with these informations.
You can find impacts on queries on the file below:
https://drive.google.com/file/d/1Stem0UEeHcBhF1snbsakNV-ciQ5ogeATLwExuebaeNw/view
It may be necessary to exclude new documents.
To do that, it's necessary to now the source system / document / item number / year / company code and update master data global filter.
Then, make a selective deletion on fiap cube and dso on company code / year (it's not possible to delete only accounting document concerned because accounting document and item number aren't available in cube FIGL for SPRINT).
When selective deletion is done, reload data on DSO Sprint with DTP with same filters used for selective deletion.
All data will be recovered, except documents on master data global filter (for some item number).
Be carreful, there is a rule between propagation DSO and business DSO to exclude lines with FIGL Domain not equal to "AP". It could happen some documents with at the origin the FIGL Domain at "AP" and then the domain change. So when we make the selective deletion and after the reloading, these lines aren't loaded.
When Sprint FIGL DSO is reload, launch delta dtp to reload SPRINT FIGL cube.
For more detail, check this documentation:
https://drive.google.com/file/d/1o98yNBZKk2VIY0d3vw0bMfmY7TuwfqkOghC6nLLPQWQ/view
Caution, take into account special periods 013 to 016, overwise December figures will be wrong.
Special periods 013 to 016 are at last stored on period 012.
See ModOp SPRINT reloadings https://drive.google.com/file/d/1mcse4gg1zrU6J0g_TailnWUJYPkmbm5Fl8VSEIaq0rc/view
It is important to check image Before/After. Only opened periods could be differents.
See ModOp SPRINT reloadings https://drive.google.com/file/d/1mcse4gg1zrU6J0g_TailnWUJYPkmbm5Fl8VSEIaq0rc/view
For information, at the reloading of readsoft there have been issue during activation of data in DSO DB_RDSF1 & DB_RDSF2.
Somes rows had currency = USA, chinese character in field wc user and "!" in the beginning of field Reference document number.
So there is an exclusion in DTPs when currency = USA and routines to clear stranges characters for wc user and reference document number.
It can happen that some Readsoft Cockpit Documents were manually updated in WP1 and PF1 (to force the Clearing Document and Clearing Date and reset the status).
In this case and for the moment, to update the changes in bw the solution is:
(2.1 + 3.1)
Don't forget to delete the routine in infopackage after the reloading;
Source data for Value Creation come from Convergence source system and loaded in bw server with help of webmethods (Transaction AL11 → directory /exploit/BW/BOZAR → filename "ConvergenceToBW.csv").
Normally, webmethods launch event Z_EVT_PC_PUPE to run process chain PC_PUPE_04 and load automatically dso and cube.
Interface Value Creation: Salesforce-Webmethods-BW-QV
With PO2 project, we had to add C_AUTHMA object in Performance data flow.
The issue is we don't have any obect linked (like C_COMPCDE) with C_AUTHMA in source of data (flat file from convergence). It was decided to add a code in convergence side after the GBU.
It means, in flat file we received a field with three characters for the GBU instead two:
And in propagation DSO, the field CPFCTR1_2 is replaced by C_GBUSCOP (with three characters).
Between the propagation and the business DSO in transformation TRSF: ODSO DPPUPE01 -> ODSO DBPUPE01, a lookup with master data global filter is done to retreive the C_AUTHMA associated to the code (0, 1, 2, Z) and split the C_GBUSCOP in CPFCTR1_2 with the two first characters and the C_AUTHMA with the text associated to the code.
It means C_GBUSCOP = CH1 is transformed in CPFCTR1_2 = CH and C_AUTHMA = ECO. All records with "1" in C_GBUSCOP are ECO, with "2" are SCO.
The C_AUTHMA is added in cube and multiprovider, then used in queries with authorization variable.
One master data text (C_BUSLINE) is filled by process chain PC_PUPE_02 (sub chain of PC_PUPE_04). Texts come from datat source DTS_PUPE_01 (same as transactional data of data flow Value Creation).
There is another master data used for Value Creation:
This master data is maintain on demand of purchasing team (Sylvie.Severini or Yi Ting Kuo).
In case of change, for attributes it's necessary to prepare a csv file in this format for example:
Then load the file in master data (change the source file of infopackage before to use the new file). For texts, for the moment, we change directly in text table of master data,.
Datasource DTS_PUPE_01: please to check data don't use "PSA Maintenance" button but use directly PSA table /BIC/B0011690001. Because of field description with type CHAR length 600 in datasource if we use "PSA Maintenance" we have a dump. It's necessary to have a lentgh of 600 to retreive all information of description (this field will be splited in next transformation).
Check process chain PC_PUPE_04 between 1:00:00 am Paris Time (Hours where the flat file is sent from convergence to BW sever) and before 7:00:00 am Pais Time (hour where qlikview run the query to load the dashboard).
If the process chain is not in progress or completed, look on Tcode AL11 and find the flat file (→ directory /exploit/BW/BOZAR → filename "ConvergenceToBW.csv").
If the file is the date of the day, there has been an issue when launching the process chain.
If the file has a date of day before, there is an issue to load flat file with webmethod. Please create a Freshdesk ticket or direct contact Support.XML@solvay.com.
If the process chain is in error, please investigate on the type of issue. In case of invalid value or invalid character please contact Salesforce team (Sylvie.Severini@solvay.com If she is unavailable, send a mail to gps.pur@solvay.com ) to know if it's a source problem and if it's possible to correct the issue in Salesforce.
If the value creation data are loaded in cube CRPUPE01 after 7:00:00 am (Paris time), please contact Qlikview team to ask to reload manually the dashbord PPV (Performing Performance Visibility).
In all cases, when data are loaded in BW, please contact QlikView team to reloaded Purchasing Performance Visibility dashboard.
There can be three types of errors:
If webMethods team can send the file to load to bw team:
BW team need to update infopackage "IP: DTS_PUPE_01 PC_FILE - Full" to use local file and not server file (do not forget to hand over server file after).
Then, load data on DTS_PUPE_01 and after that run process chain PC_PUPE_03 (Go to transaction SE37, run Function Module RSPC_API_CHAIN_START):
Wait for data to be loaded, then run also PC_PUPE_02 (Texts).
If webMethods team can't send the file to load to bw team:
Wait for data to be loaded, then run also PC_PUPE_02 (Texts).
https://drive.google.com/file/d/1YJw6Hla_TuG1hjKZR17WQoExfevNJ0lW9ia_Uytxnrw/view
These evolutions are currently in progress (list to be updated)
First analysis : https://drive.google.com/file/d/1GzJei0CCHhVDLFkEXzlzvHn4l3n1P4OE5SGJZCkt4D0/view
| Transaction | Description | Corresponding table | Comments |
|---|---|---|---|
| XK03 | Display Vendor (Central) | LFA1 | |
| MK03 | Display Vendor (Purchasing) | LFM1/LFM2 | |
| FK03 | Display Vendor (Company Code) | LFB1 | |
| ME23N | Display Purchase Order | EKKO/EKPO | |
| ME53N | Display Purchase Request | EBAN | |
| FB03 | Display Accounting Document | MKPF/BSEG BSIK/BSAK | |
| ME13 | Display Purchase Info Record (PIR) Afficher Fiche Info Achat (FIA) | to display scale (barême) choose "conditions" then icon "steps (marches) example RCS : Info Record 53002260253 or 5300260253 | |
| ME03 | Display Source List | source d'approvisionnement example RCS : material 1050025 / plant 7822 | |
| ZBW_VBF_LOAD | Load VBF filters and calculate VBF | ZBW_LOAD_FILE_VBF_FILTERS | Linked to authorization ZR_RCS_CA_M591 |
| ZBW_VBF_LOAD_2 | Load VBF filters and calculate VBF for SCO | ZBW_LOAD_FILE_VBF_FILTERS_2 | |
| ZBW_CYTEC_SPD | Load CYTEC transactional data | ZBW_LOAD_FLAT_FILE_CYTEC | Linked to authorization ZR_RCS_CA_M041 |