Transcript RosettaNet 報告人：關貿網路 朱啟光

RosettaNet簡介
報告人：關貿網路 朱啟光
前言

電子商務的發展


從提供型錄式資訊服務的電子商店(B2C)，演進到企
業間(B2B)商業處理自動化
企業間商業標準架構應運而生

RosettaNet、ebXML、BizTalk。
模式一
ERP
Web server
Company A
Internet
Company B
模式二
ERP
ERP
Business processes,
business documents
Business processes,
business documents
Transport, routing,
packaging
Company A
Transport, routing,
packaging
Internet
Company B
B2B EC的演進



商業應用程式間的交談，達成企業間商業交易
建立在標準的商業流程及商業文件之上
因此標準的制定，便形成B2B EC的重要工作
Business process and
document integration
EDI
B2B EC 標準架構

商業處理層


標準商業流程及商業文件，
技術服務層

商業處理層
技術服務層
安全可靠的溝通管道，做為
上層運作的基礎
• 各種標準
– 水平整合: ebXML
– 產業垂直整合: RosettaNet (資訊技術、電子零組件、及半導體製
造業)
– 技術服務架構:Vitria Framework,BizTalk Framework
ebXML 簡介

1999年9月由聯合國制定電子商務標準的組織OASIS和
UN/CEFACT共同推動的企業間電子商務標準。EbXML
主要任務在於提供一個開放式的XML底層架構，以利各
方在安全、一致的環境下達成共通的電子商務資訊互動。

其基本訴求為使用XML技術，提供不同規模的企業間的
垂直和水平整合。提供低成本的軟體製作，供中小企業
之用，也顧到大企業的需求。通用性的處理程序、用語、
及編碼。制定註冊機制以達成開放性及提高互通性。提
供安全的遞送路徑、封包方式以確保商業訊息送收的安
全。
ebXML架構說明
4. 查訊得知並
取得A公司的商
業處理能力及
細節
1. 取得ebXML規範
2. 製作ebXML相容軟體
A
公
司
ebXML相容
註用及儲存庫
3. 製作並登錄CPP
5. 向A公司請求
做ebXML式交
易，同意後便
進行軟體製作
6. 初使化動作過後，程式間便依之前協定進行商業交談
B2B EC 架構概念圖
B
公
司
RosettaNet




一個非營利協會所制定的企業間電子商務標準
主要目的是為高科技的資訊技術、電子零組件、及半導體製造產業建
立供應鏈管理體系
RosettaNet所定的B2B EC是一個具有上層商業處理與下層技術服務的
整體架構
在上層商業處理方面，主要在於制定企業夥伴間標準商業處理程序
 依照功能性共分成七群(cluster)核心商業處理程序，包括交易夥伴及
商品資訊之收集、維護，產品資訊之分送及更新，訂單管理，庫存管
理，市場資訊管理，售後服務及支援，製造資訊之交換
 每一群又分成幾個段(segment)，每段含有幾個夥伴間程序介面
(partner interface process, PIP)
 每個PIP定義程式對程式間以XML標準商業文件為基礎的對話程序
抽象概念
RosettaNet

從商業運作的角度來看，
一個PIP主要內容是特定的
商業工作流程及其流程中
所帶動的文件
• 為求文件一致，
RosettaNet定義了商業和
技術字典，前者為提供商業
詞彙，後者為各行業的技術
用語
• RosettaNet制定了RNIF
(RosettaNet
Implementation
Framework) ，當中定義了工
作平台間訊息交換協定
(protocol)，以支應上層PIP
在文件遞送上的基礎
商業資訊決策系統
需求處理
成功
失敗
形成需求文件
買方
PIP
形成回應文件
回應處理
賣方
商業資訊決策系統
RosettaNet



對照前面ebXML的架構，RosettaNet提供完整的商業
處理程序及工作平台
RosettaNet並不制定註冊機制及CPP/CPA，因此在商
業夥伴的探索及建立夥伴關係上必須靠人工達成
 UDDI(Universal Description, Discovery
Integration) by IBM, Microsoft and Ariba
另一個B2B EC標準Vitria Framework則是制定了相當
於RNIF角色的下層技術服務
RosettaNet 宗旨及任務

