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>

Similar Messages

Distribution Model for the Message

want to create a filter for my Distribution Model for the Message Type HRMD_A .
The filtering should be based on Company Code .
I'm getting only infotypes but now should I filter based on Field BUKRS ?

1. Go to Tcode BD59.
2. Create a Custom ALE Object Type
3. Specify the corresponding Segment name where BUKRS exists and the Field Name as BUKRS.

Internal and external distribution models utilizing the SD Module and tcode

gurus,
Did anyone have an experience with internal and external distribution models utilizing the SD Module and transactions.
Please explain the model with tcodes.
Thanks in advance
Regards,
Andy

Can you pen down your requirement !

Error while saving model to the reporting repository with logical views

I have created a view object in the logical model based on objects from the logical model. When I try to save the model to the reporting repository, an error occurs.` If I remove the view object, I can successfully save the model to the reporting repository. Here is the log detail:
2012-03-01 14:00:50,419 [Thread-71] ERROR ReportsHandler - Error Exporting to Reporting Schema:
java.lang.ClassCastException: oracle.dbtools.crest.model.design.logical.AttributeView cannot be cast to oracle.dbtools.crest.model.design.logical.Attribute
     at oracle.dbtools.crest.model.design.logical.LogicalDesign.getObjectsWithMeasurements(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSMeasurements.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
Any thoughts on what is wrong.
Thanks

Hi,
thanks for feedback.
Any thoughts on what is wrong.The program code is wrong - I logged bug for that.
Philip

Dynamic type conflict during the assignment of references. - Error while generating proxy in the backend

Hi All,
I get a short dump while generating a proxy in the backend.I give the package and the prefix and end up with a short dump.
Does any one know why this mught come up
"Dynamic type conflict during the assignment of references."
background: I imported a WSDl provided by legacy into PI and created service interfaces and then trying to generate a proxy class while i get this error.
Thanks.

Hi Shyamsundar,
I will explain a problem that I usually see in some developments:
XSD originally:                                  XSD transformed:
Root                                                     -> Root
Tag 1 type int                                    -> Tag 1 type int
Tag2 type string                               -> Tag2 type string
Tag3 type any                                  - Tag3 type string
Normally the tag3 should have a XML inside. Then the ABAPers have to construct the tag3 with a CDATA structure (CDATA is used to put in an XML tag more XML tags inside like a text and no to be interpreted).
Later in SAP PI you can extract the cdata with an XSL, you can find some examples in the SCN.
I don’t like to convert the whole XML in only one string tag, because this makes difficult the develop for the ABAPers, although the work inside the PI is very easy because with an XSL you can extract the whole message easily. (You can find some examples in the SCN)
Regards.

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.

Find distribution model in source system and maintain filter in it

I have an inbound idoc which is in status 51(error). The procedure shown by SAP is following:-
It has been determined that the particular employee 11001189 has been received for the first time.
Maintain the filter of the appropriate distribution model. To do this, call transaction BD64 in the source system.
Add new filter group to the data filter. Assign values to it.
I cannot find the distribution model. Please somebody help me in finding the relevant distribution model in the source system. One more thing, when I went to BD64 I found that some of the model views were in grey shade while others were in bold, please tell me why is it so.
Please give me some hint.

I have an inbound idoc which is in status 51(error). The procedure shown by SAP is following:-
It has been determined that the particular employee 11001189 has been received for the first time.
Maintain the filter of the appropriate distribution model. To do this, call transaction BD64 in the source system.
Add new filter group to the data filter. Assign values to it.
I cannot find the distribution model. Please somebody help me in finding the relevant distribution model in the source system.
You never maintain Filters in receivin system those has to me in sender system. Also you
need to distribute the Model from sender to receiver once you model is finalized thru menu
option in sender system. Find the Models with HRMD_A as message type
One more thing, when I went to BD64 I found that some of the model views were in grey shade
while others were in bold, please tell me why is it so
simple, If its greyed out then this model is maintained in some other system and is
just distrinuted over to this system, you shuld not maintain the greyed out entries as Maintaince
system is different. The non grey entires are those for which its same system in which the model
is created

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.

"Customer" BAPI in Distribution Model for Training and Events

We have an HR box with Training and Events - When booking an attendee on a course, you can select the "contact person" tab. Our SD box is separate from HR, so all the contact persons are maintained there. Is it possible to use the "Customer" BAPI in a distribution model so that when we search in the HR box for a contact person, it actually fetches the data from the SD box?
I remember reading up on this a while back but I can't find the documentation I had back then...
I know that in BD64 I can create a distribution model, and if I remember correctly, i should be able to "Add BAPI" and use object type "Customer" - Then add all the methods that I need... (like Find, List, Search etc) In essence, once this model has been distributed to the other system, if I go to transaction XD03 in the HR box, I should be able to display customer master details that only exist on the SD box - Is that correct?
Please help as I am not able to get this to work...

Ok I figured it out...
I have created a distribution model with the HR system as the source, and the SD system as the target.
In change mode, click the "Add BAPI" button and choose object BusPartnerEmployee, method CheckExistence
Do the same for the following:
BusPartnerEmployee.Display
BusPartnerEmployee.GetList
Customer.CheckExistence
Customer.Display
Customer.ExistenceCheck
Customer.Find
Customer.GetContactList
Customer.GetDetail2
Customer.GetInternalNumber
Customer.GetList
Customer.GetSalesAreas
Customer.Search1
Ok so I know that this might be a little over-kill, especially all the Customer methods that I added, but it works

Query in Distribution Model creation

Hello All,
we are trying to build a distribution logic based on the below criteria
first data object has the following node structure
DO1
node1
    childnode1
       -field1
       -field2
    childnode2
       -field1
       -field2
the second data object has the following structure
DO2
node1
     -field1
     -field2
     -field3
from the above data object i need to send data for the second data object DO2 based on the childnode1 and childnode2 value in DO1, can any one give a solution like how to create dependencies and create a DM.
Thanks and Regards,
Venkatesh R

I understand this: You have a rule on DO1 (which works fine and distributes DO1 instances correctly) and dependencieso n DO2 (which are not distributing DO2 instances for some reason).
Now your model is something like this:
Each of the 4 child nodes in DO1 has a partial association to the DO2s root (the missed key field is Language).
For each of these associations, there is one dependency which will map to a list of instances of DO2 for all languages, corresponding to each DO1 instance. Now you want to prune this list and only send the instance of DO2 for the device's language.
NOW: If you created the dependency after activating the rule on DO1 then the dependency and its rules will not work right away. You need to deactivate the rule on DO1 and activate it again.
What you need to do:
1. Deactivate the Rule on DO1.
2. Activate the rule on DO1 again.
Hopefully, that should fix it.
By the way, the correct way to distribute language specific data for anything is not via another data object, but via a child node.
Lets say, you have some data (which is language independent) and text corresponding to that data (which is language specific). The way you should ideally do it is:
1. Create a node as a child to the node containing the language independent data. Put the language specific data in this node (all languages)
2. Create an Extract association from the parent node to the child node, within the data object.
3. Use this Extract association to create an extract rule in the Distribution Model. The DOE will then pick the correct language data for each device and send only the child instances that correspond to the language of the device.

Removing Objects O and S from info type 1000 and 1028 in Distribution model

Hi,
My requirement is to remove the objects O and S in distribution model from the filter group of Info type 1000 and 1028.
After removing the objects I perform the below steps:
1. I send an employee (P) through PFAL.
2. Once the employee data is reached to receiver system, then check the employee from PA20.
3. From the Organization Assignment info type (0001), check whether the Org unit and Position text appears on the screen.
Currently after removing the objects O and S, the texts do not flow. But only the org unit and postion id flows to info type 0001, not the text.
Is there any other method or some other configuration to send the texts to the receiver system, apart from maintaining it in distribution model? We want the texts to be displayed in PA20 and PA30 screen for info type 0001 ( along with org unit and position id).
Thanks in Advance.

Hi,
the text for O and S are stored in infotype 1000...so PA30 reads them from that table. So if you want to have the texts in the target system you need to send at least infotype 1000. Why don't you want to send it?.
Regards,
Ana

Distribution Model (ALE) - Message type has to be deleted from model view

Hello,
I want to delete a message type from an existing model view in the distribution model (of the maintenance system).
But when I mark the concerning message type and press Edit->Delete the message 'Action cannot be carried out on the nodes selected' occures. Deleting the complete model view would work...
Does anyone know how I can get this without setting up a new model view?
Many thanks in advance,
Juergen

hi,
>>'Action cannot be carried out on the nodes selected'
you get this message if you try to delete a message type
from a model view that was not created on your system
(it has been replicated and it's maintained on another system)
so you can only delete this message type on the system that has
"master" distribution model
if it's not master then it's usually grey and you can only delete if it's black in change mode
>Deleting the complete model view would work...
if you try that you will see info that it's not the "master" system for this model
check it and let me know
Regards,
Michal Krawczyk

Need of distribution model in IDOC triggering

Hi,
I have one question dat is it necessary to maintain distibution model in BD64 for outbound IDOCs or only maintaining partner profile in WE20 is mandatory.
I have seen some cases in which distribution model is not maintained.
Please let me know the cases in which we maintain distribution model
Thanks in advance.

hi,
The distribution model describes the ALE message flow between logical systems u2013 that is, it determines which messages are distributed to which logical systems.
For example, you can make distribution dependent on conditions that you define as filters in the ALE distribution model.
please refer this blogs for more info:
Data Ditribution Model BD64 config
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
thanks ,

Reg: Distribution model

Hi All,
We have an IDoc exchange scenario like this:
1) We will receive a MBGMCR01 Idoc from a third party system into SAP system A. The same IDoc has to be dispatched to following SAP systems B1, B2, B3,...B10.
2) In system A, the target system B(n) for the incoming IDoc MBGMCR01 must be decided based on the purchase org value coming in the IDoc.
Question on part1: Can we use distribution model for the above scenario? Links for sample tutorials on creation of Distribution model would be highly helpful.
Question on part2: How can we do such a design using Distribution model? Can filters be useful?
thanks in advance.
Vish.

Hi Vishwanath,
Yes, you can use the distribution model. Just go through the following steps to create the distribution model.
1. Go to change mode in transaction BD64 and click on u201CCreate Model Viewu201D from the Application tool bar. Give a Short text, Technical Name for the model. The Start date by default would be current date and the end date would be 31.12.9999. Just click on u201CContinueu201D.
2. Select the model just created, and click on, u201CAdd message typeu201D from the application tool bar and give the sender, receiver and message type details.
3. In order that the distribution model maintained in the sender would be visible at the receiver, select the model view just created and from the menu bar, choose, Edit -> Model view -> Distribute.
4. Just click on continue, which will then give you the log of the distribution. You can check here if the model view was created successfully in the target system.
To design the Idoc distribution based on the purchase org, maintain filters. Drill down the model view newly created deep until you find the text, "No filter set". Click on it and create a filter group. Add purchase orgs to it.
~ Bineah.

Distribution model mandatory

Hi Experts,
Can anybody please explain when the Distribution model is mandatory for IDoc generation?
I have done a set up in my sap sytem that as soon as PO is created, IDoc is generated.
But if I delete the distribution model, IDoc is not generated. But in some other cases, IDocs are generated without having a distribution model. Can someone pls throw some light on this.
Thanks very much.
Regards,
Rudresh

Hi,
Distribution Model describes the ALE message flow between logical systems. The relationships between logical systems, message types, BAPIs, and filters are defined in the distribution model. Applications and the ALE layer user the distribution model to determine receivers and to control the data distribution. 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. 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.
After creating distribution model we generate partner profiles.In case you have maintained the receiver details in partner profiles in transaction WE20 then you don't have to maintain distribution model.
KR Jaideep,

Error On Distribution Model in the Backend

Similar Messages

Maybe you are looking for