Mapping Logical Systems with ECC 5.0/6.0 for WD

Hi there,
did anyone have a good documentation to implement this solution, to connect WebDynpro, especially BP for ECC5.0 and 6.0, to two different Backendsystems?
I´m searching the way, to configure the logical target system name in the WD Content Admin.
SAPHelp-Link is not informative....
http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/content.htm
Best regards
Christian

Hi Christian,
We are also looking into this functionality but have not gotten it to work yet.
Our issue is that our DEV/QA users need to test with different backend clients.
So we want to be able to specify a different JCO as part of the WebDynpro URL that we issue.
For testing, we have created two new JCOs (one data and one metadata).  The names of the new JCOs are the same as the old but with 3 unique characters appended to the name (e.g. "ABC").   Those new JCOs point to a  different client.
Then when we call the URL for the WebDynpro, we append
?sap-wd-arfc-useSys=SAP_R3_HumanResources:ABC&sap_wd_afrc-useSys=SAP_R3_HumanResources_Metadata:ABC
to the end of the URL.
However, after authenticating, this URL fails with NullPointerException
Any idea about what the problem might be?
TIA ... Bart

Similar Messages

  • Mapped logical system

    Hi Experts,
    I have a confusion to use the type of RFC connection like when
    to use ABAP connection and TCP/IP connections etc...
    I have defined one logical system and define one RFC destination and when  i am trying connect this two it is asking me to give Standard RFC destination for BAPI and dialog calls to connect to the logical system. i would like to know what is this ? why we need to give this?.
    and we assign this logical system to the Mapped logical system. i d like to know what is this mapped logical system and when we need to assign the logical system to this mapped system.
    Can anybody please clarify all my doubts.
    Thanks, Izaz.

    Hi Izaz,
    ABAP connections are given between 2 SAP systems and TCP/IP is used between ABAP and JAVA.
    Regards,
    Suman

  • Logical system with business service

    hi,
    can we have a logical system with business service just like we have with business system?? If yes,how can we create logical system for business service??
    Ratna.

    Hi,
    If you intend to use it with IDoc adapter it might be also necessary to set up corresponding Logical System (tcode: BD54) in adequate backed system.
    Refer conversion routine (logical system vs. service) in this presentation [Using the IDoc-Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd] - page no 6.
    Regards,
    Jakub

  • How to map secondry elements with main if have same ids for both?

    I need to map secondry elements with its matching primary elements if they both have same id.
    How can this be achieved in xslt.
    If ids are not matching then not a single element of secondry sholud be shown.
    If ids matching, then other fields of secondry elements, should be mapped to similar fields of primary elements.
    Eg: Its like some program running and in between some add on programs started (may be trailor or advertisement).
    the add on program is not always shown (optional), and whenever shown it has its own data information etc etc.
    Please provide me some input, how to map and proceed.
    Not sure what this code is really doing.
    <xsl:template match="SECONDARY_EVENT_LIST">
              <xsl:variable name="secondaryElements" select="ancestor::SCHEDULE/SECONDARY_ELEMENT_LIST"/>
              <xsl:for-each select="SCHEDULE_ELEMENT_ID">
                   <xsl:variable name="id" select="."/>
                   <xsl:apply-templates select="$secondaryElements/SCHEDULE_ELEMENT[(@ID=$id)]"/>
              </xsl:for-each>
         </xsl:template>
    Is this having any relation with what my requirement is all about?

    Hi,
    You can use XPATH command to get the exact tag.
    You can access each tag with it location like “/Report_Name/Group_Tag/Element_ID”.
    I think this will remove the ambiguity of Tags with same ID.

  • Mapping Logical Systems -

    Hi,
    i want to connect to 2 backends to test ESS BP functionality.
    The background is that i want to test functions for ERP 6.0 EhP3 and need to keep the old Webdynpro functionality.
    The old java webdynpro (ESS) is running on the portal side, the new ABAP webdynpro is running on the ERP system.
    I configured new JCODestinations as described in http://help.sap.com/saphelp_nw70/helpdata/EN/af/84a34098022a54e10000000a1550b0/frameset.htm
    I could connect now to iviews like life events with the correct parameters.
    The issue is now that i also need to switch the XSS Overview (XssMenu) pages.
    So far i am always connected to the old system. I tried all properties of that iview and also created a new one.
    Is it possible to connect to the old system?
    Thanks,
    Kai

    Hi Christian,
    We are also looking into this functionality but have not gotten it to work yet.
    Our issue is that our DEV/QA users need to test with different backend clients.
    So we want to be able to specify a different JCO as part of the WebDynpro URL that we issue.
    For testing, we have created two new JCOs (one data and one metadata).  The names of the new JCOs are the same as the old but with 3 unique characters appended to the name (e.g. "ABC").   Those new JCOs point to a  different client.
    Then when we call the URL for the WebDynpro, we append
    ?sap-wd-arfc-useSys=SAP_R3_HumanResources:ABC&sap_wd_afrc-useSys=SAP_R3_HumanResources_Metadata:ABC
    to the end of the URL.
    However, after authenticating, this URL fails with NullPointerException
    Any idea about what the problem might be?
    TIA ... Bart

  • Mapping Logical Systems sap-wd-arfc-useSys

    Hi all,
    I saw many many threads about this issue because sometimes seems to work but it doesn´t works for me.
    So far I did the following:
    Configure 4 JCO´s:
    SAP_R3_HumanResources
    SAP_R3_HumanResources_Metadata
    These two points to my Dev environment
    SAP_R3_HumanResourcesQAS
    SAP_R3_HumanResources_MetadataQAS
    These two points to my Qas environment
    For all this JCO´s I got a successfull ping and test.
    Then, I put the sap-wd-arfc-useSys parameters like this:
    http://server:port/webdynpro/dispatcher/sap.com/essarpdata/ZPer_Personal_AR?sap-wd-arfc-useSys=SAP_R3_HumanResourcesQAS:QAS&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetadataQAS:QAS but this does not do anything.
    In this link http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/frameset.htm the parameter should be  the SUFFIX_OF_MAPPED_SYSTEM is the system Id? the client? what should be?
    Do you have any ideas of what could I be missing?
    Regards,
    Orlando Covault

    Please use it as follows:
    sap-wd-arfc-useSys=SAP_R3_HumanResources:QAS&sap-wd-arfc-useSys=SAP_R3_HumanResources_Metadata:QAS
    It should be <Default System>:<Suffix of Mapped System>
    Your default system is - SAP_R3_HumanResources
    Mapped system is - SAP_R3_HumanResourcesQAS
    So suffix of the mapped system is - QAS
    Hope that explains it.
    Check this doc (page 17) for more info:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/526bd490-0201-0010-038e-d3ff7eb1d16e?quicklink=index&overridelayout=true
    - Shanti
    Edited by: Shanti Mupkala on Mar 16, 2011 5:26 PM

  • Connecting EP 6.0 system with ECC 5.0

    Hi,
       We are using EP 6.0 system. We want to connect ECC 5.0 System, which is located in our client place.
       Can anyone please describe the step by step process to connect ECC 5.0?
    Thanks in Advance,
    Abdul Kareem.S

    Hi abdul,
    In order to connect to Backend R/3 system in your case it is ECC 5.0 from the portal - there is a feature in portal called as SSO(Single Sign on). Using that you would be able to access R/3 backend.
    There are two methods in SSO which differs based on the userID and PWD of portal and Backend.
    Check my answer in the following thread to have a better idea on SSO and configuration steps to be done inorder to connect to backend:
    <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=107666&messageID=1196791">Configuration steps</a>
    If userID and PWD method is used then coressponding JCo connections are also to be established inorder to fetch data from the Backend.
    Hope it helps.
    Regards,
    Vivekanandan

  • Cost center integration with HR - logical system for CRT inconsistent

    Hi there,
    we are distributing Cost centers from our SAP ERP system to another SAP HR system via ALE [COSMAS01 basic type].
    The cost center created in target system contains information about source system logical system name - table CSKS, field LOGSYSTEM.
    This is causing problems in Travel Managment in SAP HR system, where we get the error: Logical system for CTR inconsistent.
    Cost centers created/changed in HR system does not contain any value in CSKS-LOGSYSTEM field and work fine.
    Any ideas how to solve this issue?
    For now to fix the issue, user needs to do a phony change in SAP HR system to get rid of original LOGSYSTEM value.
    I am thinking about removing field E1CSKSM-LOGSYSTEM from COSMAS IDoc but I gues there must be simpler soloution.
    Thanks for your advices,
    Igor

    Igor :
    I think this has something to do with matching logical system with controlling area in TKA01. Another option for cc's logical system to have no values when outbound ALE is to config V_TKA01_ALE (so it will be transported to the system that has cc ALE to other systems) to have field 'ALE Distribution Method' blank (No distribution to other system).
    This way, when SAP is creating outbound idoc for COSMAS, field CSKS-logicalsystem will not be populated (logic is in SAP 'MASTERIDOC_CREATE_COSMAS' , around line 86).
    Rgds.

  • External Party to Logical System Integration

    My scenario is as follows
    External Party --> XI --> ECC. XML coming into XI and data posted in ECC using IDoc.
    We have several different external parties that we need to integrate with but they all will send us the data in the same XML format and they do not have any different mapping requirements. So we can use the same design objects for all of them. However, they need to be setup as separate logical systems in ECC as we have different teams that support error handling for each of the external parties.
    I dont have any need to use BPM as my mapping is fairly straightforward. I have setup a party in XI for each external party.
    My problem is how can I have XI pass IDoc to different logical systems based on the external party?
    I have tried playing with the adapter specific attributes on the sender service and giving logical system there but to no avail. How can I accomplish this without creating the parties as business systems in SLD as there are quite a few of them? Or is it the only way?
    Any help will be greatly appreciated and rewarded.
    Regards
    Haseeb

    Hi,
    Is there some way that the source payload allows you to distinguish which system it comes from and what the logical system name has to be ?
    If yes, in the Idoc control record, populate the values of  SNDPRN and SNDPRT with the Sender PartnerName and Sender Partner Type ( Sender Partner Name will be the logical system name ) on the basis of this source condition and in the Idoc adapter select option "Take Sender from payload"
    Regards
    Bhavesh

  • Logical system and partner profile configuration

    Hi,
    I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
    First question is do I have to mention a logical system name for the SQL server Business system too ?
    Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
    Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
    Thanks in advance.
    Cheers,
    S

    Hi Sam,
    > First question is do I have to mention a logical system name for the SQL server Business system too ?
    Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers  you can see logical system name of SQL server business sytem which you defined in SLD.
    > Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
    Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
    > Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
    In WE20 You have to maintain partner profiles for SQL server Logical system
    For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
    In ECC you have to create logical system as SQLDEVLS and
    Partner profiles for SQLDEVLS in WE20.
    Please let me know if you have any issues.
    Cheers,
    JAG

  • Use of Logical System

    Hi GRC Experts:
    I am currently defining my RAR landscape strategy. In the past, I have used logical systems for the same "type" of system. For example, we had 3 ECC environments so I created a logical system for the 3 ECC systems.
    Now we have 1 ECC, 1 APO and 1 SRM system. Are there any benefits of setting up a logical system within this landscape? I would imagine there are some benefits with creating a logical system and assigning the BASIS risks to that system because the risks exist across the different environments. But are there any others?
    Thank you,
    Grace Rae

    Hi Grace, Logical Systems would be an optimal design if you need to add more systems in the future to the GRC landscape to perform Risk analysis.
    Logical System 1: ECC Logical System
    All the ECC Physical Systems (PR1, PR2, etcu2026)
    Function Authorizations to be uploaded are r3_function_actions and r3_function_permissions files which excludes the Basis Functions
    Logical System 2: SRM Logical System
    All the SRM physical Systems (PS1, PS2, etc...)
    Function Authorizations to be uploaded are srm_function_actions and srm_function_permissions
    Logical System 3: APO Logical System
    All the APO physical Systems (PA1, PA2, etc...)
    Function Authorizations to be uploaded are apo_function_actions and apo_function_permissions
    Logical System 4: ALL Systems
    All the physical systems (PR1, PR2, PS1, PS2, PA1, PA2....)
    Function Authorizations to be uploaded are just the Basis Function Actions and permissions
    Bugesh

  • Clarification Regarding Logical System Names

    HI all,
    I read the blogs regarding Logical System Name, even I am having the some problems in my system.
    For PI system client is 100.
          R/3 System Client is 100 is created.
    IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
    I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
    In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
    When I checking in the R/3 system that logical system Name ('PICLNT100')  is not there  and for r/3 client 100 having the different logical system name.
    IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
    It is different from the SLD logical System Name.
    How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
    when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
    How I have to maintain the logical system names in this case?
    please help me in this.
    Regards,
    Sree

    hi.
    each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
    http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
    IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
    to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
    once you configure it all data from r3 system is exported to SLD.
    if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
    each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
    hope its helps
    Rodrigo
    PD: rewards points if useful

  • Dynamic Determination of Logical System- Transaction Launcher

    Hi Friends,
    Need your suggestions and inputs on how to dynamically determine the logical system for the transaction launcher.
    Our system landscape is like this.
    We have one CRM connected to mulitple back end ECC Boxes. Currently, we have created separate TL's fo VA01 ( One each for each back end application ) and provided the same in logical link and controlled the same via business role.
    For eg: BROLE1 - LLINK1  having (TL VA01) pointing to ECC System1
    BROLE2 - LLINK2  having (TL VA01) pointing to ECC System2
    BROLE3 - LLINK3  having (TL VA01) pointing to ECC System3
    The above procedure is working fine. But what we are trying to do is, when the end user clicks on the TL link in WEB UI, Based on the assigned business role, it should dynamically determine the back end system and open the VA01 Screen in that system.
    I have activated indicator multiple systems in the customizing of mapped logical systems.
    In debugging mode, i have tried changing the LOGSYS value @ run time in the handler class.
    Any pointers on this would be of great help.
    Thanks,
    Madhu

    Hi,
    Try this..
    To maintain RFC destination in each business role, there is one functional profile  "ERP_SALES_ORDER" where in you can maintain respective rfc destination.
    Create z-functional profile's for "ERP_SALES_ORDER" and maintain corresponding rfc destination, later assign these erp sales order function profiles in respective business roles trxn (CRMC_UI_PROFILE).
    you can use the below statement to fetch rfc destination whcih assigned to business role via functional profile.
      If gv_rfc is INITIAL.
        gv_rfc = CL_CRM_IC_ERP_SERVICE=>GS_ERPPROF-RFCDEST.
      ENDIF.
    Hope this helps.
    Cheers,
    Sumit Mittal

  • Logical System is not appearing in Informer tab to check SOD's

    Hi GRC Experts,
    I have an issue with logical system to run risk analysis.
    I created logical system by following the Config guide, added physical system and generated rules (RAR Configuration>>Logical Systems>>Generate Rule) for that logical system.
    I haven't generated rules for the physical system (RAR Config>>Rule Upload>>Generate Rules) since I dont want more rules to be displayed in the reports.
    However I do not see logical system as an option in Risk Analysis (informer Tab) and Config>>Schedule background job for BAtch Risk Analysis>> under system as well.
    It would be great if any one advice me on this.
    Regards,

    Thanks Chinmaya,
    Yes you are right, I confirmed with a friend (my ex-GRC colleague) of mine as well.
    can't execute sod checks on a logical system - logical systems are only intended to eliminate the need to add the same rule set over and over for the same types of systems
    Regards,
    Ramesh K

  • Logical system creation in BD54

    hey guys
    i have a very silly question,i m really confusing myself.
    well i m doing a IDOC to File scenario.
    on the R/3 side i have RFC dest(SM59) and Port(we21) in place,both pointing to the XI system.Port is SAPXD1(XD1 is system ID of the XI system).
    i m confused in BD54 and WE20.
    i go in BD54 to create a logical system with the name XD1CLNT100(XD1 is the system ID of the XI system and 100 is the client)
    then i go in WE20 and create a partner profile,with the same name as Logical system(XD1CLNT100),then in the outbound side i enter the IDOC i m gonna send and give the Port name as SAPXD1.
    lemme know if the above steps are right?
    now my stupid question is,when we create a logical system in BD54,is that the logical system for R/3 or for XI?
    is this the same logical system name which i have to use in SLD to create a business system for the sender service?
    i have gone through lots of blog and links and m really confused.
    please dont send any links.
    appreciate ur help
    thanx
    ahmad

    Ahmad,
    Get in touch with the Basis Team. They should be able to give you the Logical System name of your R3 system . Normally it always is , SID"CLNT"ClientNumber.
    You will only create on Business System and this will be the One for the R3 system using the R3's logcial system name.
    When the Idoc is sent from R3, it will search in the SLD with its logical system name to find what the correspionding Bsuiness System is. After it finds the Business System it will fill the SOAP header with details like Sender Service and Sender Interface and Sender NameSpace and with these values deterkine the receiver.
    As you are doing a file to Idoc, the receiver can be a thrid party business system or a business service.
    The Receiever System is also a WebASABAP business system in case you are doing an Idoc to Idoc and that is a different case altogether
    Regards
    Bhavesh

Maybe you are looking for