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.

Similar Messages

Duplicate messages and mixed up headers in message list from IMAP server dovecot 2-2.2.16

These may be two different problems, but they happen about the same time and resolution work arounds work for both.
1) My inbox occasionally fills up with duplicates of most (but not all) messages. There seems to be no rhyme or reason behind what gets duplicated. Once duplication starts, the messages that appear multiple times usually appear about the same number of repeats (1-5 repeats of each message) but not always exactly the same.
Weirdly, sometimes an incoming mail triggers a refresh that disappears the duplicate messages and everything goes back to normal for a while spontaneously.
I've tried Properties->Repair folder, manually deleting the .msf files, restarting TB, rebooting the computer, restarting the mail server, and changing mail directories. Restarting the server does nothing, the others sometimes but not always resolve the problem temporarily. (all the fixes I could find from similar problems posted by others).
It is quite annoying - not only does my inbox become unreadable, I don't know which instance to reply to.
I'm connected to the same account on the same server with K9 and have no such problems.
Problem 2: occasionally the header of a message in the list pane doesn't match the message in the preview pane. The above fixes resolve this problem to greater or lesser degree most of the time as well, but it always comes back.
Is there a problem between TB and Dovecot? are there any possible fixes?
I've been having this problem for a while: http://forums.mozillazine.org/viewtopic.php?f=39&t=2852813
Maybe has found a fix? I keep hoping an update will magically fix the problem, but so far no such luck.
-David

These may be two different problems, but they happen about the same time and resolution work arounds work for both.
1) My inbox occasionally fills up with duplicates of most (but not all) messages. There seems to be no rhyme or reason behind what gets duplicated. Once duplication starts, the messages that appear multiple times usually appear about the same number of repeats (1-5 repeats of each message) but not always exactly the same.
Weirdly, sometimes an incoming mail triggers a refresh that disappears the duplicate messages and everything goes back to normal for a while spontaneously.
I've tried Properties->Repair folder, manually deleting the .msf files, restarting TB, rebooting the computer, restarting the mail server, and changing mail directories. Restarting the server does nothing, the others sometimes but not always resolve the problem temporarily. (all the fixes I could find from similar problems posted by others).
It is quite annoying - not only does my inbox become unreadable, I don't know which instance to reply to.
I'm connected to the same account on the same server with K9 and have no such problems.
Problem 2: occasionally the header of a message in the list pane doesn't match the message in the preview pane. The above fixes resolve this problem to greater or lesser degree most of the time as well, but it always comes back.
Is there a problem between TB and Dovecot? are there any possible fixes?
I've been having this problem for a while: http://forums.mozillazine.org/viewtopic.php?f=39&t=2852813
Maybe has found a fix? I keep hoping an update will magically fix the problem, but so far no such luck.
-David

Duplicate messages and emails

how can i stop receiving duplicate messages and emails

I have an iPad, and added my centurylink and hot mail accounts to it in addition to my new iCloud add. I get duplicate emails. When I get an email from someone, in a couple of minutes I get the same email over again, I looked at the settings over and over, don't see a way to stop it except deleting the two added accounts, I did try deleting one at a time to see what happen and then I did not get any mail from that account.

Pc Suite duplicates messages and fills message mem...

Hi there As above I have a nokia 6230i and when I try to browse the message inbox , the message "phone memory is full delete some messages and try again" appears. I do that and still get the same message!! Please help..thanks!

did you check this:
http://discussions.europe.nokia.com/discussions/board/message?board.id=pcsuite&message.id=5410#M5410

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

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

Messages get lost between IE and AE (IDoc to SOAP - Async)

Dear Experts,
in a IDoc to SOAP (Async) scenario a message was not transferred. I could not see any error message in RWB or ABAP Monitoring. When I enter RWB, the column engine is "Integration Engine" and the status is "Successful". At the same time other message with the same message interface were transmitted and they have engine "All" and status "Successful".
Why was this message not passed on to Adapter Engine? How can I restart the processing, so that the message is transfered?
Best regards,
David

Thank you for your answers:
@ Divyesh:
I can't resend the message. It does not have an error status. It says "Successful", although it only can be seen in Integration Engine, not Adapter Engine. There are not SM58 errors.
@ Krish:
In ABAP Monitoring all steps were performed as expected. Before and after this message some other messages with the same message interface were transmitted and they are visible in ABAP Monitoring, Inegration Engine and Adpater Engine.
@Hareenkumar:
In SAP everything looks like expected.
The only difference between this message and other messages sent at the same time (which were transmitted correctly) is that in RWB Message Monitoring (Component: Integration Server) the Engine is "Integration Engine" instead of "All". And the message is not visible when you select for component "Adapter Engine".
Do you have another idea?
Thanks in advance,
David

