IDOC_INBOUND_FROM_FILE

hi,
i'm using IDOC_INBOUND_FROM_FILE to read the content of text file, then i want to convert it into idoc.
But the idoc generate status is 64 and i want that their status is 51.
can anyone help me......this is vey urgent

Hi,
Status 64 implies that the IDOC inbound processing is yet to happen and this is decided by the WE20 configuration given below.
Go to WE20, and check for the logical system. against the logical system check for the message type and the idoc type that you have used for inbound posting.
Then check if the immediate posting flag is ticked. This flag decides if the idoc will be posted immediately or through a scheduled batch job.
Regards,
Sravanthi

Similar Messages

IDOC_INBOUND_FROM_FILE function module and UNICODE not allowed ?

Hello all,
The IDOC_INBOUND_FROM_FILE function module doesn't allow inbound IDOCs to be processed if the UNICODE flag is set on with the WE21 transaction.
I turned on the WE21 UNICODE checkbox so that I could output characters in the extended set of UTF-8 characters. Most notably, I need to output the Euro Currency character (code 8364) and the em dash character (code 8212). This worked fine for my outbound files.
When I tried to import a normal 8-bit ASCII file with RSEINB00, the function module returns a code 8 because the UNICODE flag is set for the port. This is caused in form FIRST_RECORD_READ_AND_CHECK. The function module quits before the IDOC records are even processed at all. Look at the form code around line 168 of include program LEDINF01.
This seems very wierd since program RSEINB00 is commonly used for reading IDOC files.
Has anyone else experienced this?
Can anyone recommend a different function module or global class to use for inbound files?
Thanks
Ed Baker
P.S.
If any of you need a nice website illustrating characters available with UTF-8 encoding, try this one.
http://library.seaplusplus.net/software/plourde/utf8.html

Question rephrased and asked again to improve clarity

IDOC_INBOUND_FROM_FILE? -urgent

hi Friends,
is it required to define the message type (ORDERS01) for the file format .CSV in my presentation server?
if so ,how i can assign it ?
also it would be appreciated how to use IDOC_INBOUND_FROM_FILE?
i have used this FM ,but getting as 'error in opening file'.
Thanks

hi Friends,
is it required to define the message type (ORDERS01) for the file format .CSV in my presentation server?
if so ,how i can assign it ?
also it would be appreciated how to use IDOC_INBOUND_FROM_FILE?
i have used this FM ,but getting as 'error in opening file'.
Thanks

Error in ALE-IDOC related to HR data posting in ECC 6.0

Hello People,
Upgradation done from 4.6B to ECC 6.0.
Here the data comes from the 3rd part s/w and then gets posted through a Z program which in tern calls SAP standard program " RSEINB00" and FM "IDOC_INBOUND_FROM_FILE" is used in this std program to post the data to the corresponding HR tables through IDOC postings.
ALE-IDOC Z program works fine in 4.6B but gives error in ECC 6.0.
Error in subroutine read_namtb for structure of infotype Message no. 5-109 Diagnosis An error has occurred in subroutine read_namtb for structure of infotype .
Procedure
Check the entry for infotype in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
As per the error message it seems that some table () needs to be maintained with some values, but this was working fine with the 4.6 B with current settings.
Is this error due to version change to ECC 6.0? What extra settings need to be done with respect to IDOC so that the posting program works fine without giving the stated error. Kindly let me know.
Thanks and regards,
Gaurav Joshi.

Please keep in mind ECC 6.0 is an UniCode based system.
as 4.6C was not,
did the Z-program have been tested before in the current environment?
Some special functions (keywords hints ...) are no longer supported after the upgrade.,
this was shown during the upgrade in the unicode migration tools
For sure all the own programms needs to be verfied, after an upgrade.
commonly this should be done
in the quality assurance test to avoid touble in production.

Creation of sales order using inbound idoc

