RFC adapter for two BAPIs

Hello,
I need help to call two BAPIs in RFC Adapter. My scenario is I am getting message from third party system. By default I call a BapiX to create a deal, Then I have to call another BapiZ for commision.The thing is first I have to create it by calling BapiX and BapiZ from one message which I am getting to XI.
What is best way to do it. In XI is there any way to do this.
I am not sure do i need to use DB lookup in the mapping.
Or do i need to use RFC wrapper to put these two BAPIs.
Thanks,
Srinivas

Hello Amit,
I am just confused. I am using RFC adpter on reciever side.
You mean You want to use BAPI message type for the interface and create ABAP Server Proxy.
Now how can i define other RFC message type OR you want me to call other BAPI (Pasting the BAPI code)in the Server Proxy Code.
By the way i am using synchrnous call.
Thanks,
Srinivas

Similar Messages

  • Looking for two BAPIs which will provide me specific BI information

    Hello,
    I am developing something from the Java side and I am looking for two BAPIs which will provide me the following information regarding our BI:
    1. a BAPI that by giving it a userid will provide me a list of the ODSs the users has access to.
    2. a BAPI that by giving it an infoArea will provide me the list of ODSs inside this infoArea. Here, all I could find was BAPI_ODSO_GETLIST which gives me all the ODSs in our Business Wearhouse in all infoAreas.
    Thank you in advance,
    Roy

    hello Maxwell ,
    hhave a look at tcode BAPI , under MM application area.... u will get all BAPIs related to MM modules.
    Identify if a quotation number exists in the system which a specific sales organization.
    Determine the sale price of a material for a specific customer-->u need to ask your functional consultant , may be he is creating info record for that one?
    A simplier way to identify the plant specific status of a material without using the MATERIALGETALL-->use table MARC
    Identify if a specific customer used a supplied purchase order before.
    Identify if a customer has been placed on credit hold-->i think u can make use of tcode vkm4 or custome master data will have all these info.
    regards
    Prabhu

  • Error when RFC adapter calling the BAPI

    Hi freinds
    Today when I was executing my scenario ( File -- XI -- RFC ), I got following error ::
    Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_BAPI_POS_AUTOMATION in remote system (RfcClient[RFC_Connection_SAPR3_DEV]):com.sap.mw.jco.JCO$Exception:(104) RFC_ERROR_SYST
    Before this error I executed my scenario 2-3 times without any errors.
    I found that in RWB the message status was "Waiting". SO I checked the Component monitoring & found this error in Self Test Status ( the symbol was RED )-->
    java.lang.ArrayIndexOutOfBoundException: -1  ( Not copied from the original error message )
    I clicked the "Repeat Self Test" button & the status become green so I checked my message again. Now it was successfull but in 2 retries it was giving the JCO error & after the Self test ( 3rd retry) it went fine.
    I didn't change anything else other than Self test.
    This happened two times with me today. Can anyone tell me the reason behind this & what will be the permanent solution of
    this. Is this related to some memory dumping ? Is their anything like clearing memory for adpaters in XI.
    Best Regards
    Lalit

    Could you pls check whether a short dump occured in the target system.
    Go to ST22 in the target system and check.
    Thanks,
    Renjith

  • RFC Adapter for multiple clients

    Hi All
    I have a situation where we have a Dev client (030) and a Test client (041) on our SAP Dev system. We are implementing an XI interface with a non-SAP system that also has a Dev and Test environment.  Up to now the interface has only needed to work between our client 041 and either the other Dev <b>or</b> Test system but not both at the same time (I have simply re-configured the target URL in the SOAP adapter).
    However, I have been asked to set up XI so it works with the other system's Dev and Test environements simultaneously.
    Ideally I would like to link our client 030 to their Dev system and our client 041 to their Test system but I don't believe I can have the RFC Sender adapter active for both client 030 and client 041 at the same time.
    If this is not possible then it would be OK for our client 041 to work with both the Dev and Test systems but how do I configure this?
    Our R/3 environment is 4.6C so I can't use Proxies. I have wondered whether using Parties would help but am not sure that they are an appropriate tool for internal communication.
    Any advice, pointers, links would be greatly appreciated.
    Thanks
    Andrew

    <b>Ideally I would like to link our client 030 to their Dev system and our client 041 to their Test system but I don't believe I can have the RFC Sender adapter active for both client 030 and client 041 at the same time.</b>
    u r having 3 option
    1)RFC
    2)Idoc  and
    3)proxy
    since u r having problem with RFC and Proxy..u can go for Idoc...
    parties are used in B2B communication.... i am not sure here u can use it or not....

  • Context for two BAPIs

    Hello Friends,
    I need one suggestion.... as following....
    I have a WD component which will have a view e.g create order. ....the inputfields will be mapped via component controller and I am going to call the bapi to create-order in the component controller.
    I need to implement the functionality of change and display order as well. My confusion is ( as the view and inputfields are same) how I will call the change/display bapi in component controller.
    Should I need to do dynamically mapping of my inputfields to the correspoinding structure of the corresponding BAPIs ( Create, change or display ) ??
    Thanks for suggestions...
    Regards,
    Edited by: Shah H on Nov 17, 2008 1:58 PM

    Map the input fields only once. And then use the context attributes in all the bapis call.
    e.g
    bapi create...
    call fm bapi_create
    exporting
       order_no = lv_attr1.
    call fm bapi_change
    exporting
       order_no = lv_attr1.
    call fm bapi_delete
    exporting
       order_no = lv_attr1.
    Hope it works.

  • RFC Queue for a BAPI

    Hi Guys,
    Iam using a BAPI for posting the data into R/3. Is there any way in which i can go and check the data which i had posted into SAP, at a later point of stage using the TID ? If so, please provide the TCode and the process to acheive this .
    Thanks,
    Kittu.

    You marked your answer as correct, is it solved ?
    Did you checked the appserv.log of the messaging server ? What the remote sender (PTools version) ?
    Nicolas.

  • NO RFC Destination for BAPI

    Hi,
    I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
    BUS6010 Method POST & CHECK
    BUS2072 Method FINDDETAILS
    I am using the Program RHINLV00_LSO to transfer data.
    When i execute this report it's throwing an error
    " NO RFC Destination for 2 BAPI's".
    An RFC Destination is created in SM59 to link the  two systems and i have distributed the distribution model to R/3 4.7.
    The Function modules are marked as Remote enabled function modules.
    Regards,
    Ramesh K.

    Hello,
    Did you test RFC destination whether the definition is working fine or not?
    You can test the destination,if it's working fine,then Bapis' should be able to execute.
    Thanks.
    Mark points if helpful.

  • NO RFC Destination for BAPI's

    Hi,
    I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
    BUS6010 Method POST & CHECK
    BUS2072 Method FINDDETAILS
    I am using the Program RHINLV00_LSO to transfer data.
    When i execute this report it's throwing an error
    " NO RFC Destination for 2 BAPI's".
    An RFC Destination is created in SM59 to link the two systems and i have distributed the distribution model to R/3 4.7.
    The Function modules are marked as Remote enabled function modules.
    Regards,
    Ramesh K.

    Hi,
    After creating the distribution model with 3 methods in ECC 6.0 (source system). Generated Partner profile automatically from BD64. Then distributed the distribution model to the other system i.e., SAP R/3 4.7 successfully. Then created partner profile from that system automatically.
    Port, partner profiles,outbound parameters, inbound parameters were created successfully.
    Thanks
    Ramesh

  • Same setting for two file adapter but different output

    Hi ,
    I am having two receiver file adapter for two differrent scenario with same settings but different structure.
    I want the output of the file for both the scenario should be displayed line by line but it is working fine for one scenario.File type,file encoding and FCC are same in both the interface except the fieldsnames in FCC.
    When i check both the output file i found that the scenario which is working fine  having OA OD hexadecimal value at the end of line of each line.and the second scenario which is giving the output in single line is having only OA.
    waitng for Valueable inputs!!!
    Thanks
    Santosh

    Hi Santosh,
    Kindly elaborate your question.
    it would be helpful if you post the content conversion parameters of the erroneous file channel.
    Regards,
    Varun

  • Difference In RFC Adapter and XI proxy

    I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
    Thanking you
    sridhar

    Hi,
    Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
    In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
    The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
    RFC Adapter :
    The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
    For FAQs about the RFC adapter, see SAP Note 730870
    The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
    The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
    The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
    The RFC adapter maps the following RFC calls to XML messages and the other way around:
    Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
    &#9679;     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
    &#9679;     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
    You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
    You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
    Proxy :
    Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
    ·        Interfaces designed for message exchange between application systems
    ·        Interfaces used by a cross-component integration process to receive or send messages, or both
    Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
    You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
    Interfaces are an essential component of SAP Exchange Infrastructure:
    ·        You define the interfaces to be used in an integration scenario.
    ·        Cross-component integration processes use interfaces to exchange messages.
    ·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
    ·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
    ·        You generate proxies to implement your scenario based on message interfaces.
    You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
    Hope this will help you.
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • Error while doing commint from RFC Adapter

    Hi,
    We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
    While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
    This way program works fine and there is no error
    So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any  special way that PI calls this commit work.
    PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
    Appreciate help on this.
    Regards,
    Harish

    Are there any error messages in the RFC Reciever channel in Runtime Workbench?
    RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
    Please try to give some more details on why the system says the messages are failing.

  • Monitoring of older RFC Adapter messages - RFC API

    Hi,
    I have successfully implemented a number of scenarios (File to rfc & File to Idoc)that required external data lookup - using the RFC API (calling a customer RFC FM) (and parsing the response with DOM).
    I am also using Global variables to store my lookup responses to help minimize the number of RFC calls invoked.
    When trouble shooting - as expected the log in the communication channel for the RFC adapter shows the BAPI response. However the number of records is always restricted to 25.
    If I process a message with 30 records, and lets say the first RFC Lookup fails but the remaining 29 are successfully - because the log is limited to 25 I lose a record of this error.
    Am I missing another method of search?
    Is this just a display restriction and perhaps I could report over the underlying tables myself?
    Regards
    Andrew

    Communication channel monitoring is as i understood primarily für monitoring the module chain a message is eventually running through. Did you try monitoring via RWB->Message Monitoring or sxmb_moni? There also should be a reference to the response. Maybe I didn´t get you right, but as far as I remember RFC Calls are also listed there with a bigger history.
    Thomas

  • RFC Adapter not Call

    Hello Friends,
    I am working on XI 2.0
    My Scenario is
    IDOC --> XI --> RFC Adapter --> R/3 System
    I am configuring the RFC adapter for the SAP system.
    But when I am able to try to call using the Integration Engine it’s not call the RFC adapter.
    I define the end point as
    RFC Adapter
    (X) Load Balancing Deactivated
           Application Server -- <host name>
           System Number      -- 00
    When I run the scenario it show me in the <b>sm58</b> transaction as
    <b>Connection Close (no Data)</b>
    And in the SXMB_MONI Transaction it shows
    <b>A. Status</b> as <b>Green Flag</b> means <b>Message schedule on outbound side</b>.
    So can you please identify and suggest me the solution or what else configuration is required.
    Thanks & Regards,
    Gaurav Jain

    try to register all queues in SXMB_ADM -> Manage queues.
    I think that should help you solve the issue.

  • Limitations of RFC Adapter XI 3.0

    In this presentation ( https://www.sdn.sap.com/content_documents/.../SAP%20XI%202.0%20-%20Features.pdf page 20), the following limitations are listed for the RFC Adapter for XI 2.0:
    Functionality
    Synchronous RFC
      No support forRFMsthat use update task without COMMIT WORK
      No SAP GUI
      No callbacks
      No session handling
      No RFCs to non-SAP systems (using RFC client or server libraries)
    tRFC: Support for exactly-once delivery for one message/call
      Not all tRFC functionality
      No „bundling“ of multiple calls
    With version 3.0, what are the current limitations??

    SAP Documentation states the following:
    Constraints
    Note the following restrictions:
    ·        Assignment is only guaranteed for transactional RFCs (tRFCs), that is, for messages with quality of service Exactly Once (EO).
    ·        There is no transactional context for more than one RFC call for each LUW (Logical Unit of Work).
    ·        Not provided: SAPGUI, callbacks, and qRFC (quality of service Exactly Once In Order (EOIO)).
    ·        RFC library clients (RFC SDK) are not supported.
    ·        The context in the called system is not kept open over multiple calls (calls are stateless; there is no session).
    ·        Only the payload of a received message is evaluated. Additional attachments are ignored and not forwarded.
    ·        The receiver adapter can only process valid RFC XML documents, for example, those generated by the sender adapter or by the SAP JCo.
    available at: http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
    best Regards
    Christien

  • Problem with sender RFC adapter

    Hi All
    I have created one RFC adapter for which i have created wrong business system and all then i have deleted that and i have created on more RFC adapter but when i am testing my scenario its taking the old one which i have deleted from the Integration directory. I have refreshed the cache using sxi_cache and also in RWB. But still i m getting the same error...
    Could you please tell  me how to resolve this error

    Hi
    Yes i have configured RFC as sender communication channel. I have deleted the old one including the business system. but still in adapter monitoring i m getting the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/<b>'Whirlpool_BS1'/</b><b>'RFC_Source_CC'</b>, lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QN9#800' returned party/service of ''/'QN9')"
    but i have deleted the whirlpool_bs1 business system.
    Why still i m getting this error.
    Thanks & Regards
    SUN

Maybe you are looking for


HashFlare