宗旨




Dynamic, flexible trading networks
Operational efficiency
New business opportunities
任務


促進網際網路商業標準的合作發展及快速建置
創造共通的商業語言及開放式的電子化商業程序，為
全球高科技交易網路帶來利益及提昇演進的腳步
什麼是RosettaNet



RosettaNet是由超過400家資訊技術業、 電子零組
件業、及半導體製造業廠商所組成的協會，共創及推廣
開放式的電子標準商業程序
RosettaNet名稱是以the Rosetta Stone而得名
RosettaNet創造電子商務標準語言，包括商業程序及
商業文件



促成供應鏈電子化
建立有彈性的交易夥伴關係
降低成本、提昇產量
什麼是RosettaNet標準內容

RosettaNet標準是集合高科技公司的專業知識，共創
而成的非獨占性的電子商務方案，其內容包括




商業及技術字典
 RosettaNet Business Dictionary、RosettaNet
Technical Dictionary
下層技術服務架構
 RosettaNet Implementation Framework (RNIF)
商業訊息及程序規範
 RosettaNet Partner Interface Processes™(PIPs™)
以上標準規範可由www.rosettanet.org免費取得
概念說明 一
交易夥伴
備妥內容
放入信封
送出
提出需求的交易夥伴準備好
商業文件，載明需求內容
概念說明 二
交易夥伴
備妥內容
放入信封
送出
備妥的商業文件包裝成XML
及MIME規格做成的傳輸信封
內
概念說明 三
交易夥伴
備妥內容
放入信封
送出
用預定的埠際協定(HTTP(s)
、SMTP等)送到交易夥伴的
URI
概念說明 四
交易夥伴
交易夥伴
備妥內容
Trading
Partner
收文
Trading Partner
放入信封
解開信封
交易夥伴收到信件
送出
處理內容
概念說明 五
交易夥伴
交易夥伴
備妥內容
Trading
Partner
收文
Trading Partner
放入信封
解開信封
解開以檢驗信封內的處理資
訊及商業文件是否正確
送出
處理內容
概念說明 六
交易夥伴
交易夥伴
備妥內容
Trading
Partner
收文
Trading Partner
放入信封
解開信封
根據RosettaNet規範處理驗
證過後的商業文件及程序
送出
處理內容
概念說明 七
交易夥伴
交易夥伴
收文
備妥
內容
Trading
Partner
Trading Partner
將回應的內容以信封包裝後
回覆
解開信封
放入信封
送出
處理內容
概念說明 八
交易夥伴
交易夥伴
收文
備妥
內容
Trading
Partner
Trading Partner
交易夥伴間以此模式，依照
RosettaNet規範繼續交談直
解開信封
放入信封
到完成商業程序
送出
處理內容
RosettaNet技術組件

Partner Interface Processes (PIPsTM)

Dictionaries and Codes

RosettaNet Implementation Framework
(RNIF) Core
技術組件-PIP

整合式的商業程序，其中規範了

商業文件的結構及格式

參與商業活動的交易夥伴的活動、決策、及角色扮演
技術組件-PIP

分類方式是依照高階商業功能(cluster)及次功
能(segment)而訂
Cluster 3: Transaction and Distribution
Segment B : Transportation and Distribution
PIP 3B3 – Distribute Shipment Status
PIP 3B4 – Query Shipment Status
PIP 3B18 – Notify of Shipment
Documentation
Segment A : Quote and Order Entry
Segment C : Returns and Finance
技術組件-PIP

PIP規範是可供下載的.zip檔放在Rosettanet網
站，內容包括



規格書(.doc) + 勘誤表
XML DTD說明商業文件的結構內容
訊息使用說明
 編碼、定義、訊息出現次數
技術組件-PIP