hello all,
         I have a scenario where i need to read data from a flat file, then create a sales order with the flat file data using IDOC. we can also create sales order using BAPI but the problem is that we need to handle serveral errors so we want to use IDOC.
       we are trying to use the function modules 'Idoc_input_orders' but we are not sure how exactly we need to pass the parameters into the function module, actullays data control structure is asking for different parameters like partner, idoc number, idoc port etc which we need not have as we are processing it internally in the same system.
    It would be great if some one could help me regarding.
Thanks
krishnam raju N
Message was edited by:
        krishnam Raju N
krishnam Raju N

Hi,
see FUNCTION 'IDOC_INBOUND_FROM_FILE'
Regards,
Clemens

Mass processing for inbound orders idoc's from file

Hi Experts,
I have an requirement wherein we need to process all the ORDERS idocs sent from a thrid party system to a particular folder in the SAP system. Now we use a custom programme which in turn calls fn module IDOC_INBOUND_FROM_FILE to process each file. Here if the fn. module IDOC_INBOUND_FROM_FILE hits an erroneous file (control record error) it issues abend message which causes to entire programme to exit leaving rest of the files in the folder unprocessed.
Let me know if there is any other function module or way to tackle this issue so as to process all the files.
Thanks & Regards,
Jimmy.

Add the exception ERROR_MESSAGE = 99 (or some other unique number) to the standard exceptions in the function module call in your custom program. This will allow you to trap the error and continue processing.

How to read dynamic file names in RSEINB00?

Hi, ABAP Gurus,
actually I'm a PI Consultant. Now I have a scenario to use the report RSEINB00.
In the Applicaton Server i put ASCII IDocs with the following name convension: <static name>+<time stemple>:
SAPIDOC20111127-224128-952.txt
SAPIDOC20111127-224129-115.txt
I created a new port in WE21 and the Outbound file and Inbound fiel tabs haben the same configration:
physical directory: /ABC/DEV100/inbound/
Function module: EDI_PATH_CREATE_DATE_TIME
Inbound file: SAPIDOC.txt
To execute the report RSEINB00 I must give the complete file name and port. It is not convenient.
My target is, with a job to run RSEINB00 once daily to read all files with name "SAPIDOC + <time stemple>" full automatically.
Is it possible? how to figure it out?
thanks a lot in advance! <removed by moderator>.
Regards
Rene
Edited by: Thomas Zloch on Nov 29, 2011 5:23 PM

with the extension of the standard report RSEINB00 i solved this problem. here is some code:
DATA:
dir_name LIKE epsf-epsdirnam,
file_mask LIKE epsf-epsfilnam,
g_message_fields LIKE edimessage.
DATA:
filename LIKE edi_path-pthnam,
filename2 LIKE edi_path-pthnam,
myport TYPE EDIPO-PORT.
DATA: h_EDIDC LIKE EDIDC.
DATA:
wa TYPE file_table.
DATA:
t_dir_list TYPE STANDARD TABLE OF epsfili WITH HEADER LINE,
itab TYPE table of file_table WITH HEADER LINE.
*The directoy, where the Markant ASCII IDocs are droped by XI.
dir_name = '<.../inbound>'.
*File mask of ASCII IDocs.
file_mask = 'XYIDOC.'.
*File port.
myport = '<Portname>'.
CALL FUNCTION 'EPS_GET_DIRECTORY_LISTING'
EXPORTING
 dir_name = dir_name
 file_mask = file_mask
TABLES
 dir_list = t_dir_list
EXCEPTIONS
 invalid_eps_subdir = 1
 sapgparam_failed = 2
 build_directory_failed = 3
 no_authorization = 4
 read_directory_failed = 5
 too_many_read_errors = 6
 empty_directory_list = 7
 OTHERS = 8.
IF sy-subrc <> 0.
MESSAGE e600(fr) WITH 'No ASCII IDoc exits'.
ENDIF.
"BREAK-POINT.
*The old ASCII IDocs are stored in a dataset and copied with new file name sent_<original name>
LOOP AT t_dir_list.
CONCATENATE dir_name '/' t_dir_list-name INTO filename.
CONCATENATE dir_name '/sent_' t_dir_list-name INTO filename2.
open dataset filename for input in text mode.
open dataset filename2 for output in text mode.
if sy-subrc = 0.
do.
 read dataset filename into wa.
 if sy-subrc <> 0.
 exit.
 endif.
