ALE Implementation Whitepaper

TABLE OF CONTENTS

1 Introduction to ale

1.1 What is ALE?

1.1.1 A Summary

1.1.2 Mass Processing Of IDocs

1.1.3 Cross-System Document Trace (Audit)

1.1.4 Error Handling

1.1.5 What can be distributed?

1.2 Why ALE?

1.2.1 The SAP Solution - ALE

1.3 Phases in an SAP project

1.4 Phases in an ALE project

1.4.1 Phase 1: The Assessment and Project strategy phase

1.4.2 Phase 2: The Design phase

1.4.3 Phase 3: The Configuration phase

1.4.4 Phase 4: The Development phase

1.4.5 Phase 5: The Operations phase

2 Project phase 1: ALE Assessment

2.1 Setting up the project team

2.2 Project team tasks

2.2.1 Assess business requirements

2.2.2 Assess ALE and determine gap

2.2.3 Confirm data / function distribution requirement

2.3 Project team deliverables

2.4 Obtain programme sign-off

3 Project phase 2: ALE Design

3.1 Project team tasks

3.1.1 Develop standards & procedures early

3.1.2 Distribution settings

3.1.3 Design for flexibility

3.1.4 Audit

3.1.5 Technical impact

3.1.6 Sign-off

3.2 Deliverables

4 Project phase 3: ALE Configuration

4.1 Project team tasks

4.1.1 Confirm business requirements

4.1.2 Configure ALE basis area

4.1.3 Functional configuration

4.1.4 QA & testing

4.1.5 Sign-Off

4.2 Deliverables

4.3 Other issues

5 Project phase 4: ALe Development

5.1 Project team tasks

5.1.1 Functional specifications

5.1.2 Technical specifications

5.1.3 Development

5.1.4 Quality assurance and testing

5.1.5 Business sign-off

5.2 Deliverables during this phase

6 Project phase 5: ALE Ops Support

6.1 Project team tasks

6.1.1 ALE Administrator role

6.1.2 Capacity plan

6.1.3 ALE Operations role

6.1.4 ALE Failure recovery

6.1.5 ALE Support organisation structure and process

6.2 Other considerations

6.2.1 Client copies

6.2.2 Client specific configuration

6.2.3 Error handling

6.2.4 ALE specific scenarios

6.3 Deliverables

7 Glossary

This page has been accessed times since 15th April 1999.