Symptom
- A task in CI-DS calling an RFC function from ECC/S4HANA completes successfully but does not process all data.
- From ECC/S4HANA, t-code ST05 shows connection errors while calling the function/BAPI/BADI object.
- RFC traces from within the CI-DS agent display the following errors:
-
<Timestamp> >> API RfcGetFieldDescByName
RfcGetFieldDescByName(typeHandle=000001515B6B5F30, name=XXXXX, in=0000015161BDA6D0, error=0000000EB64DC0D0)
RfcGetFieldDescByName(typeHandle=000001515B6B5F30, name=XXXXX) failed 20, 20, field XXXXX not found
typeHandle=000001515B6B5F30: name=/IBP/T_INTCPI_RET_MESSAGE (origin=OTD) with 2 fields
field 0 (TYPE, 0, 1, 0, 2, 0, 0, 0000000000000000, 0000000000000000)
field 1 (MESSAGE, 29, 8, 8, 8, 8, 0, 0000000000000000, 0000000000000000)
<Timestamp> [05500] << API RfcGetFieldDescByName returned RFC_INVALID_PARAMETER
RFC_ERROR_INFO.key: RFC_INVALID_PARAMETER
RFC_ERROR_INFO.message: field XXXXX not found
-
Read more...
Environment
SAP Cloud Integration for data services
Product
Keywords
CI-DS, Cloud Integration, RFC_INVALID_PARAMETER, not found, field, rfc, function, bapi, badi, timeout, st05, RfcGetFieldDescByName , KBA , LOD-HCI-DS , HANA Cloud Integration for Data Services , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.