3686278 - [Overview] Restrictions of Credit Memo Request (A2X) OData V4 API - S/4HANA Cloud Public Edition

This KBA provides an overview of the restrictions and known limitations of the Credit Memo Request (A2X) OData V4 API in SAP S/4HANA Cloud Public Edition.

Supported Scope

The initial version of the Credit Memo Request (A2X) OData V4 API was delivered with release CE2508. The API continues to be enhanced in subsequent releases and serves as the successor to the OData V2 API.

Recent enhancements include:

• Since CE2508: Support for read operations for variant configuration
• Since CE2602: Support for creation of credit memo requests with reference

Future innovations will continue to be delivered through this API.

Known Limitations / Constraints

Due to business design and technical framework restrictions, the following limitations apply:

1. One-Time Customer (CPD) Not Supported

Creation of Credit Memo Requests for one-time customers (CPD) is not supported via the A2X OData V4 API.

This is a standard system limitation and is also documented in the SAP Help Portal under the API constraints section.

As a result:

• One-time customer scenarios cannot be processed via this API
• A regular Business Partner (customer master) must be used instead

2. Limited Support for Initial (Empty) Field Values

To improve data integrity, validation rules have been tightened. Only specific fields allow initial (empty) values during creation.

If values are expected to be defaulted or derived by backend logic, such fields should be omitted from the payload.

Header Entity (allowed initial values):

• PurchaseOrderByCustomer
• SDDocumentReason
• HeaderBillingBlockReason
• CustomerPaymentTerms

Item Entity:

• PurchaseOrderByCustomer
• CustomerPaymentTerms

Header Pricing Elements:

• ConditionRateAmount
• ConditionRateRatio

Item Pricing Elements:

• ConditionRateAmount
• ConditionRateRatio

3. Deep Insert Requirement

Entities cannot be created individually.
Creation is only supported via deep insert requests (with the exception of header and item partners).

4. Other Constraints

• Sub-entity filtering is not supported
• Multiple credit memo requests cannot be processed in a single $batch changeset

Recommended Approach / Workaround

For integration scenarios requiring API-based creation:

• Use a regular Business Partner (customer master) instead of a one-time customer
• Optionally, implement a generic/dummy customer approach to reduce master data maintenance

Manual creation via SAP GUI or Fiori apps remains possible for one-time customer scenarios but is not suitable for automated integrations.

SAP Help Portal - Credit Memo Request (A2X, OData V4)

A_CREDIT_MEMO_REQUEST, Credit Memo Request API, CPD, One-Time Customer, API Limitation, S/4HANA Cloud, OData V4, Sales Document API , KBA , SD-SLS-CMR-2CL , Credit Memo Request and Debit Memo Request (Public Cloud) , Product Enhancement