EDI ANSI X12 and relavent IDOC types and messages...

Hi ,
    Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
210 -Motor Carrier Freight Details and Invoice
240 -Motor Carrier Package Status
753 -Request for Routing Instructions
754 -Routing Instructions
816-ORGANIZATIONAL RELATIONSHIPS
828-Debit Authorization
846- Inventory Inquiry/Advice
870-Order Status Report
Could you please help me?
Thanks and regards,
gowri

EDI ANSI X12 and relavent IDOC types and messages...
Posted: May 25, 2006 8:44 PM        Reply      E-mail this post
Hi Ravi,
     Thanks a lot for the reply. I have already checked this. In the ittoolbox.com is having some info about 214 but not about 210 and 240. I have already gone through the sapgenie.com but could able to get the relevant info on below transactions.I am basically looking for relevant idoc types and messages in SAP for the below ansix12 transactions .
Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
210 -Motor Carrier Freight Details and Invoice
240 -Motor Carrier Package Status
753 -Request for Routing Instructions
754 -Routing Instructions
816-ORGANIZATIONAL RELATIONSHIPS
828-Debit Authorization
846- Inventory Inquiry/Advice
870-Order Status Report

Do we need to create message interfaces for idocs and rfcs thatare imported

do we need to create message interfaces for idocs and rfcs thatare imported
from sap server
in scenarios from sap system to file or vice versa
i knew that we need not create message types
do we also skip creating message interfaces

hi,
you create an abstract message interface for IDOC only if you want to use
them in a BPM (integration process)
for more about IDOCs have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

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

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Help me for activate I message and facetime ! iOS 7(7.1.2) iphone 4 ! Urgent plss help !

Help me for activate I message and facetime ! iOS 7(7.1.2) iphone 4 ! Urgent plss help !

Hello Mohd,
Thank you for using Apple Support Communities.
Sorry I couldn't get to your issue quicker, but the following article should help you to activate your iMessage and FaceTime:
iOS: Troubleshooting FaceTime and iMessage activation
Regards,
Jeff D.

DIFFERENCE BETWEEN iDOC MESSAGING AND bDOC MESSAGING

hI
gurus what is the diffrence between idoc messaging and bdoc messaging?
K. Mangalum

Hi Kumara,
BDOC:
Container of business data that belongs together, for example customer, contact person, order or activity. This means that it contains all required information for a business process. The technical representation of a BDoc type is completely independent. There are many possible representations for a BDoc type.
For example, a BDoc type can be represented as follows:
as a collection of internal ABAP table structures (on the CRM Server),
by ADO record sets (on mobile clients),
as an XML form (for non-SAP systems), or,
as an IDoc.
Therefore a BDoc type is a semantic collection of business data and not a syntactical description.
There are three classes of BDoc types:
BDoc types exclusively used for mobile applications
They consist of a hierarchical data segment structure with assignment to database tables.
BDoc types for synchronization between the consolidated database in the CRM Server and mobile applications
They consist of a hierarchical segment structure with assignment to database tables.
BDoc types exclusively used for non-mobile applications
They consist of:
a hierarchical segment structure with no assignment to database tables,
additional data (complex data type modeled in the ABAP Dictionary)
Standard BDoc types are provided by SAP. Additional BDoc types can be modeled by customers.
Idoc:
IDOC: An intermediate document, container for exchanging data between R/3 and other SAP and non-SAP applications. Structured collection of segments. Segments are structured collection of data elements.
General Structure
IDocs contain administration information for technical processing, as well as the actual application data, which is stored in segments. A segment comprises segment fields as the smallest unit of the IDoc - comparable with the data elements from the EDIFACT standard.
In the SAP System, the processing status ("what has happened to the IDoc before now?") is stored in the IDoc status information. The status information also contains details about errors and indicates the data in which the error occurred. This status information is not forwarded as part of the IDoc but separately using "status processing".
IDoc types (special structure)
An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). For example, segment E1EDPT1 (document item text identification) is a child segment of segment E1EDP01 (document item data, general) in IDoc type EXPINV01 (export billing) and a child segment of E1EDP07 (order data shipping notification) in IDoc type DESADV01 (shipping notification). The segment, therefore, is used in several contexts and is the "child" of several "parents".
CRM Bdoc and IDoc are both persisted data structures.
Idoc works on a particular technology called ALE and is used for data exchange between two R/3 systems
Regards,
Satish Mathala

Urgent: Duplicate Message and Duplicate idoc ..

Similar Messages

Maybe you are looking for