Deep Structute in RFC.

Hi Everybody,
Does RFC adapter support deep structure.
Can I have a table with field point to another table.
Thanks in advance ,
Regards,
Bikram

I'm also stuck with transmitting deep structures in RFC.
According to the <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/22/5a981cfbaa06428abdfa32b81423d2/content.htm">SAP Help</a>:
<i>The RFC transmits deep structures (structures that have at least one table type) in XML, and codes the text data in UTF-8.</i>
So far so good, I even can see the result transmitted as XML over the line, however I'm not able to retrieve this XML from RFC. Any pointers where I can find further info on retrieving datastructures sent as XML?
regards
Adrian

Similar Messages

  • Can we create a deep structure in RFC?

    Hi,
    My requirement is to create an RFC which has 3 output tables. out of which 1 table contains deep structure, but SAP is not allowing me to create an RFC with deep structure. Message shows only flat structures support in RFC. can any one tell is there any limitation of creating a deep structure in RFC?
    Thanks,
    Kumar.

    Instead of a deep structure, you can define another internal table in your signature which will hold all of the data for all of th records of the other internal table,  you just need a key value from the other internal table to be able to map which records go with what record in the original internal table.  Does this make sense?
    Regards,
    Rich Heilman

  • Editing server-side Sieve via IMAP... does Messaging Server support RFC 5804?

    The Sieve Addon for Thunderird https://addons.mozilla.org/en-us/thunderbird/addon/sieve/ (https://github.com/thsmi/sieve) mentions the sieve management protocol (RFC 5804) accessible over IMAP. I did not find any mention of this on the CommSuite Wiki, so I guess it is not supported at the moment... or just not published?
    Apparently, most users of this addon use it in conjunction with Dovecot server which does support Sieve server-side filtering, and/or with projects like this to translate between client-side Mozilla filters and server-side Sieve filters: Mozilla filter to sieve converter | Free Communications software downloads at SourceForge.net
    I am not sure yet if there is an addon to automatically replicate client-side rules onto the server-side rules as the users edit them in their GUI... but this would be the next logical step
    //Jim

    Hello, thanks for the update despite the lack of forbidden details.. at least, the feature is in the pipeline
    Could you please clarify: did I understand correctly that the managesieve RFC and implementation by the Messaging Server are not compatible with the user's Sieve rules as maintained by Convergence (as of today)? I did not really dig deep into the RFC definition, but does it define that the IMAP server maintains one big script only (and not something like an IMAP mailbox with numerous small scripts, possibly ordered by some attribute)?
    Conversely, would the Messaging Server be able to use large singular sieve scripts pushed by an email client, and would these be useless or invisible to Convergence client?
    Thanks.
    //Jim

  • Problem while using CORDYS as FRONTEND

    Dear gurus
    i am using CORDYS (a web based application) uses connectors to deal with SAP.
    issue:- i have created a BDC to Update Actual GI date in Using VL02N. when i run the function module using SAP front end it works fine, But when i use CORDYS no field is updated.
    Cordys is passing only the Delivery number, current date is directly picked from the server so it can not be an issue of format miss match.
    even if i hard code the date it won't work.
    please suggest what measure i can take to do that
    Thanks in Advance
    Luthra, Deep

    it is already RFC enabled
    Actually it is devided into three parts.
    First Create Delivery using BAPI_DELIVERYPROCESSING_EXEC
    then it uses BDC to update Actual GI date which is not done by bapi
    and then third is to download a text file on a perticular address.
    my function module is able to create delivery that means the problem is not with the miss match of fields.

  • How do I pass a "deep structure" to an RFC?

    Okay, I am expecting to receive a table of data for processing from XI.  This data will be calling a BAPI to post Incoming Invoices.
    Each record in the table represents a single Incoming Invoice and will be a "deep structure."  The deep structure will consist of a structure of Header data (occuring once per Invoice) and a table of Line Item data (occuring one to many times per Invoice).
    After defining my deep structure, I assigned it as an IMPORTING parameter in my remote-enabled function.  SAP didn't like it, so I created a table type (with a line type equal to my deep structure) and assigned it to the TABLES parameter.  SAP came back and told me that deep structures weren't allowed with RFCs!
    Yikes!  I read SAP's recommendation about creating some sort of foreign key, and splitting the data into separate tables (breaking apart the deep structure).  I assume this means that I could read an Invoice Header Data table, then go read the Invoice Line Item Data table for all records matching whatever "key" I designate -- correct?  Is this what I am resigned to do, or is there a way I can keep my deep structure?
    Thank you.  All helpful posts receive points!
    Dave

    1st responder --
    LIKE isn't an option in the "Type" drop-down box; I tried entering it, but SAP will not accept it.  This is all within my function module, with the various tabs where I can specify IMPORT, TABLES, etc. (the parameters for my function).  Is there some other place I should be doing that?
    2nd responder --
    What do you mean by passing it "separately"?  I'm not sure I understand.

  • Message Mapping RFC structure to deep XML structure

    Hello,
    I have a message mapping I am struggling with. The outbound interface is an RFC with structure like this:
    RFC_send_material
    -material (1..unbounded)
    --matnr
    --meins
    --brgew
    -description (1..unbounded)
    --matnr
    --vkorg
    --text
    The inbound interface should look like this:
    Materials_from_SAP
    -material (1..unbounded)
    --matnr
    --meins
    --brgew
    --description (0..unbounded)
    ---vkorg
    ---text
    My problem is to get all the description connected to the matnr together.
    Examples with data:
    Outbound rfc:
    <RFC_send_material>
       <material>
          <matnr>100</matnr>
          <meins>c1</code1>
          <brgew>c2</code2>
       </material>
       <material>
          <matnr>101</matnr>
          <meins>c1a</code1>
          <brgew>c2a</code2>
       </material>
       <material>
          <matnr>102</matnr>
          <meins>bv102</code1>
          <brgew>addd102</code2>
       </material>
       <description>
          <matnr>100</matnr>
          <vkorg>NO10</sales_org>
          <text>testing100</text>
       </description>
       <description>
          <matnr>102</matnr>
          <vkorg>SE10</sales_org>
          <text>testing102</text>
       </description>
       <description>
          <matnr>102</matnr>
          <vkorg>DK10</sales_org>
          <text>testing103</text>
       </description>
    </RFC_send_material>
    The inbound file structure should then look like this:
    <Materials_from_SAP>
       <material>
          <matnr>100</matnr>
          <meins>c1</meins>
          <brgew>c2</brgew>
          <description>
             <vkorg>NO10</vkorg>
             <text>testing100</text>
          </description>
       </material>
       <material>
          <matnr>101</matnr>
          <meins>c1a</meins>
          <brgew>c2a</brgew>
       </material>
       <material>
          <matnr>102</matnr>
          <meins>bv102</meins>
          <brgew>addd102</brgew>
          <description>
             <vkorg>SE10</vkorg>
             <text>testing102</text>
          </description>
          <description>
             <vkorg>DK10</sales_org>
             <text>testing103</text>
          </description>
       </material>
    </Materials_from_SAP>
    So as you see, my problem is to get the correct description belonging to the material. Hope anybody can help with doing this in Message Mapping.
    Regards,
    Per

    Hi PRW,
    As Michal said correctly, it is hard to describe in words, so here are some pictures which I think is the solution of your problem.
    Description mapping  : http://www.flickr.com/photos/23639237@N02/3220030016/sizes/o/
    VKORG mapping      : http://www.flickr.com/photos/23639237@N02/3219181675/sizes/o/
    Text  mapping           : http://www.flickr.com/photos/23639237@N02/3219182919/sizes/o/
    UDF  CODE             : http://www.flickr.com/photos/23639237@N02/3219184005/sizes/o/
    And the Final Reslut : http://www.flickr.com/photos/23639237@N02/3220035356/sizes/o/
    Regards,
    Sarvesh

  • XI: RFC -- JDBC communication deep structure

    Hello to all!
    I've got a RFC <--> JDBC szenario. Insert an update statements work fine.
    Now I want to implement a "SELECT"-statement. Therefore the XML-SQL-statements needs a <key>-tags such as:
    <key>
       <col1>value</col1>
       <col2>value</col2>
    </key>
    <key>
      <col2>value</col2>
    </key>
    To represent the key structure in ABAP I did the following steps
    - I created a structure "keyvalue" with fields: column, value (for <col>value</col>),
    - a table type "andkey" with line type "keyvalue",
    -  another table type "orkey" with linetype "andkey"
    I use the table type "orkey" as exporting parameter for the element "selectkey" in my rfc funtion module :
    CALL FUNCTION 'FUBA_JDBC' DESTINATION 'XI'
      EXPORTING
        selectkey         = it_key
      TABLES
        outtab            = it_outtab
      RESPONSE          =
    My problem is now, that the rfc function module creates a shortdump: CALL_FUNCTION_OPEN_ERROR
    Does anybody know a solution? Could I use the table type "orkey" in the rfc?
    Thanks for your suggestions,
    Christian

    Christian,
    This should probably be posted in the abap forum, you can get some help there.
    Regards
    Ravi Raman

  • Passing values to RFC holding structure.

    Hi Experts,
    I have DC which needs to update backend table through RFC.  In this RFC i have a structure in import tab which holds 2 fields.
    From webDynpro Java code , i have to pass the those 2 fields as input before when i execute the model.
    How can i write code for inputing the values for this structure fields ?
    thanks in advance.
    Regards,
    suresh

    Hi Suresh,
    Steps to execute you Adaptive RFC Model:
    1. Create an instance of the BAPI's input structure-
    <Your BAPI Name>_Input input = new  <Your BAPI Name>_Input();
    2. Set the two input parameters to this input structure with desired parameter values-
    input.set<Your Para 1>(<Desired Parameter Value>);
    input.set<Your Para 2>(<Desired Parameter Value>);
    3. Create and Bind a model node in context to the input structural node of Your BAPI using model binding. Now using code bind the instance of the input structute to the model nodel in conext as stated below-
    wdConext.node<Your Custom created Model Node in Context>().bind(input);
    4. Execute the model and invalidate the output node-
    try{
                   wdContext.current<Your Model Node in Conext>().modelObject().execute();
                    wdConext.node<Output Node in the conext>().invalidate();
    }catch(Exception){
    5. Pick all the output parameters from the Output Node in the context.
    Hope it helps!!
    Regards,
    Tushar S

  • RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'

    I am having this error pop up very frequently on some new SAP systems.  This will randomly happen and keep us from being able to release transports and import them in STMS.  I receive the following error:
    There was an attempt to start the transport control program tp using the local RFC interface.
    An error occurred here.
    Error code: 4
    RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
    - When I check the Transport Tool (STMS: import queue> check> transport tool) I get the following information:
    timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Time
    out during connection setup (check that partner exists
    - When checking the TP System Log I receive the same error.  The RSTPTEST report does not give any additional information.  SM21 shows a warning and an error:
    Warning:
    Communication Error, CPIC return code 020, SAP Return code 456
    Dialog Process No. 000
    Problem cl: SAP web AS problem
    Package: STSK
    Further Details:
    Module Name: thxxhead
    Line: 7488
    Error Text: 020456
    Caller: ThRecei
    Error:
    Problem cl: transaction problem
    Package: STTO
    All of these errors are only pointing to a time out.  I cannot figure out why this is happening.  I checked the TMS RFC connection in SM59 and they are fine.  I have been able to work around this issue in 2 different ways.  First, I can delete the files in the "\trans\tmp" directory on the server.  Sometimes this resolves the error.  Else I have to restart the system.
    I need to understand where this issue is coming from and how to resolve it.  It is becoming more and more frequent.  Thank you for your help!

    Hi,
    i have had similar issues during this week. After looking for a solution everywhere i found out that i didn't set up the FQDN on this system.
    Symptoms were:
    se38 > RSTPTEST timed out sometimes(not always)
    sm59 > TCP/IP connections > CALLTP_WindowsNT > test connections timed out sometimes (again, not always)
    STMS Overview > Systems: I was not always able to distribute and activate configuration from the Domain controller via Extras > Distribute and Activate Configuration (it died on the mentioned system)
    Transports failed mostly with the same error.
    The error log was somewhere deep in ST11. It could not resolve our FQDN.
    The solution, for me, was to add our FQDN to the WINDIR\System32\drivers\etc\hosts file.
    We upgraded the kernel as well (from 7.20 patch 046 to most current) but this didn't help.
    The FQDN is a concatenation of computer name and dns suffix of the network (if you have none, you can add one via rightclick on the used network adapter>ipv4>properties>Advanced>DNS tab, so in the end the host file looked like
    127.0.0.1   localhost   computer-name.ourSuffix.com
    After this line has been added, the error stopped and the transports work again.
    I hope it helps. Good luck.

  • RFC input structure

    Hello,
    I am trying to call a RFC from my WebDynpro application.
    The RFC has a mandatory input structure called PERSDATA.
    I am using the following test code to call the RFC:
         IWDMessageManager manager = wdComponentAPI.getMessageManager();
         try{
              wdContext.nodeZ_Portal_Get_Timesheet_Input().bind(new Z_Portal_Get_Timesheet_Input());
              wdContext.currentZ_Portal_Get_Timesheet_InputElement().setKeydate(new Date(105,9,27));
              wdContext.nodePersdata().bind(new Cats_Its_Persdata());
              wdContext.currentPersdataElement().setPernr("00003000");
              wdContext.currentZ_Portal_Get_Timesheet_InputElement().modelObject().execute();
              wdContext.nodeOutput().invalidate();
         } catch(WDDynamicRFCExecuteException ce) {
              manager.reportException(ce.getMessage(), false);
    When I run this code I get the errormessage:
    <b>Mandatory parameter PERSDATA of method Z_PORTAL_GET_TIMESHEET missing.</b>
    When I display the input structure in my view (in a table) it displays one row with pernr set to 00003000 (so it seems to me that the input structure is ok).
    What am I doing wrong here?

    Hallo Johan,
    your mistake is based on the fakt, that you did not correctly aggregate your model object graph. Instead you operated on the context itself. The context only references the model objects within the model object graph. Relations between context nodes and context node elements are not automatcally mirrored within the model object graph. Principally you have to aggregate your model object graph first (independant from the contex) and afterwards you can reference the executable model class within the toplevel context node element.
    I assume, that your code should look like this:
    IWDMessageManager manager = wdComponentAPI.getMessageManager();
    try {
      // Aggregate model object graph
      Z_Portal_Get_Timesheet_Input timeSheetInput =
      new Z_Portal_Get_Timesheet_Input();
      timeSheetInput.setKeydate(new Date(105, 9, 27));
      Cats_Its_Persdata persData = new Cats_Its_Persdata();
      persData.setPernr("00003000");
      timeSheetInput.setPersdata(persData);
      // Bind executable model object to context node 'Z_Portal_Get_Timesheet_Input'
      wdContext.nodeZ_Portal_Get_Timesheet_Input().bind(timeSheetInput);
      // Execute model object
      wdContext
        .currentZ_Portal_Get_Timesheet_InputElement()
        .modelObject()
        .execute();
      // Invalidate output node so that the context-to-model-object-references will be updated
      wdContext.nodeOutput().invalidate();
    } catch (WDDynamicRFCExecuteException ce) {
    manager.reportException(ce.getMessage(), false);
    Also have a look at my related answer within the forum thread Executing model : deep structure in importing parameter of RFC which deals with the same issue.
    Regards, Bertram
    Regards, Bertram

  • String in non-RFC table types

    Hello all,
    I have a structure that also have two members of ABAP type String (yes, that string, not char255 or so ). When I declare a table type inheriting from that type, everything is quite fine, so it seems table having dyn. Strings is okay as far as I do not want to do RFC with it.
    Now, when I create a function module and want to use that table type, the compiler gives me that error message upon syntax check:
    >>
    when using "WITH HEADER LINE", the line type cannot be a table type
    <<
    Now, that is no ABAP that I have written but the auto-generator for the include. That line it complains, there is just no definition with a header line. So, is using the String type possible at all? I think this is an error having indirectly to do with it, since I know the difference on table with and without header line/work area and so...
    Btw.: this is a 4.7 Release I am talking about.
    Thanks and regards,
    Timo

    Hi,
    it is possible:
    1. define your structure ZZ_DDIC_STRING with strings in DDIC
    2. define a table type ZZ_DDIC_STRING_TAB using this structure ZZ_DDIC_STRING
    3. define a RFC FM with Imp/Exp-parameters (not a Table-Param) using this table type ZZ_DDIC_STRING_TAB
    4. call the FM:
    DATA: lt_string_tab type ZZ_DDIC_STRING_TAB,
          ls_string_tab type line of lt_string_tab.
    ls_string_tab-string1 = 'some text'.
    ls_string_tab-string2 = 'some more text'.
    append ls_string_tab to lt_string_tab.
    CALL FUNCTION XYZ
        DESTINATION 'MY_DESTINATION'
        EXPORTING
          I_STRING_TAB = lt_string_tab[]
        IMPORTING
          E_STRING_TAB = lt_string_tab[]
    This will work with almost any deep structure too.
    Regards,
    Juergen
    P.S.: pls. post Reward Points if this was usefull! Thanks!

  • Performance check in RFC

    Hi All,
    I have created a remote enabled function module.
    Based on the import parameter value ,  values are populated in the internal table of the export parameter ( which has no of recortds).
    The RFC works as expected.
    But when i do the syntax check, it shows the message
    "Paratmeter it_wbs ( table type ztwbs of structure zswbs )  can reduce performance in RFC " as a warning.
    I should not get this warning message. What i have to do stop getting this warnig message from the RFC .
    If anyone encountered the problem. ...... please put your valuable suggestions and hints to solve this.
    Thanks
    ABAP Developer

    Hello
    You will always get this warning when using table types as RFC parameters. If you replace an IMPORTING parameter using a table type (e.g. BAPIRETTAB) with the corresponding TABLES parameter (e.g. BAPIRET2) then the warning will disappear.
    However, the general rule is to avoid TABLES parameters in function modules and replace them by IMPORTING / EXPORTING parameters. Therefore I would ignore the warning at the moment and only consider it again if you really have a performance bottleneck here.
    The long text for the warning (FL 397) is shown below:
    NA FL397
    Short Text
         Parameter &1 (type &2) can reduce performance in RFC
    Diagnosis
         The parameter contains a data type that, in the external system, can
         lead to a high memory consumption and poorer performance. Affected by
         this are parameters in IMPORT, EXPORT, and CHANGING parameters that use
         "deep, nested" (that is, type 2) data types.
         Remember also that such data types can cause a large load on the network
         since they can contain high data volumes and are not compressed in the
         selected definition during transfer.
         You can avoid possible disadvantages if you use the TABLES parameter
         instead. In this case, conversions at the interface may be possible.
         These are described below. A flat structure refers to a structure that
         contains only fields of the data types ACCP, CHAR, CLNT, CUKY, CURR,
         DATS, DEC, FLTP, INT1, INT2, INT4,LANG, NUMC, PREC, QUAN, RAW, TIMS, or
         UNIT.
         SYMPTOM:
         1.  A flat structure that contains at least one field of a STRING type.
         2. A table whose lines always consist of the same, flat strucutre.
         3. A table whose lines always consist of the same flat structure, but
         contain at least one field of a STRING type.
         4. A table that contains tables whose lines consist of a flat structure
         in each case.
    Procedure
         1. Check whether a fixed size can be defined for the field.
         2. You can switch the IMPORT, EXPORT, or CHANGING parameter immediately
         to the TABLES parameter.
         3. You can only switch the IMPORT, EXPORT, or CHANGING parameter to the
         TABLES parameter after the STRING type fields have been converted to
         fields of a fixed size.
         4. You can switch the IMPORT, EXPORT, or CHANGING parameter to several
         TABLES parameters.
         Possibly, "foreign keys" must be supplemented for the connection between
         the tables.
         Example: Position numbers can be explicitly contained in the data; these
         can then function as "foreign keys".
         5. Arbitrary combinations from the named tyes that can then be be split
         into fields of fixed size (STRING types), similar to the description
         above, and distributed to several TABLES parameters.
    Regards
        Uwe

  • RFC:Complex structure

    Dear experts,
    In my PI box,i used one RFC SXMB_GET_MESSAGES.I provided input to the table parameter with over 155 values.
    My attempt was to retrieve from output table parameter which is a deep structure
    If i drill EX_MSG_CONTENT , i get table MSG_VERS_T as one of table output and on further drilling this i get PROP again of type table line.
    <table>EX_MSG_CONTENT_LIST -> <table> MSG_VERS_T ->  <table> PROP
    Ultimately i fetched two fields from table PROP.Only issue is that if i am providing 155 input values i get 36 output values only.
    Further incase i put 222 input values then output values get affected in same ration ex 56 output values and so on..
    What should  i conclude.IS this because RFC (Remote Enabled) doesnot support complex nested structures and i should give up this assignment or may be i need to put something in addition. ?.For those of you familiar with java i am trying something like this
    _ob_c.function.execute(ob_c.destination);    //Problematic as it return less number of rows_
    call function statement:
    ArrayList<PayLoadType> payloads  = new ArrayList<PayLoadType>(fetchmessagepayloads(tableresout)); 
    //Works well as content fetched is actually equal to number of records fetched above.
    public ArrayList<PayLoadType> fetchmessagepayloads (JCoTable tableobj)
    int count = 0;
    ArrayList<PayLoadType> oba = new ArrayList<PayLoadType> ();
    while (count < tableobj.getNumRows()) {
    PayLoadType obj = new PayLoadType();
    JCoTable subtab1  = tableobj.getTable("MSG_VERS_T");
    count = count + 1;
    int rec = subtab1.getNumRows();
    int numrecs = 0;
    while ( numrecs < rec )
    subtab1.nextRow();
    numrecs = numrecs + 1;
    JCoTable subtab2  = subtab1.getTable("TPROP");
    numrecs = 0;
    rec = subtab2.getNumRows();
    while (numrecs < rec )
    numrecs = numrecs + 1;
    if (subtab2.getString("LCNAME").trim().equals("Main")) {
    obj.msgid = subtab2.getString("MSGGUID");
    obj.payload = subtab2.getString("CONTENT");
    oba.add(obj);
    subtab2.nextRow();
    tableobj.nextRow();
    return oba;
    Edited by: aditya  sharma on Aug 16, 2010 10:20 AM

    Hi,
    The problem is basically in message mapping from file to RFC external message.
    The option 2 is working now and I get correct converted file strcuture after FCC and into RFC and also a correct RFC payload.
    However, business is stressing that can send the file in the format as given in Option 1 where u have different structure - Header and Items. This is not coming out correct in RFC payload as the header has 5 fields as compared to more in item but the header and item are still being mapped to the flat RFC structure and this is creating a mismatch. The item line is missing the 5 fields from Header.
    How do i do the FCC in this situation to get the correct structure in RFC?
    This means that in RFC payload, the first line should be the one as below-
    H,100890,P100,A02,S101,AUD#
    The 2 records after this as received in RFC internal table should be as 2 given below-
    I,P,NULL,TH,Test PO TH,1,EA,100,10160000,A002,0001,720090,E.1.4.3,,,,VT#
    I,P,NULL,TH,Test PO TH1 2,2,EA,100,10160000,A002,0001,720090,E.1.4.3,,,,VT#
    However, the 2 structures contain variable field columns.
    Please help.
    Regards,
    Archana

  • ABAP RFC doen't get called, although XI says it does

    Hi all,
    sorry for my noob question, but I'm completely new to XI.
    The following situation:
    I've a scenario, where some mappings are done in XI and at the end the payload is handed over to a ABAP RFC function to persist the mapped data to the backend system.
    I've got a communication channel set up,
    Inferface mappings are fine,
    receiverdetemination looks fine,
    SXMB_MONI shows all messages, all with checkered flags,
    The last message of XI lists properly the RFC function to be called. Receiver determination is ok, lists the proper business system which has a communication channel (receiver) available.
    But when I have a look at SLG1, not even a starter log is written. Nothing. It seems that the ABAP function is never being called.
    So my questions are:
    Where can I find some information what might get wrong?
    Any ideas where I can have a look at, what might be configured wrong?
    Can I test the login credentials I gave in the communication channel for the business system?
    The SOAP message part "RunTime" lists in the "User" element a different user name that I gave in the Business System / Communication Channel. Where does this one come from?
    Any help and ideas appreciated,
    Tnx,
    Martin.

    Hello Manjusha.
    >
    Manjusha Nair wrote:
    > Can you check in Runtime Workbench.
    > Goto Message monitoring.Here you please check the details of your message .
    >
    > ref:
    > http://help.sap.com/saphelp_nw04/helpdata/en/2f/4e313f8815d036e10000000a114084/frameset.htm
    Oh thanks! This was the useful hint!
    With the help of the Message Monitoring I could find out, that there was an authorization problem.
    Although the password was given properly.
    I found out, that XI doesn't like whitespaces at the beginning or at the end of a password!! Somewhere deep down, there must be a trim() call on the password. ARRRGGHH Cost'd me several days!
    Thanx to all!
    Martin.

  • RFC Structure Reference in V12

    We had a custom RFC developed to perform a read on a Z_Table.  The ABAP developer unfortunately used a complex deep structure that could not be used with the JCO connector.
    We have had the problem with the RFC fixed, but xMII has retained the original polluted structure information, so using the current RFC name the JCO throws an error.
    If we rename the RFC 'ie. myRFC_2', all is well.  However, we would like to stick with our original naming convention.
    How can we clear out any cached structure information on this RFC in V12.  I'm told that in previous versions we could have deleted the cached structure file(s).  I'm assuming that with 12 they are in the DB.  Is there a way to do it from within Netweaver, or do I need to contact a DBA?
    Regards,
    Rod Hoffman

    Udayan,
    Thanks a bunch.  My apologies, my search technique is a bit rusty this morning.
    Regards,
    Rod Hoffman

Maybe you are looking for