bd64 related issue

[Former Member]

Hi All,

If i create distribution model in BD64,

1) may i know i still need to assign message type in We20 in sending system outbound parameter and also in receiving system, inbound parameter message type?

2) BD64 distribution model is to create in sending system or receiving system?

3) If distribute data from 1 system to another system via ALE, I create the model in BD64, do i still need to decide the message type, idoc type to use?

thanks

[Former Member]

Hi All,

If i create distribution model in BD64,

1) may i know i still need to assign message type in We20 in sending system outbound parameter and also in receiving system, inbound parameter message type?

2) BD64 distribution model is to create in sending system or receiving system?

3) If distribute data from 1 system to another system via ALE, I create the model in BD64, do i still need to decide the message type, idoc type to use?

thanks

[Former Member]

create 2 logical system....

log_sen and log_rec.

assign log_sen (logical system) to client..

with another (logical system) log_rec name create the RFC Destination...(dont change the name of rfc destination ,give logical system log_rec rece name itself ).

now in model view....create modelview.

there give sender ,rece ,and message type alone.

save and generate patner profile (in menu environment---->generate patner profile)...

here system itself will generate port and patner profile so u need to go to we20 or we21

then in menu edit-->modelview-->distribute

[Former Member]

1. You must mention message type as matmas for outbound if you are sending material master.For inbound it is same.It will be converse on receiving system.

2. As you are sending material from sender system you must create customer distribution model on sender system.

3. With Tcode bd64 you have to enter your model name , sender system receiving system and message type matmas if you are sending material master

[Former Member]

What should be the ideal distributed environment?

u2022System should understand the syntax and semantics of the data

u2022Distribution of the data should be based on business rules and not on database replication techniques

u2022Distributed system should be able to maintain its autonomy while being integrated with other distributed system

Consists of Model Views

Each model view defines:

between which sending

and which receiving logical system(s)

which message types are to be communicated

and any message filtering required.

Distribution model normally maintained in one central system.

Model views distributed (or transported) to the relevant logical systems.

Generate partner profiles from model view.

Multiple message types can be attached in single Distribution model.