BIT300 Application Link Enabling (ALE) Technology

(1)

BIT300

Application Link Enabling (ALE)

Technology

SAP NetWeaver

Course Outline

Course Version: 95

Course Duration: 3 Day(s) Publication Date: 2015

(2)

Copyright

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. • ORACLE® is a registered trademark of ORACLE Corporation.

• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. • Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

• JAVA® is a registered trademark of Sun Microsystems, Inc.

• JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP SE in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING

WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,

INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

(3)

BIT300 Contents

Course Overview

This course explains how to use Application Link Enabling (ALE) using predefined example scenarios. You will learn how to configure ALE scenarios and how to control data exchange between systems.

Target Audience

This course is intended for the following audiences: • Consultants

• Project team members

Course Prerequisites

Required Knowledge

• SAPTEC (Fundamentals of SAP Web AS) Recommended Knowledge

• BIT100 (SAP NetWeaver Process Integration)

Course Goals

This course will prepare the participant to:

• Create a system landscape for using different ALE scenarios (distributing master data and transaction data)

• Control data exchange between systems in a distributed system landscape • Correctly assess the capabilities and limitations of ALE

Course Objectives

After completing this course, the participant will be able to:

• Set up a distribution model for exchanging master and transaction data between systems • Create partner profiles for data exchange in enterprises and for electronic communication

with business partners

• Determine the scope of data to be distributed, depending on its type and recipient • Monitor data exchange between systems

(6)

BIT300 Course Overview

(7)

BIT300 Course Outline

Unit 1

ALE Fundamentals

Unit Overview

In this unit, you will first learn about the possible applications of ALE in enterprises. You will then find out which basic settings you need to make in Customizing and applications to use ALE.

Lesson: Cross-System Business Processes

Lesson Objectives

After completing this lesson, the participant will be able to:

• List examples of business processes in distributed  system landscapes • Differentiate ALE from EDI

Lesson: The Distribution Model

• Explain the terms "logical system" or "logical system name", "mes-sage type" and "distribution model"

• Explain the function of the distribution model

Lesson: Basic ALE Customizing

• Define logical system names and assign them to clients in SAP systems, where applicable

• Explain the terms "IDoc" and "basic type"

• Determine the assignment of message types to basic types • Complete a view in a distribution model

(8)

Lesson: Intermediate Documents

• Explain and differentiate between the terms "basic type", "master IDoc" and "communications IDoc"

• Determine the details of basic types

• Describe the process from the creation of an IDoc in the sender system through to processing in the target system

Lesson: Synchronizing Customizing

• Describe methods for adjusting Customizing settings in SAP system landscapes

Lesson: ALE and the SAP NetWeaver Exchange

Infrastructure

After completing this lesson, the participant will be able to: • Explain how ALE scenarios are integrated into SAP XI

(9)

Unit 2

Master Data Distribution

Unit Overview

The decision to manage master data centrally is one of the main reasons for using ALE. In this unit you will learn about all the settings needed for setting up a central master data administration.

Lesson: Example: Material Master

• Describe the configuration of an ALE scenario for distributing material master data • Distribute material masters

Lesson: Using Change Pointers

• Explain the use of change pointers in master data distribution and set them up in the system

Lesson: Data Filtering and Reducing the Scope of Data

• Describe different methods for filtering data in IDoc processing • Create a reduced message type and use it in the distribution process

(10)

Unit 3

Distributing Transaction Data: Message

Control

Unit Overview

Transaction data (documents, postings) can also be distributed beyond system boundaries using ALE. Message control is one of the methods you can use to implement cross-system processes. However, you can also use it for electronic communication with business partners (suppliers, customers).

Lesson: Message Control and IDoc Generation

After completing this lesson, the participant will be able to: • Differentiate ALE and EDI

• Describe the basic functions of message control • Explain how message control is used to generate IDocs

Lesson: Example: Purchase Order Processing

• Create a purchase order and check the events of your message determination • Describe the cross-system purchase order process

• Explain the most important Customizing settings for this process

(11)

Unit 4

Distributing Transaction Data: BAPIs

Unit Overview

This unit explains how transaction data in a system landscape can be distributed in ALE using preconfigured interfaces to business object types, the Business Application Programming Interfaces (BAPIs).

Lesson: Business Object Types and BAPIs

After completing this lesson, the participant will be able to: • Explain the terms "business object type" and "BAPI"

• Determine business object types and BAPIs using the BAPI Explorer, and also determine detailed information on BAPIs

Lesson: The Usage of BAPIs in ALE

After completing this lesson, the participant will be able to: • Enter Customizing settings for synchronous BAPI calls

• Enter Customizing settings for asynchronous BAPI calls using the ALE interface

Lesson: Example: Travel Expenses

• To describe the configuration of the ALE scenario "Transferring the accounting results of the travel expenses to Accounting".

(12)

Unit 5

Monitoring Data Distribution,

Error-Handling and Archiving

Unit Overview

This unit handles various different tasks that arise from the implementation of ALE and EDI scenarios. You will learn how to monitor the evolution of an IDoc, how to correct errors and then how to archive IDocs that are no longer needed.

Lesson: IDoc Status Management

After completing this lesson, the participant will be able to: • Use the status monitor efficiently

• Set up and use the ALE audit

Lesson: Error Analysis and Handling

After completing this lesson, the participant will be able to: • Perform error analysis using the ALE status monitor • Resolve errors in the IDoc processing

Lesson: SAP Workflow in ALE Environment

After completing this lesson, the participant will be able to: • Check workflow settings for the error handling of IDocs • Understand the settings for process codes

• Describe the notification concept

• Monitor the IDoc processing using the SAP Workflow

(13)

Lesson: Archiving IDocs

After completing this lesson, the participant will be able to: • Describe the IDoc archiving procedure

(14)

Unit 6

Appendix

Unit Overview

In this appendix, you will find information about renaming logical systems and about courses of action for identifying and resending lost IDocs after a database breakdown.

Lesson: Renaming Logical Systems

• Explain the correct procedure for changing logical system names

Lesson: IDoc Recovery Following Database Error

• Describe the IDoc recovery procedure and the settings required for this function