QRFC inbound issue

I registered RFC destination in tcode SMQS and excuted report RSTRFCT0 in order to create an outbound queue qRFC.
The result is that I can see the queue just created in SMQ1.
However, I can have good understanding about inbound side.
I also registered exact the queue in SMQR and expected to see the relevent inbound LUW underlying this queue. But the fact is I cannot see anything. The list in SMQ2 is empty.
Is there anything I understand in wrong way?
Any help would be appreciated. Thank you.

Yes, I have created queue in SMQR of receiving system with exact name in coordination with the parameter in report RSTRFCT0 , but after exceuting the report RSTRFCT0 in sending system, what I excepted to see in receiving queue didn't appear.
I set the queue with U status and assumed the incoming LUWs would pipe up in that queue but it didn't.  I'm confused.

Similar Messages

  • Messages stuck in QRFC inbound and outbound queues by system error

    Hi Experts,
    We faced a big problem in our PI server which stopped all the traffic in the iDoc to File interface. Both the QRFC queues (inbound - SMQ1 as outbound - SMQ2) where stuck by a system error.
    In IDX5 of PI we saw two inbound iDocs on exact the same date/time of creation. Both iDocs are displayed in SXMB_MONI with the status "Canceled - Since Already Processed". The output files of both iDocs are generetad on the outbound side.
    The output files are genereted with a date/time stamp in filename exactly as: "pi_20101106-221812-437.dat" and "pi_20101106-221812-438.dat". So it seems that both processes where running on exact the same time.
    When looking into the system error we see the following details:
    com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 00505697-181b-1ddf-babd-68f1ac208528(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key
    This caused that the QRFC queues where both stuck in inbound as outbound with a SYSERROR, so PI stopped and the queues should be reactivated manually.
    Does anybody have some idea of the real cause of this error. We really want to prevent such situation in the future.
    Thanks in advance!
    Best regards,
    Joost

    Hi Joost,
    Are you using an adpater module to avoid the same file name processed by the receiver channel ???
    If this is the case change the filename and retest flow otherwise remove the module (ex: localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean) from the channel check it whether the file getting processed or not...
    OR...you have an incorrect module configuration in the receiver channel.
    Do not remove the standard SAP module and make sure that you add additional modules before it.
    cheers,
    Ram.

  • QRFC Inbound processing example using JCo

    Hi Freinds,
    1. I am trying to set qRFC queue for Inbound processing, in order to process on IDoc from external system.
    Queue when I say regsiter, it shwos as status Starting, its not showing active status.
    2. is tehre any JCo example which can be used to comunicate from Java program to qRFC?
    Thanks

    Hi ,
    I have registered qRFC queue name, and able to see records entering in qRFC queue scheduler.
    when I process LUWs in queue, its processing successfully.
    I am not able to understand the behavior of QueuePosition now.
    I tried with queuePosition 2,1,3,2
    but,in the queue, when I see records, ther are entered with time, not with queue position number.

  • WRT54GC Inbound Issues

    Hi
    I have been using the WRT54GC for over a year at our office. We're in a daisy chain setup with the WRT54GC as the DHCP controller andtwo other routers/hub with closed down DHCP to connect additional computers.
    Internally everything works fine. But we have recently installed a mailserver and VPN on our server. These both work fine but since we have a cable modem, we need to use a dynamic IP service (I use dyndns).
    I recently upgraded the firmware to the latest version as well since there was an update to the dyndns client in it. Arouynd the same time, we started seeing heavy usage of our mail server (meaning we actually rolled it out to end-users in general).
    But since that time, the router seems to "loose" inbound connectivity. I use both dyndns and no-ip as a backup service but the router seems to start rejecting inbound connection after 2 or 3 days now no matter which route I choose (eg: both no-ip and dyndns).
    This is becoming an issue as we use rpc through http for laptop users to access thgeir e-mail and we need to unplug the router from the wall for it to "route" itsef properly again.
    I have not used the reset switch yet as I have plenty of port info I'd rather not have to set up again.
    Any help on this issue would be greatly appreciated.
    PS : Internally, the network continues to work as it should, the router just seems to start rehecting connections all of a sudden.
    PSS : The server has a static IP obviously and is plugged into the WRT54GC and not into another part of the chain.

    Following this post I did a reset of the router to no avail. Is there anyone who could help out ?

  • PO Creation Using IDOC ORDERS05 - Inbound Issue

    Hi Experts,
    I am new to the ALE/IDOCs. I am trying to create a PO in one client and trasnferring it to another client using the IDOC extension. I am using Message type ORDERS and Basic type ORDERS05 (Extended). I have craeted Partner Profile for both Inbound and outbound in their respective clients.From Outbond the Purchase order is sent successfully to the Port. On the inbound the PO is failing due to incorrect function mudule chosen for processing through process code. I have tried process codes like ORDE,ORDS,DELO and ME11.
    Please Let me know the corrects process code in the inbound, to process IDOC as PO.
    If i need to go for all together a different mesasge type. Please give me all the relevant details like BASIC type, Process code in Inbound and outbound . And i want the BASIC type to be extensible.
    Thanks,
    Murali

    Hi,
    In the inbound side create a new entry in WE57 tcode.. with the functio mdoule as "IDOC_INPUT_ORDERS", basic type "ORDERS05", extn< specify the extn u created at outbound side>, message type "ORDERS". Now see if it is working.
    Regards,
    Nagaraj

  • Regarding inbound issue

    Hi all,
    Like, for outbound we use the port in the partner profile as a receiver port.
    but for inbound idoc where, we use the defined port.
    Regards
    krishna

    >
    Murali Krishna Makineni wrote:
    > Hi all,
    > Like, for outbound we use the port in the partner profile as a receiver port.
    > but for inbound idoc where, we use the defined port.
    >
    > Regards
    > krishna
    Hi Krishna,
    Define segments: WE31
    Create new basic idoc type: WE30
    Create message type: WE81
    Link message type to IDOC basis type: WE82
    Create RDC destination: SM59
    Create logical system: SALE
    Create port: WE21                                 "Declare Port
    Create partner profile: WE20                  "Add port to Partner profile
    Set up distribution model (If necessary): BD64
    for indound and outbound we define port at same areas in we21 but we will mention the whether it is outbound or indound...
    regards,
    Prabhudas

  • Time limit exceeded in inbound qRfc

    Hi all!
    Please I need your help with this timeout issue. I have the following scenario:
    FTP --> XI (Java mapping) --> R3 (Idoc)
    Where from that Java mapping I do some RFC's to R3 in order to make conversions and validations.
    When I test this interface in development environment with a 1Mb flat file, it took 5 minutes to process. However, i did the same test in QA environment, it took pretty much more than 5 minutes and I got this "time limit exceeded" in the qRfc inbound queue (sxmb_moni t-code).
    I was told that the hardware beneath development and QA are different but theorically, the later should be faster.
    Anyone has any suggestion to resolve this? I will really appreciate it.
    Best regards!
    Vanesa.

    Hi,
    have a look on this doc called "HowTou2026 Investigate Timeouts in Synchronous XI/PI Scenario"
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747
    You will certainly find your answer.
    Regards.
    Mickael

  • Missing material line in Inbound delivery

    Hi All,
    Outbound delivery and inbound delivery are created successfuly, but in the inbound there is no material appear.  There is only 1 material in the outbound.  What is the cause of the issue and how to fix the inbound issue?
    Thanks.

    Hi,
    I guess this is not the correct forum to post question on functional stuff. you can put this may be eaither in ABAP General or BPX forum.
    Thanks,
    Chandra

  • Difference between TRFC and QRFC

    Dear all,
    i understand that TRFC functions as EO and QRFC functions as EOIO.
    but can anyone of u pls make me understand there significance with a practical example :
    1. in terms of XI
    2. without XI when we say that one R3 is connected to other with say TRFC or QRFC
    pl help

    Hi! Tarang,
    I just adding few points in this forum...Actually your question and some of the answers given are different .Some of them are deviating the topic.
    According to my knowledge and as per SAP documentations also I am adding these points. Correct me if I am wrong.
    At first QRFC , TRFC are different from the BE, EO and EOIO because trfc are message protocols and BE , EO and EOIO are nothing but Quality of Services (QOS).
    You can check this in the below URL::
    http://help.sap.com/saphelp_nw70/helpdata/EN/0d/5ab43b274a960de10000000a114084/frameset.htm
    QOS is one of the property of TRFC's.
    1) See Got o SMQ1 an SMQ2 what you will found:: ?
    QRFC Monitor Outbound Queue and QRFC Monitor Inbound Queue. both Queues QRFC s common.ok its a simple thing.
    2) Also lets take IDOC Adapter for IDOC whether it may be File to IDOC or IDOC to File Scenario where you will monitor the IDOC in SM58 also right ? why because this TRFC's are mainly for communicating with one SAP system to another SAP System. IDOC is mainly sending data via TRFC ports. That is why you ill monitor the IDOC if data doesn't reached means in Transaction COde:: SM58.
    3) QRFC Outbound and QRFC Inbound is mainly for communicating with SAP System and Non SAP Systems. Okay you can get this information in the below further explination and link.
    Note::qRFC communication is an extended form of tRFC communication. It adds a serialization concept to the transactional concept of tRFC.
    http://help.sap.com/saphelp_nw70/helpdata/EN/3b/befa40badbf46fe10000000a1550b0/frameset.htm
    Some applications use qRFC with outbound queue to improve system performance and not for serialization. If this is the case, you can switch automatically from the qRFC LUW with outbound queue to the tRFC LUW to avoid a hanging queue if a SYSTEM_FAILURE occurs
    Note:: To cancel a background job if tRFC errors occur use program RSARFCEX to restart tRFC.
    First What is the purpose of RFC:: ?All types of applications are instructed to communicate with other applications. This communication may take place within an SAP system, with another SAP system, or with an application from a remote external system. An interface that can be used for dealing with this task is the Remote Function Call (RFC).  RFCs can be used to start applications in remote systems, and to execute particular functions.
    There are 3 types of communications::
    Communication within an SAP system or with a remote system can take place using Remote Function Call (RFC). This enables the following scenarios:
    ·      a)  Communication between two independent SAP systems
           b)  Communication between a calling SAP system and an external receiving system
           c)  Communication between a calling external SAP system and an SAP system as the receiving
                system
    Features of the Three Communication TypesTo help you decide which communication types you need to implement according to your system landscape and your requirements, the advantages of the three types of communication are explained below:
    ... 1)      tRFC
    Suitable only for independent function module calls; the sequence of the calls is not preserved
    ·   2)   qRFC with outbound queue
    Function modules in a queue are guaranteed to be processed only once and in sequence (serialization). Also suitable for communication with non-SAP servers.
    ·   3)     qRFC with inbound queue
    The function modules created in the outbound queue are transferred from the outbound queue to the inbound queue; the sequence of the function modules is preserved. An inbound scheduler processes the inbound queues in accordance with the specified resources. Both the client and the server system must be SAP systems. One work process is used for each inbound queue.
    http://help.sap.com/saphelp_nw70/helpdata/EN/3b/befa40badbf46fe10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/e7/555e3c0f51a830e10000000a114084/content.htm
    XI point of View...
    Basically Once the TRFC or QRFC is funtion is over XI will place the Message into the Adapter engine queues based on the Comminication channel configuration.
    Suppose if it is and EO then XI ill place the message in any  Queue based on the free and priority and if configuration is done as per EOIO then XI ill place all the messages in the Same queue name so that it ill processes in order one after another and if the above message fails and remaining all other messages will be in the queue and doesnt process untill the failed mesages gets removed
    But in case of  EO it may be places in any queue and if one message fails then another message of same interface may processed sucessfully based on another queue order.
    I hope it wil be helpful to you...
    Regards::
    Amar Srinivas Eli

  • Inbound idoc sales order error status 51

    hi,
    am getting inbound issue with status 51,
    means in same client with difeerent systems like client 100 and sender system in client side
    and receiver system offshore side.
    sender system having company code 001, and sales organization ip01, distribution chennel 10,
    receiving system have different compay code and sales organization.
    while getting sales inbound it will the status 51 like company code(bukrs), sale(vkorg), channel (spart)
    could not be determind.
    after that i have debugging use the transaction we19.
    finally it giving status is 62.
    how to correct the issues.
    anybody pls send proper functionalities.

    Hi Sathish,
    First of all for creating a Sales order the Customer should be part of the Company Code and Sales Area ie Sales Org, Distribution Channel and Division.
    If that combination is not present then you cann't create a slaes order.  You cann't create a Sales Order with the help of ALE configuration unless and until and the sender system can send the sales org, distribution channel and division of the receiver system inorder to send this kind of information from the sender system you need to write lot of code in the sender system.
    Thanks,
    Mahesh.

  • Inbound idoc sales order error

    hi,
    am getting inbound issue with status 51,
    means in same client with difeerent systems like client 100 and sender system in client side
    and receiver system offshore side.
    sender system having company code 001, and sales organization ip01, distribution chennel 10,
    receiving system have different compay code and sales organization.
    while getting sales inbound it will the status 51 like company code(bukrs), sale(vkorg), channel (spart)
    after that i have debuggin use the transaction we19.
    finally it giving status is 62.
    how to correct the issues.
    anybody pls send proper functionalities.

    Hi Sathish,
    First of all for creating a Sales order the Customer should be part of the Company Code and Sales Area ie Sales Org, Distribution Channel and Division.
    If that combination is not present then you cann't create a slaes order.  You cann't create a Sales Order with the help of ALE configuration unless and until and the sender system can send the sales org, distribution channel and division of the receiver system inorder to send this kind of information from the sender system you need to write lot of code in the sender system.
    Thanks,
    Mahesh.

  • QRFC example using JCo

    Hi Friends,
    I am Looking for an example to make qRFC inbound call to SAP, using JCo API.
    Please helpme if you have any JCo example for the same.
    Thanks.

    Look here:
    Re: qRFC list of inbound queues
    http://help.sap.com/saphelp_470/helpdata/en/ee/fa5f3c90de2d73e10000000a114084/frameset.htm

  • Setting QRFC Queue Status to STOP

    Hello
    We will be scheduling reports in Prod to auto restart stopped outbound and inbound QRFC queues. But before implementing these changes we need to know if these reports are working fine TEST environemnt. Can anyone recommend us a way of setting the Status of QRFC queues to STOP.
    Thanks.
    Kiran

    Thanks everyone !!
    We executed a simple scenario where we selected the Sender SOAP of the type EOIO which enabled us to define a specific queue e.g. TEST_QUEUE. In the Receiver SOAP we entered incorrect usrr id which caused the messages to be blocked in the queues. Once that was done we again reset the password to the correct values and ran our reports to restart QRFC inbound queues which helped us verify the auto restart of queues.
    Best Regards,
    Kiran

  • Async RFC - File - EOIO

    I have the following XI Scenario:
    Async RFC (R/3) -> XML File (Filesystem)
    I want to achieve a QoS of EOIO. I know that the RFC Adapter doesn't support this but I would like to see if there is another way of achieving this:
    Assumptions:
    - XI is SP16
    - No ABAP proxies because R/3 is 4.6D.
    - XI receives the data in the correct order because we've implemented qRFC outbound queues in R/3.
    - The QOS in XI ends up being EO because the RFC Adapter doesn't support qRFC (inbound queues).
    Questions:
    1) Is there a way to "force" EOIO on these incoming messages without using BPM? They are already being received in the correct order. The issue is that XI can process them in any order because the QOS is EO.
    2) Is it possible to use BPM to do this? Here's one idea similar to what I use to collect IDocs.
    There's no collecting in this case, but by using a receive step in a loop to handle multiple calls, it guarantees that only one instance of the BPM will be running at a given time.
    Loop
    - Checks a counter < 100 which allows us to set a maximum # of calls that the BPM will handle. This is so the workflow log doesn't get to big to view.
    Inside the Loop is a Block:
    - Contains deadline branch - 1 minute from 'Creating the Step'.
    - If the call sits in the block for more than a minute (aka if we haven't received anything in a minute) call the deadline branch
    - In the deadline branch throw an exception
    - In the exception branch quit the BPM
    Inside the Block is:
    - Receive Step
    - Increment Counter
    - Send Step with EOIO (SP16)
    3) Will the calls be sent to this BPM in the order that they were received or will they be sent to the BPM in any order since they are EO?
    Any ideas or comments on this approach will be appreciated. Points will be awarded.
    Thanks,
    Jesse

    Krishna,
    > <i>3) Will the calls be sent to this BPM in the order
    > that they were received or will they be sent to the
    > BPM in any order since they are EO?</i>
    > >>Yes.. this depends on , how and which order XI is
    > receiving the message..
    The IE receives the messages in the correct order because we make the RFC call asynchronously (tRFC) and use a qRFC outbound queue.
    > Now my question is , what is the idea behind to
    > achieve the EOIO here? How is the RFC triggered here?
    > Is it scheduled ? Whatever, at a time only one
    > message will be sent right from R/3.. So what is the
    > purpose/possibility of the multiple messages will be
    > coming from the R/3..
    We need EOIO because the RFC calls contain changes to R/3 records. If the calls are processed out of order, the data will get out-of-synch in the receiving system.
    The RFC is triggered nightly and real-time on demand. There are typically multiple RFC calls (each with 1000 records) coming from R/3 within a few seconds (configurable) of each other. Even if there weren't multiple calls, if XI is down or a message fails, the IE could process them out of order when it comes back up because they're EO.
    Essentially, I can get the messages to the IE in the correct order. I just need to process them in the correct order from that point forward.
    Are you saying that the BPM (with a loop) will definitely pick up (receive) messages in the order that they are sent to the IE? I think this is critical to this approach working.
    Alternatively, is there anyway to change (hack) the SOAP header using an adapter module to switch it from EO to EOIO?
    Thanks,
    Jesse

  • Initial customizing loads (DNL_*) causing short dumps in R/3

    Hi,
    I'm trying to run the initail loads for the DNL_* customizing objects.  When I start a load in R3AS and check the status in R3AM1, it shows "Running".  In the CRM oubound queue (SMQ1), there is an entry for the load with status SYSFAIL.  The detailed status message is "The current application triggered a termination with a short dump". 
    The short dump in R/3 shows an error "No external system (such as CRM) connected" which occurs in function module CRM_FIRST_CALL_OPERATIONS.  Looking at the code, there seems to be a problem with the CRMRFCPAR table.  I had only one record in this table for object CUSTOMER_MAIN, so I tried adding a record with Object Name "*" and Load Type "I", but this had no effect. 
    What is the proper configuration of table CRMRFCPAR for customizing loads?  Is it possible that this error is related to some other config or a problem with the RFC connection?  These loads work fine in our quality system which is configured the same as production (as far as I can tell).
    Thanks.
    Martin

    hi,
    Maintaining Table CRMRFCPAR (SAP R/3)
    The parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.
    You can send data to a certain consumer only in an initial download and not in a delta download by making the appropriate specifications for the data exchange.
    User- That uses the OLTP plug-in functions as data receivers
    Object name -Object name
    Destination -Specifies the destination of the CRM server
    Load Type -Restricts CRMRFCPAR entries to the initial (I) or delta (D) download.
    Out Queue - Name RFC outbound queue
    In Queue -Name RFC inbound queue
    BAPI name
    INFO -Information/Comments
    InQueue flag- Controls whether qRFC inbound queues are used on the CRM server
    Send XML -XML supports (Should data be sent in XML format?)
    Stop data -Causes the OLTP System to place data into the outbound queue.
    Regards
    sri

Maybe you are looking for