You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

General presentation

Objective of the application

The infoprovider has all the data related to the Billing items. 

Tool Leader + IT leader of the application: Craig Wanamaker

Usage information

Users use this information Worldwide where  the Billing items are used in the queries

History

The Condition record number(CONDREC) from  KONV , Reference Document number (XBLNR) from VBRK table  and Preferential flag(PREFE) from VBRP  is extracted to the C_BILLITM through 

ZZ_VBRK_KONV Data source for both the PF1 and WP1 flows. 

Dataflow overview

The characteristics  C_CONDREC, C_PREFE1 and C_XBLNR are added to the ADPSDSO47 (Billing and Conditions DSO) and mapped  as follows. 

These are mapped to the C_BILLITM through ADPSDSO47. 


Further more, there is another requirement for adding the condition type (C_CONDTYP) in the transformation between ADPSDSO47 and C_BILLITM .



Functional and Technical rules on Workbench + Reporting

Rules & Explanations

The Queries which were changed are 

BW_QRY_MVSDSO45_SD0005 -  The condition record number C_BILLITM__C_CONDREC is added as a characteristic

BW_QRY_MVSDSO45_SD0001.- The reference Document number C_BILLITM__C_XBLNR is added as a characteritstic

BW_QRY_MVSDSO53_0001 - The preferential flag C_BILLITM_C_PREFE1 is added as a characteristic. 

Dependencies with other applications

NA

Data loadings

Info providers and objects loaded

PC_GL_SALES_C_BILLITM

Loading frequency

Daily

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

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels