Page tree


This application was decomissioned and replaced by IMEP. Data is used only for historical data from queries and not possible in IMEP because there is no GBU linked to them.


Access Management 


Roles & Access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation




Authorization Objects

List of authorization objects mandatory for the application.

Authorization objectExplanation


DataFlow

Overview



Technical Rules on Workbench

Objective of the application: general documentation about COPC

Dependencies with other applications

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

Data Loading


About the monthly process chain : RSP_COPC_MONTHLY

The process chain is scheduled with an event : ZEVT_PC_RSP_COPC_MONTHLY

This event is launched by the daily process chain : RSP_DAILY

The variant ABAP_WORKING_DAY is done with the program Z_WORKINGDAY_EVT + Variant ZPP_PC_CCR

Now the variant is customized to run the process chain from 1st to 5th working day before only the 5th working day to be sure to retrieve from the ECC part all informations from the previous month (month n-1).

Link with CPX system:

In scope of  8612 - Solstice Areo project, a link with CPX system was done to calcul and use vault informations in integrated margin.


Data Quality Control

Data come from SAP system. To compare data between BW and sources systems, check propagation layers.

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)>