on 2025 Jun 13 9:53 AM
Hello Community,
I'm currently working on integrating maintenance order confirmations through the standard OData service API_MAINTORDERCONFIRMATION. Previously, we used a custom BAPI (ZF_G_EAM_WEP_CONF_CREATE) with a working payload that performed as expected when tested directly.
However, when we tried to use the same payload structure through the OData service via SAP API Management (APIM), we encountered issues.
The to_LongText field only accepts null values — any string value results in a failure.
The WorkNotCompleted field does not accept boolean values like true or false. It only works with numeric values.
Even after removing these two fields, we are still getting the following error:
"Confirmation no. 0020912981 does not correspond to operation 0020"
We are transitioning from our custom Z BAPI to the standard OData service for a cleaner, more maintainable integration. The Z BAPI does accept to_LongText as a string and WorkNotCompleted as 'X' (character). These discrepancies between the two interfaces are causing unexpected issues.
Has anyone faced similar problems with API_MAINTORDERCONFIRMATION? Any guidance on handling to_LongText and WorkNotCompleted fields properly in the OData payload would be appreciated.
The following is a payload I am using(POST) : {
"MaintOrderConf": "209012981",
"MaintenanceOrder": "4005892228",
"MaintenanceOrderOperation": "0020",
"MaintenanceOrderSubOperation": "null",
"MaintenanceWorkCenter": "S16d1Ab",
"MaintenanceWorkCenterPlant": "K000",
"PersonnelNumber": "",
"IsFinalConfirmation": false,
"RemainingWorkQuantityUnit": false,
"ActualWorkQuantity": "3",
"ActualWorkQuantityUnit": "D",
"ActivityType": "",
"OperationConfirmedStartDate": "/Date(1744329600000)/",
"OperationConfirmedStartTime": "/Date(1744329600000)/",
"OperationConfirmedEndDate": "PT09H26M00S",
"OperationConfirmedEndTime": "PT09H26M00S",
"PostingDate": "/Date(1744329600000)/",
"ActualDuration": "null",
"ActualDurationUnit": "D,
"ConfirmationText": "Confirmed_By: Sza (3) s",
"to_LongText": " : "Replaced the filter unit as per standard operating procedure. No abnormalities were detected.",
"VarianceReasonCode": null
}
Thanks in advance!
Rofhiwa
Request clarification before answering.
User | Count |
---|---|
31 | |
15 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.