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,

Similar Messages

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

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 ,

Distribution Model Filter - BD59 question

Hi,
if you have a look at BD59 (assign Objecttyp) for example "CREMAS", why is ALE-Objecttyp "MSGFN" used ?
MSGFN is filled in several Messagetypes "but" not showing in distribution model filter.
What is the use of MSGFN as Ale Objecttyp ?

Hello,
The Field MSGFN is a Qualifier / Action Code / Action Field which need not be mandatory. So, probably thats the reason why is not showing up.
Thanks and Regards,
Venkat Phani Prasad Konduri

Inbound idoc- distribution model

Hi,
    Is it mandatory to create distribution model for inbound idoc processing?

Hi all,
        Mine is inbound scenario.
        Sender is XI system
        Receiver is R/3 system.
        Do i need to maintain distribution model for this?
1.As per my knowledge, distribution model is only created in outbound scenario? In inbound scenario why distribution model is not created?
2.On the outbound side, after generating partner profiles we get SYNCH SYNCHRON in outbound partner profile. My question is there any setting to generate partner profiles on inbound side also?
or else SYNCH SYNCHRON will be for only outboud?
Please clarify........

Cannot find the Recv Logical system in Distribution Model

HI experts,
Im triying a Idoc to file scenario, the logical system for PI and R3 has been already created and assinged for the appropriate clients.
and i ve created the port from r3 using tcode we21 and in PI using idx1 and Idx2. The RFC destination also created for PI and R3 system.. when i created the distribution model using BD64 in R2. when i assigning message type i can give the source logical system and i cant find the Receiver logical system... Also in WE19 i cant find the receiver port (which i created in IDX1 and IDX2)..
Could u tell me how to solve this prob???
Regards
Balaji

Hii Ravi,
Thanks for your reply,
Yes i have created the port (RFC800) idx1 and give RFC destination which points the R3 system.
I have assigned the meta data to that port using tcode idx2.
And I have created port with port name "PORT800" in R3 using we21 and give the RFC destination which points the PI system
when im using the WE19... i gave source logical system as R3 Logical system and receiver logical system as PI Logical system.
now im getting error like "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS".
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM

Hiding fields of a table in distribution model

Hello Folks,
I have a standard table with the append structure included with two fields.
I have created two distributed systems to two different servers- but want to transfer standard table data without custom fields data to one system, where as standard + custom fields structure to other system.
Could some help me out in fixing this.

Hi,
Go for field level filtering in Distribution model.
Thanks,
Asit Purbey

Not able to create Distribution Model nor Import using IDX2

Hello,
I have created an RFC destination, and i'm able to connect successfully also remote logon is working with error, i have also created Port associated in RFC destination.
But when i try to added a message type in distribution model, i get an error rfc destination not maintained.
Same goes with Import of metadata, i not able to maintain an Port in IDX1, hence not able to import metadata.
If i import an Idoc or create an external defination will it help.
any help would be appreciated.
Regards,
Abhishek

>>i not able to maintain an Port in IDX1
I hope you have created RFC destination in PI system. What error do you see when you try to maintain port?
Regards,
Prateek Raj Srivastava

How to create a data filter for BAPI used in a Distribution Model ?

I am trying to create IDOC's for a QM inspection plan via message type QPMK in ECC 6.0. When creating the new message type in the Distribution Model, it forced me to use a BAPI (MasterInspectionChar) rather that just the message as I have done in the past. In order to ensure that only IDOC's related to a specific plant and material type get sent out, I was trying to create a filter.
I am able to get into a 'Change Filter' dialog by double clicking 'No data filter set' under the node 'MasterInspectionChar.SaveReplica'. However, an attempt to highlight anything on this dialog and clicking button 'Create filter group' results in msg. 'Select node: Content-dependent parameter filtering'.
Online help led me in a different direction, one thread led me to believe I needed to create a table entry for the filter in table TBD16 via BD81 for later attachment to the BAPI in the Distribution Model. Before this, I created two Z* ALE Object Type records for plant and material type in table TBD11 via BD95 for what I thought would provide a lookup back in BD81 for creation of a new filter record, but these objects are not found. Per the help, I am also unclear as to whether I would need to set up Receiver determination or Parameter filtering, nor where to make this step in the configuration happen?
Can anyone point me back in the correct direction to get a data filter set up for this BAPI within the Distribution Model ?
Thanks - Mike

Just to clarify, what I am having trouble with is finding where exactly to plug in the name of the plant to be filtered? If using a message type such as MATMAS in a distribution model, it is very straight forward to navigate down from the 'Data filter active', and assign a value to whatever field you wish to filter via the 'List of Values'. But in this example, message type QPMK required use of the BAPI MasterInspectionChar, and therefore the different method in creating the filter.
I cannot find similar functionality when navigating the BAPI related row, for MasterInspectionChar. The 'Change Filter' dialog popup displays a row for 'Container' and then 3 more rows containing 'BAPI structure...'. Clicking the 'Attribute' checkbox on any of these rows sets 'Data filter active' as a node under the BAPI. Double clicking the 'Data filter active' brings me back into the same dialog, and selecting any row with an attempt at this point to create a filter results in the 'Select node: content-dependent parameter filtering' warning. Is this warning occuring because of missing configuration?
Thanks - Mike

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

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

Material Master Change Pointers/Distribution Model - any suggestions?

Dear All,
Hope everyone is doing good.. I have been trying to come up with a solution for the below issue, but didn't get any further. Your help is highly appreciated.
Initial Design:
Couple of years before we had a plant 123 and plant 456 where we need to send the materials. So we had specified these plants in Distribution Model and things worked fine.
First Problem
During testing what we have found out was, if some one changes MARA level, IDOC is being created but it's not being sent out of SAP system because the IDOC doesn't have 123 and 456 plants which the distribution model filtered it out and no data got sent to SAP PI.
Solution implemented:
After doing lot of analysis and research we have implemented solution as per the blog The specified item was not found.
Today's problem
There are couple of more plants we were supposed to send the data 789 and 678. The problem is if some one did a mass change on plant 456, the above solution implemented takes all the data(not the deltas) and pushing it out. Even though the change is only on 456 plant, we were unnecessarily sending the data to 789, 678 which is causing lot of problems.
Now we realize we shouldn't have gone with the solution mentioned above, because it's not applicable in my scenario.
Does anyone handled this kind of scenarios in the past, if so can you please shed some lights?
Thanks,
Raj

Hi Raj,
As per my experience what you had already implemented, that is absolutely correct. I don't think there is any alternative to send the data as a whole (I understood if you are not sending the Plant data, how the middle ware filter them).
Now your requirement is if you make some mass changes in the materials which are extended different plants other than 456 plant, we have to restrict them. To restrict the outbound Idocs for MATMAS. you can use the Filter option in BD64 (Distribution Model). Here after creating the Filter Group, you can edit LOV for Plants.
Once your mass changes transmission is over, you can remove this.
Hope this will work, at least you can give a try...............

Disable ssn field in distribution model for e-recruiting

We are running e-Recruiting 3.0 as a stand alone, and moving HR master data using ALE. The only problem is that the client does not want to have SSN in the e-Recruiting system. Is it possible to filter out SSN within the distribution model, if not where is it stored in e-Recruit so we can mask it after it is moved over.
Thanks,
Alex

Hi Alex:
Follow this path in IMG path
SAP Netweaver --> Application Server -->IDoc Interface/ALE --> Modelling and implementing Business processes --> Converting data between sender and receiver
Follow the steps there and you can do it.
Please award points if Helpful.
Thanks
Venkat

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.

To add condition on which distribution model MATMAS should be sent

Hello All,
I have to send MATMAS Idoc to XI. But in R/3 there 2 distribution models created one for XI and other for some R/# system.
I have created a custom report of MASTERIDOC_CREATE_SMD_MATMAS to handle specific conditions. Now I want to send to distribute this IDoc only to XI sytem and not to the other R/3 system.
Where can I add this condition.
Thanks in advance..
Shabari

hai..
MDD1     Advance for MDD0
MDD2     Adv.frm prev.per.for MDD0
MDD3     Advance MDD2 paid back
MDD5     Arrears w. balance recov.
MDD6     Recovery for MDD5(IT15)
MDD7     Balance & IT15 entry
MDD8     Deduction for MDD7
MDD9     Total deducted via MDD8

Distribution model mandatory

Similar Messages

Maybe you are looking for