Generate Distribution Model ERP = EWM

HI
I am performing Generate Distribution Model ERP => EWM for new WH. Getting below error message.
Method BUS2015.SAVEREPLICA exists in model view WMS
Message no. BDDISTMODEL051
Please Help to resolve as early
Rgds
Dinesh.P

Hi Dinesh,
When you are trying to Generate Distribution Model for your warehouse that time there are three fields one of those is your ERP warehouse number and Second is Logical System of EWM and third one is Distribution Model view. You might have entered a wrong model view name and then you tried to execute, system is giving you error that ".... method exists in model view WMS" that means you need to enter WMS model view in third field and then execute with radio button selected CREATE ENTRIES along with BOTH radio button selected.
Thanks and regards
Anoop Singh

Similar Messages

  • Error while generating Distribution Model in ERP to EWM

    I am trying to generate new distribution Model from ERP to EWM for my warehouse.
    In system one distribution Model already exists for another warehouse. Below error encountered.

    Hi Suraj,
    Thanks for the answer
    Yes i was using the Wrong Distribution Model , I should have selected EWM , but i was giving some new name as i thought that was required. Hence message came.
    I did with EWM distribution Model and all worked well.
    Thanks
    Inder

  • Distribution model of cep load generator

    Hi guys,
    Do you happen to know the distribution model (eg. Poisson ,uniform...) of Oracle CEP load generator?
    Cheers,
    Alireza

    Seems there is no documentation for this.
    My curve fitting experiment shows it does not follow a particular distribution. For example for rate 100 tuple per second the distribution model is t location-scale for some queries, whereas for rate 50k and 100k the distribution is more fit to Weibull and generalized extreme value distribution.
    I just wanted to insert some pics here but the system gives me error. Anyway, this is the answer.

  • ALE Distribution model view

    Hello
    I am setting up an ALE scenario to send idocs from system A to system B. I have a problem with the distribution model view. The model has been distributed to the receiving system with the wrong basic idoc type entered in the partner profile. I would like to know how I can change the model view and re-distribute it.
    Thanks,
    A.P.

    Hai
    Go through the following Procedure
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode  BD64 ? Create Model View
    Tcode  BD82 ? Generate partner Profiles & Create Ports
    Tcode  BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    I know how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
            save and goback.
    2) Tcode BD50--->  check the MATMAS check box save and comeback.
    3) Tcode BD51--->  goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52--->  give message type : matmas press ok button.
       select all  what ever you want and delete remaining fields.
       save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
       it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
       give Message type : MATMAS and Executte
    ALE/IDOC Status Codes/Messages
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    Regards
    Sreeni

  • Error in inbound delivery replication ERP - EWM

    Hi,
    We have recently installed SAP ERP 6 EhP 6 and EWM 7.0 Ehp2 Add-On
    Now, we are not being able to replicate Inbound Delivery from ERP to EWM.
    As we save the ID in ERP we are getting a message that the ID has been distributed.
    But the document is getting stuck in the RFC queue.
    In SMQ2 the particular queue gets the status "SYSFAIL" with the error message "Function module does not exist or EXCEPTION raised. Message no. SY359"
    The function module field contains "/SCWM/INB_DLV_SAVEREPLICA" 
    The status message says: "CREATE DATA: The document /1DF/_PDI000 is no... "
    I've properly defined the standard BAPI destination and I've checked note 1398474.
    Please help me get out of this mess.
    Regards,
    Oritra

    Hi Oritra
    As per my knowledge I haven't see this issue and table you are asking are not found as requirement in system without which delivery is able to replicate in EWM.
    Also try to create new delivery in ECC and send... As you was checking in SMQ2 it means
    "The status message says: "CREATE DATA: The document /1DF/_PDI000 is no..." it means after sending your delivery from ECC it is coming to back to the system where you are checking inbound queue and trying to create delivery.
    That time it find NO range for delivery , so see  number range assignment or number range maintenance and refusing to create delivery.
    so update Number range and assignment properly for ID in EWM system and check new flow.
    if resolved dont see below points.
    please provide more infrmation of below error from SLG1. keep some extra selection time zone.
    1. Do you have same or different client. As per above your description my understanding was same client (ECC and EWM).
    If you have different client then your ECC WM parameter under EWM interface makes ur delivery move to EWM system with distribution model created with BAPI replica.
    As I do not have ur system my second option will be try to check above setting and if not try to push in debug mode to see proper code.
    As per my knowledge I haven't see this issue and table you are asking are not found as requirement in system without which delivery is able to replicate in EWM.
    Regards
    Suraj

  • How to restrict the idoc creation based on the distribution model

    Hi all,
    I want to create the idocs for certain material types only, for this i configured Distribution  model and set the filter for material types.
    If the delivery is created with the material type which is not in the filter means,
    Idoc is creating for that Delivery with header segments only and restricting Item level segments.
    it is coming to XI and failing in mapping every time.
    I do not want to generate the whole idoc itself. Am i missing any thing??
    Regards
    Edited by: Suman gupta on Jun 10, 2010 11:13 PM

    Hi Mike,
    >>config in PI in the routing condition - if no lines exits don't send the message to the mapping/receiver
    If no lines exists we can restrict don't send to receiver, but how can we restrict dont send to mapping??
    It comes to mapping and failing in PI MONI.
    Is there any way that i can restrict the Idoc generation itself in ECC ??
    Regards

  • R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

    Hi All,
    I have a very basic question regarding Distribution model.
    My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
    I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
    Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
    Thanks
    Shirin

    Hi,
      if you create partner profiles and port via t.code.
      i hope, it's not required to maintain Distribution model.
      please check the below points.
    Configuration Steps for Idoc to File Scenario.
    This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
    To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
    STEP 1:ALE SETTINGS IN SAP-XI
    We need to do the following settings in XI
    1) Create an RFC Destination to the Sending System in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code IDX1
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client
    d) Enter the RFC Destination created in SAP R/3 towards other system
    e) Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1
    SETTINGS IN SAP R/3
    We need to do the following settings in R/3
    Logon to Sap R/3 System
    1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
    a) Create RFC Destination using T.code in SM59.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both must be succesful
    2) Create communication Port for Idoc processing Using Transaction(We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile with Outbound Parameters (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang
    Then Save
    e) Select Partner no. and LS which were create above
    f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g) Select Message type
    h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
    I) save
    4) In Transaction SALE, Create Logical System
    a). Go to Basic Settings-> First Define logical systems
    and then assign logical systems
    b) Double click on Define the logical systems
    c) Give data for your Logicaal System and Name
    d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e) Assign the logical system name to the client
    5) Create Customer Distribution model in the transaction code BD64
    1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3) Save the Distribution model
    Generate Partner Profiles
    Click on Menu Item u2018Generate Partner Profilesu2019
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4) Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
    Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
    warm regards
    mahesh.

  • ALE Distribution Model

    Hi,
    I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movements and the IDOC's were generated but they were not sent to the FI system. We've a look at tRFC and an error concerning user or password invalid appears, so i define again the user comunication and after a few adjustments to the model view we distribute it again to the FI system. When i execute it the following message appears : <b>Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.
    </b>
    Next step we delete the model view and created it again but the same error still remains.
    Can anyone help me ???
    Thanks is advance.
    JMMatos

    Hi
    Distribution Model – A model that describes the ALE message flow between logical systems.
    Applications and the ALE distribution service layer use the model to determine receivers and to control the data distribution. The relationships between logical systems, message types, BAPI’s and filters are defined in the distribution model.
    Ex: The screen shot depicts customer distribution mode ALE_TRNG_Mar07.
    Sender Logical System – EC1CLNT800
    Receiver Logical System  – SALES
    Message Type – CREMAS
    No filter conditions defined.
    This configuration step allows the installation of core ALE features on which data transfer activity will be based.
    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
    After creating the distribution model – the model needs to be distributed to the receiver system.
    Partner profiles need to be generated in both sender and receiver systems using transaction BD82 (automatically) or WE20 (manually).

  • Problem with IDoc filtering in the distribution model

    Hello Experts,
    We are using a distribution model in which we have set filters as like the following
    Filter Group 1
               Plant : XYZ
               Sales Org: SAP1
    As far as the documentation says this Condition should work with AND logic between Plant and Sales Org
    (i.e ~ Plant XYZ and  SO SAP1 ) but the IDoc gets created even if any one of the condition is met(looks like working in OR logic).
    How to achieve the AND filtering between the different objects.
    Would appreciate your kind help.
    Thanks in advance.
    RGds,
    Vasanth.

    > Jakub ~ Yes I checked the generated IDocs(classified pertaining to my Model)for my model alone and that's where we are facing this problem
    So that's the filtering problem.
    I would check in which segments are the "filtering objects" located (BD59) and whether it is a mandatory segment. If it is a mandatory segment - IDoc should not be created. If it is an optional segment - this segment and its subsegmets will be filtered out - but IDoc will be created.
    > ~ Do we need to apply some SAP Notes to avoid this problem ?
    >  But why the filter should behave in OR fashion ? I do not understand.
    I believe that Sachin meant that the logic is:
    Filter Group1 OR Filter Group 2 OR ... Filter Group N
    Filter Group 1 Object 1 AND Filter Group 1 Object 1 ... AND Filter Group 1 Object M
    Filter Group 1 Object 1 Value 1 OR Filter Group 1 Object 1 Value 2 OR ... Filter Group 1 Object 1 Value L
    regards,
    Jakub

  • Error On Distribution Model in the Backend

    Hello,
    I'm customizing our SRM and Backend to work together.
    I'm in the part Distribution Model. It works on SRM but on my backend, when I want to "Generate Partner" I have a message "No messages have been defined for the selection conditions in the model" and nothing is done.
    I don't know why...
    I don't know if it is link but me RFC connexion that I created on SRM to link to the backend name for example ABC_020 and in the backend is one RFC is ABCMAND020. doesn't it matter if they don't have the same name?
    Thanks in advance.
    If someone has a cookbook or documentation about SRM can you please send me at "[email protected]"
    Thanks twice.

    Hi Eileen,
    We have observed that without local RFCs i.e.
    SRM to SRM
    R/3 to R/3
    the business objects (matl/services) don't get replicated as you can not configure the Middleware sites in SMOEAC.
    Don't know whether it will help for Distribution model but worth trying
    BR
    Dinesh
    <b>Reward if helps</b>

  • How to maintain Customer distribution model in ALE

    hi FRIENDS..
      i wish to know what will be the transaction code of maintaining the customer distribution model, and how we maintain it.  and also distribute custome model in IMG sreen... please reply me...i will surely award you  nice points....
    bye...
    naim

    U can create/maitain distribution model using BD64.
    Or else u can create it using SALE transaction code.
    U need to give sender/reciver/msg type.
    ==============================================
    procedure:
    click on Create Distribution model button-->give the technical name
    select the DModel Technical name>add msgtype>
    it will ask sender/reciver/msgtype.
    pass those parameters and generate partner profiles through environment menu
    =================================
    to distribute a model view to partner syste,:
    Select mview
    edit>modelview>distribute
    Message was edited by: Eswar Kanakanti

  • ALE-manual configuration of the customer distribution model

    DEAR EXPERTS
    how do i manually configure the customer distribution model

    hi ,
    to maintain or configure the customer distribution model (CDM)
    go to tcode BD64.
    give the sender address -
    you have to mention the logical system name of the sender system. if u r sending one version to other then you have to specify  the sender system address,
    give the receiver address--- same as  above but mention the details of receiver system.
    meaintain the message type--- depends upon the type of applicaiton using like MATMAS or ........
    do the same procedure again in the reverse way to transer the information from one system to other system and vice versa.
    next step is to generate partner profiles.
    BD82 is the tcode for it
    next distribute CDM.
    thats it.
    If u find it useful mark the points
    Regards,
    GNK.

  • Error in IDOC Distribution Model

    HI all ;
    Please Help me in this Issue!!
    am  working with standard IDOC  Using MATMAS (Material Master Transfer)
    LS_800 - Outbound.
    LR_810 - Inbound.
    --> BD54.
    --> SCC4.
    -->SM59.
    -->WE21.
    -->WE20.
    --> WE20 ( in inbound side) Clear Up to this level.
    After that the Problem in Distributing the Model,,,,
    In Bd64 t-code Distribution Model.
    while Generating the Partner Profiles in BD64 ;
    its giving the blank message like below.
    No message has been defined for the selection conditions in the model.
    when we distribute(in BD64) 2 Errors (red) Like Below;
    RFC destination for Syncronous Communication (Message type SYNCH)
    Partner Profile LS LR_810 SYNCH does Not Exits.
    Generate Partner Profile.
    or Specify outbound partner Profile for message type SYNCH
    RFC destination for Syncronous Communication (Message type SYNCH)
    Partner Profile LS LS_810 SYNCH does Not Exits
    Generate Partner Profile.
    or Specify outbound partner Profile for message type SYNCH
    Thannks;
    Upender.

    In Bd64 t-code Distribution Model.
    create the model view ,
    add message type Matmas to it.
    -> select the model view
    ->environment-> generate partner profiles
    In Partner Profiles u hv to maintain the Outbound parameters in Both LS_800 &
    LR_810 .
    in receiver port, double click & make sure that the rfc destination assigned connects successfully..
    Regards.

  • How to transport the distribution model from devlopment to quality in idocs

    Hi ,
    I am developing settings for idocs for the basic idoc type 'MATMAS03'.
    By using SM59 , I gave the connections of two logical systems.
    I created the distribution model by using BD64. when I generate the partner profiles , automatically, port and partner profiles are created.
    How to transport from DEV to QUALITY of RFC connections, Distribution model and automatically generate partner profils and port ?
    Plz give me the answer in broad way
    Regards
    NTR

    hi,
    Refer to this link...
    how to transport distribution model

  • ALE problem with distribution model

    Hi ,
    I have created one logical sys for client 030 as LOGSYS030. and i Have created one more dummy logical sys for client 030 as LOGSYSD30.
    then i have created model view with LOGSYS030 as sender and LOGSYSD30(dummy log sys) as receiver ,then i have generate the partner profile.
    next i am trying distribute model view while i got error ,model view has not been updated ,reason distribution model currently being processed.
    How can i distribute the model view for same client act as recevier and sender.
    Thanks & regards
    laxman

    Hi Joerg ,
    actually i want to create sales order with some changes when the customer create the sales order in the same client,
    i used ale . outbound idoc for sales order1 details, again i triger inbound idoc (orde) for creating second sales order based on 1st sales order.
    mainly client needs sales order2 without manual interaction(report program)
    Thanks & Regards
    laxman

Maybe you are looking for

  • Creation of Ibase for satellite systems in Solution Manager 4.0 SP13

    Hello! Can enybody help? We are trying to creat Ibase for Satellite systems in solution landscape in SolMan system, using the automatic generation(TA SOLUTION_MANAGER) for specific solution. After successfully generation we have only one iBase for on

  • Problem in changin the username at the Step Level

    Hi All, I had a small problem with background processing in SM37.I was trying to change a job which was running from my Id to some other Id which I needed to run from.I changed it successfully, but the problem is the job is running under new Id now,

  • Report to find out Manager change in given period of time.

    Hi All, There is a standard report to find out info type changes. But it is not capturing the HRP1001 info type. Is there any report or function module which will Identify the manager change for a given period of time? Regards, Ravi

  • Upgrade from solaris 8 to solaris 9 with sun solstice disksuite

    Hi, I have to upgrade the solaris 8 with Solstice disksuite to Solaris 9 OS. Please let me know the steps for the upgrade. Regards chesun

  • SEM CPM - Link a Query in Web Mode

    Hi all, Im working with SEM-CPM ; i can't add a link to a query in web mode ; i have tried this : 1)Add URL ; works fine but i cannot add the URL dinamycally in order to take the local server ; for example when i transport to QAS then links points to