規範是遵循Open-EDI Reference Model
(ISO/IEC 14662)的概念制定而成，包括



商業運作觀點(Business Operational View, BOV)
 以商業角度看待商業交易
功能服務觀點(Functional Service View, FSV)
 以技術角度看待商業交易
製作架構觀點(Implementation Framework View, IFV)
 RosettaNet下層技術服務製作的架構
PIP摘要
交易夥伴
PIP規定一個特定商業活動商
業文件的結構及格式
商業文件表示成XML文件
交易夥伴
備妥內容
Trading
Partner
收文
Trading Partner
放入信封
解開信封
送出
PIP也規定交易夥伴間交換
處理內容
文件的協定
技術組件 - 字典
字典
交易夥伴
交易夥伴
備妥內容
Trading
Partner
收文
Trading Partner
放入信封
解開信封
送出
處理內容
標準碼

交易夥伴識別號 (DUNS®)
標準碼使用時機

交易夥伴識別號(DUNS®)

PIPsTM 用來識別交易夥伴及其位址
交易夥伴的識別

DUNS® Numbering






“Data Universal Numbering
System”
Managed by DUN and
Bradstreet
(www.dnb.com)
Nine Digit Number
No Embedded Intelligence
Guaranteed Unique Partner
Identifier
Used in Every RosettaNet
PIPTM
範例
00-825-575 4
------------- |
|
|
----> Check Digit
|
---------------> Company
Identification
總覽
RNIF
LAYERS
POLICY
• PKI
• TPA
• Compliance
SPECS.
• Network
Protocols
Base Spec.
• PIP Metamodel
• PIP Design patterns
• Network Component
Communications Reference
Model
Core
Common
Supply Chain
RNIF簡介

RosettaNet Implementation Framework Core

RNIF (usually pronounced R-NIF)

RNIF 1.1 Defines RosettaNet Object (RNO),
RNIF 2.0 Defines RosettaNet Business Message

Specifies how to transport RosettaNet Objects and Business
Messages between trading partners’ network applications

(Remember those PIPsTM? This is how the Business Document
Payload is packaged and transported.)
RNIF
交易夥伴
交易夥伴
RNIF制定以XML及MIMI為
收文
備妥
內容
Trading
Partner
Trading Partner
依據的“信封套”，以便放
入商業文件
放入信封
解開信封
送出
處理內容
RNIF比較
PIPTM1
PIP2A1B1
PIP3B3
PIP3B4
RNIF 1.1
Preamble
Header +
Service
Header +
RNIF 2.0
RosettaNet
Business
Document
Service
Header +
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Header +
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
The Preamble is the first component of the
service message and contains elements
that are global to the RosettaNet service
PIP 1
and elements thatPIP2A1
are
common to the
B1
Service HeaderPIP3A2
and the Service Content.
TM
PIP3A4
RNIF 1.1
Preamble
Header +
The Preamble Header is an XML document.
RNIF
Service
Header +
RosettaNet
Business
Document
Service
Header +
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
2.0
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Header +
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
The Service Header contains:
• Process Controls
• Transaction Controls
PIP 1
• Action Controls
PIP2A1B1
PIP3A2
• Signal Controls
TM
PIP3A4
RNIF The
1.1Service Header is an XML document. RNIF 2.0
Preamble
Header +
Service
Header +
RosettaNet
Business
Document
Service
Header +
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Header +
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
RNIF




