SAP ALE编程指南：技术详解与应用

需积分: 3 163 浏览量更新于2024-08-02 收藏 2.07MB PDF 举报

"ALE programing guide 是一份详细阐述ALE（Application Link Enabling）编程的指南，适合用作工具书和技术文档，适用于SAP系统的版本4.6C。此文档由SAP AG出版，版权归属于SAP AG，未经许可不得复制或传播。请注意，文档中的信息可能随时变更，且包含其他软件供应商的专有软件组件。此外，还提及了多家知名软件公司的注册商标，如微软的Windows、Excel等，IBM的DB2、OS/390等，Oracle的注册商标，以及与互联网技术相关的HTML、XML等标记语言。" ALE（Application Link Enabling）是SAP系统中的一种集成技术，用于在不同的应用程序之间实现数据交换和业务流程自动化。它允许不同系统间的无缝交互，确保企业内部或跨企业间的数据一致性，是SAP R/3系统实现企业资源规划（ERP）集成的关键部分。在ALE编程指南中，读者可以期待学习到以下核心知识点： 1. **ALE基础**：了解ALE的基本概念，包括事件驱动的架构，以及如何通过IDoc（Intermediate Document）进行数据传输。 2. **EDI（Electronic Data Interchange）与ALE的关系**：ALE在更广泛的业务环境中如何与电子数据交换（EDI）协同工作，以实现不同组织间的标准数据交换。 3. **RFC（Remote Function Call）**：理解SAP系统中的远程功能调用机制，它是ALE实现不同系统间通信的基础。 4. **Partner Profile和Distribution Model**：学习如何设置合作伙伴配置文件，以及创建和管理数据分发模型，这是配置ALE服务的关键步骤。 5. **IDoc的结构和使用**：深入探讨IDoc的结构，包括其段（Segments）、类型（Types）和结构（Structures），并学习如何创建和修改IDoc来适应特定的业务需求。 6. **ALE监控和故障排除**：学习使用SAP的监控工具来跟踪ALE过程，以及如何解决可能出现的问题。 7. **与外部系统集成**：讨论与非SAP系统的集成策略，例如使用适配器（Adapters）和技术，如Web Services或APIs。 8. **实例分析**：通过实际案例研究，了解ALE在供应链管理（SCM）、财务会计（FI）、物料管理（MM）等SAP模块中的应用。 9. **最佳实践和安全考虑**：获取实施ALE的最佳实践建议，以及确保数据安全性和系统性能的方法。 10. **最新版本的更新和变更**：由于文档提及版本4.6C，可能还会包含对新特性、增强功能或API的解释。通过这份编程指南，无论是初学者还是经验丰富的SAP开发者，都可以深入理解ALE的工作原理，并掌握如何有效利用ALE技术提升企业系统的集成能力。

ALE Programming Guide SAP AG

Implementing Your Own BAPIs

SAP provides a large number of BAPIs. If you want to implement your own BAPIs, you have to

use your own namespace.

Procedure

You have the following options:

• You can develop your own BAPI in the customer namespace.

• You can modify a BAPI delivered in the standard system.

1. Copy and modify the function module belonging to the original BAPI.

2. In the Business Object Repository create a subobject type for your BAPI object type in the

customer namespace (Tools → Business Framework → BAPI Development → Business

Object Builder).

When you create the subobject type the methods of the business object inherit the

subtype.

3. Set the status of the object type to Implemented (Edit → Change release status → Object

type).

4. You can change and delete the methods of the subtype or enhance them with your own

methods.

For further information about creating new BAPIs and enhancing existing ones refer to

Modifications and Customer Enhancements [Extern]

in the BAPI Programming guide.

Notes about Asynchronous BAPIs

If you want to implement an asynchronous ALE business process, you have to Define a BAPI-ALE

Interface [Seite 30] from the BAPI.

If you implement a BAPI as an asynchronous interface, in addition to following the standard

programming BAPI guidelines, keep in mind the following:

• The BAPI must not issue a COMMIT WORK command.

• The method's return parameter must use the reference structure BAPIRET2.

• All BAPI export parameters with the exception of the return parameter are ignored and are not

included in the IDoc that is generated.

• Status records log the BAPI return parameter values.

After the function module which converts the IDoc into the corresponding BAPI in the

receiving system has been called, status records are written for the IDoc in which

messages sent in the return parameter are logged.

If, in at least one of the entries of return parameter, the field Type in the return parameter

is filled with A (abort) or E (error), this means:

• Type A:

Status 51 (error, application document not posted) is written for all status records,

after a ROLLBACK WORK has been executed.

• Type E:

Status 51 (error, application document not posted) is written for all status records

and a ROLLBACK WORK is executed.

