Entitlement Systems Logical System Name

Environment:
- BusinessObjects Edge Series BI 3.1 (standard packge)
- Business Objects XI Integration for SAP Solutions
- Windows Server 2003 x64
I am trying to configure a Logical System Name in the Entitlement Systems of the BusinessObjects Central Management Console.
Our BI 7.01 system uses a different naming convention for the logical system name (not the standard <SID>CLNT<client#>
(i.e. BWQCLNT300).  We use BWQ300.  How would I override the default configuration (put in a different logical system name)  in CMC - SAP Authentication?
Please advise.  Thank you in advance.
Francis

Ingo,
That is correct.  It generated the logical system name automatically for me. 
But our BW system have a logical system name of BWQ300 (not BWQCLNT300). 
How would I override this ?
Thank you very much for your reply.
Francis

Similar Messages

  • What is a R/3 system, logical system, and legacy system...???

    Hi,
    Please throw some light on...What is a R/3 system, logical system, and legacy system...???

    Hi,
    R/3 system is a normal SAP system that stores data.
    A legacy system is an existing computer system or application program which continues to be used because the user does not want to replace or redesign it.
    Logical System:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
    Technical System:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
    Regards,
    Subhasha

  • ALE settings in sapR3 system logical system

    Hi People
    IN IDoc to File scenario
    How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that,  we have to 1st create LS name (for R3 sys & PI sys),   after that we have to assign that name's how to assign that,    PLS can u provide me to with screen shots (if possible) r any links 
    Regards
    shekar

    Hi,
    IDOC
    http://msdn2.microsoft.com/en-us/library/ms942196.aspx
    Idoc configuration Required~
    in R/3
    1) RFC destination pointing to XI
    2) WE20 Partner Profile entries
    in XI
    1) RFC destination pointing to R/3
    Go thru this -
    configuration steps for receiving idoc in xi from r/3
    Go thru these for Idoc to XI scenarios-
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    These will be the Configurations needed in your R3,
    1. SM 59 - Create an RFC destination for your XI .
    2. We21 -- Create a port for XI
    3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
    Configuration on XI
    1. IDX2 - Import IDOC metadata.
    For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
    In XI :
    Step 1 : In SALE Tcode :
    a)Create Logical systems for R/3 and XI.
    EG : (QZACLNT100) and (X7ACLNT100).
    b) Assign the logical system of XI to Client.(X7ACLNT100)
    Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
    Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
    Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
    In R/3 :
    Step 1:
    In SALE Tcode :
    a) Create Logical systems for R/3 and XI for
    b) Assign the logical system of R/3 to Client.(QZACLNT100)
    Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
    Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
    a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
    b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
    c)In Menu Bar EDIT->Generate Partner Profile.
    Click on that and press Execute .
    This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
    d) Click EDIT->MODEL VIEW->Distribute.
    This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
    This configuration shall surely help u out as it worked out for me.
    Configurations required for IDocs in R/3
    In your XI system, you need to do the following.
    1. Create a RFC destination to your R/3 system
    2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
    3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
    4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
    5. Import the business system and you can use it in your configuration scenario.
    Please also refer below links for details.
    Go thru this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    SAP R3 ->Legacy system including master data using XI
    Regards,
    Phani

  • Source System(Logical system) issue

    Hi All,
    Recently we have done QA refresh & copied with production data.
    For 0vendor master data we are extracting data from ECC source system. When I was trying to execute the DTP it is pointing older source system. We tried to create new DTP but when I'm executing still it is showing older system.
    By using RSBKDTP_BDLS  program I forcefully tried to convert old source system to new source system but we are unable to solve this issue.
    Here I'm attaching the issue .Please help on this issue.
    Best Regards,
    Sammar.K

    Hi Ram,
    I have compared Production & QA system entry's in RSLOGSYSMAP Table.
    in prd system
    source       target
    qa6            prb01
    in qa system
    source       target
    qa6             qa6
    we found in qa it is pointing wrong target.
    Regards,
    Sammar.K

  • I need help in logical system name in business system

    i created two business system with same logical system name and now am getting error in ID when i try to activate business system"" Logical system LSSUN already exists in service | BS_RCVESUN"" So,i again changed a logical system name in SLD and tried to activate it again but changes is not reflected back in ID.again it show logiacal system alredy exists.
    pls giv me a steps to reflect changes back in ID.
    thanks & Regards
    Manikandan Shanmugam

    open BS in edit mode,
    choose from menu: Adepter Specific Identifiers
    Here you push button: Compare SLD data
    Save and activate

  • Logical System Name changing

    Dear Team,
    We had upgraded BI system from 3.0B to BI 7.0. At the time of upgrade dev
    copy(shadow system) logical system was not changed because most of the data is coming from ETL. Now we want to test the extraction from R/3 Dev.
    R/3 Dev is already connectwed to BW dev 3.0B, Now we need to test
    extraction from R/3 Dev to BW dev copy server( NW2004SR1 ).
    Here we are facing a problem with Logical system. While upgrading the
    same logical sys was copied to BW dev copy.
    What is the procedure to change the existing logical system name in BW
    dev copy and establish connectivity with R/3 dev?
    what is the impact if we run BDLS transaction.
    Thanks& Regards,
    Satish.K.Neni

    Hi Satish,
    Go to transaction SALE -> Basic settings -> Logical systems -> execute "Define logical system" to create a new logical system -> then execute "Assign Logical System to Client"
    That should solve your problem
    Regards
    Juan
    Please reward with points if helpful

  • How to change or rename the logical system name T90CLNT090 IN BI 7

    HI Expert's,
    i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
    in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
    In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
    because of this i am not able to create the source system between r/3 also.
    so how to change this source system name for T90CLNT090.
    regards
    harikrishna N

    Hi,
    Pls follow this OSS note : 325525.
    Note 325525 - Copying and renaming systems in a BW environment
    Summary
    Symptom WARNING: THIS NOTE HAS BEEN REPLACED.  FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
    You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
    Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
    Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
    Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
    Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
               Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
               Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
               Reactivate all partner agreements that carry the new logical system name after renaming.
    Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
               Solution scenario 2):
    If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                        Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                        Reactivate all partner agreements that carry the new logical system name after renaming.
    Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
    Scenario 3) You want to copy a single BW system of the group by database copy.
    Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                         Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
    Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                         Solution scenario 3)b): See Note 184754.
    Scenario 4) You want to copy a single source system of the group by database copy.
    Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                         Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
    Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
               Solution scenario 4)b): See Note 184322.
    Scenario 5) You want to import a client copy in a source system.
               Solution scenario 5): See Note 325470.
    Thanks & Regards,
    Suchitra.V

  • How to chage logical system name SYSTEM ECC6.0

    Dear Experts,
    We need one help, in one of our production client which is on ecc6.0 and on oracle. in that when we are executing transaction rsa1. its giving error " logical system name has been change for this system ",
    then later on we have found that the logical system name in table T000 has been changed , so now we need revert back orignal name, so we require your help to do proper step to revert back the name, also we requre what other things we need to change with respect to logical system name...
    Need your help on this issue we request your immediate support for this.
    Regards
    Yogesh

    Hi Yogesh,
    Hi Anil,
    1) Logical System Name can be changed using SALE transaction.  Go to ALE -> Sending and Receiving System -> Logical Systems -> Define Logical Systems.
    2) After changing Logical systems you have to check partner Profile using WE20 and do the necessary modifications. if required
    Hope this solves your issue.
    Regards,
    Karthik

  • Logical System(ORGLOGSY) populating from which table in R/3 system

    Hi Friends,
    I would like to understand about the Logical System(ORGLOGSY) from which table or from where this logical system being populating.
    Because we could see this fields Logical System(ORGLOGSY) exist in PO item, HDR, SGR data sources.
    Can anybody give some idea, how we'll get this source system logical system name into BW system.
    SIRI

    Hi Siri,
    Check here
    V_TBDLS
    TX: RSA13----->Tools -
    >assigment of source system to source system id
    hope this will help you.  
    Thanks,
    Vijay.

  • 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

  • R/3 Logical Systems in BW

    Hi All,
    I have an idea that we have to create logical systems(SALE) for all BW clients and R/3 clients in BW system. After that, we will assign the BW logical systems to the respective BW Clients in SCC4. But we are not using the logical systems of R/3 system in BW anywhere(please correct me if I am wrong). Then what is the point in creating the logical systems for R/3 in BW?
    Thanks,
    RPK.

    Hi RPK,
    I think here you are getting confused..
    You have to create logical system for R3 in R3 system only , and Logical system for BW in BW only.
    The name you used for the source system (logical system) must be used again for the creation of the source system in the Administrator Workbench for the BW and vice versa..so that BW and R3 can understand each other...
    I hope i am clear to you now ..please let me know If I am not....
    Regards,
    BRB

  • Business Service and logical system naming criteria across environments

    Hi !
    Imagine this scenario: File-XI-IDOC. There is a file server where files are uploaded by a legacy application. XI polls that directory, converts the file to IDOC and sends it to R/3.
    R/3 is a production business system, for example "R3_PROD", the file server is a business SERVICE, because of its abstract nature.
    Is it ok to give that business service a name such as "BS_FileServer" and then create the logical system "LS_FileServer" in R/3, to be able to receive IDOCs from the sender business service?
    If we need to use 3 different file servers, one for development, one for test and another for production...is it ok to create the business service in each integration directory with SAME name, and the 3 logical systems with same name in each R/3 receiver...because creating business services as "BS_FileServer_DEV", "BS_FileServer_TEST" and "BS_FileServer_PROD" we imagine that could give us problems when transporting scenarios from dev to test, and from test to prod...because we will need to recreate the whole scenario using the new object denomination.. e.g. a scenario including BS_FileServer_DEV in development is called BS_FileServer_TEST in test..or worse..we could have the BS object transported and as a result we would have a BS_FileServer_DEV object in integration directory of our test environment...
    Is this the right path?
    Thanks,
    Matias.

    Hey,
    When a technical system is defined  for a product / s/w comp version we also enter the parameter for logical system name. If a buisness system is defined for a technical system then it in turns refers to the technical system with buisness system assigned to it.
    Itz lyk linkage of  <b>PRODUCT -> S/W COM VERSION -> TECHNICAL SYSTEM (LOGICAL SYSTEM) -> BUSINESS SYSTEM</b>
    As per file to idoc scenario where <b>BUSINESS SERVICE</b> is used it doesn't refer to technical landscape so there is no question of Business system. With relevance to transports.
    With File -XI-Idoc scenario the concept of logical system only comes into picture if we have  a integration process also involved in the scenario. Where in adapter specific identifiers we specify the logical system name of the sender file system.
    Integration Repository.
    1)  The Software Component version need to be same in all the landscapes that is a prerequisite else transport will fail.
    Integration Directory:
    2) Assuming that transport is being done for all the objects under a service and the objects has been transported to the test landscape business service with same name will be create in test sys only address and access parameters that have to be entered again and the change list has to be activated.
    I haven't  tried exporting individual object from ID so no clue.
    Please refer the following link<a href="http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm">Transporting XI Objects</a> .
    Hope itz helpfull.
    Cheers,
    *RAJ*
    *REWARD POINTS IF FOUND USEFULL*

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

  • Logical system missing in PI SLD

    Hi,
    The problem I facing currently during transport of SAP business system from Dev to Quality system, logical system  is missing in the Adapter Specific parameters.
    The actual problem I have seen in the SLD, the logical system is a blank and even after I pushed from RZ70.
    Can you please suggest me how could i retrieve the Logical system in the SLD by automatically.
    Thanks in advance.
    Best Regards,
    Sateesh

    Hi Sateesh,
    Please check the following links for similar issue , if it helps:
    Logical system of PI in SLD
    Logical system name in SLD for the R3 buss. system is not open for input.??
    Logical System Name Not appearing in the Business System
    Also, you can enter the Logical Name in the SLD, for the related TS / BS.
    Regards,
    Azhar

  • Unable to convert the sender service to an ALE logical system... Urgent..!!

    Hi,
    Im DOing File to Idoc scenario.
    Firstly i check LS name exist or not in BS.. then i found its not maintained.
    I edited the BS and provided the required LS name.
    and the same has been tested in ID
    Business System -> Service -> Adapter Specific Identifiers .
    Now i got logical system name in "Adapter Specific Identifiers".
    Pressed Apply, save and activate the changes.
    But still it is showing the same error.
    1. Any idea what might have gone wrong??
    2. I need to maintain the
       LS name of R/3 in  XI system? and
       LS name of XI in R/3 system?
        Is it necessary?
    Waiting for your answers.
    Regards
    Seema.
    Edited by: reddy seema on Dec 27, 2007 1:37 AM

    Hi Reddy,
            just mention the logical system name in the  Sender Business system or Service ( click on sender business service> Service(menu)>  Adapter Specific Identifiers--> specify the logical system name  which you configured in R/3  WE20 ..)  in R/3  side  WE20  you need to configure  the Inbound parameters  of your Idoc  .. 
    Here  sender business system and Reciver Business system logical system names are different.. for checking just go to  Services and check the adapater specific identifiers..--> then you   can find the name of logical system.. like that you need to check for both systems.. and both should be different..
    try with this option..
    Regards
    @jay

Maybe you are looking for