Logical system determination

Hi,
how can I determine own logical system.
Thanks.
Marian

U can determine the own logical system using the FM OWN_LOGICAL_SYSTEM_GET.See the example code below :
data :  l_ownsys   TYPE logsys.
  CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
    IMPORTING
      own_logical_system             = l_ownsys
    EXCEPTIONS
      own_logical_system_not_defined = 1
      OTHERS                         = 2.
l_ownsys will contain the logical system.
Cheers
Nishanth

Similar Messages

  • Could not determine BW release of logical system 'BWPCLNT100

    after a BI systemcopy (production to development) we get the following
    error when we run load jobs of type "delta load". full loads work fine
    "Could not determine BW release of logical system 'BWPCLNT100'"
    even if i start the deltaload from the R/3 system with transaction RSA3
    with update mode "C" i get the same error . when i use update mode "F"
    it works fine , but that's not the thing we want.
    BWPCLNT100 is the logical system of the productive system .
    we have changed all the logical system setting to BWDCLNT100 using
    transaction BDLS and we have also changed all entries in RSBASIDOC,
    RSISOSMAP, RSOSFIELDMAP,.... .
    we have done several systemcopies in the past , they all worked fine
    and without this error. this is the first copy in BI 7.00 .
    are there any loadmodules which have to be regenerated with the new logical system name?
    thank you for your help and kind regards hannes toefferl

    Hi,
    As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
    This mainly happens due to init disturbance in the source system.
    I would suggest you to delete the init and rerun the Init from BW once again.
    This should solve your problem.
    Thanks
    Mayank

  • No logical system group can be determined for administrative unit &1

    Dear GTS gurus,
    In Risk Management module when we execute the report "Analyze LTVD Request Relevance of Products" (/SAPSLL/PRE_VD_OPT_ANL_PROD) we sometimes get the error message:
    No logical system group can be determined for administrative unit *******
    Now I did some googling and found the following website: consolut - /SAPSLL/PRE_VDEC139 - No logical system group can be determined for administrative unit &1 - /SAPSLL/…
    It says that in customizing item "Define Administrative Unit Attributes" some assignment is missing but I was not able to figure out what exactly. I compared it with Administrative Units which did not not issue any error messages and customizing looks good to me.
    Can you share your insights on this topic?
    Best Regards
    Greg

    Hello Gregor,
    Under the Admin Unit attributes, you must have a Plant Group defined.
    Is that Plant Group assigned to a logical system ?
    (IMG: General Settings -> Organizational Structure -> Define Cross-Plant evaluation (or Define Plant-based BOM evaluation)
    By the way, the site you have found is one of the many sites out there that lists the messages available in a SAP system. The same information is available within GTS (Transaction SE91).
    Regards.
    Mouaz BEN REDJEB

  • ATP Check Issue - No business system could be determined for logical system

    Dear all
    Got an issue while executing ATP check on a planned order in product view,
    with a message: "No business system could be determined for logical system"
    CIF setting wise:
    regular business system group maintained and assigned in place,
    master data wise:
    business system group info fine in product master,
    Is there anywhere suggested to check under ATP setting:
    category, check mode, business event, check control/check instruction?
    Your kindest enlighting is appreciated,
    Thank you,
    mandy

    Dear Mandy,
    usually this error is caused by a missing customizing entry:       
    spro:                                        
    Integration with SAP Components
       Integration via APO Core Interface (CIF)
         Basic Settings for Creating the System Landscape                             
           - Maintain Business System Group
           - Assign Logical System and Queue Type :
    Please read the documentation for these two transactions and create the systems.
    You need to specifiy there all systems that are in your BSG. The documentation for the customizing of 'name logical system' in APO  says:                                                                               
    To enable the transfer of data between SAP R/3 and SAP APO, you need to name both the SAP APO system in which you are working and the SAP R/3  system to which you want to transfer data as logical systems.          
    I hope this helps.
    Regards,
    Tibor

  • How to determine logical system in a routine

    Hello everybody,
    I want to extract data from a ODS-Object (let's say A) to the other ODS-Object (B).
    The A-ODS includes data from different R/3-source-system, where I want to select the data from one R/3-source system into B-ODS. Normally I can use the InfoObject 0LOGSYS (which exist as a key-field in A-ODS) with a constant string ofR/3-source system. But the Problem I we have when tranposting to different BW-System.
    My question is: how can I determin the BW-System (logical system in a routine, where I can program the coding more flexible? Is there a field for source system similar to sy-datum or is there a function module ?
    Thanks so much in advance!
    Van Anh

    Welcome to SDN
    Check the table RSOSFIELDMAP
    Assign points if useful
    Regards
    N Ganesh

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

  • 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

  • SWO1 - No destination could be determined for logical system

    Hi there,
    I am trying to call a remote transaction via SWO1, but I am getting the following error:
    No destination could be determined for logical system TSTCLNT120
    Message no. OL860
    Diagnosis
    You attempted to instantiate an object with the specified logical system within the distributed runtime environment. However, an RFC destination has not been defined for this logical system.
    System Response
    The object instance cannot be generated.
    Procedure
    Define the RFC destination or use the local runtime environment.
    I go to SW01 --> Type an object name "TSTC" --> Click TEST --> New Dialog window Clicked on the Full key --> Entered the Logical Name for remote system (ECC), and also Entered Key: SU01 --> When I click on the continue, I am getting the above mentioned error.
    I can clearly see that it is looking for mapping Destination for that Logical name. Can someone please tell me what t-code or table I need to go and map the Logical Name with a RFC destination?
    Thanks in Advance
    Kumar

    hi
    try these links
    Re: R/3 Connections in RFC destination node.
    Assign a logical system in RFC
    Regards
    Sajid

  • "Cannot Determine Logical System"

    "Cannot determine Logical System is an error I am facing in an RFC connection. What changes to the sttings do I need to make to remove this error?

    Hi Yogesh,
    just check with the below links they may help you.
    help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    help.sap.com/saphelp_nw70/helpdata/en/e9/9bc93f92908032e10000000a11405a/content.htm - 22k
    www.*******************/2007/05/ale-abap-cross-applications.html - 138k
    www.sap-img.com/bc059.htm - 6k
    help.sap.com/saphelp_nw04/helpdata/en/da/5990df015b5b43a36f6ce7fa1ee8c0/content.htm - 8k
    help.sap.com/saphelp_nw70/helpdata/en/cb/0f3040cbe60d418d7b4373c0cbf84a/content.htm - 12k
    thanks
    karthik

  • Party/Receiver determination/agreement with logical system

    Hi all
    I have gone thru various messages in the forum dealing more or less with the issue, but haven't really found an answer to my problem yet.
    XML orders from a Web shop are sent to XI, which I am mapping to an IDoc of type ORDERS.ORDERS05 to be sent to the SAP R/3 backend system. The partner profile in the backend system is defined as a logical system because (a) even though the Web shop is for a closed user group of known customers, I could not possible create a partner profile of type KU for every of them, and (b) I need to do some special stuff for IDocs of this order process which is triggered by a separate process code.
    My plan in XI configuration was to create a new scenario and setting up either two parties or one party and a service without party (with a business service). I have tried both ways, but I am not getting it to work. The main reason for that is because of "Unable to convert sender service xxx to an ALE logical system". The "standard logical system" is used in another scenario already, and because of the special processing in the backend, I would like to keep it separate by a logical system defined for this process only anyway.
    Posts with party definitions and logical system problems exist already, but I haven't really found a applicable answer. Can something be done in the header mapping (which I am not so familiar with yet) to get one or the other way to work, or is there another "good" way completely to handle this?
    I am a little bit lost right now, and would appreciate your feedback. Thanks,
    Daniel

    Hi Michal
    Thanks for your feedback. I have implemented the scenario anew based on your input, and other information that I've found. I've got a working solution after playing around with the settings for a while, and is as following now:
    R/3:
    System id: D01
    Client: 200
    WE20: Partner Type LS
    ...Partner no.: XI_ABC
    ...Parter type: LS
    ...Inbound message type: ORDERS
    SLD - Technical system:
    Technical system type: Third-Party
    Name: XI_ABC on xy01sys01cs
    ...Installed products: SAP R/3 ENTERPRISE, 47X200
    ...Business systems: XI_ABC
    SLD - Business system:
    Business system type: Third-Party
    Name: XI_ABC
    ...Related integration server: XD1
    Integration Directory:
    Scenario: CSC_ABC_ORDER
    ...Party: PP_ABC_SYSTEM
    ......Business service: BS_All_Data
    ......Communication channel: CC_S_File_ABC_Order
    ......Adapter type: File
    ...Party: PP_SAPSYS_ABC
    ......Business system: XI_ABC
    ......Adapter-specific identifiers: Logical system XI_ABC
    ......Communication channel: CC_R_IDoc_To_SAP
    ......Adapter type: IDoc
    ......RFC destination: D01_200
    ......Port: SAPD01
    ......NO Apply Control Record Values from Payload
    ......NO Identifiers
    ...Service without Party:
    ......Business system: XI_ABC
    ......Adapter-specific identifiers: Logical system XI_ABC
    ...Receiver Agreement
    ......Sender party: PP_ABC_SYSTEM
    ......Service: BS_All_Data
    ......Receiver: PP_SAPSYS_ABC
    ......Service: XI_ABC
    ......Interface: ORDERS.ORDERS05
    ......Receiver communication channel: CC_R_IDoc_To_SAP
    ......Sender service constant: XI_ABC
    ......Receiver party constant: <space>
    Once again, thanks for your input.
    Regards,
    Daniel

  • How do you identify the Logical system in start routine of a transformation

    My scenario is this.  I have five r3 systems that I am extracting from.   In the start routine of the transformation from the r3 data source to my data store I  am going to delete data and I need to know the source system id.    How do I identify the logical system or source system id in the transformation.  Is there a system field that contains this information.    I do not want to hard code the source system id in the routine.

    hi
    have a lool at tables rsreqdone and rsbkrequest with a join you should be able to determine the source.
    regards
    Boujema
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).
    Edited by: Boujema Bouhazama on May 9, 2008 12:04 AM

  • New outputs generated when changing logical system in output master record

    Hi!
    We are sending documents from ECC 5 to a legacy system via XI/PI. We are about to move from an old XI installation to a new PI installation. The output record used (for example in a billing document) is set up based on logical system. When moving from the old to the new platform, we need to change the output records from the old logical syste to the new logical system. However this leads to generation of new outputs in all billing docs when opened in change mode. This goes also for billing docs where we already generated outputs via lthe old logical system in the past. Is there any solution to prevent the automatic generation of outputs for documents where the condition type already was successfully processed (as it works when the logical system is not changed)?
    Best regards
    /Björn

    Normally the same output is not supposed to be generated, unless 'Multiple issuing' checkbox is checked in the output type configuration.
    Also you can probably add a requirement in the output determination procedure and check if output record already exists. Take a look at the standard 'Reprint' routine, kind of the opposite is needed in this case.

  • Can there be more than one port for the same logical system

    Can we have more than one TRFC port for tranferring data from one logical system to another?
    The requirement is to transfer same basic idoc type from one logical system to another through two different ports. Is it possible?
    For eg. some specific data (country specific) for the same basic idoc type can be sent through a separate port and the other data through a different port inorder to distinguish between the two.

    Hi Shital,
    I don't think so. Because of that what i told you. There would be a dirty trick (back routing) to solve your issue. But its quite difficult and not standard. You create two http receiver services  and two http sender services. You route your message depending on payload to the one or the other http receiver channel. The receiver is in both cases: THE XI! Now you have a second message, which you  can route to IDoc adapter. But in this case you have different sender and in the receiver determination you can put the sender, so you will be able to use different communication channnels and so different ports / destinations.
    Advantage: Your task would run, no performance problem (http: very good, asynchron)
    Handicap: You see every message double in the monitoring, the scenario is not easy to understand and it is a big task 4 other people to change it.
    Regards,
    Udo

  • RFC and Logical System names

    Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

    Hi Gaurav,
    It is recommended, but not mandatory, right, Muthuraman?
    The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
    Regards,

  • ALE logical system - File -- XI -- R/3 scenario

    Hi
    I have the following scenario which I'm trying to run.
    File --> XI --> R/3 scenario.
    I have created a sender agreement XID|ASN_out|NBD where XID is my XI 3.0 system and NBD is my R/3 system. I have also created an interface determination and receiver determination.
    The following error is in transaction SXMB_MONI in my XID system:
    "Unable to convert the sender service to an ALE logical system"
    Both XID and NBD are business systems defined in SLD and they have both a logical system assigned.
    Why do I get this error and how can I fix it?
    Best regards
    Göran
    Message was edited by: Göran Westin
    Message was edited by: Göran Westin

    Ok. I fixed the problem.
    In the Integration Builder - Configuration > Select business system of choice > Menu > Service > Adapter specific identifiers > IDOC Adapter > Logical system - got a value after reading/refreshing it from the SLD.

Maybe you are looking for