Access Management 

DataFlow

Overview

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

Technical Rules on Workbench

TRSF: ODSO DPCOCA01 -> ADSO ABECO203 & TRSF: ADSO APCOCA01 -> ADSO ABECO211 & TRSF: APCOPP01 -> ADSO ABECO201 & TRSF: APCOPP02 -> ABECO207 & TRSF: ODSO ODS6CCA9 -> ADSO ABECO202 & TRSF: ODS_CCA9 -> ABECO208

Start routine:

Collecting Information from Table T006: The code performs a SELECT query to extract information from the T006 table into the internal table ITB_T006. The extracted data includes rows where the DIMID field is equal to specific values like 'AAAADL', 'ENERGY', 'MASS', 'POWER', 'VOLUME', or 'ZAI'.

Checks if the unit extracted from the source structure is found in the ITB_T006 table. If the unit is not found in the table, the data row is deleted from the source package.

Collecting Cost Center Information: Next, the code performs two SELECT queries to collect information about cost centers from the ZECR_FT_CC_T and /BIC/MC_COSTCTR tables. It uses this informatios to potentially remove non-compliant data rows.

If source line exists in ITB_CC (in function of co_area and c_cosctr):

Check in ITB_FT_CC is the logsys and c_costctr exist. If not, the record is deleted.

If source line not exists in ITB_CC (in function of co_area and c_cosctr):

Delete record.

Collecting Other Information: The code carries out additional SELECT queries to collect information from various tables such as /BIC/PC_COSTCTR, /BIC/PC_COMPCDE, ZECR_AS_CC2EQ_T, ZECR_AS_CE2VC_T, ZECR_CV_UOM2_T, ZECR_AS_VFLAG_T, and /BIC/PC_PRDEQUI. 

Collecting Information from Table T006: The code performs a SELECT query to extract information from the T006 table into the internal table ITB_T006. The extracted data includes rows where the DIMID field is equal to specific values like 'AAAADL', 'ENERGY', 'MASS', 'POWER', 'VOLUME', or 'ZAI'.

Checks if the unit extracted from the source structure is found in the ITB_T006 table. If the unit is not found in the table, the data row is deleted from the source package.

End routine:

Read internal table ITB_UOM (from table  ZECR_CV_UOM2_T) with help of LOGSYS, COSTELMNT, U_UNITUM, C_PLANT, and C_COSTCTR. If a corrspondance is done and in function of the period: K_ACT_QTY *<FS_UOM>-K_UOMCVRT * <FS_UOM>-K_UMREZ / <FS_UOM>-K_UMREN and  U_UNITUM  = <FS_UOM>-UNIT.

If nothing found in internal table ITB_UOM, check with source fields LOGSYS, COSTELMNT, U_UNITUM, C_PLANT and C_COSTCTR empty.If a corrspondance is done and in function of the period: K_ACT_QTY *<FS_UOM>-K_UOMCVRT * <FS_UOM>-K_UMREZ / <FS_UOM>-K_UMREN and  U_UNITUM  = <FS_UOM>-UNIT.

If nothing found in internal table ITB_UOM, check with source fields LOGSYS, COSTELMNT, U_UNITUM, and C_PLANT + C_COSTCTR empties.If a corrspondance is done and in function of the period: K_ACT_QTY *<FS_UOM>-K_UOMCVRT * <FS_UOM>-K_UMREZ / <FS_UOM>-K_UMREN and  U_UNITUM  = <FS_UOM>-UNIT.

Read internal table ITB_T006 and in function of the dimension, make a conversion of the quantities (examples here).

For dso ABECO202 and ABECO208

Production equipment (C_PRDEQUI) and Vecotr (C_VECTOR) are by default assigned to "ND" (not defined).

Read internal table ITB_PRDEQUI (from ZECR_AS_CC2EQ_T) with LOGSYS, COSTCTR and COSTELMNT if there is a corrspondance in internal table, tkae the C_PRDEQUI from internal table. If no correspondance, search the same but with COSTELEMNT empty, is corrspondance take C_PRDEQUI.

If not, same principle with COSTELMNT and COSTCTR empties.

Read internal table ITB_VECTOR (from  ZECR_AS_CE2VC_T) with LOGSYS, COSTCTR, C_MATNR2 and COSTELMNT if there is a corrspondance in internal table, tkae the C_VECTOR from internal table. If no correspondance, search the same but with COSTCTR empty, is corrspondance take C_VECTOR.

If not, same rinciple with C_MATNR2 empty, then C_COSTCTR + C_MATNR2 empties, then C_COSTCTR + C_MATNR2 + C_COSTELMNT empties.

For dso ABECO203 and ABECO211 same logic but with STKEYFIG instead COSTELMNT.

For dso ABECO201 and ABECO207 same logic but with C_HRKFT + C_INDEX1 + C_KSTRG4 + LOGSYS or  LOGSYS  + C_HRKFT + C_HRKFT + C_KSTRG4 + C_ORIMAP3.

After these steps if we have a C_PREDQUI and this one is present in internal table ITB_SITE (master data C_PRDEQUI).

Read internal table ITB_VFLAG (table ZECR_AS_VFLAG_T) in function of site of internal table ITB_SITE.

If a result is found and in function of fiscal period, if last two characters of C_VECTOR = SO →  C_PRCOIND = P. Else if (source fields DB_CR_IND = S and K_ACT_QTY >= 0 ) or two last characters of C_VECTOR = PU → C_PRCOIND = PU. Else C_PRCOIND = P.

Further explanations for program ZBW_ZECO2_FILE - ZECO2_FILE Transaction

User can choose an Excel flat file from his local computer by using the "File to load" browser.

Once the file is chosen, the user can preview the content to be uploaded from his selected file by clicking on "Preview" icon.

