Problem in file to rfc scenario without using BPM concept

hi ,
  I have configured the file to rfc scenatio and in that i have created a synchronous message interface .i have even aaded modules to my sender adapter .
I have one sender aggrement , 2 receiver aggrement , 1 interface determination , and 1 receiver determination .
the problem that i am facing is that i am able to perform the operations on r3 side succesfully but i am not getting the response back in xi .
can any one pls help me in getting out of this problem .
with regards
Bhawarlal Choudhary

Hi Amit ,
   My scenario is for creating the notification ( in plant maintenance) . every time i transmit a file a new notification nos is generated and even i am able to see it in SAP . in RWB when i check my communication channel i am not getting any response . The synchronous process seems to be working fine according to me do i need to even create a FRC communiation channel for sender as i have not done that .
with regards
Bhawarlal Choudhary

Similar Messages

  • Problem with File RFC File scenario without using BPM

    Hi all,
      I am trying a File RFC File scenario without using BPM with the help of the following thread:
    File - RFC - File without a BPM - Possible from SP 19.
      The XI system is PI 7.0 sp 12. When I am trying to acheive the above scenario, I am getting wierd results i.e., when I observe in SXI_MONITOR, the message is showing as processed successfully, but when I watch the message status in communication channel monitoring, I am getting the following error:
    "Attempt to process file failed with com.sap.aii.af.service.cpa.CPAException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=DEV120;TS=Test_Service;AN=MI_Invoice;ANS=urn:sap.com:test;"
    I am not able to understand what the problem is. By the way, one more thing, is, I have kept the File processing mode as "Delete" in the sender file adapter. But the file is not getting deleted. I think the reason could be because of the above error.
    Can any body help me out in getting my problem resolved?
    Thanks,
    Adithya K

    CPA Cache Refresh from the Adapter Engine To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following
    URL: http://<host>:<port>/CPACache/refresh?mode=<b>delta|full</b>
    The Monitoring url is like this: http://<host>:<port>/CPACache
    Thanks & Regards,
    Farooq.

  • File to RFC scenario with no BPM

    I want to create File to RFC scenario with no BPM. I want to invoke RFC synchronously to verify that I'm getting correct response back, but i dont wanna process the response. So, In SXMB_MONI i can check the response back from RFC right? Or do I need to have BPM if want to see the response back from RFC?
    What kind of business system i need to create for RFC? can i use same business system for both File and RFC? I'm using one Business System created on Third party technical system, which i'm using for file Input, also for RFC. Is that OK?
    Thanks,
    Deepesh

    Hi,
    I need to have BPM if want to see the response back from RFC? ... yes
    The BPM will help you find the response very comfortable.
    What kind of business system i need to create for RFC? can i use same business system for both File and RFC? I'm using one Business System created on Third party technical system, which i'm using for file Input, also for RFC. Is that OK? ..Yes you can .
    Regards
    Agasthuri Doss

  • Many files to one file Processing in XI without using BPM

    Hi XI Experts,
    Greetings!!
    I have one requirement in which I have to send three files from ERP system to some Third Party system via XI without using BPM.
    I seached many threads..but not got the solutions.
    Please help me.
    many thanks.

    Hi Arya,
    > the sturcture of the Target file will be diffrent.
    I assume you have only one target structure but three different input structures. So create one interface for each 3 different sender files and in the output use the same file receiver communication channel in append mode. So when ever your interface is run it will keep appending to the same file comm channel. There is no blog or document for this integration.
    If I were you I will go with BPM which is best solution for this scenario. With BPM you have the standard help and design in your SAP BASIS component only:
    http://help.sap.com/saphelp_nw04/helpdata/en/0e/56373f7853494fe10000000a114084/content.htm
    Regards,
    ---Satish

  • Output XML file problem (in FILE to RFC scenario)

    hi,
       my problem is that in the export parameter i have 3 variables but my output xml file shows only 2 parameters . I have checked my mapping all 3 parameters are mapped properly in output mapping .
    Initially when i started the scenario there were only 2 parameters in my export list .
    i completed this suuccesfully and then as per new requirement one more parameter was needed to be added i added a new parameter and reimported my rfc .
    the response tab of the reimported RFC shows me the newly added parameter but my final xml file only shows me the previous 2 it doesnt show me the newly added one is there any seeting which i need to change like in idoc where we have to readd the idoc in IDX2
    With regards
    Bhawarlal Choudhary

    Hi,
    2 Introduction
    Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
    systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
    simple, are many times missed or mis-configured, causing the delivery of messages to fail.
    Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
    ABAP.
    Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
    SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
    backend SAP system.
    3 The Step By Step Solution
    The basic steps for the IDoc configuration are outline below:
    1. Configure SM59 on XI to communicate to SAP backend system.
    2. Configure port on XI for IDoc communication.
    3. Create or verify the Logical System Name on the SAP backend system.
    4. Create or verify business system in XI’s System Landscape Directory.
    5. Verify the Logical System Name of the business system.
    6. Verify or add the Logical System Name for the sender business system.
    7. Create/configure the Communication Channel for the IDoc receiver adapter
    3.1 Configure SM59 on XI to communicate to SAP backend system.
    1. Using transaction SM59, create an RFC destination with Connection Type = “3”.
    In this example, the RFC destination name is “NDVCLNT510”.
    2. Enter the logon information:
    3. Test the connection by clicking on “Testing connection” and “Remote logon”.
    Both must be successful.
    3.2 Configure port on XI for IDoc communication.
    4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is “SAPNDV”.
    •     &#61472;The Port name must be in the form of “SAPxxx”, where xxx is the system ID of the backend SAP
    system.
    •     The Client must be the client number of the backend SAP system.
    •     Select the RFC Destination which was created in the previous step.
    3.3 Create or verify the Logical System Name on the SAP backend system.
    5. Enter transaction SALE on the SAP backend system.
    6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
    3.4 Create or verify business system in XI’s System Landscape Directory.
    The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
    7. In the System Landscape Directory,  select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical  System Name.
    3.5 Verify the Logical System Name of the business system.
    8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
    Navigate the menu:
    Service • Adapter Specific Identifiers.
    If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
    9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
    Landscape Directory.
    •     &#61472;Double-click on the business system in the Integration Directory.
    •     &#61472;Switch to Edit mode.
    •     &#61472;Select menu: Service • Adapter-Specific Identifiers 
    10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
    11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
    3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
    15. In the Integration Directory, create an IDoc receiver communication channel.
    •     &#61472;The RFC Destination is from step 3.1.
    •     &#61472;The Port is from step 3.2.
    NOTE:
    There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
    4 Appendix
    Transaction: IDX2
    There are a couple of situation where IDX2 can be useful on the XI system.
    1. When we want to test connection between the XI and SAP backend system.
    2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
    meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
    Go to transaction IDX2 and click on “Create”.
    Enter the IDoc Type and the Source Port as defined in step #2. Click “Continue”.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
    Regards
    Hemant
    If find helpful plz award points

  • How to send 100 records from an IDOC to File Scenario without using BPM?

    Hi All,
    I have a requirement that i need to send 100 records from sap to file by using the scenario IDOC to File. Can you suggest how can i achieve this?
    Regards,
    Ramvilas.

    Hi,
       Create a H type RFC destination.Tagert host and port give  Xi system host and port.Path give the
       /sap/xi/adapter_plain?namespace=<NameSpcae>&interface=<Interface> &service=<SenderBusinessSystem>&qos=EO or EOIO.
    Go to we21 find xmlhttp port.give the port name and assign RFC.Give the port in we20 your idoc and change to collective.
    In Xi export the IDOC and change the occurance to 0-unbounded and import it.
    Regards,
    Prakasu.M

  • Choosing Receiver Interface (IDoc or RFC) without using BPM

    Hi,
    We have a scenario wherein the receiver interface (either IDoc or RFC) must be dynamically determined at runtime based on the source message. I've tried using Multi-Mapping but this did not work since IDoc and RFC interfaces are not on the same Adapter Engine.
    How do I configure this scenario without using BPM?
    Thanks,
    Francis

    Hi,
    >That was my first solution but it did not work since it seems that conditions only work for determining the Operation Mapping to use for the same Receiver interfaces.
    not true - not only Operation Mapping but also receiver agreement
    so the receiver's channel
    >I was misled into thinking that we could use it to dynamically determine the receiver interface.
    but you can do it over there
    intrface determination can be used for pseudo receiver determination too
    so you can have one interface that either goes to one
    channel or the other (within the same receiver)
    Regards,
    Michal Krawczyk

  • Async- Sync without using BPM

    Hi experts,
    could you please suggest if is it possible to implement asyn sync scenario without
    using BPM. If answer is yes then how to go about it
    My Scenario is : File ->RFC ->File
    thanks in advance
    francis

    Hi-
    This thread from Bhavesh is very useful
    File - RFC - File without a BPM - Possible from SP 19.

  • File-To-RFC without using BPM

    hey guys
    is a File-To-RFC scenario possible without using BPM? i have gone through the blog by Arpit Seth ( /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit ) but it uses BPM.
    i am new to XI and not very comfortable with BPM.
    please let me know if BPM is the only way out or are there some other methods too.
    Also under what circumstances one should use BPM?
    thanx in advance.
    aamir suhail

    Hi,
    it's a standard non BPM scenario
    (you can find many weblogs like this)
    the only different thing is the RFC signature import
    (inside repository)
    and the use of different channels (file and RFC)
    you can find many examples in my XI FAQ
    (document section)
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Problem in storing data in BAPI in File to RFC Scenario

    Hi everyone,
    I m doing File to RFC Scenario.......I completed design and configuration part and actived the Communication Channels.....
    Now when I check in Runtime workbench I am getting succefully executed both at outbound and Inbound Channels.......but
    data is not updated in BAPI...........
    I m getting following error when I check in Component monitoring......
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: RfcAdapter: receiver channel has static errors: configuration exception caused by: com.sap.aii.af.rfc.core.config.RfcChannelInactiveException: channel has status inactive: com.sap.aii.af.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: configuration exception caused by: com.sap.aii.af.rfc.core.config.RfcChannelInactiveException: channel has status inactive
    Please help me out.......
    Regards,
    Sudheer.

    Hi
    "I took Business Service as Service but not Business System.....Will it effect the scenario???......"
    I suggest While dealing with the SAP Systems we should use Business systems.
    Pls check the foolowing Threads for the above Query
    RFC - Business Service
    Re: business service for file to rfc
    Regards
    Abhijit

  • File to RFC scenario - receiver determination problems

    Hi ,
    Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
    While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
    This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
    Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
    Thanks,
    Joe
    I also cleared the SLD cache by the way.. that didnt work either .
    Message was edited by:
            Joe Stein

    Thanks a lot for you replies guys , but problems still not solved ;
    1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself  in the list of services for the configured receiver. How to implement this has not been shown in the blog.
    2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
    SOS !
    I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
    Any pointers at all ??
    Message was edited by:
            Joe Stein

  • Error handling in File - XI - SOAP scenario without BPM

    Hello!
    We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
    We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
    We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
    I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
    Regards, Tanja

    Hi Tanja,
    >>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
    I think, you should check that out. It is assumedly only 2 days work to build a scenario:
    IDoc -> BP
    BP <-> SOAP/HTTP
    BP -> IDoc (Acknowledgement)
    In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
    Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
    >>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
    Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
    Filling of ALEAUD fields:
    E1ADHDR/MESTYP: original message type
    E1ADHDR/E1STATE/DOCNUM: original IDoc number
    E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
    E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
    I ve done such a scenario several times. That works without any problems.
    Regards,
    Udo

  • Send multiple records to rfc without using BPM

    Dear Experts,
    Could you please help on the following scenario.
    I need to send multiple customer master data records from a file  to rfc without using BPM.
    The following is the mapping i am using
    source                                                 Target( RFC)
    ======                                          =============
    Tree             occurance   type           Tree occurance              
    cust_mt        1..1        
       customer     0..unbound -
    >          ztest_cust( rfc )  1..1
          cname     1..1             -
    >            cname   0..1
          cno          1..1            -
    >            cno       0..1
           bank           -
    >            bank    0..1
                                                                    item :  0..unbound
             code      -
    >                                   code   0..1
             name     -
    >                                    name  0..1
             location   -
    >                                      location 0..1
    1. Multiple banks possible for one customer
    2. Multiple customers possible in datafile from mdm
    Problem 1:Only one customer record from file is being sent to RFC thouth many records are in the file, the second, third .. and so on records not being sent to rfc.
    Problem 2:
      if add o.. unbound for the rfc occurance, <messages>,<message1> tags are getting added in message mapping, and no single customer record sent to rfc..
    Your help is rewarded with good points.
    Appreciate your help.
    Thanks.
    sravya.

    Hi VJ,
    Thank you for the immediate reply.
    one more thing, when i tried to change the occurences of   ztest_cust( rfc) to 0..unbound,
    I am not seeing the occurances updated in the imported rfc structure.
    The following is the wsdl for rfc, could you please help me to add occurances 0..unbound.
    Thanks a lot.
    sraya.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" name="ZTEST_CUST" targetNamespace="urn:sap-com:document:sap:rfc:functions">
         <wsdl:documentation>
         test for mdm
         </wsdl:documentation>
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions">
                   <xsd:element name="ZTEST_CUST">
                        <xsd:complexType>
                             <xsd:all>
                                  <xsd:element name="CNAME" minOccurs="0">
                                       <xsd:simpleType>
                                            <xsd:restriction base="xsd:string">
                                                 <xsd:maxLength value="10" />
                                            </xsd:restriction>
                                       </xsd:simpleType>
                                  </xsd:element>
                                  <xsd:element name="CNO" minOccurs="0">
                                       <xsd:simpleType>
                                            <xsd:restriction base="xsd:string">
                                                 <xsd:maxLength value="10" />
                                            </xsd:restriction>
                                       </xsd:simpleType>
                                  </xsd:element>
                                  <xsd:element name="BANK" minOccurs="0">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" type="ZST_CUST" minOccurs="0" maxOccurs="unbounded" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:all>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element name="ZTEST_CUST.Response">
                        <xsd:complexType>
                             <xsd:all>
                                  <xsd:element name="BANK" minOccurs="0">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" type="ZST_CUST" minOccurs="0" maxOccurs="unbounded" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:all>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:complexType name="ZST_CUST">
                        <xsd:sequence>
                             <xsd:element name="CODE" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="60" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NAME" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="60" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="LOCATION" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="60" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="ZTEST_CUST.Input">
              <wsdl:part name="parameters" element="rfc:ZTEST_CUST" />
         </wsdl:message>
         <wsdl:message name="ZTEST_CUST.Output">
              <wsdl:part name="parameters" element="rfc:ZTEST_CUST.Response" />
         </wsdl:message>
         <wsdl:portType name="ZTEST_CUST.PortType">
              <wsdl:operation name="ZTEST_CUST">
                   <wsdl:input message="rfc:ZTEST_CUST.Input" />
                   <wsdl:output message="rfc:ZTEST_CUST.Output" />
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="ZTEST_CUST.SAPBinding" type="rfc:ZTEST_CUST.PortType">
              <rfc:binding style="rfc" />
              <rfc:type name="ZST_CUST">
                   <ifr:container xmlns:ifr="urn:sap-com:ifr:v2:metamodel" xmlns:xlink="http://www.w3.org/1999/xlink">
                        <ifr:descriptor>
                             <ifr:description language="EN">
                             test
                             </ifr:description>
                        </ifr:descriptor>
                        <ifr:properties>
                             <ifr:sourceSystem />
                             <ifr:sourceClient>
                             020
                             </ifr:sourceClient>
                             <ifr:release>
                             640
                             </ifr:release>
                             <ifr:category>
                             structure
                             </ifr:category>
                             <ifr:unicode1>
                             true
                             </ifr:unicode1>
                             <ifr:unicode2>
                             true
                             </ifr:unicode2>
                             <ifr:isFlatStructure>
                             true
                             </ifr:isFlatStructure>
                        </ifr:properties>
                        <ifr:definition>
                             <ifr:internalLength1>
                             180
                             </ifr:internalLength1>
                             <ifr:internalLength2>
                             360
                             </ifr:internalLength2>
                             <ifr:fields>
                                  <ifr:field name="CODE" category="simple">
                                       <ifr:descriptor />
                                       <ifr:properties>
                                            <ifr:helpValuesSupported>
                                            false
                                            </ifr:helpValuesSupported>
                                            <ifr:offset1>
                                            0
                                            </ifr:offset1>
                                            <ifr:offset2>
                                            0
                                            </ifr:offset2>
                                       </ifr:properties>
                                       <ifr:definition>
                                            <ifr:scalarType>
                                                 <ifr:definition>
                                                      <ifr:type>
                                                      CHAR
                                                      </ifr:type>
                                                      <ifr:abapType>
                                                      C
                                                      </ifr:abapType>
                                                      <ifr:length>
                                                      60
                                                      </ifr:length>
                                                      <ifr:internalLength1>
                                                      60
                                                      </ifr:internalLength1>
                                                      <ifr:internalLength2>
                                                      120
                                                      </ifr:internalLength2>
                                                      <ifr:decimals>
                                                      0
                                                      </ifr:decimals>
                                                 </ifr:definition>
                                            </ifr:scalarType>
                                       </ifr:definition>
                                  </ifr:field>
                                  <ifr:field name="NAME" category="simple">
                                       <ifr:descriptor />
                                       <ifr:properties>
                                            <ifr:helpValuesSupported>
                                            false
                                            </ifr:helpValuesSupported>
                                            <ifr:offset1>
                                            60
                                            </ifr:offset1>
                                            <ifr:offset2>
                                            120
                                            </ifr:offset2>
                                       </ifr:properties>
                                       <ifr:definition>
                                            <ifr:scalarType>
                                                 <ifr:definition>
                                                      <ifr:type>
                                                      CHAR
                                                      </ifr:type>
                                                      <ifr:abapType>
                                                      C
                                                      </ifr:abapType>
                                                      <ifr:length>
                                                      60
                                                      </ifr:length>
                                                      <ifr:internalLength1>
                                                      60
                                                      </ifr:internalLength1>
                                                      <ifr:internalLength2>
                                                      120
                                                      </ifr:internalLength2>
                                                      <ifr:decimals>
                                                      0
                                                      </ifr:decimals>
                                                 </ifr:definition>
                                            </ifr:scalarType>
                                       </ifr:definition>
                                  </ifr:field>
                                  <ifr:field name="LOCATION" category="simple">
                                       <ifr:descriptor />
                                       <ifr:properties>
                                            <ifr:helpValuesSupported>
                                            false
                                            </ifr:helpValuesSupported>
                                            <ifr:offset1>
                                            120
                                            </ifr:offset1>
                                            <ifr:offset2>
                                            240
                                            </ifr:offset2>
                                       </ifr:properties>
                                       <ifr:definition>
                                            <ifr:scalarType>
                                                 <ifr:definition>
                                                      <ifr:type>
                                                      CHAR
                                                      </ifr:type>
                                                      <ifr:abapType>
                                                      C
                                                      </ifr:abapType>
                                                      <ifr:length>
                                                      60
                                                      </ifr:length>
                                                      <ifr:internalLength1>
                                                      60
                                                      </ifr:internalLength1>
                                                      <ifr:internalLength2>
                                                      120
                                                      </ifr:internalLength2>
                                                      <ifr:decimals>
                                                      0
                                                      </ifr:decimals>
                                                 </ifr:definition>
                                            </ifr:scalarType>
                                       </ifr:definition>
                                  </ifr:field>
                             </ifr:fields>
                        </ifr:definition>
                   </ifr:container>
              </rfc:type>
              <wsdl:operation name="ZTEST_CUST">
                   <ifr:container xmlns:ifr="urn:sap-com:ifr:v2:metamodel" xmlns:xlink="http://www.w3.org/1999/xlink">
                        <ifr:descriptor>
                             <ifr:description language="EN">
                             test for mdm
                             </ifr:description>
                        </ifr:descriptor>
                        <ifr:properties>
                             <ifr:sourceSystem />
                             <ifr:sourceClient>
                             020
                             </ifr:sourceClient>
                             <ifr:release>
                             640
                             </ifr:release>
                             <ifr:package>
                             $TMP
                             </ifr:package>
                             <ifr:akhNode />
                             <ifr:released>
                             external
                             </ifr:released>
                             <ifr:outbound>
                             false
                             </ifr:outbound>
                             <ifr:synchronous>
                             true
                             </ifr:synchronous>
                             <ifr:asynchronous>
                             false
                             </ifr:asynchronous>
                             <ifr:unicode1>
                             true
                             </ifr:unicode1>
                             <ifr:unicode2>
                             true
                             </ifr:unicode2>
                        </ifr:properties>
                        <ifr:definition>
                             <ifr:parameters>
                                  <ifr:parameter name="CNAME">
                                       <ifr:descriptor>
                                            <ifr:description language="EN">
                                            Character Field Length = 10
                                            </ifr:description>
                                       </ifr:descriptor>
                                       <ifr:definition>
                                            <ifr:scalarType name="CHAR10">
                                                 <ifr:properties>
                                                      <ifr:helpValuesSupported>
                                                      false
                                                      </ifr:helpValuesSupported>
                                                      <ifr:fixedValuesListDefined>
                                                      false
                                                      </ifr:fixedValuesListDefined>
                                                      <ifr:mixedCaseSupported>
                                                      false
                                                      </ifr:mixedCaseSupported>
                                                      <ifr:signedNumber>
                                                      false
                                                      </ifr:signedNumber>
                                                 </ifr:properties>
                                                 <ifr:definition>
                                                      <ifr:type>
                                                      CHAR
                                                      </ifr:type>
                                                      <ifr:abapType>
                                                      C
                                                      </ifr:abapType>
                                                      <ifr:length>
                                                      10
                                                      </ifr:length>
                                                      <ifr:internalLength1>
                                                      10
                                                      </ifr:internalLength1>
                                                      <ifr:internalLength2>
                                                      20
                                                      </ifr:internalLength2>
                                                      <ifr:decimals>
                                                      0
                                                      </ifr:decimals>
                                                      <ifr:outputLength>
                                                      10
                                                      </ifr:outputLength>
                                                 </ifr:definition>
                                            </ifr:scalarType>
                                       </ifr:definition>
                                       <ifr:properties>
                                            <ifr:direction>
                                            in
                                            </ifr:direction>
                                            <ifr:class>
                                            import
                                            </ifr:class>
                                            <ifr:type>
                                            scalar
                                            </ifr:type>
                                            <ifr:optional>
                                            true
                                            </ifr:optional>
                                            <ifr:basedOnDictionaryReference>
                                            true
                                            </ifr:basedOnDictionaryReference>
                                       </ifr:properties>
                                  </ifr:parameter>
                                  <ifr:parameter name="CNO">
                                       <ifr:descriptor>
                                            <ifr:description language="EN">
                                            Character Field Length = 10
                                            </ifr:description>
                                       </ifr:descriptor>
                                       <ifr:definition>
                                            <ifr:scalarType name="CHAR10">
                                                 <ifr:properties>
                                                      <ifr:helpValuesSupported>
                                                      false
                                                      </ifr:helpValuesSupported>
                                                      <ifr:fixedValuesListDefined>
                                                      false
                                                      </ifr:fixedValuesListDefined>
                                                      <ifr:mixedCaseSupported>
                                                      false
                                                      </ifr:mixedCaseSupported>
                                                      <ifr:signedNumber>
                                                      false
                                                      </ifr:signedNumber>
                                                 </ifr:properties>
                                                 <ifr:definition>
                                                      <ifr:type>
                                                      CHAR
                                                      </ifr:type>
                                                      <ifr:abapType>
                                                      C
                                                      </ifr:abapType>
                                                      <ifr:length>
                                                      10
                                                      </ifr:length>
                                                      <ifr:internalLength1>
                                                      10
                                                      </ifr:internalLength1>
                                                      <ifr:internalLength2>
                                                      20
                                                      </ifr:internalLength2>
                                                      <ifr:decimals>
                                                      0
                                                      </ifr:decimals>
                                                      <ifr:outputLength>
                                                      10
                                                      </ifr:outputLength>
                                                 </ifr:definition>
                                            </ifr:scalarType>
                                       </ifr:definition>
                                       <ifr:properties>
                                            <ifr:direction>
                                            in
                                            </ifr:direction>
                                            <ifr:class>
                                            import
                                            </ifr:class>
                                            <ifr:type>
                                            scalar
                                            </ifr:type>
                                            <ifr:optional>
                                            true
                                            </ifr:optional>
                                            <ifr:basedOnDictionaryReference>
                                            true
                                            </ifr:basedOnDictionaryReference>
                                       </ifr:properties>
                                  </ifr:parameter>
                                  <ifr:parameter name="BANK">
                                       <ifr:descriptor>
                                            <ifr:description language="EN">
                                            test bank type
                                            </ifr:description>
                                       </ifr:descriptor>
                                       <ifr:definition>
                                            <ifr:complexType xmlns:xlink="http://www.w3.org/1999/xlink" name="ZST_CUST" type="structure" xlink:role="type" xlink:href="/Content?TYPE=type&amp;NAME=ZST_CUST" />
                                       </ifr:definition>
                                       <ifr:properties>
                                            <ifr:direction>
                                            inout
                                            </ifr:direction>
                                            <ifr:class>
                                            tables
                                            </ifr:class>
                                            <ifr:type>
                                            structure
                                            </ifr:type>
                                            <ifr:optional>
                                            true
                                            </ifr:optional>
                                            <ifr:basedOnDictionaryReference>
                                            true
                                            </ifr:basedOnDictionaryReference>
                                       </ifr:properties>
                                  </ifr:parameter>
                             </ifr:parameters>
                        </ifr:definition>
                   </ifr:container>
              </wsdl:operation>
         </wsdl:binding>
    </wsdl:definitions>

  • File to RFC Scenario - Not working with AAE

    I have a File to RFC Scenario (calling RFC /POSDW/CREATE_TRANSACTIONS_EXT)  using AAE but it is failing with following error in PI .
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
    But When I run the same scenario using IE instead of AAE, it is successful from PI. So probably there is nothing wrong in RFC channel configuration.
    There's an OSS note-730870  on this error ,it says the XML document sent to RFC Adapter may not be RFC-XML but as I am using AAE, payload generated after technical routing cannot be viewed.
    Could you all please suggest why this error is coming and solution for the same?
    Thanks,
    Ankit

    Hi Debashish,Monica,
    Thanks for your help, I checked this SAP note its question 16 do describe my problem but do not provide solution and as I am using AAE it does not allows me to see the target structure generated whereas if I use IE the target structure generated is sucessfully getting posted.
    Also, the functional module is present in target system. I have reimported the RFC also.
    Is there some AAE related configuration required to enable AAE with RFC which could be missing?
    This is what I get in log as the RFC reciever is called..
    06.09.2011 14:15:31 Information MP: entering1
    06.09.2011 14:15:31 Information MP: processing local module localejbs/RfcAFBean
    06.09.2011 14:15:31 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    06.09.2011 14:15:31 Error Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    06.09.2011 14:15:31 Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
    Thanks,
    Ankit

  • Step by Step Guide Details for RFC to File and File to RFC scenario

    Hi Guru's
    Good day to you. I am tyring to develop some scenarios based on RFC adaptor. so i want to start up with basic scenarios like RFC to File  scenario(Here i just want to pull some data from SAP using RFC and put it in destination folder as an text file) and FILE to RFC scenario (Here i just want to take some data from the file and update into SAP).
    For doing these scenarios i would like to request you people to send me the step by step guide which explains me about the complete steps of configurations required to do the RFC to FILE scenario and FILE to RFC scenario.
    I found some scenarios and i am in confused state. so i request you to please put your experience to help me out.
    thanks in advance.
    Regards
    Raj

    Hi Aaron,
    I don't know your scenario and your ECC and PI versions but I learned how to use ABAP Proxy more than 1 year ago with the following tutorial:
    Edit--> The forum doesn't allow me to post external link, just search "ABAP Proxy Communication Scenario" in google and visit the 1st result
    The way to develop ABAP Proxys has changed a little if your PI is 7.1. In the ECC side, the transaction SPROXY looks much better too if you have a recent version of the ECC.
    Edited by: Marshal on Oct 8, 2009 5:08 PM
    I've found that SDN Document. Maybe the scenario is not the most simple to start with ABAP Proxy but is very well documented and is for PI 7.1. The document also handles the inbound and outbound proxys
    [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c00ca32e-f991-2b10-f5be-97114bd2b08f&overridelayout=true]
    Edited by: Marshal on Oct 8, 2009 5:22 PM

Maybe you are looking for

  • Image Manipulation

    A client came to me today, not knowing any form of coding, he asked me if for his front page, he could place the images anywhere he wanted in the article he submits to the front page, as in being able to click on an image and drag it to his liking wi

  • How to Register a Custom Template for Accounts Payable

    How do I register a Custom Template for Accounts Payable?

  • [SOLVED] Unable to download Libreoffice.

    Hello all, I've been trying to download and install libreoffice by running "pacman -S libreoffice" but I am repeatedly getting an error message saying "error: 'libreoffice': could not find or read package". I checked the wiki but found no mention of

  • Top n analysis without analytical function or rownum

    Hi I am working on Oracle 9i and i have the following query. My data is like as Year Type Total 1996 A 23 1996 B 34 1996 C 19 1996 D 11 1996 E 45 1996 F 32 1997 A 12 1997 B 11 1997 C 34 1997 D 45 1997 E 67 1997 F 11 My requirement is to get the top 4

  • Shut down maintenance with revision codes

    Hi guys, For creation of shut down order, revision is needed, in IMG we can create revison (Revision is created with planning plant number and revision number and start and end of revision dates.) and this number is to be mentioned in order,  could y