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

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.

Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016