The order changes reports in the BW is part of the global sales folder. The primary objective of the reports is to oversee the confirmation time of an order in SAP, providing valuable insights into the efficiency of order processing. Additionally, these reports are designed to monitor any modifications that happened after the initial confirmation date, offering a comprehensive view of the order's lifecycle and enabling proactive management of changes in the SAP system.
Describe the key User profiles that exist for the application.
General role/Viewer role:
Approver role:
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 18.12.2023 | Azadeh Nasiri | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
2.0 Business Process
Capture the business process that the application supports . This can be describe through a process diagram or a business capability model
3.0 Application Feature Overview
Information about the existent Workbooks and the respective BW queries.
| Reports | Technical Name |
|---|---|
BW- Order promising | BW_WBK_CPSDCH01_0001 |
Order changes | BW_WBK_CPSDCH01_0020 |
4.0 Functional Specification
4.1 General Data/Calculations
There are indicators in the report that explores the time taken to confirm an order in SAP by comparing the order line creation date and the confirmation date. The target is to be less than 48 hrs (=< 2 business days).
Furthermore, the report assesses the 'Stability' factor, determining whether the first confirmation date has been altered subsequently. If so, the report provides insights into the frequency and extent of these changes, shedding light on the order's stability over time.
4.2 Process Detail
Scope :
- The scope has been aligned with the OTIF scope. See scope HERE
- Exclusion of material types services and packaging (i.e. units in KWH): PF1/Z703 WP1/ZDIE WP1/ZVER WP1/ZUNB
- Consolidation Method ≠ Sold (entities)
- Deleted order lines are excluded
- Order lines with a “Reason for rejection” have been excluded, except for the WP1 reason "98 - Incompleted delivery, tb closed-not OTIF".
Reference Date : for the KPI % Order Promising and the Cycle Time the reference date is Order Line Creation date. Order lines are taken into consideration as soon as they are entered in the system. (data load delay of 1 day, night batch)
Cycle Time :
- Order line creation date -> 1st ATP confirmation date
- In case of credit block the KPI measures: Cycle Time between FIRST credit release > 1st ATP confirmation date
- If the order hasn’t been confirmed yet we calculate the cycle time with Today’s date
- Measured in business days (of server location: Belgian holidays excluded)
Scenarios/ Rules
Order still blocked? | First credit release date | 1st confirmed ATP date | Cycle Time | |
Case 1 | no | no | yes | Order line creation -> 1st confirmed |
Case 2 | no | no | no | Order line creation -> today |
Case 3 | no | yes | yes | First credit release -> 1st confirmed |
Case 4 | no | yes | no | First credit release -> today |
Case 5 | no | yes | yes (but prior to credit release date) | Order line creation -> 1st confirmed |
Case 6 | yes | - | yes | Order line creation -> 1st confirmed |
Case 7 | yes | - | no | Order line creation -> today |
Case 8 | no | yes (but prior to order line creation date) | yes | Idem case 1 |
Case 9 | no | yes (but prior to order line creation date) | no | Idem case 2 |
1st ATP confirmation date:
- First Confirmed quantity date from Change Log in PF1
- If there is no quantity change in the change log and the order line has been delivered, BW takes the order line creation date assuming that the order was confirmed immediately
- in case the order line was created, deleted, recreated, we consider the last order line creation date
- If a schedule line comes from a value to zero, we assume the order line was confirmed immediately (1st conf. date = order line creation date)
- If a 1st confirmation date is inferior to the order line creation date then we read the change log and take the next quantity confirmed date as the 1st confirmation date.
- For WP1 BW uses a dedicated field ZZERDAT "1st committed delivery date" (Order line - Additional Data B)
4.2.1. Report/Process Definition
Promising Split : Each order line is categorized in 5 possible Confirmation Status
Details of Confirmation Status:
- GOOD : confirmed =< 2 business days
- FAILED 3-9 business days
- FAILED 10-30 business days
- FAILED > 30 business days
- FAILED with ALLOCATION :
- For WP1: if order line has failed to be confirmed within 2 business days and has ever had ZPEN flag on order line level
- For PF1: there is no common process, therefore this category is not defined for PF1 GBUs
KPI Order Promising percentage : # of GOOD confirmed < 2 business days / # total orders lines
Confirmed in 2 business days : KPI is based on 1st ATP confirmation (whether the order line has been updated or not)
# of Confirmations :
- Count the # of distinct dates* the order line has been confirmed in the change log (after confirmed quantity or schedule line date change)
*even if the change log shows several changes per day, we can count only 1 confirmation per day
- A change that goes from value to zero is considered as an instability, not a cancellation (+1)
- If there is no change in the confirmed quantity or schedule line date in the change log and the order line has been delivered, BW counts as 1 confirmation and assuming that the order line was confirmed immediately. (WP1) BW uses order line creation date in cycle time.
Stability (Stable confirmation) :
Calculation: Based on KPI “# of Confirmations”, Stable Y = 1 confirmation and Stable N > 1 confirmation
If the order has no GI date, it is considered as not possible to calculate the KPI.
5.0 Non-functional Descriptions
Please populate the relevant section and delete those that are not applicable.