RFC Messages

Explanation:	Valid return values are not specified in the function return parameter when parsing the property value string.
User Response:	Enter valid return values in the function return parameter.

RFC_17405 Status or text field of return parameter must have ABAP type char in the source definition.

Explanation:	The ABAP datatype in the status or text field for the return structure is not specified as char in the source definition.
User Response:	Specify the ABAP datatype as char in the status or text field for the return structure in the source definition.

RFC_17411 Output data conversion error for row number <row number> of table parameter <parameter>. This row will be skipped.

Explanation:	An invalid value has been provided for the function table parameter. This error occurs if the input data to the function table parameter field is not convertible to the data type of the corresponding field in the mapping.
User Response:	Enter a valid value for the function table parameter.

RFC_17412 Output data conversion error for Scalar Output parameter. This row will be skipped.

Explanation:	An invalid value has been provided for the scalar output parameter. This error occurs if the input data to the scalar output parameter field is not convertible to the data type of the corresponding field in the mapping.
User Response:	Enter a valid value for the scalar output parameter.

RFC_17416 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 with an exception.
User Response:	Enter valid input data for the SAP system. Verify that the SAP application server is running.

RFC_17422 Function Name <Function name> and Sequence ID <Sequence ID> do not match. One of them is incorrect.

Explanation:	The specified function name and sequence ID for the incoming row to the Custom transformation is not in sync. Data may be incorrect or corrupt.
User Response:	Prepared data might be modified or incorrectly prepared in the prepared data pipeline. Check the specified row data.

RFC_17423 Input for function <Function name> is received while expecting input for function <Function name>.

Explanation:	There is only one function in the mapping and the value of sequence ID is not 1, or you have more than one function in the mapping and the order of SequenceID is not in sequential order. For example, the first row comes into the RFCMSFunctionCall Custom transformation with SeqID = 1, the second row comes into the RFCMSFunctionCall Custom transformation with SeqID = 3.
User Response:	The RFCFunctionCall Custom transformation expects the SequenceID to increase by increment of 1 from the previous SequenceID. Check the data in the PreparedData targets.

RFC_17424 Call to function <Function name> corresponding to TransactionID = <Transaction ID>, IntegrationID = <Integration ID> failed. Cannot continue transaction.

Explanation:	The function call to SAP with the specified TransactionID and IntegrationID has failed.
User Response:	See the error messages in the session log for more information.

RFC_17425 Commit call failed for TransactionID <Transaction ID>.

Explanation:	The commit function call to SAP has failed.
User Response:	See the error messages in the session log for more information.

RFC_17427 Error when trying to create SAP internal table for function table parameter <Parameter name>.

Explanation:	The Integration Service failed to create new SAP internal table.
User Response:	Check if the node where the Integration Service process runs is out of memory.

RFC_17439 The value of all connected input indicator ports is NULL. The source file may be invalid. See the session log to find the row with the error.

Explanation:	The source file may be invalid.
User Response:	Examine the session log and the source file and eliminate errors.