Duplicate Idoc in XI

Hi Friends
we are facing a issue ,please help me from getting out from this
when ever idoc created in R/3 and it has status of 01, 30 03,29,01,30,03,finally 41.when i monitored in XI IDX5 we foind the same IDOC 2 times ,can some one explain what might the reason for appearing twice in XI and this cause creation of duplicate entries in target system
can some one explain how to over come this
thanks in advance
siva

Hi !
Did you read:
http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
IDoc status 29: Missing or incorrect partner profile
To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners.
For more information, see Interfaces ® External Systems ® Configure Warehouse Management ® Communication R/3 -> External System ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.
If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:
* Define the missing partner profile.
* Resend all existing IDocs, which the system has not yet been able to send.
For this error, the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user.
You trigger subsequent sending of the IDocs that contained errors from the inbox.
On subsequent transmission, the incorrect IDoc is flagged with status 31 and copied to a new IDoc, which is enhanced with data from the partner profile and transferred to the asynchronous RFC.
Note
Errors in partner profiles normally only occur in the test run.
Check WE20.
Regards,
Matias.

Similar Messages

  • How to stop the duplicate idoc processing ? whar need to done SAP R/3

    Hi All
    If the Same Idoc is processed to SAP R/3 then what to do for not processing
    the duplicate IDOC ?
    Or some thing like this...
    If by mistake same idoc processed then how to avoid to process the idoc?
    what i need to in SAP R/3 side?
    Regards
    Kiran lvs

    Hi
    some thing like this:Using T.code: we19 ...Idoc processed a day ago
                                           today by using the same t.code we19 ..processed the
                                           same  idoc, what  i sent a day ago.
                                           Here how to stop this duplicate processing ?
    I hope this is clear...else pl put a note
    regards
    Kiran lvs

  • Urgent: Duplicate Message and Duplicate idoc ..

    Hi  All,
    need help.
    I have   file(Asynchronous ) to Idoc  scenario.
    We are processing file and creating idoc.
    in file  adpater  :  we have confguration 
    1) Exactly once.
    2) File content conversion/
    3) Processing mode : Archive
    4) Add time stamp
    It was working fine  but for some file.  It is creating two message in  SXMB_MONI at same time and also  created two idoc in R/3.
    I checked all the configuration.All are  fine . this is configuration  is working for other file also. This issue happening randomly.
    Please help to know why it is showing two message in  Monitoring and  creating two idoc.
    Please help me to resolve this.

    Hi Bhavesh,
    We are using File Content Conversion(Asynchronous).
    File->>XI-->R/3
    Processing mode : Archive
    Add time stamp
    File Name : ab
    We put file in source folder  and XI pull the file and process. At Random  we see in sxmb_moni  that one message processed at same time. but having different payload.
    This thing is  fine but While processing after XI , It is creating  duplicate idoc at r/3 with same payload. It is not for all.  We process other files also. Which is fine. This is Running system And we see this problem first time.
    Every thing is fine at  configurationin design and  nothing is changed. It is unexpectd behaviour  we see of XI.
    I am not able to understand, Where I can find the root cause  and how can we avoid this in future. We are using sp14.
    Thanks in Advance.

  • Avoid Duplicate IDOC :

    Hi All,
    I need to code for avoid duplicate IDOC when my program convert one idoc to another IDOC. The Code is written below..
      LOOP  AT  t_seldoc.
        SELECT SINGLE * FROM  edidc
              WHERE docnum  EQ t_seldoc-idoc.
        REFRESH: t_idocst,
                 t_edidd.
        IF edidc-mestyp = c_msg_type.
          MOVE:  c_new_type     TO  edidc-mestyp,
                 c_st69         TO  edidc-status,
                 c_st69         TO  t_seldoc-status,
                 t_seldoc-idoc  TO  t_idocst-docnum.
        ELSE.
          MOVE:  'Z_NGI_SBT_TICKET'     TO  edidc-mestyp,
                 c_st69         TO  edidc-status,
                 c_377          TO  edidc-stdmes, "Add the stdmes for acks
                 c_st69         TO  t_seldoc-status,
                 t_seldoc-idoc  TO  t_idocst-docnum.
        ENDIF.
        APPEND  t_idocst  TO  t_idocst.
        PERFORM  update_idoc.
        READ TABLE t_output  WITH KEY idoc = t_seldoc-idoc.
        MOVE  sy-tabix  TO  l_tabix.
        MOVE c_upd_idoc TO  t_output-status.
        MODIFY t_output INDEX  l_tabix.
        MODIFY t_seldoc.
      ENDLOOP.
    Line: -
    This is the perform statement.
    CHANGE BY Swati Namdev 28042009
    types : begin of ty_vbak,
          vbeln    type   vbak-vbeln,
    end of ty_vbak.
    Data : LT_dup_check type standard table of Z1NG_SBTTICKETHD,
           it_vbak      type standard table of ty_vbak.
    End Here  Swati Namdev 28042009
      CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
        EXPORTING
          document_number                     = t_seldoc-idoc
         ALREADY_OPEN                        = 'N'
       IMPORTING
         IDOC_CONTROL                        =
        TABLES
          idoc_data                           =  t_edidd
        EXCEPTIONS
          document_foreign_lock               = 1
          document_not_exist                  = 2
          document_not_open                   = 3
          status_is_unable_for_changing       = 4
          OTHERS                              = 5.
      IF sy-subrc  NE 0.
        MESSAGE ID     sy-msgid
                TYPE   sy-msgty
                NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
      LOOP AT t_edidd  WHERE segnam  EQ  c_tickey_hdr.
        MOVE  t_edidd-sdata  TO  z1tickethd.
        IF  z1tickethd-tkt_type  EQ  '0'.
          MOVE  '3'  TO  z1tickethd-tkt_type.
        ELSEIF
            z1tickethd-tkt_type  EQ  '1'.
          MOVE  '4'  TO  z1tickethd-tkt_type.
        ENDIF.
        MOVE  z1tickethd   TO  t_edidd-sdata.
        MODIFY  t_edidd.
      ENDLOOP.
      DATA: z1ng_sbttickethd LIKE z1ng_sbttickethd,
            z1ng_sbtticketdt LIKE z1ng_sbtticketdt,
            z1ng_ticketdt LIKE z1ng_ticketdt.
      LOOP AT t_edidd  WHERE segnam  EQ  'Z1NG_TICKETDT'.
        MOVE  t_edidd-sdata  TO  z1ng_ticketdt.
        CLEAR: z1ng_sbtticketdt.
        MOVE-CORRESPONDING z1ng_ticketdt TO z1ng_sbtticketdt.
        MOVE  z1ng_sbtticketdt  TO  t_edidd-sdata.
        t_edidd-segnam = 'Z1NG_SBTTICKETDT'.
        MODIFY  t_edidd.
        CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENT'
             EXPORTING
                  idoc_changed_data_record = t_edidd
             EXCEPTIONS
                  idoc_not_open            = 1
                  data_record_not_exist    = 2
                  OTHERS                   = 3.
      ENDLOOP.
      LOOP AT t_edidd  WHERE segnam  EQ  'Z1NG_TICKETHD'.
        MOVE  t_edidd-sdata  TO  z1ng_tickethd.
        CLEAR: z1ng_sbttickethd.
        MOVE-CORRESPONDING z1ng_tickethd TO z1ng_sbttickethd.
        MOVE  z1ng_sbttickethd  TO  t_edidd-sdata.
        t_edidd-segnam = 'Z1NG_SBTTICKETHD'.
        MODIFY  t_edidd.
    CHANGE BY Swati Namdev 28042009
       MOVE-CORRESPONDING z1ng_sbttickethd TO LT_dup_check.
        append  z1ng_sbttickethd to LT_dup_check.
    End here Swati Namdev 28042009
      ENDLOOP.
    CHANGE BY Swati Namdev 28042009
      refresh it_vbak. clear it_vbak.
      if lt_dup_check[] is not initial.
         Select vbeln from vbak into table it_vbak for all entries in
                            lt_dup_check where KUNNR = lt_dup_check-CUST
                            and  ZZTKT_NBR = lt_dup_check-TKT_NBR.
        if it_vbak[] is not initial.
            Message text-002  type 'E'.
        endif.
      endif.
    End here Swati Namdev 28042009
      CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
           EXPORTING
                idoc_changed_control         = edidc
           EXCEPTIONS
                idoc_not_open                = 1
                direction_change_not_allowed = 2
                OTHERS                       = 3.
      IF  sy-subrc NE  0.
        MESSAGE ID     sy-msgid
                TYPE   sy-msgty
                NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
      CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENT'
           EXPORTING
                idoc_changed_data_record = t_edidd
           EXCEPTIONS
                idoc_not_open            = 1
                data_record_not_exist    = 2
                OTHERS                   = 3.
      IF sy-subrc <> 0.
        MESSAGE ID     sy-msgid
                TYPE   sy-msgty
                NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
         EXPORTING
            document_number        = t_seldoc-idoc
            do_commit              = c_yes
            do_update              = c_yes
               WRITE_ALL_STATUS       = 'X'
         TABLES
                STATUS_RECORDS     =  T_EDI_DS40
         EXCEPTIONS
            idoc_not_open          = 1
            db_error               = 2
            OTHERS                 = 3.
      IF sy-subrc <> 0.
        MESSAGE ID     sy-msgid
                TYPE   sy-msgty
                NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
      CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
           EXPORTING
                idoc_number = t_seldoc-idoc
           TABLES
                idoc_status = t_idocst.
      COMMIT WORK.
      CALL FUNCTION 'EDI_DOCUMENT_DEQUEUE_LATER'
           EXPORTING
                docnum = t_seldoc-idoc.
      COMMIT WORK.
    ENDFORM.                    " UPDATE_IDOC
    AT  present I am checking if IDOC is Duplicate giving error message but now I have to set status as 51 and for duplicate idoc and run for remaining.
    Please provide the solution.
    regards
    Swati
    Edited by: Swati Namdev on May 5, 2009 11:26 AM
    Edited by: Swati Namdev on May 5, 2009 11:28 AM
    Edited by: Swati Namdev on May 5, 2009 11:28 AM
    Edited by: Swati Namdev on May 5, 2009 11:29 AM
    Edited by: Swati Namdev on May 5, 2009 11:32 AM

    Hi all
      any inputs on this pl...?
      Q: If the same idoc is received second time then how to stop the processing
           the duplicate idoc ?
           (I understood the question this way )
    regards

  • Duplicate IDOC

    Hi,
    Am having a file to idoc scenario using integration process.  Everything is working fine except instead of one idoc am getting duplicate idocs.
    I have checked the configuration directory and checked out the xml messages , everything looks fine.
    Let me know what would have caused these things.

    HI,
    A way which does not involve corrupting the I-Doc and leaving it lying around in an unprocessed status is to use BD87. Select the radio button for the appropriate current status, Insert the number(s) of the I-docs which are not required, untick the import in background box and then process. Use the path edit >>> delete which then sets the I-Doc to status 68, so you know that it has been dealt with. There is nothing worse when looking for I-Docs which are at the wrong status than having lots of junk hanging around.
    BD87 is exactly the same as processing through workflow, but is the way to get at the I-Doc where there is no message available, or where someone has messed around with the I-Doc and the message is now in their personal inbox. You need to take the same care in SO01 as in BD87 to select the right item to flag.
    The end screen of workflow is the same as BD87, except that you cannot - as you rightly say, get there without a workitem being created via an Error.
    If the IDoc has not been processed then it will have a status 64, and will hence not be in your Inbox anyway, although I would question the validity of an EDI / ALE process which requires the manual processing of IDocs.
    The workflow functions are not necessarily the "Right" way, but I believe them to be generaly safer.
    We have a situation at our company at present with IDocs, in that there are lots of old unprocessed IDocs sitting in the EDI tables.
    If by some chance I was to go into BD87 and execute it with no parameters by mistake, the system will attempt to re-process ALL outstanding IDocs for that status.
    I suppose people use what they feel comfortable with, and I happen to use a
    combination of both.
    Reward Points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • Duplicate Idocs - XI - SAP

    Hi Experts,
    In our scenario Idocs are coming in SAP from XI which generates Measuring Document.
    Now, Here Duplicate Idocs are getting generated carrying the same data where in one of the Idocs generates a Measuring document and other gives an Error Measuring document already exists.
    We would like to find out how the Duplicate Idocs are getting generated.
    Can anyone through some light on this kind of issues.??
    Thank You
    Deepak

    Hi,
    Now today also i found two Idocs, one has created the measuring document XYZ and the other is lying in 52 status-Duplicate Measuring Document Found. Document - XYZ.
    Now, we checked in XI system we couldnt able to find both these Idocs, dont know how these are getting generated in SAP or by any chance if they are coming from XI ??
    Also, can we have a report from SAP system showing Measuring Document generated against the IDOC number???
    Can anyone guide about this ??
    regards
    DM
    Edited by: Deepak M on Jun 30, 2010 2:40 PM

  • Duplicate IDOCS

    Hello all,
    I am having a peculiar problem here. I have a program which reads all debi change documents and creates debmas idocs for the changed customers. Then we will run rseout00 program to process those debmas idocs. These 2 programs are scheduled as 2 separate background jobs in SAP. The problem is in the job log for these jobs, it says 22 communication idocs are created and 22 idocs are selected and processed, but when I go to we05 and check the idocs, there are 44 idocs. 2 idocs are getting published for each customer. What could be the problem? Please suggest.
    Thanks,

    Hi Somen,
    Please check your distribution model (BD64) perhaps you have more than one receiver systems were defined/setup for message type DEBMAS.
    If not, please check the partner receiver (WE02) for duplicate IDocs.
    Are they the same?
    Regards,
    Ferry Lianto

  • Duplicate IDOC created for basic type PEXR2002

    Hi,
    We are using PEXR2002 idoc for some document postings in FI. For a segment EIEDP02, when trying to write a BELNR field value which exceeds its size of CHAR 35. Its creating a duplicate segment with same key value. Because of this, the idoc not getting created and ends up in error.
    Could you please anyone help me in this regard?
    Thanks and Regards,
    Vimala P

    Hi,
    In our process, the EIEDP02-BELNR value is actually filled with document text field value which is of length more than 35. What is happening right now is, if the length of document text having more than 35 characters and then with first 35 character of BELNR value one segment is created. And it again create one more segment EIEDP02 with BELNR value having the rest of the fields value(>35 characters). Thus creates duplicate segments which results in IDOC creation failure
    Thanks and Regards,
    Vimala P

  • RSEOUT00 run sends duplicate IDOCs causing duplicate payments

    We are using RSEOUT00 to send out payments to vendor using PAYEXT type. Program is run in background job mode on daily basis.
    Occasionally, 1 IDOC out of couple of hundred gives error and then program starts from the beginning and send out all IDOCs again sending those before the 'error' IDOC twice.
    Today's error IDOC had below status in the given sequence:
    01
    30
    02 - Could not write to file  (At this stage it restarted the process)
    30 (Second attempt worked fine)
    03
    20
    24
    06
    08
    10
    This is happening atleast once a month.. Any suggestions would be appreciated.
    thanks.
    sudhir

    Hi Sudhir,
    I see two seperate issues here...1) why is the job periodically failing to write to the output file and 2) why is RSEOUT00 not marking the idocs written to the file to status 03 as they are written?  Sounds like it is trying to write all idocs to the file before changing the status messages.
    As to point number 1, please check with the unix team to determine if the files are written to a NFS mount point.  There could be a possibility that the NFS mount has sporadic issues, causing failure of the job.  This situation would be very difficult to diagnose and recreate.  However, I have seen this issue at a client site.
    My concern is that I would expect RSEOUT00 to exit at failure, leaving a single file on the server with 19 records.  I would then expect the next occurance of RSEOUT00 to run and process/write all 380 idocs to a second file.  However, per our conversation you indicated that RSEOUT00 only ran one time, creating two files.  Can you please confirm if my understanding is correct, and if there are any other batch jobs (or steps within other jobs) that call RSEOUT00 and picking up these idocs.
    Whether RSEOUT00 ran once or twice, I see the failure during the write to the file as the primary problem to be solved.
    Terri

  • Duplicate Idocs in SAP

    Hi Everyone,
    I'm hoping at least one of you have had this issue and know of a fix. We received a batch of 111 850's (PO's) in our ftp In Folder and then XI created 111 855's to send back to the customer in our ftp Out Folder. In SAP I have 222 idocs from this batch! I can tell the batch duplicated 1 for 1 each order. This happens every once in a while and makes our order folks crazy because they have to Delete all the dupe orders that get in. Does anyone have a direction for me or an answer to this problem. Please let me know if I need to provide some info here.
    Thanks!
    Eddie 
    PS we are running the Seeburger Adapter incase that helps.

    Hey
    >>BUT!! SXMB_MONI shows 636!!! So in XI we see the 106 orders X 6 - Any Ideas???
    are the messages coming from outside your landscape?
    if yes,then its possible that the sender system send the message 6 times.
    its possible that that they send the message to XI and they might have not got the acknowledgment for it so they send it again n again n again.
    Thanx
    Aamir

  • ABAP Report duplicating IDOC

    Hello has anybody of you an ABAP Report, that is able to duplicate IDOCs?
    Regards Mario

    @ Agasthrui & Volker: I was looking for an ABAP. WE19 was already known.
    @Bhavesh:
    Our requirements are:
    We are testing at the moment a scenario that sends one IDOC to TWO different backend-systems.
    But sometimes we just want to send the IDOC to system A; in other cases to system B. And sometimes to both systems.
    Our idea was to configure conditions in receiver determination depending of the number range of the IDOC.
    Sample.
    - If the IDOC number starts with 1, send to system A
    - If the IDOC number starts with 2, send to system B
    - If the IDOC number starts with 3, send to systems A&B
    Thats the reason for the requirement of the ABAP to duplicate IDOCs
    Regards Mario
    Mario Müller

  • File to multple Idocs based on souce values

    Hi,
    I have the below requirement. Flat file to Idoc scenario
    Current scenario:
    Flie has n B records, so n Idocs are generated
    New Scenario
    Flie has n B records, so n Idocs are generated.
    In addition, If material starts with 4* and plant = xxxx, then additional same  docs need to generated
    Eg:
    if 2 B records are there 2 idocs are generated. and one of the record has material starts with  4* and plant = xxxx, then one more idoc is generated. so in this case total 3 idocs are generated
    How to do this ?
    Thanks
    Edited by: Varun Reddy on Apr 21, 2011 6:55 PM

    Hi Varun,
    Duplicate Idoc node in the Idoc structure.
    Keep the current mapping to the first Idoc node and apply the new mapping logic to the 2nd node.
    Regards
    Arpil

  • Status 51 in IDOC Basic type: ORDERS05

    Hi,
      When Inbound IDOCs of IDOC basic type : ORDERS05 are processed in bulk then few of the IDOCs go to status 51 with error message : "Sales organisation, Distribution channel and division cannot be determined for the customer (followed by customer number)". But when these failed IDOCs are processed again using BD87 few more IDOCs go to status 53. Similarly if the failed IDOCs are reprocessed for 4/5 times without changing any data in the IDOC then all the IDOCs go to status 53.
    When I try to create a duplicate IDOC using WE19 then the IDOC goes directly to status 53. So if processed in bulk then few IDOCs go to status 51 and when processed one by one the IDOCs go to status 53 without any problem. Can someone tell me what is the reason behind it and what has to be done to avoid the continuous reprocessing of IDOC.

    Hi,
      When Inbound IDOCs of IDOC basic type : ORDERS05 are processed in bulk then few of the IDOCs go to status 51 with error message : "Sales organisation, Distribution channel and division cannot be determined for the customer (followed by customer number)". But when these failed IDOCs are processed again using BD87 few more IDOCs go to status 53. Similarly if the failed IDOCs are reprocessed for 4/5 times without changing any data in the IDOC then all the IDOCs go to status 53.
    When I try to create a duplicate IDOC using WE19 then the IDOC goes directly to status 53. So if processed in bulk then few IDOCs go to status 51 and when processed one by one the IDOCs go to status 53 without any problem. Can someone tell me what is the reason behind it and what has to be done to avoid the continuous reprocessing of IDOC.

  • Duplicate material document created BD20 (POS)

    hi guys,
    We have a IDOC number status 64 generated with barcode and quantity details (POS data) in the segments through custom programs.. when we run BD20 to post the IDOC into application then the IDOC status changes to 53 and material document and Billing document is generated ( we can check in WPER)..
    but sometimes for a single IDOC we can see multiple Material documents and billing documents where the data (articles) in both the material documents are SAME..
    Can some one through light on this issue plz...
    regards,
    nazeer

    Hi Nazeer,
    Its very much possible that multiple IDOCs get generated for the same material it depends how frequently your BD20 program is scheduled, What parameters are passed to BD20. Another possibility is that same IDOC may get generated with change pointer program RBDMIDOC.
    Do you sense any Negetive impact of having the Duplicate IDOCs. I guess you just need to Ignore it.
    Regards
    Shital

  • IDoc Duplication Problem

    Hi All,
    My scenario is File-XI-R/3
    While sending messages, message got stuck in queue and queue stpos
    Question 1: Why does this queue stops?
    Now once I activate the queue, duplicate IDocs are getting created at R/3.
    Could any1 help me out???
    Thanks,
    Greg

    Greg,
    This is a rather strange issue.
    A few questions,
    1. Is it a file to idoc with Idoc Packaging?
    2. Are you sure that you do not have duplicate files/ duplicate records in the file?
    3. Check the message id of your Message in MONI. This same message id will be displayed in the Idoc control record under the details option ( i think. ) Not sure of the exact option but you can see the message id in the Idoc control record in one of the tabs and check if you have the duplication of the message id.
    Regards
    Bhavesh

Maybe you are looking for