DISTRIBUTION MODEL

[Former Member]

hiiiiii friends

can anym one tell me wt is the use of distribution model.....

why do we use it...

iam nt getting it plzzzz tell me clearly yaar....

Edited by: satish abap on Jan 23, 2008 11:14 PM

[Former Member]

Distribution model is majorly used in ALE to identify the target and receiving ports & logical systems

through programically by executiong the FM

MASTER_IDOC_DISTRIBUTE and pass the Idoc records in the specified tables(EDIDC, EDIDD, and etc).

dont forgot to reward if it helpful

regards,

surya

[Former Member]

Distributed Process:

A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.

Need for Distributed Process:• Business in Different Geographical Locations.

• Non availability of dedicated network.

• Cultural and language differences in Geographical locations.

• Running of Mission-critical Applications (Like Maintenance downtime etc.).

• Separate up gradation of Modules.

Distributed SAP SYSTEM – CHALLENGES

• A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.

• Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.

• Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.

• Receiving systems that can handle their own problems and not tie up the sending system.

• Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.

• A sound technology and methodology that can be used in all distribution scenarios.

SAP Distributed environment:

ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.

ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.

Benefits of ALE:• Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.

• Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.

• Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.

Regards.

[Former Member]

Hi Friend,

if it is help full to u please give me max reward point.

2.3. Configuring the Distribution Model

This task is performed on your ALE reference client.

2.3.1. Manual Configuration (BD64) Client dependent

To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:

• Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)

• Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)

• Choose the receiving systems to which the sending system must forward message type ZINVRV to.

• For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.

• Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.

• Save the entries.

NOTES:

You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.

Only the owner is authorised to modify the model.

To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.

To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.

[Former Member]

In the distribution model, you can determine which system (1) sends specific data (2) to what system (3).

You will find :

(1) a sending system (indentified by a logical system name)

(2) a receiving system (logical system name)

(3) a message type (what kind of data is sent)