Output Type Medium - ALE vs EDI

iteye_2994

于 2008-11-28 18:33:31 发布

阅读量188

点赞数

分类专栏： EAI (PI/GIS/EDI) 文章标签： Access

EAI (PI/GIS/EDI) 专栏收录该内容

38 篇文章

订阅专栏

本文详细介绍了在企业应用集成中，电子数据交换(EDI)与应用级集成(ALE)的配置过程。对于EDI，文章强调了不需要配置分配模型和输出确定，但必须设置合作伙伴配置文件中的消息类别(MC)，以及相关的端口、RFC目标和逻辑系统。对于ALE，则需要额外配置分配模型、输出确定等更多细节。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

EDI medium: don't need config distribution model and output determination, but need config partner profile with MC, and related port, RFC Destination, LS. The output message links to partner profile by partner number specified in PO/SO/GR/Invoice etc.

If not maintain MC in partner profile, we'll meet such an error:

The solution is to config the MC in partner profile properly:

ALE medium: need config Distribution model, Output Determination (Output type, access sequence, condition table, condition records, procedure/schema, assign procedure to application) and Partner Profile with MC and related Port, RFC Destination, LS.