Outbound Idoc 03 status - SM58 error

Hi ,
For Oubound Idoc, I am getting Idoc with status 03 but is not there in Receipient system.
When I check Idoc in Sm58, Idoc has error <b>"The ABAP/4 Open SQL array insert results in duplicate database records".</b>
Can anybody help me how to solve this issue?
Thanks & regards,
Yogita

use FM idoc_status_write_to_database to change the IDoc status from 03 to 30 and then  run WE14 or  RSEOUT00 to change the status back to 03
resending idoc from status 03 ...is a data duplicatino issue on receiving side...why do u need to do that ?
Use WE19 tcode to debug
In we19
1)U can choose your Idoc number in existing Idoc textbox
2)Press execute
3)u will display ur Idoc struct
4)Dbl click on any field then u can modify its content
5)PressStd Outbound Processing Btn to process modified Idoc
Thats it

Similar Messages

  • Error handling problem with outbound idoc status 02 and  XML HTTP Port

    I set up an ALE scenario to send master data out of SAP via an XML HTTP port.  All goes well until the idoc receives error 02. 
    It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques.  Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
    Is there any solution to still use the standard ALE error handling ?

    Hi Karin,
    Looks like based on note 701597, you can only reprocess these idocs manually via a workitem.  I qouted the relevant text below:
    3. Error handling with status '02':
    An HTTP IDoc in status '02' should not automatically be sent once again.
    Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
    However, this report was adjusted and now deletes all IDocs in status 02
    to be routed to a HTTP port from the list of selected IDocs. IDocs to a
    HTTP port in status '02' should only be sent manually via a work item.
    Regards:
    Rex

  • JDBC - XI - IDOC scenario, SM58 error

    I am trying to set up a scenario with JDBC -> XI-> IDOC.  I seem to get the data, but when I look at it in SXMB_MONI, I get the checkered flag, for the overall status, but a red flag for the outbound status.  This led me to SM58 where I see this error "No authorization to send IDocs with message type Z...".  It shows the caller ID as being XIAFUSER (which is different from the ID I have created on the receiving SAP system) and is in function module IDOC_INBOUND_ASYNCHRONOUS.   On XI, I have the RFC (SM59) and Port (IDX1) setup for the receiving SAP system.  The receiving system has an ID setup (used in the RFC on XI), has a partner profile, port, logical system, and a RFC to XI setup.
    Any ideas on where to track this down?  I tried giving XIAFUSER sap_all, and it still fails and this ID does not exist on the receiving system.

    HI,
    Just to inform you that, if any SM58 error, mainly because of IDX1 entry and RFC destination .
    So that;s the reason , i just suggested to check this SAP note.
    Now you have given SAP_ALL access to test right ? Even you can check with this SAP note-837595
    Also check that SM59 (RFC destination) in XI system uses any User ID ? DO not select CURRENT USER option here.. and check it
    Regards,
    Moorthy

  • Regarding  idoc status  26 Error

    In ABAP(Selection program)
    can anyone give the solution for the idoc status code below
    26 Error during syntax check of IDoc (outbound)
    what could be wrong in the idoc creation
    Edited by: vijay on Jan 7, 2008 3:39 PM

    hi vijay,
             It depends on the type of program.if it is custom written program check with your program logic and compare it with idoc structure.
    Reward if it usful,
    Thanks,
    Srikanth.A

  • IDoc Status 02 error

    Hi All,
                 Whenever we create the PO the outbound IDoc gets triggered but when we see the Idoc status it goes to 02 every time. Then when we manually re trigger the PO the status goes 12 which is ok.
    we want that whenver PO is created Idoc should succesfully posted to status 12.
    we are using the standard pgm for outbound idoc (RSNASTED).
    Let me know how to resolve the issue.
    Thnx
    AC

    Hi,
             I have checked in WE20 transactiona and everything is ok as per your input, but still proble persist.
    In partner profile in output mode "Transfer Idoc imm has been activated already.
    Let me know what are other things i need to check to resolve this issue.
    Thnx
    AC

  • Outbound IDoc status set as 31

    Hi Friends,
    I am working on the outbound IDoc interface IDOC_OUTPUT_ORDRSP. I modify/add few segments based on the business conditions using the user-exit EXIT_SAPLVEDC_003 (ZXVEDU15). According to the business need, I have to set the IDoc status record as 31. Now IDoc is being created with status record as 30. Is there any way to set the status record with status 31 within the scope of this IDoc interface IDOC_OUTPUT_ORDRSP.
    Pls let me know if any user exit for this same purpose. If not possible to set status explain me the reason for that.
    Thanks
    Hari

    Hi,
    You can use this standard program RC1_IDOC_SET_STATUS to change IDoc status 30 to another status.
    If the program does't exits then try this ...
    DATA: L_EDIDC_TAB       LIKE EDIDC      OCCURS 1 WITH HEADER LINE,
          L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
          L_IDOC_CONTROL    LIKE EDIDC.
        L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
        L_IDOC_STATUS_TAB-STATUS = '68'.
        APPEND L_IDOC_STATUS_TAB.
        CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
             EXPORTING
                  IDOC_NUMBER               = L_EDIDC_TAB-DOCNUM
             IMPORTING
                  IDOC_CONTROL              = L_IDOC_CONTROL
             TABLES
                  IDOC_STATUS               = L_IDOC_STATUS_TAB
             EXCEPTIONS
                  IDOC_FOREIGN_LOCK         = 1
                  IDOC_NOT_FOUND            = 2
                  IDOC_STATUS_RECORDS_EMPTY = 3
                  IDOC_STATUS_INVALID       = 4
                  DB_ERROR                  = 5
                  OTHERS                    = 6.
    <b>Reward points</b>
    Regards
    Message was edited by:
            skk

  • IDoc Status 02 Error passing data to port

    Hi Experts,
    I wrote a custome program to send customer via HTTP XML port. This program collects customer and send in single IDoc as per specified batch size.eg if batch size is 5 then 5 custome will be send in one IDoc. On devlopment environment it was working fine upto batch size 500. In quality single customer is transfering successfully but while selecting a batch size arround 100 it is displaying error 'Error passing data to port' with status 02.
    Please help me to be out of this.
    Regards,
    Ravinder

    status 02 is     Error passing data to port ...it simply means your port setting has some problem. do configure your port setting and also in partner profile
    Thanx and Regards
    Arpan Maheshwari

  • IDoc Status 56 error F21_IDOC_INSERT_WITH_FAIL_STAT

    Hi,
    I am trying to create an inbound idoc in a particular client and trying to post it in the same client using standard function module.
    IDoc type is CREAMAS and Basic Type is CREAMAS04. The function module to process this IDoc is "IDOC_INPUT_CREDITOR".
    I am building the data records, control data inside my program and passing it to the function module "IDOC_INBOUND_WRITE_TO_DB". This function module creates an IDoc but it goes in status 56. I could see the error message from Subroutine F21_IDOC_INSERT_WITH_FAIL_STAT in program SAPLEDI1. When i manually process the idoc in we19 data is posted to SAP sucessfully.
    Can anyone help me why my idoc is going to status 56 though all the segments are correct?
    Thanks
    Slasher

    Hi Guys,
    Thanks for your reply...The issue is solved. I had to define the port setting sender Partner profile.
    Hence closing this request.
    Thanks
    Vasanth

  • IDOC STATUS 8 error

    Hai friends,
    We have implemented CRM 2007 in our landscape. The data from 0CRM_SRV_PROCESS_H to 0CRM_PROH got extracted from CRM DEVELOPMENT To BW Development.
    But when we try it from CRM Production to BW Production, the error message we get is as follows:
    No data available
    Diagnosis
    The data request was a full update.
    In this case, the corresponding table in the source system does not
    contain any data.
    System response
    Info IDoc received with status 8.
    Procedure
    Check the data basis in the source system.
    However in RSA3 of the source system, the data is getting extracted.
    We need to resolve this issue by today. kindly help.
    Regards,
    Neha Solanki

    Hai,
    I checked in SM37 and got the following log :
    Job started
    Step 001 started (program SBIE0001, variant &0000000000017, user ID ALERMOTE_BW)
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 0CRM_SRV_PROCESS_H
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 2000000000                              *
    abap/heap_area_total.......... 2000000000                              *
    abap/heaplimit................ 40000000                                *
    zcsa/installed_languages...... DE                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 6500000                                 *
    ztta/roll_extension........... 2000000000                              *
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records
    Result of customer enhancement: 0 records
    IDOC: Info IDoc 2, IDoc No. 37230, Duration 00:00:01
    IDoc: Start = 06.08.2008 10:07:44, End = 06.08.2008 10:07:45
    Synchronized transmission of info IDoc 3 (0 parallel tasks)
    IDOC: Info IDoc 3, IDoc No. 37231, Duration 00:00:00
    IDoc: Start = 06.08.2008 10:07:47, End = 06.08.2008 10:07:47
    Job finished
    This means that the data is not extracted at all.
    What do you think ?
    Regards,
    Neha Solanki

  • Idoc status  05-Error During Translation

    hi ,
    we have two failure IDocs with status 05 for ORDERS type message. we did not see any diffrence between the failed Idocs and succesfull . for the same partner we got succesfull Idocs .
    can any one throw some light on how to approach ?
    regards ,
    Prakash.

    Hi,
    What  i feel is that the IDocs didn't translate correctly and were fixed, but no subsequent status records were created to reflect that fact. But you won't know for sure until you talk to
    whoever's running your EDI translator. That person can also
    tell you what went wrong with those IDocs, which you'll want to
    find and fix before you re-process anything.
    The problem is in the Mapping tool.. when the mapping tool tried to map the IDOC for EDI . it errored.. and  the EDI group should be fixing .. or contacting you if they need something in the IDOC that is missing.
    Regards,
    nagaraj

  • Idoc status 51 error

    Hi friends,
    When the inbound idoc is processed my user is getting the following error
    System error: Error in routine MRM_CHECK_RBKPV -RBKPV-BLART
    Message no. M8 607
    Procedure
    Contact your system administrator.
    Can any one help me understand this error. Is it related to any config. Any inputs appreciated.
    Thanks in advance
    Regards
    Genie

    Hi Genie
    I am not an expert in this matters but I have found following information that should be useful:
    In function MRM_INVOICE_VERIFICATION_ERS : (Transaction SE37)
    In the User-exit (to change header details)
      CALL CUSTOMER-FUNCTION '001'
          EXPORTING
              I_RBKPV              = H_RBKPV
      The Header details in H_RBKPV are OVERWRITTEN by E_RBKPV_ERS_CHANGE
    (field BLART is included here).
      In the coding of your user exit, please add the following line:
        move-corresponding I_RBKPV into E_RBKPV_ERS_CHANGE
    Then you can change the header details via E_RBKPV_ERS_CHANGE and this
    SHOULD be passed back to the standard R/3 system with BLART still in
    tact, UNLESS:
    a) The BLART field is already empty in H_RBKPV before the call to
    the customer-function, or
    b) It is cleared within your user exit (& therefore E_RBKPV_ERS_CHANGE)
    Regards
    Javier

  • How to Reprocess Outbound Idocs in Status 02 (Errors)

    Hi,
        I have an urgent problem. How do I re-process an Outbound IDoc in Status '02' (Error Passing Data to Port)
        I have tried reprocessing this IDoc through BD87 using both the options Edit>Process and Edit>Restrict and Process, but it doesn't work
         Please help as we are migrating cutover data from SAP to another system
    Regards,
    Aditya

    Worth to have a look at this thread
    Error handling problem with outbound idoc status 02 and  XML HTTP Port
    Regards
    Vivek
    Reward points for all the useful answers

  • Recommended Status Codes usage for Inbound & Outbound IDocs

    Hi,
        Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
    I assume we use 51 for Posting Program (not 56) and
    26 for a Z-Selection Program (Not 37 or any other Code).
       Please let me know what is recommended and which status codes most of the people use while Custom Development.
    Thanks and Regards,
    Venkat.

    Hi,
    Outbound IDOC Status Codes
    The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
    Outbound IDOCs
    Code Error Event Severity SAP Meaning
    02 Yes Error Error passing data to port
    03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
    04 Yes Error Control information of EDI subsystem
    05 Yes Error Translation
    06 No Harmless Translation
    07 Yes Error Syntax check
    08 No Harmless Syntax check
    09 Yes Error Interchange handling
    10 No Harmless Interchange handling
    11 Yes Error Dispatch
    12, 13, 14 No Harmless OK
    15 Yes Warning Interchange acknowledgement negative
    16 No Harmless Functional acknowledgement
    17 Yes Warning Functional acknowledgement negative
    18 No Harmless Triggering EDI subsystem
    20 Yes Error Triggering EDI subsystem
    22 No Harmless Dispatch OK, acknowledgement still due
    23 Yes Error Retransmission
    24 No Harmless Control information of EDI subsystem
    25 Yes Warning Processing despite syntax error
    26 Yes Error Syntax check
    27 Yes Error ALE error
    29 Yes Error Error in ALE services
    30 No Harmless Ready for dispatch (ALE)
    31 No Harmless IDOC is marked for deletion
    33 No Harmless Original of an IDOC which was edited
    34 Yes Error Error in control record of IDOC
    36 Yes Error Timeout error; electronic signature not performed
    37 Yes Error IDOC added incorrectly
    38 No Harmless IDOC archived
    39 No Harmless Receive confirmed
    40 Yes Error Application document not created in target system
    41 No Harmless Application document created in target document
    Inbound IDOC Status Codes
    The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
    Inbound IDOCs
    Code Error Event Severity SAP Meaning
    51, 52 Yes Error Posting error
    53 No Harmless Posting successful
    54 Yes Error Error during formal application check
    55 No Harmless Formal application check
    56 Yes Error IDOC with error added
    60 Yes Error Syntax error
    61 Yes Warning Processing despite syntax error
    62 No Harmless IDOC passed to application
    63 Yes Error Error passing IDOC to application
    64 No Harmless IDOC ready to be passed to application
    65 Yes Error ALE error
    68 No Harmless IDOC is marked for deletion
    70 No Harmless Original of an IDOC which was edited
    73 No Harmless IDOC archived
    Regards,
    Raj.

  • Handling outbound IDOC errors through workflow TS00007989

    Hi,
    I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
    I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
    Moreover i couldnt find any trigerring events for the above task.
    Can any one help me with a step by step guide for achieving this.
    Regards,
    Krishnakumar

    Hi,
    the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
    And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
    If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
    Hope this helps.
    venu

  • Query on User exit for outbound idoc

    Hi ,
    Can u all pls help me out to solve these queries
    1. when we extend a new segment (at we31) and create a new idoc type(at we30), say,for DELVRY05 idoc type-<b>what is the logic to be written inside the Exit</b>(at Transaction code - CMOD -where a project is created and the exit is found for the enhancement) ,to view our extended segment -that needs to be appended (viewed below the existing segment)at we02?
    2.Can we delete the outbound idoc generated with errors from development server?
    3.How to recify the outbound idoc errors-like runtime,syntax,port unreachable errors(at the status record and data records listed inside we02 transaction code)?
    4.How to check values populated at our extended segment inside we02-Transaction code.
    say,the logic required inside the exit may be,
    <b>Select single ladel from eikp into wa_ladel where refnr = (inbound delivery)</b>
    In this,the ladel exists in eikp table as EIKP-LADEL field.
    The main thing is- an inbound delivery is created at transaction code VL31N for which an outbound idoc(using an  Exit )should be generated  with few more validations for the fields like
    i) ekpo-pstyp(corresponding IDOC segments are  E1EDL26-PSTYV )
    ii)ekko-lifnr and ekko-lichn(E1EDL24-LICHN )
    Segment name-item(at transaction we63)                          Segment no.
    iii)   E1TXTP8-TDLINE => SCAC Code.                                    11
          E1TXTH8-TDID   => Z001.                                                 10
    iv)   E1TXTP8- TDLINE => Primary seal number.                       13
          E1TXTH8-TDID => Z002.                                                   12
    v)    E1TXTP8- TDLINE => Secondary seal number.                   15
          E1TXTH8-TDID => Z003.                                                   14
    5.Can you help me out to know the logic by which we can validate few fields from different tables like eikp,ekpo and ekko inside our Exit (in the project created at CMOD transaction?
    With Regards,
    Srividya

    Hi Swati Choudhary,
    please ask your question in devlopment forum, please see its 2 yr old thread, and i don;t think Phileas Fogg still remember his stuffs.

Maybe you are looking for