RFC Call for EarlyWatch

Hi,
What is the RFC Call for EarlyWatch with regards to extracting a monitoring report?
Thanks
John

Hi John,
Solution Manager can use its own BI or a remote BI.
If it is local the RFC will be 'NONE'
The table is E2E_WA_CONFIG
Type = SAP_BID
LINE = 1
STRING = NONE
If there is an entry of the Type =SAP_BID_M it will overrule SAP_BID
The STRING= 'value' will be the RFC that is used.
Both SAP_BID abd SAP_BID_M are found in Table   E2E_WA_CONFIG
Regards,
Paul

Similar Messages

  • Flat File-to-RFC question, multiple RFC calls for one file.

    Hi guys,
    I'm quite new to XI / PI and I have a question regarding a File-to-RFC scenario we're trying in NW PI 7.1.
    We have a flat file which has two lines with two fields each, let's take this as an example :
    001,001
    002,002
    The files needs to be converted to XML and then transferred to the RFC program which will update a table with the values above.
    In the ESR I've created 3 data types (z_row1,z_record1 and z_fileinput1), 1 message type (z_file2rfc_ob_mt), 1 message mapping (z_file2rfc_mm), 2 Service Interface (z_file2rfc_ob_si and z_file2rfc_ib_ztestpi) and 1 operation mapping (z_file2rfc_om).
    In the Integration Builder (ID) I've created everything required (The sender and receiver communication channels, sender and receiver agreement, receiver determination and interface mapping).
    We're also using content conversion to convert the flat file to XML, this does seem to work because I see all the lines/field in the message when it gets into PI. The problem is that the RFC can only accept two fields at a time and only the first line gets updated. I see that only the first line gets sent to the RFC.
    How can I make the RFC call for each and every line ?
    Thanks !!

    Create the RFC with table, which takes multiple lineitem as input and update the table in single call.
    If you want response back then call RFC as synchrounous else in Asynchrounous mode.
    By doing this in single call it will update the complete table.
    Gaurav Jain
    Reward Points if answer is helpful

  • Itanium: Rfc call for SXMI_XMB_SYSLOG_READ fails Error INVALID_DATE_TIME

    I have a distributed NetWeaver 2004S Environment: Main SAP Instance and Database are located in a CST Time Zone on the same machine. A dialog SAP instance, installed on an HP-UX Itanium Host, is located in a PST Time Zone, but, the system clock set for CST time - 2 hours behind the main SAP instance host system clock time.
    My application is installed on the HP-UX Itanium Host and connects to the local (dialog) SAP instance, and makes RFC library calls to collect data. For Syslog data, the RfcCallReceive call is made to function SXMI_XMB_SYSLOG_READ with all the required input parameters.  This call succeeds for the first time, but, fails all subsequent times if the call is repeated at 1 minute interval. Following error message is returned:
    gid:105 key:INVALID_DATE_TIME
    The date times on start and stop times are correct - they match very well with the system clock time.
    Now, if I increase the repetition interval from 1 minute to 5 minute, the Rfc call to the function SXMI_XMB_SYSLOG_READ  succeeds for the repeated calls.
    Please note that the Rfc application was compiled on an HP PA-RISC development machine, and, uses ARIES emulator to run on HP Itanium Host.
    There is another piece of information I can provide here if that helps: I am able to make 1 minute spaced repeated Rfc call to  SXMI_XMB_SYSLOG_READ function with success on a PA-RISC dialog instance of another SAP deployment that has the main SAP instance plus database on one machine in a CST time zone, and, the dialog SAP instance hosting the application on PA-RISC host on a different machine, but, in the same CST time zone.

    Hi Manoj,
    The Application and the dialog instance are on the same machine - HP-UX IA64. This is what TZ has on this host
    TZ=CST6CDT
    How do I synchronize the application and the SAP dialog instance  - they are located on the same physical machine?
    The main instance and the database are on another machine - SunOS5.10 sparc. This is what TZ has on that host
    TZ=US/Central
    The date on HP-UX IA64 (dialog instance) is
    date
    Fri Nov 21 13:13:35 CST 2008
    The date on SunOS5.10 sparc (Main Instance + Database) is
    date
    Fri Nov 21 13:13:35 CST 2008
    Please note that the dialog instance and the main instance are located geographically in PST and CST time zones - being 2 hours apart.
    I appreciate very much your effort. Looking forward to the follow-up.
    Thanks

  • RFC call having problem while calling from webdynpro

    Hi ,
    I am facing a strange problem .In my webdynpro i have a RFC function module . the structure is like this.
    Loop.
    <GET current system>.
    TRY.
    call <RFC FUNCTION MODULE> DESTInation <own system> .
    ENDTRY.
    ENDLoop
    With in the Function module we have created  a BDC seesion.
    Here the loop is running for 10 times .for the first time it is the rfc call is perfect and a session is created in sm35.
    For the second loop run the system is going to hang.and when i checked sm35 the next day 1 session is created (for the second loop)
    Like this the session are created in different days .And the session created times are like00:00:04,00:00:08 etc.
    I have checked if any hold time is there for the session but there is noting like this .
    And i digged more and checked in SM50 there the call is running in background and it is connected some other system though i have given the target system as own system.
    please advice me about this and how to find the root cause for this.
    thanks

    Thanks for your reponse .
    Here the problem is it has already been developed now the Bug is the function call is still running and the sessions created as
    below
    17.06.2010     00:00:30     SAPMSSY1
    17.06.2010     00:00:28     SAPMSSY1
    16.06.2010     00:00:36     SAPMSSY1
    15.06.2010     01:21:46     SAPMSSY1
    15.06.2010     00:59:33     SAPMSSY1
    15.06.2010     00:01:06     SAPMSSY1
    Now teh problem is why the sessions are not created at the same time i executed it.ie,on 11:06:2010.
    so,please let me know why is call is taking that much long time .(it is very rare for RFC call for such a long time ).

  • How to loop through single XML File and send multiple RFC calls?

    I am looking for the best approach to use for making multiple RFC calls (can be sequential) using a single XML file of data.  I have been attempting to get a BPM loop working, but to no avail.  My RFC only accepts a single set of delivery input and I have been told to try to work with it as is.
    input xml sample:
    <?xml version="1.0" encoding="UTF-8"?>
    <ProofOfDelivery>
       <POD>
          <delivery_number>1</delivery_number>
          <carrier_name>UPS</carrier_name>
       </POD>
       <POD>
          <delivery_number>2</delivery_number>
          <carrier_name>UPS</carrier_name>
       </POD>
    </ProofOfDelivery>
    I need to make a synchronous RFC call for each set of POD data.
    Thanks in advance!

    Thanks for the inputs.
    I tried with a BPM and multi-mapping transformation before a ForEach block.  I am getting this error:
    Work item 000000028028: Object FLOWITEM method EXECUTE cannot be executed
    Error during result processing of work item 000000028029
    com/sap/xi/tf/_ProofOfDeliveryMultiMapping_com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionRuntim
    Error: Exception CX_MERGE_SPLIT occurred (program: CL_MERGE_SPLIT_SERVICE========CP, include: CL_
    Probably because I am not making/using the container objects properly.  Here is a screenshot of my BPM.  Can anyone spot my issue or point me to an example on this sort of container use?
    [http://kdwendel.brinkster.net/images/bpm.jpg|http://kdwendel.brinkster.net/images/bpm.jpg]
    Thanks

  • BOM Explosion not happening in RFC call...

    Hi All,
    We are facing a strange issue in our project. We are using a RFC call for order creation. When we execute the FM through SE71 using a BOM material, the BOM gets exploded correctly. However, if the same material is passed through the RFC call, it is not getting exploded.
    The BAPI used for order creation is BAPI_SALESORDER_CREATEFROMDAT2.
    If any of you have encountered such an issue and know any resolution, please let me know at the earliest.
    Thanks in advance.

    Make sure that you are converting to the internal format when calling via RFC.  Meaning, that you need to have leading zeros for things like sales document numbers.  So if your sales documennt number is 12345, make sure that you are passing it to the RFC call, like 0000012345.
    Regards,
    Rich Heilman

  • Custom Metadata Extension with RFC call

    Hi all,
    I am trying to create a custom metadata extension that pulls data from ECC via an RFC call and returns values as a IMetaValueList in the getAllowedValues method.
    Does anybody have any experience?
    Thx
    Ismail

    Hello Sanjeev,
    - I Kept External break point in SRM where we are calling RFC Call for ECC, I am able to debug untill the RFC call,
    - But, on RFC Call ( CALL FUNCTION ZABC destination <Destination>), when I press F5 it is not going inside the function module.
    - I am getting Export parameter values, means ctrl is going to ECC, but not able to debugg our BE system -ECC.
    Pls suggest. Thanks for your quick reply.
    Regards,
    Mohan Vamsi

  • Target system(Destination) for RFC call ?

    Need some help in calling an RFC for xi interface.
    For triggering the data in to xi , RFC needs to be called. This RFC can be called using an ABAP Program / report . BUT inorder to call that RFC a Destination / Target system needs to be defined . Even though RFC destinations can be managed by transaction SM59 what will be the target system for calling this RFC in a generic sense?
    Like what destination i should be expecting this code : ?
    REPORT  Z_TEST.
    CALL FUNCTION 'ZFunctest' destination ????
    Please suggest
    Krishna

    Yes i now understand the scenario : well is this statment correct ?
    When we say like this :
    CALL Function 'ZTEST' Destination SIDCLNT015
    does this mean ZTEST should be there in destination system ? which means the RFC i am writing should be there on xi systems whose system id is SID ?
    As i heard some where that ZTEST should be there on targetsystem i call for ?
    Please suggest
    Krishna

  • Login information for RFC call

    Hi there,
    I would like to know if there is a way to authenticate a user via bsp and get that login information to make the RFC call to different systems.
    i tried the to call an FM via RFC directly from abap and it forces me to login and it works but when i put that code to bsp. I just get a "page cannot be displayed" error.
    I know i can enter an ID and password on sm59 for the connection but i need to let the user login
    I am using this for a user creation tool.. instead of using su01 to create a user it will be done via bsp and would like to reflect the changes done when running the reports from SUIM
    thanks in advance
    Ryan

    Hi Ryan,
    I will assume your RFC Destination already trusted system and using current user logon (see my previous reply).
    However this still prerequisite for the next step.
    Now, please correct me if my understanding is wrong.
    In your reply, you have at least 2 System, right?
    S1 & S2.
    Where S1 has BSP Application (Ex:/ FormRegistration)
    And S2 is where you control the user and Function Module.
    Do you put, generic user for all BSP Service in System S1?
    You can create another BSP Application in System S1 (Ex:/ CallingFM)
    but this time don't put default user in BSP Service.
    And from BSP Application FormRegistration, you create 1 button to call the BSP Application CallingFM.
    I will give you sample code:
    FormRegistration: address:http://systemS1.sap.com/FormRegistration/page1.htm
    HTML Part:
    ===========
    <HTML>
    <input type="button" value="Register the user" onclick="submitUser();">  
    <script>
       function submitUser(){
           document.forms[0].action = 'http://systemS1.sap.com/CallingFM/page1.htm';
           document.forms[0].target = '_new';
            //it will open new window, just put it empty if you don't want to open new window.
           document.forms[0].submit();
    </script>
    </HTML>
    Now, when user click Button "Register the user" it will open the new window.
    But because it doesn't allow you to using default user, it will prompt user id and password.
    After that it will submit the data to CallingFM
    Now in CallingFM we already have the sy-uname = user-B.
    CallingFM: address-> http://systemS1.sap.com/CallingFM/page1.htm
    OnInputProcessing Part:
    =================
    call function 'zcreate_user' destination 'S2'
    Why you need CallingFM BSP application? because you need to re-assign sy-uname in S1 from default user with user-B ID, and use it to connect to System S2, S3, etc.
    Please note: SM59 and User Id must be set before this.
    Because when you call RFC from other destination, SAP will refer to Logon setting in SM59 for that destination.
    Hope this will help you.

  • 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/

  • 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

  • SLD setup for UDF to RFC Call in XI

    Hello,
    I am trying to create a UDF that has an RFC Call to the XI backend and I have it working in my development system.  But for some reason I cannot create the Business Service > Communication Channel > GeneratedReceiverChannel_RFC in my Assurance system. 
    I'm guessing it has something to do with a missing connection in my SLD but right now I can't see what could be missing.  What do I need to create in the SLD to allow XI to appear as a business service?
    Thanks,
    Matt

    Hi
      you dont need to do anything in SLD
    follow this link
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231
    infact there is another way (from what is explained in this doc), even without importing the RFC in IR/ ESR
    more info
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35
    Regards
    Vishnu

  • 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.

  • 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

  • How to Use synchronous RFC calls during test run for remote accesses

    there is a Setting for the usage of RFC accesses from a tested system
    using eCATT.
    'X' - Use asynchronous RFC calls during test run for remote accesses
    ' ' - Use synchronous RFC calls during test run for remote accesses
    I developed an eCATT as following :
      SAPGUI ( SAPGUI_1 , Target_system_1 ).
      SAPGUI ( SAPGUI_2 , Target_system_2 ).
    My question is how to run the eCATT in a synchronous RFC calls
    PS: I do not want to change the Target_system to the same one in the
    above script of ecatt.Because I need to run it in 2 different Target
    systems sometime.
    for example, I give a Target_system_3 when run this eCATT
    I want the SAPGUI_1 and SAPGUI_2 run the Target_system_3 but not the
    Target_system_1 or Target_system_2 .
    Could you please tell me how to make it without the changes in script?
    Edited by: Weitong Liu on Mar 24, 2011 9:44 AM

    Hi Liu,
    Weitong Liu wrote:
    > ' ' - Use synchronous RFC calls during test run for remote accesses
    This is the standard option value. Asynchronous are not the standard way and used only for very special purposes.
    Weitong Liu wrote:
    > I developed an eCATT as following :
    >   SAPGUI ( SAPGUI_1 , Target_system_1 ).
    >   SAPGUI ( SAPGUI_2 , Target_system_2 ).
    > My question is how to run the eCATT in a synchronous RFC calls
    The commands will be executed in sequence. So each call will be synchronously replayed against TS1 and TS2.
    What is you issue with this standard procedure?
    Kind regards,
    Christoph

Maybe you are looking for