《RosettaNet简介.ppt》由会员分享，可在线阅读，更多相关《RosettaNet简介.ppt（76页珍藏版）》请在三一办公上搜索。
1、RosettaNet簡介,報告人：關貿網路 朱啟光,前言,電子商務的發展從提供型錄式資訊服務的電子商店(B2C)，演進到企業間(B2B)商業處理自動化企業間商業標準架構應運而生RosettaNet、ebXML、BizTalk。,模式一,Company A,ERP,Web server,Company B,Internet,模式二,ERP,ERP,Company A,Company B,Internet,B2B EC的演進,商業應用程式間的交談，達成企業間商業交易建立在標準的商業流程及商業文件之上因此標準的制定，便形成B2B EC的重要工作,EDI,Business process and do
2、cument integration,B2B EC 標準架構,商業處理層標準商業流程及商業文件，技術服務層安全可靠的溝通管道，做為上層運作的基礎,商業處理層,技術服務層,各種標準水平整合:ebXML產業垂直整合:RosettaNet(資訊技術、電子零組件、及半導體製造業)技術服務架構:Vitria Framework,BizTalk Framework,ebXML 簡介,1999年9月由聯合國制定電子商務標準的組織OASIS和UN/CEFACT共同推動的企業間電子商務標準。EbXML主要任務在於提供一個開放式的XML底層架構，以利各方在安全、一致的環境下達成共通的電子商務資訊互動。其基本訴求為
3、使用XML技術，提供不同規模的企業間的垂直和水平整合。提供低成本的軟體製作，供中小企業之用，也顧到大企業的需求。通用性的處理程序、用語、及編碼。制定註冊機制以達成開放性及提高互通性。提供安全的遞送路徑、封包方式以確保商業訊息送收的安全。,ebXML架構說明,A,公,司,B,公,司,ebXML相容註用及儲存庫,B2B EC,架構,概念圖,1.取得ebXML規範,2.製作ebXML相容軟體,3.製作並登錄CPP,4.查訊得知並,取得A公司的商,業處理能力及,細節,5.向A公司請求,做ebXML式交,易，同意後便,進行軟體製作,6.初使化動作過後，程式間便依之前協定進行商業交談,RosettaNet
4、,一個非營利協會所制定的企業間電子商務標準主要目的是為高科技的資訊技術、電子零組件、及半導體製造產業建立供應鏈管理體系RosettaNet所定的B2B EC是一個具有上層商業處理與下層技術服務的整體架構在上層商業處理方面，主要在於制定企業夥伴間標準商業處理程序依照功能性共分成七群(cluster)核心商業處理程序，包括交易夥伴及商品資訊之收集、維護，產品資訊之分送及更新，訂單管理，庫存管理，市場資訊管理，售後服務及支援，製造資訊之交換每一群又分成幾個段(segment)，每段含有幾個夥伴間程序介面(partner interface process,PIP)每個PIP定義程式對程式間以XML標
5、準商業文件為基礎的對話程序,抽象概念,RosettaNet,從商業運作的角度來看，一個PIP主要內容是特定的商業工作流程及其流程中所帶動的文件,為求文件一致，RosettaNet定義了商業和技術字典，前者為提供商業詞彙，後者為各行業的技術用語,RosettaNet制定了RNIF(RosettaNet Implementation Framework)，當中定義了工作平台間訊息交換協定(protocol)，以支應上層PIP在文件遞送上的基礎,形成需求文件,需求處理,形成回應文件,回應處理,PIP,成功,失敗,買方,賣方,商業資訊決策系統,商業資訊決策系統,RosettaNet,對照前面ebXML
6、的架構，RosettaNet提供完整的商業處理程序及工作平台RosettaNet並不制定註冊機制及CPP/CPA，因此在商業夥伴的探索及建立夥伴關係上必須靠人工達成UDDI(Universal Description,Discovery Integration)by IBM,Microsoft and Ariba另一個B2B EC標準Vitria Framework則是制定了相當於RNIF角色的下層技術服務,RosettaNet 宗旨及任務,宗旨Dynamic,flexible trading networksOperational efficiencyNew business opportu
7、nities任務促進網際網路商業標準的合作發展及快速建置創造共通的商業語言及開放式的電子化商業程序，為全球高科技交易網路帶來利益及提昇演進的腳步,什麼是RosettaNet,RosettaNet是由超過400家資訊技術業、電子零組件業、及半導體製造業廠商所組成的協會，共創及推廣開放式的電子標準商業程序RosettaNet名稱是以the Rosetta Stone而得名 RosettaNet創造電子商務標準語言，包括商業程序及商業文件促成供應鏈電子化建立有彈性的交易夥伴關係降低成本、提昇產量,什麼是RosettaNet標準內容,RosettaNet標準是集合高科技公司的專業知識，共創而成的非獨占
8、性的電子商務方案，其內容包括商業及技術字典 RosettaNet Business Dictionary、RosettaNet Technical Dictionary下層技術服務架構RosettaNet Implementation Framework(RNIF)商業訊息及程序規範RosettaNet Partner Interface Processes(PIPs)以上標準規範可由免費取得,概念說明 一,備妥內容放入信封送出,交易夥伴,提出需求的交易夥伴準備好商業文件，載明需求內容,概念說明 二,備妥內容放入信封送出,交易夥伴,備妥的商業文件包裝成XML及MIME規格做成的傳輸信封內,概念
9、說明 三,備妥內容放入信封送出,交易夥伴,用預定的埠際協定(HTTP(s)、SMTP等)送到交易夥伴的URI,概念說明 四,Trading Partner,備妥內容放入信封送出,交易夥伴,交易夥伴收到信件,Trading Partner,收文解開信封處理內容,交易夥伴,概念說明 五,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,交易夥伴,解開以檢驗信封內的處理資訊及商業文件是否正確,概念說明 六,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,交易夥伴,
10、根據RosettaNet規範處理驗證過後的商業文件及程序,概念說明 七,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,交易夥伴,將回應的內容以信封包裝後回覆,概念說明 八,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,交易夥伴,交易夥伴間以此模式，依照RosettaNet規範繼續交談直到完成商業程序,RosettaNet技術組件,Partner Interface Processes(PIPsTM)Dictionaries and Codes Rose
11、ttaNet Implementation Framework(RNIF)Core,技術組件-PIP,整合式的商業程序，其中規範了商業文件的結構及格式參與商業活動的交易夥伴的活動、決策、及角色扮演,技術組件-PIP,分類方式是依照高階商業功能(cluster)及次功能(segment)而訂,Cluster 3:Transaction and Distribution,Segment B:Transportation and Distribution,Segment C:Returns and Finance,Segment A:Quote and Order Entry,PIP 3B3 Dis
12、tribute Shipment StatusPIP 3B4 Query Shipment StatusPIP 3B18 Notify of Shipment Documentation,技術組件-PIP,PIP規範是可供下載的.zip檔放在Rosettanet網站，內容包括規格書(.doc)+勘誤表XML DTD說明商業文件的結構內容訊息使用說明編碼、定義、訊息出現次數,技術組件-PIP,規範是遵循Open-EDI Reference Model(ISO/IEC 14662)的概念制定而成，包括商業運作觀點(Business Operational View,BOV)以商業角度看待商業交易功
13、能服務觀點(Functional Service View,FSV)以技術角度看待商業交易製作架構觀點(Implementation Framework View,IFV)RosettaNet下層技術服務製作的架構,PIP摘要,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,交易夥伴,PIP規定一個特定商業活動商業文件的結構及格式商業文件表示成XML文件,PIP也規定交易夥伴間交換文件的協定,技術組件-字典,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,
14、交易夥伴,字典,標準碼,交易夥伴識別號(DUNS),標準碼使用時機,交易夥伴識別號(DUNS)PIPsTM 用來識別交易夥伴及其位址,交易夥伴的識別,DUNS Numbering“Data Universal Numbering System”Managed by DUN and Bradstreet()Nine Digit NumberNo Embedded IntelligenceGuaranteed Unique Partner IdentifierUsed in Every RosettaNet PIPTM,範例,00-825-575 4-|-Check Digit|-Company
15、Identification,總覽,RNIF簡介,RosettaNet Implementation Framework CoreRNIF(usually pronounced R-NIF)RNIF 1.1 Defines RosettaNet Object(RNO),RNIF 2.0 Defines RosettaNet Business MessageSpecifies how to transport RosettaNet Objects and Business Messages between trading partners network applications(Remembe
16、r those PIPsTM?This is how the Business Document Payload is packaged and transported.),RNIF,Trading Partner,備妥內容放入信封送出,交易夥伴,Trading Partner,收文解開信封處理內容,交易夥伴,RNIF制定以XML及MIMI為依據的“信封套”，以便放入商業文件,RNIF比較,RosettaNet Object(RNO),Service Header,Preamble Header,+,+,Digital Signature,RNIF Version ID,+,+,MIME Pa
17、ckaging,Service Message,RosettaNet Business Message,Service Header,Preamble Header,+,MIME Packaging,Encrypted Payload Container,Delivery Header,Digital Signature,S/MIME Envelope,+,+,+,RNIF 1.1,RNIF 2.0,+,Attach-ments,Service Content,RosettaNet Business Document,RosettaNet Object(RNO),Service Header,
18、Preamble Header,+,+,Digital Signature,RNIF Version ID,+,+,MIME Packaging,Service Message,RosettaNet Business Message,Service Header,Preamble Header,+,MIME Packaging,Encrypted Payload Container,Delivery Header,Digital Signature,S/MIME Envelope,+,+,+,RNIF 1.1,RNIF 2.0,+,Attach-ments,Service Content,Ro
19、settaNet Business Document,The Preamble is the first component of the service message and contains elements that are global to the RosettaNet service and elements that are common to the Service Header and the Service Content.The Preamble Header is an XML document.,RosettaNet Object(RNO),Service Head
20、er,Preamble Header,+,+,Digital Signature,RNIF Version ID,+,+,MIME Packaging,Service Message,RosettaNet Business Message,Service Header,Preamble Header,+,MIME Packaging,Encrypted Payload Container,Delivery Header,Digital Signature,S/MIME Envelope,+,+,+,RNIF 1.1,RNIF 2.0,+,Attach-ments,Service Content
21、,RosettaNet Business Document,The Service Header contains:Process Controls Transaction Controls Action Controls Signal ControlsThe Service Header is an XML document.,RNIF,Process Controls identify the RosettaNet PIPTM,version,sender and receiver services,process instance ID,etc.Transaction Controls
22、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,The RosettaNet B
23、usiness 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.The RosettaNet Business Document is an XML document.,Technical Components-RNIF,MIME-Version:1.0Content-Type:Multipart/Re
24、lated;boundary=RN-part-boundary;type=Application/x-RosettaNet“Content-Description:This is the RosettaNet business message-RN-part-boundary Content-Type:Application/XML;RNSubType=preamble-header Content-Description:This is the Preamble Header part of the business message The Preamble Header goes here
25、-RN-part-boundary Content-Type:Application/XML;RNSubType=service-header Content-Description:This is the Service Header part of the business message The Service Header goes here-RN-part-boundary Content-Type:Application/XML;RNSubType=service-content Content-Description:This is the Service Content par
26、t of the business message The Business Content goes here-RN-part-boundary-,MIME-Version:1.0Content-Type:application/pkcs7-mime;smime-type=enveloped-data;name=smime.p7mContent-Transfer-Encoding:base64Content-Disposition:attachment;filename=smime.p7mMIAGCSqGSIb3DQEHA6CAMIACAQAxgDCCASACAQAwgYgwgYIxCzAJ
27、BgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhNb25yb3ZpYTEMMAoGA1UEChMDU1RDMRQwEgYDVQQLEwtEZXZlbG9wbWVudDEnMCUGA1UEAxMeU1RDIFRlc3QgQ2VydGlmaWNhdGUgQXV0aG9yaXR5AgECMA0GCSqGSIb3DQEBAQUABIGADytB2IkYlPqgivlcnQiCPJxWDcshCKUaOm9/k07detAfX0f1LaEA23qFolSmevKrNZcUlMfm32HTUdZQpHj9Iy8da5GNI9OW+5EB7W7X
28、oiJgyfeD6m2X3UfwnPJJUnOlC6klVBzpalFHXOw5rK2ZeGIGjiPiIq4p1DmkKlfLle4wggEgAgEAMIGIMIGCMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTERMA8GA1UEBxMITW9ucm92.,The version ID identifies RosettaNet Implementation Framework version for interoperability purposes.Part of the RNIF 2.0 Preamble Header serves th
29、e same purpose.,The RosettaNet Object is created by concatenating the Version ID,Service Message,Signature Length and Signature.The RosettaNet Object is sent to the trading partner using HTTPS,while the RosettaNet Business Message wraps everything using standard MIME packaging.The RosettaNet Busines
30、s Message may be sent using HTTP,HTTPS or SMTP(other protocols to be specified in the future).,RNIF 2.0,Support for multiple transfer protocolsTransfer-independent message format(MIME&S/MIME)Support for both SMTP and HTTP(S)FTP,message queues,and others in the futureTransfer-level headers for debugg
31、ing,RNIF 2.0,Support for end-to-end and persistent encryptionS/MIME-based packaging for digital signatures and content envelopingSupport for attachments and message manifestSupport for 3rd party(hub-based)routing(due to Delivery Header),3B18,RN3B18 is to carry elements of“Invoice”and“Packing List”to
32、 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),續,ShipmentKey,PackingListNo,
33、InvoiceNo,1:N,1:M,p.s.N,M 0,Generic-As per shippers request A shipment is grouped by pre-assigned HAWBby internal serial number,續,3B18 PIP 使用對象,Electronic Components(EC)Information Technology(IT)Semiconductor Manufacturing(SM),3B18 BOV,參與角色SellerBuyer3PL or 4PL,3B18 BOV,內容Bill of LandingCommercial I
34、nvoicePacking List,3B18 BOV,3B18 FSV,3B18 IFV,應用範例,出貨指示,取貨,訂艙資訊,進倉,國內清關,起飛,到達,國外清關,到貨簽收,流程,訊息,3B18,N/A,3B3,3B3,3B3,3B3,3B3,3B3,3B3,交換對象,承攬業者,N/A,貨棧,貨棧,Shipper,海關,目的地海關,Shipper承攬業,Shipper承攬業,3B3,3B4 PIP 使用對象,Electronic Components(EC)Information Technology(IT),3B3 BOV,The Distribute Shipment Status Pa
35、rtner 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,3
36、B3,3B3,交換對象,承攬業者,N/A,貨棧,貨棧,Shipper,海關,目的地海關,Shipper承攬業,Shipper承攬業,3B4由shipper主動對Hub或LSP發出查詢貨況,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
37、)a transport service provider to answer the query.,3B4 BOV,3B4 FSV,3B3&3B4,挑戰,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 i
38、mproved.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 EngagementLevel 1:ConnectivityLevel 2:Syntax&Domain Value CheckingLevel3:Data Content Validation,SAP R
39、/3 IDOC Connector,SAPR3 IDoc Source ConnectorSAPR3 IDoc Target ConnectorBoth implement SAPs tRFC protocol,SAPR3 IDoc Source Connector,Receive IDOCs from a SAP/R/3 systemGenerate BusinessWare events(String)Send to Record MapperConvert 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 eventsRecord Mapper converts it into String eventIDOC target flow converts the events into IDOCs and pushes them to SAP/R3,
