Port Type CPI-C (Inbound Processing): Scheduling Reports (SAP Library - IDoc Interface/Electronic Data Interchange (BC-SRV-EDI))

Port Type CPI-C (Inbound Processing): Scheduling Reports

Purpose

In inbound IDoc processing, you must schedule a report to select the IDocs in the R/2 System and then transfer them to the R/3 System. If the status "successfully arrived" is not to be returned immediately, an additional report is required. A special report which allows IDocs saved in the R/3 System to be processed by the application in the event of an error is available as a further option.

Process flow

Retrieving IDocs

Schedule the report RSEINB10, which retrieves IDocs from the R/2 System. Enter the following parameters:

CPI-C port in R/3 (local)

Name of the port type "CPI-C", which you have just created in the IDoc interface.

Output CPI-C trace

If the indicator is set, the connection is logged and outputted.

Additional criteria (for example company code, application transaction or logical message), according to which IDocs in the R/2 System are to be selected.

Delayed return of IDoc status records

If you have specified in the port definition that status records be returned at a later time (that is, not directly after the R/2 IDoc has been received), you must schedule the report RSESTA11, specifying the ports again:

CPI-C port in R/3 (local)

Name of the port type "CPI-C", which you have just created in the IDoc interface. The "sender port" field of the IDoc control record (SNDPOR) must contain this name, so that it can be taken into account in the selection.

Output CPI-C trace

If the indicator is set, the connection is logged and outputted.

IDoc processing after program interruption

IDoc inbound processing essentially comprises two steps. The transferred IDocs are separated from the data stream and stored. The connection to the R/2 System is terminated and the IDocs are transferred to the corresponding application, that is to say the business process which is responsible for the IDoc is started.

If the program is interrupted between the IDoc being posted and processed, the IDocs which have been posted but not processed by the application can be sent. In this case, the report RSEINB11 must be started or scheduled as a job. The only control parameter here is the port maintained in the R/2 System and written to the field RCVPOR in the IDoc control record. All of the IDocs which belong to this port and still have status 50 (IDoc added) are passed to the application. The corresponding port is determined from the "receiver port" (RCVPOR) in the IDoc control record.