The IBX xCBL 3.5 Order specification is based on the XML Common Business Library 3.5 (Copyright 2000 Commerce One, Inc. - terms and conditions specified
at http://www.xcbl.org/license.html). The original XML schema of the xCBL 3.5 Order document type has been modified slightly. Some elements which are optional according to the original schema have been excluded while others have become mandatory to meet the requirements of IBX Platform services.
The Order comprises the creation of a purchase order that is sent for acceptance or rejection by a seller. A requisitioner, buyer, or buying organization can initiate an Order in response to a variety of factors in the electronic business arena, contracts, auctions, order requests, etc.
The OrderHeader element contains the header information of the order.
Mandatory according to IBX Order specification, but optional in original xCBL schema. The OrderDetail element contains the line item and package details of the Order.
Mandatory according to IBX Order specification, but optional in original xCBL schema. The OrderSummary element contains the summary information of the Order, typically totals of numerical fields.
The Order comprises the creation of a purchase order that is sent for acceptance or rejection by a seller. A requisitioner, buyer, or buying organization can initiate an Order in response to a variety of factors in the electronic business arena, contracts, auctions, order requests, etc.
OrderNumber is the unique number assigned to the Order, typically according to the system that generated the Order
OrderIssueDate holds a time stamp provided by the application that created the Order document.
A combination of Date and Time. Note the presence of a “T” character between the date and time portions, and the use of colons to separate hours, minutes, and seconds. These are as per ISO 8601. Format: YYYYMMDDTHH:MM:SS[[+-]HH:MM]? (the first MM is Months, the other two are minutes).
Mandatory according to IBX Order specification, but optional in original xCBL schema. OrderReferences contains external references to the Order that are important to the processing and use of the Order.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Mandatory. The EDIFACT 1225 code used to communicate the purpose of the document. The only codes supported according to IBX Order specification:
• “Original” – The usual case where buyer sends an initial purchase order to a supplier.
• “InformationOnly” – Indicates that there is no action needed, this transmission is for information only. In IBX Connect orders with this purpose code are not submitted to suppliers, only to buyers’ backends and to IBX Procurement Intelligence.
The RequestedResponse element specifies the type of acknowledgment requested by the buyer from the seller. The only code currently expected is "ResponseExpected".
Mandatory according to IBX Order specification if document is a "limit"/"blanket" order. Optional in original xCBL schema. Defines the type of order.
Mandatory. Default currency of the whole Order using the standard currency code list according to ISO 42179.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
OrderLanguage identifies the language of the Order.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. OrderTaxReference identifies the default tax information for the Order.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Mandatory according to IBX Order specification if document is a "limit"/"blanket" order. Optional in original xCBL schema. OrderDates is used to hold a list of the pertinent dates for the Order - dates include validity dates, RequestedShipByDate, RequestedDeliverByDate, among others. These dates apply to the entire order, acting as defaults and that may be overwritten at the item level or package level in the body of the message.
PartialShipmentAllowed is a flag that indicates whether less than the entirety of the order can be shipped.
The OrderParty element holds all party information related to ordering goods.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Optional. A unique identifier for this route of transport to be referenced. Intended to be used as an internal reference for the document..
OrderTermsOfDelivery defines the terms of delivery for the Order.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Only one payment term and one payment method per Order is supported.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Free text information about the order entered by the buyer.
The ListOfStructuredNote element contains one or more structured notes that allow you to provide notes that are more than a simple free-text field. Such notes may include the message text, or this text may be referenced with an external identifier. An agency may be specified, and is needed in the case where an ID has been provided for a note that is either included in-line or referenced.
Typically used NoteID e.g.: “LegalNote” or ‘Goods Marking’.
ListOfNameValueSet is used to hold sets of name value pairs.
OrderHeaderAttachments holds a list of attachments applicable to the entire Order, or a large part of the consignment it describes. This information is not specific to a particular line item or package unless specifically noted. Files can be attached on both header and/or line item level. Attachments have to be referenced in the following structure and be present as MIME content parts in the envelope of the submitted transaction. In both cases according to xCBL the mandatory tags in this structure are AttachmentPurpose and AttachmentLocation, but for reference in IBX SOM and PDF formatted orders the FileName is required, too. Attachments are not transferred to buyers' backends.
BuyerOrderNumber is the unique number assigned by the buyer to the Order. Max length supported by IBX Platform services: 40 characters!
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Mandatory according to IBX Order specification, but optional in original xCBL schema. Contains seller’s account number for the buyer. Should be a buyer specific code or the catalog name. If element is absent in received order documents then it's added with value "N/A" instead of rejecting the order.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. ContractReferences is an element that holds the contract number and contract type for referencing a contract.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
OtherOrderReferences is all other references to the Order not explicitly stated as the content of other elements. Is used to identify the type of source of information by using a standard code list (e.g.: ContractNumber, CostCentre, AccountNumber, ProjectNumber, CustomersUnitInventoryNumber).
The Identifier element is used to provide an identification number that is assigned by a standards agency.
The Agency element identifies the organization from which the identifier is assigned.
Ident holds the identification number assigned by the agency.
AgencyCoded specifies the agency, company or organization responsible for issuing the codelist or identifiers.
Within the element ../Party/PartyID/Identifier/Agency/AgencyCoded the value is usually "AssignedByBuyerOrBuyersAgent".
Within element ../Party/ListOfIdentifier/Identifier/Agency/AgencyCoded other values are typically:
• “AssignedBySellerOrSellersAgent” to specify a vendor specific ID for a buyer or an internationally unique ID like
• “EAN” (International Article Numbering Association) or
• “DunAndBradstreet” (Dun and Bradstreet Corporation).
Mandatory if value of "AgencyCoded" is "Other". A custom value then must be provided, e.g. "CompanyCode" for buyer's internal organizational identifiers, "BuyerTPID" or "SellerTPID" to specify IBX TradingPartnerID's, “VAT Number” in case of TaxIdentifiers.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Is used to identify the type of source of information by using a standard code list.
Mandatory if value of "ReferenceTypeCoded" is "Other". Is used to identify the type of source of information if the standard code list does not support the code needed.
Holds the highest level of identification of the information source. This is typically used to identify a document.
PrimaryReference holds the highest level of identification of the information source. This is typically used to identify a document.
SupportingSubReference holds the lowest level of identification of the information source. This is typically used to reference a sub line item in a document.
ReferenceDescription is used to describe a reference using free form text.
Supported by IBX Order specification are only: "Original" and "InformationOnly". "InformationOnly" means that the order won´t be submitted to the supplier.
Typically the value is "StandAloneOrder". If Order is of type "Blanket" or "Limit" Order, then the value has to be "BlanketOrder".
Mandatory if value of "OrderTypeCoded" is "Other". A custom value for order type then must be provided, e.g. “STANDARD”.
The ISO language code for the order document.
Mandatory if value of "CurrencyCoded" is "Other". Then a custom currency code not contained in the standard ISO code list can be provided.
The Identifier element is used to provide an identification number that is assigned by a standards agency.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Mandatory. Stores the company name.
Optional. Used if more lines are necessary for sending the company name.
Optional. Used if more lines are necessary for sending the company name. Not recommended.
Optional. Identifier contains a specific identifier for the company name. Not recommended.
Optional. But either "POBox" or "Street" should be provided.
Optional. But either "POBox" or "Street" should be provided. May contain even the house number. In this case the element "HouseNumber" shall not be used.
Optional. Housenumber may already be included in "Street".
Optional. StreetSupplement1 contains any additional information to identify the street. In Germany used for “Adresszusatz 1”.
Optional. StreetSupplement2 contains any further additional information to identify the street. In Germany used for “Werk”.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
This code identifies the region within a country. This code list is derived from ISO 3166/1998 (Country code subdivision code, UN/LOCODE 2000).
Mandatory if value of "RegionCoded" is "Other". Then a custom region code not included in the standard ISO code list can be provided.
This code identifies a country. This code list is derived from ISO 3166-1997.
Mandatory if value of "CountryCoded" is "Other". Then a custom country code not included in the standard ISO code list can be provided.
Is the date items in the purchase order must be shipped from the seller.
RequestedDeliverByDate is the date items in the purchase order must be received by the buyer.
PromiseDate is used mainly for confirming orders when a date was promised by the supplier over the phone.
ValidityDates contains the dates between which the Order is effective.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
BuyerParty contains the information for the party purchasing the goods.
The Party element identifies an entity doing business and the relevant information pertaining to it.
BuyerTaxInformation describes the taxing information for the buying party. Contains usually the buyer's VAT ID. Element is not mandatory but strongly recommended.
The Party element identifies an entity doing business and the relevant information pertaining to it.
Optional. SellerTaxInformation describes the taxing information for the selling party. Contains usually the seller's VAT ID.
The Party element identifies an entity doing business and the relevant information pertaining to it.
The Party element identifies an entity doing business and the relevant information pertaining to it.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
The Identifier element is used to provide an identification number that is assigned by a standards agency.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
The NameAddress element contains the name and the address information for an entity.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Official Description: CorrespondenceLanguage identifies the language in which all correspondences with the entity identified by the Party should be. Within the IBX Platform services this element can be used to set the language of an order document in PDF format - based on the value of CorrespondenceLanguage/Language/LanguageCoded. If the order is created in IBX eProcurement then the language code is the same as for the supplier as it is registered in IBX eProcurement.
The Identifier element is used to provide an identification number that is assigned by a standards agency.
Mandatory. ContactName identifies the department or employee name.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
ListOfContactNumber lists one or more communication points. At least one of e-mail address, telephone number and fax number is required.
The Identifier element is used to provide an identification number that is assigned by a standards agency.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Free form text for special shipping instructions.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Only one price is supported per line item if type of order is not "BlanketOder".
PricingType identifies the type of price. Price is always assumed to be a catalog price, so this should only be used if the price is not a catalog price, which is the case when order type is "BlanketOrder". Then the pricing type shall be specified as:
1. “ExpectedUnitPrice” - the first price type in the ListOfPrice
2. “MaximumOrderQuantityPrice” - the second price type in ListOfPrice
The pricing type in blanket orders is not sent to suppliers and only the first price (ExpectedUnitPrice) is included in the order to the supplier.
Expected price for the in "PriceBasisQuantity" mentioned value.
Quantity on which the "UnitPrice" is based.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Optional. Contains a note to further describe the payment term, eg.:”within 8 days 3% cash disc.,net cash with.30 days”.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
The Attachment element is a container for specifying the attachments to a document.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
AttachmentPurpose explains the reason or purpose for attaching the message to the document or its intended use.
FileName provides name of the attached file.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. AttachmentTitle displays the title of the attached document.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. AttachmentDescription describes the attachment.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. Language denotes the language the attachment is written in.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. MIMEType describes the format of the attachment.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema. ReplacementFile indicates whether it is a replacement attachment or not.
AttachmentLocation dentifies the location of the attachment to the document.
ListOfItemDetail contains a list of line items for the Order.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.The ListOfPackageDetail element is a container to hold one or more PackageDetail elements. PackageDetail is the packaging information at the detail level for the items, packages, and equipment.
The ItemDetail element contains information to describe and identify an item along with all pricing and delivery information for that item.
The BaseItemDetail element identifies the line item for the document. This contains the description, specific identifiers, weights, measures and other information associated with the product.
The PricingDetail element contains all pricing information, including taxes and total price for an item. Only one price is supported per item except for Blanket/Limit Orders.
Allowances and charges, part of PricingDetail in original xCBL 3.5 schema, are not supported by IBX Order specification, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
The DeliveryDetail element is used to specify the scheduling information for a distinct set of ship from party, ship to party, and transport information for the line item.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema.
LineItemNote describes any free form text pertinent to the line item. This element may contain notes or any other similar information that is not contained explicitly in another structure. You should not assume that the receiving application is capable of doing more than storing and/or displaying this information.
ListOfStructuredNote contains one or more structured notes that allow you to provide notes that are more than a simple free-text field. Such notes may include the message text, or this text may be referenced with an external identifier. An agency may be specified, and is needed in the case where an ID has been provided for a note that is either included in-line or referenced.
ListOfNameValueSet is used to hold sets of name value pairs. Example: eForm (smartform) specific article information like size, colour etc...
LineItemAttachments contains attachments for the line item. Files can be attached on both header and/or line item level. Attachments have to be referenced in the following structure and be present as MIME content parts in the envelope of the submitted transaction. In both cases according to xCBL the mandatory tags in this structure are AttachmentPurpose and AttachmentLocation, but for reference in IBX SOM and PDF formatted orders the FileName is required, too.
Attachments are not transferred to buyers' backends.
Mandatory. Buyer’s line item number. Buyer is free to have a non-consecutive line numbers as long as each number is unique.
The LineItemType element contains information on whether the line item is part of a component group. According to the IBX Order specification only “Item” is allowed.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.According to the original xCBL 3.5 schema it can be used to define sub line item relationships
The ItemIdentifiers element is used to provide the identification of the item being ordered. Typically, the //ItemIdentifiers/PartNumbers/SellerPartNumber should be sufficient to identify what is being ordered, although other identifiers of the item can also be specified. Partnumbers are typically not given if order type is “BlanketOrder”.
The ListOfDimension element is a container for a list of one or more dimension elements. Not used by IBX Platform services, but won´t be removed from outbound orders either.
Mandatory according to IBX Order specification as long as OrderType is not "BlanketOrder", but optional in original xCBL schema. The TotalQuantity contains the total amount of the line item pertaining to the document.
The MaxBackOrderQuantity specifies the maximum quantity of an item that a customer will allow to be back ordered.
The ListOfQuantityCoded element is a container holding a list of quantities not explicitly stated in other elements. Not used by IBX Platform services, but won´t be removed from outbound orders either.
Mandatory according to IBX Order specification, but optional in original xCBL schema. True if the item is a free text item, false if the item is ordered from a catalogue (this includes OCI web-shops).
The CatalogReference element references a catalog. Not used by IBX Platform services by default (element ListOfItemReferences is used instead), but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
ItemContractReferences lists information about any contracts that apply to the line item. Not used by IBX Platform services by default (element ListOfItemReferences is used instead), but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
The ListOfContractItem element lists the information on one or more contracts.
ListOfItemReferences lists one or more references relating to the line item. Primarily used to refer to a contract or catalogue and to denote cost object information for the buyer. It can also be used to add information about tax codes or the origin of a line item meaning the system that has been involved to add the item to the shopping cart and finally to the order.
Frequently used codes in //BaseItemDetail/ListOfItemReferences/ListOfReferenceCoded are:
• ContractNumber
• CostCentre
• AccountNumber
• ProjectNumber
• GeneralLedgerAccount
• CustomerReferenceNumber
• CustomersUnitInventoryNumber
• Other
Using “Other” in //ListOfReferenceCoded/ReferenceCoded/ReferenceTypeCoded allows to specify a non standard code in //ListOfReferenceCoded/ReferenceCoded/ReferenceTypeCodedOther as e.g.:
• ProcessType – describing the call-off method of the item
• COST_CTR – a non standard code for cost center
• COST_CENTRE_DESCRIPTION – a non standard code for cost center description
• NCM_CODE – appropriate field in IBX e-Procurement: ZZ_BR_STEUC
• MaterialUsage – appropriate field in IBX e-Procurement: ZZ_BR_MATUSE
• MaterialOrigin – appropriate field in IBX e-Procurement: ZZ_BR_MATORG
• CFOP_CATEGORY – appropriate field in IBX e-Procurement: ZZ_BR_INDUST
• TaxCode – appropriate field in IBX e-Procurement: ZZ_BR_TAXCODE
CountryOfOrigin specifies the country code for the country in which the line item was manufactured. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
CountryOfDestination specifies the country code for the country in which the delivery is finally received. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
FinalRecipient identifies the person or organization who will ultimately receive the item. If the segment FinalRecipient is present, then the element Order/OrderHeader/OrderParty/ShipToParty/Party/NameAddress shall be empty. This segment needs to exist for every item or only on header level.
ListOfPartyCoded specifies any other parties associated with the line item that are not already explicitly stated. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
ConditionsOfSale details the conditions of sale for the item. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
HazardousMaterials contains the hazardous information for the line item. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
The PartNumbers element identifies all identification numbers for the item.
Service identifies the item as a service. A value of true will identify the line item as a service. If this element does not exist, or is set to false, the item is assumed to be goods.
Mandatory according to IBX Order specification, but optional in original xCBL schema. ItemDescription is a free form field that is used to give a text description of the item.
The ListOfItemCharacteristic element is a collection of one or more characteristics that describe the item such as surface finishes.
This information usually comes from an eForm in IBX Search Engine.
CommodityCode contains the harmonized (HS) system code. This is the international notation to categorize individual commodities. These are also known as customs codes. The code type shall be specified in //CommodityCode/Identifier/Agency/AgencyCodedOther (e.g.: "UNSPSC 5.0.2", "US-UN-SPSC", "UNSPSC 6.0315U", "eCl@ss 4.1") while element //CommodityCode/Identifier/Agency/AgencyCoded has to be "Other".
The Identifier element is used to provide an identification number that is assigned by a standards agency.
The Category element contains the product category. Not used by IBX Platform services (element CommodityCode is used instead), but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
The supplier’s product identifier for the ordered product. Not to be sent if the product has no ID or if the buyer does not know the product ID.
The buyer's internal product identifier for the ordered product.
ManufacturerPartNumber is the identification of a product as assigned by the manufacturer of the product and identification of the manufacturer.
The Identifier element is used to provide an identification number that is assigned by a standards agency.
Mandatory according to IBX Order specification, but optional in original xCBL schema.
Tax contains tax information as it relates to the pricing of an item.
Not supported by IBX Order specification, will be removed from outbound xCBL 3.5 orders. Optional in original xCBL schema. ItemAllowancesOrCharges contains the allowances and/or charges that apply to the pricing of an item.
Mandatory according to IBX Order specification, but optional in original xCBL schema. TotalValue identifies the monetary net total for pricing of an item (based on UnitPriceValue / PriceBasisQuantity/QuantityValue * //BaseItemDetail/TotalQuantity/QuantityValue).
If OrderType is "BlanketOrder" then the TotalValue is based on the ExpectedUnitPrice and not the MaximumOrderQuantityPrice.
MonetaryAmount contains the value of the monetary amount.
ShipToLocation is the location to which the shipments are to be delivered. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
ShipFromLocation identifies the party from which the item is to be shipped from. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
ListOfScheduleLine is all of the schedule information relevant to the line item for the shipping parties. This may indicate several shipments to the same location over a period of time.
ItemPackagingReference contains reference information when detailed packaging information contained in list of package detail is to be associated with the line item. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
SimplePackageNote is free form text relating to the packaging. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
TermsOfDelivery includes the information related to delivery including shipment method payment and transport. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
CargoClassification contains different conventions for the classification and description of the goods being transported. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
ScheduleLine contains the information on a portion of the line item shipment to be sent on particular set of dates with a particular set of transport information.
ScheduleLineID uniquely identifies the schedule line within the line item. This is used for external reference. Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. ShipmentStatusEventCoded is used to provide status information pertaining to the shipment of a schedule line (should only be used in an OrderResponse.).
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. ShipmentStatusEventCodedOther is used to provide a non-standard StatusEventCode. This element is mandatory if the value of StatusEventCoded is 'Other'.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. ShipmentStatusReasons is used to provide reasons for a shipment status. This should only be used if the ShipmentStatusEventCoded element is used.
Quantity contains the sub-quantity to be shipped on a particular set of dates.
RequestedDeliveryDate is the date the buyer requested for delivery.
ListOfOtherDeliveryDate lists the dates revolving around delivery.This is used to express simple date information that is not tied to particular carriers, transport, etc.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. ScheduleLineNote is a free form text field that is used to provide any additional information relating to this schedule.
Transport contains carrier, equipment, and mode of transport information.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions.TransportReference references the transport routing element to identify which transport legs the package is travelling on. This element is repeated if the package travels on more than one transport route.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. ListOfShipToSubInformation details place and quantity information regarding the shipto sub-location.
NumberOfLines identifies the number of line items. Mandatory according to IBX Order specification, but optional in original xCBL schema.
TotalTax contains the total tax amount for the Order.
Mandatory according to IBX Order specification, but optional in original xCBL schema. TotalAmount contains the total price (net amount, ecxluding TotalTax) for the entire Order.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. TransportPackagingTotals is a summary of transport and packaging information if included in the Order.
Not used by IBX Platform services, but won´t be removed from outbound orders either if provided by non IBX eProcurement solutions. SummaryNote contains any free form text for the OrderSummary. This element may contain notes or any other similar information that is not contained explicitly in another structure.