3802713 - Unable to find standard apps to calculate supplier volume rebates and create supplier debit notes in SAP S/4HANA Cloud Public Edition

• Unable to find any standard tile, report, or configuration to automatically calculate volume-based or period-based supplier discounts and generate the corresponding supplier debit note.
• Requires the ability to track cumulative purchase quantity/value against agreed volume discount slabs within a defined period.
• Requires calculation of the eligible discount amount for a specific period and issuance of a supplier debit note accordingly.
• No error messages or error codes are provided in the case.

• SAP S/4HANA Cloud Public Edition
• Tax (Public Cloud)

1. In SAP S/4HANA Cloud Public Edition, search for standard apps/tiles/reports to track cumulative purchase quantity/value against volume or period-based supplier discounts and to generate a supplier debit note.
2. Observe that no suitable standard tiles, reports, or configurations are found.

• The purchasing rebate processing capability is not activated in the system, or the user role lacks access to the relevant apps; when this capability is inactive, no related tiles or settings are visible.
• The supplier “debit note” is realized as a settlement document that posts as a supplier credit memo.
• If rebates are maintained in legacy purchasing agreements (not as condition contracts), the system does not track them.
• The system only accumulates purchases posted after the condition contract is created; purchases from earlier in the period are not counted automatically.

1. Activate the Purchasing Rebate Processing capability in SAP S/4HANA Cloud Public Edition.
2. Assign the required business catalogs/roles to access these apps: Manage Condition Contracts – Supplier Rebates, Monitor Condition Contracts – Supplier Rebates, Update Accruals – Supplier Rebates, and Settle Condition Contracts – Supplier Rebates.
3. Create a supplier rebate condition contract defining the validity period and the volume/value discount slabs (use condition contracts, not legacy purchasing agreements).
4. Post relevant business transactions within the validity period; the system will accrue and track quantities/values for the contract.
5. Run Update Accruals – Supplier Rebates to keep accruals current for the period.
6. Run Settle Condition Contracts – Supplier Rebates to create the settlement document; this posts a supplier credit memo (equivalent to a debit note from the buyer’s perspective).
7. Review cutover periods: only transactions after contract creation are considered automatically; handle earlier-in-period purchases per standard processing as needed.
8. If settlement run issues occur, validate configuration for tax code and profit center relevance before rerunning.

• Refer to: Purchasing Rebate Management
• Refer to: KBA 3130828 (condition contract settlement tax-code error)
• Refer to: KBA 3130898 (condition contract settlement profit-center error)

purchasing rebate processing, supplier rebates, condition contract, volume-based rebate, period-based discount, debit note, settlement document, supplier credit memo, manage condition contracts, monitor condition contracts, update accruals, settle condition contracts, automatic calculation, goods receipt accumulation, s/4hana cloud public edition , KBA , MM-IV-INT-TAX-2CL , Tax (Public Cloud) , Problem