Page tree


Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Functional and Technical rules

...

Access Management 


Panel
borderColor#ffffff
titleColor#ffffff
titleBGColor#009EE0
titleRoles & Access

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

Role CodeRole DescriptionExplanation
Panel
borderColor#ffffff
titleColor#ffffff
titleBGColor#009EE0
titleAuthorization Objects

List of authorization objects mandatory for the application.

Authorization objectExplanation


DataFlow

Overview

Image Added

https://drive.google.com/file/d/1Am47Dk54BTT-vbQCe0vPnYNwAdBC8ORTrIfHv8Kz7Ao/view


Technical Rules on Workbench

This flow, based on CO PM standard datasources, completes commitments and actual costs key figures in the Project Costs Reporting. 

The assignment of these costs on WBS elements is done in BW.Dataflow:

Image Removed

https://drive.google.com/open?id=1WBod4apHIioL3iN8NzoFPpwSnSDOok4uR0MRib-9KRQ


WBS element determination / split (R1 & R4):

...

There is no split of PM order costs to WBS Element. We look for the WBS Element attribute in the PM order Master Data and all the costs on the PM order are assigned to this WBSE.
 
In Actual dataflow:
TRSF : DPPMCS01-> DBFICS03 (Solvay) & TRSF : ODS_PM01 -> DBFICS01 (Rhodia)

...

/!\ Do not collect 0AMOUNT from DBFICS03, as the amount is copied in each entry of the DSO, meaning the totals are usually duplicated (or more) compared to the actual value. 0AMOUNT is collected in DBFICS03 only for calculation of K_SETTLMT. Same issue with 0QUANTITY for K_INV_QTY.
 
Acetow (not loaded anymore):

...

Partner object mapping (R3):

Partner objects are mapped from a generic field "Partner IO val" (RSPAROBVAL) to specific infoobjects "Partner Costs center" (0PART_CCTR), "Partner WBSE" (C_PARTWBS), "Partner Order" (C_PARTORD),... according to the partner type (RSPOBART). It is done using the Function Module 'CO001_BIW_PARTNER_DECODE' as provided by the SAP Business Content.


Datasources customer exit:

  • 0PM_OM_OPA_2: retrieve additional data from tables EKKO, EKPO, COEP and AUFM. The quantity "SMEG" is redetermined with the quantity of the goods movements (table AUFM).
  • 0PM_OM_OPA_3: retrieve additional data from tables EKKO, EKPO, EBAN.
    It also determines an adjusted net due date (zznetdt) that corresponds to the delivery day (or the current date if the delivery date < current date) to which is added the terms of payment.

Reporting


Dependencies with other applications

Plant Maintenance: Actual and commitments costs propagation DSO are sources for PM application flow (Solvay and Rhodia).

Data loadings

Info providers and objects loaded

...

Process Chain
Code
Type
Frequency
Comments
Plant MaintenanceRSP_PMSLAVE
  • launched by RSP_DAILY
  • DailySunday night to thursday night, 2:30am
  • Daily (not saturday) at 1:30 am) 
  • Whole chain lasts around 1 hour30 mins
  • RCS
  • From datasources to cubes
  • PM Actual costs, Commitments and orders distribution rules (but also other PM flows: notifications, operations...)
Solvay : Plant Maintenance RSP_PM_SOLVAY_SLAVE
  • launched by RSP_DAILY
  • Daily
  • Monday to Friday, 2:00am
  • Whole chain lasts around 1 hour
  • Solvay legacy system
  • From datasources to cubes
  • PM Actual costs
  • Commitments and orders distribution rules
Acetow : Plant MaintenanceRSP_PM_ACETOWSLAVE
  • launched by RSP_DAILY
  • Daily
  • Sunday night to thursday night, at 2:00am
  • Whole chain lasts around 5 minutes1 minute
  • Acetow legacy system
  • From datasources to cubes
  • PM Actual costs, Commitments

Loading frequency

Actual Costs = daily Delta

Commitments = RCS/Acetow: daily Full with deletion, Solvay: weekly Full with deletion

Distribution rules = RCS: daily, Solvay: weekly.

Average performance

...

Key Figure

...

Estimation
  • Decomissioned, load 0 lines.

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

...

Daily RCS = 1h

Daily non RCS = 30min

...

Record Keeping

...