xCBL 3.0 XML Document Definitions


    • AuctionCreate: A message used to initiate an auction within a portal-based auction related service. The AuctionCreate can be used to set up either a forward or a reverse auction. Rules for bidding, winner determination as well as customer defined auctioning rules can be specified within this document. Multiple items can be set up for auction along with details on pricing, ordering, and delivery options.
    • AuctionCreateResponse: A message used by portal-based auction related services to provide information and status related to the request to create an auction via the AuctionCreate message. The response can also include portal services initiated changes to the AuctionCreate.
    • AuctionResult: A message used by portal-based auction related services to report the results of a given auction. The winning bid(s) will be returned to the initiator of the auction along with any relevant pricing or order related details. Depending on how the auction initiator has set up the auction, all participant bid can also be returned for reporting or comparison purposes.
    • AuctionResultResponse: A message to acknowledge receipt of an AuctionResult document by the auction initiator. In the case that the AuctionResult was not successfully received, the auction initiator may specify in the response document that the portal-based auction related service resend the AuctionResult document.


    • AvailabilityToPromise: Asynchronous document for querying availability and/or ability to commit.
    • AvailabilityToPromiseResponse: Application-level response to the AvailabilityToPromise.

    Catalog Content 

    • ProductCatalog: Covers the pricing and product descriptions for catalog content, and has a self-describing set of extensions for further characterizing products and services offered. May be used to transfer self-configured product characteristics as well.

    Message Management 

    • MessageAcknowledgement: A message sent from one Connector to another Connector. The message is sent from the Business Document receiving Connector to the Business Document sending Connector and only indicates that the Business Document was successfully received. The use of the message is optional since some Connectors may or may not report protocol level errors.

    Invoicing and Payment 

    • Invoice: A message sent from the seller to the buyer notifying the buyer that payment is due for the goods or services detailed in the invoice supplied under conditions agreed between the buyer and the seller. An invoice may refer to goods, items or services related to one or more orders. An invoice may contain references to payment terms and transport.
    • PaymentRequest: A message to arrange for payment of a specified value amount to a beneficiary in settlement of a business transaction. The payer can initiate a Payment Request to instruct its financial institution to debit its' account by the specified amount to be paid to the beneficiary for goods and services rendered. The Payment Request can reference multiple documents and consolidated payment is supported. The payer can send multiple payment requests in a single payment request document. From the information in this document the financial institution will have all the details necessary to debit the payer's account and process the payment to the specified supplier's bank.
    • PaymentRequestAcknowledgment: A message sent to the payer by the financial institution to acknowledge receipt of a Payment Request document and also to inform of any errors in the business data.
    • RemittanceAdvice: A message sent from the payer to the beneficiary to serve as notice that the payment process has begun.
    • FXRateRequest: A message to enable payers to retrieve a foreign exchange quote from a financial institution needed to complete a payment request for goods or services.
    • FXRateResponse: A message to enable a financial institution to provide a foreign exchange rate quote in response to a foreign exchange rate request.
    • PaymentStatusRequest: A message to enable payers to query the status of a previously submitted payment to/from a financial institution.
    • PaymentStatusResponse: A message to enable the financial institution to send the information on the status of a payment to the payer.

    Material Management 

    • AdvanceShipmentNotice: A Message sent from the seller to the buyer to advise of the dispatch of goods. The shipment can be for planning or serve as a notice of a shipment in progress. Therefore it is not necessary for a supplier to provide a preliminary notice of shipment, nor is it necessary for a supplier to send an actual note of shipment. Actual tracking of freight will initially be handled by the shipper directly and not via the ASN.
    • PlanningSchedule: A message sent the buyer to the seller. The document consists of the notification of a forecast to be sent from the buyer to the seller. The document outlines the requirements regarding the details for short-term delivery and/or medium to long scheduling for products. The scheduling can be used to authorize manufacturing and/or the provision of materials. This is based on the terms and conditions defined in a purchasing agreement commonly outlined by a contract or order. The Planning Schedule defined here will not be designed to support release capability. This document will serve solely as a materials requirement schedule.
    • PlanningScheduleResponse: A message sent to the buyer by the seller to acknowledge receipt of a PlanningSchedule document and also to inform of any errors or changes in the business data.
    • ShippingSchedule: A message from a buyer to a seller containing the notification of short-term shipping requirements in reference to an existing planning schedule or purchasing agreement. The document provides specific details relating to the required products, quantities, delivery points and requested delivery dates. The Shipping Schedule document supersedes certain shipping and delivery information transmitted in a previous planning schedule, but does not replace it. Shipping Schedules are usually stated in daily, weekly or monthly buckets (depending upon the industry) and are used to refine planning schedules in support of a just-in-time planning environment. This provides a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule. The Shipping Schedule also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedules are issued by a consolidated scheduling organization.
    • ShippingScheduleResponse: A message sent to the buyer by the seller to acknowledge receipt of a ShippingSchedule document and also to inform of any errors or changes in the business data.

    Order Management 

    • Order: A message sent from buyer to seller for the ordering of goods or services. The Order document is suited for use as a standing order, a stand-alone order, or most other typical order functions within MRO and direct goods. An Order may refer to goods or services and can provide information such as delivery schedules and pricing.
    • OrderRequest: A message sent from the seller to the buyer; requesting an Order from the buying application. This document is typically used by configurators on a supplier's website. The document contains ordering information that is a result of a buyer's inquiry to purchase. There is not a response to the OrderRequest as the OrderRequest results in the creation of an Order. Any changes to the OrderRequest will be represented in the Order.
    • OrderResponse: The message used to acknowledge application receipt of an Order, or to indicate changes to the Order received. This message can also be used to respond to and acknowledge a ChangeOrder.
    • ChangeOrder: A message sent from the buyer to the seller to indicate changes to an Order. Buyers may change an order for various reasons such as changing the ordered items, quantity, delivery date, ship-to address, etc. Sellers can accept or reject the change order using the order response document.
    • OrderStatusRequest: A synchronous message sent to by the buyer to the seller requesting the status of the order. More than one order can be queried, and particular line items within an order can queried. The document allows the sender to query the status of whole orders and parts of orders in one message.
    • OrderStatusResult: A message sent by the seller to the buyer in response to the OrderStatusRequest. The result can give information on the order status, the shipping status and the payment status of the order.


    • RequestForQuotation: A message sent from the buyer to the seller requesting a quotation on goods or services. The requests are based on pre-agreed terms and conditions or the terms can be stated in the message. Delivery information can also be specified within the RequestForQuotation. This message functions on a point-to-point basis where one message is sent to one recipient.
    • Quote: A message sent from the seller to the buyer in response to a RequestForQuotation giving details of the number, price and delivery availability of the quoted goods or services. This message can form the basis of a purchase order for the buyer if appropriate.

    Statistics and Forecasting 

    • TimeSeriesRequest: A message used to request statistical information. The response to this document is the TimeSeries. TimeSeries is a forecasting document that can be used to process data based on variable characteristics. Data is collected over a period of time, and time slices can be presented as a historical account or a planned forecast.
    • TimeSeries: A message used to communicate statistical information. Generally, this is applied to forecasting requirements and can be used to process data based on variable characteristics. Data is collected over a period of time, and time slices can be presented as a historical account or a planned forecast. This document can be used as a response to the TimeSeriesRequest.
    • TimeSeriesResponse: A message used as an application-level acknowledgement and to acknowledge receipt of the TimeSeries document.

    Synchronous Checks 

    • PriceCheckRequest: Document for requesting the price of an item offered for sale.
    • PriceCheckResult: The application response, containing pricing information.
    • AvailabilityCheckRequest: A request for immediate availability of a particular item.
    • AvailabilityCheckResult: Response to the availability query.

    Trading Partner Documents 

    • TradingPartnerOrganizationInformation: Used to maintain trading partner registry information throughout a trading community at the organizational level.
    • TradingPartnerUserInformation: Used to maintain user information in the TP registries throughout a trading community.
    • TradingPartnerOrganizationDelete: Used to delete an organization from the TP registry.
    • TradingPartnerUserDelete: Used to delete a user from the TP registry.
    • TradingPartnerResponse: Used to acknowledge receipt of trading partner information, and to request additional data.

License Information - Copyright © 2000
For problems or questions regarding this site, contact xcblwebmaster@commerceone.com.