Process Controls identify the RosettaNet PIPTM, version, sender and
receiver services, process instance ID, etc.
Transaction Controls contain info relating to the transaction like
global transaction code, instance ID, etc.
Action Controls contain info related to a specific PIP action. (like is
this request or response)
Signal Controls contain info related to a specific PIP signal. (like
what kind of signal is this)
RNIF
Action/Signal Layer
Transaction Layer
Process Layer
Service Layer
Agent Layer
Application Layer
HTTPS
Session Layer
SSLv3
Transport Layer
HTTP
Transfer Layer
Security Layer
TCP/IP
Network Layer
Data Link Layer
Physical Layer
OSI Layered
Ubiquitous Communications
Reference Model
Internet and WWW
Protocol Stack
RosettaNet Layers
e-Business Communications
Reference Model
The RosettaNet Business Document
or Service Content is the business
document payload as defined by a
particular PIP. Under RNIF 2.0, it
may refer to attachments or consist
of non-RosettaNet
content.
PIP 1
TM
PIP2A1B1
PIP3A2
PIP3A4
The RosettaNet Business Document is
an XML document.
RNIF 1.1
Preamble
Header +
Service
Header +
RosettaNet
Business
Document
RNIF 2.0
Service
Header +
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Header +
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
MIME-Version: 1.0
Content-Type: Multipart/Related;
boundary="RN-part-boundary";
type="Application/x-RosettaNet“
Content-Description: This is the RosettaNet
business message
Technical Components - RNIF
--RN-part-boundary
Content-Type: Application/XML;
RNSubType="preamble-header"
PIP1B1
PIP2A1
Content-Description:
This is the Preamble Header
PIP3A2
part of the business message
PIP3B4
RNIF 1.1
Preamble
Header +
Service
Header +
RNIF 2.0
[The Preamble Header goes here]
RosettaNet
Business
Document
--RN-part-boundary
Content-Type: Application/XML; RNSubType="service-header"
Service
Content-Description: This is the Service
AttachService
Header part of the business+message
Content
+
ments
Header
[The Service Header goes here]
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
S/MIME Envelope
--RN-part-boundary
Encrypted
Content-Type: Application/XML;
Preamble
Delivery
Payload
RNSubType="service-content"
+
+
Header
Header
Container
Content-Description:
This is the Service
Content
part of the business message
+
Digital
Signature
MIME Packaging
[The Business Content goes here]
RosettaNet Object
(RNO)
--RN-part-boundary--
RosettaNet Business
Message
MIME-Version: 1.0
Content-Type: application/pkcs7-mime;
smime-type=enveloped-data;
name=smime.p7m
PIPTM1
Content-Transfer-Encoding: base64
PIPTM2B1
TM
Content-Disposition: attachment; filename=smime.p7mPIP A1
PIPTM
3A2
MIAGCSqGSIb3DQEHA6CAMIACAQAxgDCCASAC
3B4
RNIF 1.1
AQAwgYgwgYIxCzAJBgNVBAYTAlVTMRMwEQYD
VQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhN
b25yb3ZpYTEMMAoGA1UEChMDU1RDMRQwEgYD
RosettaNet
VQQLEwtEZXZlbG9wbWVudDEnMCUGA1UEAxMe
Business
Preamble
Service
+
+
U1RDIFRlc3QgQ2VydGlmaWNhdGUgQXV0aG9y
Document
Header
Header
aXR5AgECMA0GCSqGSIb3DQEBAQUABIGADytB
2IkYlPqgivlcnQiCPJxWDcshCKUaOm9/k07d
MIME Packaging
etAfX0f1LaEA23qFolSmevKrNZcUlMfm32HT
UdZQpHj9Iy8da5GNI9OW+5EB7W7XoiJgyfeD
RNIF
Service
Digital
Preamble
6m2X3UfwnPJJUnOlC6klVBzpalFHXOw5rK2Z
+
+
Version ID
Message
Signature
Header +
eGIGjiPiIq4p1DmkKlfLle4wggEgAgEAMIGI
MIGCMQswCQYDVQQGEwJVUzETMBEGA1UECBMK
Q2FsaWZvcm5pYTERMA8GA1UEBxMITW9ucm92
...
RosettaNet Object
(RNO)
RNIF 2.0
Service
Header +
Service
Content
+
Attachments
S/MIME Envelope
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Business
Message
PIPTM
PIP2A1
1B1
PIP3A2
PIP3A4
The version ID identifies
RosettaNet Implementation
Framework version for
interoperability purposes. Part
RosettaNet
of the RNIF 2.0 Preamble
Business
Service
Document
Header serves the same
Header +
purpose.
RNIF 1.1
Preamble
Header +
Service
Header +
RNIF 2.0
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Header +
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
PIPTM
PIPTM1B1
2A1
PIP3A2
PIP3B4
RNIF 1.1
Preamble
Header +
Service
Header +
RosettaNet
Business
Document
MIME Packaging
RNIF
Version ID +
Service
Message +
Digital
Signature
RNIF 2.0
The RosettaNet Object is
created by concatenating the
Version ID, Service Message,
Service
AttachSignature
Length and
Service
Content
+
ments
Header +
Signature.
The RosettaNet Object S/MIME
is sentEnvelope
Encrypted
to the trading
using
Preamble
Delivery partner
Digital
Payload
+
+
+
Header
Signature
Container
HTTPSHeader
…
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
RNIF 1.1
…while the RosettaNet
Business Message wraps
everything using standard
RosettaNet
Business
Preamble
Service
MIME packaging.
+
+
Header
Header
RNIF 2.0
Service
Header +
Document
The RosettaNet Business
MIME Packaging
Message may be sent using
RNIF HTTPS
Service
Digital
HTTP,
or SMTP
+
+
Version ID
Message
Signature
(other protocols to be
specified in the future).
RosettaNet Object
(RNO)
PIPTM
1B1
PIP2A1
PIP3A2
PIP3B4
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Header +
Delivery
Header
+
Encrypted
Payload
Container
+
Digital
Signature
MIME Packaging
RosettaNet Business
Message
RNIF 2.0

