IDocEncodeSDATA

The service is called before sending an IDoc to an SAP® system through clientInvokeTransaction or by an RFC adapter service for function module IDOC_INBOUND_ASYNCHRONOUS or INBOUND_IDOC_PROCESS.

Input parameters

serverName

SAP system alias, which is used as repository for structure information about the IDoc. The name must match a configured RFC connection alias at SAP® ERP.

$encoding

Optional. Specifies the encoding that is used in the output document's XML header, for example, iso-8859-1.

iDocList - OR -

Contains the IDocs as object of com.sap.conn.idoc.IDocDocumentList.

IDOC_CONTROL IDOC_DATA - OR -IDOC_CONTROL_REC_40IDOC_DATA_REC_40

Both keys are Document lists (Tables) containing the control and data tables for the IDoc. The SDATA field is a document object that contains the keys and values from the segment table. The name of the segment table is specified by the SEGNAM field.

Note: This service handles both IDoc versions 2 and 3. The difference between the two is that, for IDocs version 2, the service looks for IDOC_CONTROL and IDOC_DATA in the pipeline. For IDocs version 3, it looks for IDOC_CONTROL_REC_40 and IDOC_DATA_REC_40.

Note: You can specify the iDocList or IDoc tables that contain IDOC_CONTROL and IDOC_DATA or IDOC_CONTROL_REC_40 and IDOC_DATA_REC_40 in the input parameters.

Return values

IDOC_CONTROL IDOC_DATA - OR -IDOC_CONTROL_REC_40IDOC_DATA_REC_40

Both keys are document lists (Tables) containing the control and data tables for the IDoc. The SDATA field is a 1000 bytes field.At this point, the IDoc in the pipeline is ready to be sent to an SAP system through either clientInvokeTransaction or an adapter service for one of the function modules (IDOC_INBOUND_ASYNCHRONOUS” or “INBOUND_IDOC_PROCESS”).