Problems with RFC transport confirmation in a BPM

Hi everyone.
I have an interface that is stopped now. The problem is that XI tried to send a RFC and the R3 backend is down.
Now i have this interface waiting for a transport confirmation (since last sunday morning).
is there any way to 're-send' the RFC or 'unlock' this situation?
Regards.

Hi.
Status of the RFC is ok. At the right side of the status, i have a green '?' due to no-confirmation os the transport of the RFC. In the bpm i have set the property 'transport acknowledge' in every RFC i try to send to R3 backend. XI is waiting for the ACK but no ACK is arriving so i would like to 're-send' angain teh RFC.
Is that possible?
Regards

Similar Messages

  • Problem with po receipts confirmation customization

    hi
    i have a problem with po receipts confirmation customization
    previously once po is approved and run the po receipts confirm concurrent
    program then work flow will be triggered
    they add 15 days more to the due date
    but my requirement i s have to add 15 days to the po approved date.
    in the PORCPTWF .get_order_info procedure they wrote a code
    due date is standard attribute in the po confirm receipts workflow....
    they assign due date to
    x_exp_receipt_date := wf_engine.GetItemAttrDate ( itemtype => itemtype,
    itemkey => itemkey,
    aname => 'DUE_DATE');
    and then
    x_due_date_plus_15 := x_exp_receipt_date + 15;
    wf_engine.SetItemAttrText ( itemtype => Itemtype,
    itemkey => Itemkey,
    aname => 'DUE_DATE_PLUS_15',
    avalue => x_due_date_plus_15 );
    but i need to get po aproved date so there is a select statement in the same procedure i have added approved_date from po_headers and retrived into
    a variable x_approved_date;
    SELECT poh.segment1,
    pov.vendor_name,
    poh.agent_id,
    poh.note_to_receiver,
    poh.approved_date -- i added this
    INTO x_po_number,
    x_supplier_name,
    x_buyer_id,
    x_note_to_receiver,
    x_approved_date -- i added this
    FROM PO_HEADERS poh,
    PO_VENDORS pov
    WHERE po_header_id = x_po_header_id
    AND poh.vendor_id = pov.vendor_id (+);
    then
    i have created a approved_date attribute in the po confirm receipt workflow
    since there is no standard attribute related to approved dat
    and in this procedure i wrote
    x_approved_date_plus_15 := x_approved_date + 15;
    wf_engine.SetItemAttrText ( itemtype => Itemtype,
    itemkey => Itemkey,
    aname => 'APPROVED_DATE',
    avalue => x_approved_date_plus_15 );
    but its not working
    any suggestions....please

    I see that the steps you have performed is correct.
    1. You created an Item Attribute APPROVED_DATE in PO Confirm Receipts workflow definition.
    2. In a function activity, queried approved date from PO Headers and added 15 to it and set this new value to Item Attribtue APPROVE_DATE. (Though it is ok, you may use SetItemAttrDate for a Date Type Item Attribute as a good practice).
    3. You should be able to access this Item Attribute in any of the function activities after the above activity or assign this Item Attribute in a Message Attribute and display it in a Notification Message.
    I would need more information on What is not working (?) in this in order to provide assistance.
    Thanks
    Vijay

  • Problem with RFC Communication in BPM

    Hi,
       I'm again facing problem with transfer of
    File->RFC->File scenario.The error in sxmb_moni is given below .
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
      <SAP:P1>Error opening an RFC connection.</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error
    opening an RFC connection.</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Can anyone help me in fixing out this problem.
    Regards,
    Prashanth K.R,

    Hi Prashant,
    Just click onto your namespace and verify the details given in the "Connection data for import from SAP system". Check whether its matching the system from where you have called the RFC.
    hope this will help u.
    regards
    divya
    Message was edited by: Divya Nambiar

  • Problem with file transport

    Hi ,
    I am transporting some of my XI 3.0 objects from XIQA to XIPROD.
    When I am importing the objects in XIP I am getting numbers of problem.
    1- Scenarios SOAP to RFC . when I am activating the objects it saying
    Communication Channel | PRD_400 | RFC_QA3_Receiver: 
    Enter a value for attribute 'Application Server' 
    Enter a value for attribute 'System Number' 
    Enter a value for attribute 'Logon User' 
    Enter a value for attribute 'Logon Password' 
    Enter a value for attribute 'Logon Language' 
    Enter a value for attribute 'Logon Client'
    Do I need to Give these values manually again as they are moved from Env to other?
    2- Why my Receiver communiation channel coimg as
    Communication Channel | PRD_400 | RFC_QA3_Receiver: 
    As this PROD env it should come PR3 in place of QA3.
    I  have also transport other interfaces in PROD but in that there was no such problem with Communication channel Name.
    Regards

    Do I need to Give these values manually again as they are moved from Env to other?
    When we transport ID objects, the values stored in the channel get lost and have to be manually enetered......it happens even for DEV --> QA environment.
    Now your channel should reflect PROD-related data.
    2- Why my Receiver communiation channel coimg as
    Communication Channel | PRD_400 | RFC_QA3_Receiver:
    The channel name does not depend on the environment it is present....verify the name once again!
    Regards,
    Abhishek.

  • Problem with RFC connection - tp program not registered

    Hello everyone
    recently there  has appeared a problem with the RFC connection on our system - we received the following set of messages:
    Trace file opened at 20101221 130738 Central European Standard Time, SAP-RE
    ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Tp program is not registered.
    ABAP Programm: RSRFCPIN (Transaction: SM59)
    User: xxx(Client: 100)
    Destination: SIDRFC_IFSAPHRCZPKCP (handle: 2, , )
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Program transakcji nie jest zarejestrowany
    DEST =SIDRFC_IFSAPHRCZPKCP
    HOST =%%RFCSERVER%%
    PROG =IFCZPKCP
    GWHOST =ssapprod
    GWSERV =sapgw21
    I tried to register program with a command:
    rfcexec -aIFCZPKCP -gssapprod -xsapgw21
    but with no success - the program didn't appear on the list of logged clients on the system in gateway monitor. Frankly speaking we do not know now what else we can do - please help!
    We have ECC 6.0 (SAP_BASIS 700 SP18) on Windows Server 2003 R2 x64.
    Thanks in advance for any help.
    Regards
    Peter

    Hi Salim
    thanks for your reply.
    ./rfcexec -a(PROG_ID) -gssapprod -xsapgw21 &
    The syntax you're providing refers to UNIX systems, but I did similar thing on our Windows system - I tried all of the following methods (unfortunatelly without success):
    rfcexec -a(PROG_ID) -gssapprod -xsapgw21
    full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod -xsapgw21
    rfcexec -a(PROG_ID) -gssapprod.domain -xsapgw21
    full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod.domain -xsapgw21
    Can you advise me what to do now?
    Thanks
    Piotr

  • Problem with RFC for Risk Terminator - GRC 5.2 SP12

    We are having a problem with the RFC connection for Risk Terminator in one of our SAP environments.  It is working in our 'DV3' environment, but not in our 'RT3' environment.  Everything is set up just the same in both environments and all SAP Adaptors show green.
    This was working in RT3 when we first upgraded to GRC 5.2 last November, but it now gives me an error when I do an update with PFCG and it calls RT.  The error message and our Basis support group both say the RFC needs to be 'registered', but our SAP Support contact during our upgrade said it does not, and I can't find any documentation that says this is required also.  Plus it was working before even though it was unregistered.
    What is causing this problem and how do I resolve it?
    Also, if these RFCs do not have to be registered, is there some documentation that states this that I can show to our Basis group?
    Thanks.

    What about the question of the RFC needing to be registered?  This is the solution our Basis group thinks is required, so it will be hard to get them to do anything else until this issue has been addressed.
    Thanks.

  • Problem with SPAU Transports after Upgrade and after applying SAPKW70016

    Dear All,
    we copied old dev to new QA, upgraded new QA, then copied new QA to new DEV.
    did the SPAU adjustments in DEV.  At that time DEV SAP_BW version was SAPKW70015.  After that we applied SAPKW70016.  Now we're having problems with the SPAU transport because of the application of SAPKW70016. 
    Requested to kindly suggest ASAP.
    Thanks & Regards
    janardhan Kumar K

    Hi,
    Could you please to be more specific with the error ? Please check the log e send us the message error that is happening during the transport.
    Thanks,
    Walter Oliveira.

  • PROBLEM WITH RFC DESTINATION

    Hi GURU,
    I have a problem with the record of RFC destination.
    When i created RFC destination TCP/IP when i made the tests, it`s ok.
    But when i used this rfc destination in a  function of ABAP. I have an error. The error is:
    RfcExecProgram'#Win32 error 2: The system cannot find the file speci
    Can you help me??
    What should I do to run properly?
    Thank for all.
    regards,
    RAFA

    Hi,
    Even I am also new to SAP , but I have little knowledge about RFC, try to create your RFC of type 3 (ABAP type ), then if you use this RFC , I hope no problem will come if the authorization details and IP /Host name of the destination system are perfect.
    also Please suggest me why ( when ) we use TCP /IP type of RFCs

  • Problems with query transport (missing object)

    Hello,
    I've a problem while transporting a query with the transport connection. I choose the option "necessary objects" but the import in the productive system fails due to a missing object.
    How can I find the missing object? In the transport log only the ID is given (e.g. " Element 67ZP0WYO09DFA52PLG2SREVBT is missing in version M")
    Thanks in advance,
    Markus

    Hi Markus,
    Check data base tables RSZELTXREF & RSZELTTXT for the missing element in the transport.
    Try to include all the missing elements of a Query in a new transport and try again.
    Hope this will help.
    Praveen

  • Problem with RFC INTEGRATION_DIRECTORY_HMI

    Hello !
    I h’ave one problem with the RFC connection INTEGRATION_DIRECTORY_HMI.
    When I test it, SAP ask me in a pop-up window an user/password.
    I’m sure that SAP should’nt ask me another user/password like I fill it (XIISUSER) in the definition of the RFC destination.
    Coul someone help me ?
    Thanks in advance

    Hi,
    this problem are strang. I also have this problem with my
    test installation. Even when i try the trick from Lui it
    doesn't work in my case. The popup screen still appeare.
    I futhermore have problem with the abap cache refresh in
    full mode where i describe in another topic. I would also
    interested how to get rid of this problem.
    For Martial:
    did you install a new XI-System with NW04-SR1 on windows
    e.g. windows 2000 Server? Did you have also the cache problem on the abap side?
    regards,
    Ly-Na Phu
    Message was edited by: Ly-Na Phu

  • Problem with WAD transports

    Hi there
    We have a problem with transporting templates created in the WAD.
    The transport goes through succesfully, but when I run the template(s) in PROD, the changes are not reflected.
    If I open the template in the WAD in PROD, then I can see that the changed template is indeed in PROD, but executing it in the portal shows the old template.
    We are seeing this problem now with templates, but noticed it about a week ago with reusable library items that weren't updating correctly in PROD. The way we resolved it on that occasion was with a server reboot (J2EE)
    I am sure a Java restart will do the trick again this time, but we can't have a situation where we need to restart systems each time a transport is sent through ... that's ridiculous.
    I imagine there is some sort of caching holding onto the old items, but I don't know where to look to clear that cache.
    Please, can anyone provide some assistance on this?
    Cheers,
    Andrew

    Hi Andrew,
    i think that you will find the cache in 'RSRT' T Code.
    and refresh will also help this problem.
    If not then find the ABAP Program and regenerate it.
    Hope this will solves your problem.

  • Problem with translation transport

    hello everybody,
    I have an application with two corresponding transport requests (this is because I would like to transport to different systems only part of the functionality of the app). Recently a translator made an English translation of my application which resulted in a new transport request with about 100 new objects. I would like to distribute accordingly these objects to the two old transport requests ( respectively the two parts of the app). Is there a way to do this, to find out which translation object belongs where?
    Thanks

    problem with translation transport
    Same message here?
    Regarding to the issue, perhaps giving some information would be helpful. What kind of objects are them? (Data element, message class? )
    Best regards,
    Matyas

  • Problem with RFC exception in BPM

    Hi,'
    I have created control step for RFC exception. Assigned the alert catagory and given alert message.
    i have below steps:
    Transformation-control-send RFC-cancel process.
    while trying to test i changed ip address of rfc channel and tested but i am not receiving any alert but messages are getting stucked in BPM with error -
    permanent error in message proccessing
    could you please suggest how to trigger rfc execption

    Suggestions..
    refer  BPMPatternReqRespTimeout for triggering exception.
    Basically you might change the sequence of steps as follow
    Create Block with deadline branch where you use control step to trigger exception and have another branch exception handler  and in that branch you have transformation and senderror.  This will help.

  • Problem with RFC-Call within BPM

    Hello Experts,
    I am developing a scenario in which I call an rfc-function-module for saving information from an incoming xml which will be transmitted as Idoc to another SAP System.
    The Idoc transmission is doing properly. But the RFC-Call I try to do always ends with a red flag. Error-Message: message has error status on outbd. side at the Process-Engine.
    Can someone help solving that problem?
    Thanks in advance.
    Regards, Alexander

    Hi Rajhans,
    1) The user mentioned in the RFC communication channel is having the authorization.
    Yes, he have the authorizations.
    2) Go to Communication channel monitoring and check what error you are getting for the communication channel is showing.
    There is an error about the FileSenderChannel. Error: java.lang.NullPointerException.
    3) Check whether the RFC created at abap stack is remote enabled or not.
    The function module is remote enabled.

  • Collection problem with RFC function module WSDL.

    Hi.
    I have developed an RFC function module in a SAP system version 4.7 (WAS 620). This FM has 2 table parameters. I have no problem when I see the WSDL in the SAP Web Service Browser.
    Another team is trying to consume this RFC FM as a web service from a Java application but they say they can't see the table parameters as collections.
    Here is the WSDL of the FM, the table parameters are T_MOVIM and T_ERROR:
    <?xml version="1.0" encoding="UTF-8" ?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="urn:sap-com:document:sap:rfc:functions">
         <types>
              <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
                   <xsd:element name="ZMMFUSAPTK_0001">
                        <xsd:complexType>
                             <xsd:all>
                                  <xsd:element name="GENIDOC" minOccurs="0">
                                       <xsd:simpleType>
                                            <xsd:restriction base="xsd:string">
                                                 <xsd:maxLength value="1" />
                                            </xsd:restriction>
                                       </xsd:simpleType>
                                  </xsd:element>
                                  <xsd:element name="T_ERROR">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                                  <xsd:element name="T_MOVIM">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:all>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element name="ZMMFUSAPTK_0001.Response">
                        <xsd:complexType>
                             <xsd:all>
                                  <xsd:element name="CODRET">
                                       <xsd:simpleType>
                                            <xsd:restriction base="xsd:string">
                                                 <xsd:maxLength value="1" />
                                            </xsd:restriction>
                                       </xsd:simpleType>
                                  </xsd:element>
                                  <xsd:element name="T_ERROR">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                                  <xsd:element name="T_MOVIM">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:all>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:complexType name="ZMMTASAPTK_0011">
                        <xsd:sequence>
                             <xsd:element name="REFERENCIA" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="FECHACONT" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="8" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="FECHADOC" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="8" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CODMOV" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="2" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NROPLAN" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="12" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NROCOMP" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CLASEMOV" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="3" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CENTRO" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="ALMACEN" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="MATERIAL" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="5" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="LOTE" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CANTIDAD" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="15" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="MOTIVOMOV" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CENTROREC" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="ALMACENREC" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="4" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CENTROCTO" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="ORDEN" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="12" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="TIPOSTK" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="1" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="NROPEDIDO" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CODCISTERNA" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="50" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="ZMMTASAPTK_0012">
                        <xsd:sequence>
                             <xsd:element name="REFERENCIA" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="10" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="CODERR" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="3" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                             <xsd:element name="MSJERR" minOccurs="0">
                                  <xsd:simpleType>
                                       <xsd:restriction base="xsd:string">
                                            <xsd:maxLength value="100" />
                                       </xsd:restriction>
                                  </xsd:simpleType>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </types>
         <message name="ZMMFUSAPTK_0001Input">
              <part name="parameters" element="s0:ZMMFUSAPTK_0001" />
         </message>
         <message name="ZMMFUSAPTK_0001Output">
              <part name="parameters" element="s0:ZMMFUSAPTK_0001.Response" />
         </message>
         <portType name="ZMMFUSAPTK_0001PortType">
              <operation name="ZMMFUSAPTK_0001">
                   <input message="s0:ZMMFUSAPTK_0001Input" />
                   <output message="s0:ZMMFUSAPTK_0001Output" />
              </operation>
         </portType>
         <binding name="ZMMFUSAPTK_0001Binding" type="s0:ZMMFUSAPTK_0001PortType">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
              <operation name="ZMMFUSAPTK_0001">
                   <soap:operation soapAction="http://www.sap.com/ZMMFUSAPTK_0001" />
                   <input>
                        <soap:body use="literal" />
                   </input>
                   <output>
                        <soap:body use="literal" />
                   </output>
              </operation>
         </binding>
         <service name="ZMMFUSAPTK_0001Service">
              <documentation>SAP Service ZMMFUSAPTK_0001 via SOAP</documentation>
              <port name="ZMMFUSAPTK_0001PortType" binding="s0:ZMMFUSAPTK_0001Binding">
                   <soap:address location="http://dbades00.bue.bemberg.com.ar:8002/sap/bc/soap/rfc" />
              </port>
         </service>
    </definitions>
    Should I change something in the definition of the parameters of the FM? or the problem is with the parsing process on the other system?
    Thanks in advance.
    Fabian.

    Welcome to SDN.
    I am not sure about this particular issue, but i have used WSDL from WAS6.20 system in MS Office infopath to consume webservice where we have had table parameters without any issue.
    may be try with office infopath to make sure that the problem is with the WSDL or with the java application.
    Regards
    Raja

Maybe you are looking for