Support for multiple transfer protocols

Transfer-independent message format (MIME &
S/MIME)

Support for both SMTP and HTTP(S)

FTP, message queues, and others in the future

Transfer-level headers for debugging
RNIF 2.0

Support for end-to-end and persistent encryption

S/MIME-based packaging for digital signatures and
content enveloping

Support for attachments and message manifest

Support for 3rd party (hub-based) routing (due to
Delivery Header)
3B18






RN3B18 is to carry elements of “Invoice” and
“Packing List” to the other party for declaration and
cargo documents.
“Invoice” is for billing to the buyer.
“Packing List” tells the consignee how to pack the
cargo (including the information of dimension, weight,
pieces, packing method….).
Invoice No. ：Packing List No.
=
1
：
1
(generic)
=
n
：
1
(specific)
續
1:N
ShipmentKey
1:M
PackingListNo
InvoiceNo
p.s. N, M > 0
Generic
--
As per shipper’s request
A shipment is grouped by pre-assigned HAWB
by internal serial number
續
TYPE A
INV-1 INV-2 INV-3
PAK-A
PAK-B
Packing List for
INV-1,INV-2
Packing List for
INV-3
RN3B18
INV-1
PAK-A
RN3B18
INV-2
PAK-A
RN3B18
INV-3
PAK-B
TYPE B
INV-1 INV-2 INV-3
PAK-A
PAK-B
Packing List for
INV-1,INV-2
Packing List for
INV-3
RN3B18
INV-1
RN3B18
INV-2
RN3B18
INV-3
RN3B18
PAK-A
RN3B18
PAK-B
3B18 PIP 使用對象



Electronic Components (EC)
Information Technology (IT)
Semiconductor Manufacturing (SM)
3B18 BOV

參與角色



Seller
Buyer
3PL or 4PL
3B18 BOV

內容




