cdb tech concept2

8/14/2019 CDB Tech Concept2

http://slidepdf.com/reader/full/cdb-tech-concept2 1/14

AlstomPowerMax

Internal use only

189028527.doc.ms_officeVersion: 1.0Status: In WorkDate: 11/17/2013

of 14

Alstom Power

PowerMax Program

Technical documentation BW

CDB

Reports Interfaces Conversions Enhancements Forms

Version: 2.0

Status: In WorkIn Work Ready for Review Ready for Approval Approved



AlstomPowerMax

Internal use only


of 14

General Attributes

Document Title Technical description–

CDBDescription

Application Area Teranga-CDB

Requestor

Functional design docu-

ment

Date of approval

Date to production November 2009

Document History

Version Author / Department Date / Type Changes made / Remarks1 Stephan Dold / BW November 30, 2009 First draft

2 Petra Huber February 4, 2010 Update because of design changes

Don’t forget to update the footer with the version and date information!



AlstomPowerMax

Internal use only


of 14

Table of Content

1 Detailed technical documentation ............................................................................................................. 4

1.1 Technical realization .................................................................................................................................. 4

1.1.1 Data extraction ............................................................................................................................... 4

Generic extractors ............................................................................................................... Error! Bookmark not defined.

1.1.2 Design of data flow .......................................................................................................................... 5

1.1.3 Business Planning and Simulation (BPS) ............................................................................................ 6

Variables: .......................................................................................................... ............................................................... .. 6

Characteristic Relationship ............................................................................. ............................................................... .. 6

Layouts 7

Planning Functions ........................................................... ................................................................. ................................ 8

1.1.4 Newly built objects for Administration................................................................................................ 9

1.1.5 Transformations ............................................................................................................................ 9

1.1.6 Cubes .............................................................................................Error ! Bookm ark not def ined.

1.1.7 Output .......................................................................................................................................... 12

1.1.8 Data loading procedure (Delta/Full) ................................................................................................. 13

1.2 Operations.............................................................................................................................................. 14

1.2.1 Process chains ............................................................................................................................... 14

1.2.2 Distribution ................................................................................................................................... 14

1.2.3 Authorization ............................................................................................................................... 14



AlstomPowerMax

Internal use only


of 14

Design of data flow

FBS0049_FBS_CDB002



AlstomPowerMax

Internal use only


of 14

1.1.2 Business Planning and Simulation (BPS)

Technical Objects:Multi Planning Area: PA000003 Multi CDBSince in the first description actual data loaded from ECC6 seemed also to be part of the layout, a Multi-planning area was created, to fulfill this requirement.

At the moment this is not the case anymore, nevertheless, the needed levels, layouts and planning functionsare based on the Multi Planning Area.

Variables:

Description Technical Name Logic

Company code AUTH PA000002 Manual Entry, restricted to authorized values

CP Number PV000001 Manual Entry

Currency PV000003 Manual Entry

Profit Center AUTH PA000001 Manual Entry, restricted to authorized valuesReporting Period PV000006 User Exit; Filled depending on InfoObject

IOREPPER

Fiscal Year PV000007 User Exit; Filled depending on InfoObjectIOREPPER

Project Definition PV000009 Manual Entry

Reporting Period - Period PV000015 User Exit; Filled depending on InfoObjectIOREPPER

Characteristic Relationship

The characteristic relationship is defined behind Planning Area PA000001 CDB Plan

Step1: Deriving logging Information and Sender Reporting UnitSource:0PROFIT_CTR Profit Center



AlstomPowerMax

Internal use only


of 14

IOREPPER Reporting Period

Target:0CREATEDON Created on0CREA_TIME Time0USERNAME User Name, Person who entered data

IOINSIND Insertion indicator = „M‟ meaning manual entry, to be evaluated e.g. in Reporting IOMOD SAP module of origin = „BPS‟ IORUNIT Reporting Unit, derived by Profit Center Masterdata

Function Module: ZPA000001_DERIVE_CHAS

Step2: Deriving Posting Period Information from the Reporting Period

Source:IOREPPER Reporting Period

Target:0FISCPER Fiscal year/period0FISCPER3 Posting period0FISCYEAR Fiscal year

Function Module: ZPA000001_DERIVE_TIME

Step3:

Source:

Project Definition

Target:CP Number

Function Module: ZPA000001_DERIVE_CPNR

Step4:Posting periodFiscal yearFiscal year/period

Function Module: ZPA000001_DERIVE_FISCPER

Layouts

Layouts on contract/project definition Level CAPT

CAPW-000 Partnerized PL000004CAPW-000 not Partnerized PL000005CAPW-001 Partnerized PL000006CAPW-001 not Partnerized PL000007CAPW-001 not Partnerized Rest PL000008CAPW-103 not Partnerized PL000009CAPW-108 not Partnerized PL000010



AlstomPowerMax

Internal use only


of 14

Layouts on contract/project definition Level CFPT

CFPW-102 not Partnerized FINAL PL000002CFPW-102TP not Partnerized FINAL PL000003

Layouts on Reporting Unit Level

CAPW-108 not Partnerized PL000001

Planning Functions

On Contract Level:PFUN Combination_Check_CP_PC

For authorization purposes, to reuse the actual available concept and roles, the Profit Center and CompanyCode is required, entering data into a layout. To prevent a contradiction between Profit Center, Company Codecombination and the according Project Definition in ECC6, representing the CP#, the entry is checked againstthe masterdata of 0PROJECT. If there is a contradiction, a message occurs and the values for this wrongcombinations are deleted (reposted).Remark: the outbound interface to Teranga has to aggregate those values and exclude then records with val-ue=0.Function Module: ZPA000001_PLFUNC_CHECKCP_VS_PC

