General presentation

Objective of the application

The objective of the application is to extract from SAP Vault source system Work center data and calculate capacity at week level & month level.

Then these data are used for the application BW - DPS - Forecast Vs Booking / Component and in the query BW-DP-Labor Planning Tool Interface (Core query).


Tool Leader: Lei Shen

IT leader of the application: Lei Shen (PP), Craig Wanamaker (BW)

Name of project: Solstice

PMO Project: 8612 Solstice AERO

Reporting Coordinator: Lei Shen

Usage information

Number of users: tbd

Critical period: none

Geographical perimeter: worldwide

InfoArea:

History

This application is linked to the Solstice global project and this specific need was named "DEV47- Other MiniBW request for planning team".

MiniBW (CPX) dedicated platform was created for Aero Requirements about Solstice project.



Roles & Access

Roles and 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 autorisation objects mandatory for the application.

Authorization objectExplanation
  
  
  

Dataflow overview

Reporting documentation drive folder

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

Dataflow overview

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Specification Document

Sheet "Dim_Resource" & "Dim_ProdVersion" :

Available capacity calculation

There are 2 ADSO following the calculation level :

  • Capacity Planning - Weekly (ABPPCP02)
  • Capacity Planning - Monthly (ABPPCP03)

Both ADSO are loaded by the same datasource DTS_DPS_ZWPPT042 based on SAP (Vault) table ZWPPT042.

Calculation is done in end routine of each transformation between ADSO and datasource by reading ADSO APPPCP01 (Interval of Available Capacity) with function module Z_WBW_READ_KAZY_2 (duplication and adaptation of existing one on WBP BW system).

There are 2 key figures calculated :

  • 0STANDCAP : Available capacity (constraint) => Available capacity of work center in Period - Shut Down
  • K_CAPUNCO : Available capacity (unconstraint) => Available capacity of work center in Period

This ADSO (APPPCP01) is loaded by the datasource DTS_DPS_KAZY based on function module  Z_WBW_DTS_DPS_KAZY (duplication and adaptation of existing one on WP1 SAP system).

The capacity loaded in APPPCP01 is reported in secondes for a defined weekday, then it is calculated in hours in ABPPCP02 (by week) & ABPPCP03 (by month).


Dependencies with other applications

Capacity data are used in application BW - DPS - Forecast Vs Booking / Component.

Data loadings

Info providers and objects loaded

Master Data

  • Work Center Master Data is loaded by following process chain : 
    • Attributes : PC_GLOBAL_ATTR_02

    • Texts : PC_GLOBAL_TEXT_02

  • Production Version Master Data :
    • Attributes : PC_PP_05
    • Texts : PC_PP_06


  • Capacity Planning Group Master Data :
    • Texts : PC_PP_06


All these previous process chain are part of global RSP_DAILY_GLOBAL :



Transactionnal Data

There are 2 process chain :

  • Propagation Layer : PC_PP_02
  • Business Layer : PC_PP_03


They are part of process chain PC_PP_04 :




PC_PP_04 is part of global RSP_DAILY :



Loading frequency

Daily loading

Average performance

 

Key FigureEstimation
~ Average Process Chain Runtime 
~ Average nb of rows loaded per load 
~ Total nb of rows loaded (if full) 
~ Average Runtime for 10k lines 

Record Keeping

Reporting

Queries End User Documentation

 

Main queries

There are 2 queries :

  1. BW_QRY_CPPPCP02_0001 (BW - Labor Planning Tool (Core Query) ) : This query is based on composite provider CPPPCP02 (Capacity Planning - Weekly).
    More details here : BW-DP-Labor Planning Tool Interface (Core query)

  2. BW_QRY_CPPPCP03_0001 (Capacity Planning Monthly data)  based on composite provider CPPPCP03 (Capacity Planning - Monthly).
    This query was used for testing data coming from SAP source system but it is not used and accessible by key users.

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution

 

  • No labels