xCBL 3.5 Application Specific Documents

Application Specific Documents In addition to the 9 new general-purpose documents in xCBL3.5, this release also contains several new documents that are more application-specific, tailored to particular ERP system interfaces. These documents may, at some point, become part of xCBL but until then are subject to change at any time.

Auction Event Documents 

• AuctionEventCreate: A message used for initiating an auction within a portal-based auction related service. The AuctionEventCreate can be used to set up auctions based on lots. Each lot is auctioned off according to the lot dependencies, bid rules, and win rules specified within this document.
• AuctionEventCreateResponse: A message used by portal-based auction related services to provide information and status related to the request to create an auction via the AuctionEventCreate message.
• AuctionEventResult: A message used by portal-based auction related services to report the results from a given AuctionEventCreate. 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.
• AuctionEventResultResponse: A message used to acknowledge receipt of an AuctionEventResult document by the auction initiator. In the case that the AuctionEventResult was not successfully received, the auction initiator may specify in the response document that the portal-based auction related service resend the AuctionEventResult document.

Bulletin Board Documents 

• BulletinBoardNoteChange: A message used to change an existing bulletin board posting.
• BulletinBoardNoteCreate: A message that enables businesses to rapidly share and locate information of any kind, including business opportunities (e.g., auctions, request for quotation processes, exchanges, classified advertisements) from an auction application. Any XML-enabled application can create, change or delete Notes on the BulletinBoard via a fixed XML format.
• BulletinBoardNoteDelete: A message that describes the deletion of a note from a bulletin board.
• BulletinBoardNoteReceipt: A message that describes the receipt of the creation, changes, or deletion of a BulletinBoardNote. Notifies whether the creation, charge or deletion was successful.

Internal Documents 

• InternalInvoice: A message sent from an e-procurement system to an backend system. The message is needed for replication of an (external) invoice to an application's backend system. The internal invoice contains all elements of the external invoice and some additional information, in particular information regarding account assignment and commitment reduction.
• InternalOrder: A message sent from an e-procurement system to a backend system. The document is needed for replication of an (external) order to a backend system. The InternalOrder can be a prerequisite for posting of the goods receipt. It contains all elements of the external order plus some additional information, in particular information regarding the purchasing organization, limit, category, and for account assignment.

Transport Documents 

• TransportOrderInitialRequest: A message sent by a shipper to submit a request for shipment of goods through a transportation exchange. The transport order will be handled as an auction within the transportation exchange. Registered carriers will view and bid upon the shipment request. This was developed to support SAP requirements. The initial design supports only simple, limited use cases.
• TransportOrderQuoteConfirm: A message used to communicate and confirm the carrier selected by the shipper from the given set of TransportOrderQuoteResponses. This was developed to support SAP requirements. The initial design supports only limited functionality.
• TransportOrderFollowUpRequest: A message sent by a shipper to submit a request to the transportation exchange to cancel the transport order. This was developed to support SAP requirements. The initial design supports only limited functionality.
• TransportOrderQuoteResponse: A message sent by the transportation exchange to communicate a carrier's quotation and availability for the transport order. This was developed to support SAP requirements. The initial design supports only limited functionality.
• TransportOrderResponse: A message sent by the transportation exchange to acknowledge the receipt and communicate the status of the TransportOrderInitialRequest, the TransportOrderFollowUpRequest, and the TransportOrderQuoteConfirm documents. This was developed to support SAP requirements. The initial design supports only limited functionality.
• TransportOrderStatusRequest: A message used to request tracking information for the transport order. This was developed to support SAP requirements. The initial design supports only limited functionality.
• TransportOrderStatusRequestResponse: A message is used to communicate the status of the transport order shipment. This can be sent as a response to the TransportOrderStatusRequest document or it can be initiated by the transportation exchange without a requesting document. This was developed to support SAP requirements. The initial design supports only limited functionality.

External Requirement Documents 

• ExternalRequirement: An external requirement is sent from a demand generating planning software system to an e-procurement system. The ExternalResuirement contains information that results in the creation of an Order to be generated out of the demand/requirement in the e-procurement-system.
• ExternalRequirementFulfillment: A message sent from an e-procurement system back to the demand generating software in response to the ExternalRequirement. The ExternalRequirementFullfillment provides information on the Order that has been created and scheduling information.

Opportunity Documents 

• Opportunity: A message that describes the model of a business opportunity being offered. For example, 'creating an auction' is equivalent to 'creating an opportunity of type auction'. So auction is specific type of opportunity. Going by this definition, there are four types of opportunities in Dynamic Pricing: Auction, Exchanges, RFQ and classifieds. Typical for opportunities is that the opportunity is given to several possible partners and the one(s) with whom the business is (are) done (the winner(s)) isdetermined by a dynamic price finding. The business opportunity (for instance Auction) can be responded to by an offer (for instance bid) and will typically be opened to multiple possible business partners.
• OpportunityAcknowledgement: A message acknowledging that an Opportunity or OpportunityResponse has been received on the marketplace.
• OpportunityList: is the answer of the marketplace on an OpportunityRequest and thus gives a list of opportunities matching the searching criteria defined in the OpportunityRequest.
• OpportunityRequest: A message containing a request for a list of opportunities matching some specified search criteria. The criteria are specified through the selection of parameters.
• OpportunityResponse: is the response (offer) or reaction to an opportunity. More specifically, a response to an Opportunity for an auction is a bid, response to an exchange is an offer and response to RFQ is a quotation. How ever, response to a classified is simply a message.
• OpportunityResult: A message containing the result of the opportunity offered. After all responses are given and the winner(s) is/are of the opportunity is determined the result is sent to the initiator and the winner(s).