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

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

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

  • Outbound IDoc Error: Status Code 37  'Sender Port' is invalid

    Hi
    I have an Error when the Outbound IDoc is triggered.
    It shows that 'Sender Port in Control Record is invalid'.
    Status Code: 37.
    I know that there are some issues with the Sender Port Definition.
    Please help me out to solve this problem using some checkpoints at each and every step.
    Reward Points Assured.
    Regards,
    Baburaj

    Hi Baburaj Manickam
    Good
    Follow this simple procedure
    1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
    -  Create File Port (WE21) for outbound file.
    -  Maintain Distribution Model (BD64) for sender ->receiver system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s). 
    _  Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    -  Create File Port (WE21) for inbound file.
    -  Maintain Distribution Model (BD64) for receiver -> sender system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RSEINB00 to upload IDoc MATMAS file(s). 
    INBOUND IDOC PROCESSING:
    Firstly attach your idoc to a process code.
    In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
    Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
    1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
    2. Set Function Modules as Inbound: - Transaction BD51
    3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
    4. Create process codes : Transaction WE42, and link the z-function module.
    5. Create partner profile: transaction WE20 and attach the message type and process code.
    6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
    Try the Trasaction WE19 for testing your inbound and outbound IDOCs
    Good Luck and Reward me for the same
    Thanks
    Ashok.N

  • Trigger an outbound idoc to sender system after inbound idoc has status 53

    Hi all,
    We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
    Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
    Kindly help me in solving this issue.
    Thanks,
    Aravind

    Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
    & call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
    Master_IDOC_CREATE, hope the solution works for you

  • Outbound Idocs in 03 status

    How do these get processed to be sent to the external system...in this case XI. They are setup as "Transfer idoc Immediately" but I am not sure what to execute to get them to process....message type WP_PLU....Thank-You

    Test: Outbound Processing from IDoc 
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated, to allow the test program to intervene. You can make sure that this is the case by setting the output mode to "Collect IDocs" in the partner profile for the IDoc interface. If you now generate an outbound IDoc for the partner (for example, via the application or the test tool), the IDoc is only generated in the R/3 System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode "Collect IDocs" in live operation.
    Activities
    Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
    You can decide whether the output mode is set to "Start subsystem" or "Do not start subsystem" in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Thanks,

  • Urgent --- How to resend an outbound IDoc which is in status 03

    Hi Experts,
    I've a rquirement to resend an outbound IDoc which is in status 03. I don't want to use BD87  or WE19 to reprocess.
    Please provide me some FM or some technique by which I may use in a Z-program to accomplish the above requirement.
    Even if IDoc no is changed....that won't cause any problem....i just need to resend the IDoc.
    Thnx in advance
    Rudresh
    Mumbai

    Test: Outbound Processing from IDoc
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated, to allow the test program to intervene. You can make sure that this is the case by setting the output mode to "Collect IDocs" in the partner profile for the IDoc interface. If you now generate an outbound IDoc for the partner (for example, via the application or the test tool), the IDoc is only generated in the R/3 System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report
    RSEOUT00, which is also generally scheduled with the output mode "Collect IDocs" in live operation. 
    Activities
    Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
    You can decide whether the output mode is set to "Start subsystem" or "Do not start subsystem" in the partner profile. This defines whether the external (sub) system processes the IDocs further.

  • Attaching Error Status to Outbound IDOC. ?

    Hello Experts,
    We have a scenario in SAP PI / XI were upon creation of a Sales Order , Purchase Order or Material Master Flow to Non-SAP System through SAP PI/XI , the IDOC shouldn't flow to SAP PI following a validation on Material Group.
    The IDOC is triggered through Output Type , there is a custom Z function module which create outbound communication IDOC. This output type is attached to a Process Code ZSO, ZMPO defined for respective scenarios defined above.
    Currently i am attaching the the status = 07 to control data structure & the IDOC is getting created but is having error.
    Is this the right practice to follow for attaching error message Outbound IDOC.
    Awaiting for your response.
    Best Regards
    Priyesh Shah

    It depends on the business requirement.
    in a previous project, if there was any error during the validation of the data within the iDoc before it is created and sent, i would trigger an error and send the error to the person who created the data with the error for them to correct.  they would then correct the error within the document and save and the iDoc would be triggered and sent correctly.

  • Outbound IDoc Error status 26

    Hello All,
             I have got one issue in outbound IDoc scenario. ( Basic type is ORDERS02 ). The IDoc failure  status shown in WE02 as 26 (Error during syntax change of IDoc outbound).  To solve this I am trying to Repeat Output through VA02 ( as this is related to salesorder) , it does not give the same error status 26 . Rather it gives status as 30 i.e. IDoc Ready for dispatch which I then process through BD87 gives status 03 i.e. Data passed to port OK .
           I repeted this for 4-5 times, everytime I do not get any error status (as that was occured at the very first time) .
    Kindly suggest what should be done to overcome this.
    Thanks in anticipation...

    Hi Ubhaka,
    In that case you should check the segments associated with the message type.Also, check the partner profile settings.
    At first (when you got the error) what was IDOC generation method - was it through VA02 or some custom/standard program? If the methods were different for generating Idocs then check the program.
    Hope that helps!
    Regards,
    Saba

  • How to update the status of Outbound IDOC in case of error

    I want to know about how to update the status of Outbound IDOC in case of error.
    I am using message control functionality here.

    HI,
    If u r using the standard message and basic type
    u can do it in the FM attached to the basic and message type.There u need to write ur own message instead of standard SAP message..chek if there r any userexits available in the FM..where u can overwrite ur own message ..
    If u r using the Zmessage and Zbasic type
    then u need to declare an internal table of EDIDS structure and then append ur message to the internal table..
    idoc_status-docnum   = idoc_contrl-docnum.
      idoc_status-msgty    = <message type>
      idoc_status-msgid    = message-id.
      idoc_status-msgno    = message-number.
      idoc_status-msgv1    = message-message_v1.
      idoc_status-repid    = sy-repid.
      idoc_status-status   = <give the error status>.
      APPEND idoc_status.
    Reward if u find useful
    Regards,
    Nagaraj

  • 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

  • Segment mising in IDOC for outbound with status 3

    Hi ,
    Segment mising for IDOC for outbound and IDOC status in 03 . What could be the possible reason for segment missing ?
    Edited by: Raghavendra Balegar on Jan 11, 2010 8:26 AM

    how do you create the IDOC?
    which IDOC?
    what segment?

  • IDOC status 30 but partner profile is set to send immediately (04)

    Hi guys,
    I have a problem with idocs not being sent immediately... The outputs, the EDI partner profiles are all set up correctly...
    it is configured to send immediately however, it's not doing so... prior to upgrade to ECC 6.0 it's working fine... now its not...
    However, in BD87 thru manual release of IDocs, it is working fine...
    Is there any changes to ECC 6.0 for this matter? or is there anything that needs to be set up other than those mentioned above in order for it to work in ECC 6.0?
    Thanks a lot!

    Mark, have you looked at the OSS notes? By 'IDOC status 30' it finds 300+ notes, this is really a wide-spread issue.
    The most recent one is 150202, which actually recommends collecting the IDocs instead of having "send immediately" because it saves the RFC resources. This is not really an ABAP issue, so you might want to discuss this with your Basis admin.
    Also, from my experience, even with "mission critical" processes the users, in fact, never feel any real difference between "immediate" and 5-10 min. Sometimes (due to a technical problem, for example) nothing goes on for 30+ min. and no one even notices.

  • Outbound IDOC in status 12

    Hi all,
    We have posted outbound IDOC from SAP R3 system to the middleware. Middleware system has received all the IDOC except few(2) idocs and in the very next day again they confirmed that they have not received 3 idocs.
    missing idocs were manually processed to have a immediate solution.
    we would like to konw how to trouble shoot this scenario?
    Following checks were done from our side.
    1.There are no entries listed in SM58(tRFC queue)
    2.No corresponding entries in the table ARFCRSTATE
    3.No network issues.
    4.No clue in the Gateway trace.
    Is there a way to trace the IDOC stats??
    Clara

    Hi,
    Status 12 means that the IDoc has been passed over to the receiving system.
    The report RBDMOIND checks that the transaction ID for all IDocs in status 03 are not stuck in the RFC layer  If no entry is found, the status is changed to 12.
    The receiving system has not acknowledged that this specific IDoc has been received, it is only an indicator that the RFC call is not pending.
    aRs

Maybe you are looking for