Showing results for 
Search instead for 
Did you mean: 

RSEINB00 flat file to idoc uploading in XI

Former Member
0 Kudos


I've searched a lot of posts here in SDN on how to use RSEINB00 to upload flat file idocs, and i tend to get lost as there are conflicting answers...

can anyone give me a clear/consolidated answer on how to use RSEINB00 in XI?

correct me if i'm wrong but the process is basically to upload a flat file idoc (residing in the XI application server) using RSEINB00, then after successful upload you're supposed to see your idoc in SXMB_MONI (the idoc flat file will be converted to idoc xml using the meta data loaded automatically in IDX2 and be passed to the xi pipeline)

is it needed to finish first all the setup in Integration Builder to enable the automatic loading of the metadata in IDX2?

Also what is the difference between executing RSEINB00 in a 4.5B to 4.5B system, and a 4.5B to XI system? (because rseinb00 is existing even before xi). is it the idoc xml convertion? if it is then definitely the importing of the idoc type in XI Integration Builder Design is necessary right?

Hope someone can explain clearly

I'll be more than willing to give points to the answer that will completely explain the concept..

Thanks in advance

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos


Complete Design and Configuration steps of the Scenario first, and run the report, you should see the message in SXMB_Moni. The Key is Control Segment - your sender / Idoc/ Message Type in the scenario should exactly match your control segment's contents).

It has worked for us...



Message was edited by:

Sarat Vellaturi

Former Member
0 Kudos

Hi HJ,

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

Report RSEINB00 just calls a function module:


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

Regards Mario