Entering content frameProcedure documentation Exceptions and Export Parameters of MASTER_IDOC_DISTRIBUTE Locate the document in its SAP Library structure

The module uses the table parameter COMMUNICATION_IDOC_CONTROL to return the control records of the IDocs that were created in the database. To find out the IDoc number and the current status for example, see fields docnum and status. In general, this table is not relevant to the calling application.

If the IDoc recipient was passed in the control record when master_idoc_distribute was called, but the distribution model does not allow the recipient to receive this IDoc, exception error_in_idoc_control is output with an appropriate error message.

If a receiver was not given in the control record and ALE does not find a recipient in the distribution model, an exception is not issued. If you want to react to this case, you must query the return table communication_idoc_control. If this table is empty, no IDoc was created.

This different behavior for the initial and non-initial receiver has historical reasons. The initial recipient is the standard case for master data replication: here it is of no further interest whether an IDoc was actually created. Presetting the receiver is the standard for dispatching transaction data: if an IDoc is not created, this is interpreted as an error.

 

List of Exceptions and Their Occurrences

Exception

Occurrence

error_in_idoc_control

Incorrect or no message type specified.

Incorrect or no IDoc type specified.

No IDoc created, although recipient was preset by application.

error_in_idoc_data

No data records passed.

error_writing_idoc_status

Technical problems when writing status records.

sending_logical_system_unknown

Own logical system could not be determined.

 

Leaving content frame