Transaction created to upload and consult the GBR objects used by Finance, Global Sales and other reports.
Project BI4 Optimization (9584).
The transaction is used by around 40 users in the worldwide split between corporate members and GBU users from Novecare, Aroma, Silica, Technology Solutions, Soda Ash, Peroxide, Special Chem, Coatis and Polyamides
The Global Business Repository (GBR) has been built some years ago with the objective to add reporting dimensions that were not managed as master data in SAP WP1 (like Customer Group, Market, Application, End-Use ). Some of the reporting dimensions are now used as well in PF1.
Technically speaking that was an Oracle database managed by specific tables dedicated to the purpose from image above.
It was thought in the context of BI4 (*) reporting and with the time these dimensions have been integrated in BW and QlikView dashboards
The QUIKLOAD was the tool responsible for getting the files tool used to load data in the GBR.
Different Functions are available and each one of them is specific for a type of data to be managed: customer groups, material groups, key-accounts, end-use … etc
Authorizations are managed bi BI4 team according to 2 levels:
by Function
by GBU
The authorization are divided between access to the transaction code, type of function (corporate and/or GBU) and also by GBU permitted.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZBI_RCS_GBR_A01 | GBR– Global Business Repository - Corporate User | GBR– Global Business Repository - Corporate User |
| ZBI_RCS_GBR_A02 | GBR– Global Business Repository - GBU User | GBR– Global Business Repository - GBU User |
| ZR_*_CA_P05 | Check authorization for the GBU |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| ZCORPORATE | Corporate information |
| ZGBUUSER | GBU User |
| Z*P05 | GBU |
Project documentation drive folder:
https://drive.google.com/drive/folders/0B_pMmZqoSOpOZ09JV0lnX19pTlU
The transaction ZBW_GBR has in the background the program ZBW_SD_GBR.
There is possible by the first block of the information to check the user manual, where:
As mentioned by the authorization section, the type of function is split between the corporate users (left screen below), that allows to upload files for all function types and GBU, which it is only allowed to upload objects with the prefix 'GBU'.
According to the GBU function selection, a new parameter with the check box option is open to check into the file the GBU filled and the user accesses.
The last box is regarding the directory from the .xls / .xlsx file and the buttons:
As it is possible to check in one of the records from previous screenshot, once the user fill the deletion flag during the upload, the attribute is erased from master data and this action is also reflected for others master data where the erased line is classified as attribute.
Other rules can be find in the functional document below.
Dependencies with other applications
For the PAX GBUs, we have the program GBR > BO, that gets valid data from GBU PX, PY and PV and send it to BO directory /exploit/BW/CIS by the program ZBW_GBR_BO with the parameters setted in the daily process chain PC_GBR_14.
The list of process chains could be found in the application component DICO_PC_BW_GBR, where except the Send data to BO, the other chains are triggered on demand by the users on the ZBW_GBR tcode.
All steps inside the chain have a treatment for error message that send a e-mail to contact the support team doing reference of the chain with error.
The load is triggered by the user via transaction ZBW_GBR
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | ~1 minute |
| ~ Average nb of rows loaded per load | ~100 |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
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.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Decommissioning of the chains/ objects using the PEP and DW2 as source is planned to be done before the project Go live.