Inbound IDOCs to XI triggered from SAP going missing... !!

Hi ,
We have been recently facing issues with idoc messages missing in XI. The IDOC is in status 3 in source SAP system. Running bd75 shows the staus as 12.We do not see an entry in the trfc queue of source system(sm58) to conclude it is stuck in the source system.
Now, the idocs are not visible in IDX5 in XI either and not in sxmb_moni. Is there any other way , say a log/table in XI where we can check to be sure it has not reached XI at all. Or Is it possible that the idoc has reached XI but there is an issue with the Sender IDOC adapter. If its possible , where can we check this idoc is persisted in XI and the IDOC-XML conversion failed ?
Appreciate any pointers!!
Thanks
Saravana

Maybe obvious, but I'd also check <b>ST22</b> in XI.
More, <b>check your network</b>: do a
ping -t hostname > ping_hostname.txt
from XI to R/3 and viceversa, say for at least one hour. Put collected stats somewhere like an excel sheet and check you don't have <i>holes</i>. In that case you need help from network guys (maybe a naughty switch?)
Alex
Message was edited by: Alessandro Guarneri

Similar Messages

  • IDOC is successfully triggered from SAP ECC

    hi,
          IDOC has been Trigerred from ECC Sucssesfully and the status is 03, but it not reached in PI, what will be the error, please do the needful at the earliest.
    Share some more errors where i can stuck with idoc when doing IDOC to File scenario.
    Nissi

    Hi
    Please check the following options:
    1. In SM 58 are you getting any error message, if yes analyse it and correct.Delete the entry and try triggering the IDOC again.
    2.Check the connection test  RFC destination for PI maintained in SAP system, check if the User ID maintained there is not locked
       ,try resetting the pwd .RFC connection works even if the user is locked.
    3. I think you can also check if correct port is maintained in PI IDX1 and also try loading metadata again in PI  IDX2.
    4. Check with sap guys if they have written  Commit in the IDOC program.
    Regards,
    Srinivas

  • INVOIC Inbound IDOC automatically getting triggered during O/B

    Hi Experts,
          As per the req of our client, we are planning to send the sales invoice details to customer by INVOIC IDOC message type. We mapped the fields and tried to execute the INVOIC.
    During execution we noticed that, when ever one "Outbound" IDOC sent then immediatly another one "Inbound" IDOC is getting generated and its going to an error message.
               For example, INVOIC IDOC message type is getting generated for "Outbound" for the customer partner profile we maintained. Immediatly another one "Inbound" IDOC is getting generated for the "Logical system" (Partner type LS). But for this partner we didnt maintained any "partner profiles" in WE21. Even then one IDOC is getting generated with error.
    Any expert feedback on this will help us to resolve our issue
    Regards,
    Nag

    Better check the BD64 and WE20 settings...
    Check whether inbound is defined for any other partner profile...
    Also in WE21 what is the port that is used which is given as the o/p of the outbound idoc in WE20 config...

  • What are the idoc to send data from sap hr to sap fi

    what are the idoc to send data from sap hr to sap fi

    Message type of IDoc depends on the data you wish to send.
    please detail on the data that you need to send in the IDocs.
    regards,
    Nitin

  • IDOC not reaching XI from SAP

    Hi,
    I am trying to fire IDOC (DEBMAS) from SAP to XI. The basic Idoc has been exxtended to add some new segments. The required configuration has been done on SAP and XI side(partner profile on SAP and IDX1/IDX2 on XI).
    However whenever I fire this idoc from SAP, it shows that Idoc has been triggered but am not able to see the same in SXMB_MONI in XI.
    Please let me know if you have any clues

    Hi Anand,
    The monitoring in SXMB_MONI can only inform u about integration engine.
    SM58 errors occur if a RFC destination does not work.
    Also what is the Status Text message you see in the SM58 ?
    Anyways have a look at this Blog....
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

  • Inbound idoc values when updated from user exit not saved

    I'm trying to process some user exits of an inbound idoc from WE19.
    The values get correctly populated to IDOC_DATA internal tables of IDOC_INPUT_ORDRSP function module in debug kode
    but when the new idoc is generated from WE19 , those segment values (populated by exit) are not shown/saved.
    The user exit is EXIT_SAPLEINM_007.
    Is it not possible to populate segment values of inbound idocs from using user exits. If yes , then during testing using WE19 , every time a new idoc is created it should display those values into the concerned segments. Please help.

    Hello,
    yes is possible it ...
    I think the problem is:
    or
    you have something wrong when to append the new line on internal table
    or
    the exit used is not correct: read the documentation on EXIT_SAPLEINM_0**

  • Inbound idoc to R/3 from XI

    Hi ,
    i am trying to post an idoc from Xi to R/3 system . I m using a file system as the input for the idoc and later using a communication channel of idoc adapter type to transfer the idc thus generated to the R/3 system .
    The file syetm i m using is defined as third party system in the SLD and there is a separate business service which is being used for the R3 system .
    But in sxmb_moni  i m getting an error sayin ' Unable to convert sender service to an ALE logical system ' .
    Can somebody please help to solve the problem .
    Thanx ,
    srestha

    Hi Srestha,
    The solutions mentioned below will help you solve your problem:
    - Check if your Logical System Name is maintained correctly in the System Landscape Directory.
    - Go to Integration Directory - > double click on your business system (for file system) -> services -> Adapter-Specific Identifiers..... Here if there is no logical system, Please do give the Logical System name that is maintained in the SLD. if you are giving the Logical system name, do save and then activate the changes made.
    Regards,
    abhy

  • Missing IDOCS from SAP to BODI

    I have an issue of missing idocs from sap going to BODI.
    Idocs are received by BODI trough adapter, but there are idocs that are missing but are successfully sent by SAP. When trying to resend the idocs it was successfully received by BODI.
    We thought that it is an intermittent connection issue, so we try to send idoc from SAP while the adapter was down. The idoc was successfully sent from SAP. Then we try to start again the adapter and it was loaded after sometime.
    Iu2019m now out of idea on why does the idocs went missing. Can someone help me?
    Thanks in advance.

    Hi Parida,
    IDoc Status 03...Green Status... wills not guarantee you that IDoc reached EDI subsystem...
    Run the Program RBDMOIND in SE38...
    Changed on                               :<Date>
    IDocs/Commit Work                   :100
    Display IDoc not sent- Check the Check Box.
    Now you will get list of un posted IDocs
    Ramesh

  • Data flowing into incorrect CC when triggered from a SAP - RFC

    hi Experts,
    I have a RFC to SOAP scenario. Data is triggered from SAP through RFC. Initially, this was done from client 200. Now for the same system there is one more client 210 from which data needs to be triggered.
    I completed the configuration. But when data was triggered from client 210, the communication channel of the client 200 is showing the following error.
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'ECQCLNT200'/'CC_SAP_RFCEproPOSender', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'ECQ#210' returned party/service of ''/'ECQCLNT210')
    The client 210 communication channel is not showing any message. Also no messages are seen in moni.
    Waiting for your replies.

    Thank you for your reply everyone.
    I cleared the cache and now am getting the following error in the communication channel of client 210.
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'ECQCLNT200'/'CC_SAP_RFCEproPOSender', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'ECQ#210' returned party/service of ''/'ECQCLNT210')
    I have created the communication channel under the bussiness system of client 210 and also have created the receiver agreements and sender agreement specific for the client 210. Still getting the error.
    Need your help in solving this.

  • How to create the INBOUND Function Module for INBOUND IDOCs

    Hi Friends,
    Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
    which are recieved from XI Server ?
    I am working in SAP-ISU
    Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
    We have a Standard INBOUND FUNCTION MODULE
    IDOC_INPUT_ISU_MR_UPLOAD
    which Uploads the Meter Reading Results.
    I copied the Same function Module into ZIDOC_INPUT_
    and working on it.
    Can any one suggest me, whether i am going in correct way or not.
    In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
    BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
    My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
    Can I Use the Same BAPI
    BAPI_MTRREADDOC_UPLOAD
    to Update the below fields,
    EABL-SERNR
    EABL-ZWNUMMER
    EABLG-ABLESGR
    EABL-V_ZWSTAND
    EABL-N_ZWSTAND
    EABL-ABLHINW
    EABL-ZSKIPC
    EABL-ADAT
    EABL-ATIMTATS
    EABL-ADATTATS
    EABL-ATIM
    EABL-ZMESSAGE
    EABL-ABLESER(Meter reader number)
    Kindly Suggest me,
    Thanks in Advance,
    Ganesh

    Hello Ganesh
    I think you are going completely astray with you z-function module for IDoc processing.
    If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
    EABL-SERNR => BAPIEABLU-SERIALNO
    EABL-ZWNUMMER =>REGISTER
    EABLG-ABLESGR
    EABL-V_ZWSTAND
    EABL-N_ZWSTAND
    EABL-ABLHINW
    EABL-ZSKIPC
    EABL-ADAT
    EABL-ATIMTATS => ACTUALMRTIME
    EABL-ADATTATS => ACTUALMRDATE
    EABL-ATIM
    EABL-ZMESSAGE
    EABL-ABLESER(Meter reader number)
    Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
    Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
    - BAPI_TE_EABL
    - BAPI_TE_EOSB
    Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
    Regards
      Uwe

  • Inbound Idoc customer number conversion

    I am new to EDI and have a question to ask you both about inbound IDOC's. We have customers sending remittance advices through EDI. The customer numbers in them are their own customer numbers. In SAP, we maintain different customer numbers. Where do the mapping of the customer numbers take place -- In the EDI subsytem itself or in SAP? If in SAP, can you let me know the procedure to do this.
    Any help will be appreciated and points awarded.
    Thanks,
    Nile.

    Hey Fren,
    1. Data Mapping
    Within the framework of SAP EDI, the conversion of a business document in IDoc format to an EDI standard format (and vice versa) is the most important task performed by a subsystem. This process is resource intensive and, hence, is better done at the subsystem level than within SAP. The following conversions and translations are carried out by the subsystem.
    Creating a control record for each inbound IDoc.
    An inbound IDoc must have a control record. The EDI subsystem builds the control record using the information stored in its local repository or from the SAP repository.
    Removing the control record during the outbound process.
    The control record in the IDoc file is used by the subsystem for housekeeping functions, such as locating the trading partner profile. The data on the control record is not needed for translating the content of the EDI documents.
    Translating data from IDoc format to EDI format.
    For an outbound transaction, the EDI subsystem converts data in the IDoc format to a suitable EDI format.
    Translating data from EDI format to IDoc format.
    For an inbound transaction, the EDI subsystem converts data in the standard EDI format to IDoc format.
    Bundling and unbundling IDocs.
    If several IDocs are passed to the EDI subsystem in one file, the subsystem separates them into individual documents. Similarly, on the inbound process the subsystem can bundle multiple IDocs into a single file to improve performance.
    2 Maintaining the Partner Profile
    A partner is defined as the business partner with whom you conduct business and exchange EDI documents. These partners are not necessarily the same as the partners in the partner profile of SAP. However, the concept is quite similar. In SAP, the partner profile maintains parameters specific to the IDoc process, and in the subsystem the partner profile maintains parameters specific to the EDI process. Some typical attributes in a partner profile are
    · A unique partner number
    · The partner type (Customer, Vendor)
    · The standard used (EDIFACT, ANSI X12, and so on)
    · The version of the EDI standard
    · The EDI message exchanged (850, 860, ORDERS, ORDCHG)
    · A functional acknowledgment flag
    3 Triggering the Inbound Process
    After receiving an inbound EDI transmission and creating an IDoc file, the subsystem is often responsible for triggering the inbound process. SAP provides a program named startrfc to start any RFC−enabled function module from the operating system level. For the EDI process, the subsystem uses the startrfc program to
    trigger the function module EDI_DATA_INCOMING. Chapter 6, "Configuring Basic EDI Components," provides the complete details and parameters of the startrfc progam.
    4 Reporting Process Status to SAP
    In an outbound process, after an IDoc has been transferred from SAP to the subsystem, SAP loses control over the process. However, SAP maintains visibility into the process by requiring the subsystem to report on the status of the process. SAP provides a file interface for the subsystem to send a status report at every milestone.
    I hope you got some idea from this process.....
    <REMOVED BY MODERATOR>
    Warm Regards,
    Abhi...
    Edited by: Alvaro Tejada Galindo on Apr 25, 2008 4:36 PM

  • AEDTM + UNAME not filled via HRMD_A inbound idoc

    Sorry if this is the wrong forum but I couldn't find any forum related to IDocs.
    I have an inbound idoc:
    message type: HRMD_A
    basic type: ZHRMD_A0701
    Processing the idoc is working, however, AEDTM and UNAME isn't filled (the fileds are empty). I would assume that those fields are filled automatically with sy-datum and sy-uname. I did some debugging and found the corresponding INSERT:
    IDOC_INPUT_HRMD
    - IDOC_PROCESS_HRMD
      - RH_IDOC_OBJECTS_SAVE
        - inbound_objects_block
          - RH_CREATE_INFTY_PA_PB
            - SAVE_PA_PB_INFTY
              - insert_pa_pb_objects
                INSERT (dbname) FROM <f_prel_db>.
    AEDTM and UNAME are emtpy in <f_prel_db>. Any idea why? Is this a known issue?

    HR inbound idocs actually do not override change date / time (aedtm, uname) with date/ user id of the user who processes the inbound idoc. These info should automatically be populated in the oubound idocs as is from sending SAP system.
    I guess the reason being is this is meant to replicate data (with all original info from sending system) to receiving system. If you notice in the receiving system, when HR inbound idocs are processed, change pointers are not recorded.
    Therefore, if the inbound idcocs are not senf from SAP, these info would need to be populated when outbound idocs are created. Otherwise, you may have to look at inbound user-exit to see if these fields can be populated in the idocs segments.

  • Can inbound Idoc Contain .PDF attachment?

    Hi there,
    I have a requirement where there is a need to create an Inbound Idoc in the CRM system containing a .PDF file attachment.
    1) Can and IDOC contain file attachments?
    2) If yes which segment woult contain it, or how it should be attached.
    The inbound idoc would be created from an XI system.
    Regards,
    Kiran

    Kiran,
    Its not going to be easy. If you plan to use that then
    1. Either you need to have two different interfaces one for the IDOC and one for PDF or design your interface to split that and send as two different messages to R/3.
    2. Moreover do you want to maintain the PDF as it is in R/3? If that is the case, then you might have to write some Custom RFC which can read the PDF and upload the same and attach the doc.
    Regards,
    Ravi
    Note : Please mark the helpful answers

  • Send data to ECC table through RFC Call function from SAP B1 via  b1if

    Hi,
    I have created scenario in B1if which triggers from SAP B1, now I have to send this data in to ECC table, so I have created scenario for that with inbound SAP B1, outbound void and in process RFC Call atom is there but I am not getting data in receiver and also how to write xml to send data in RFC function. Function for RFC has configured from ECC end and have access of that function.
    So please help me to send data to ECC table through RFC Call function from SAP B1 (9.0) via b1if
    Thanks

    Solved by my own.

  • Inbound idoc posting directly even with 'Trigger by background' option

    We have inbound idocs coming into ECC from Siebel via PI. The partner profile is setup for "Trigger by background program' .So that we can run the job RBDAPP01 to sweep these status 64 idocs. But we don't get a chance as the idocs are getting posted directly(its already in status 51 or 53) as if we used the 'Trigger Immediately' option. Where could the problem lie ? Is there a possibility of some RFC call from PI overriding the Partner Profile config ? Any advice or useful tip is welcome!
    thanks,
    S

    Hi,
    I guess you can still check in the control record for EDIDC-EXPRSS - Overriding in inbound processing, the documentation of the Data Element EDI_EXPRSS is as below
    Short Text
    Overriding in inbound processing
    General
    This field determines for ALE whether a time schedule is to be deactivated for inbound processing and replaced by immediate processing.
    Regards,
    Chen

Maybe you are looking for