Rules and guidelines for BAPI/RFC mapplets in mappings
Rules and guidelines for BAPI/RFC mapplets in mappings
When you configure a mapping with a BAPI/RFC mapplet, use the following rules and guidelines:
Pass a value to the Integration ID ports in the scalar input group and all mandatory table input groups of the BAPI/RFC transformation.
Add a target object if you want to receive BAPI/RFC function call errors from the BAPI error group.
Use the following guidelines when passing data to BAPI/RFC function input parameters:
When the function input parameter data type is INT1 or NUMC, provide positive values for the function input.
When the source input data for a BAPI/RFC function is of the integer data type, do not use string data in the source transformation. Otherwise, the mapping fails.
If the input data for a BAPI/RFC function mapping
contains a higher scale than the SAP metadata specification, the Secure Agent rounds
the data to comply with the SAP metadata. When you run a mapping in high precision
mode, the mapping can fail due to overflow if the round-off data cascades to the
precision digits. For example, the data type and precision for a BAPI/RFC function
parameter is DEC (6,5). The input data that you pass to the function parameter is
9.99999. When the Secure Agent processes the input data, it rounds the input data to
10, which is not compatible with the SAP metadata. The mapping fails.
ASK INFAPreview
