Trading Partne Recei gure 9-8 Fund 9.3.3 Business document Business document definitions are the specifications for the business document schemas and information components that compose the business document and contained information components. A schematic representation of a business document can be seen in Figure 9-9. beloy Example: Purchase Order Information component Order nformation Component rmation Componen Information component OrderDetail OrderDetail OrderSumma Figure 9-9 Document Conceptual View Documents such as Purchase Orders, Invoices, etc, exist at the business process level and are exchanged in business transactions by means of placing documents into document envelopes Documents are put into document envelopes. They are addressed with the business identifier (e.g. DUNS number)of the recipient and sender. This is analogous to the "Attention: "line on a standard mailing address. A document envelope is placed into a message envelope and is exchanged between business service interfaces. The message envelope might be addressed with the urn of the destination business service interface. messages have timeouts and other transaction control mechanisms associated with them. Message envelopes are placed into a transport/routing envelope for low level transmission across an e-business network. The target ddress on message envelope might be the URL of the destination's message-in-box service. A logical view of the nested envelope structure is shown in Figure 9-10Send Receive Trading Partner Trading Partner Figure 9-8 Functional Service View: Run Time Phase 9.3.3 Business document Business document definitions are the specifications for the business document schemas and the information components that compose the business document and contained information components. A schematic representation of a business document can be seen in Figure 9-9, below. Figure 9-9 Document Conceptual View Documents such as Purchase Orders, Invoices, etc., exist at the business process level and are exchanged in business transactions by means of placing documents into document envelopes. Documents are put into document envelopes. They are addressed with the business identifier (e.g. DUNS number) of the recipient and sender. This is analogous to the “Attention:” line on a standard mailing address. A document envelope is placed into a message envelope and is exchanged between business service interfaces. The message envelope might be addressed with the URN of the destination business service interface. Messages have timeouts and other transaction control mechanisms associated with them. Message envelopes are placed into a transport/routing envelope for low level transmission across an e-business network. The target address on message envelope might be the URL of the destination’s message-in-box service. A logical view of the nested envelope structure is shown in Figure 9-10