设为首页 收藏本站
查看: 661|回复: 0

[经验分享] SAP EDI Architecture (Inbound and Outbound process)

[复制链接]

尚未签到

发表于 2015-9-20 10:02:10 | 显示全部楼层 |阅读模式
  The SAP EDI process comprises two distinct processes.

  • Outbound process
  • Inbound process
The Outbound Process
  The outbound process sends documents from the SAP system to a business partner (vendor, customer, and bank). The outbound process consists of six steps.
  The application document is created. The first step in the outbound process involves creating an application document such as a purchase order or sales order and saving it in the database tables. This step is no different from the way in which these documents are normally created. It is the following steps that have relevance to EDI. The document is created and leaves some hooks for the EDI process to begin.
  The IDoc is generated. The application document just created is now formatted to an IDoc format.At this point you can think of IDoc as yet another format in which the application document has been represented. A document in an IDoc format is suitable for processing by EDI components.
  The IDoc is transferred from SAP to the operating system layer. The IDoc created in the above step resides in the SAP database repository. This IDoc document must be passed down to the operating system layer for processing by the EDI subsystem. Now the IDoc is transferred to the operating system as a text file. The document is still in an IDoc format. The only difference is the medium of storage.
  The IDoc is converted to EDI standards. The IDoc format is an SAP proprietary format. For EDI purposes, the document in IDoc format has to be converted into an EDI standard format. Third-party software called a translator carries out the transformation process and reports status back to the SAP system. SAP refers to these translators as EDI subsystem or other middleware translltor like SAP XI/PI. SAP takes no responsibility for translation. Thus, from SAP's perspective, after the IDoc is delivered to the subsystem or middleware, SAP does not have control over the process, but it maintains the status reported by the EDI subsystem.
  The EDI document is transmitted to the business partner. After the document is converted to an EDI standard format, it is transmitted to a trading partner based on the partner's EDI settings. This step is not part of the SAP EDI architecture, but is mentioned here to describe the complete process from a business perspective.
  The EDI subsystem reports status to SAP. When an IDoc is under the control of the EDI subsystem, the subsystem can optionally report the state of processing at various milestones back to the SAP system. This mechanism is always recommended because it provides complete visibility of the process from within SAP, and the user does not have to be involved with the intricacies of the EDI subsystem.
The Inbound Process
  The inbound process simply reverses the steps of the outbound process. The inbound process receives an EDI document (such as a purchase order response, sales order, or payment information) from a business partner (such as a vendor, a customer, or a bank) and creates SAP documents from it.
  The inbound process consists of five steps.
  The EDI transmission is received. EDI documents are received from a business partner via the VAN or AS2. These documents are in one of the EDI standard formats. The documents are deposited in a common repository for the subsystem. This part of the process is not part of the SAP EDI architecture.
  The EDI document is converted into an IDoc. The EDI-specific headers and trailers are stripped off, and the document is converted into an IDoc format suitable for SAP applications. The process is carried out at the EDI subsystem or middleware level.
  The IDoc is transferred to the SAP layer. The IDoc created in the above step is stored in a text file at the operating system layer. The subsystem starts an inbound program in the SAP layer. This program reads the IDoc file and creates an IDoc in the SAP repository for further processing.
  The application document is created. The IDoc received from the subsystem is passed to a posting program. This program creates an application document such as a sales order, purchase order acknowledgment, invoice, or shipment notice.
  The application document can be viewed. The application document created via EDI is the same as any document created manually in the system: The document can be viewed using standard application transactions. For example, if an incoming sales order was created via EDI, you could view the sales order document via transaction VA03.

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-116111-1-1.html 上篇帖子: 关于SAP的号码范围(number range) 下篇帖子: 什么是SAP(摘自百度百科)
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表