Distribution system for logical system not correctly maintained

Im logged in into SAP R/3 system. When starting transaction POIT I chose "production orders for".
I fill in the fields for
Plant -> 001
Material -> T-HV200 (Ice Mix)
At the top I have to enter a "optimization system".
I chose the logical system I created (CE6CLNT850) from a list.
After I hit the execute button it says:
"Distribution system for logical system CE6CLNT850 not correctly maintained."
The distribution model for CE6CLNT850 (transaction: BD64) looks like this:
Componentsystem CE6 SAP R/3 4.6c----
CE6CLNT850
     NX7CLNT800----
NX7CLNT800,No Short text exists
           LOIPRO----
Production order
What is the problem here?
And by the way, WHY DO I HAVE 479 entries in my list of logical systems when I'm trying to chose the "optimization system"???
best regards,
Lunatikk

Thanks for your answer,
the RFC destination is configured correctly. It says that the connection works when I run the test.
I'll post it in an other forum as you suggested but I have another question:
You said that it is possible to have 474 logical systems configured on the system.
1. Who defined those systems and why?
I am the first one in my company using this system.
We ordered to a SAP system through RAC Service.
I thought we would get a "fresh installation" of the SAP system -
2. please correct me if I'm wrong.
For example there are logical systems with names like "boon software" and "camstar", which are real companies.
There aren't just logical systems configured, there are also additional RFC destinations, distribution models and ports that were there from the beginning.
3. Is it possible that those logical systems interfere with the sending of the IDOC. Could it be possible?