Preview is color-coded: green entries are correct, while red entries contain one or more errors based on Business Rules detailed below.

Once the file is chosen, the user can start the content checking of the file by clicking on "Check file" icon.

If errors exists, they will be listed with the associated error code and long text (MD C_REJECT) at the end of each line.

Once the file content is checked and all errors corrected, the user can load the file to BW application server (AL11) and raise the event associated with the type of import they chose by clicking on "Load file" icon.

The event raised Z_EVT_PC_CO_ECO2_22 triggers the process chain PC_CO_ECO2_22 which loads the user's file data into CO2 ADSO ABECO206.

Source Code

Report ZBW_ZECO2_FILE contains several distinct forms:

Interface

Selection screen.

Import File

f200-import_file:  Import the XLS file from user's workstation.

f210-upload_excel:  Convert the XLS file in Internal table.

f220-check_file:  Check content of the file as follow:

• BUSINESS RULE 1. DATASOURCE  VALUE  - ECO2_BR1 (Rejection Code)

Authorized values: SERT and EPS

• BUSINESS RULE 2. FISCAL PERIOD  VALUE  - ECO2_BR2

Between 001.1900 and 012.9999

• BUSINESS RULE 3. PRODUCTION EQUIPMENT EXISTS   - ECO2_BR3
• BUSINESS RULE 4. VECTOR EXISTS   - ECO2_BR4
• BUSINESS RULE 5. PROD/CONS INDICATOR  VALUE  - ECO2_BR5

Authorized values: C (Consumption) and P (Production)

• BUSINESS RULE 6. VALIDATION FLAG  VALUE  - ECO2_BR6

Authorized values: 'X' or empty

• BUSINESS RULE 7. UNITS EXIST
  • BUSINESS RULE 7.1. AI UNIT EXISTS   - ECO2_BR7_1
  • BUSINESS RULE 7.2. STANDARD UNIT EXISTS   - ECO2_BR7_2
• BUSINESS RULE 8. CURRENCY EXISTS - ECO2_BR8
• BUSINESS RULE 9. KEY FIGURES ARE NUMERICS - ECO2_BR9
• BUSINESS RULE 10. NO DUPLICATED ENTRIES - ECO2_BR10

Program Output

f300-output_preview: Generate ALV grid to show Converted data from Excel.

f310-output_check: Generate ALV grid to show Converted data from Excel after check.

Program Load

f400-load_pchain: Check if process chain is already in progress.

f413-csv_file_data: Import Customer file in ALL11.

• Filename consumed by process chain PC_CO_ECO2_22 is hardcoded in this form:  "/exploit/BW/ECO2/ECO2_flat_file.csv".
• Flat file integrated manually by user, is saved as follow: '/exploit/BW/ECO2/' w_file '_' sy-sysid '_' sy-uname '.csv'.
  Where  w_file is the filename on user's local pc, sy-sysid is the BW environment and sy-uname is the user name which is running the program.

f423-filename_data: Update Global filter master data with new file name.

f433-savelog_data: Update log after loading (ADSO APECO201  - "ECO2 - Flat Files Log").

f440-finish_message: Pop- up  message once the program's operations are complete .

f453-send_email_data: Send an email after data loading.

Program Log

f500-display_log: Display log.

Historisation of Conversion Data

Based on Validation Flag set in ZECO2 for a given Site/Period.

ABECO204 → ABECO205 → ABECO212

Read ABECO212 & ABECO205 when loading ABECO204.

Load ABECO205 only with entries where Validation Flag = ''

Before reloading ABECO204 & ABECO205, check ABECO205 entries and load every entry where Validation Flag = X in ZECO2 table into ABECO212.

Delete entries in ABECO212 if they exist in ABECO204 with Validation Flag = ''.

Reporting

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

Data produced by CERISE is to be used in QlikView.

Data is collected from the following existing BW applications:

• IMEP Main Dataflow PF1 (APCOPP01) + WP1 (APCOPP02)
• COCA : Cost Center Accounting (DPCOCA01, ODS_CCA9 & ODS6CCA9)
• ODS_CCA9 data is enhanced through ADSO APCOCT01

Loading frequency

Master Data (PC_CO_ECO2_02) loaded daily + on-demand upon ZECO2 Transaction run.

Transactional Data (PC_CO_ECO2_01) loaded twice daily.

Flat Files import (PC_CO_ECO2_22) on-demand.

Average performance

Record Keeping

All data is deleted before each load, no history to speak of outside of ABECO206 (Historical data from previous storage) which currently contains data up to 6 years prior (2015).

Global filters (C_GLBFILT) used in Chains

ABAP Programs used for Data Load

Further explanations for program ZECO2_LOAD_VIEWS - ZECO2 Transaction - ZECR Function Group

When leaving the Screen after editing a table, an event is launched to run the associated Process Chain. Event Z_EVT_[PC_NAME] runs [PC_NAME].

In all assignment tables, an empty key field means "ALL VALUES". Keys are listed in order of priority to determine assignment value.

Ex. for ZECR_AS_PL2VC_T: If no match is found for key 0LOGSYS/C_PLANT/C_WORKCTR/C_MATNR2, check key 0LOGSYS/C_PLANT/C_WORKCTR/'', then 0LOGSYS/C_PLANT/''/'', then 0LOGSYS/''/''/''. If still no match is found, assignment is set to default value ('ND' for C_VECTOR and C_PRDEQUI).

If the table forces C_VECTOR, leaving the Screen releases event Z_EVT_PC_CO_ECO2_13 (which runs PC_CO_ECO2_13). If it forces C_PRDEQUI, it releases event Z_EVT_PC_CO_ECO2_14 (which runs PC_CO_ECO2_14).

Data Quality Control

Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticity, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD)>