How does RSEINB00 work?

[Former Member]

Dear Experts,

I'm trying to convert a flat file to idoc based on the how to guide of idoc to flat file conversion and vice versa. I would like to know how does RSEINB00 convert the flat file into the IDOC? Wht is the basic functionality behind the program?

Thanks and regards,

Merrilly

[aashish_sinha · Accepted solution]

Hi,

Report RSEINB00 just calls a function module:

IDOC_INBOUND_FROM_FILE

This is the documentation of IDOC_INBOUND_FROM_FILE unfortunately just in german language available:

Report RSEINB00 just call A function modules:

IDOC_INBOUND_FROM_FILE This is the documentation OF IDOC_INBOUND_FROM_FILE .

The functional module leads the IDoc Eingangsverarbeitung of IDocs out, which are in the handed over file (DATA set). The IDocs is selected from the Ddatei and on the IDoc data base put down. IDocs, which are further-processable, are passed on asynchronously to application. The temporal uncoupling between selections and storing on the one side and the processing by application on the other side is managed by producing an Workflow event. The event container takes up on behalf more than only one IDoc number. The task, which is released by the event, passes all IDocs on and application. A COMMIT is set off not after processing of each individual IDocs, but steered, released by a data record counter.

************************************

Normally IDOCs are posted to a R/3 System and will processed automatically.

If you have a IDOC lying in the file system of your R/3 you can upload this file and trigger the automatic processing. Your R/3 knows what to do with every single IDOC type. IDOCs point to

a) function modules or

b) workflows

Regards

Aashish Sinha

PS : reward points if helpful

[vijay_b4]

Hi Merrilly,

Report RSEINB00 just call A function modules:

IDOC_INBOUND_FROM_FILE This is the documentation OF IDOC_INBOUND_FROM_FILE .

The functional module leads the IDoc Eingangsverarbeitung of IDocs out, which are in the handed over file (DATA set). The IDocs is selected from the Ddatei and on the IDoc data base put down. IDocs, which are further-processable, are passed on asynchronously to application. The temporal uncoupling between selections and storing on the one side and the processing by application on the other side is managed by producing an Workflow event. The event container takes up on behalf more than only one IDoc number. The task, which is released by the event, passes all IDocs on and application. A COMMIT is set off not after processing of each individual IDocs, but steered, released by a data record counter.

Report RSEINB00 is no dedicated XI Report. You will NOT see the IDOC in SXMB_MONI.

Report RSEINB00 just calls a function module:

IDOC_INBOUND_FROM_FILE

This is the documentation of IDOC_INBOUND_FROM_FILE unfortunately just in german language available:

Der Funktionsbaustein führt die IDoc-Eingangsverarbeitung von

IDocs aus, die sich in der übergebenen Datei (Dataset) befinden.

Die IDocs werden aus der Ddatei ausgelesen und auf der IDoc-Datenbank

abgelegt. IDocs, die weiterverarbeitbar sind, werden asynchron an die Anwendung weitergegeben. Die zeitliche Entkopplung zwischen Auslesen und Abspeichern auf der einen Seite und der Verarbeitung durch die Anwendung auf der anderen Seite wird durch Erzeugen eines Workflow-Ereignisses bewerkstelligt. Der Ereignis-Container nimmt i.a. mehr als nur eine IDoc-Nummer auf. Die Aufgabe, die durch das Ereignis ausgelöst wird, reicht alle IDocs and die Anwendung weiter.

Ein COMMIT wird nicht nach Verarbeitung jedes einzelnen IDocs abgesetzt, sondern durch einen Datensatzzähler gesteuert, ausgelöst.

************************************

Normally IDOCs are posted to a R/3 System and will processed automatically.

If you have a IDOC lying in the file system of your R/3 you can upload this file and trigger the automatic processing. Your R/3 knows what to do with every single IDOC type. IDOCs point to

a) function modules or

b) workflows

Hope that helps

Reward points if this helps

Regards

Pragathi.

[former_member859847]

Hi,

You can use that program for inbound procesing using file.

where u need to provide file path and file port.

where as file port created in i.code we21.

regards

mahesh.

[Former Member]

Hi,

When using ALE programs like RSEINB00 you will be reading in a file which will be on your O/S or a mounted drive.

You will not need to do this using XI. You can use the Idoc adapter in XI which will convert the XML payload into IDOC-XML using meta data imported in transaction IDX2 in XI. Also you will need to configure a port using transaction IDX1.

The IDOC-XML will be passed to the application via this port at runtime where its converted into RFC protocol and the IDOC_INBOUND_ASYNCHRONOUS standard program will be called, which then looks up the partner agreement from WE20 to get the inboound process code to identify the inbound posting program i.e. IDOC_INPUT_<MSGTYP>.

You need to ensure that you are creating the segments and mappping the data correctly in message mapping for example.

1. Create an ALE port of type File on the Integration Engine

2. Run the Program RSEINB00 on the Integration Engine.

This program takes parameter of the port name and the complete file name along with the path.

Traditionally SAP's IDOC interface (even before XI comes in picture) has utility programs to post incoming IDOCs in to SAP. One such program is RSEINB00 which basically takes the IDOC file name and the port as input. This program opens the file and posts the contents to the SAP IDOC interface (which is a set of function modules) via the port. The idea is to read the control record and determine the routing and further posting to application. Note that one information in the control record is the message type/idoc type which decides how the data records need to be parsed.

Now in XI scenario, what happens if we receive data as flat file? Normally, we use flat file adapter and in the file adapter we provide information on how to parse the file. But, if the incoming file is flat and in IDOC structure, why do we have to configure the file adapter, when the parsing capability is already available using RSEINB00/Standard IDOC interface.

This the reason, the guide suggests you to use RSEINB00. Now, your concern is what if you need to provide a dynamic filename. My idea is to write a wrapper program. This would be an ABAP program in your integration engine. This program will determine the file name (based on a logic which should be known to you) and then call program RSEINB00 using a SUBMIT/RETURN. You would then schedule this ABAP program in background to run in fixed schedules.

Refer

Thanks

Swarup

Edited by: Swarup Sawant on May 22, 2008 12:41 PM

[Former Member]

Hi,

Check the links:

http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm

Thanks,

Soumya.