Prob in distributing the model

Hi
Being done with the initial steps, I created the distribution model
When i distribute that , i get the error stating "Communication error , function xxxxxxxxxx is not available".
Due to what reson this error could be? Kindly elaborate .
Thanks

Hi,
1.Check in the SM59.That error due to the RFC destination is not correctly assigned.
2.Check both sides in outbound and inbound.
Regards,
Kumar(Reward if helpful).

Similar Messages

  • IDoc to IDoc scenario: distribute the model view

    Hi!
    I try currently to  configure a IDoc to IDoc scenario for SAP ECC 6.0 system with following business 2 systems:
    ERP:100 (Sender)
    ERP:200 (Receiver)
    and XIB:100 (XI system)
    I successfuly created  a message type and generated the model view in tcode BD64.
    Question:
    When I try to distribute the model view which system should I choose?
    a) XI System or
    b) Receiver system ERP:200
    When  I choose the receiver system ERP:200 and get the following error
    Target system: ERP:200
    Model view ECCCLNT100 has not been updated
    Reason: Distribution model is currently being processed
    When I try to choose my XI system I get the following error:
    Target system: XIB:100
    RFC destination for synchronous communication (message type SYNCH)
    Partner profile LS PIBCLNT100 SYNCH does not exist
    Generate partner profile
    or specify outbound partner profiles for message type SYNCH
    Is that an error? If yes, how can I fix them?
    Thank you very much
    Thom

    Hi
    Look my reply on this thread regarding SYNC Message Type.
    Re: problem while distribute model view
    When I try to distribute the model view which system should I choose?
    a) XI System or
    b) Receiver system ERP:200
    You are sending IDoc to XI then R/3 so select XI system. because receiver of IDoc is XI then IDoc would be send from XI.

  • Error - Distributing the Model using BD64

    Hi! All
    Not able to distribute the model from the Sender System.
    Error : Model view ZDMKANBAN has been changed
    While Generating the Partner Profile able to generate Partner, Port, Outbound parameter from the Sender System.
    but if i execute an IDOC through WE19 able to get the Status - 03 for Sender System & Status - 53 for Receiver System
    when i try to transfer IDOC from Sender System to Receiver System could not do it.
    Hope so bz of error occurred in Distribution Model. Is it So
    kindly help me.

    you have to distribute the distribution model in its new version

  • Error in Distributing the model view

    Hi,
    I have clients 600, 610 & logical systems (ls_600, ls_610) in the same system.
    I am trying to set up the ALE customizing and distribute the model view.
    I have created RFC from 600 to 610 and the test connection is fine.
    I have created a model view in which i have given sender system as LS_600 and
    receiver system as LS_610 and the message type as MATMAS.
    In the partner profile(WE20) of LS_610(client 600), in the outbound parameter SYNCH
    i have given a port which uses the RFC to 610.
    When i have tried to distribute the model view it is giving error as
    'communication error occured.  Username or password is not correct (Repeat Registration).'
    I am not able to figure out the error.
    There is also a partner profile as ls_600. Do i have to
    make any changes there ?
    Do i have to do something in the client 610 ?
    Your help is highly appreciated.
    Thanks,

    Hi Prasad,
    Please maintain the MATMAS & SYNCH Message type in the Outbound partner profiles of LS 610.
    Test distributing the MATMAS IDoc's using BD10 without even maintaining Distribution Model.
    And let me know if you are able to distribute the IDoc or not.
    If you get the error. Please let me know the error.
    Regards,
    Krishna

  • Unable to distribute the MODEL to backend system in SRM 5.0

    Hello Experts,
    I have created distribution model " SRM_to_R3" in BD64, maintained message types BBPCO, BBPIV and MBGMCR
    Every time I try to Distribute this MODEL to back end system I get the following error in IDES system
    Target system T90CLNT090       Commnunication error occurred, error when opening an RFC connection
    RFC connections are
    T90CLNT090   - SRM to R3
    SRM_00_800   - R3 to SRM
    Systems got connected successfully and I can "Remote Logon" too......
    My query is why am not able to send or distribute the MODEL from SRM to ECC backend system ?
    How to get rid of the error and successfully distribute MODEL to backend system.........appreciate your help in this regard
    Rgds !
    SAP Novice

    Hi Zuljana,
    Kindly check if your partner profile is active. (Indicated by 'A')
    Sometimes if your partner profile is not active, you wont be able to distribute your model. Check the 'A' indicator
    Regards,
    Nikhil
    Edited by: Pbponikhil on Dec 21, 2010 4:11 PM

  • WhAT Is distributing the model

    Hi All
    Can anybdy plzz explain me what do we mean when we say we distribute the distr model in bd64?

    Hi
    The distribution model describes the ALE message flows between logical systems.
    <b>Use</b>
    You can specify the relationships between logical systems, message types, BAPIs and filters in the distribution model. Applications and the ALE layer use the model to determine receivers and to control the data distribution.
    <b>Structure</b>
    In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
    The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views.
    The relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.
    Hope this helps.
    Regards
      Sumit Jain
    **Reward with poitns if useful

  • Error while distributing the model

    Hi
    I am not able to successfully distribute my model thru BD64. I am getting the error msg as ' the model has not been updated'.The configuration done till now is according to the basic procedure.
    Can anyone please suggest a way to overcome this error.
    thanks

    Hi,
    You can create a distribution model and then add message type to it; however, there are some preconditions which you need to ensure before you create the model.
    Preconditions:
    1) Ensure that you have the message type in both the systems; if custom msg type is used, you need also to create the one in the partner system.
    2) Do all configuration related to msg type, idoc type, etc in your partner system as well
    3) Create RFC destination in the current system for your partner system... and test the connection if it is working fine
    After you create the model and added msg type to it, you also need to do the following:
    1) Go to Edit --> Model View --> Distribute to distribute/ create it in your partner system
    2) To validate, you can check in your partner system if the model is automatically created there
    3) Then create Partner profile in both the systems by going to Environment --> Generate Partner Profiles
    Hope it helps and solves your problem.
    Regards, Tapas
    <Pls award pts if useful or answered>

  • Not able to distribute the model

    Hi
    I created a model using BD64 according to the procedure to the best of my knowledge. But i am getting the following error
    "Model view has not been updated. Reason: the distribution model is currntly being processed."
    Nobody else are logged in. Can anybody say what the prob might be and how can that be solved

    hi
    check this link
    [Re: getting problem while creating the dist model in bd64|Re: getting problem while creating the dist model in bd64]
    Thanks& Regards
    Nagesh.Paruchuri

  • Error in distributing the Model View in BD64

    Hi Experts,
    I have some problem in distributing model view in BD64. please see here the error details:
    Model view <logical client> has not been updated
    Reason: No authorization to create model view <logical client>
    .....authorization object B_ALE_MODL
    .....Parameter: activity 01, model view <logical client>
    i have created full auth and B_ALE_MODL role for the specific account but still i cant proceed.
    Please help.
    Thank you,
    Tony

    Hi Experts,
    In addition, this is in line with our integration between SRM 7.0 EHp1 SPS05 and ECC 6.0 EhP4 SPS03. both systems are running in windows 2003 64bit.
    Edited by: Tony on Aug 3, 2011 4:30 AM

  • Cannot distribute ALE model

    I've gone through the steps to create a model view, message types and generate the partner profiles in my SRM system. When i try to distribute the model to the backend, I get the follwing error:
    Model view XXX has not been updated             
    Reason: No authorization to create model view XXX
    ..... authorization object B_ALE_MODL           
    ..... Parameter: activity 01 , model view XXX   
    Can anyone tell me what that means?
    Thanks,
    SN

    Hi ,
    It means that your ALE user that is used to connect to the backend does not have all the authorization required to replciate the ALE model.
    B_ALE_MODL is missing.
    Please add this object to the ALE user and test again.
    Kind regards,
    Yann

  • Error while distributing customer  model

    hi,
    i am getting the following error when i am trying to send data between two R/3 systems using distribution model
    i am unable to distribute the model to the other system
    Error:
    "Target system is an external System. It does not support this function."
    even after successfully generating partner profiles i am getting this error.
    could someone help me out with this problem

    Hi Siddharth
    Can you please update about all the ALE setting that you have done before trying to distribute the model to the other system.
    And whether you have put correctly - the sender and receiver while creating the distribution model. And, most importantly the partner profiles?
    Please update..
    Regards
    Ashish

  • Related to  distribution the model view

    hi
    When we try to distribute the model view, we get an error 'Model View has not been updated. Reason : Maintenance systems for model view D-HR-MD are not identical...Maintenance system in sending system D-OFS-HR.....Maintenance system in receiving system DH3-500' .
    What is being referred to as the maintenance system here? Are we missing out on something?

    Are you created distribution model for the correct Logical systems. Check it once.

  • Error while distributing the ALE distribution model through BD64

    Hi,
    I am getting the error while distributing the distribution model through BD64. The error is as follows:
    "Model view DVGDVH has not been updated
    Reason: the following ALE connection already exists in model view TESTMOD".
    What does this means?
    Regards,
    Soumya.

    Dear Sapera,
    I faced the same problem last night.
    We just manually deleted the distribution model from receiving system.
    Log on to receiving system => BD64 => change/dispay => edit => delete => Save.
    Once deleted log in to sender system and then select model and distribute again.
    by performing this we were able to resolve this issue.
    Warm regards,

  • Using the Model Facade Pattern in a Java EE 5 Web application

    Hi,
    Yutaka and I did a Tech tip
    http://java.sun.com/mailers/techtips/enterprise/2006/TechTips_Nov06.html#2 on using a model facade pattern in Java EE 5 web-only applications recently. We got some questions about it, and these were some of the questions raised...
    Question 1) the first part of the tech tip(it has two articles in it) http://java.sun.com/mailers/techtips/enterprise/2006/TechTips_Nov06.html showed how to access Java Persistence objects directly from a JSF managed bean, is this a good practice?
    Question 2) when to use a facade(as mentioned in the second part of tech tip) ?
    and maybe
    Question 3) why doesn't the platform make this easier and provide the facade for you?
    Briefly, I will take a shot at answering these three questions
    Answer 1) You can access Java persistence directly from your managed beans, but as your application grows and you start to add more JSF managed beans or other web components(servlets, JSP pages etc) that also directly access Java Persistence objects, you will start to see that you are cutting/pasting similiar code to handle the transactions and to handle the Java Persistence EntityManager and other APIs in many places. So for larger applications, it is a good practice to introduce a model facade to centralize code and encapsulate teh details of the domain model management
    Answer 2) IAs mentioned in answer 1, its good to use a model facade when your application starts to grow. For simple cases a spearate model facade class may not be needed and having managed beans do some of the work is a fast way to jumpstart you application development. But a facade can help keep the code clean and easier to maintain as the aplication grows.
    Answer 3) First note that both of the articles in the tech tip were about pure web apps(not using any EJBs) and running on the Java EE5 platform. Yes it would be nice if a facility like this was made available for web-only applications(those not using EJBs). But for web-only applications you will need to use a hand-rolled facade as we outlined in the tech tip. The Java EE platform does provide a way to make implementing a facde easier though, and the solution for that is to use a Session Bean. This solution does require that you use ythe EJB container and have a Session Bean facade to access your Java Persistence objects and manage the transactions. The EJB Session Facade can do a lot of the work for you and you dont have to write code to manage the transactions or manage the EntityManager. This solution was not covered in this tech tip article but is covered in the Java BluePrints Solutions Catalog for Perssitence at
    https://blueprints.dev.java.net/bpcatalog/ee5/persistence/facade.html in the section "Strategy 2: Using a Session Bean Facade" . Maybe we can cover that in a future tech tip.
    Please ask anymore questions about the tech tip topic on this forum and we will try to answer.
    hth,
    Sean

    Hi Sean,
    I'm working on an implementation of the Model Facade pattern where you can possibly have many facades designed as services. Each service extends a basic POJO class which I'm calling CRUDService: its short code is provided below for your convenience.
    The CRUDService class is meant to generalize CRUD operations regardless of the type of the object being used. So the service can be called as follows, for example:
    Job flightAtt = new Job();
    SERVICE.create(flightAtt);
    Runway r = (Runway) SERVICE.read(Runway.class, 2);
    Employee e = (Employee) SERVICE.read(Employee.class, 4);
    SERVICE.update(e);
    SERVICE.delete(r);SERVICE is a Singleton, the only instance of some service class extending CRUDService. Such a class will always include other methods encapsulating named queries, so the client won't need to know anything about the persistence layer.
    Please notice that, in this scenario, DAOs aren't needed anymore as their role is now distributed among CRUDService and its subclasses.
    My questions, then:
    . Do you see any obvious pitfalls in what I've just described?
    . Do you think traditional DAOs should still be used under JPA?
    . It seems to me the Model Facade pattern isn't widely used because such a role can be fulfilled by frameworks like Spring... Would you agree?
    Thanks so much,
    Cristina Belderrain
    Sao Paulo, Brazil
    public class CRUDService {
        protected static final Logger LOGGER = Logger.
            getLogger(Logger.GLOBAL_LOGGER_NAME);
        protected EntityManager em;
        protected EntityTransaction tx;
        private enum TransactionType { CREATE, UPDATE, DELETE };
        protected CRUDService(String persistenceUnit) {
            em = Persistence.createEntityManagerFactory(persistenceUnit).
                createEntityManager();
            tx = em.getTransaction();
        public boolean create(Object obj) {
            return execTransaction(obj, TransactionType.CREATE);
        public Object read(Class type, Object id) {
            return em.find(type, id);
        public boolean update(Object obj) {
            return execTransaction(obj, TransactionType.UPDATE);
        public boolean delete(Object obj) {
            return execTransaction(obj, TransactionType.DELETE);
        private boolean execTransaction(Object obj, TransactionType txType) {
            try {
                tx.begin();
                if (txType.equals(TransactionType.CREATE))
                    em.persist(obj);
                else if (txType.equals(TransactionType.UPDATE))
                    em.merge(obj);
                else if (txType.equals(TransactionType.DELETE))
                    em.remove(obj);
                tx.commit();
            } finally {
                if (tx.isActive()) {
                    LOGGER.severe(txType + " FAILED: ROLLING BACK!");
                    tx.rollback();
                    return false;
                } else {
                    LOGGER.info(txType + " SUCCESSFUL.");
                    return true;
    }

  • Need suggestion for ISE distributed deployment model in two different data centers along with public certificate for HTTPS

    Hi Experts,
    I am bit confused about ISE distributed deployment model .
    I have two data centers one is DC & other one is as a DR I have  requirement of guest access service implementation using CWA and get public certificate for HTTPS to avoid certificate error on client devices :
    how do i deploy ISE persona for HA in this two data centers
    After reading cisco doc , understood that we can have two PAN ( Primary in DC  & Secondary in DR ) like wise for MnT (Monitoring will be as same as PAN ) however I can have 5 PSN running in secondary i.e. in DR ISE however I have confusion about HA for PSN .. since we have all PSN in secondary , it would not work for HA if it fails
    Can anybody suggest me the best deployment solution for this scenario ?
    Another doubt about public certificate :
     Public Certificate: The ISE domain must be a registered or part of a registered domain name on the Internet. for that I need Domain name being used from customer .
    Please do correct me if I am wrong about certificate understanding :
    since Guest will be the outside users , we can not use certificate from internal CA , we need to get the certificate from service provider and install the same in both the ISE servers
    Can anybody explain the procedure to opt the public certificate for HTTPS from service provider ? And how do i install it in both the ISE servers ?

    Hi there. Let me try answering your questions:
    PSN HA: The PSNs are not configured as "primary" or "secondary" inside your ISE deployment. They are just PSN nodes as far as ISE is concerned. Instead, inside your NADs (In your case WLCs) you can specify which PSN is primary, which one is secondary, etc. You can accomplish this by:
    1. Defining all PSN nodes as AAA radius servers inside the WLC
    2. Then under the SSID > AAA Servers Tab, you can list the AAA servers in the order that you prefer. As a result, the WLC will always use the first server listed until that server fails/gets reloaded, etc. 
    3. As a result, you can have one WLC or SSID prefer PSN server A (located in primary DC) while a second WLC or SSID prefer PSN server B (located in backup DC)
    Last but not the least, you could also place PSNs behind a load balancer and that way the traffic would be equally distributed between multiple PSNs. However, the PSN nodes must be Layer 2 adjacent, which is probably not the case if they are located in two different Data Centers
    Certificates: Yes, you would want to get a public certificate to service the guest portal. Getting a public/well known certificate would ensure that most devices out there would trust the CA that signed your ISE certificate. For instance, VeriSign, GoDaddy, Entrust are some of the ones out there that would work just fine. On the other hand, if you use a certificate that was signed by your internal CA, then things would be fine for your internal endpoints that trust your internal CA but for any outsiders (Guests, contractors, etc) that do not trust and do not know who your internal CA is would get a certificate error when being redirected to the ISE guest portal. This in general is only a "cosmetic" issue and if the users click "continue" and add your CA as a trusted authority, the guest page would load and the session would work. However, most users out there would not feel safe to proceed and you will most likely get a lot of calls to your helpdesk :)
    I hope this helps!
    Thank you for rating helpful posts!

Maybe you are looking for

  • List of Export Excise Invoice Created.

    Hi Gurus, I wanted to know any transaction code or report(standard) avaialble to differenctiate between an local excise invoice and export excise invoice generated. I have tried using T. Code : J1I7

  • Can I update a  Mac 10.5.8 to 10.6 or later

    can I update a  Mac 10.5.8 to 10.6 or later????

  • NPE when calling getConnection() with JBoss 3.0.0RC1

    I'm getting the following exception only when I'm using JBoss 3.0.0RC1. No problem with earlier version of JBoss 3.0, so this maybe a JBoss issue. However, I can't debug this without knowing what URL Kodo is trying to look up. My guess is getTransact

  • Part of photo attachments  is grey

    when i receive a photo attachment the most part of the photo is grey i am using 10.7.5. Is there a way i can fix it? thanx

  • IPhone and IOS5.1

    I just updated my laptop (and for that matter the iPad2) with IOS5.0.  My iPhone3G has not been updated since last year when I changed my laptop for fear of losing my precious Contacts.  I would like to update my iPhone 3's.ver 4.3.5 to IOS5.0.  Trou