Order Promising 

Technical Document - Order Promising


Order Changes 

Access Management

Role Code

Role Description

Explanation

ZBI_RCS_SD_A01

Application role for Global Sales project / SD data / Orderbook

Role for the application

ZR_RCS_CA_M49

SD - Sales and Distribution

Role menu for the application

List of authorization objects mandatory for the application.

Authorization object

Explanation

CPFCTR1_2

GBU

C_COMPCDE

Legal company

C_SAL_OF

Sales office

WARNING: For the PO part the notion of sales offices doesn't exist. The restriction in sales offices will not be considered for the reports PO and PO+SO.

Data flow 

Overview

The objective of the is to track the changes in the SAP tables: VBAK(Sales Document: Header Data), VBAP(Sales Document: Item Data), VBEP(Sales Document: Schedule Line Data), VBKD(Sales Document: Business Data), VBPA(Sales Document: Partner).

The data flow is based on the LSA method. The data visualization is done on the multiproviders MVSDCH01(SD - Sales Order Modifications (Global)) .

Core Rules 

An example of changes done on 23.10.2023 for order:3445278/10.

Reporting

Core queries

The core queries are based on the multiproviders MVSDCH01:

Workbook


Query


Order ChangesBW_WBK_MVSDCH01_0020BW - Follow-up modification on SO (Core Query)BW_QRY_MVSDCH01_0020

Data loadings

Main Process ChainFinal Info ProviderFrequencyStart TimeDuration
PC_SD_CHANGE_DOC

CRSDCH05, 15

Daily~9:00am CET~1h

Data Quality Controls

Data comes from SAP system. To compare data between BW and sources systems, check propagation layers.

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 criticality, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD)>