Logical System: Activities:

Notes:

·        Maintain logical system
(Cross-Application Components ® Distribution (ALE)  ® Basic configuration  ® Set up logical system  ® Maintain logical systems)

·        Assign logical system to client (for SAP system only)(Cross-Application Components  ® Distribution (ALE)  ® Basic configuration  ® Set up logical system  ® Allocate logical system to the client)

The logical system is used on the selection screen for entering the target optimization systems. You can use as many logical systems as you like for a physical optimization system.

Set up a logical system for the SAP system if it does not already have one, and assign it to a client. The external logical optimization system is not assigned to a client

Communication: Activities

Notes:

·        Define RFC destination
(Cross-Application Components  ® Distribution (ALE)  ® Communication  ® Define RFC destination  ® TCP/IP connections)

Standard settings for POI:

ALE destination
Connection type T
Activation type: Register
Program ID: <Name 1>

RFC destination SAP system  ® external system

Connection type T
Activation type: Register
Program ID: <Name 1>
The <Name 1> identifier is provided by the external optimization system.

·        Define port for RFC destination
(Cross-Application Components ® Distribution (ALE)  ® Communication  ® Manual maintenance of partner profiles  ® Define port ® Transactional RFC)

Standard settings for POI:

Port: <generated automatically>
Description: <enter a description>
Logical destination: <above defined RFC destination for ALE>

·        Reduce interim structures for IDocs:
(Cross-Application Components  ® Distribution (ALE  ® Master data distribution  ® Create reduced message types for master data.)

For each logical system and each basic message type (for example, LOIBOM), a unique message type has to be defined by reducing the original one (for example, MYBOM). A list of the IDocs used with POI is included in the section IDocs.

You can also activate the writing of change pointers for reduced message types in this step.

If you reduce a message type, only the obligatory fields are automatically selected. You must select those segments and fields you want to have transferred. Fields that have not been selected for transfer always contain the value “/”.

·        Maintain partner profile
(Cross-Application Components ® Distribution (ALE) ® Communication  ® Manual maintenance of partner profiles ® Maintain partner profile)

Standard settings for POI:

Partner number: <external logical system>
Partner type: LS
Classification
Partner class: i.e. LOI
Partner status: A
Outbound parameters

Each of the message types of the customer distribution model (see above) must be assigned to the partner profile. Enter the receiver port (see above), package size, output mode and IDoc type in the detail screen of the receiver port. You must also define whether the IDocs should be sent immediately, or if they should be collected first.

·        Maintain customer distribution model directly
(Cross-Application Components  ® Distribution (ALE) ® Distribution customer model ® Maintain customer distribution model directly)

First define a customer model for a logical SAP system. The displayed list shows which logical system is the sender and all the possible receiving systems that have been defined. "Create message type" defines which logical system receives information from the logical SAP system.

When maintaining the customer distribution model, you usually add all (reduced) message types that should be sent from the SAP system to the external system.