A Receipt Acknowledgment is a positive signal acknowledging receipt of a Business action message. 1 1 Supports a process for trading partners to issue and acknowledge new purchase orders. Allows partners to exchange price and availability information, quotes, purchase orders and order status, and enables partners to send requested orders, or shopping carts, to other partners The collection of business properties that allows the description of multiple proprietary documents and applicable line number references. Information required to support non-repudiation of receipt. The collection of business properties that describe a business document entry for a product 1 1 Provides a quick, automated process for trading partners to request and provide product price and availability. incoming message of a request for a quote (request_quote) contact information of a partner. Includes contact_name, phone, and email. cross-enterprise processes involving more than one type of trading partner This header identifies the PIP, the PIP instance, the activity, and the action to which this message belongs. The collection of business properties that describe the occurrence of the public conveyance of goods as a commercial enterprise. The collection of business properties that describe a business identity and location Business information returned to a requesting party if a business processing error occurs. incoming message for RequestShoppingCartTransfer Provides a quick, automated process for trading partners to transfer the contents of a shopping cart and reply to the transfer. 1 1 The collection of business properties that describe the nature of business processing errors. Lets buyers provide daily inventory reports to sellers, allows sellers to notify buyers when reports are reflected in their records and enables sending of discrepancy reports The collection of business properties that describe a product's time frame for being available to a customer This header identifies message sender and recipient and message instance information. This information is placed separately from the Service Header to allow access to the information by a Hub when the Service Header is encrypted. The collection of business properties that describe the parametric query for product's price and availability. outgoing message of a request for a quote (request_quote) incoming message of a request for a purchase order Provides for issuance of billing, payment and reconciliation of debits, credits and invoices between partners as well as supports product return and its financial impact The collection of business properties that describe an offer to supply a quantity of products at an agreed price and schedule. incoming message for request_price_and_availability Preamble>DeliveryHeader>ServiceHeader>Message or business signal Business signals are positive and negative acknowledgment messages that are sent in response to business actions. Enables inventory management, including collaboration, replenishment, price protection, reporting and allocation of constrained product outgoing message of a request for a purchase order Total price for the entire business document, including freight, tax and special handling if applicable. The collection of business properties that describe a buyer's offer to purchase a quantity of products at an agreed price and schedule. outgoing message in a order_status_query outgoing message for request_price_and_availability Partner Interface Process - protocol of outgoing and incoming messages representing resquests and response dialogue. The collection of business properties that describe a business partners' identity and their function in a supply chain groups of core business processes, that represent the backbone of the trading network. The collection of product descriptions, quantities and prices that comprise a buyer's intent to purchase Message incoming to initiator of transaction, example: xxx_repsonse, xxx_acknowledgement, xxx_confirmation 1 1 Supports a process for trading partners to cancel and change purchase orders, and acknowledge changes, as well as provides an automated process for product sellers to report order status on all open orders -- those that have not been shipped -- on a periodic basis agreed upon in their trading partner agreement. Message outgoing from initiator of transaction, example: xxx_request, xxx_query, xxx_order The collection of business properties that describe a product entry for a product price and availability business document. Information identifying a participant in the transaction. Agreed upon sale price for each unit ordered, has currency and monetrary amount information 1 1 Support process for requesting a quote This header identifies the standard with which this message structure is compliant. Incoming message in a order_status_query The collection of business properties that describe a product's price and availability. outgoing message for RequestShoppingCartTransfer The collection of business properties that describe a product entry in a quote business document. The collection of business properties that describe a business partners' identity and their function in a supply chain. has a document reference Global unique product identifier. RosettaNet has adopted the Global Trade Identification Number (GTIN). Code identifying a partner's function in the supply chain. A unique identifier for referencing shopping cart descriptions Code identifying the status of a shopping cart Name of the contact person(s) within the organization. Code identifying the supply chain for the partner's function. A unique business identifier. The DUNS number is specified by RosettaNet. Indicates whether the requesting business document will permit additional information to be returned on the responding document. requested quantity specifying the number of product units. the proprietary_document_id of the requesting document. The version of the message standard used to create the message. The name of the administering authority of the applicable standard that is being followed. Identifies a message component, e.g. Preamble, Delivery Header, Service Header, that caused the exception. the date/timestamp of the requesting document Electronic mail address The base-64 encoded digest of the entire original mime message received. The digest MUST use the same algorithm as the original signed message. Code identifying the function of a document as either a request or a response. Number of the line in the document An internal identifier used to identify a product. Code identifying the three character currency code specified in ISO 4217-1995. Code identifying a product unit of measure. The numerical schema designed to achieve contact via telephone. A complete description of the nature and source of error. Magnitude of currency amount. Identifies the specific error which occurred during message processing. A unique identifier specifying the type of exception encountered during message processing. Code identifying a partner's function in the supply chain. Specifies an instance in time. Based on the ISO 8601 specification where "YYYY" represents the year, "MM" the month and "DD" the day. The letter "T" is the date/time separator and "hh", "mm", "ss.sss" represent hour, minute and second respectively. This representation is immediately followed by a "Z" to indicate Coordinated Universal Time. Informal format: YYYYMMDDThhmmss A quantity specifying the number of product units. A quantity specifying the estimated number of product units available.