HR ALE : Error in Idoc Status table

Hi,
We are transporting HR Master data from one client to another (message type HRMD_A) and extension ZRMD_A06. For this purpose we are using the PFAL transaction. So far, we are able to send employee data to the receiving client, all Pnnnn tables also get updated correctly ( we have applied some translation rules in our user exit).
The problem we are facing is that the idoc in our receiving client is in status 51, even though all data commit to the database tables.I checked the status records, for every segment it says "Infotype nnnn cannot be updated on database table Pnnnn " I checked the entries in T777D as suggested in the message, and everything looks fine.
Has anybody encountered this problem before? Do we need to maintain any settings/configuration for the same? All suggestion welcome!
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma Iqbal
At present I also have to work on ALE for HR Master Data from Production to other systems like Development and Test. I shall appreciate if you give me guideline on how to use the Tcode PFAL.
Thanks
Plavini

Similar Messages

  • Error in idoc status

    hI all,
    can any one tell me "ERROR_WRITING_IDOC_STATUS " why this exception will raise.
    Thanks,
    Prakash .S

    Just check this.
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
            EXPORTING
                 VALUE(MASTER_IDOC_CONTROL) LIKE  EDIDC STRUCTURE  EDIDC
                   " Control record of master IDoc
                 VALUE(OBJ_TYPE) LIKE  SERIAL-OBJ_TYPE DEFAULT ''
                 VALUE(CHNUM) LIKE  SERIAL-CHNUM DEFAULT ''
           TABLES
                  COMMUNICATION_IDOC_CONTROL STRUCTURE  EDIDC
                   "  Control records of created comm. IDocs
                  MASTER_IDOC_DATA STRUCTURE  EDIDD
                   " Data records of master IDoc
           EXCEPTIONS
                  ERROR_IN_IDOC_CONTROL
                   " Incorrect entry in IDoc control record
                  ERROR_WRITING_IDOC_STATUS
                   " Error when writing IDoc status records 
                  ERROR_IN_IDOC_DATA
                   " Incorrect entry in IDoc data records
                  SENDING_LOGICAL_SYSTEM_UNKNOWN
                   " Own logical system unknown

  • Error in Idoc (Status - 51Missing data - HRALX00_ORG315)

    Hi Experts,
    We are getting the below error (Status - 51(Missing data)) when we try to process the Inbound Idoc (SRM) from R/3 to SRM system
    "It has been determined that the employee 00108937 has been received for the first time. However, not all the data that is needed to create a business partner has been received. In this case, the infotype 1001 and the subtype A209 have not been entered for the employee."
    But when I check these Info type in table HRP1001 these values are maintained in R/3.
    Suggest us how to determine the Outbound Idoc for the particular employee in R/3 and the root cause for the error.
    Regards
    Paul

    Hi,
    He pls debugg the outbound IDOC .Below are the steps to be followed.
    1) Put the breakpoint in the FM
    2) Goto the application document repeat the output and save.
    3)Goto program RSNAST00 give the document number and execute.
    Hope this helps..
    Regards,
    Sharath

  • Error Inbound IDoc - Status 51

    Hi,
    i am new in working with SAP and I am trying to integrate an inbound IDoc type WPUBON via WE19 transaction, l solved all the issues related with ports and partner profiles(they were the first errors). But when I want to check if the process has been done well with the WE05 transaction I get two error messages, both of them with status 51:
    The transactions for intermediate document 0000000000052247 could not be written
    Message no. /POSDW/INPUT004
    Document flow: Error reading model data of object relationship se
    Message no. /POSDW/CORE028
    Diagnosis
    Error reading model data of object relationship se
    System Response
    The document links could not be updated.
    Procedure
    Contact your system administrator.
    Procedure for System Administration
    Check the format of the document links transferred to the POS Workbench.
    Thank you very much in advance!!
    Best regards,
    Ander
    Edited by: AAnder on Nov 3, 2010 11:46 AM

    General process for a correct IDOC infrastructure is:
    Create RFC destination  --> SM59 (You can point to local machine for tests)
    Create RFC port to process IDOC  --> WE21 with the RFC create before
    Create FILE port to process IDOC --> WE21
    Create  LOGICAL SYSTEM (BD54)    --> IDOC2FILE
    Define partner in  WE20 with partner type "LS"  --> WE20 ... add message
    RECEIVER port ( created in  WE21 )
    FROM   WE19 GENERAte IDOC with LOCAL SYSTEM as sender And FILE PORT as receiver
    WE19 is  FOR TEST...
    tell me if you can understand, sorry for my english ....

  • IDOC status to sender system

    I configured IDoc within 2 clients in same server, when I send IDoc to receiver it is giving  03 (success) but in receiving system IDoc gives error 51 as some data is not maintained, i am using "Z" function module for inbound IDoc
    question - how to send that same error message to the sender

    Hi Ankush ,
    question - how to send that same error message to the sender?
    I have done the same  requirement . Please find the below Procedure
    -> before ending of the Custom function module  check whether Idoc is Success or  not .
       IF (error)
    LOOP AT idoc_status INTO wa_idoc_status
                          WHERE   docnum =  idoc_data-docnum . "Loop the Idoc Status table
      l_i = 0.
    CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
       id              = wa_idoc_status-msgid
       lang            = '-D'
       no              = wa_idoc_status-msgno
       v1              = wa_idoc_status-msgv1
       v2              = wa_idoc_status-msgv2
       v3              = wa_idoc_status-msgv3
       v4              = wa_idoc_status-msgv4
    IMPORTING
       msg             = l_msg
    EXCEPTIONS
       not_found       = 1
       OTHERS          = 2
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
      l_i = l_i + 1.
      CASE l_i .
        WHEN c_1.
          MOVE  l_msg  TO   wa_zf40-error_msg1.
        WHEN c_2.
          MOVE  l_msg  TO   wa_zf40-error_msg2.
        WHEN c_3.
          MOVE   l_msg TO   wa_zf40-error_msg3.
        WHEN c_4.
          MOVE l_msg   TO   wa_zf40-error_msg4.
        WHEN c_5.
          MOVE   l_msg TO   wa_zf40-error_msg5.
      ENDCASE.
    ENDLOOP.
    ->Now create a Ztable to make the error descrptions.(Matian some Key fields to identify the Idoc .
    ->After this create   a  RFC to read the entries .
    I hope this helps to you.Please let me know  if u have any query.
    Rgds
    Sree M
    Edited by: Sree  Merugu on Mar 27, 2008 6:22 PM

  • Status 29: Error in ALE service : Entry in outbound table not found

    IDoc: 0000000003560240 Status 29: Error in ALE service
    Entry in outbound table not found
    No partner profile (outbound parameter) could be found using the following key:
    /0000000000/LS//YHROT_XXM_IN////
    This refers to the key fields in table EDP13:
    RCVPRN  Partner number
    RCVPRT  Partner type
    RCVPFC  Partner function
    MESTYP  Logical message
    MESTYP  Message code
    MESCOD  Message function
    TEST    Test indicator
    Procedure
    Please check the EDI partner profiles.
    But The IDOC befor this and after this is successfully run.
    And even after reprocessing also it is giving same error.
    After checking Contorl record, we found that there is no data in receipant Info in Partner Tab.
    What would be the issue.
    Please suggest. 
    Thanks & Regards,
    Monika

    Hi ,
    Thanks for your reply.
    We are using one custom message type.
    I would like to give you example of exact scenario.
    Suppose my IDOC has large amount of segments then ,
    It is dividing as
    1st IDOC : Control record ....header and data segments
    2nd IDOC : only data segment
    3rd IDOc : only data segment
    4th IDOC : data segment and Trailer.
    In this way, I am getting all my 4 IDOCs in error.
    What should be d reason?
    your help will be grateful.
    Hi Everyone,
    any update?
    Edited by: Monika.Dhumal on Feb 14, 2012 11:49 AM

  • IDOC Error - Entry in outbound table not found - Status 37

    Hello,
    we try to generate the IDOC in a Test Tool WE19. I always get the same error "Entry in outbound table not found" - Status 37. I tried already many config changes (Partner, Ports, Distribution Modell...).
    The thing is that the IDOC should be sent on external system (non-SAP System) but also the IDOC should be write to file. The external system should later on catch the IDOC and process the data.
    I suppose the problem is the fact that we send it to external non-SAP System. I add as Port Data and the source where the IDOC shoud be generated. The Partner that I choose is logical system. However I dont specify the RFC Connection because the file should only be saved and not send directly on the external system. Is it possible or maybe I need to specify the IP-Adress of the external system?
    When it works I need to generate the IDOC as service management IW32. I try it with TA IORD. I get the message "rejected". Probably because of the error in the test tool WE19.
    I am already fighting on it for many hours...
    Thank you in advance
    Michael

    Hi
    In we 19
    Receiver
    Port: A port created in R/3 referencing RFC dest pointing to XI.
    Partner no: LS of XI (CLNT100)
    Partner Type: LS
    Sender
    Partner no: LS of R/3 (RD1CLNT500)
    Partner Type: LS
    Message Type is DESADV
    Basic DELVRY05
    and i am sending blank idoc for testing.
    Regards
    Monika

  • Confirmation  - error in process - idoc status 29

    HI ,
    i got one new problem today.
    This is one of the case when one user createsconfirmation of the Purchase order and then Confirmation status goes to error in process. i check in RZ20 and found error in Idoc which is generated from that confirmation,When i check the status record it says error in ALE.status 29. Only an inactive partner profile was found with the following key and this is my PRDCLNT100 (production system address).
    I can see that all other confiramtions are getting posted but having an issue with one confirmation.
    2ndly how i can delte error in process Confirmation . So that we can create new confirmation , or is there any other way to get my present confirmation status to Posted.
    Smriti

    Hi Smriti,
    Regarding working on the faulty IDOC
    In WE19 check what Function module will be used to post the data, you can see it when you go to 'standard inbound'. Then you can debug it when you click to the button 'inbound function module', here enter the function module and click 'call in debugging mode' and 'in foreground', then press the button 'enter'. Now you are in the debugger and can check why the error occurs and what should be filled.                                 
    If you know the error number set watchpoint at sy-msgno = *** or just set breakpoint at statement message.
    If this is only happening for one confirmation, the standard approach to delete this is the following.
    Issue:
    The corresponding IDOC for the confirmation document has not been processed successfully and ended with error in the backend.
    Solution:             
    Because of this there is entry left in the table bbp_document_tab,              
    which is not allowing to cancell the confirmation document.                                                                               
    Please find the attached note 338985, which contains the procedure to           
    to delete entries from table bbp_document_tab.
    Hope this helps,
    Kind Regards,
    Matthew

  • ALE Error 29 - Entry in Outbound Table not found

    Hi,
        I am getting the following error in the IDOC  processing.
    IDoc: <IDOC Number>  Status: Error in ALE service
    Entry in outbound table not found
    I have checked the partner profile. It is OK
    I noticed that the IDoc record doesn't have the defined port. The value in the port section is empty.
    The IDoc message type - CRMXIF_ORDER_SAVE_M
    Basic Type: CRMXIF_ORDER_SAVE_M01
    Any inputs will be appreciated.

    Observations -
    I checked the Status records for the IDOC and there are only 2 entries -
    1. 01 IDoc Generated and
    2. 29 Error in ALE Service - Entry in Outbound table not found

  • Getting idoc error - Entry in outbound table not found- in outbound scenari

    hi,
    while generating idoc for outbound idoc to file scenario - i am getting error
    "Entry in outbound table not found" (29 - error in ALE service)
    Diagnosis
    No partner profile (outbound parameter) could be found using the following key:
    /C100/KU//WP_EAN////
    This refers to the key fields in table EDP13:
    RCVPRN  Partner number
    RCVPRT  Partner type
    RCVPFC  Partner function
    MESTYP  Logical message
    MESTYP  Message code
    but already entry has been maintained in partner profiles for the corresponding message.
    same setup is working for other message types. pls let me know what might be the problem

    Hi,
    Check whether partner name is correct or not in WE20/outbound parameters undoer Logical System.
    Regards,
    Sreenivas.

  • IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

    Hi All,
    I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
    Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
    Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
    Error Detail :
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
    This error can have several reasons:
    The segment ZPROSEG is assigned to a group whose header segment does not occur.
    The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
    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 PROACT01 (extension PROACTEX).
    Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
    Below is the Details of the Steps which I have followed:
    1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
    2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
         Here when I run syntax check warning appears "No predecessors exist".  I am not sure if its okay!!
    3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
    4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
    5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
    DATA segnam(27).
    READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
    IF sy-subrc NE 0.
    LOOP AT dedidd WHERE segnam = 'E1EDP31'.
    CLEAR dedidd.
    dedidd-segnam = 'ZPROSEG'.
    zproseg-matnr = 'Mat1'.
    zproseg-lgort = '001'.
    zproseg-gernr = 'SNo1'.
    zproseg-labst = 2.
    dedidd-sdata = zproseg.
    APPEND dedidd.
    ENDLOOP.
    ENDIF.
    Finally ran  transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
    Looking forward for your reply.
    Many thanks in advance.

    Hello,
    Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
    So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
    LOOP AT dedidd WHERE segnam = 'E1EDP31'.
    lv_index = sy-tabix. " <<--
    ADD 1 TO lv_index. " <<--
    CLEAR dedidd.
    dedidd-segnam = 'ZPROSEG'.
    zproseg-matnr = 'Mat1'.
    zproseg-lgort = '001'.
    zproseg-gernr = 'SNo1'.
    zproseg-labst = 2.
    dedidd-sdata = zproseg.
    *APPEND dedidd.
    INSERT dedidd INDEX lv_index. " <<---
    ENDLOOP.
    Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
    So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

  • Regarading IDOC status 26 ,syntax error

    Hi All,
    we have some problem to create IDOC type ORDERS05 for Purchase Order.
    *ERROR STATUS 26:*
    (SYNTAX ERROR IN IDOC (SEGMENT CANT B IDENTIFIED))
    msg number E0078:
    The segment E1EDK14 does not occur at the current level of the basic type ORDERS05 (extension ) AND
       e1edk14 segment missed.instead of 5 ,it shows only 4.
    *ERROR STATUS 26:*
    (SYNTAX ERROR IN IDOC (MANDATORY DATA MISSING))
    msg E0072:The segment E1EDK01 has the attribute 'Mandatory' in the syntax description of the basic type ORDERS05 (customer enhancement ).
    header data was totally different.
    it contains street fields,n country ,,like dat,instead of document number
    However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
    This happens for order create (ORDERS) and for order change (ORDCHG)
    Do you have any idea to solve the problem? I'm using a standard IDOC.

    hi
    Usually posting program contains your logic which exists in process code this process code contain function module nothing but posting program
    and also
    check whether u r using
    1) sap standard program
    2) user defined program
    3) enhancing sap program using user exits
    if it is standard program check all ur ALE settings once again
    if ur using user defined check ur program logic and compare it with idoc structure
    if ur enhancing sap standard program check partner profiles using correct message & idoc type
    check your user exit logic
    reward if u find helpful
    Thanks&Regards
    Nagesh.Paruchuri

  • 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

  • BI extraction error --  Application document not posted - IDOC Status 51

    Hi,
    I am getting the following error while extracting data from ECC to BI.
    'Application Document not posted'
    I went to BD87 in ECC and found that the Idoc Status is 51 and the message is
    'Request REQU_4C65QV...V9QRNZ2X9TV9QRNZ does not exist in target system N05CLNT100'.
    I have already checked partner profile parameters with Basis and they claim everything is okay.
    Do you have any ideas what might be the issue?
    Thanks,

    Hello Rajendra,
    You can review the note 417307 which contain information about the MAXSIZE of a  package size. This is a collective note which contain more notes to other extractors.
    417307 - Extractor package size: Collective note for applications
    549184 - FAQ: What is important for extraction
    157652 - Main memory requirement for extraction from R/3
    You can review the table ROIDOCPRMS and check if the parameter StatFrqu contains a 'X' or a number? You can set this option to 99.
    You can also review the correction note 1147326.
    Check as well if the user ALEREMOTE have the proper profiles configured in both source and target system, sometimes the user is missing the profiles, to check this, read the note 150315.
    I hope that the information can help you.
    Regards,
    Daniel

  • All ALE configuration are right, but why errors in idocs?

    hi any anybody explains why error are occurs in IDOCs when all ALE setting are ok. please explain any scenario

    Hi,
    One of the commonly occuring error status - 26(Syntax error in Idoc) Outbound
    The reason for the occurence of this error is mostly related to the structuring of the segments in the IDoc, the normal structure should have a parent segment followed by the sub segments but in cases when that fails to happen, the Idoc is in 26 status. For correction of this error goto WE30 and check if the mandatory segment is checked.
    status 51(Application Document not posted) Inbound
    This normally occurs due to the incorrect data being populated in the segments or it could also be related to serialization.
    ~Krithika

Maybe you are looking for