transfer wa to filename2.
 append wa to itab.
 enddo.
endif.
close dataset filename.
*loop at itab into wa.
transfer wa to filename2.
*endloop.
close dataset filename2.
PERFORM inbound_processing USING filename.
ENDLOOP.
*& Form inbound_processing
FORM inbound_processing USING filename TYPE edi_path-pthnam.
do inbound processing from file
CALL FUNCTION 'IDOC_INBOUND_FROM_FILE'
 EXPORTING
 file_name = filename
 port = myport
 EXCEPTIONS
 file_open_failed = 1
 marker_to_be_deleted = 2
 read_file_failed = 3
 idoc_not_stored = 4
 file_delete_failed = 5
 marker_modify_failed = 6
 event_create_failed = 7
 first_record_invalid = 8
 invalid_record = 9
 OTHERS = 10.
IF sy-subrc <> 0.
fill message fields for exception handling from system fields
 MOVE-CORRESPONDING sy TO g_message_fields.
error handling using the 3.0 business workflow
 CALL FUNCTION 'IDOC_ERROR_WORKFLOW_START'
 EXPORTING
 docnum = 0
 eventcode = 'EDIM'
 mess = g_message_fields
 EXCEPTIONS
 no_entry_in_tede5 = 0
 error_in_start_workflow = 0
 OTHERS = 0.
do not care for exceptions here
 COMMIT WORK.
append message for RFC
 MESSAGE ID g_message_fields-msgid
 TYPE 'A'
 NUMBER g_message_fields-msgno
 WITH g_message_fields-msgv1 g_message_fields-msgv2
 g_message_fields-msgv3 g_message_fields-msgv4.
ENDIF.
ENDFORM. "inbound_processing

File-to-Idoc complete design suggestion

Hi all,
Could anyone suggests and validate the following approach.
design:
Sender file adapter communication channel will be used to pick up the file from the ftp. File adapter polls into ftp directory and pickup the right file and archived the file into archive directory. Adapter module checks the consistency of file and allows processing the file in XI. Java mapping program is used to segregate records into correct records and erroneous records. By using BPM, success message will be configured to send SAP as an Idoc message by receiver Idoc adapter communication channel. Error message, as an attachment will be notified to the specified system administrator by mail adapter configuration.
1) Adapter module checks the consistency of file and allows processing the file in XI.
This module will be used to reject the file if Header not present. Sets the error flag to the payload. This error flag is read in the condition in the receiver determination step and the message is sent to a receiver that will handle error messages. Mail adapter then sends this message via e-mail to the administrator. The mail content consists of the erroneous payload, erroneous file name and the error records. The processing is stopped here.
Q) How can I handle the output of adapter module in Java mapping? Shall I design the source message like the output of adapter module or some thing?
Q) How can I handle this process in BPM?
2) Java mapping program is used to segregate records into correct records and erroneous records. Is the Java mapping program output will be input to that graphical mapping or something?
Q) How can I handle the success and error records of java output.
Q) How can I handle this process in BPM?
Q) How can I configure the receivers based on the conditions set by Java services.
Thanks in advance,
venu.

Hi Krishnan,
You need to pass the control record.
Std code checks whether the first record is a control record and then on tries to fetch the other details.
I suggest one debug of IDOC_INBOUND_FROM_FILE or the main program RSEINB00 would help a lot.
Rgds,
HR

How to pass the contents of an internal table to the IDoc FIDCC2?

Hi,
I have an internal table. Using its contents, I have to create an Idoc and do GL posting.
I have to use FIDCC2 Idoc and the function module IDOC_INPUT_FIDCC2.
Can u please let me know how to pass the contents of the internal table into the idoc FIDCC2 and do the GL posting?
Regards,
Balaji. R

