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

Similar Messages

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.

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.

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

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.

Sender FTP MVS file duplicate Handling

Hello,
I am facing the following challenge in one of my current development. I know it is an age old issue but Would greatly appreciate
some new inputs/views into this.
The following is the scenario.
1. PI 7.3 Sender File adapter (FTP) reads the file from the mainframe (MVS)
2. The MVS dataset is like
     TEST.MVS.DATA.C001D00
     TEST.MVS.DATA.C002D00
     TEST.MVS.DATA.C003D00 ....
3. For a specific reason the MVS file is not allowed to be deleted/archived, were as the new file will be keep on adding (004, 005, 006 ....)
3.1 Handled this using "ftp. ignoreSourceFileDeletion " -- true
4. Now the challenge in SAP PI is "how to READ the NEW files ONLY, ignoring/skipping the old files"
4.1 The file size is big enough to avoid reading all files and filter/delete using Mapping/Script
5. I have used the default "Duplicate Handling" option available in the File Sender adapter, but
        5.1 the problem is, the channel throws the duplicate error after processing the first file (DATA.C001D00)
            but dose not move on to process the next file (since the first file is still available on the FTP, as mentioned in step 3).
        5.2 For every poll interval it throws the duplicate error/message (in CC monitor) for the first file again n again.
        5.3 Duplicate handling config :- Duplicate Message Alert Threshold = 0
Pls let me know if you have had a similar scenario and how to handle it.
Adapter module would be a last resort :-)
Thanks in advance
Prasanna

Hi Hareesh
Thanks for the reply. The mainframe dosent allow the file permission to be changed!!
We have figured out to use an abap program (bg scheduled job) which will do the ftp pull and also maintains the filename, timestand and size in an custom table. So every time it will check the table entries and will get the latest files only.
Marking it as answered!!
Regards
Prasanna

IDOC Output for Payment Run through F110

Gurus,
I am trying to generate IDOCS for the payment run through F110 transaction. I have setup the following but still unable to generate the IDOCS.
- Bank partner setup with IDOC PEXR2001 and message PAYEXT.
- House bank configuration.
Can anyone help me with the complete set of instructions to generate the idocs?
Thanks in advance,
Rishi

Hi
Have you done House Bank Configurations (FI12) and APP settings (FBZP)
Are you using workflow concepts in this Scenario.
Please check these 2 settings may be problem with these settings.
Thanks
Chandra

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

[svn:fx-trunk] 21141: Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors .

Revision: 21141
Revision: 21141
Author:   [email protected]
Date:     2011-04-26 06:40:39 -0700 (Tue, 26 Apr 2011)
Log Message:
Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors.
QA: Yes
Doc: No
Checkintests: Pass
Details: When a logout was followed by an immediate login, sometimes the server would throw duplicate session detected errors. This was because when logout happened, a fire-and-forget disconnect message was sent to the server that established a new session, and if the subsequent login happened before disconnect ACK returned from the server, that would establish another session and hence the error. The fix is to insert a slight delay between disconnect and ResultEvent dispatching. This way, disconnect has a chance to return before a login is performed.
Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

You've got an incompatible Logitech driver and java was incompletely uninstalled.
You may have a problem with the Wacom driver.
I don't know if fixing those things will help.
There also a few window server errors, but I don't know if they are causal.
If you can note the time of the hangs, that might help narrow it down in the logs.

Pages 2.0 is exporting Word files in name.docx format causing duplicates files on my PC via iTunes. Anyway to have it export name.doc files as Pages did earler?

Pages 2.0 is exporting Word files in name.docx format causing duplicates files on my PC via iTunes. Anyway to have it export name.doc files as Pages did earler?

What I read in the PDF version of the manual (while I was waiting for my plane this afternoon), it seems pretty comprehensive. I was particularly interested in what it had to say about creating your own templates.
Supposedly, it will remember if I left invisibles showing in templates (one of my big complaints with Pages 1). I'll find out soon enough. I must say that opening my two documents I use for answering posts here in discussions sure did open faster & navigating an 11-page table was much faster.
Another good thing I noticed, the font used for the serial number is much clearer & there were no confusing characters - O/0, S/5, etc.
Peggy

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

IDOC for Partial payments

hi guys,
Kindly let me know if there is any IDOC for partial payments. when you run f-53
With Reagards
Pradeep N

Hi,
The partial payment for the finance transaction you find in BSIK , BSID tables.
When the invoice paid fully then all this partial payment will shift form BSIK and BSID to BSAK and BSIK table.
For all the partial payment REBZG, REBZJ will contain the invoice number , fiscal year of the invoice .

Limit send of IDoc from SAP-ERP to SAP-XI or a Non-SAP

Hi guys,
I send the following IDocs from SAP-ERP over SAP-XI to Non-SAP for an initialload: Artmas, Bommat, Infrec, Cond_a, Mmaddi, Cremas
Example: Artmas with TA: BD10.
Problem: SAP-ERP send all 25'000 IDoc to SAP-XI. The effect is that the qRFC and tRFC in SAP-XI is full, because the Non-SAP is not fast enough to takeover the Idocs. From then other systems can't send out or get in Idocs.
I tried to limit in WE20, but it didnt work. TA: RSEOUT00 ist not so useful, because of the quantity of the IDocs.
Is in SAP-ERP a possibility to limit the sending of IDocs to SAP-XI or Non-SAP?
Example: Automatic sending of 200 Idocs every 2 Minute.
Thanks

may be u can write a wrapper above BD10 this way
report zaRs message-id b1.
select-options: matsel for marav-matnr matchcode object mat1.
parameters: receiver like tbdlst-logsys no-display.
start-of-selection.
select * from mara into i_mara where matnr in matsel.
refresh : matsel.
v_no = 0.
loop at i_mara.
    move i_mara-matnr to matsel-low
* fill up sign option etc.
    append matsel
do.
   move mara
   if v_no = 200.
    submit rbdsemat " Program behind BD10
          with logsys eq receiver
          with matsel in matsel
          with mestypat eq 'ARTMAS'
          and return.
          wait 20 seconds
    exit.
    clear v_no.
   endif.
enddo.
a®

Getting FLBP to run after posting IDOC of type FINSTA01

Hi experts:
We are getting an EDI 820 feed from Chase of customer payments. That feed is taken by PI an an IDOC for each payment is created of type FINSTA01. After it processes we need the automatic matching program FLBP to run immediately after the status 53 of the IDOC to clear open invoices.
1) Is there a segment field I can populate in FINSTA01 to make this happen automatically - I didn' see one.
2) Is there a user exit where I can set a parameter to force the FLBP to take place at the end? If so, what user exit and what do I need to set?
3) If not, is there a user exit that occurs after the successful processing (status 53) of the IDOC, where I could call that transaction? I can't find one.
I really don't want to create a custom IDOC for this to tack that code on the end of the process. My fallback solution is to create a job to run FLBP but I can't tie it to the successful completion of a FINSTA01 IDOC.
Any ideas would be much appreciated.
Thanks,
Scott

no answer

RSEOUT00 run sends duplicate IDOCs causing duplicate payments

Similar Messages

Maybe you are looking for