Logon exit for jco rfc call

Hi. There is a external system to access our SAP rfc function by jco. I want to limit the jco access must be come from a certain ip.
I found user exit SUSR0001 and can limit GUI logon. But it is no effect on jco logons. Is there another user exit for jco logon or others way to limit jco logon? Please give me some help. Thanks.

Thanks for the attention guys.  A little clarification.
1.  I have been assuming that I cannot use the IllumnLoginPassword for the JCO SAP password in the action block.  If this is NOT true, then it solves my whole problem.
2.  It would not work to prompt a shop floor person for their password every time they do an operation completion.  Well, at least
if I don't want to not get lynched! 
3.  I am planning on prompting people every time they log on for their ECC password and retaining it somewhere secure while they are logged on (and longer if they skip the logoff step.)
4.  I have been focusing on how/where to retain the password, but also need a way to encrypt it during transmission.  Jeremy said the applet/BLS would at least encode it for me.  That is good.
--Amy Smith
--Haworth
Edited by: Amy Smith on Feb 18, 2010 1:30 PM

Similar Messages

  • User Name and Password for JCO RFC call to BAPI

    Hi all,
    What I think I know:
    --We do NOT have Single Sign On configured so don't tell me to use SSO please - I agree, but...
    --We have a requirement to do a goods receipt which prints labels for the handling units 
    .....The printer to which the labels are directed depends on the user who is running the transaction
    What I think this means
    --We will need to specify a user name and password in the RFC call so the label will go to the correct printer
    --I cannot use the IllumnLoginPassword (or whatever its name is) for the password
    --I need to prompt the user for their password a second time after they login to our MII app
    The problem
    --I will need to store the password somewhere for the duration of the session
    ......In session variable that has been encryted
    .............I didn't see an encryption action block so I could create my own
    ......In the database using database column encryption
    .............A little bit of a pain, but not too bad
    Any corrections, alternatives, ideas .... ???
    Thanks,
    --Amy Smith
    --Haworth

    Thanks for the attention guys.  A little clarification.
    1.  I have been assuming that I cannot use the IllumnLoginPassword for the JCO SAP password in the action block.  If this is NOT true, then it solves my whole problem.
    2.  It would not work to prompt a shop floor person for their password every time they do an operation completion.  Well, at least
    if I don't want to not get lynched! 
    3.  I am planning on prompting people every time they log on for their ECC password and retaining it somewhere secure while they are logged on (and longer if they skip the logoff step.)
    4.  I have been focusing on how/where to retain the password, but also need a way to encrypt it during transmission.  Jeremy said the applet/BLS would at least encode it for me.  That is good.
    --Amy Smith
    --Haworth
    Edited by: Amy Smith on Feb 18, 2010 1:30 PM

  • Asyncronic JCO RFC call from JAVA to ABAP

    Hi,
    Please could you provide a sample java code to establish JCO RFC call to ABAP?
    Thanks.

    Hi Denis,
    Import the model In NWDS for ABAP for RFC.
    Please check here [Accessing ABAP Functions using the Adaptive RFC Model |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00f7103-6790-2a10-ac9c-fcac7c5b18a3?quicklink=index&overridelayout=true]
    [Web Dynpro Model: Backend Access|http://www.sdn.sap.com/irj/sdn/nw-wdjava?rid=/webcontent/uuid/403e6bf5-426e-2910-b0a8-a95548724af9#section10 [original link is broken]]
    Also check here /docs/DOC-8661#section10 [original link is broken]
    Hope it helps,
    Redards,
    Arun

  • Strange response time for an RFC call viewed from STAD on R/3 4.7

    Hello,
    On our R/3 4.7 production system, we have a lot of external RFC calls to execute an  abap module function. There are 70 000 of these calls per day.
    The mean response time for this RFC call is 35 ms.
    Some times a few of them (maybe 10 to 20 per day) are way much longer.
    I am currently analysing with STAD one of these long calls  which lasted 10 seconds !
    Here is the info from STAD
    Response time :                10 683 ms
    Total time in workprocess : 10 683 ms
    CPU time  :                               0 ms
    RFC+CPIC time :                       0 ms
    Wait for work process           0 ms
    Processing time           10.679 ms
    Load time                            1 ms
    Generating time                   0 ms
    Roll (in) time                        0 ms
    Database request time         3 ms
    Enqueue time                      0 ms
    Number      Roll ins            0
                     Roll outs           0
                     Enqueues         0
    Load time   Program             1  ms
                      Screen              0  ms
                     CUA interf.          0  ms
    Roll time    Out                 0  ms
                      In                  0  ms
                    Wait                0  ms
    Frontend    No.roundtrips       0   
                      GUI time            0  ms
                      Net time            0  ms
    There is nearly no abap processing in the function module.
    I really don't uderstand what is this  10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
    A usual fast RFC call gives this data
    23 ms response time
    16 ms cpu time
    14 ms processing time
    1 ms load time
    8 ms Database request time
    Does anybody have an idea of what is the system doing during the 10 seconds  processing time ?
    Regards,
    Olivier

    Hi Graham,
    Thank you for your input and thoughts.
    I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
    I'm used to investigate performance problems with ST03 and STAD.
    My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
    Kernel 6.40 patch level 109
    We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
    I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step  of type <no buffer>. (what is this ?)
    This SAPSYS dialog step has the following data :
    User : SAPSYS
    Task type : B
    Program : <no buffer>
    CPU time                       0 ms
    RFC+CPIC time              0 ms
    Total time in workprocs    5.490 ms
    Response time               5.490 ms
    Wait for work process           0 ms
    Processing time             5.489 ms
    Load time                            0 ms
    Generating time                   0 ms
    Roll (in+wait) time                0 ms
    Database request time          1 ms ( 3 Database requests)
    Enqueue time                       0 ms
    All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
    It looks like the system was frozen during 5 seconds...
    Here are some extracts from STAD of another case from last saturday.
    11:00:03     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     13     13     0     0
    11:00:03     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     16
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     77     77     0     16
    11:00:04     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     16
    11:00:05     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     16
    11:00:05     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     53     53     0     0
    11:00:06     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     76     76     0     0
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     20     20     0     31
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     0
    11:00:06     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     13     13     0     0
    11:00:06     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     34     34     0     16
    11:00:07     bt1sqkvh_PLG_18      RFC     R     0     USER_LECDIS     15     15     0     0
    11:00:07     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     13     13     0     16
    11:00:07     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     0
    11:00:07     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     23     13     10     0
    11:00:07     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     38     38     0     0
    11:00:08     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     20     20     0     16
    11:00:09     bt1sqkvg_PLG_18      RFC     R     0     USER_LECDIS     9 495     9 495     0     16
    11:00:09     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     9 404     9 404     0     0
    11:00:09     bt1sqkvh_PLG_18      RFC     R     1     USER_LECKIT     9 181     9 181     0     0
    11:00:10     bt1fsaplpr02_PLG RFC     R     3     USER_LECDIS     23     23     0     0
    11:00:10     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     8 465     8 465     0     16
    11:00:18     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     18     18     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     89     89     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     75     75     0     0
    11:00:18     bt1sqkvh_PLG_18      RFC     R     1     USER_LECDIS     43     43     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     1     USER_LECDIS     32     32     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     1     USER_LECDIS     15     15     0     16
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     0
    11:00:18     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     69     69     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     49     49     0     16
    11:00:18     bt1sqkve_PLG_18     RFC     R     5     USER_LECKIT     19     19     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     15     15     0     16
    The load at that time was very light with only a few jobs starting :
    11:00:08 bt1fsaplpr02_PLG RSCONN01                     B 31 USER_BATCH     39
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 31 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH                B 33 USER_BATCH     64
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 33 USER_BATCH     43
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 34 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 35 USER_BATCH     37
    11:00:09 bt1fsaplpr02_PLG RVV50R10C                    B 34 USER_BATCH     60
    11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH    206
    I'm thinking also now about the message server as there is load balancing for each RFC call ?
    Regards,
    Olivier

  • Complete information only for activated RFC calls ( settings) error SM66

    Hi,
       I have a BW, CRM 5.0 & ECC 6.0 instances.. And I have created new users in all the systems with SAP_ALL permissions. After successfull password change, I entered the SM66 T-Code  to view the WP list but I am getting error "Complete information only for activated RFC calls (> settings)" like this. I couln't find any log in SM21for this error. But I  am able to view all the work process in SM50 and I am able to view all the Application Servers list in  SM51 T-Codes.
    Thanks
    Suresh Sammeta

    Hi,
    This is not an error but an information message :
    Diagnosis
    Complete information on report, transaction, memory usage amongst other things, is only available when the option 'Only display short information, avoid RFC' under 'Settings' is deactivated.
    Regards,
    Olivier

  • How to set the language for a RFC call ?

    Hi,
    when calling from BSP (WAS620) to our R3 using RFC the results (units, ...) are always in DE. How do the call to get the results in EN?
    Language in RFC Destination/Logon&Security does not have an effect.
    thx for your support.

    Martin,
    I am not sure whether this is a logon problem.
    If you run the function module in transaction SE37 then you will get PC because there are some exits associated to it.
    When you call it from "outside", then the internal value is returned to the caller.
    The same happens when using BAPI from languages like Java or .Net
    The material field - in particular - is well-known for this behaviour.
    Hope someone else could testify because I haven't crossed the problem myself.
    Check this thread for instance:
    sap.net connector error
    If you have a doubt, then set an external breakpoint in the remote system for the RFC user. Then, check the content of the <i>sy-langu</i> field.
    Best regards,
    Guillaume
    Message was edited by:
            Guillaume GARCIA

  • SAP adapter giving the merged result set (First RFC call data + Second RFC call data) for second RFC call

    I have a WCF Adapter service to call a SAP RFC. When I call the RFC first time, it gives me correct no of result set but when I call this RFC second time immediately after first call, it gives me merged result set (First Result set + Second Result Set).
    e.g. We have a RFC which receives vendor number and blank object of result set as parameter and gives back the list of purchase orders as Response in object of result set for that vendor.
    Suppose, we have a vendor "a" and vendor "b". For vendor "a" there are 5 purchase orders and for vendor "b", we have 4 purchase orders in SAP. When I call the WCF adapter service for this RFC for vendor "a",
    it gives me 5 purchase orders. Immediately after first call, when I call WCF service for vendor "b", it gives me 9 (5+4) purchase order records which is wrong.
    In brief, one RFC call is affected by its previous call.
    For each new WCF request, a new object of result set is created, connection is opened, rfc is executed and connection is closed.
    Can anybody have any idea on this?
    Thanks.
    Thanks, Nishant Gupta

    Hi，
    Please refer to the document
    http://seroter.wordpress.com/biztalk-and-wcf-part-vii-about-the-biztalk-adapter-pack/

  • Use PI between J2EE and CRM for JCO/RFC?

    Hello,
    I have a question concerning the use of PI RFC-Adapter:
    is it possible to use PI as an intermediator between a Netweaver J2EE System which connects to another system (eg. ABAP) using JCO/RFC (giving the following setting:
    [NW Java -> JCO] -> [PI] -> [RFC-Receiver-System]
    To be more specific, we plan using CRM eCommerce Shop. This Java based shop connects to CRM backend using JCO/RFC. The Java based shop needs to be placed in a different network zone than CRM system and the only (allowed) way to have a connection from the zone with the shop is through PI.
    Best regards,
    Manuel

    Hello Rajeev,
    yes, this would be the best way - but unfortunately the policy does not let us connect directly using jco/rfc. Only ways using PI (decentral advanced adapter engine) are allowed.
    Is this possible to use PI to transfer the jco/rfc requests between the two network zones or does PI not support this scenario?
    Regards,
    Manuel

  • Enhancement /User Exit for logic setting call date / Horizon

    Due toe planning in IP10 we have a horizon set by the system for (eks.) 80%. This is working OK for small planning intervals (i.e. up to 24 mth intervals).
    However when intarval exceeds this limit we will set the call date to be maximum 30 days (for instance) ahead of the sceduled start date of the order.
    Thus we need a user-defined way to manipulate / set the call date by a user exit (logic in ABAP - or by IMG settings if possible) that differs from the standard SAP setting for this date.
    The question is then how we - in best practice -  can do so.
    Please advice if you need mor information on this issue.

    Hi
    Find the available exits with the following program:::
    *& Report  ZFINDUSEREXIT
    report  zfinduserexit.
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
    tables : tstct.
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    parameters : p_tcode like tstc-tcode obligatory.
    select single * from tstc where tcode eq p_tcode.
    if sy-subrc eq 0.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'PROG'
    and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
    select single * from trdir where name = tstc-pgmna.
    if trdir-subc eq 'F'.
    select single * from tfdir where pname = tstc-pgmna.
    select single * from enlfdir where funcname =
    tfdir-funcname.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'FUGR'
    and obj_name eq enlfdir-area.
    move : tadir-devclass to v_devclass.
    endif.
    endif.
    select * from tadir into table jtab
    where pgmid = 'R3TR'
    and object = 'SMOD'
    and devclass = v_devclass.
    select single * from tstct where sprsl eq sy-langu and
    tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
    select single * from modsapt
    where sprsl = sy-langu and
    name = jtab-obj_name.
    format color col_normal intensified off.
    write:/1 sy-vline,
    2 jtab-obj_name hotspot on,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
    else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
    endif.
    else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
    endif.
    at line-selection.
    get cursor field field1.
    check field1(4) eq 'JTAB'.
    set parameter id 'MON' field sy-lisel+1(10).
    If there are no available user exits you could go for badi's.
    To search for a badi, go to se 24 display class cl_exithandler. double click on method get_instance, get a break point on case statement. execute and start the required transaction in new session. look for variable exit_name. It would show the available badi's.
    Please reward if useful....
    regards
    Dinesh

  • Are Import parameters compressed in external JCo RFC calls?

    I would like to send XML data from a Java program to an SAP ABAP System running on NW 7.02.
    The connection is done by Java Connector 3.0. The XML file should be passed as a parameter of an RFC function module.
    In older versions the data would have been passed as a TABLES parameter and would be compressed automatically if the payload exceeds 8kb or the connection would be marked as a slow connection. (see also Note 977407).
    Now I would like to use the basXML RFC protocol. There it is advised to use Table Types in Import parameters instead of TABLES parameters for table data. Now will the data be compressed if I send them as Table data in an Import parameter? And will they also be compressed when I send them as an Import parameter as STRING or XSTRING instead of a table?
    Unfortunately the help documentation is incomplete on these topics and I did not find any details for this scenario.

    Yes it is possible
    SAP JCo can be implemented with Desktop applications and with Web server applications.
    SAP JCo is used as an integrated component in the following applications:
    ●     SAP Business Connector, for communication with external Java applications
    ●     in the Application Server, for connecting the integrated J2EE server with the ABAP environment.
    SAP JCo can also be implemented as a standalone component, for example to establish communication with the SAP system for individual online (web) applications.
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/09/a4a9e1d51d11d6b2c200508b5d5c51/frameset.htm

  • User Exit for Variable which calls to a Function Module is NOT working ???

    Hi all,
        I have a created a variable 'ZNBUSDAY' with Processing Type 'Customer Exit' on 0SCL_DELDAT  (Date). The query is on 0PUR_C04 and passing 0SCL_DELDAT  to Function Module  Z_WORKDAY to get the Next Business Day by using the company Calendar(30). The following code is NOT working and what is WRONG with it, PLEASE? The FM is working FINE.
    DATA: wa_calendar(2) TYPE c value '30',
          wa_znbusday    like sy-datum,
          0scl_deldat    like sy-datum,
          p_days         TYPE i value 1.
    case i_vnam.
       when 'ZNBUSDAY'.
       CLEAR wa_znbusday.
       CALL FUNCTION 'Z_WORKDAY'
         EXPORTING
         CURR_DATE        = 0scl_deldat
         NUMBER_DAYS      = p_days
         CALENDAR         = wa_calendar
       IMPORTING
         WORK_DAY         = wa_znbusday
         l_s_range-low  = wa_znbusday.
         l_s_range-opt  = 'EQ'.
         l_s_range-sign = 'I'.
         append l_s_range to e_t_range.
    endcase.
    Thanks,
    Venkat.

    Hi Venkat,
    Looks like you're only assigning type sy-datum to 0scl_deldat but not the actual value. Try the following:
    DATA: wa_calendar(2) TYPE c value '30',
          wa_znbusday    like sy-datum,
          0scl_deldat    like sy-datum,
          p_days         TYPE i value 1.
    case i_vnam.
       when 'ZNBUSDAY'.
       CLEAR wa_znbusday.
       0scl_deldat = sy-datum.
       CALL FUNCTION 'Z_WORKDAY'
         EXPORTING
         CURR_DATE        = 0scl_deldat
         NUMBER_DAYS      = p_days
         CALENDAR         = wa_calendar
       IMPORTING
         WORK_DAY         = wa_znbusday
         l_s_range-low  = wa_znbusday.
         l_s_range-opt  = 'EQ'.
         l_s_range-sign = 'I'.
         append l_s_range to e_t_range.
    endcase.
    Kind regards,
    Alex

  • Prevent log to be created for Failed RFC calls in SM21.

    Can you find out if there is way to stop RFC cancelled transactions thru CALL_TRANSACTION from getting logged as u201Ccancelled transactionsu201D in SM21.
    Thanks in advance.
    Rajiv Kanoria

    Alsi in case there is some FM to delete the existing Logs from the SM21.
    Regards,
    Rajiv

  • For JCO , rfc gate way ,bridge, cannot find need help

    Hi!
    I am not sure about sneak preview but who are you logged in as when you say "can't find sld"?
    What happens when you try to go to "http://localhost:500XX/sld" ? Any message?
    Thanks
    BMG

    Have you check a common, trivial, issue with the connection? Connectors and cables that worked fine for ages start creating such issues.
    Some tips:
    * Try with another cable.
    * Connectors contacts get dirty, especially those that are often connected and disconnected. Not long ago a USB key and a USB drive were getting randomly suddenly disconnected. It even made my Mac OS crash sometimes. One the household must-haves, IMHO, is a contact cleaner spray. It does miracle on the connectors of your sound-system, your batteries, your computer, etc. I sprayed all the ports and cables, just in case. It solved the problem. Clean both sides, male and female. Do it as a regular maintenance.
    Hope it helps.
    BTW. I used to have my RAW format pics (CR2) converted to DNG while being downloaded. Then Photo Downloader started messing them up, so I stopped and I now use the native RAW format.
    Nick

  • Question on service userid - for RFC call

    Hi
       In XI 3.0 SP18 , we are making a RFC call from XI mapping runtime - to XI's ABAP stack - RFC function module . In the RFC receiver communication channel , I tried using service user XIISUSER , XIAPPLUSER for this RFC call - I got short dumps on XI ABAP stack mentioning that these two service users do not have authorization to make RFC calls -
    Does anybody out there know what service user on XI has RFC call authorization that can used to make RFC calls onto XI ABAP stack from its mapping runtime ?
    Correct answers will be rewarded rightaway. Thanks for your time in advance.

    Hi,
    u have to make entry in sld...
    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.
    Reward points if find useful.

  • Question: Can Jco RFC Provider registers Program Id for BW7.3

    Hello, Friends
      I encounter the following issue and I wonder whether it is supported by Netweaver product. Please help answer.
      My scenario is to create RFC (TCP/IP Connection) in ABAP server with program id registered by Jco RFC Provider (Visual Admin of NW7.02 Java)
      If my ABAP BW NW server is 7.02 version, RFC can be tested successfully. However, for this time, I worked on another ABAP BW NW 7.3 Server and I create the RFC(TCP/IP Connection) with program id registered by Jco RFC Provider. As a
    result, the RFC cannot find the program id registered by Jco NW 7.02 Java.  Does Netweaver support ABAP 7.3 RFC with Program id registered by Nw 7.02 java Jco RFC provider?
    Thanks a lot!
    Welkin

    Hi, Ejersbo
      If you are using 7.3 portal, you can refer to the following on how to register Jco RFC provider on 7.3 Java:
    (1) Open http://<server>:<port>/nwa
    (2) Search for "Jco RFC destinations", open "Jco RFC destinations"
    (3) Create a Jco RFC destination, with program id in the same name as the one which is used in your ABAP RFC in SM59
    Welkin

Maybe you are looking for