Otherwise status 53 (application document posted) is written and a COMMIT WORK

executed.

16 April 2001

ALE Programming Guide SAP AG

Filtering Data

There are two filtering services provided for asynchronous BAPI calls using the BAPI-ALE

interface.

• Interface Reduction:

If you want to reduce the BAPI interface, you do not have to define any filter object types.

The BAPI reduction does not have any conditions - it is a projection of the BAPI interface.

The developer of the BAPI whose interface is to be reduced must create the BAPI as a

reducible using appropriate parameter types.

The optional BAPI parameters and/or BAPI fields are deactivated in the distribution model

for the data transfer.

You can reduce an interface in two ways, see Reducing Interfaces [Seite

21]

• By fields (using checkbox lists)

• Fully

• Parameter Filtering

Filter Object Types [Extern]

are assigned to the business object method. The valid filter

object values must be defined in the distribution model.

The BAPI parameter filtering is linked to conditions, it is therefore content-dependent: The

lines in table parameters of asynchronous BAPIs are determined depending on the values

in the lines (or dependent lines) for the receiver.

Filters are used to define conditions in the form of parameter values that must be satisfied

by BAPIs before they can be distributed in ALE outbound processing.

The table dataset of a BAPI is determined when the parameters are filtered.

Hierarchy relationships between table parameters of the BAPI can also be defined.

Distribution by Classes [Extern]

is also supported.

For more information see Filtering BAPI Parameters [Seite

25]

BAPI filtering is the term used for the shared use of both the filter services of the BAPI interface.

BAPI filtering is implemented as a service in ALE outbound processing.

Prerequisites for Using Filter Services

The table below lists the prerequisites that the BAPI interface must satisfy, so that ALE filter

services can be used.

The BAPI can have the following parameter types:

Field

Reduction

Full Filtering Parameter

Filtering

1. Unstructured without checkbox

2. Unstructured with checkbox X

3. Single-line structured without checkbox

4. Single-line structured with checkbox X

18 April 2001

SAP AG ALE Programming Guide

Filtering Data

5. Multiple-line structured without checkbox X X

6. Multiple-line structured with checkbox X X X

7. Multiple-line unstructured without checkbox X

8. Multiple-line unstructured with checkbox

Note: The fields filled with X satisfy the prerequisites.

Explanation of above table:

1. An unstructured parameter without a checkbox is, for example, a BAPI key field (e.g. the

parameter Material in methods of the business object Material).

This parameter type cannot be reduced.

2. If there is an unstructured checkbox parameter with the name PX and the data element

BAPIUPDATE for an unstructured parameter with the name P, the parameter P is reducible.

The parameter is reduced by setting the value of P and of the checkbox parameter PX to

EMPTY.

3. A single-line, structured parameter without a checkbox is not reducible.

4. A single-line, structured parameter P with structure S and associated checkbox PX with

structure SX can be reduced by fields, provided that:

• S and SX have the same number of fields, which are identical in name and sequence.

• The FUNCTION field and the key fields in S and SX each have the same data element.

• All other fields in SX have the data element BAPIUPDATE.

The FUNCTION field in P and the key fields must be marked as mandatory fields. All the other

fields you can chose whether to label them as mandatory. Mandatory fields cannot be

reduced. Non-mandatory fields are reduced by setting the field values and the corresponding

checkbox to EMPTY.

5. Multiple-line structured parameters (table parameters) without a checkbox cannot be reduced

by fields. Parameter filtering and full filtering are possible.

If the hierarchy is maintained and, if dependent tables exist in the hierarchy, records of the

dependent tables will also be filtered.

6. A multiple-line structured parameter P with checkbox PX can be reduced by fields, fully

filtered or filtered by parameters.

• For field reduction the prerequisites under 4 must be met.

• The checkbox PX must lie directly under P in the hierarchy, with identical key fields, so that

the corresponding lines from P and PX are filled, when the parameters are filtered.

• If the hierarchy is maintained and, if dependent tables exist in the hierarchy, records of the

dependent tables will also be filtered.

7. A multiple-line, unstructured parameter can only be fully filtered and cannot be used in a

hierarchy.

Parameter filtering is not allowed.

8. Multiple-line, unstructured parameters with a checkbox cannot be filtered.

April 2001 19

剩余217页未读，继续阅读

cyeros

粉丝: 0

SAP ALE编程指南：技术详解与应用

SAP ALE Programming Guide

AE开发编程指南

Step by step guide to ALE and IDOCs

NS2D-ALE.rar_ALE fortran_ale fortran_fortran ale_navier FORTRAN

ALE:ALE 1丰蒂斯

ALE enhancement

ale_interface\ale_c.dll

idoc ale 配置

ALE Quick Start

ALE 学习记录

最新资源