Similar Messages

  • Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA

    Hi,
    I am facing a big problem...I have created WebDynpro Application & when I am running that application from WebDynpro, it's showing the page but giving me the error message as:-
    Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA - Model: class com.bcone.bcool.musa.model.MUSABAPI. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    What do I do? what connections I have to check?
    pls help.

    Hey if you are connecting to SAP system making use of adaptive RFC model you hav to create logical systems(JCOs).So while creating the model you have to specify 2 logical system names(one for model data or on for the meta data).If you have not created the JCOs or if the JCOs are not active  then you are going to get this type of error.To activate those JCOs ask your administrator to activate the JCO for metadata of your application.If you are having proper credentials then log on to portal
    System administration>webdynpro>expand the local directory>select your project>click on maintain JCOs and activate the JCO for the metadata.
    Or else change the logical system in your application.

  • Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST

    Hi ,
    I am getting the below error:
    Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.eligibilitymodel1.EligibilityModel1. The SSO ticket needed for authentication to WD_MODELDATA_DEST has expired. Close all applications and logon anew!
    Regards
    Anumit

    Anumit,
    when will you get this error?
    if you are getting this while using adaptive rfc model follow this link Could not create JCOClientConnection for logical System:
    if it doesnot work
    try to reimport the certificate or restart the server
    Thanks
    Bala Duvvuri

  • Could not create JCOClientConnection for logical System:

    Hi,
    I am facing a wierd problem in using the JCO destinations.
    I created a page where it is using some JCO destinations say SAP_R3_HumanResources.
    when i open the page it is working for the first time .without closing the page if i open the same page again it is giving the following error
    Error connecting using JCO.Client: null
    Error connecting using JCO.Client: null
    Pernr:Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.swissre.CustomData. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Please let me know how to solve this issue
    Thanks
    Bala Duvvuri

    Hi Bala,
    It seems that this is a custom webdynpro application which when executed causes such problem.  This might be due to JCO connection not released back to the pool.
    Please refer to the following threads and that might be helpful. 
    Re: JCO Connection close
    How to close a model object connection for Adaptive RFC?
    You might have to call disconnectIfAlive method on your model.
    Regards,
    Jigar

  • Could not create JCOClientConnection for logical System: SAP_R3_HumanResour

    Hi,
    For all the standard ESS (sap.com) the JCo connection used is SAP_R3_HumanResources .
    All the applications are working fine.
    I am trying to add a test Component in one of the (sap.com~eepro) for testing a standard BAPI call for getting user details.
    I have used the same Model and the same SAP_R3_HumanResources destination name.
    But i get the following error when i try to execute the standard BAPI_USER_GETDetails (non - HR).The other applications for standard components (Vc ) work when i run the application.
    My question here is why a custom , local webdynpro when try to make a RFC call using the running already existing JCO connection throws such error.
    How could this be solved.Note the connection is running and working fine for all the ESS webdynpros!!
    Error:
    Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.test.hr.model.Test. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Your experience would be worthy enough.
    Regards,
    Swathi

    Hi Swathi,
    Here are some suggestions to trace down to the actual problem.
    1) First check if all users are having this issue. (All other applications working and only one application giving problem)
    2) If no, then take list of users having this problem and check their portal and SAP accounts
    3) If yes, then concentrate on testing the JCo connections and the user account mapped in JCo settings
    Possible things u can check is user's portal account (locked or not), SAP account (lock or validity), pernr mapped (validity), JCo user (check for lock), ping and test JCo connections
    If none of them are issue, check the logs if there are any trace for this issue. I believe there must be certainly one. That can help u going further.
    Regards,
    Harini S

  • JCOClientConnection for logical System

    Hello Experts,
    I get this error when i launch my HR application, can anyone inform wht i have to to correct this error. Currently the portal run on SP7.0 sp15.
    JCOClientConnection for logical System: HRSC_MODELDATA_DEST - Model: class com.infineon.hr.hrsc.formdatamodel.masterdata.MasterDataModel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Thank you
    BR
    Ramesh

    Hi,
    The error HRSC_MODELDATA_DEST saying that you haven't configured the JCo destination.
    To configure a JCo destination, login to portal ---> content Administration ---> WebDynPro Content
    Then click on "Maintain JCo Destinations" tab, there you can see all the available JCo destinations. Here you have to configure the required JCo destination.
    Note: If a JCo destination is not configured you can see a Red Color simbol and if it is configured you can see a Green color simbol......
    For Creating JCo destinations:
    http://help.sap.com/saphelp_nw70/helpdata/EN/6f/1bd5c6a85b11d6b28500508b5d5211/frameset.htm
    Regards,
    Srinivas.

  • 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

  • Couldn't create jco client connection for logical system

    Dear Experts,
    we are facing a strange issue in our custom webdynpro java application, few of our portal users are getting the "couldn't create jco client connection for logical system" for Model Data JCO Destination. below are details
    1. portal version 7.02 SP14 (we have recently updated to SP14 from SP02-- is this is causing the issue ?)
         1.1. updated the NWDI track with SP14 SCA files as well as added latest WD Runtime SCA file deployed the applications to Production also.
    2. above said exception is inconsistent and happening for only few users
    3. ping and test of jco destinations are successfull in content administration as well as in SLD, destinations were added in the SLD system.
    4. cleared the JCO ARFC meta data cache in webdynpro console
    5. jco destinations are configured using uid/pwd, configured user is not locked active and tested in the backend by logging in with the same user.
    6. restarted the portal server
    even though, we are getting the above said exception for few of portal users randomly.
    Please help me on this ASAP, as i am not getting any further help on this.
    Thanks,
    Ram.

    Hello Ram,
    Check the JCo Pool Configuration settings of your JCO Destination. This message normally comes when the maximum connections has been reached. Increase the "Maximum Connections" to some number depending on the usage. A good habit is to disconnect the jco connection after executing the same in your webdynpro code if you don't want it to be synchronous.
    <ModelName>.modelInstance().disconnectIfAlive()
    Hope this helps.
    Regards
    Vijay

  • JCO connection error:Couldn't create JCOClientConnection for logical System

    Hi All,
    We are facing a production outage issue.
      We have a Federated Portal Network setup where one of our producer goes down automatically (seems on heavy load).
      On this Producer server we have 3 Web Dynpro applications deployed and default trace is full with JCO connection error   saying Could   not create JCOClientConnection for logical System: CSVMR_WD_MODELDATA_DEST.
    We had issue with max allowed JCO connections so we changed the below mentioned parameters for JCO connection settings in portal:
    u2022     Minimum value of JCo Pool Size in total = 80
    u2022     Minimum value for CPIC_MAX_CONV per SAP Web AS = 320
    u2022     Maximum Number JCo Connections = 160
    Please let us know if we are missing on some settings, any help in this regard is appreciated.
    Regards,
    Priyanka

    Hi,
    As you have already increased the maximum number of connections/pool size but still you are facing this problem. I would suggest you to check the web dynpro application which might not be able to release/disconnect the JCO connection.
    Please check this [Thread|How to close a model object connection for Adaptive RFC?; for more details.
    Regards
    Puneet

  • 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

  • Difference between client system and logical system

    Hi all
    Can any one explain about the client system and logical system??
    When this message type will comes in to picture at the time idoc processing??
    Thanks and Regards
    Arun Joseph

    hi Arun,
    I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
    and to know the diffrence between client and logical system very keenly go thru this link
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
    IDOC Administration
    Step 1: Tcode: WE 46
    Setting the Global Parameter for IDOC Interface
    Step 2: Maintaing a Logical System
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Define Logical systems
    Go to Spro transaction
    Step 3: Allocating Logical systems to the Client
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Assign Client to Logical systems
    Go to Spro transaction
    Step 4: Setting up an RFC destination
    Tcode: SM 59
    Path: From the ALE Customizing in IMG, choose Communication, Define RFC
    Destination
    You can also do the Advanced Settings in the RFC Destination
    Step 5: The PORT definition
    TCode: WE 21
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Systems in Network, Asynchronous Processing, Assign Ports, Define Port
    Step 6: Generating Partner Profiles
    TCode: BD 82
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
    Step 7: Distributing the Model
    TCode: BD 64
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, Maintain Distribution Model and Distribute Views
    Technques for Distributing the Master Data:
    Technique 1: The Push Approach
    Executing the Process:
    TCode: BD 10
    Path: from the ALE Main Menu, choose Material Data Distribution, Cross
    Application, Material, Send
    Technique 2: The Change Pointer Technique
    Enable Change Pointers Globally
    TCode: BD 61
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers
    Enable Change Pointers Globally
    TCode: BD 50
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers for Message Type
    Specify the Fields for which Change Pointers are to be written
    TCode: BD 52
    Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
    Change-Relevant Fields
    How the Classification system works:
    Creating a Class Type
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Status for the Class Types:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classification Status:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classes:
    TCode: CL 01 (it is zero)
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
    Allocating classes to the Logical Syatems
    TCode: BD 68
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Assign classes
    to Logical systems
    Filering at the IDOC level:
    Identify the Filter Object:
    TCode: BD 59
    Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
    Type to IDOC Field
    Modify the Distribution model
    How Segment Filtering Works:
    Configuration:
    Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
    TCode: BD 56
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
    The Reduced IDOC Type:
    The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
    The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
    represented by a forward slash(/) in the field.
    TCode: BD 53
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
    Create Reduced Message Type
    IDOC:
    Complete Documentaion on any IDOC using TCode: WE 60
    IDOC Display Tool: TCode: WE 02 or WE 05
    IDOC DEfinition components:
    Segment Components:
    1. Segment Type (E1, Z1)
    2. Segment Definition(E2, Z2)
    3. Segment Documentation(E3, Z3)
    E- SAP Defined
    z- Custom Defined
    IDOC runtime componets:
    control Record:
    Data Record:
    Staus Record:
    First Create the Segments using TCode: WE 31
    and then create the IDOC using TCode: We3 30
    first release the segments and then IDOC.
    Creating a new Basic IDOC Type:
    STEP 1: Analyze the Data:
    STEP 2: Create Data Elements:
    STEP 3: Create Segments:
    STEP 4: Create Basic IDOC Type:
    1. Execute TCode: WE 30
    2. Select the Create new option and enter a description for your basic IDOC type
    3. click the IDOC name, and click the create icon.
    Enter the segment type and its attributes.
    4. Keep on adding the segments as in step 3.
    5. Save the basic IDOC type
    Step 5: Release the Segment Type and Basic IDOC Type
    STEP 6: Transport the Segments and Basic IDOC Type
    Extending a Basic IDOC type:
    STEP 1: Analyze the Data:
    STEP 2: Create Custom Segments:
    STEP 3: Create the IDOC Type:
    STEP 4: Release the custom Segment and IDOC Extension
    Develop the function module for fteching the Data and then inserting the data into IDOC using
    EDIDD(for control Record) and EDIDC table(for DATA Record)
    Configuring the Systen for IDOCs
    Configure an Outboubd Process that uses Message Control
    Step 1: Create a new Message Type
    TCode: We 81
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 2: link the IDOC type to the Message Type
    TCode: We 82
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 3: Create a new Process Code
    TCode: We 41
    Path: From the Area menu of EDI, choose Control,Outbound Process COde
    Step 4: Create or Change a Partner Profile
    TCode: We 41
    Path: From the Area menu of EDI, choose IDOC,Partner Profile
    Configure an Outboubd Process for Stand-Alone Programs
    1. Create a new message type
    2. Link the IDOC type to the Message Type
    3. Add the message to the ALE Distribution Model(use BD 64)
    4. Create or change the Partner Profile
    go through the following site to have screen shots.
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    thanks
    karthik
    reward me points if usefull

  • CHARM activation check failing on "consolidation system for development system SSA-200 in project ZTEST2

    Hello,
    We are implementing Charmlite and want to activate in project landscape.
    We are Solution Manager 7.1 SP11 and testing this scenario in sandbox.
    Steps completed:
    1. in sandbox domain controller, created two virtual systems and made 3 system landscape, where, I can release the transport and see it in QA system (Virtual system buffer)
    2. The LMDB has been updated with Virtual system and in SMSY, the entries of virtual system shows up. The logical components have the client information.
    Issue:
    in /nsolar_project_admin ->System landscape -> change management, When consistency check is performed, we get error message saying
    Virtual RFC is miising (I am guessing, it should be okay)
    The logical component is incosistent (This might be the reason the CHARM is not getting activated.
    "No consolidation system for development system SSA-200 in project ZTEST2
    No track for project ZTEST2 with log. system SSA/200"
    For me, when i look in satellite system, the consolidation system is a virtual system and it should be fine.
    Please advise
    Regards,
    Durga PK Saitana

    Thank you Karthik. Still the problem persists
    I went through the blog earlier. I created l ABAP instance manually in SLD and moved into LMDB and can see the entry in SMSY. (I did not see any option of putting  virtual flag)
    We were trying harmonization of RFC from note 1384598 and since we had virtual systems, went with domain links.
    After domain links, the virtual systems are read. the Dev ABAP system is not able to find the consolidated system. In the satellite system, I can release transport and move the transport.
    Not sure, why this issue is persistent.

  • Changing the data in DataSource in R/3 System for Project System

    Can we change the data of DataSource which is extracted from R/3 sYSTEM for Project System Module?

    Hello Rajesh,
    You can modify it in PSA. Or write the routines or rules logic as per your requirement.
    Could you please elaborate more on what kind of changes you are interested for.
    San.

  • Diffebetween Business system and Logical system...

    what is the difference between Business system and Logical system...

    Hi
    Business system is a logical layer needed for configuration in integration directory. On the other site technical system is physical representation of your technical landscape. In case of SAP technical systems you can have more than one business system relation. In that situation there is relation one client to one business system.
    If your technical system changes, then you definitely need to point this new technical system to the existing Business system which has been used to do all the Configurations in the Integration Builder.
    Re: business system
    Re: business system
    Thanks

  • Business system for legacy system

    hi guys,
    Can we create  business system for legacy system ?If yes what is the use?
    satya reddy

    Hi,
    Yes you have to create Business system for legacy systems..
    It may be the Standalone java . or Third party system..
    When you are doing some POC or such type of things create Business Services
    also..
    A business service represents an abstract unit for addressing message senders and message receivers. You can use a business service to group interfaces.
    It is useful to use business services when configuring cross-company processes. Usually, the interface descriptions of the business partners involved are made publicly available. The system landscape is only partly known, however.
    See the below links..
    http://help.sap.com/saphelp_nw04/helpdata/en/ae/e3bd4f6b61e146ad1384954ecabb41/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ae/e3bd4f6b61e146ad1384954ecabb41/frameset.htm
    Regards
    Chilla..

Maybe you are looking for