Error in re-processing inbound idocs of status 51

Hi
We are facing problems in reprocessing inbound idoc from BD87 transaction
We have an inbound process code 'STA1' which is pointing to a standard task 'TS30000206'.  we have an errored inbound idoc(status 51) of message type 'STATUS' ( standard status change idoc pointing to process code STA1 for a valid port. Whenever we try to process it using BD87 transaction, we are getting errors B1033-'No function module for input process code STA1'.
We dont understand what we were missing. When we try the same for a process code which points to a function module, BD87 reprocesses it correctly.
We tried adding an entry in BD67 with an inbound function module 'APPL_IDOC_INPUT1'. Note that we still had the process code pointing to the same task. This time BD87 reprocessed idoc, but gave 51 again saying that 'Function module not allowed: APPL_IDOC_INPUT1'.
Any pointers or help in this regard will be highly appreciated.

Hi,
        Please check IDOC TYPE, MESSAGE TYPE & PROCESS CODE  and also check the we30, we42. & try BD87 reprocess of an IDOC.

Similar Messages

  • Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

    Hello,
    I have a inbound Idoc of type HRMD_A (basistype  HRMD_A07) which is processed by Function module (FM)  IDOC_INPUT_HRMD with  proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
    Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty)  When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
    Return and Return1
    of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
    CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
              EXPORTING
                pernr                          = ins_objects-objid       "#EC DOM_EQUAL
                actio                           = 'INS'
                tclas                           = tclas
                dialog_mode               = dial_mode
                luw_mode                  = '0'
                no_existence_check = $cross
                no_enqueue              = $cross
              IMPORTING
                return1                       = return
                hr_return                    = hr_return
              TABLES
                proposed_values    = proposed_values.
            REFRESH proposed_values.
         IF hr_return-msgty = 'E'.                           "note 984409
          CLEAR protocol_error.
          protocol_error-msgty  = hr_return-msgty.
          protocol_error-msgid  = hr_return-msgid.
          protocol_error-msgno  = hr_return-msgno.
          protocol_error-msgv1  = hr_return-msgv1.
          protocol_error-msgv2  = hr_return-msgv2.
          protocol_error-msgv3  = hr_return-msgv3.
          protocol_error-msgv4  = hr_return-msgv4.
          READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                           infty = hr_return-infty
                                           subty = hr_return-subty.
          protocol_error-segnum = t_hrobjinfty-segnum.
          protocol_error-routid = 'create_prf_pa_pb_object'
    As mentioned above, the error message is only placed in the parameters Return and Return1  and not in HR_RETURN.please read the first reply

    Hi,
    I think you have preety much done from your end itself .
    Could you please tell me what you got in this parameters:
         protocol_error-msgty  = hr_return-msgty.
          protocol_error-msgid  = hr_return-msgid.
          protocol_error-msgno  = hr_return-msgno.
          protocol_error-msgv1  = hr_return-msgv1.
          protocol_error-msgv2  = hr_return-msgv2.
          protocol_error-msgv3  = hr_return-msgv3.
          protocol_error-msgv4  = hr_return-msgv4.
    It may help us to track down the issue in more better way .
    Thanks!

  • How to process inbound idoc in R/3 with status 75 - idoc received via qRFC?

    Hi gurus,
    we are using EOIO for source to R/3, and all the idocs a received in r/3 with this status. But they can't be processed from BD87. How to process these?
    Thanks,
    Olian
    Edited by: Olian Saludew on Sep 11, 2008 11:44 AM

    Hi,
    Idocs Works on tRFC Queues.
    Check this Report to Process Inbound Idocs with Specified Status.
    RBDAPP01
    Regards
    Seshagiri

  • Processing inbound Idoc ORDERS03  with status 51

    Dear ALL
    While processing inbound idoc with message type ORDERS03 i am getting a status 51 with below erros
    I have maintained the data under VOE2 & VOE4 but not got the solution. We are on  SAP ECC6 Version
    Customer 1100 is customers purchase organization
    Partner no 1109 is customers plant
    VKORG, VTWEG, SPART cannot be determined for customer 0000001100 , vendor REN15D
    Message no. VG204
    Terms of payment in IDoc E1EDK18 have been transferred: Check data
    Message no. VG202
    Partner number 1109 for customer 0000001100 , partner function WE does not exist.
    Message no. VG140
    Regards
    Arun

    Hi,
    Vendor 100002 is not maintained in your system. Maintain the same or use some other vendor which is there in your system.
    You should be able to post the document.
    Regards,
    Lalit Kabra

  • Database error changing table ADR2 - Inbound IDOC Create Order

    Hi experts,
    I have a backgroud job for program RBDAPP01 to process inbound IDOC message type OILLDD. It woked perfectly for years. Few days ago, the job got short dump and cancelled. In Error log, it shows error MESSAGE_TYPE_X Database error changing table ADR2 in function module ADDR_SAVE_INTERN.
    I already try to activate trace log to see sql statement but still couldn't find anything suspicious. Have anyone been through this problem before? Please suggest.
    Regards,

    Hi,
         Please check if this SAP note is useful.  1300825
    Regards,
    Srini.

  • I am trying to process inbound idoc

    I am trying to process inbound idoc it will be showing error i.e
    51-Purchasing document 8000200 not selectable
    Pls give me advise

    Hi,
    You inbound FI idoc is containing Purchase order no, which is not existing in receiving system, that's the reason you are getting this error.

  • Process Inbound IDOC

    Hi there,
    I have an IDOC file store in the application server, I would like to know if exist a funcion module to read this Idoc and process it as inbound message in SAP.
    Thanks in advance
    Alexis

    Hi,
    You can use standard program RSEINB00 to process inbound IDoc file.
    Regards,
    Ferry Lianto

  • Inbound Processing of Idocs with status other than success

    Hi,
           I am new to ALE/Idocs. Can anyone  please let me know how can I process the Idocs which have the status other than 53.
    Thanks &  Regards,
    Indira

    Hi,
    In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
    - Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
    - Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
    - Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
    ~ Bineah

  • 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

  • Process Inbound IDoc WPUWBW

    Hi experts,
    I am quite new in SAP, and I am finding a lot of problems trying to make probably the easiest things.
    My problem is this:
    I am trying to process an inbound IDoc type WPUWBW, and it has status 53, but when I try to view it in the workbench, the system does not recognize the IDoc as good movement type and I can not find the way to insert in one field of the IDoc via we19 transaction the transaction type.How can I make it?And in which field can I insert the transaction type??
    Thank you very much in advance!
    Best regards,
    Ander

    Hi Praveen,
    First of all thank you very much for your help.
    My problem continues, because I am not able to find the field inside the WPUWBW IDoc to insert the transaction type, in my case 1502. But I can find the field to introduce the goods movements type, in my case 7004 in E1WPG02 segment, movement type line.
    Thank you very much.
    I wait your reply.
    Best regards,
    Ander

  • Processing Inbound IDOC's from FTP.

    Hi,
             I have an issue where IDOC's (WPUBON01 & DEBMAS01) are being saved in ftp folder and once these IDOC's are saved, we have to process it in SAP System, i would like to know the simple way of having these IDOC's processed in Unix based SAP system as the IDOC's will be coming in at Real time evey minutes or Seconds.
             is there a way to do it with out ABAP process i mean just by using the Unix Scripts or by triggering the SAP background job.
    Thanks in Advance.

    Hi,
    for testing purposes you can trigger inbound IDoc processing in transaction WE16. Otherwise you can schedule program RSEINB00 to periodically import IDoc into system. You can make a copy of that program and made changes if you need to add some extra logic.
    Cheers

  • Error in outbound processing:ALE/IDOC

    Dear all,
    I am getting an error in outbound processing as follows(I have extended the BD12 IDOC for customer master).
    The issue is that there is no hierarchie of segments in IDOC transaction we05.(Thogh the hierarchie can be observed in WE30)
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment Z1KNA1M_ADRC does not occur at the current level of the basic type DEBMAS06 (extension ).
    This error can have several reasons:
    u2022     The segment Z1KNA1M_ADRC is assigned to a group whose header segment does not occur.
    u2022     The segment Z1KNA1M_ADRC does not exist in the syntax description of the basic type DEBMAS06 (extension ).
    u2022     The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type DEBMAS06 (extension ).
    I will be thankful if anybody can help resolve the issue.
    thanks.
    Edited by: sanjivrd on Aug 4, 2009 2:17 PM

    hi,
    after adding those segments you need to release it.
    check it menu you can see the release option, you need to release it.
    then only it will work
    [Refer following link|EDI: Syntax error in IDoc (segment cannot be identified)]
    In the menu edit-> set release
    click on it and release
    Even check If the Hierrarchy of the segment is correct. This also will result in Syntax Errors.
    thanks & Regards,
    ShreeMohan

  • Job cancelled while processing inbound IDOcs

    Hi All,
    we are sceduled job in background processing mode for the program RBDAPP01(Inbound Processing of Idocs),
    but job was cancelled due to RAISE_EXCEPTION.
    if i cheked in ST22 it is showing as
    ""The termination occurred in the ABAP program "SAPLMCS2" in "MC_SEND_MAIL".
    The main program was "RBDAPP01 ".
    The termination occurred in line 108 of the source code of the (Include) program "LMCS2U09""
    i didn't understand why it is cancelled ?
    can any one pls help me ....
    regards,
    suresh

    Hello,
              Sometimes if the Data / Right Data is not present in the IDoc, then it would not help the Standard SAP Program / Programs / Function Modules to fill-in Certain Field Symbols due to which the Short Dump might have occured.
             Check the IDocs and try executing the Job again.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • Inbound idoc ( shipment) - Status change

    Hi Experts,
    I will be getting an inbound idoc containing tracking number of the shipment from an external agent.
    I have to update this tracking number in the shipment and change the status of 'shipment Start' and 'Shipment End' to be completed.
    1. Is this status change feasible ?
    2. If so can you please guide me both to update tracking number & status .
    Thanks
    Seema

    Hi Martin,
    Thanks for the response.
    Can you tell me which basic type will suit for this among SHPMNT01 to 05. I need to get the tracking number from any of the segments.
    thanks
    Seema

  • Splitter program for processing the IDOCS with status 64.

    Hello folks,
    I have a requirement explained below. I am looking for a sample code which could help me to jump start with initial development.
    Requirement:
    Develop a splitter program which retrieves all the IDCOS with status 64, create and schedule batch jobs with 200 IDOCS each. The splitter program with be scheduled every 15 min.
    Restrictions
    Only 150 batch jobs can be created at a time.
    Estimation
    There may be around 36000 IDOCS with status 64 every hour.

    Srinivas,
    Here is the explaination why we require a splitter program.
    Using RBDAPP01 parellel processing
    Let us assume there are 4 servers A, B, C and D in a server group. If we select RBDAPP01 parellel processing there will be too many RFC calls to the servergroup.
    (there are some more RFC calls later on for Order creation for example). As there is a restriction with number of RFC calls, we need to clear other RFC's before making new one. This is making complex and messy.
    Using RDBAPP01 serial processing
    For the volume of orders getting created each day, it takes a week to process those Idoca created in one day. Hence it is not a good solution.
    Splitter program
    We spawn 150 batch jobs with 200 records each. This way if we think it takes 20 min for each job to complete...by the end of 20th min we must had processed 30000 idocs.
    Hence it is the solution offered.
    Srinivas...still this confuses me..but if I am wrong anywhere please correct me.
    But your initial response has helped me a lot. Everything was blank to me, ur reply made it clear over the requirement.
    Thanks a lot,
    Naren

Maybe you are looking for