ALE setting

[#1]

What are ALE setting exactly?and how to go about it?

[former_member189440]

CONTENTS

Distributed processing 2

Introduction 2

Reasons for Distributing Processes 2

Existing Technologies for Data Distribution 2

Disk Mirroring 2

Online Distribution Using Two-Phase-Commit Protocol 3

Distributed Updates to Replicas 3

What should be the ideal distributed environment. 3

SAP’s solution for Distributed environment 3

Benefits of ALE 4

Data exchanged between distributed SAP system 4

ALE Architecture 4

Outbound processing 4

Components used in Outbound ALE process 5

Triggering Outbound ALE process 6

Difference between EDI and ALE process 6

ALE configuration steps for outbound processing 6

Outbound business scenarios 7

Distributed processing

Introduction

Fig 1.0: Two distributed SAP system Exchanges relevant data.

Two sap systems exchange data with each other at appropriate points to stay synchronized. Distributing a process does not enhance any application functionality. Then, Why Distribute?

Reasons for Distributing Processes

· Geographical Location

· System Capacity

· Data Security

· Political and business reasons

Existing Technologies for Data Distribution

Various technologies or techniques offered by database vendors are based on the structure of data and not the business rules.

Disk Mirroring

Its like Disk Copy changes occurring in a database are simultaneously propagated to another disk that maintains a mirror image of the main disk’s contents. This technique has bad effect on OLTP transactions and it cannot encapsulate business rules for copying only specific data.

Online Distribution Using Two-Phase-Commit Protocol

The database design dictates where a table resides , and the database management system manages queries and updates to these tables. Two-phase-commit protocol guarantees that related tables across system are updated in one logical unit of work.

In this technique segregation based on the semantics of data is not possible. For example, you can not specify that a material master for your Asian subsidiary should be created on system B, whereas a material master for the U.S. unit should be created on system A.

Distributed Updates to Replicas

In this technique the system allows you to maintain redundant data across multiple systems. This technique require same version of database and operating system components on the systems involved in the process.

What should be the ideal distributed environment.

· System should understand the syntax and semantics of the data

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

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

· Distributed system should able to handle different data models.

· Receiving system should handle its own problem and not tie up the sending system and vice versa.

· In spite of network failure , system should maintain continued operation. Changes made to either system should be synchronized after the network connection is restored.

SAP’s solution for Distributed environment

SAP introduced ALE to support integration of distributed systems.

ALE is not based on any database replication techniques. It is based on application-to-application integration using messaging architecture. A message defines data that is exchanged between two processes

In ALE, data is exchanged using IDOC containers.

Benefits of ALE

· Integration with Non-SAP systems

· Reliable distribution

· Release upgrade

· Autonomy

Data exchanged between distributed SAP system

Distributed SAP system exchange three types of data ………

a) Transactional data : sales orders, purchase orders, contracts, invoices, GL posting.

b) Master data : Material master, customer master, vendor master, employee master

c) Control data : Company codes, business areas, plants, sales organizations, divisions, distribution channels.

Transactional and master data are distributed using ALE interface. Control data is transferred using CTS (Correction and Transport System).

ALE Architecture

ALE architecture consists of ………..

· Outbound process

· Inbound process

· Exception handling

Outbound processing

Step 1 : Identify the need for sending an IDOC

a) Start outbound program (Application starts outbound program)

Step 2 : Generate Master Idoc. (Outbound ALE program does this task)

a) Read document or master data from database

b) Format it into IDOC format ie. Generate master IDOC in memory

Step 3 : Generate the communication IDOC. (ALE service layer does this task)

a) Generate & store the communication IDOC for each recipient

Components used in Outbound ALE process

· Customer model

· Idoc Structure

· Selection Program

· Filter objects

· Conversion rules

· Port definition

· RFC destination

· Partner profile

· Service programs

· Configuration tables

Customer model :

In customer model you identify the systems involved in a distribution scenario and the messages exchanged between the systems

Filter objects :

In distributed environment, each recipient of data may have different requirements for the data being distributed. Filter objects remove unwanted data for each recipient of data.

Port Definition :

A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE uses tRFC port, which transfers data in memory buffers.

RFC destination :

In Ale , the RFC specifies information required to log on to the remote SAP system to which an Idoc is being sent.

Partner Profile :

