on ‎2025 Feb 04 12:03 PM
Hello
We're using Sales Order OData V4 API to get the characteristics in item level, and for all characteristics with CharcDataType = DATE, the value of the date is not showing in the GET call result.
For example, I have a characteristic populated with 01/30/2025 in SO 73 item 10, and when calling the OData:
{hostname}/sap/opu/odata4/sap/api_salesorder/srvd_a2x/sap/salesorder/0001/SalesOrderItem(SalesOrder='73',SalesOrderItem='10')?$expand=_VariantConfiguration($expand=_Instance($expand=_Characteristic($expand=_AssignedValue($select=Characteristic,VarCnfCharacteristicValue,VarCnfCharcValueDescription))))
This is the characteristic piece of the result
Thanks & Regards,
Ahmed.
Request clarification before answering.
Hello,
In the response shared, the `VarCnfCharacteristicValue` is showing `null`, which is unexpectedly missing the date value '01/30/2025'.
This behavior may not be standard and can result from a few potential factors:
1. **Formatting Issue**: The formatting of the date might not be correctly handled in the OData service. Given that the `CharcTemplate` is "MM/DD/YYYY", ensure your system is correctly interpreting and returning this format as expected. Sometimes system locale or configuration settings can impact date representation.
2. **System Configuration**: Confirm that the configuration within SAP for the characteristic correctly maps and handles DATE types. Any middleware or transformation layer could potentially influence data display.
3. **Filtering or Query Adjustments**: Ensure that there are no additional filters or limitations in your OData Service that may strip out or mask specific types of data like dates.
4. **Testing with Direct API Calls**: Sometimes testing the service with a wider set of queries or confirming with direct database reads (if accessible and safe in your environment) may highlight if this is an API-specific issue or a wider data propagation issue.
To troubleshoot further, you could try:
- Checking if there's an update to the OData Service or any known issues reported for your version of SAP S/4HANA.
- Re-evaluating any enhancements or additional functionalities added to the system that might impact standard behavior.
Best regards,
Dequan Xu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 33 | |
| 18 | |
| 14 | |
| 13 | |
| 9 | |
| 4 | |
| 3 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.