3676392 - Contract leakage data discrepancy in Manage Purchase Contracts app -SAP S/4HANA Cloud Public Edition

1. When checking contract leakage on a purchase contract using the Manage Purchase Contracts app, no data is displayed.
2. Leakage data is visible in the Contract Leakage App  - Purchasing Spend without Contract Reference app for the same purchase contract.

SAP S/4HANA Cloud Public Edition

1. Open the Manage Purchase Contracts app.
2. Enter the purchase contract number in the selection field .
3. Navigate to the Contract Consumption and Leakage section; no data is displayed.
4. Open the Contract Leakage - Purchasing Spend without Contract Reference app.
5. Enter the same purchase contract number in the selection field.
6. Leakage data is displayed for the purchase contract.

Standard system behavior

The Manage Purchase Contracts app displays contract leakage and consumption information to help purchasers monitor contract utilization and identify purchasing spend that bypasses existing contracts.

Contract leakage will be displayed in Manage Purchase Contracts app orders when follow on Purchase Order will be created without contract references despite available contracts

The leakage percentage is calculated as: (Leakage amount / Sum of purchase order amounts) × 100 

Contract leakage will be displayed  in consumption and leakage tab for quantity contract only  for PO created without referencing the contract.

Contract Consumption will be displayed in Manage Purchase Contracts app orders when follow on Purchase Order will be created with contract references 

Basic Formula: (Released Amount / Target Amount) × 100

 Contract Leakage app can be used to find out the amount of purchases made without considering existing contracts. It can determine whether this amount has increased or decreased over time, and which purchasers, suppliers, supplying plants, product categories, or items are responsible for the contract leakage.

• Refer to: Manage Purchase Contracts app documentation
• Refer to: SAP Note 2319491 - How to clean up the cache after applying changes that affect SAP Fiori apps

contract leakage, manage purchase contracts, consumption and leakage, follow-on documents, purchase orders, sap s/4hana cloud public edition, contract leakage app, purchasing spend without contract reference, business catalog, BR_PURCHASER, SAPUI5 update, cache cleanup, discrepancy, data model. , KBA , MM-FIO-PUR-SQ-CON-CL , Fiori UI for Manage Purchase Contracts (Public Cloud) , Problem