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

Similar Messages

  • Logical system group

    Hi all,
    I asked this question a few weeks ago and I am still unclear about it. I am going to connect a second ERP system to the GTS box and want to know the following.
    Since the two ERP systems don't share any master data or org structures I am going to create a new logical system group for this.
    What I am unclear of and I can't seem to find the answer anywhere is do I need to also create a new logical system group name for GTS also.
    My gut feeling is no but I am not sure.
    Thanks in advance,
    Chris

    Hi Chris,
    No.  You just need a single LSG for GTS, so that you can create local master data - for example, Customs Offices - that is not related to a feeder system.
    I hope that answers your question.
    Regards,
    Dave

  • BI:Logical system name has been changed for This System

    Hi, Gurus,
    I want to Use my IDES SAP ERP 7.0 as my BI system for training purposes,when iam executing the transaction RSA1 in the system it is giving message
    "Logical system name has been changed for
    system"
    I Have changed the entries in table "RSADMINA" and maintained the Client no as 100 (My base client for BI) which i have copied from 001.
    When iam executing the Transaction RSA1 in 100 it is giving above mentioned error ,whereas in 001 it is working fine.
    Please Help . ..
    I tried to change the system logical name by "bdls" but it doesnt worked........

    Hi Deepak,
    Check the entries in table RSLOGSYSMAP (this is meant for correct conversion of logical system names for tansports).
    You can easily maintain the entries using tcode RSLGMP.
    Hope it helps.
    Grtx
    Marco
    PS I'm not a basis guy but do you have a correct BI installation yet?

  • RSA1 error  Logical system name has been changed for this system

    Hello All,
    Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.
    But now when we login to client 500 and execute RSA1 it is showing
    Logical system name has been changed for this system"
    In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps
    Change the name of the logical system (table T000) for client back to SIDCLNT300. This enables you to continue working with the system.
    If you really want to change the logical name, than you can, if and when you:
    change the system name back to SIDCLNT300,
    delete all existing connections between this system and other systems,
    delete all transfer structures that still exist, and
    do not use ALE or Workflow.
    Guys do you know how to fix this ? .
    Also do you know Assignment of Source System to Source System ID (table RSSOURSYSTEM) using RSA1 ?
    Edited by: Sahad K on Mar 17, 2008 10:55 AM

    Hello Hari,
    Both the options you said  cannot be used
    since the logical system SIDCLNT300 is used by client 300 and it cannot be given to client 500.  Also there already exist a logical system SIDCLNT500 which is assigned to client 500.
    I found out the issue. In the table RSBASIDOC  the logical system name that can use rsa1( bw  client )is set as  SIDCLNT300).  Only if we delete that entry and set it to SIDCLNT500 ( 500) we can use it on client 500.
    The solution is specified in /message/3284842#3284842 [original link is broken]
    Let me try the solution 2 and inform you.
    Solution 2:
    You cannot delete the source system. Two cases have to be distinguished:
    The source system still exists.
    Switch to Transaction SM59. Find the destination which has the same name as the logical system of the source system from field SLOGSYS in table RSBASIDOC (see above).
    Such a destination does not exist in Transaction SM59. In this case, you have to create the destination to the source system. Name the destination equal the entry in SLOGSYS from above. Then return to the Administrator Workbench and repeat the deletion.
    The entry exists but a remote login is not possible. Correct the communication parameters.
    Everything works. Change to Transaction SE37, function module RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS = <log. name of the source system>, I_FORCE_DELETE = 'X'.
    The source system no longer exists or was replaced with another source system with the same IP address.
    Proceed as described in the first case but make sure, that the field 'Target host' contains a not existing server in the maintenance screen of the destination (Transaction SM59). If necessary, change an existing entry. Later when you delete, the system asks you whether you want to delete, although the source system is not available. Select 'Ignore'.
    Incase you have any idea other than this please let me know how to edit the RSBASIDOC table  and change the entry to client 500.
    Edited by: Sahad K on Mar 18, 2008 5:07 AM

  • Error message "No business area can be determined for item 000010"

    Hi all,
    I had maintained business area assignements.
    However, while creating a sales order, the following error message appears : "No business area can be determined for item 000010"
    What does it mean ? And how can I fix this problem ?
    Regards,
    Bahia.
    Edited by: Bahia M. on Nov 13, 2008 11:58 AM

    Dear Bahia,
    Please go to IMG path assign the business area
    IMG>Enterprise structure>Assignment>Sales and Distribution>Business Area Account Assignment-->Define Rules By Sales Area(Roule 1)
    -->Assign Business Area To Plant And Division
    I hope this will help you,
    Regards,
    Murali.

  • No business area can be determined for item 000010

    Hi All
    I'm facing above error during sales contract (T code VA41) creation.The following are the scenario,
    we had two plants, one is manufacturing 'A' and another one is warehouse plant 'B'.Noramally we will do GR against production order in manufacturing plant 'A'and will make stock transfer to ware house plant 'B'.We made this transaction and material also transferred.
    But we are trying make sales from warehouse plant 'B' for that material.We are getting error message during sales contract creation 'No business area can be determined for item 000010'.This error comes for all materials extended to warehouse plant 'B'.This plant newly created,we checked all config every thing alright.
    Anybody can help me out of this issue.
    S S

    Hi Suresh,
    Go to TCode: SPRO -- Enterprise structure -- Assignment -- Sales and Distribution -- Business Area Account Assignment -- Assign Business Area To Plant And Division and check also --  Assign Business Area by Sales Area.
    Check whether you have maintained here the necessary settings for plant B.
    Hope this solves your problem.
    Thanks,
    Viswanath

  • BI  Error Logical system name has been changed for this system

    Hello All,
    I have installed the BI system and did a client copy from 000 to 200 client with profile SAP_ALL.
    Now I have loged into the system with client 200 and wen I run RSA1, I am getting the following error
    message: "Logical system name has been changed for this system"
    Thanks
    Sekhar..

    Hi,
    Goto tcode SCC4.
    Switch to change mode. (System will prompt that this table is cross client. Continue)
    Select your client (in this case 200). Click on details button (next to change mode button)
    Enter the proper logical system name in Logical system field.
    Click on Save button.
    Then try RSA1.
    Hope it helps
    regards,
    Pruthvi R

  • Logical system name has been changed for this system

    Hi gurus,
    I am fasing problem in BI7 system. we created a new client in the system & want to set it for BI development.
    System Response
    The transaction is canceled.
    Procedure
    Change the name of the logical system (table T000) for client  back to BID500. This enables you to continue working with the system.
    If you really want to change the logical name, than you can, if and when you:
    change the system name back to BID500,
    delete all existing connections between this system and other systems,
    delete all transfer structures that still exist, and
    do not use ALE or Workflow.
    Regards,
    Darshan..

    Sorry, BI is a one client system. You cannot have a prod client and a dev client within one SAP system.
    But...
    ...NO, you can't!
    Best regards
    Michael
    EDIT: just to add, there is an exception if you have a SCM/APO type system [522569 - BW: Working in several clients (especially APO 4.x/SCM 4.x)|https://service.sap.com/sap/bc/bsp/spn/sapnotes/index2.htm?numm=522569]

  • Logic Pro 9.6.1 searching for Audio units

    Logic keeps hanging and stops repsonding in 64-bit mode. Same for MainStage. Is there a fix or an issue with Lion. This worked then just stopped working and this problem began. When I re-install and bring it back to 32-Bit no problems. Does anyone know if you can run these pro Apps in 64-Bit with Lion or is this a Lion issue? Never had a problem with Snow leopard. Any help or advice would be greatly appreciated.
    If it is that I must run in 32 bit mode then what is the purpose of 64-Bit if you cannot use it?
    Thanks to all the fellow users out here!!!

    Hi all, went back to Snow Leopard. Lion is not worth the problems and money that you have to keep on spending.
    It will make apple the wealthiest business ever.

  • Output determination for Handling units

    Hi
    In logistic execution, where should handling unit out put determination procedure be assigned pls ?
    Thanks In Advance

    Dear Jaya,
    Once, Configuration settings done, go to  T. Code: Nace  and select Application as V6 - Handling Units and click Tab: Procedures. Now select Procedures, as available, and double click Control.
    Here, maintain, Condition type: and Requirement:
    Now go back, and again select Application as V6 - Handling Units and click Tab: Output Types.
    here, select the Output Type and maintain entries for Mail title and texts, Processing routines and Partner functions
    Hope, this may help you.
    Best Regards,
    Amit
    Note: Alternatively, T. Code: VHAR, and select Packaging Material Type, and double click.
    On to next page, under Tab: Packaging Material Type, key-in entries in to Fields: OutputDet.Proc and Output Type

  • Multiple Logical Systems in Partner Profile for one instance

    Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System?  If it is possible, can we create Logical System with respect to Plant/Country?

    I am not quite sure if I understood your problem completley. But let's see...
    Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
    You can find more information about it in this guide here on SDN:
    Link: [High Availability;
    More information about High Availability Setups for SAP System can be found here on SDN:
    Link: [High Availability]
    If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
    Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
    Hope this helps.
    Best regards,
    Mathias

  • Logical system name for acknowledgement in BPM

    Hi,
    I have a szenario:
    IDOC --> BPM --> MAIL
    Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
    When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
    "Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
    What can I do?
    Possible Solution 1:
    I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
    Possible Solution 2:
    I can enter an existing logical system name in the "adapter specific attributes".
    BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
    Is Solution 1) a common way?
    Thanx
    Regards
    Wolfgang Hummel

    Hi,
    there are many ways:
    some for aleaud are described in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    >>>>Is Solution 1) a common way?
    no this is not good a good idea
    BTW
    you can also supress aleaud raport IDX_NOALE
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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

  • Wrong logical system for partner profile

    Dear gurus,
    we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
    Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
    After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
    But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
    Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
    EDI: Partner profile outbound process code not available
    Message no. E0335
    Diagnosis
    An outbound partner profile could not be found with the following key:
    /MSC_MM_PRD/LS//EF/ZEDI//
    [u2026]
    Procedure
    Please check the outbound partner profiles for the assignment of the process code:
    As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
    Can anyone please tell me why SAP uses the old logical system and how I can change that?
    Cheers
    Alicia

    Hi,
    problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
    Cheers
    Alicia

  • From R/3 to CRM create one logical system for CRM client 300.

    Suppose i create one logical system for CRM in R/3 TO CRM scenario for client 300.another user wants to work on jdbc to CRM client 300 for this he wants to create another logical system for client 300 it is not possible,so,it is ok if he assign same logical system when he was working for CRM client 300 when he wants to create business system for CRM in JDBC to CRM.

    Hi,
    Business Systems are te logical system name for a CLient in the SAP.
    These can be reused again for different configuration scnario that you must have created for different interface.
    All you need to do is assing the Business system to your configuration scenario and Communication channel to the same.
    Regards
    Vijaya

Maybe you are looking for