Use of Logical Systems -  Compliance Cal +ve's and -ve's

Hello
We are looking at setting up a logical system to connect all our various systems to CC.....  rather than entering each system individually in each of the functions.
Does anyone have any experience they can share with regards to use of logical systems?
I can only see positives - given that you add a Logical system once to a Function and then when a new system comes along, you just update the Logical System.
However I am interested to hear what do you think of using of logical systems and if there are any downsides?
Thanks

I always use LOGICAL connectors as this allows you to more easily manipulate the ruleset and teh systems that it is connected to.

Similar Messages

  • 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

  • Use of Logical Systems - RAR 5.3

    Hi,
    i have created 2 physical systems (QA and Production systems) with the necessary connectors and assigned it to a single logical system.
    Subsequently i have generated the rules for that logical system. However when i run a risk analysis i do not see tha tlogical system as an option for the dropdown box labelled "system". How is the logical system set of rules supposed to be used?
    The config guide states that it allows maintenance of a single ruleset across several systems, can this theory be applied for risk terminator as well?
    Thanks,
    Edwin

    Hi Edwin,
    Subsequently i have generated the rules for that logical system. However when i run a risk analysis i do not see tha tlogical system as an option for the dropdown box labelled "system". How is the logical system set of rules supposed to be used?
    You wont see the logical system in the dropdown list. If you set up the logical system and generate the rules correctly it will automatically call the logical ruleset whether you choose QA or PRD.
    The config guide states that it allows maintenance of a single ruleset across several systems, can this theory be applied for risk terminator as well?
    RT's is configured in the backends for every system with transaction /N/VIRSA/ZRTCNFG
    Kind Regards,
    Vit

  • Already used Logical System in Business Service?!

    Hi, well i am facing a JMS2IDoc-Scenario.
    As sender i configured a Business Service (K15) with the CC_JMS. The receiver is a business system (HRT) with the CC_IDoc.
    While i test the scenario i received following error:
    "Unable to convert sender service to an ALE logical system"
    Thats fine so far, therefore i checked the Adapter-Specific Identifiers and entered the Logical-System name. This is already in use at the business system (HRT) because of some CC for other Scenarios.
    Now there is the problem that i can't use this logical system name at K15, no idea why.
    Because of not having the technical details of the source-system (JMS) i choose to use business service. Is there another idea?! Party?!
    br, Jens

    Hi,
    The issue is with the fact that this Logical System Name has been assigned to another Business System ( say Buss System X) .And you want to use this same Logical System Name for the sender JMS service( Buss System Y) as well , correct?
    Solution is,
    In the Receiver Agreement , Select Header Mapping and for the Sender Servicce, select the Correspodning Sender Service  ( Sleect Buss System X )to which the Logical System Name is assigned.
    Now in the runtime this will be used as the Sender Service from which the Logical System Needs to be taken.
    Regards
    Bhavesh

  • Logical System already use in BPM

    Hi
    We have created two BPMs and one of them the Logical system is configured to 0071ME36. For the second BPM we tried to use the same logical system but we get an error in the XI "Logical System 0071ME36 is already use in the BPM_6547_.
    That`s means we must use diferent logical system name for each BPM we created?
    Thanks in advanced.

    Hi Ger,
    >That`s means we must use diferent logical system name for each BPM we created?
    Yes, u r right.
    One (dirty) trick: Route the message per HTTP adapter back to XI and route incoming message without mapping 2 IDoc adapter. Use only dummy datatyepes, messagetypes, interfaces. There not prooved during runtime.
    Regards,
    Udo

  • Logical system and business system

    Hi experts, please help me with the below questions---
    1) What is the diff between logical system and business system?
    2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
    3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

    Hi,
    Business System :
    1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
    2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
    Business Service:
    1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
    2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
    3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
    4.Business Service has no SLD Entries and No Assigned Products and SWCV's
    Regards
    Sangeetha

  • Integration server as logical system in IDoc to file scenario

    Hi,
    Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
    For which logical system will the outbound partner profile configured?
    Regards,
    Gajendra.

    Hello,
    I feel that the RFC destination linked to the port is the key here.
    Because the scenario (IDoc to File) works in both the cases:
    Case 1: Used the logical system as Integration server
    Case 2: Used the logical system related to the file (third party) in the SLD.
    In both the above cases the RFC destination points to the integration server.
    Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
    It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
    Thanks.
    Regards,
    Gajendra.

  • ALE logical systems for business service or process

    Hi,
    I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
    I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
    "Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
    How can I handle this problem?
    Should I hard code values somewhere?
    Which ones?
    I have read the other posts for the error above, but my situation seems to be different.
    Help!
    Chris

    Hi,
    To solve your problem, here my solution:
    1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
    2/ Create this Logical System on your target system (R/3).
    WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
    Mickael.

  • 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

  • RFC destination Could not be SPecified for Logical System

    Hello there
    i am traying to costomize Transaction Luancher for some of the report which is been devloped in ECC (wich is ARD 100)
    when  on Transaction launcher Wizard--> techincal
    i am  having a  logical system as ARD100(my r.3 system where report is devloped and which is connected to CRM )
    while chosing the OBJ.TYpe :   and Method:
    it says shows three erroe :
    1) RFC destination could not be specified  for the logical system ARD100
    2) Object type and Method is not available
    i have checked RFC  , in  SM59 entriesu2026u2026 There is an RFC named ARD100 and the connection test works. I also did an authorization test and it also works. I also checked to make sure the logical system name ARD100 exists
    could you please help me to resolved the same
    Regards
    Rajiv

    Hi Rajeev,
    In a system landscape it's important and necessary to use the logical system names consistently throughout all systems!
    Therefore please make sure, that you always use the same name for a logical system in all systems (CRM and R/3 systems).
    The following steps are required before a RFC call is made from the CRM system to the R/3 system :
        o  Use transaction SM59 to create an RFC destinations for the remote
           system.
        o  Use transaction BD54 to create the logical system.
        o  Use transaction BD97 to link the RFC destination created in SM59
           with the logical system created in BD54.
    I hope this helps.
    Best Regards
    Gavin

  • Logical system name in SRM system

    We are into SRM version 5.(SRM server 5.5) with the backend system as SAP ECC 6.0 .
    The logical system is defined as '0000000050' for backend SAP  system . All the systems like CRM and BW uses this as the logical system name for backend system . Recently SRM is implemented in our organization and we have no other choice and have to use the logical system name as '0000000050'
    When product categories are assigned in the org attributes , the system stores the back end system as  50 and this is the issue. SAP support mentions that this is issue with logical system naming convention and that need to be fixed . But they fail to understand that the same name works fine in all other systems and also in SRM system except product categories .
    Is there any OSS note for this fix. I would like to hear your experiences in this scenario.
    Thanks
    Mani

    Hi Mani,
    Logical System names are system specific, hence you have a different name in SRM system which will represent your backend system and this is not at all an issue. As suggested by SAP; '0000000050'  is not the best name as per best practices.
    You should have a name which should be of the pattern: <SID>CLNT<Client Number>.
    Now here is the solution/work around. But be very careful and try this in sandbox system before being carried out in Dev/QA/PRD systems. Please make sure no other users are performing any activity while these tasks are being carried out.
    In addition, please read through the ["Set up and system copy of SRM server 5.5";|https://websmp204.sap-ag.de/~sapidb/011000358700000310782007E/SRM50_SetupTranspCopy.pdf]  guide before you carry out this activity:
    The below activities are to be carried out only in SRM system
    I assume SRM & Backend are separate instances
    1. Create a new logical system name for the backend system in SRM system as per the standard suggested above.
    2. Then use the transaction BDLS, to convert the old logical system name to new logical system name in all the tables.
    3. Now, the step 2 ensure the logical system name is converted appropriately in all tables except SRM Org Structure related table.
    4. Use the report RHOMATTRIBUTES_REPLACE, for replacing all the old logical system value with new logical system value. Please note while providing the inputs in the screen, there will be a Checkbox field called "Sub-String", you must check this one for all attributes you enter in the report. Then when you execute the report, a list will be display, here you have to select all the rows and click the first button on the toolbar. Only then the attributes will be updated.
    Please let me know, if further inputs are required.
    Regards, Kathirvel

  • Logical System for R/3 IDoc processing

    Is there a way to use one logical system when data is coming from multiple sender communication channels?
    We get data from several MQ Queues via JMS Sender Communication Channels.  There is a separate queue per plant.  No matter which queue a file comes in on, it needs to create the same IDoc type in R/3.  So, they all need to be assigned the same logical system.  Is this possible?

    It is possible in the reciever agreement to define which service the message should come from.
    See http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    Here you can make a header mapping and define which service you want the message to come from.

  • Error in the logical system (BW - R3 connection)

    Hey guys, i need help, actually i created a connection between BW and R3 system, but i think i wrongly assigned the details to another BW system and now whenever i tried to load the data, it's not being processed.
    And i checked and it shows me that the connecetion is between source system (538) and BW (B3T800), though my BW client is BW (BW TEST). so how do you think i can change my background users i assigned while creating the source systems, because i think, while creating the source system, i used wrong background users. So instead of connecting via logical system (BW test), its connecting via (B3T800) to SAP R3 (538).
    --> Also i tried changing the Logical system name, as i checked and showed that for my BW client now it has a entry of the BW system (B3T800) and when i tried chnging it, it let me change that, but when i went to the RSA1, SAP doesn't let me access that, saying a message "your logical system has been changed", so can i change the logical system, do you guys think my problem will be solved?
    Regards,
    Amit Jaidka

    I have checked in SM37 taking that request number and when i checked the job log , its showing
    5 LUWs confirmed and 5 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    Lock table overflow
    Job cancelled after system exception ERROR_MESSAGE
    what is the reason for this termination in R/3.
    Thanks

  • Message determination and Partner function LS (Logical system) for PO

    Hi,
    I have worked in the past with vendors (VN) as partner roles in a PO, with the message to create an EDI outpout to Partner Type: LI (Vendor), and this works succesfully.
    Now, the idea was to use in EDI, a Partner Type: LS (Logical system) as a receiver of EDI messages (message types: ORDERS) for inbound Purchase Orders to the Partner.
    So, we have set up a respective message condition, with Partner Function: LS  (Logical System), in transaction: MN04 (Create Output-condition records).
    A. When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent to partner.
    B. When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
    Company code is assigned to purchase organization, and so is purchase organization to plant.
    Any idea why there is no automatic message determination in the case of the transaction: ME21N?
    There is a single message condition that is to be read for both cases (trans: ME59N and ME21N).
    Note: If I try ME21N, and enter the output type and partner (=Logical System), manually, I receive a warning message :
    VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent.
    However you can not assign a partner function LS to a vendor, in vendor master data, because of message CZ 327 (Can not use this partner role).
    Anyone with similar experience? Thank you for your advice.

    Hi,
    I well understand that the receiving partner can be a partner: Vendor (LI).
    I have seen that working.
    However, in the Partner Profiles (trans: WE20), the receiver was created as a Logical System (LS).
    We want the partner Logical system (LS) to receive the idoc for purchase order (ORDERS).
    After that, I think that the idea is that the LS can generate an idoc for a sales order creation that will then outbound to another partner.  I think that this is the concept.
    The issue is that I have seen that the POs created with transaction: ME59N, have received from message determination (trans: MN04) the message with partner LS (automatically), and the idoc of the purchase order (ORDERS) have reached the partner LS.
    The question is why the message determination fails when creating the PO from trans: ME21N or ME21, with reference to the PR. Message condition is the same and message determination procedure is the same for both cases.
    There is no issue with customizing for the LS in trans: WE20
    (Port processing agent is Active for LS and ORDERS have the proper processing code for application EF).
    I hope I am helping more with this.

  • How to configure a Logical System for XI External System

    I'm following the 'How to configure SAP XI to use the standard SAP communications APIs (idoc, pabi, rfc) from external system - How to create XI content with the Integration Builder' document.
    I have everything configured, but in section 6.7 when I try to do a transaction BD10 on to send a MATMAS01 idoc using my Logical System IQS_EXTERN to my external system, it says '1 master IDocs set up ...', then it says '0 communication IDocs generated ...' and my external system does not get the IDoc. The NX7 Integration Engine does not get a message from SAP_CE8  to IQS_EXTERN.
    How do I specifically configure my Logical System IQS_EXTERN to communicate with my external system via XI (NX7)?
    I'm using the ICC Test-System CE8, SAP R/3 Enterprise 4.7 IDES and the NX7 Exchange Infrastructure (http://iccpi7.sap.com/rep/start/index.jsp).
    Thanks,
    Ed Culnane
    Edited by: Ed Culnane on Oct 15, 2008 7:02 PM

    Check whether you have setup Partner profile for receiving system ( Here its XI system). You need to create outbound parter profile for XI system.
    Check out this forum ...
    Re: trying to send Idoc using Standard Outbound Processin option
    and blog ..
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    Hope this will help.
    Nilesh

Maybe you are looking for