SAPconnect：R/3系统的邮件与传真接口详解

需积分: 10 84 浏览量更新于2024-08-01 收藏 107KB PDF 举报

"SAPconnect是SAP R/3系统中用于电子邮件和传真系统的接口，它基于RFC技术，提供了一个标准的通信渠道，用于与各种通信系统集成，包括SAP Internet Mail Gateway和不同R/3系统之间的连接。此文档详细介绍了SAP BC-CON组件，特别是SapConnect的功能和RFC接口的使用。" SAP BC-CON，即SAPconnect，是一个在R/3系统中用于电子邮件和传真系统的接口。它的设计目标是作为SAPcomm的替代品，以标准化的方式支持所有通信系统，包括与SAP互联网邮件网关的集成以及不同R/3系统之间的交互。通过使用远程功能调用（RFC）技术，SAPconnect允许用户直接从R/3系统访问各种通信系统，如传真服务器、X.400 MTA（消息传输代理）和互联网邮件节点等。文档的变更记录显示，在V01.01.C版本中，新增了地址类型'PAG'，用于支持寻呼功能，并对管理部分（如CSP/ICC）进行了小的改进。 SAPconnect-RFC功能概述中，主要包含以下几个方面： 1. **状态转移过程**：这是SAPconnect处理通信任务的核心流程，涉及对象数据的发送、接收和状态更新。该过程确保了消息的正确传递和反馈。 2. **对象数据**：对象数据包含了通信任务的详细信息，如发送者、接收者、内容和格式等。这些数据通过RFC接口在R/3系统与通信系统之间交换。 3. **接收者列表**：定义了消息可以发送给多个接收者的方式，支持批量处理和多目的地通信。文档详细描述了两个关键的RFC函数： 4. **SX_OBJECT_RECEIVE**：这个RFC函数用于接收对象数据，通常在初始化通信任务或从外部系统接收状态更新时调用。它处理输入参数，例如接收者的详细信息，以及返回的对象状态。 5. **SX_OBJECT_STATUS_RECEIVE**：这个函数用于接收对象的状态信息。当通信任务完成或发生错误时，R/3系统可以通过此接口获取发送或接收操作的最新状态。在附录中，还列出了状态代码列表，这为理解通信任务的不同阶段和可能的结果提供了参考。 SAPconnect是R/3系统与外部通信系统之间的桥梁，利用RFC技术实现了高效、灵活的集成。这份文档为开发者和管理员提供了详细的操作指南，帮助他们理解和实现SAPconnect的各种功能。

2.2. Using RFC in SAPconnect

RFC Server and Client

SAPconnect defines two function modules:

SX_OBJECT_RECEIVE is used for transferring objects (E-mail, fax, IDocs, etc.) and

SX_OBJECT_STATUS_RECEIVE is used for transferring status information about

objects.

If these functions are called in R/3, from the point of view of the external system,

the R/3 is dealing with received, i.e. inbound, objects. In such a case, the R/3

System represents the RFC server and the calling program represents the RFC

client. If R/3 calls the functions in an external system it is dealing with sent, i.e.

outbound, objects. In such a case, the R/3 System becomes the RFC client and

the called program becomes the RFC server.

Synchronous RFC

Although data in the R/3 System is updated, synchronous RFC is used instead of

transactional or asynchronous RFC. Any possible problems (duplicates in the

receiving system) must be detected in the receiving system (in the case of

SAPconnect, the corresponding R/3 System). In SAPoffice, the message ID,

receiver and sender are analyzed for this purpose. The use of the synchronous

RFC also ensures that status information for each receiver can be returned to the

caller after the processing of the RFC (synchronous status). In addition, status

values can also be sent asynchronously (later) via SX_OBJECT_STATUS_RECEIVE,

e.g. for read confirmations.

RFC Server Registration

(see Figure 1)

The RFC server running on workstation/front-end platform can be called by the

R/3 System in two ways:

a) Triggered start (via application server, SAPGUI

and explicit computer ID entry), or

b) Via registration with the SAP Gateway

Due to the fact that a communication system (e.g. fax server) usually represents

a process which is constantly running (e.g. NT Service or UNIX Daemon), does not

use SAPGUI and is not forced to run on the SAP Gateway, the registration variant

is used. While the system is being booted, the RFC server part of the

communication system informs the SAP Gateway of the identifier under which it

should be addressed. This identifier must also be defined in the corresponding

RFC destination in the R/3 System.

A standalone R/3 gateway can be installed on the partner hardware platform

for better performance, please check OSS note 85254 (4.0x/4.5A) or 137478 (4.5B)

for more details.

剩余35页未读，继续阅读

luodx1021

粉丝: 5

SAPconnect：R/3系统的邮件与传真接口详解

SAP Java Connector 3.0 操作手册

sap.net connect2.0

SAP专业教材资料bc_sapconnect.pdf

SAP BW SCOT

SAPSMTP邮箱系统配置手册(发送邮件).pdf

SAP-SMTP邮箱系统配置手册(发送邮件)

SAP配置邮件服务器.docx

SAP javaconnect连接jar包及部署sapjco

SAP采购订单外发到供应商邮箱

SAP配置邮件服务器[参照].pdf

最新资源