Reprocessing of Inbound Idoc

I am trying to update customer master data using inbound IDOC technique,I am getting Error code 51
Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1.But in Data record NAME1 is holding value.
Pls tell me How to reprocess IDOC ..
If Possible Pls Explain me step wise

Hi,
You can use transaction BD87 to reprocess the IDoc, but that will not help I think. You can put a break-point in Function module IDOC_INPUT_DEBITOR, reprocess the IDoc with BD87 and when the breakpoint is hit set field input_method to "A". You can then see exactly where in the BDC the error is generated.
Regards,
John.

Similar Messages

SAP T-code - What transaction for reprocessing inbound IDocs?

Hello,
From what I know, WE19 is used for reprocessing outbound IDocs...
What is the transaction for reprocessing inbound IDocs?
Thanks.
Moderator message: Please use a meaningful subject for your questions. I've edited it for you this time
Edited by: Matt on Nov 6, 2008 1:39 PM

Hi,
We19 is used for testing the IDOC.
We can fill the parnter details & idoc segmetns manually and can try to post it.
This is a test tool for idoc processing manually. not specifically outbound or inbound.
Regards
Manasa

INBOUND IDOC REPROCESSING IN CUSTOM PROGRAM

Hello,
I have a custom program which displays the INBOUND IDoc data for the message type = ZSTLSP in the ALV format.
Requiremt is that I shall select a record and change one of the coulmn contents . A button 'Reprocess' will be
made available , when clicked it needs to reprocess the Idoc . The reprocessed idoc will be strored with the new values entered
and the original idoc will be stored with status 70.
Kindly let me know how to reporcess the IDoc in the custom program.
Note that If I try to cakk l standard program RBDAPP01 to reprocess the IDOCs using SUBMIT statement. We can pass the IDOC Number, Message type etc. while submitting the program but CANNNT pass the changed SDATA field.
Thanks in Advance!!
Senthil

I am able to change the value using FM IDOC_INPUT , but the changed values is not updateing in the databse.
Maybe I need to do commit. kindly let me know how to do commit in this scenario.
Senthil

Creation of Service Contract from Inbound IDOC

Hi Experts,
I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
Thanks in Advance.
Regards,
Priyabrata.

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

Hello all,
I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc.
So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
During the development and testing phase in the Sandbox system this works.
However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
I was wondering if there are any ideas why this could have happened?
Oh ... I also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
Well I hope to hear from you.
Regards
Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

Hi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay

How to change field values AFTER Inbound IDOC Posted successfully

Hi SAP Experts,
In my project I receive the inbound IDOC PORDCR05 from PI and posted as an Purchase Order in ECC.
I create the Z process code and Z function module (which is a copy version of IDOC_INPUT_PORDCR) and complete all the necessary configuration steps. It works perfectly.
My problem is: I have to collect some inbound idocs (that satisfied some criteria) and change the value of field EKPO-TXJCD and EKKN-KOSTL of the PO AFTER it posted successfully (means the purchase order is created and save in database).
How can I do this? I've try to put the logic code in Z function module, but it does not work, since at that time, the Inbound IDOC is not updated to the database yet.
Aprreciate your advise.
Regards,
Elaine.

Hi Elaine ,
as per your cretiria pick the idocs and take created PO# from status 53 & use the BAPI (BAPI_PO_CHANGE) to change the neccessary values in the PO. We can't reprocess those idocs again.
Reddy

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Inbound Idoc segment change

Hi All,
How can We modify or append a segment to the inbound IDOC. The scenario is as follow
We have an inbound IDOC to create/change contract order. There are some segments in the IDOC to hold the error records.
while processing the inbound IDOC we need to fill these blank segments with relevant data, so that we can reprocess the IDOC with ease.
I am trying the modify the IDOC_DATA inside the processing function module. Till the end of the function module IDOC_DATA is having the added segment data, however when I am checking from WE02, the segments are appearing to be blank.
Please let me know, what is missing above.
Thanks & Regards
D. Pradhan

Which exit / BAdI are yous using for adding the segment & what is your inbound processing function module ?
Anyways i also had the same problem a few weeks back i was trying to delete a segement though
My understanding is in WE02 it displays the data from EDIDC & EDIDD. In your I/B processing FM you only modify the data in the IDOC_DATA table & not in EDIDD.
Check in EDIDD, the segment would not be there.
BR,
Suhas

Error in Inbound Idoc trigering Workflow Scenario

I am getting below Error while I am posting Z Inbound IDOC in production system.
Please tell me what is getting wrong and how to correct.
Work item 000000000000 cannot be read
Message no. WL803
Diagnosis
The work item with the specified ID can either not be read completely or partly (for example, its container).
System Response
The action was cancelled and the work item, if it still exists, set to error status.
Procedure
Check whether the work item has already been deleted or whether only parts of it can no longer be read.
In the latter case, the work item is inconsistent.
Refer to your workflow system administrator.
Points will be surely given to helpful answers.
Regards
Edited by: Tushar Mundlik on Feb 12, 2008 8:15 AM

Hi Krishna,
First we have to find out if the error comes from processing in the application or from one of the checks performed before the application is called.
Go to function module IDOC_INPUT_OPDERS and put a breakpoint on "PERFORM edi_mode_to_mem.". Then reprocess the Idoc and when the program stops at your breakpoint set INPUT_METHOD to 'A'. In this way your order will be processed online (using BDC and you can find the error).
If the program doesn't stop at your breakpoint the error comes from one of the checks before.
But please try this first and come back if this doesn't solve your problem.
Kind regards,
John.

Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Receiver port missing in inbound idoc

