Order Processing > Order Promising

General Description

This indicator explores the time taken to confirm in the system an order to the customer from the order creation and the confirmation date given by the Back Office & Planners (Plant). The targeted KPI is 48 hrs.

Scope:

- 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".
- Filter on Sales Order Types, same as OTIF scope

Business day: We take into account server location: Belgian holidays excluded.

Process of order promissing:

Promising Split: Each order line is categorized in 5 possible Confirmation Status. We are supposed to confirm and order line within 2 business days. In this case, we are good, otherwise, we failed.

Good < 2 days	Order line was confirmed =< 2 business days
Failed 3-9 days	Order line confirmation date is between 3 and 9 business days
Failed 10-30 days	Order line confirmation date is between 10 and 30 business days
Failed > 30 days	Order line confirmation date is more than 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 (supply issue) For PF1: there is no common process, therefore this category is not defined for PF1 GBUs

Key figures	Calculation
Order Promising ratio	# of GOOD confirmed <= 2 business day —————————————————————— # total orders lines Confirmed within 2 business days
Order Promising Cycle Time	Number of business days between Order line creation date and the first ATP confirmation date In case of credit block the KPI measures: Number of business days between the first credit release and the 1st ATP confirmation date If the order hasn’t been confirmed yet we calculate number of business days with today’s date When we don’t have the order confirmation date and the command has been issued then we consider that the order was immediatly confirmed. Fisrt confirmation date = Orderline confirmation date
Failed Orders	Total of orders with a Failed Confirmation Status
# of Confirmations	Count how many times the order has been confirmed in the change log (after quantity or requested date change) If the order line was confirmed immediately and there is no confirmation in the change log, then count as 1 confirmation and use order line creation date in cycle time.
Stability	Stable Y = 1 confirmation Stable N = more than 1 confirmation No GI date = if the order has no GI date, it is considered not possible to calculate the KPI
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)
First Confirmation Date	For WP1: First Confirmed quantity date from Change Log. If there is no change in the quantity in the change log and the order line has been delivered, BW takes the order line creation date assuming that the user was confirmed immediately. For PF1: BW uses a dedicated field ZZERDAT "1st committed delivery date"

Target Users

Supply Chain Managers
Supply Chain Operational
Supply Chain Excellence
Logistics
Customer Service
Account Managers

Authorization & Rights

All the accesses must be validated by:

Supply Chain Excellence

Click here for the Access form to get access to the Global Supply Chain Dashboard.

Technical Documentation

Source:

CORE - BW_QRY_CPSDCH01_0001

QlikView - QV_BW_QRY_CPSDCH01_0001

Update: Daily

Global Overview of Dimensions:

		Order Promising
Global Filters	Date	[C_ITM_SD__C_CDATE2] Order line creation date
	GBU	[CPFCTR1_2] BFC GBU
	Group of Activity	C_SUBACT2__CPFCTR2_2 - BFC Group of activities
	Sub-Activity	C_SUBACT2__C_MAGNITU - BFC Activity 1
	Company	[C_COMPCDE] Company_code
	Zone	[C_PLANT] Plant\Attributes\[C_GZONE] Geographie/Zone
	Country	[C_PLANT] Plant\Attributes\[0COUNTRY] Country key
	Plant	[C_PLANT] Plant
	Zone	[C_SHIPTID] Ship-to party\Attributes\[C_GZONE] Geographie/Zone
	Country	[C_SHIPTID] Ship-to party\Attributes\[0COUNTRY] Country key
	Corporate Group	[C_SHIPTID] Ship-to party\Attributes\[C_CORPGR] CRM Customer Corp. Group (PRS)
	Ship Destination	[C_SHIPTID] Ship-to
	Product Hierarchy	[C_MATNR2] Material\Attributes\[0PROD_HIER] Product Hierarchy
	Product	[C_MATNR2] Material\Attributes\[C_PROD] Coimmercial Product / Material Group
	Bulk/Packed	[C_MATNR2] Material\Attributes\[C_BULKPAC] Transportation Group
	Packaging Type	[C_MATNR2] Material\Attributes\[C_PACKAG] Packaging type
	Transport Mode	[C_SHIPCD2__C_TR_MODE] Transportation mode