A partner profile specifies the various components used in an outbound process (logical name of the remote SAP system, Idoc type, message type, tRFC port, the packet size of an Idoc, person to be notified in case of errors.

A partner profile is created for each SAP system that you communicate with, and a record exists for each message sent and received from a system.

Partner Profile :

SAP provides sevice programs and configuration tables to link these programs and configuration tables and provides various customizing options for an outbound process.

Triggering Outbound ALE process

· MM/SD transactional data

Ø Message control technique

· FI/PP/HR transactional data

Ø Do not use message control techniques. Application program takes care of

generating IDOCs.

· Master data

Ø Stand alone programs for example BD10/BD11 for material master

Ø Change pointers

Difference between EDI and ALE process

The EDI process transmits Idocs to an EDI subsystem using flat file format. The ALE process transmits Idocs to an SAP system via memory asynchronous communication.

ALE configuration steps for outbound processing

· Setting on source system

· Basic Setting

· IDOC Administrator

· General IDOC interface

· Communication Setting

· Logical system

· Allocate client to the sending logical system

· RFC connection

· Port definition

· Basic configuration for distributing data

· Maintain distribution model

· Generate partner profile

· Distribute customer model

· Maintain workflow setting

· Setting on Target system

· Create partner profile on target system

· Execution

· Start outbound program through application

· View IDOCs

Outbound business scenarios

ü Normal ALE interface : Exchange data object such as material master

between two systems to its full extent using

stand-alone program.

ü Normal ALE interface : Exchange data object such as material master

between two systems to its full extent using

change pointers.

ü Reducing Idoc types : Exchange data object such as material master

between two systems for desired information.

ü Filtering : The filtering techniques creates a subset of data at

run time. Filtering can remove certain segments

from an IDOC or complete Idoc for distribution to

specific system

ü Conversion : The conversion techniques converts data in certain

fields of the IDOC from their local meaning to a

global meaning for distribution.

ü Version Change : Idocs and segments are version controlled. The

system can be configured to distribute a specific

version of an Idoc or a segments to a destination

system.

ALE Implementation Methodology

ü Analysis Phase

ü Preparation phase

ü Setup phase

ü Testing phase

ü Execution and Verification phase

Analysis Phase

ü Study the integrated process

It is very important to understand the business process. The online help provides detail description of the business process. IMG points to the customizing options available in the process. And the reference model can help with process flows and component descriptions.

ü Identify process boundaries in the distributed system

Process boundaries define the business functions that take place on each system.

For example, a contract is created on central system and purchase order against contract is created on another system.

ü Identify data flows

One of the system is owner of the data is responsible for creating, maintaining, and distributing it to the other system. For the data flows you should be able to identify the various transactional and master data exchanged between system.

ü Study the system limitations

For example, if a sales order is being entered in a single integrated system, the system calculates delivery dates and carries out credit checks instantaneously. If, however, the systems are distributed, a real time availability check performed in another system may not be supported.

ü Deciding on customer Enhancements

There may be gaps between the business needs and standard SAP functionality. If gaps can not be filled with one of the customizing options , you can use user exits. For example, if you may need to populate the data in extended Idoc through user exit.

Preparation Phase

ü Identify central and Decentral systems

Identify the SAP systems involved in the process. Assign logical name to each system.

ü Identify Lists of Idocs and Messages

A list of Idoc types and Messages should be identified for each type of data exchanged between the systems.

ü Identify workflow parameters

Identify user ID, position, workcenter etc for handling errors associated with the business process involved.

ü Identify list of control objects

For example, Customizing object for Company code is V_T001.

Setup Phase

ü Identify Lists of Idocs and Messages

These settings are specific to business scenario being implemented.

ü Message control setting to propose ALE output

ü Configure ALE components

ü Maintain basic ALE infrastructure

ü Maintain customer distribution model

ü Distribute the customer model

ü Generate the partner profile

ü Make workflow setting

Testing Phase

ü Test ALE setting

ü Test Control data setting

ü Test application setting

Execution and Verification Phase

ü Execute the application program to trigger the ALE process

ü On Sending system

ü Make sure that application document posted

ü Check the IDOC and make sure it was posted to port successfully

ü On Receiving system

ü Check the IDOC and make sure it was posted to port successfully

ü Make sure that application document posted

Support Phase

ü Monitor the system on an ongoing basis and identify and fix the problems.