Konfiguration IGS for RFC

Hello,
we installed the BI System diffrent to the portal. Now I've got the the problem that in the SM59 the IGS connection cannot established. How could I connect from SM59 to the IGS ? Is there any Description ?
Thanks
Frank

Hi Frank:
IGS deployment is now included as part of SAP NetWeaver application server installation.  You may as well consider the IGS part of the kernel on the app server.  The technique with SM59 and RFC is generally not utilized anymore.  The location of the portal which supports BI should not be impacted by the local (app-server based) IGS installation.
Best Regards - Ron Silberstein, SAP NetWeaver RIG (Global Expert)

Similar Messages

  • How to install IGS for the ABAP trial version SP11

    Hi,
    Please can anyone provide me with the steps to install IGS for the ABAP trial version SP11.
    Which version of IGS to download?
    What are extracting the SAR files what steps should be followed?
    Please advice,
    Thanks,
    sam

    Hi Rich and Sam,
    here is some kind of how to guide which hopefully contains all steps you need do perform.
    Best regards
    Matthias
    The IGS consists of a directory structure under DIR_INSTANCE/igs (containing folders and configuration files) and executables and libraires under DIR_EXECUTABLE. These excutables and libraries are available on the Service Marketplace in archive igsexe.sar. This file has to be extracted to DIR_EXECUTABLE.
    On the Service Marketplace you also find the file igshelper.sar which contains the above mentioned folder structure that must be extracted to DIR_INSTANCE. Normally this comes with a Web AS installation.
    Afterwards please go to DIR_INSTANCE/igs/conf and rename the files gfwchart.tpl, xmlchart.tpl and bwgis.tpl to gfwchart, xmlchart and bwgis, see notes 531668, 596825 and 1011372.
    To include the IGS to the start of the system you have to add the following to the start profile:
    Start internet graphics server
    IG = $(DIREXECUTABLE)\igswd$(FT_EXE)
    Start_Program_03 = local $(_IG) -mode=profile pf=$(_PF)
    Normally parameter _PF is defined as absolute path to the instance profile. If not use the absolute path instead.
    To enable HTTP administration you have to add the instance profile parameter:
    igs/listener/http= 4$(SAPSYSTEM)80,administration
    HTTP administration access was disabled by default with patch 4, see note 959358.
    If your system is a Java only system you must deactivate the RFC listener with the instance profile entry:
    igs/listener/rfc=disable
    For using the IGS with Web Dynpro Java you must define the IgsUrl according to note  704604. After a system restart the IGS should be up and running.
    You can test if the IGS is up and running with the link http://localhost:4$(SAPSYSTEM)80 or in an ABAP system via report GRAPHICS_IGS_ADMIN.

  • PI 7.11 - Alert creation for RFC Exceptions does not work

    Hi folks!
    In our PI 7.11 SP04 system we have created an Alert Category as well as an Alert Rule to be informed about errorneous messages in the Integration Engine (ABAP).
    The scenario is synchronous SOAP Axis to sRFC, where the RFC answers with an exception that is transferred to a SOAP Fault response message.
    Now we see messages with Application Errors in the Integration Engine, but no alert is created. Having a look at the alert creation log using report SXMSALERT_LOGREADER shows us that the system even does not try to create an alert for these messages.  Alerts are only created for errors in the Adapter Engine.
    Question:
    Why does the system not create alerts in this case and how can we achieve this?
    Thanx for any hint!
    Kind Regards,
    Volker

    Hi!
    Additional information for all:
    When forcing an error like "receiver not found" both kinds of alerts are created: AE Alert and IE Alert. Thus in general the alert configuration and the alert rule for IE errors are correct and working - only not for RFC exceptions ....
    Regards,
    Volker

  • IGS for BW 3.5- Chart showing as column only

    IGS for BW 3.5
    Hi All,
    We've been having problems with our WAD chart, it is showing up only as column chart even though we change the chart type to e.g line chart, bar chart..etc.
    I found note 653249 but it everything seems okay in our system. IGS test in RSRT is working. Checked as well the settings by running BW_IGS_ADMIN and everything seems okay.
    We upgraded our front-end and now using BW 3.5 Patch 2 ( this came with SAP GUI 7.10), but still not working.
    I am not a Basis person, but i need to know what caused this problem and how to fix it. We are using BW 3.5 and IGS version is 6403.0.8.2.
    Seems like we are using the IGS standalone installation since the configuration file path is in D:\Program Files\SAP\Internet Graphics Server\conf\igs.xml.
    I read somewhere that IGS standalone is not for BW 3.5? Is this right? Any ideas about this?
    Thanks!
    Jti

    Hi Kai,
    Thanks a lot for your quick reply.
    However, i would like to clarify on something. in note 653249, it says there that "The IGS must not contain a gfwchart.dll file." In our setting, the chart is using the mischart.dll ( see below).
    3291 CHART 6403.0.8.5 SAPMIS
    3292 CHART 6403.0.8.5 SAPMIS
    So i was thinking our setting is alright. So this should be gfwchart.dll? Please confirm. If so, do you know of any note/docs for this setting? I will need it so i can endorse it to Basis.
    We use graph reporting in Crystal for most of our reports, so we never had issue about this charts in WAD until now. Do we still need to run the chart migration although we didnt have any web templates with charts before?
    Your input is appreciated.
    Regards,
    Jti

  • RFC destination for RFC to File scenario

    Hi,
    I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
    Step 1:
    For this a Registered server program is created in Jco RFc Destinations with,
    Program Id : pgm1
    Gateway host : PI's host
    Gateway service : PI's service
    application server host: ECC's host
    system numer     : ECC's number
    client  : ECC's client
    logon user : ECC user
    password : pwd
    Step 2:
    In SM59, TCP/IP connection the following parameters are given:
    Program ID : pgm1
    Gateway host : PI's host       -
    > is this correct
    Gateway service : PI's service      -
    > is this correct
    Step 3:
    So i am calling the RFC in ABAP program (R/3 system) like:
    CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
    IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
    Step 4:
    In PI side,
    for RFC sender I am passing :
    Application server : PI server
    Application server service: PI host
    program ID: pgm1 which was created in the previos step
    For RFC Metadata Repository Parameter, i am passing all the values related to R/3
    Please let me know whether the steps and values i given is correct.
    B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
    so i am confused as which is the correct method. pls clarify

    Ok I will try to explain....
    Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
    While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
    So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
    CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
      IN BACKGROUND TASK
      DESTINATION 'R3_TO_XI'
      TABLES
        comp_detail = company_detail.
    COMMIT WORK.
    Regards,
    Sarvesh

  • Getting metadata for RFCs using RFC SDK (with position of parameters)

    Hi!
    I'm currently using the RFC SDK Function "RfcGetFunctionInfoAsTable" to retrieve metadata for RFCs from SAP. What i see is that the "Position" field in the RFC_FIELDS_U structure contains arbitrary values, and so I am not able to determine what is the actual ordering of the parameters.
    What can I do to determine the exact ordering of the parameters of an RFC? (ordering as in - I want to obtain the parameters in the same order as they appear in SAP GUI).
    Thanks,
    Mustansir

    Hi,
    I think you can use the code similar to the one below...
    some of the things not covered in this are
    1. all types for which   CALL FUNCTION 'RFC_GET_NAMETAB' is not returning result, you can call CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION' directly. I have not covered that in this code. Hope this is helps in resolving your issue.
    Also, the code is not optimized. So there is some scope for optimization of this code.
    REPORT  ZTEST_GET_SREUCTURE.
    DATA : PARAMS     type table of     RFC_FUNINT,
          ls_params like line of params.
    data: NAMETAB     type table of     X031L,
          ls_NAMETAB like line of NAMETAB.
    data: FIELDS  type table of RFC_FIELDS,
          ls_fields like line of fields.
    CALL FUNCTION 'RFC_GET_FUNCTION_INTERFACE'
      EXPORTING
        FUNCNAME                      = 'fm_test_fm'
      TABLES
        PARAMS                        = PARAMS
    IF SY-SUBRC <> 0.
    ENDIF.
    loop at params into ls_params.
      CALL FUNCTION 'RFC_GET_NAMETAB'
        EXPORTING
          TABNAME                     = LS_PARAMS-TABNAME
        TABLES
          NAMETAB                     = NAMETAB
      IF SY-SUBRC <> 0.
      ENDIF.
      loop at NAMETAB into ls_NAMETAB.
        CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION'
      EXPORTING
        TABNAME                     = LS_NAMETAB-ROLLNAME
      TABLES
        FIELDS                      = FIELDS
        loop at fields into ls_fields.
          write: ls_fields-FIELDNAME.
        endloop.
      endloop.
      endloop.

  • How to install and configure configure IGS for J2EE server 700

    Hi,
    Please help me in installing and configuring IGS for J2EE server700 as i need it to run Business Graphics for my Web DynPro application. Earlier i had installed J2EE server 640 and i didnt have to do any separate installation for IGS. I just had to configure the IGS URL from Visual Admin. But i can't find any igswd.exe running on my J2EE700 engine.
    Please let me know the procedure for this.
    Thanks an Regards,
    Smriti.

    Hi,
    Check the below link,
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/17/86c039c7811f11e10000000a114084/frameset.htm">About IGS Configuration and Adminisatration</a>
    Regards,
    Suresh.T

  • XML pay load for RFC call in java mapping

    Hi,
    I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
    Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
    Say i have 2 import parameters(input1,input2) and one output(output1)......
    Thanks in advance,
    H.L.Babu

    >
    hlbabu123 wrote:
    > Hi,
    > I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
    >
    > Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
    >
    > Say i have 2 import parameters(input1,input2) and one output(output1)......
    >
    > Thanks in advance,
    > H.L.Babu
    have a look at this document - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439&overridelayout=true
    in case u still have issues do get back

  • Runtime Error: "Time out" for RFC.

    Hi,
      During RFC, I am getting a runtime error stating "Timeout error".  Even while the job is run in background I am getting this error. Seems like the time for RFC task is set to 600 secs.
    How to resolve this and is there any way we can see time limit set for different tasks?
    thanks,
    Arun

    Hi,
       More info:  I am using multithreading or mass processing technique, so the logic has to be written in FM which has RFC enabled. So while the task is in process in background it exceeds the time limit set for RFC i.e 600secs.
    Sample code:
        CALL FUNCTION 'ZZ_ABC'
          STARTING NEW TASK gv_task
          DESTINATION IN GROUP gv_grp
          PERFORMING rcvb_endprocess ON END OF TASK
          EXPORTING
            e_batch_date = gv_batch_date
    FORM rcvb_endprocess                                        "#EC CALLED
                  USING gv_task  TYPE any.                      "#EC NEEDED
      RECEIVE RESULTS FROM FUNCTION 'ZZ_ABC'
       TABLES
            t_receivables = it_receivables.
      gv_rcvd = gv_rcvd + 1.
    ENDFORM.                    " RCVB_ENDPROCESS

  • How to understand the STAD relevant for RFC

    Hello performance experts.
    I have question about how to understand the STAD relevant for RFC.
    I want to know how to calculate the response time of action of "Push save buttion"
    which call function module by RFC.
    In our system, the screen is created using web dynpro and after push the button,
    function module for application will be called.
    When I push Save button, 2 STAD line is created.
    One is for function code " SAVE" and the other is for "RFC".
    Line for "SAVE" include RFC as client, and RFC line has RFC info as server (also client)
    I wonder how I should calculate the response time of action"Save" button in following case.
    Should I add the 2 response time?
    1) 5,867 ms +   5,797 m  is collect?
    2) 5,867 ms  include RFC time, so no need to sum the value and 5,867 ms is collect??
    3)  590 ms  +   5,797 ms is collect?
    4) Or other calculation is correct ?                                                   
    1) STAD for function code:    
    CPU time                     578 ms    
    RFC+CPIC time              5,280 ms                                                  
    Total time in workprocs      594 ms
    Response time            5,867 ms                                                                 
    Processing time              590 ms    
    Load time                      1 ms               
    Wait            5,273  ms
    Roll (in+wait) time        5,274 ms
    as Client
    Number    Connections                              1
               Destinations                             1
               Users                                    1
               Calls                                    2
    Time      Calling                              5,280   ms
               Remote execution                    10,527   ms
               Idle                                11,110   ms
    Data      Sent                               135,836   Bytes
               Received                               620   Bytes
    2) STAD for RFC
    CPU time                   1,406 ms
    RFC+CPIC time                  9 ms
    Total time in workprocs    5,080 ms
    Response time            5,797 ms
    Processing time            2,132 ms
    Load time                     50 ms
    Roll (in+wait) time          718 ms
    Database request time      2,882 ms
    Enqueue time                  16 ms
    Roll time
    Wait              717  ms
    as Client
    Number    Connections                              1
                      Destinations                             1
                         Users                                    1
                           Calls                                    4
    Time      Calling                                  9   ms
              Remote execution                         1   ms
              Idle                                     0   ms
    Data      Sent                                   686   Bytes
                 Received                             1,360   Bytes
    as Server
    Number    Connections                              1
              Destinations                             1
              Users                                    1
              Calls                                    2
    Time      Calling                              5,272   ms
              Remote execution                     5,269   ms
              Idle                                        11,118   ms
    Data      Sent                                   620   Bytes
              Received                           135,760   Bytes
    Thanks for your cooperation in advance.
    Keiichiro

    Hi Keiichiro,
    I wonder how I should calculate the response time of action"Save" button in following case.
    Should I add the 2 response time?
    1) 5,867 ms +   5,797 m  is collect?
    2) 5,867 ms  include RFC time, so no need to sum the value and 5,867 ms is collect??
    3)  590 ms  +   5,797 ms is collect?
    4) Or other calculation is correct ?
    It depends of what you mean with response time of action "Save" button.
    If you mean ALL time, the value is 5.867 because the local time from save was 594ms, the "external" RFC time was 5280ms.
    If you want separete analysis, the 594ms is your option since the 5280ms is in other part...
    Also, analysing the other part there's another other part which represents a good part of processing time:
    Database request time      2,882 ms
    Hope this help youl.
    Regards, Fernando Da Ró

  • Authorization Required for RFC user  in R/3-APO system.

    Could you please help regarding one authorization issue. I want to know the authorization required for one RFC user. Now this RFC user used for RFC connection of SAP R/3 - SAP APO system. user type is given dialog type and SAP_ALL profile has been given to this user  id. Now I have to remove SAP_ALL from this user id in R/3 and APO system and  provide the required the authorization in R/3 and APO system.
    Regard
    Auroshikha

    The RFC authorisation depends completely on what the user is doing (ALEREMOTE?).  We can't tell you what RFC auths your connection requires. 
    There is a guide to doing this here: https://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections

  • ** Sender Agreement is required for RFC but not IDoc, XI, & HTTP.. Why ?

    Hi Friends,
    All we know that since IDoc, XI adapters running on Integration Engine (SAP WAS 6.40), Sender Agreement is need not required.
    Since RFC is proprietary document for SAP like IDoc, why we are creating Sender Agreement for RFC adpater ? (We know that RFC adpater is running on Adapter Engine, so that ...). Some of our guys asking me this question.
    Why is this difference (IDoc adapter running on Integration Engine & RFC adapter is running on Adapter Engine) ? Anyboday can clarify the exact reason on this ...
    Kind regards,
    Jegathees P.

    Hi,
      RFC Adapter:
        RFC adapter can abe to  manage metadata while using the Jco call.This turns the RFC data to RFC xml message.
    IDOC Adapter:
       But Loading the metadata for IDOC we should create a port and rfc destination.IDOC adapter and metadata container placed in integration server before and after the pipeline step.metadata container converts the IDOC to IDOCxml.IDOC adapter converts the IDOC xml to native xml format.Using idx2 we uploaded the IDOC metadata with the help of RFC destination and port.
    Regards,
    Prakasu.M

  • Any SAP Note for RFC Error between BI and ECC 5.0

    Hi..
    the RFC Destination between BI and ECC 5.0 is giving errors.
    Plz let me know if there is any Support pack  or any solution to fix this error.
    thanks..

    Hi,
    pls find the RFC connection details
    1 Prerequisites
    1.1 User Roles
    Use
    With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
    Technical name Description File name for upload
    B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
    B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
    C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
    B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
    Procedure
    Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
    2 Local Settings
    This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
    2.1 SAP R/3
    2.1.1 Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu Define Client Administration (SAP R/3)
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    Then carry out the following steps:
    1. Choose Display  Change.
    2. Confirm the warning message Caution: The table is cross client.
    3. Select your SAP R/3 client and choose Details.
    4. In the Change View Clients: Details screen, activate the following settings:
    u2022 Automatic recording of changes
    u2022 Changes to Repository and cross-client Customizing allowed
    u2022 eCATT and CATT allowed.
    5. Save.
    6. Go back to the SAP Easy Access menu.
    2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1. Define the systems as logical systems.
    2. Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code SPRO
    SAP R/3
    IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
    2. Choose New entries.
    3. In the column Log System, enter a name for the logical system that you want to create.
    4. In the column Name, enter a description of the logical system.
    Log. System Name
    where XXX is the system name
    and NNN is the client.
    5. Save your entries.
    A transport request for Workbench appears.
    6. Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7. Select an existing request or create a new request, if necessary.
    2.1.3 Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Assign Logical System to Client
    Transaction Code SCC4
    SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Choose Display ® Change.
    3. Confirm the warning message The table is cross client.
    4. Select your R/3 client and choose Details.
    5. Enter the name of the logical system of your SAP R/3 client.
    6. Save and confirm the warning message Be careful when changing the logical system.
    7. Choose Back twice.
    2.1.4 Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1. Access the transaction using:
    SAP R/3 Role Menu Creating an RFC User (SAP R/3)
    Transaction Code SU01
    SAP R/3 Menu Tools  Administration  User Maintenance  Users
    2. In the User field, enter RFCUSER.
    3. Choose Create.
    4. On the Maintain User screen, enter the following data on the Tab entry screens:
    Address
    Last Name
    Function
    Logon data
    User type System
    Password LOGIN
    Profile
    Profiles SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language EN
    5. Save your entries.
    2.3 SAP BW
    2.3.1 Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1. To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu Local Settings ® Define Client Administration
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    2. Switch to change mode.
    3. Select your client.
    4. Choose details.
    5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6. In field Client Role enter Customizing
    7. Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2 Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
    Transaction Code SPRO
    IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
    1. A dialog box informs you that the table is cross-client. Choose Continue.
    2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
    3. On the New Entries: Overview of Added Entries screen enter the following data:
    Field name Description R/O/C User action and values Note
    Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
    Name Textual Description of the Logical System Enter a clear description for the logical BW system
    4. Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3 Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu Assigning Logical System to Client (SAP BW)
    Transaction Code SCC4
    SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
    1. In the view Display View "Clients": Overview, choose Display.  Change
    2. Confirm the message.
    3. Select your BW client.
    4. Choose Details.
    5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6. Save the entries and go back.
    2.3.4 Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Modeling  Administrator Workbench: Modeling
    Transaction Code RSA1
    1. In the Replicate Metadata dialog box, choose Only Activate.
    2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5 Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu Creating RFC User
    Transaction Code SU01
    SAP BW Menu Tools  Administration  User Maintenance  Users
    Then carry out the following steps:
    1. On the User Maintenance: Initial Screen screen:
    a. Enter the following data:
    Field Entry
    User RFCUSER
    b. Choose Create.
    2. On the Maintain User screen:
    a. Choose the Address tab.
    b. Enter the following data:
    Field Entry
    Last Name RFCUSER
    Function Default-User for RFC connection
    c. Choose the Logon data tab.
    d. Enter the following data:
    Field Entry
    Password LOGIN
    User type System
    e. Choose the Profiles tab.
    f. Enter the following data:
    Field Entry
    Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g. Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6 Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu Define RFC-USER as default (SAP BW)
    Transaction Code RSA1
    SAP BW Menu Modeling  Administrator Workbench: Modeling
    1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
    2. In the Global Settings/Customizing dialog box choose Glob. Settings.
    3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
    a. Choose Display  Change.
    b. Enter RFCUSER in the BW User ALE field.
    c. Choose Save.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • Which user type to user for RFC receiver channel

    Hi Forum,
    I m developing XI scenarios which include RFC receiver chhanel (in IB: Integration Directory), to call a function moule in a R/3,
    which kind of user should i use for this purpose, i mean to say,
    which user type:
                    SYSTEM
                    Dialog
                    Communication
                    System
                    Reference
    and what should be the roles of that user,
    which type of the user doesnt gets locked, on wrong attempts

    Hi,
    Generally S_RFC and S_SERVICE authorizations  are nedded while calling RFC module from R3. Also check for role S_RFC_ADM
    The backend should have the authorization to execute the RFC on the backend.
    You can test the module in R3 and create a role using PFCG assign the tcode - SU53 (authorization check) and also assign the S_RFC and S_SERVICE to role.
    Refer
    RFC Logon user authorizations
    Question on service userid - for RFC call
    End User Authorizations and Roles
    Calling R3 RFC via http
    For RFC different authorization object is requried. You can ask your basis team to add the relevant authorization object in a new role and then add the new role to any existing service user or better create a new system user and add the role.
    Thanks
    swarup

  • In the bw instlationat login details for RFC CONECTION SOME ERROR?

    HI ALL
    in the bw instlationat login details for RFC CONECTION SOME ERROR? IS OCCURED LIKE THAT ,USERNAME : DDIC, PASSWORD_________________-:
    WHICH PASSWORD I WILL GIVE

    use the default password 19920706
    With Regards
    Bhaskar
    Edited by: bhaskar1818 bhanu on May 28, 2008 12:35 PM

Maybe you are looking for