Solution : https://service.sap.com/sap/support/notes/206068 (SAP Service marketplace login required)
Summary :
Issues arise when calling a BAPI from the Business Connector leading to RFC errors, erroneous BAPI return structures, or unexpected return values compared to calls made via SAPGui with identical inputs. The root causes include outdated BAPIs and SE37's unexpected behaviors. Solutions involve updating BAPIs as per notes 160291 and 169573, configuring Business Connector settings to utilize hidden SAPGui, ensuring input parameters match internal formats using conversion exits or the BAPIs for data conversion. The outcome discrepancies are manageable by adjusting BC lookup tables or through post-call output conversions.
Key words :
field order_partners-partn_role refers, conversion routine parvw attached, sap -> sap servers, conversion exits convert, bapi works fine, bapi call fails, actual bapi call, abap error dynpro_send_in_background, user readable format, bapi return structure
Related Notes :
| 550431 | FAQ: BAPI in sales - general questions |
| 206689 | Problems when executing a Function Module from the browser |
| 169573 | EPS termination saving DYNPRO_SEND_IN_BACKGROUND |
| 160291 | When creatg sales order via Bapi, terminatn occurs |