Bill of Landing
Commercial Invoice
Packing List
…
3B18 BOV
: Shipper
: Shipping Prov ider
START
<<NotificationActivity>>
Notify of Shipping
Documentation
[ SUCCESS ]
END
<<SecureFlow>>
Shipping Documentation
Notification
[ FAIL ]
FAILED
Receive Shipping
Documentation
3B18 FSV
: Shipper
Service
: Shipping
Provider Service
1. request(ShippingDocumentationNotificationAction)
1.1 signal(ReceiptAcknowledgement)
3B18 IFV
Table 5-1: Business Message and Communications Specification
#
Business Message Guideline
Digita
l
Signa
ture
Requi
red?
SSL[
1]
Requ
ired?
1.
Shipping Documentation Notification Guideline
Y
Y
1.1.
Receipt Acknowledgment Guideline
Y
Y
應用範例
流程
出貨
指示
取貨
訂艙
資訊
進倉
國內
清關
起飛
到達
國外
清關
到貨
簽收
訊息
3B18
N/A
3B3
3B3
3B3
3B3
3B3
3B3
3B3
文件
Invoice No.
Packing List
報單
艙單
艙單
報單
簽收單
(POD)
N/A 進倉計畫 托運單
提供者
Shipper
N/A
承攬業
承攬業
報關業
交換
對象
承攬業者
N/A
貨棧
貨棧
Shipper
通關網/
Overseas
航空公司 航空公司 Overseas
Agents
Agents
海關
目的地
海關
Shipper Shipper
承攬業 承攬業
3B3,3B4 PIP 使用對象


Electronic Components (EC)
Information Technology (IT)
3B3 BOV

The "Distribute Shipment Status" Partner
Interface Process™ (PIP) enables a
transport service provider to distribute
shipment status information to another party,
such as a consignee, a third-party logistics
firm, a shipper, or another transport service
provider.
應用範例
流程
出貨
指示
取貨
訂艙
資訊
進倉
國內
清關
起飛
到達
國外
清關
到貨
簽收
訊息
3B18
N/A
3B3
3B3
3B3
3B3
3B3
3B3
3B3
文件
Invoice No.
Packing List
報單
艙單
艙單
報單
簽收單
(POD)
N/A 進倉計畫 托運單
提供者
Shipper
N/A
承攬業
承攬業
報關業
交換
對象
承攬業者
N/A
貨棧
貨棧
Shipper
通關網/
Overseas
航空公司 航空公司 Overseas
Agents
Agents
海關
目的地
海關
Shipper Shipper
承攬業 承攬業
3B3 BOV
3B3 SFV
3B4

The "Query Shipment Status" Partner
Interface Process™ (PIP) enables (1) a party,
such as a consignee, third-party logistics
firm, or shipper, to query for the status of
one or more shipments, and (2) a transport
service provider to answer the query.
3B4 BOV
3B4 FSV
3B3 & 3B4
RN3B4 & RN3B3 Collaboration Flow
Shipper/Consignee
1. Request Shipment Status
2. Response Shipment Status
3. Follow-up Response Shipment Status
BEGIN
END
END
Create Shipment
Status Query
Process
Shipment Status
Response
Process
Shipment Status
Information
Send Message
Receive
Receive
3B4(Request)
3B4(Response)
Receive
Send Message
3B3
Tradevan
Send Message
Process
Shipment Status
Query
Create Shipment
Status
Response
Collect
Shipment Status
Information
BEGIN
挑戰

There are many “standards” from which to choose.

The specifications are being improved, which means they are
changing.

Some aspects of the specifications are ambiguous.

The readability of the existing documentation needs to be
improved.

The enterprise readiness effort for RosettaNet implementations
is often underestimated.
導入準則

Base on “Shipping & Logistics for IT Manufacture Project(SLIM)
for Plan D”
導入準則
測試進程




Level 0:Partner Engagement
Level 1:Connectivity
Level 2:Syntax & Domain Value Checking
Level3 : Data Content Validation
SAP R/3 IDOC Connector



SAPR3 IDoc Source Connector
SAPR3 IDoc Target Connector
Both implement SAP’s tRFC protocol
SAPR3 IDoc Source Connector





Receive IDOCs from a SAP/R/3 system
Generate BusinessWare events (String)
Send to Record Mapper
Convert it into IDL events (by using
MTDParser)
Pushs it to the Channel Target flow to
publish to channels
SAPR3 IDoc Target Connector



A multi-threaded Subscriber flow receives
IDL events
Record Mapper converts it into String event
IDOC target flow converts the events into
IDOCs and pushes them to SAP/R3