Other Contract or Reporting Unit LevelPFUN Check PC vs Company Code is checking the combination between entered Profit Center and CompanyCode. Wrong values will be reposted automatically

Function Module: ZPA000001_PLFUNC_CHECKC_PC_CC

Global Planning Sequences

PGSEQ001To be able to run the planning function PFUN after saving in the planning folder PF000002, there is a need tohave the global planning sequence PGSEQ001PGSEQ002To be able to run the planning function PFUN after saving in the planning folder PF000006, there is a need tohave the global planning sequence PGSEQ002PGSEQ003To be able to run the planning function PFUN after saving in the planning folder PF000004, there is a need to

have the global planning sequence PGSEQ003

Planning Folders

CDB CAPT Contract Level PF000002CDB-Reporting Unit Level PF000004CDB CFPT Contract Level new PF000006



AlstomPowerMax

Internal use only


of 14

Integration in Teranga

Call Planning Folders from Dialog (Report Painter Screen, ABAP: ZTERANGA_MAIN)

Steps:1. Call SE38, ABAP UPB_PM_START and create Variant PF000002 for example

The variant name should represent the planning folder to be called

2. Enter in the coding of the PAI Modul:Submit UPB_PM_START using selection-set 'PF000002' and return.For the status representing the relevant Screen Painter Button

1.1.3 Newly built objects for Administration

Object Name Technical name

Info Object Reporting Period IOREPPER

The InfoObject contains the actual Period, reporting and planning is done for. It has to be maintained manual-ly. The system is reading the first record having Active CDB Flag = X. Don‟t forget the activation after changing

the period.

Object Name Technical name

Info Object Contract Database Rules IOCDBRULE

The InfoObject contains the rules, for CASH X selections to Teranga accounts/Flows. Since different selec-tions are handled by different DTP‟s, the technical name of the DTP has to be put into a record, being as-signed to the according Teranga accounts/Flows.

1.1.4 Transformations

Cash X

( 1 )Cube

PDFCX03A: Cash X

▼ ( 2 )Transformation

CUBE PCFCX0002 -> CUBE PCCDB0002

▼



AlstomPowerMax

Internal use only


of 14

( 3 )Cube

PCCDB0002Contract Database Reporting Cash X

Step2Enhancement of Reporting Period reading InfoObject IOREPPEREnhancement of Teranga Code and Flow according to Rules in InfoObject IOCDBRULEEnhancement of Partner Reporting Unit reading Masterdata of 0Customer, 0Vendor

COPA

( 1 )DataSource

1_CO_PA_TERANGA


RSDS 1_CO_PA_TERANGA DE1CLNT110 ->

▼ ( 3 )DSO

PDCOPA01SoT COPA

▼

( 2 )

Transformation

RSDS 1_CO_PA_TERANGA DE1CLNT110 ->

ODSO PDCOPA01

▼ ( 3 )DSO

PDCOPA01SoT COPA


ODSO PDCOPA01 -> ODSO PDCOPA02

▼ ( 4 )DSO

PDCOPA02Copa matches Teranga


ODSO PDCOPA02 -> CUBE PCCDB0001

▼ ( 6 )Cube

PCCDB0001Contract Database Reporting COPA



AlstomPowerMax

Internal use only


of 14

1.1.5 Relevant MasterData

0Project -> CP# from ECC6 table PROJ

0Customer-> IORUNIT

0Vendor -> IORUNIT

1.1.6 Output

.



AlstomPowerMax

Internal use only


of 14

Report XXX

Most Current Data variable to be used when data from BPS should be shown and the Cube is still open forplanning

Key figures

CSV files:

Z_EXTRACT_CDB_FINAL is an ABAP, that is reading data of the relevant Multiprovider PMCDB0001. It willcontain the final selection criteria to create the files per-Organization (Reporting Unit)

-Package (CAPT, CFPT)-Reporting Period

Examples how to use the right functions for data extraction on DB1Extraction from the Multiprovider: Z_EXTRACT_CDBExtraction from the BPS Cube, taking care of yellow requests: ZTEST_BPS_EXTRACTThe final program will be a mixture of both, calling each procedure several times to collect the right data, writ-ing it into a file.Not to double the values one either selects the 3 dataproviders, excluding the BPS Cube) while selecting dataof the Multicube and then runs the BPS selection, or an extra Multicube will be created, not containing the BPScube and then the two selections are started on the new Multiprovider and on the BPS Cube.

Prerequsite:The planning Cube PCCDB0015 has to be switched from “planning” to “loading” that will automatically closethe open request and switches the status to green, so it will be read by the ABAP.

Structure:

Header CSV file Info Object Source BW Source ECC

….

1.1.7 Data loading procedure (Delta/Full)

The plan is to have in the last staging level to the Cubes full loads, so that all the four Cubes below the Mul-ticube contain all relevant data in one Reporting Period Slice.When, e.g. for performance reasons, this procedure will be changed, it will be necessary to have multiple se-lections in ABAP Z_Extract_CDB reading either the relevant reporting period or the complete cube.



AlstomPowerMax

Internal use only


of 14

1.2 Operations

1.2.1 Process chains

.

1.2.2 Distribution

.

1.2.3 Authorization

Authorization objects

cdb tech concept2

Documents