BAPI Messages

Explanation:	The RFC/BAPI application connection does not contain values for one more required parameters.
User Response:	Include valid values for all required application connection parameters.

BAPI_99102 None of the parameters of function <function name> has been selected as STATUS RETURN structure.

Explanation:	No parameter of the specified function is selected as the RETURN structure status in the BAPI/RFC transformation.
User Response:	Specify a RETURN structure for the table export parameters.

BAPI_99103 Function RETURN parameter is specified. However, only <number> out of <number> required values found when parsing the property value string.

Explanation:	The Integration Service could not find valid return values for the function return parameter when parsing the property value string.
User Response:	Enter valid return values in the function return parameter.

BAPI_99105 STATUS or TEXT field of RETURN parameter must have ABAP type CHAR or NUMC.

Explanation:	The ABAP datatype in the status or text field for the RETURN parameter in the BAPI/RFC transformation is not CHAR or NUMC.
User Response:	Set the ABAP datatype to CHAR or NUMC in the status or text field for the RETURN parameter in the BAPI/RFC transformation.

BAPI_99106 Could not find the STATUS field [{0}] in the RETURN structure.

Explanation:	A valid value in the status field for the RETURN structure is not specified in the BAPI/RFC transformation.
User Response:	Specify a valid value in the status field for the RETURN structure in the BAPI/RFC transformation.

BAPI_99107 Could not find the TEXT field [{0}] in the RETURN structure.

Explanation:	A valid value in the text field for the return structure is not specified in the BAPI/RFC transformation.
User Response:	Specify a valid value in the text field or the return structure in the BAPI/RFC transformation.

BAPI_99109 Could not read the internal table for the function table parameter.

Explanation:	A BAPI/RFC transformation imported from another repository or folder that was modified before it was imported. As a result, the Integration Service could not read the internal table for the function table parameter.
User Response:	Export and import the BAPI/RFC transformation again.

BAPI_99113 Exception <exception> has been raised from the RFC function call with IntegrationID <integration_ID>.

Explanation:	The RFC call to the SAP system from the SAP application server failed.
User Response:	Enter valid input data for the SAP system. Verify that the SAP application server is running.

BAPI_99116 The Integration Service could not create an SAP internal table for function table parameter [{0}].

Explanation:	The Integration Service could not create an SAP internal table. The node where the Integration Service process runs might be out of memory.
User Response:	Verify that the machine on which the node resides has enough memory.

BAPI_99118 The Integration Service could not find field [{0}] in the RETURN structure.

Explanation:	A valid value in the status field for the RETURN structure is not specified in the BAPI/RFC transformation.
User Response:	Specify a valid value in the status field for the RETURN structure in the BAPI/RFC transformation.

BAPI_99129 Commit call to SAP failed.

Explanation:	The Integration Service could not make a commit function call to SAP.
User Response:	See the error messages in the session log for more information.

BAPI_99133 The Integration Service could not connect to SAP.

Explanation:	Connection information in the BAPI/RFC application connection is invalid.
User Response:	Verify the connection parameters.
Explanation:	An SAP system error occurred.
User Response:	See the additional error message for more information.

BAPI_99135 Data overflow occurred when the Integration Service applied default value <value> to function parameter <function parameter name> for Integration ID <ID number>.

Explanation:	The Integration Service could not copy the default values of the parameter. The parameter value does not comply with the parameter metadata. For example, it might not have the correct length, scale, or precision.
User Response:	Verify that the value complies with the metadata of the parameter.

BAPI_99136 Data <data> overflow at port <port number> for Integration ID <ID number>.

Explanation:	The Integration Service could not copy the input data for the parameter. The parameter value does not comply with the parameter metadata. For example, it might not have the correct length, scale, or precision.
User Response:	Verify that the value complies with the metadata of the parameter.

BAPI_99137 Data overflow occurred when the Integration Service applied the default value <value> to the field <field name> for the Legacy Key <legacy key value>.

Explanation:	The Integration Service could not copy the default values of the field. The field value does not comply with the field metadata. For example, it might not have the correct length, scale, or precision.
User Response:	Verify that the field value complies with the metadata of the field.

BAPI_99138 Data conversion error for port <port number> with data <data>.

Explanation:	The SAP system might have sent data with a precision or scale that does not comply with the parameter metadata.
User Response:	Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port.
Explanation:	The data contains inconsistencies.
User Response:	Contact Informatica Global Customer Support.

BAPI_99139 Data conversion error for port <port number>.

Explanation:	The SAP system might have sent data with a precision or scale that does not comply with the parameter metadata.
User Response:	Verify that the transformation datatypes are compatible with the SAP datatypes. Or, increase the precision or scale for the port.
Explanation:	The data contains inconsistencies.
User Response:	Contact Informatica Global Customer Support.

BAPI_99140 The Integration Service could not retrieve metadata for parameter <parameter name> of RFC function <function name> from SAP.

Explanation:	The SAP system may not contain the metadata for the specified parameter.
User Response:	See the additional error message for more information.
Explanation:	The Integration Service could not connect to the SAP system.
User Response:	Verify the connection parameters in the RFC/BAPI application connection. Or, verify that the Integration Service and SAP systems are running. See the additional error message for more information.