Clickable Business Models eBusiness Education Acronyms Cross References
B2B Content Standards EC Technology Standards Glossary Implementation Guidelines
Implementation Options General Recommendations References Methodology/Legends
 Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search
 Inventory Models Index | Supporting Documentation | Downloads | FAQs |

Inventory Management Model 1 - Report Inventory Levels, Buyer to Seller, Version 1.0
Status:  Provisional Draft in process.  Created as part of recast of Consignment Scenarios (Balloted and Ratified by Membership, August 1998)

Implementation Option 3c - Integrated B2B, no VAN, using RosettaNet Standard

Special Notes:                   
Introduction
Activity Diagram
Narrative
 
In Technology Option 3 (Generic) Section:
General Information About This Technology
Business User View
 

Introduction

In this example, both buyer and seller support the RosettaNet standard, and the same messaging standards, including security and transport protocols.  The buyer is using a solution where the Enterprise Integration Application pulls data from the buyer's back-end system to the
B2B gateway, and the seller is using a solution that pushes data from the back-end application to the B2B gateway.

In practice, a company with either type of B2B gateway process (push vs. pull) can exchange data with companies that have either type of B2B gateway process.

RosettaNet has specific requirements for transport and routing, as specified in the RosettaNet Implementation Framework.


Activity Diagram (See also Narrative)

Smaller Print Version of Diagram


Narrative (see also Graphic):

Step Description
In this example, both buyer and seller support the same B2B business content standard, and the same messaging standards, including security and transport protocols. 
A. At start state A, the buyer is ready to create an inventory report.  The trading partners have a relationship already established; all applications and parties involved in the exchange have the correct configurations established, including registration of the trading partnership in both B2B gateways.
1. The buyer creates an inventory report in the back-end application.  The buyer may save it if it is not ready to send, or may mark it as ready to be transmitted and/or printed.  
2. The EAI software or other B2B gateway application extracts the inventory report data.   The data may be extracted into a proprietary or application-specific format such as SAP IDOC, Oracle data file, Baan EDI file, and so on, or it may be extracted into a standard XML format.
3. If the backend application does not generate RosettaNet XML natively, the B2B gateway application maps (translates) the application file into RosettaNet XML.
4. The document (the payload) is packaged into a RosettaNet Business Message for transmission to the seller (a/k/a Wrapping, Enveloping) per the RNIF
  • RosettaNet Implementation Framework (RNIF) version 1.1 requires RosettaNet-specific packaging that results in the creation of a package called a "RosettaNet Object" (RNO); only a RosettaNet payload can be contained in the package.
  • RosettaNet Implementation Framework (RNIF) version 2.0 is a step towards converging on the ebXML TR.  It uses a more standard enveloping (S/MIME), and allows the inclusion of attachments containing non-RosettaNet payloads.
5. EIDX recommends that a sender validate their own outbound documents for compliance with the standards before sending the documents to a trading partner.  More.
6. The business document is authenticated electronically through the attachment of a digital signature, and is encrypted in preparation for secure transporting.
7. Inventory reports are sent to the trading partner.  Typically, the buyer's B2B gateway is given a secure login to a directory on the seller's gateway server, where the buyer deposits documents intended for the seller.  Buyers can access only their own directories, and no buyer can access another buyer's directory.
B. Start state B indicates that the seller's gateway is checking the server for deposited files independently from the inventory report process.  Typically, the seller's B2B gateway polls trading partner directories every n seconds to n minutes to see if any files have been received.
8. When files have been received, the B2B gateway routes the files to a another directory.  The presence of files in this other directory invokes the appropriate processing.
9. The data is decrypted.
10. The seller unwraps (opens) the Business Message.
11. The seller checks the incoming document for compliance against the standard.
12. If required by the buyer, the seller creates a Receipt Acknowledgment, which indicates that the seller received the inventory report document at their gateway, and whether or not it passed the compliance check.  Just like the inventory report document, the Receipt Acknowledgment needs to be packaged and validated before being sent.  Unlike the inventory report, which is a "document", the Receipt Acknowledgment is classified as a "service" transaction.
  • RosettaNet requires the use of a Receipt Acknowledgment.
13. If necessary, the B2B gateway application maps (translates) the file into the format expected by the back-end application.
14. The seller processes the inventory report to load it into their back-end application. 
B. At End State B, the seller has processed the Inventory Report.
15. Just like the inventory report document, the Receipt Acknowledgment needs to be packaged and validated before being sent.  Unlike the inventory report, which is a "document", the Receipt Acknowledgment is classified as a "service" transaction.
16. The documents are transferred as in the buyer's step 7 above.
17. When files have been received, the B2B gateway routes the files to a another directory.  The presence of files in this other directory invokes the appropriate processing.
18. If it is used, the buyer decrypts and unwraps (opens) and validates the Receipt Acknowledgment.  Unlike the inventory report, which is a "document", the Receipt Acknowledgment is classified as a "service" transaction.  A Receipt Acknowledgment is never created in response to an Receipt Acknowledgment!
19. The status of the inventory report transmission is updated in the gateway to indicate that the transmission was received by the seller.
C. End state E, the PIP is concluded.

Last updated 02 March 2003