Specific Filters
	Sales Office	[C_SAL_OFF] Sales Office
	Ship Destination Zone	[C_SHIPTID__C_GZONE] Geographie/Zone
	Ship Destination	[C_SHIPTID] Ship-to party
	Product	[C_MATNR2__C_PROD] Commercial Product / Material Group

Page tree

Order Processing > Order Promising

Joëlle Hilaire

Diogo Paiva

EMEA: Emma Glasson

NAM/LAM: Karina Tsuji

APAC: Lilian Cheong

This indicator explores the time taken to confirm in the system an order to the customer from the order creation and the confirmation date given by the Back Office & Planners (Plant). The targeted KPI is 48 hrs.

Scope:

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".

Filter on Sales Order Types, same as OTIF scope

Business day: We take into account server location: Belgian holidays excluded.

Process of order promissing:

Promising Split: Each order line is categorized in 5 possible Confirmation Status. We are supposed to confirm and order line within 2 business days. In this case, we are good, otherwise, we failed.

Good < 2 days

Order line was confirmed =< 2 business days

Failed 3-9 days

Order line confirmation date is between 3 and 9 business days

Failed 10-30 days

Order line confirmation date is between 10 and 30 business days

Failed > 30 days

Order line confirmation date is more than 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 (supply issue)

For PF1: there is no common process, therefore this category is not defined for PF1 GBUs

Order Promising ratio

# of GOOD confirmed <= 2 business day——————————————————————# total orders lines

Confirmed within 2 business days

Order Promising Cycle Time

Number of business days between Order line creation date and the first ATP confirmation date

In case of credit block the KPI measures: Number of business days between the first credit release and the 1st ATP confirmation date

If the order hasn’t been confirmed yet we calculate number of business days with today’s date

When we don’t have the order confirmation date and the command has been issued then we consider that the order was immediatly confirmed. Fisrt confirmation date = Orderline confirmation date

Failed Orders

Total of orders with a Failed Confirmation Status

# of Confirmations

Count how many times the order has been confirmed in the change log (after quantity or requested date change)

If the order line was confirmed immediately and there is no confirmation in the change log, then count as 1 confirmation and use order line creation date in cycle time.

Stability

Stable Y = 1 confirmation

Stable N = more than 1 confirmation

No GI date = if the order has no GI date, it is considered not possible to calculate the KPI

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)

First Confirmation Date

For WP1: First Confirmed quantity date from Change Log. If there is no change in the quantity in the change log and the order line has been delivered, BW takes the order line creation date assuming that the user was confirmed immediately.

For PF1: BW uses a dedicated field ZZERDAT "1st committed delivery date"

Supply Chain Managers

Supply Chain Operational

Supply Chain Excellence

Logistics

Customer Service

Account Managers

All the accesses must be validated by:

Supply Chain Excellence

Click here for the Access form to get access to the Global Supply Chain Dashboard.

Source:

CORE - BW_QRY_CPSDCH01_0001

QlikView - QV_BW_QRY_CPSDCH01_0001

Update: Daily

Global Overview of Dimensions:

Global Filters

Date

[C_ITM_SD__C_CDATE2] Order line creation date

GBU

[CPFCTR1_2] BFC GBU

Group of Activity

C_SUBACT2__CPFCTR2_2 - BFC Group of activities

Sub-Activity

C_SUBACT2__C_MAGNITU - BFC Activity 1

Company

[C_COMPCDE] Company_code

Zone

[C_PLANT] Plant\Attributes\[C_GZONE] Geographie/Zone

Country

[C_PLANT] Plant\Attributes\[0COUNTRY] Country key

Plant

[C_PLANT] Plant

Zone

# of GOOD confirmed <= 2 business day
——————————————————————
# total orders lines