Hi balaji,
use function IDOC_INBOUND_FROM_FILE. This will do half the process.
Documentation is missing, but program RSEINB00 explains something,
also some links
[http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
[RSEINB00 does not work in background]
[RSEINB00 flat file to idoc uploading in XI]
[Loading flat idoc via report RSEINB00 into integration server fails]
Hope it helps.
Regards,
Clemens

RSEINB00 flat file to idoc uploading in XI

Hi,
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

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:
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
Regards Mario

EDI Inbound-Port definition

Hi,
We are doing EDI Inbound for PO. For this I need to define the port(Sender Port) as in the control record(i.e as they r sending) .If they change their port it is not working what shold I do for this.
regds,
Vinsa.R

Hi,
As i mentioned before, the sender should inform any change in control parameter so you can change your port too.
Check with the sender if they can provide this information before changing. I do not what is the terms of your company with this sender, but they should inform you before doing any change.
Option-2
The other option you have is, you create your custom program which runs before RSEINB00. In this program you have to,
- read each and every file from this UNIX directory
- read the control record.
- check if SNDPOR is what you have defined in your system
- if not then change it and save it back.
You can check the source code of FM 'IDOC_INBOUND_FROM_FILE' to see how SAP read this file. ( Program RSEINB00 calls this FM internally ). This will give you an idea, how to read control record.
I do not know if option-2 of changing control record in file will affect anything else or not.
Let me know if you have any question.
Regards,
RS

Get idoc number of receiver system in a SAP-to-SAP scenario

Hi,
In a my custom program i create cremas idoc that i send to another SAP system to create the vendor in the second SAP.
How can i do to get the inbound idoc number created in the receiver SAP to get and show its status in the sender SAP without to use the ALEAUD process?
My scenario is SAP-SAP without anything between the two .
Thanks lot.
Matteo Vernile.

Hi,
Hi,
The inbound IDoc is usually created by middleware system i.e. SAP XI, Gentran and etc.
Once the IDoc created, you can use the inbound function module to post to the application. The function module is usually starting with 'IDOC_INPUT_xxxxx' where normally the xxxxx is the name of the IDoc message type.
You can find the associated inbound process code/function module with the IDoc message type via transaction WE42.
FM like IDOC_INBOUND_FROM_FILE...
Check the Function module idoc_inbound_aysnchronous
Reward points
Regards

IDoc adapter inbox: IDoc sender partner is initial

Hi,
I have requirement to read the IDOC flat file and post IDOCs to SAP. As suggested in the following guide I am using report RSEINB00 to post IDOCS. This report basically calls the function module IDOC_INBOUND_FROM_FILE.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20convert%20between%20idoc%20and%20xml%20in%20xi%203.0.pdf
While executing the IDOC_INBOUND_FROM_FILE I am getting error:
"IDoc adapter inbox: IDoc sender partner is initial".
Please advise.
Thanks
Rajeev Gupta

Hi,
Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
In SAP ECC you need to have this logical system ...to process the received idocs..
thats it... Hope you got
Regards
Rajesh

Port values for inbound IDoc processing

We're using GIS to send IDocs into SAP, and are switching over to using file-based rather than tRFC due to some file size issues.
Can someone clarify for me why EDI_DATA_INCOMING needs a file port for loading (makes sense to me), but the receiver port (RCVPOR) value in the IDoc control record has to be SAP<sid> for the IDoc to load properly? I would expect that having a receiver port equal to the file port that we're receiving files via would be correct.
Thanks,
James

Hi James,
Why does EDI_DATA_INCOMING need a file port for loading?
The file port is used to determine the file type of the input file whether is flat or XML file.
If the file type is XML, then FM EDI_DATA_INCOMING will call FM IDOC_XML_FROM_FILE to process inbound IDoc file. Otherwise, it will call FM IDOC_INBOUND_FROM_FILE for processing the IDoc input flat file.
Hope this will help.
Regards,
Ferry Lianto

XML-IDOC inbound for ECC 6.0

Hi,
in a ECC 6.0 only landscape we would like to process XML-IDOC in inbound. For outbound we have already create a XML-IDOC port... but I don't be able to find it for inbound.
How can I do it ?
Regards.
Ganimede Dignan.

Hi,
it's quite simple, if you have a system base on NW 2004s or newer you have all that you need but take in mind XML-IDOC it's not a Free XML .... it's an XML structure as an IDOC.
In WE21 TCODE you can set-up and "XML File" port or and "XML Http" port.
In anyway you can parser each XML by ABAP custom code.
read olso some of my old notes....
IDOC_INBOUND_FROM_FILE => called within report RSEINB00
IDOC_XML_FROM_FILE         => not called by any report (on release 4.6c)
I have used fm IDOC_XML_FROM_FILE already many times to manually transfer XML-IDocs from one SAP system to another.
Given the fact that report RSEINB00 is quite simple (see below) you could create your ZRSEINB00 for processing XML IDocs.
The reports can be scheduled in background to process the inbound IDocs continuously.
REPORT RSEINB00 MESSAGE-ID E0.
* EDI inbound processing (main program to be scheduled)
* This program processes one file with one ore more intermediate
* documents. When an error occurs, a message will be send via workflow
* processing.
* The index of the last successfully processed record of the file is
* always written to the table EDFI2.
* If the program is startet again for this file, the table EDFI2 will
* be interpreted and the processing will start at the next record.
* PARAMETERS
PARAMETERS:
* directory + name of file that has to be processed
P_FILE LIKE EDI_PATH-PTHNAM DEFAULT '/usr/sap/.../SYS/global/...'.
* DATA
DATA:
G_MESSAGE_FIELDS LIKE EDIMESSAGE.
* MAIN PROGRAM
START-OF-SELECTION.
* do inbound processing from file
CALL FUNCTION 'IDOC_INBOUND_FROM_FILE'
       EXPORTING
            FILE_NAME            = P_FILE
       EXCEPTIONS
            FILE_OPEN_FAILED     = 1
            MARKER_TO_BE_DELETED = 2
            READ_FILE_FAILED     = 3
            IDOC_NOT_STORED      = 4
            FILE_DELETE_FAILED   = 5
            MARKER_MODIFY_FAILED = 6
            EVENT_CREATE_FAILED = 7
            FIRST_RECORD_INVALID = 8
            INVALID_RECORD       = 9
            OTHERS               = 10.
IF SY-SUBRC 0.
* fill message fields for exception handling from system fields
    MOVE-CORRESPONDING SY TO G_MESSAGE_FIELDS.
* error handling using the 3.0 business workflow
    CALL FUNCTION 'IDOC_ERROR_WORKFLOW_START'
         EXPORTING
              DOCNUM                  = 0
              EVENTCODE               = 'EDIM'
              MESS                    = G_MESSAGE_FIELDS
         EXCEPTIONS
              NO_ENTRY_IN_TEDE5       = 0
              ERROR_IN_START_WORKFLOW = 0
              OTHERS                  = 0.
* do not care for exceptions here
    COMMIT WORK.
* abend message for RFC
    MESSAGE ID     G_MESSAGE_FIELDS-MSGID
            TYPE   'A'
            NUMBER G_MESSAGE_FIELDS-MSGNO
            WITH   G_MESSAGE_FIELDS-MSGV1 G_MESSAGE_FIELDS-MSGV2
                   G_MESSAGE_FIELDS-MSGV3 G_MESSAGE_FIELDS-MSGV4.
ENDIF.
* end of report
there are some function modules to accomplish this.
IDOCS_OUTPUT_IN_XML_FORMAT
IDOCS_OUTPUT_VIA_XML_HTTP
for inbound processing,
IDOC_INBOUND_XML_SOAP_HTTP
IDOC_INBOUND_XML_VIA_HTTP
IDOC_XML_FROM_FILE
IDOC Adaptor,
IDX_IDOC_TO_XML
Extended table maintenance, to display IDOC in XML format with XSL,
IDOC_XML_DISPLAY
IDOC_XML_TRANSFORM

IDOC_INBOUND_FROM_FILE

Similar Messages

Maybe you are looking for