Hi All,
I am posting idocs from XI to R/3. All the ALE settings have been done correctly. Idocs were being posted to R/3 successfully, however suddenly the idocs started failing in R/3 with error: EDI: Partner profile inbound not available
When i checked the control record for the errored idocs i found that the receiver port is missing. I am not sure why this is happening as in the idoc adapter we have provided this and also the idocs were being posted successfully with the same setting.
Pls help to find the root cause for this problem.
Further what would be the best way to reprocess these failed idocs? The number is huge around - 30,000 hence manual processing through we19 is not possible. Also BD87 cannot be used as i need to edit the idoc to add the receiver port information before reprocessing.
Kindly suggest. Any help in this regards would be welcome.
Thanks
Anand Chavan

hi
Go thru the below blogs
check the partner profile settings
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/frameset.htm
Idocu2019s not posted in the receiver SAP Systemsu2026.
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
Troubleshooting File-to-IDOC Scenario in XI.
Troubleshooting File-to-IDOC Scenario in XI.
reward points if helpfull
regards
kummari

Inbound idoc ordsp fm:IDOC_OUTPUT_ORDRSP

my problem is that idoc fails when it comes in as a response of ORDCHG when user changes the delivery date in PO outbound idoc triggers with message type ORDCHG. Vendor sends the response as a confirmation of order via inbound idoc message type ORDRSP. it fails at that movement and gives an error ME 790(material number differ from .............) it is comparing the value of segment E1EDP19 qualifier 001 field IDTNR with ekpo-matnr &ekpo-ematn.
NOTE: there is value in segment and it is correct value. but when inbound idoc fails it is taking blank value in fekpo and comparing with ekpo-matnr &ekpo-ematn and giving an error ME 790
and when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully
one more thing i noticed in all failed idoc that segment E1EDK02 qualifier 002 not got populated which contains vendor acknowledgement number.
but when we reprocess it in WE19 without doing any changes it posted sucessfully.
thanks in advance.

You say that "when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully". What about if you reprocess the same iDoc via BD87 ? If you are using the same Function Module, this shouldn't happen, unless you have some very specific userexit code around the user or transaction type.
Cheers, Paul.

How to edit inbound idoc with data errors in multiple segments and reproces

Hi friends,
i have a requirement for error handling of inbound sales order(ORDERS04) without using WORKFLOW and WE19.
i have seen some function modules like edic_* ..
but my doubt is how to edit the error data(how can i identify the particular error fileds in the segments)and how to reprocess the same idoc.
Please help me...
Thanks in advance

Hi Narasimh,
Please find the following steps to edit IDOC segment after you find the error using WE02.
The example codes can be found in website
http://www.sapgenie.com/sapedi/idoc_abap.htm
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                 OTHERS                  = 3.
STEP 3a - Change control record
CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
       EXPORTING
            idoc_changed_control         = itab_edidc
       EXCEPTIONS
            idoc_not_open                = 1
            direction_change_not_allowed = 2
            OTHERS                       = 3.
STEP 4 - Close Idoc
Update IDoc status
CLEAR t_itab_edids40.
t_itab_edids40-docnum      = t_docnum.
t_itab_edids40-status      = '51'.
t_itab_edids40-repid       = sy-repid.
t_itab_edids40-tabnam      = 'EDI_DS'.
t_itab_edids40-mandt       = sy-mandt.
t_itab_edids40-stamqu      = 'SAP'.
t_itab_edids40-stamid      = 'B1'.
t_itab_edids40-stamno      = '999'.
t_itab_edids40-stapa1      = 'Sold to changed to '.
t_itab_edids40-stapa2      = t_new_kunnr.
t_itab_edids40-logdat      = sy-datum.
t_itab_edids40-logtim      = sy-uzeit.
APPEND t_itab_edids40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
       EXPORTING
            document_number = t_docnum
            do_commit        = 'X'
            do_update        = 'X'
            write_all_status = 'X'
       TABLES
            status_records   = t_itab_edids40
       EXCEPTIONS
            idoc_not_open    = 1
            db_error         = 2
            OTHERS           = 3.
Hope this will help.
Regards,
Ferry Lianto

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

INBOUND IDOC issue

Hi,
I'm facing the following problem:
A program reads a file from a directory in the unix server itself and populates an IDoc. No BDC is involved.The file contains all the data required to populate the IDoc like control record, data records etc. But when the IDoc is posted, it fails giving the message " Receiver port in the control record is invalid ". But when I try to reprocess the IDoc through WE19 without changing anything, I'm able to process it successfully by giving the Inbound Function Module corresponding to the process code.This is not happening in the case of Standard Inbound. I'm using a file port with ALE services but not EDI.All the other configurations are maintained.
Please suggest a solution.
Thanks,
Raj.

Hi Rajgopal,
for an inbound idoc no need for port configuration.Please see whether u have done all the configurations correctly.Also if this is inbound that means u r updating to SAP , so already data will be available in control record and data record.So please check the sender information and the receiver information.check the port the sender using.
For a custom function module,custom message type,custom basictype,the below configurations r generally done.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
In we20 u have give u r zmessagetype in the inbound parameters and also u r custom process code.
Regards,
Nagaraj

Reprocessing of Inbound Idoc

Similar Messages

Maybe you are looking for