Fulfillment Using Confirmations (SAP Library

Fulfillment Using Confirmations

Technical name: 0CDS_C02_Q0002

Use

The query allows you to analyze how confirmed quantities were used to fulfill requested quantities, over a certain time period.

Free Characteristics

InfoObject	Description
0COMP_CODE	Company code
0PLANT	Plant
0SHIP_POINT	Shipping point
0SALES_GRP	Sales group
0DIVISION	Division
0SALESORG	Sales organization
0DISTR_CHAN	Distribution channel
0MATL_GROUP	Material group
0CUST_GROUP	Customer group
0DISTR_CHAN	Distribution channel

Variables Used

Variable	Description
0P_PER	Evaluation period Requirements and confirmed requirements with a delivery date that lies within the evaluation period are taken into account.
0I_MATER	Material
0I_CUSTO	Sold-to party

Exceptions

Exceptions, which have different priorities, are used in this query.

Defined Exceptions

Exception

Description

0F_LTOL2

Tolerated shortage confirmation

The system proposes a value of 0.9, meaning that a shortage confirmation of up to 10% below the customer requirement is tolerated.

0F_UTOL2

Tolerated surplus confirmation

The system proposes a value of 1.1, meaning that a surplus confirmation of up to 10% above the customer requirement is tolerated.

Example

You can use exceptions to quickly determine extraordinary deviations in the fulfillment of the requested quantities or confirmed quantities.

If you confirm too much or too little the system issues alerts.

Fulfillment of requested quantities using confirmed quantities in the case of the shortage confirmation

Requested Quantity	Confirmed Quantity	Priority/Alert Level of Deviation
Your customer requests 100 navigation systems from you within the evaluation period.	You confirm 99 navigation systems.	The result of the evaluation is the alert level (medium), because the confirmed quantity does not correspond to the customer’s requested quantity; however a deviation of 1% is still within the defined tolerance limit.
	You confirm 89 navigation systems.	The result of the evaluation is the alert level (bad), because the confirmed quantity is more than 10 % under the requested quantity.

Fulfillment of requested quantities using confirmed quantities in the case of the surplus confirmation

Requested Quantity	Confirmed Quantity	Priority/Alert Level of Deviation
Your customer requests 100 navigation systems from you within the evaluation period.	You confirm 105 navigation systems.	The result of the evaluation is the alert level (medium), because the confirmed quantity does not correspond to the customer’s requested quantity; however a deviation of only 5% is still below the defined tolerance limit.
	You confirm 125 navigation systems.	The result of the evaluation is the alert level (bad), because the confirmed quantity is 25% above the requested quantity, exceeding the tolerated 10%.

For more information about exceptions see Structure link Exception Reporting.

For more information about Alert Management and the universal worklist, see the SAP Library for SAP NetWeaver under Structure link Using Universal Worklist.

Rows

InfoObject	Description of the InfoObject (or restriction or calculation formulas)
0SOLD_TO	Sold-to party
0MATERIAL	Material
0CALDAY	Calendar day

Columns

InfoObject

Description of the InfoObject (or restriction or calculation formulas)

Relative surplus/shortage confirmation

Calculation:

0APO_ORCON (Original confirmed quantity)

= ¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾

0APO_ORREQ (Original requested quantity)

Absolute surplus/shortage confirmation

= 0APO_ORCON ‑ 0APO_ORREQ

(Original confirmed quantity minus original requested quantity)

Background documentation

Note that the columns can only contain cumulated values. The values are cumulated using the property Cumulated of the characteristic Calendar Day.

Example

You can find an example in the analysis scenario Sales Scheduling Agreement Processing.