Symptom
In case customer consumes OData APIs with currency codes a schema validation might fail. The content of the currency codes for filtering, reading or modifying should not be affected.
Environment
SAP S/4HANA Cloud
Cause
SAP changed from an internal to ISO standard currency code in the OData APIs to be compliant with ISO standards which led to the change of the property length from 5 to 3 in OData V4 services.
Resolution
Customers, please check consumption of your OData APIs and reprogram / adjust implementations that rely on the property length for currency properties (e.g. schema validations)
This needs to be done before the P-Upgrade of CE2108 to ensure your processes are not impacted.
The following APIs are impacted:
API Technical Name | API Title |
API_CABILLABLEITEM | Convergent Invoicing Billable Item - Read |
API_CABILLINGPLAN | Convergent Invoicing Billing Plan |
API_CABUSINESSTRANSACTION | Contract Accounting Business Transaction - Read |
API_CADISPUTECASE | Contract Accounting Dispute Case – Manage |
API_CADOCUMENTMANAGE | Contract Accounting Document – Manage |
API_CASECURITYDEPOSIT | Cash Security Deposit |
API_CN_PAYMENTREQUISITION | Payment Requisition (Synchronous) |
API_CONDITION_CONTRACT | Condition Contract |
API_CONTRACTACCOUNT | Contract Account |
API_MAINTENANCETASKLIST | Maintenance Task List |
API_RECONTRACT | Real Estate Contracts |
API_SETTLMT_DOC | Settlement Document |
API_SUPPLIERITEM | Supplier Item - Create, Read, Update |
Keywords
KBA , BC-ESI-RAP-SRV , RESTful ABAP Programming Model Services , Problem