SAP Knowledge Base Article - Public

3808410 - Price adjustment credit memo from SAP Ariba via 42K posts as standard credit memo instead of subsequent credit in SAP S/4HANA Cloud Public Edition

Symptom

  • An Invoice Price Adjustment created in SAP Ariba (SAP Business Network) and transmitted via the 42K integration is created in SAP S/4HANA as a standard Credit Memo rather than a Subsequent Credit.
  • During validation in SAP S/4HANA, only informational messages are displayed; no error message explains the behavior.
  • Reported error text: "Error Encountered When Processing a Price Adjustment Credit Memo from SAP Ariba to SAP S/4HANA After Invoice Posting."

Environment

  • Product: SAP S/4HANA Cloud Public Edition
  • Logistics Invoice Verification (Public Cloud)

Reproducing the Issue

  1. Create a material Purchase Order in SAP S/4HANA and approve it so that it is transmitted to SAP Business Network.
  2. In SAP Business Network, create an Order Confirmation for the PO.
  3. In SAP S/4HANA, post the Goods Receipt against the PO.
  4. In SAP Business Network, create and submit an invoice for the confirmed order.
  5. In SAP S/4HANA, post the received supplier invoice.
  6. In SAP Business Network, create a Line Item Credit Memo and select “Price Adjustment” as the credit memo type.
  7. Enter a price adjustment amount (for example, -0.50) and submit the document.
  8. In SAP S/4HANA, verify the posting; observe it is created as a standard Credit Memo instead of a Subsequent Credit.

Cause

  • The 42K integration between SAP Business Network and SAP S/4HANA does not support Subsequent Debit/Credit document types.
  • Consequently, a Line-Item Credit Memo flagged as a Price Adjustment is processed as a standard Credit Memo; no error is issued because this is a documented functional limitation.

Resolution

  1. Acknowledge that this is a current 42K integration limitation; it is not a defect in Logistics Invoice Verification.
  2. If a true Subsequent Credit posting is required, post it manually in SAP S/4HANA using the Create Supplier Invoice app (F0842A) after receiving the supplier document.
  3. Optionally evaluate an integration approach that supports subsequent debits/credits (for example, cXML-based), subject to project and architectural constraints.

See Also

Keywords

42K, subsequent credit, subsequent debit, price adjustment, line-item credit memo, standard credit memo, SAP Business Network, Ariba, S/4HANA, LIV, MM-IV, integration limitation, F0842A, BNS-INT-ARI, invoice verification , KBA , MM-IV-LIV-2CL , Logistics Invoice Verification (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions