Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Distribution Model

Former Member
0 Likes
3,315

Hi Friends,

What is the use of creating the Distribution model in BD64 transaction?

I have created a custom IDOC and I can able to post it from client200 to client 900 successfully, without creating the distribution model.Is it really necessary to create it? Can u ppl help on this?

20 REPLIES 20
Read only

Former Member
0 Likes
2,411

Hi,

refer to this link..[Distribution Model|https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_all&query=whatisDistribution+Model&adv=false&sortby=cm_rnd_rankvalue]

Read only

Former Member
0 Likes
2,411

Hi,

we cannot distribute idocs without BD64. the only other way is by using function module master_idoc_distribute .

Regards,

Phani.

Read only

0 Likes
2,411

Hi friend,

I cant get it clearly.. Wt do u mean by Distribute? I can able to transfer Data from one client to another with out Distribution model. Also is tr any other Function Module to Post the Outbound IDOC?

Read only

0 Likes
2,411

Hi,

Don't know about other FM than the one mentioned, but Distribution Model is a necessity in order any IDocs can be sent out to different system or received from it. You say you are able to send IDocs without maintaining Distribution Model first. In that case it must have been already defined for these two systems.

As Distribution Model (DM) simply create a logical path between two systems (source system and target one). "Phisical" connection between those two are created in SM59 (RFC configuration). This will allow systems to communicate, but you need to set for them by what means data are sent. When RFC is configured you still need to create a DM for systems, otherwise you will not be able to send any data (your target and source system must know which BAPIs/methods should be used and which IDoc types are accepted). After you maintain DM you generate Partner Profiles from it. Then the systmes are able to exchange data.

Refer [this link|http://help.sap.com/saphelp_470/helpdata/en/6c/b9b77f806311d2b45a006094b9c9b4/frameset.htm] to lear how to set up the DM configuration.

Regards

Marcin

Read only

0 Likes
2,411

Hi Marcin,

I dont hv any DM between these 2 system and also the Idoc typa & Message type are a custom one " Z'. But still i can able to send and receive the data.

Read only

0 Likes
2,411

Hi SASIKANTH,

Waht kind of RFC you are using? Is it R/3 connections or TCP/IP. Go to SM59 and check the connection type. Also check if Partner Profile is generated for target system. Go to WE20 -> Exand the node Partner Tyoe LS and check if you can see target system ID.

Regards

Marcin

Read only

0 Likes
2,411

Hi Marcin,

I am using R/3 connection in SM59. Also I have created an entry in partner profile in WE20.

But i hv not created any distribution model. Still i can able to post the IDOC successfully.

Read only

0 Likes
2,411

Hi Sasi,

You can generate idocs sucesfully and post in other client ( not in other system) without Distribution model in Single server .

If you want to do this transfer between 2 different systems ( servers) then you need to go for craetion of Distribution model view, because through this only it will identify the partner system and Message type and filters if any.

As in ur case, u r in single system but only 2 diffrent clients, then u can craete and post idocs without distribution.

revrt back if any issues,

regards,

Naveen

Read only

0 Likes
2,411

Hi Naveen,

Thanks for ur answer... I need more inputs on this...

1) Is this Distribution Model needed to be creadted for NON-SAP system( TIBCO) also?

2) When do we need to create this Model? Before or After creating a entry in Partner profile in WE20.

Read only

0 Likes
2,411

hi,

1)you should create distribution model for NON_SAP system also, thru this only partner systems are recognised in teh distributed environment.

2) thsi should be cerated after creating Partner profles.

regards

Naveen.

Read only

0 Likes
2,411

Hi guys

2) thsi should be cerated after creating Partner profles.

Parter profiles are generated based on Distribution Model after it is created. Correct me if I am wrong, but this is the procedure we always follow (generating partner profiles using BD64 -> Environment -> Generate partner profile and distributing it to subseuqent system Edit -> Model view -> Distribute , so after DM is defined)

Regards

Marcin

Read only

0 Likes
2,411

Hi Marcin,

you are correct , and i said "thsi should be cerated after creating Partner profles."

what i mean here is first we create partner profiles thru WE20 tcode, then go for Distribution Bd64 .

and what you mean is the same BD64 -> Environment -> Generate partner profile and distributing it to subseuqent system Edit -> Model view -> Distribute , so after DM is defined)

In ur case u r calling WE20 through BD64 and then go for distribution. what you mean is the same .

overall conclusion is that we need to create Partner profiles, then Distribute.

Revert back if you have issue.

Reagrds,

Naveen

Read only

0 Likes
2,411

Hi Naveen,

Sure, I thought you meant first creating parter profile then create a model for it. But as far as we are talking about order of creating profiles and distributing it further, what you said is correct. Obviously first we create DM on our side, then Parter Profiles from this DM and then distribute it to related (subsequent) system.

No issue then, just my misunderstanding with interpretation.

Regards

Marcin

Read only

0 Likes
2,411

Hi,

Can u plz explain the step by step procedure in creating n didtributing Model view...

If there is any attachements plz send it too as well...

thanks for ur replys...

Read only

0 Likes
2,411

Hi,

I already sent this [link|http://help.sap.com/saphelp_470/helpdata/en/b4/d05336d0cd0809e10000009b38f839/frameset.htm] but please check it once again. This is easy to follow example on configuring ALE for HR, but similar you do for different IDoc types.

Regards

Marcin

Read only

0 Likes
2,411

Hi Sasikanth,

First of all you need two logical systems, one will act as sender and other as reciever .

1)Define logical systems through BD54.

2) Assign clients to logical systems (SCC4)

3) Create RFC Destination (SM59)

4) create port(we21)

5) Create Partner profile

If all these steps are done then go to BD64, there

1) Create Model view

2) Mention your sender and Reciever for that Model (logical systems)

3) Mention The message type

4) Distribute your model view through Environment -> Distribute

If model view is distributed sucessfully that means messages can flow sucessfully between two systems. To ensure your your model view is distributed sucessfully, take special care while setting up partner profiles in sending and recieving system

you can also create filters for the model, if you want to filter out any segment, fields etc, this can be done for model view.

You can also refer following link for Distribution model:

http://help.sap.com/erp2005_ehp_04/helpdata/EN/6c/b9b76d806311d2b45a006094b9c9b4/frameset.htm

Regards

Vinod

Read only

Former Member
0 Likes
2,411

Hi Sasi,

Check this thread, it may answer ur question.

Read only

Former Member
0 Likes
2,411

Hi,

In Distribution Model(BD64) you can also Generate Partner Profile

Gotto Environment ->Generate Partner Profiles.

Thanks

Krithika

Read only

0 Likes
2,411

Hi Friends,

Now i hv one more query... If we try to create Partner Profile from BD64, Environment ->Generate Partner Profiles, in the new screen it will ask for the view name and Receiver system alone.

But inwe20 screen we need to give the port to create an outbound entry. So which port the system will take? also i tried creating the partner profile from bd64, but i dont find an entry in outbound parameter we20, under my LS.

Read only

0 Likes
2,411

Hi,

First you have to create partner profiles for LS system using WE20 and then

genarate them using BD64.