File to idoc  (Idoc is not getting posted in R/3 system)

Hi Experts,
I am having file to idoc scenario. In sxmb_moni i have seen success messages . The flag is checked on both sides.
So when clicked on the right hand side there are 443 idocs.but idoc is not posted on r/3  side.  when i give the idoc number in r/3 system in we09 i couldnt find it? soi went for bd 87 transaction and gave the idoc number. it is saying that idoc is strucked in qrfc queue?
Kindly suggest.
Thanks in advance.
Regards
sai

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

Similar Messages

  • FI - Interface triggerring multiple idoc is not getting posted

    Hi all,
    I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
    now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
    But the same idoc, when i proccess indivisually get's process gets posted successfully.
    I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
    As an abaper, I am not able to understand problem to take corrective steps.
    Thanks & Regards
    shashikant

    hi,
    if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
    please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
    let us know.
    Rodrigo P-.

  • Idoc not getting posted into XI

    Hello Experts,
    I am trying IDoc-XI-File senario...
    I have configured, ALE on backend system. Configured IDX1 and IDX2 in XI system.
    At sender the Idoc has been sent without any errors.
    But when I check in XI using SXMB_MONI there are no messages. Idoc is not getting posted into XI.
    Please suggest as I am struck at this point. I am using XI 7.0
    Thanks
    Suma

    Hi,
    Kindly verify the ALE steps that you have performed...
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    Step 6)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 7)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    Reward points if helpful...
    PrasHaNt

  • Plz Help:Idoc not getting posted

    In my requirement some of the idocs are not getting posted.The error message is "Balance not zero".Idoc type is "INVOIC01".In my requirement they told to look into the standard sap pgm"SAPLMRMC" in that FM MRM_AMOUNT_COMPARISON.Please give me suggestions to proceed.

    Hi Hema,
    Please check the invoice data that your are trying to send. From the error it seems that the IDoc is failing the data validations that must be placed in the program/FM that is used to generate/post the IDoc.
    Regards,
    Ashwinee

  • IDOC Not getting Posted in PI from CRM

    HI All,
    I had Configured,
    in CRM side : SM59,WE21,BD54,WE20
    in XI side: datatypes,MT,MI, Maaping not yet done, IDX1,SM59
    Idoc is not getting displayed in XI system.
    I had a small Question, Do we need to Configure all the setting in XI for Getting IDOC from CRM.
    Thanks in Advance,
    Sriram.

    Hi Jag,
    Thanks for the reply.
    1.CRM: go to Tcode-WE81 and check message type CRMXIF_PARTNER_SAVE created?
    Yes exists
    2.CRM: Execute Tcode-WE82, Check message type CRMXIF_PARTNER_SAVE has relevant IDOC type and version.
    yes both message type and basic type exists
    3.XI: Did you import right Message type and IDOC type in to IR in XI?(name will be like Message_type.IDOC type)
    yes imported CRMXIF_PARTNER_SAVE.CRMXIF_PARTNER_SAVE01 in IR.
    When i see in Table EDMSG in XI system i am not finding the value CRMXIF_PARTNER_SAVE, but this value Exists in CRM system
    in XI i m not finding the message type in WE81 and WE82.
    Thanks in Advance,
    Sriram

  • Urgent IDOC -  EXIT_SAPLLMDE_002 not getting triggered.

    I am doing an inbound idoc on message type WMMXY goods movement.
    The idoc is sucessfully getting posted when tested through we19.
    But the user exit  EXIT_SAPLLMDE_002  where i am doing an enhancement is not getting triggered when the idoc is posted.
    I have activated the exit functional module, the project in CMOD is also activated.
    Some one pls help me .. if u have its document pls post it to me.

    Hi,
    Please refer to this documentation of user-exit; may be of some help for you.
    You can use this user exit to influence the processing of IDOCs of the
    message type WMMBXY (goods movements) that are sent to SAP from external
    systems via the MM-MOB or WM-LSR interfaces. You can also access
    customer-specific processing in this case.
    Call transaction and other important requirements
    The user exit is performed in the function module that processes the
    IDOCs of the message type WMMBXY, after the IDOC is withdrawn and
    checked but before direct processing in the application has been
    initiated. (That is, the data for the goods movement has already been
    determined and edited, but the function module for updating this has not
    yet been accessed. The standard function module for processing the
    message type WMMBXY is called L_IDOC_INPUT_WMMBXY. The IDOC is processed
    in an update task, which means that the source code is also executed in
    the update.
    If an error arises, then messages should not be issued since processing
    is being carried out in the background and the result of processing must
    always be returned to the ALE interface. For this reason language
    elements such as MESSAGE, COMMIT WORK, LEAVE and the like should not be
    used. If errors that should be passed on to the ALE interface or that
    affect the result of processing are found in the user exit, you should
    also use the user exit MWMIDI07(EXIT_SAPLLMDE_001) since it alone can be
    used to take your errors into account (see documentation of the user
    exit).
    Parameters and options
    The user exit in the program is the function module EXIT_SAPLLMDE_002.
    In order to be able to use it, you must first create Include zxlidu10
    and activate the enhancement by means of transaction CMOD. As
    parameters, you can use the following data:
    o   Goods movement data already determined from the received IDOC:
        -   Transaction code that is given along with the application
            function module (see interface description (import parameter
            X_TCODE).
        -   Indicator: post only if all items o.k. (import parameter X_XALLP
            ). This indicator must be set by default, to enable IDOC error
            processing.
        -   Indicator: Reset all tables (as primary call) (import parameter
            X_XALLR). This indicator is not set by default to enable the
            processing of several IDOCs. Normally you will not change these
            two indicators.
            -   Goods movement items table (table parameter T_IMSEG)
        o   Received IDOC data:
            -   IDOC control record (import parameter I_IDOC_CONTROL)
            -   IDOC data records (table parameter T_IDOC_DATA)
        This user exit can be used to:
        o   Influence the determined data for the goods movements. All data can
            be changed in this case.
        o   Analyze and process data that is transferred using customer-specific
            segments.
        o   Access additional activities.
        Examples
        A number of potential applications are described below.
    A number of potential applications are described below.
    o   You want to inform a user by mail when the goods movements of
         certain vendors or customers take place.
    o   You want to start your own label printout, for example at goods
         receipt.
    o   You want to update your own tables, for example statistical data.
    o   You want to analyze a missing parts table at goods receipt and
         redirect the goods receipt correspondingly.
    Reward points if helpful.
    Regards,
    Pankaj Sharma

  • IDOCS Error - Not getting processed automatically

    Hi All,
    We are loading hierarchy for a Product from R/3 system using the standard datasource.
    When we execute the info package, IDOCs are not getting processed automatically.
    We are facing the below error message.
    Error when updating Idocs in Business Information Warehouse
    Diagnosis
    Errors have been reported in Business Information Warehouse during IDoc update:
    No status record was passed to ALE by the applicat
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
    Error handling:
    How you resolve the errors depends on the error message you get.
    But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
    Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
    Thanks in Advance
    Regards,
    Sachin

    Hi,
    This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
    Hope it helps a lot.
    Thanks and Regards,
    Kamesham

  • For the new delivery type created the Idoc is not getting triggered

    Hi All,
    I am facing the following problem:
    For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
    Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
    The Idoc being used is:   DESADV01
    Message type :DESADV
    Thanks,
    Geeta

    I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

  • IDOC - EXIT_SAPLLMDE_002 not getting triggered.

    I am doing an inbound idoc on message type WMMXY goods movement.
    The idoc is sucessfully getting posted when tested through we19.
    But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
    I have activated the exit functional module, the project in CMOD is also activated.
    Some one pls help me .. if u have its document pls post it to me.

    I am doing an inbound idoc on message type WMMXY goods movement.
    The idoc is sucessfully getting posted when tested through we19.
    But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
    I have activated the exit functional module, the project in CMOD is also activated.
    Some one pls help me .. if u have its document pls post it to me.

  • Files are not getting posted in destination directory,how to trace in XI

    Hi,
    our scenario is proxy to file.
    We are posting files of .TRG and .DAT format in destination directory.Due to less space in destination directory, files only .TRG files are getting posted but .DAT are not getting posted.but i have checked in XI system SXMB_MONI,no error message is coming.message is getting processed successfully.
    why it is not visible and to monitor that files are not saved at the destination.
    Is this normal with XI that we can not see of files are really saved?

    Hi,
    > it should generate two files as per scenario but only one file is getting generated due to less space,
    NO.
    If  No  Space, The error will pops  out  in RWB  .
    Check the directory of the File Adapter  you are using
    Regards
    Agasthuri Doss

  • Data is not getting posted in ABAP Proxy.

    Hi,
    I am working on File to ABAPProxy scenario. The data is not going to proxy.
    In PI sxmb_moni is status is successfull and in the R3 sxmb_moni the status is successfull. But the data is not getting posted in the tables(ABAPProxy). I had checked the inbound and oubound queues. And with the same input data, abapers cheked their code in Abapproxy, then the table is getting updated. When we trigger from PI, the tables are not getting updated.Please help me.
    Thanks,
    Pragathi.

    Hi,
    The problem may be
    Case 1: Cache is not getting refreshed(Check SXI_CACHE)
    Case 2: The Queue Is blocked (Check SMQ1 & SMQ2)
    Regards,
    Sainath

  • Invoice is not getting posted to accounts it is showing the export error

    invoice is not getting posted to accounts, it is showing an error of foreign trade / export data. where as it is with in the country. it is maintained for the plants abroad stock transport order.

    A stock transport order to a location overseas etails crossing national borders and change of legal regulations. hence you need to maintina FT data. Please check the FT data in the billing header and item and maintian them. They are simple items like customs offices meas of transport...
    This will give you a green status from the red status you will initially have. Then you can post the invoice.
    regds

  • Controlling Document Not Getting Posted

    Dear All,
    We have a peculiar scenario of Controlling Document not getting posted. Any pointers on wat could be the issue will be highly helpful.
    Scenario:
    We have an interface which posts an accounting document.
    Dr. Expense
    Cr. Balance Sheet.
    The Cost Center is supplied thru the interface and FI document and Profit Center Document is posted without any issues. However, CO document is not generated, not sure wat could be the issue. We have performed the basic checks. Also, for the same expense account, we observe some postings have gone into CO where are some didnt'. The difference between documents posted with corresponding CO and documents without corrsponding CO posting is only the "Transaction Key". When we maintain blank Transaction key.. the system posts CO document, when transaction key is "WRX" for that specific GL the system doesn't post.
    Not sure why Standard SAP behaves like that. Please advice wat items i need to check to resolve
    this.
    regards
    Diwakar

    Hello,
    Make sure in OBYC, for key WRX, you have maintained the GL accounts.
    Regards,
    Ravi

  • COPA Documents not getting posted - Doc with unauthorized busi.trans SD00

    Dear Experts,
    COPA Documents are not getting posted, although billing /accounting documents are getting posted
    We are getting the below error message,  when KE4ST is executed
    Kindly share your inputs for this issue
    Document with unauthorized business transaction "SD00"
    Message no. KE/AD604
    Diagnosis
    Document 6000000026 cannot be transferred to Profitability Analysis (CO-PA) because the business transaction"SD00'"(Billing document) is not profit-related.
    System Response
    The document is not posted to CO-PA.
    Procedure
    If you decide that the document does contain data relevant to CO-PA and that it therefore should be posted to CO-PA, change your Customizing settings accordingly. Otherwise you can ignore this message.
    Advance Thanks,
    Sanjai

    Hi,
       1. First please check if COPA is active in the system i.e. tcode KEKE
       2. Then check if operating concern is active in tcode KEA0
       3. If so then check if billing document has an account assignment to PA segment. If not then maybe you have changed the account assignment in OKC9.
       4. If all the 3 conditions above are satisfied then you need to check if this is a made-to-order scenario (MTO). A made-to-order scenario can be identified in COPA in that the billing doc will have an account assignment to a sales order in addition to a
    PA segment (field vbap-kzvbr = 'E' and vbap-vbelv = sales order no).
      If the above conditions are satisfied then from a COPA point of view it is a MTO. In this case the invoice will be assigned to the sales order and will not be directly transferred to COPA. With the order settlement the costs and the revenues (invoice) will then be posted to COPA.
    regards
    Waman

  • Urgent:TimeCard entries thro TimeKeeper not getting posted

    Hello,
    We are creating TimeCards for a set of employees thro TimeKeeper,however this is not getting posted although we run the following programs
    1.Transfer time from OTL to BEE
    2.Validate for BEE
    3.Transfer to BEE.
    TimeCard is in a Approved State and there are no errors.
    Can somebody pls advise what needs to be done?
    Regards,
    Gayatri

    Hi Ramu,
    Thanks for the response.
    We are able to xfer successfully from SelfService to HRMS and neither the time Card is locked when we transfer from Timekeeper.
    So can you pls tell me if there is any other issue?
    Regards,
    Gayatri

Maybe you are looking for

  • Checking the actual instance of reference, like "instance of" in Java

    Hi All, I have a method that has the ability to return a number of Z exception class types.  All of these exception classes inherit from the same super Z exception class.  This means that when called the callee only needs to catch the super Z excepti

  • Itunes 11.3 won't recognize ipod 5th generation

    Itunes will not respond to my ipod touch 5 generation after I installed the latest update for the itunes software/program (itunes 11.3). However, my computer (Windows 8 PC) is able to detect my ipod. I've been searching the forum like crazy and tryin

  • HP LaserJet 500 support on HOST-RESOURCES-MIB

    Hi, We've various HP printer install in our campus.  I've tried to enable snmp in one of the HP printer ( e.g.  HP LaserJet 500 color M551).   Our goal for the HP printer is to have them response the SNMP "hrDeviceDescr"  under the HOST-RESOURCES-MIB

  • HT1549 How do I install software from a cd in remote computer on the network.

    I have a new software program(on CD/dvd) I want to install on my new mac.  My old mac has a cd/dvd drive.  How do I install the program on my new computer from my

  • Problem with TLF - floating an inline image

    I am running the latest version of Flash Builder 4 (4.0.1).  The problem that I having: When I use an InlineGraphicsElement if aTextFlow (in a RichEditableText component), if I set a value for the "float" attribute of an <img> element; the image is n