Consistent set of interfaces derived from a business object model

The following identified U.S. patent applications are relied upon and are incorporated herein by reference in this application in their entirety:

U.S. Patent Application No. 60/577,453, entitled “Interfaces Derived from a Business Object Model Shared by the Heterogeneous Applications,” filed on Jun. 4, 2004.

U.S. Patent Application No. 60/581,252, entitled “Interfaces Derived from a Business Object Model Shared by Heterogeneous Applications,” filed on Jun. 18, 2004.

U.S. Patent Application No. 60/582,949, entitled “Interfaces Derived from a Business Object Model Shared by Heterogeneous Applications,” filed on Jun. 25, 2004.

U.S. Patent Application No. 60/656,598, entitled “Interfaces Derived from a Business Object Model Shared by Heterogeneous Applications,” filed on Feb. 25, 2005.

U.S. patent application Ser. No. 11/145,464, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Jun. 3, 2005.

PCT Patent Application No. PCT/US05/19961, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Jun. 3, 2005.

U.S. patent application Ser. No. 11/155,368, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Jun. 17, 2005.

PCT Patent Application No. PCT/US05/021481, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Jun. 17, 2005.

U.S. patent application Ser. No. 11/166,065, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Jun. 24, 2005.

PCT Patent Application No. PCT/US05/22137, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Jun. 24, 2005.

U.S. Patent Application No. 60/729,480, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Oct. 21, 2005.

PCT Patent Application No. PCT/US06/07760, entitled “Consistent Set Of Interfaces Derived From A Business Object Model,” filed on Feb. 27, 2006.

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

The subject matter described herein relates generally to the generation and use of consistent interfaces derived from a business object model. More particularly, the subject matter described herein relates to the generation and use of consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business.

Transactions are common among businesses and between business departments within a particular business. During any given transaction, these business entities exchange information. For example, during a sales transaction, numerous business entities may be involved, such as a sales entity that sells merchandise to a customer, a financial institution that handles the financial transaction, and a warehouse that sends the merchandise to the customer. The end-to-end business transaction may require a significant amount of information to be exchanged between the various business entities involved. For example, the customer may send a request for the merchandise as well as some form of payment authorization for the merchandise to the sales entity, and the sales entity may send the financial institution a request for a transfer of funds from the customer's account to the sales entity's account.

Exchanging information between different business entities is not a simple task. This is particularly true because the information used by different business entities is usually tightly tied to the business entity itself. Each business entity may have its own program for handling its part of the transaction. These programs differ from each other because they typically are created for different purposes and because each business entity may use semantics that differ from the other business entities. For example, one program may relate to accounting, another program may relate to manufacturing, and a third program may relate to inventory control. Similarly, one program may identify merchandise using the name of the product while another program may identify the same merchandise using its model number. Further, one business entity may use U.S. dollars to represent its currency while another business entity may use Japanese Yen. A simple difference in formatting, e.g., the use of upper-case lettering rather than lower-case or title-case, makes the exchange of information between businesses a difficult task. Unless the individual businesses agree upon particular semantics, human interaction typically is required to facilitate transactions between these businesses. Because these “heterogeneous” programs are used by different companies or by different business areas within a given company, a need exists for a consistent way to exchange information and perform a business transaction between the different business entities.

The United Nations established the United Nations Centre for Trade Facilitation and Electronic Business (“UN/CEFACT”) to improve worldwide coordination for the exchange of information. The primary focus of UN/CEFACT is to facilitate national and international transactions by simplifying and harmonizing processes, procedures and information flow to contribute to the growth of global commerce. UN/CEFACT is still in its early stages of developing such a harmonized system. Additional information regarding UN/CEFACT can be found at www.unece.org/cefact/.

Currently many standards exist, which offer a variety of interfaces used to exchange business information. Most of these interfaces, however, apply to only one specific industry, and are not consistent between the different standards. Moreover, a number of these interfaces are not consistent within an individual standard. Thus, there is a need for the harmonization of interfaces across these standards and across various industries.

Methods and systems consistent with the subject matter described herein facilitate e-commerce by providing consistent interfaces that can be used during a business transaction. Such business entities may include different companies within different industries. For example, one company may be in the chemical industry, while another company may be in the automotive industry. The business entities also may include different businesses within a given industry, or they may include different departments within a given company.

The interfaces are consistent across different industries and across different business units because they are generated using a single business object model. The business object model defines the business-related concepts at a central location for a number of business transactions. In other words, the business object model reflects the decisions made about modeling the business entities of the real world acting in business transactions across industries and business areas. The business object model is defined by the business objects and their relationships to each other (overall net structure).

A business object is a capsule with an internal hierarchical structure, behavior offered by its operations, and integrity constraints. Business objects are semantically disjoint, i.e., the same business information is represented once. The business object model contains all of the elements in the messages, user interfaces and engines for these business transactions. Each message represents a business document with structured information. The user interfaces represent the information that the users deal with, such as analytics, reporting, maintaining or controlling. The engines provide services concerning a specific topic, such as pricing or tax.

Methods and systems consistent with the subject matter described herein generate interfaces from the business object model by assembling the elements that are required for a given transaction in a corresponding hierarchical manner. Because each interface is derived from the business object model, the interface is consistent with the business object model and with the other interfaces that are derived from the business object model. Moreover, the consistency of the interfaces is also maintained at all hierarchical levels. By using consistent interfaces, each business entity can easily exchange information with another business entity without the need for human interaction, thus facilitating business transactions.

Methods and systems consistent with the subject matter described herein provide a consistent set of interfaces that are suitable for use with more than one industry. This consistency is reflected at a structural level as well as through the semantic meaning of the elements in the interfaces.

Methods and systems consistent with the subject matter described herein provide an object model and, from this object model, derive two or more interfaces that are consistent.

Methods and systems consistent with the subject matter described herein provide a consistent set of interfaces suitable for use with a business scenario that spans across the components within a company. These components, or business entities, may be heterogeneous.

Additionally, methods and systems consistent with the subject matter described herein provide a consistent set of interfaces suitable for use with different businesses.

An electronic message to request cancellation of an accounting can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to request cancellation of the accounting. Responding to a request to cancel an accounting can include receiving a message including an accounting cancellation package and initiating cancellation of an accounting of posting information. An accounting cancellation package can contain an accounting cancellation entity and a business transaction document reference package, where the accounting cancellation entity identifies a first document that characterizes cancellation of an accounting and identifies a type of a second document characterizing posting information previously sent and to be canceled, and the business transaction document reference package contains a reference entity identifying the second document.

In some variations, the posting information can include posting information previously sent for an invoice or credit memo, and the request for cancellation of an accounting can include a request for cancellation of an accounting of an invoice. The posting information can include posting information previously sent with respect to a movement of goods, and the request for cancellation of an accounting can include a request for cancellation of an accounting of a movement of goods. The accounting cancellation package can further contain a note entity characterizing a reason for the cancellation, and a date entity characterizing a date on which the cancellation is to be entered.

An electronic message to request a bank account statement can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to request the bank account statement.

The generated message can include a bank account statement package containing a bank account statement entity characterizing a statement of a bank regarding turnovers on a customer bank account. The bank account statement package can also contains a bank account package containing information characterizing a bank account. The bank account statement package further contains a bank account statement item package containing an item entity characterizing a single turnover on a bank account. The bank account statement item package also contains a payment explanation package containing information characterizing payments in a bank account statement. The payment explanation package contains a payment difference explanation package containing information characterizing documents relating to payments in a bank account statement.

The bank account statement package can further contain a party package containing a payment transaction initiator party entity characterizing a party that initiated a payment. The party package can also contain a payment transaction destination party entity characterizing a party that receives payment in case of a bank transfer or whose account is debited in case of a direct debit. The party package can also contain an original payment transaction initiator party entity characterizing a party executing a payment transaction. The party package can also contain a final payment transaction destination party entity characterizing a party to receive a payment or to be debited. The bank account statement package can also include a bank account statement bank account package containing a payment transaction initiator bank account entity characterizing a bank account of a party initiating a payment transaction. The bank account statement bank account package can also contain a payment transaction destination bank account characterizing a bank account of a party receiving a payment or to be debited. The bank account statement package can also include a business transaction document reference package containing a payment reference entity characterizing a document from a payment transaction initiator. The business transaction document reference package can also include a payment order reference entity characterizing a payment order by a payment transaction initiator. The business transaction document reference package can also include a business transaction document reference package. The business transaction document reference package can further contain a bill of exchange reference entity characterizing a bill of exchange number.

The payment explanation package can further contain a payment explanation item characterizing a payment amount. The payment explanation package can also contain a payment explanation party package containing an original payment transaction initiator party entity characterizing an original party on behalf of which a payment transaction is executed. The payment explanation party package can also contain a final payment transaction destination party characterizing a party on behalf of which a payment is received or debited. The payment explanation package can also contain a business document object reference package containing a payment explanation payment transaction initiator invoice reference entity characterizing an invoice of a transaction initiator. The business document object reference package can also contain a payment explanation payment transaction destination invoice reference entity characterizing an invoice of a party receiving a payment or being debited. The business document object reference package can also contain a payment explanation payment transaction initiator contract reference entity characterizing a contract of a transaction initiator. The business document object reference package can also contain a payment explanation payment transaction destination contract reference entity characterizing a contract of a party receiving a payment or being debited. The business document object reference package can also contain a payment explanation payment transaction initiator purchase order reference entity characterizing a purchase order of a transaction initiator. The business document object reference package can also contain a payment explanation payment transaction destination purchase order reference entity characterizing a reference to a purchase order of a party receiving a payment or being debited.

The payment difference explanation package can contain a payment difference explanation item entity characterizing differences between expected and actual payment amounts. The payment difference explanation package can also contain a business document object reference package containing a payment difference explanation payment transaction initiator invoice reference entity characterizing an invoice of a transaction initiator. The business document object reference package can also contain a payment difference explanation payment transaction destination invoice reference entity characterizing an invoice of a party receiving a payment or being debited. The business document object reference package can also contain a payment difference explanation payment transaction initiator contract reference entity characterizing a contract of a transaction initiator. The business document object reference package can also contain a payment difference explanation payment transaction destination contract reference entity characterizing a contract of a party receiving a payment or being debited. The business document object reference package can also contain a payment difference explanation payment transaction initiator purchase order reference entity characterizing a purchase order of a transaction initiator. The business document object reference package can further contain a payment difference explanation payment transaction destination purchase order reference entity characterizing a reference to a purchase order of a party receiving a payment or being debited.

Generating a request for a bank account statement can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating generation of a request for a bank account statement. The received message includes a bank account statement package containing a bank account statement entity characterizing a statement of a bank regarding turnovers on a customer bank account. The bank account statement package also includes a bank account package containing information characterizing a bank account. The bank account statement package further contains a bank account statement item package containing an item entity characterizing a single turnover on a bank account. The bank account statement item package also contains a payment explanation package containing information characterizing payments in a bank account statement. The payment explanation package also contains a payment difference explanation package containing information characterizing documents relating to payments in a bank account statement.

An electronic message to request bank account balances for a time period for a group of bank accounts can be generated by a first application that executes in a landscape of computer systems. Transmission of the message to a second application can be initiated in order to request account balances for a time period for a group of bank accounts. Responding to a request for account balances for a time period for a group of bank accounts can include receiving a message including a bank account balance report query package and initiating a request for bank account balances for a time period for a group of bank accounts. The bank account balance report query package can contain a bank account balance report query entity, a bank account package, and item package. The bank account balance report query entity characterizes a request for balance information for a bank account. The bank account package characterizes the bank account for which requests are to be made. The item package characterizes criteria that are relevant for determining bank account balances. The bank account package can contain a bank account entity identifying the bank account for which balance information is to be ascertained. The item package can contain a bank account balance report query item entity characterizing criteria for determining bank account balances. The bank account balance report query item entity can contain a bank account balance type code characterizing a type of a bank account balance and a date period entity identifying a period for which the bank account balances are to be taken into consideration. In some variations, the bank account package can further contain a bank account differentiator entity characterizing the difference between accounts that are managed under one account number. In some variations, the bank account differentiator entity can contain a bank account differentiator ID characterizing a unique identifier to differentiate between bank accounts.

An electronic message to respond to a request for bank account balances for a time period for a group of bank accounts can be generated by a first application that executes in a landscape of computer systems. Transmission of the message to a second application can be initiated in order to receive account balances for a time period for a group of bank accounts. Responding to a request for account balances for a time period for a group of bank accounts can include receiving a message including a bank account balance report package and initiating a request for bank account balances for a time period for a group of bank accounts. The bank account balance report package can contain a bank account balance report entity containing information about balances of a bank account.

In some variations, the bank account balance report package can contain a log package, a bank account package and a bank account balance package. The log package characterizes log messages that are issued when bank account balances are determined and can contain a log entity characterizing a sequence of log messages issued by an application while executing a task. The bank account package characterizes information about the bank account for which requests are made and can contain a bank account entity characterizing the bank account to which balance information belongs, and a bank account differentiator entity characterizing the difference between accounts that are managed under one account number. The bank account differentiator entity can contain a bank account differentiator ID characterizing a unique identifier to differentiate between bank accounts. The bank account balance package characterizes bank account balances, and can contain a bank account balance entity containing bank account balances.

An electronic message to record business document data from a digitized image of the data can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to record the digitized business document data either manually or automatically. Responding to a request to record business document data from a digitized image of the data can include receiving a message including a business transaction document image recognition package and initiating recording of the digitized business document data either manually or automatically. A business transaction document image recognition package can contain a business transaction document image recognition request entity characterizing a request for a digitized business document to be recognized and an attachment package containing an attachment entity identifying the digitized business document.

In some variations, the digitized business document to be recognized can include an invoice, and the request to record business document data from an image can include a request for the manual entry of the invoice data. The digitized business document to be recognized can include an invoice, and the request to record business document data from an image can include a request for automatic entry of the invoice data with the use of Optical Character Recognition (OCR) software.

An electronic message requesting to change, create, or delete items in a catalogue can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to request to change, create, or delete items in a catalogue. Responding to the request to change, create, or delete items in a catalogue can include receiving a message including a catalogue publication transmission package and initiating generation of a confirmation to the request to change, create, or delete items in a catalog. A catalogue publication transmission package can contain a catalogue entity that characterizes a structured directory of catalogue items.

In some variations, the catalogue publication transmission package can further contain a content package. The content package can contain a content entity, catalogue item package, a catalogue view package, and a transmission information package. The content entity can characterize a list of items to be changed, created, or read. The catalogue item package can contain a catalogue item entity, a catalogue item description entity, a catalogue classification entity, a property valuation entity and a catalogue item relationship entity. The catalogue item entity can characterize information about a catalogue item required to change, create, or delete it. The catalogue item description entity can characterize an item in various locales. The catalogue classification entity can characterize a classification of a catalogue item. The property valuation entity can characterize a value of a property associated with a catalogue item. The catalogue item relationship entity can characterize a relationship between two catalogue items. The catalogue view package can contain a catalogue view entity and a catalogue view item entity. The catalogue view entity can characterize a restricted subset of a catalogue. The catalogue view item entity can characterize a catalogue item to be included in a catalogue view. The transmission information package containing information characterizing a transmission of an object contained in the message.

An electronic message confirming receipt of a request to change, create, or delete items in a catalogue can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to confirm receipt of the request to change, create, or delete items in a catalogue. Responding to the confirmation request can include receiving a message including a catalogue publication transmission package and initiating generation of a confirmation that the request to change, create, or delete items in a catalog can be performed. The catalogue publication transmission package can contain a catalogue publication transmission entity characterizing information required to confirm whether items in a catalogue request can be changed, created, or deleted. The catalogue publication transmission package can also contain a catalog package. The catalog package can contain a catalogue entity that can characterize a catalogue of items which can be changed, created, or deleted.

An electronic message to request institutions to carry out one or more payment transactions can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to request institutions to carry out on payment transactions. Responding to a request for instructions to carry out one or more payment transactions can include receiving a message including the instructions to carry out one or more payment transactions, and initiating an instruction to a payer's account to record the results of payment transactions.

The message can comprise a collective payment order package which in turn can include a collective payment order entity and a payment order package. The collective payment order entity characterizes an instruction to a credit institution to carry out one or more payment transactions. The payment order package contains a payment order entity characterizing one or more instructions to a credit institution to carry out a payment transaction, and a net amount entity identifying a payment amount associated with the payment order entity.

In some variations, the instruction to a credit institution can comprises a payment form code identifying a form of payment, and the instruction to the payment transaction initiator's account to record the result of the payment transaction can comprises the result of the payment transaction based on a form of payment. The instruction to a credit institution can also comprise an account debit indicator identifying whether or not the payment transaction initiator's account is to be debited, and the instruction to the payment transaction initiator's account to record the result of the payment transaction can comprises an indication as to whether or not the payment transaction initiator's account was debited. The instruction to a credit institution can comprise a payment procedure code identifying one or more technical characteristics of the payment transaction, and the instruction to the payment transaction initiator's account to record the result of the payment transaction can comprises the result of the payment transaction based on a payment procedure code. The instruction to a credit institution can comprise a payment execution date identifying an execution date for the payment transaction, and the instruction to the payment transaction initiator's account to record the result of the payment transaction can comprises a date of execution of the payment transaction.

The collective payment order package can include a party package containing information characterizing information concerning parties involved in the payment transaction, and a bank account package containing information characterizing information concerning banking details of a payment transaction initiator and a bank account to be used by a bank for bank charges.

The party package can include a payment transaction initiator party entity characterizing the party that initiated a payment. The bank account package can include a payment transaction initiator bank account entity characterizing a bank account of the payment transaction initiator, and a bank charges bank account entity characterizing a bank account to be debited with bank charges for a collective payment order.

The payment order package can include a party package containing information characterizing the party that placed the order and a bank account package containing information characterizing banking details for the destination party of the payment transaction. It can also include a payment instruction package containing information characterizing information for participating banks concerning a payment transaction execution, and a state central bank report package containing information characterizing legal reporting information to a central bank. The payment order package further can include information to satisfy a legal reporting requirement for payments to foreign payees, and a business transaction document reference package containing information characterizing references to different documents involved in the payment transaction, such as checks. It can also include a payment explanation package containing information characterizing an explanation for a purpose, and an amount of a payment, which can include references to individual invoices or credit memos.

The party package can include a payment transaction destination party entity characterizing the party that receives a payment or whose account is debited, and an original payment transaction initiator party entity characterizing the party on whose behalf a payment order can be executed by the payment transaction initiator party entity. It can also include a final payment transaction destination party entity characterizing the party that can optionally receive a payment or be debited.

The bank account package can include a payment transaction destination bank account entity characterizing a bank account of the party that the payment transaction is destined.

The payment instruction package can include a payment instruction entity characterizing an instruction to an executing bank related to the payment order, such as to send a bank advice to the payee, and a correspondence bank details entity characterizing details from a bank of a correspondence bank that should be used for forwarding the payment order. The correspondence bank details entity further can include a correspondence bank type code characterizing a type of a correspondence bank, a bank code characterizing an address or identifier for the correspondence bank, and a bank account code characterizing a correspondence bank account.

The state central bank report package can include a central bank report item entity characterizing information to satisfy legal reporting to a central bank and a requirement for payments to foreign payees.

The business transaction document reference package can include a payment reference entity characterizing a reference to a payer's payment document representing an actual payment that includes at least the payment procedure, the payment currency, the payment amount, the payment date and the payment receiver. The payment reference entity can also identify parties involved and banking details associated with a payment. The business transaction document reference package can also include a check reference entity characterizing a reference to a check (i.e., checknumber) that was used for the payment, and a bill of exchange reference entity characterizing a reference to a bill of exchange (i.e., a bill of exchange number) that was used for the payment.

The payment explanation package can include a payment explanation item entity characterizing a payment amount for the payee. It can refer to one or more invoices or other business documents relevant for the payment amount such as potential adjustments applied by the payer.

An electronic message to provide notification of the payment behavior of the business partner can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to provide notification of the payment behavior of the business partner. Responding to the message to provide notification of the payment behavior of the business partner can include receiving a message including a credit payment behavior summary package and initiating the notification of the payment behavior of the business partner. A credit payment behavior summary package can contain a credit payment behavior summary message entity and a party package. The credit payment behavior summary message entity can characterize key figures regarding the payment behavior of a business partner. The party package can contain information that characterizes the parties relevant to the payment behavior of the business party.

In some variations, the party package can contain a debtor party entity, a creditor party entity, and a seller party entity. The debtor party entity can characterize a debtor party having a payment obligation. The creditor party entity can characterize a party that owns a receivable due from the debtor party. The seller party entity can characterize a party that has sold a product to the debtor party. The message to provide notification of the payment behavior of the business partner can further contain a product information package. The product information package can contain information that characterizes the product sold to the debtor party. The product information package can further contain a payment information package. The payment information package can contain information that characterizes the payment behavior of the debtor party. The payment information package can contain a last payment entity, an oldest open item entity and a maximum level dunned open item entity. The last payment entity can characterize a last payment received from the debtor party. The oldest open item entity can characterize an oldest open item of the debtor party. The maximum level dunned open item entity can characterize an open item of the debtor party having a highest dunning level.

An electronic message requesting to generate a query regarding creditworthiness of a party can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate a query regarding creditworthiness of a party. Responding to a message requesting to generate a query regarding creditworthiness of a party can include receiving a message including a credit worthiness query package and initiating a query regarding creditworthiness of a party. The credit worthiness query package can contain a credit worthiness entity and a party package. The credit worthiness entity can characterize a query regarding creditworthiness of a party. The party package can contain a debtor party entity that can characterize a party for whom creditworthiness information is to be provided.

In some variations, the party package can further contain a creditor party entity and a seller party entity. The creditor party entity can characterize a party that owns a receivable due from a debtor. The seller party entity can characterize a party that sells or plans to sell a product to a debtor. The credit worthiness query package can further contain a product information package. The product information package can contain information that can characterize a product category of a product sold or to be sold to a debtor.

An electronic message requesting to generate a response to a query regarding the creditworthiness of a party can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate a response to a query regarding the creditworthiness of a party. Responding to a message requesting to generate a response to a query regarding creditworthiness of a party can include receiving a message including a credit worthiness query package and initiating a response to a query regarding creditworthiness of a party. The credit worthiness query package can contain a credit worthiness entity, a party package and an information package. The credit worthiness entity can characterize a query regarding creditworthiness of a party. The party package can contain a debtor party entity that can characterize a party for whom creditworthiness information is to be provided. The information package can contain a credit rating entity that can characterize a credit rating for a debtor party.

In some variations, the party package can further contain a creditor party entity and a seller party entity. The creditor party entity can characterize a party that owns a receivable due from a debtor. The seller party entity can characterize a party that sells or plans to sell a product to a debtor. The credit worthiness query package can further contain a product information package. The product information package can contain information that can characterize a product category of a product sold or to be sold to a debtor. The information package can further contain a credit risk class entity, a credit limit entity and a credit exposure entity. The credit risk class entity can characterize a risk of non-payment by a debtor party. The credit limit entity can characterize a credit limit for a debtor party. The credit exposure entity can characterize a level of a credit limit that has been consumed.

An electronic message to request generation of delivery quantity and scheduling information can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to request generation of delivery quantity and scheduling information. Responding to the request for generation of delivery quantity and scheduling information can include receiving a message including a purchase request package and initiating a generation of delivery quantity and scheduling information. A purchase request package can contain a purchase request entity and a purchase request item package. The purchase request entity can characterize requisition requirements. The purchase request item package can contain a schedule line package that can characterize quantity and date information associated with a requisition.

In some variations, the party package can further contain a buyer party entity and a bill to party entity. The buyer party entity can characterize a party that buys goods or services. The bill to party entity can characterize a party that is billed for goods or services. The item package can further contain a delivery information package, a delivery schedule item party package, a location package and a schedule line package. The delivery information package can contain a previous delivery entity and a cumulative delivery entity. The previous delivery entity can characterize identification and validity of a last release instance previously transferred in a delivery schedule. The cumulative delivery entity can characterize identification and validity of instances previously transferred in a delivery schedule. The delivery schedule item party package can contain a buyer party entity and a product recipient party entity. The buyer party entity can characterize a party that buys the goods to be delivered. The product recipient party entity can characterize a party that receives a goods delivery. The location package can contain a ship from location entity, a trans-shipment location entity and a ship to location entity. The ship from location entity can characterize a place from which ordered goods are delivered. The trans-shipment location entity can characterize a location to which ordered products are trans-shipped en route to a recipient. The ship to location entity can characterize a place to which ordered goods are delivered. The schedule line package can contain a schedule line entity and a confirmed schedule line entity. The schedule line entity can characterize a statement about goods to be delivered. The confirmed schedule line entity can characterize a confirmation from a vendor party as terms of a delivery of goods from a scheduling agreement

An electronic message to request generation of delivery quantity and scheduling information can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to request generation of delivery quantity and scheduling information. Responding to the request for generation of delivery quantity and scheduling information can include receiving a message including a purchase request package and initiating a generation of delivery quantity and scheduling information. A purchase request package can contain a purchase request entity and a purchase request item package. The purchase request entity can characterize requisition requirements. The purchase request item package can contain a schedule line package that can characterize quantity and date information associated with a requisition.

In some variations, the party package can further contain a buyer party entity and a bill to party entity. The buyer party entity can characterize a party that buys goods or services. The bill to party entity can characterize a party that is billed for goods or services. The item package can further contain a delivery information package, a delivery schedule item party package, a location package and a schedule line package. The delivery information package can contain a previous delivery entity and a cumulative delivery entity. The previous delivery entity can characterize identification and validity of a last release instance previously transferred in a delivery schedule. The cumulative delivery entity can characterize identification and validity of instances previously transferred in a delivery schedule. The delivery schedule item party package can contain a buyer party entity and a product recipient party entity. The buyer party entity can characterize a party that buys the goods to be delivered. The product recipient party entity can characterize a party that receives a goods delivery. The location package can contain a ship from location entity, a trans-shipment location entity and a ship to location entity. The ship from location entity can characterize a place from which ordered goods are delivered. The trans-shipment location entity can characterize a location to which ordered products are trans-shipped en route to a recipient. The ship to location entity can characterize a place to which ordered goods are delivered. The schedule line package can contain a schedule line entity and a confirmed schedule line entity. The schedule line entity can characterize a statement about goods to be delivered. The confirmed schedule line entity can characterize a confirmation from a vendor party as terms of a delivery of goods from a scheduling agreement.

Generating a notification regarding a shipment event associated with a delivery of goods can be accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiating transmission of the message to a second application to generate a shipment notification regarding an event associated with a delivery of goods. The generated message includes a delivery package containing a delivery entity characterizing goods or a combination of goods to be made available for transportation. The delivery package also contains a location package containing a ship to location entity characterizing a place to which goods are shipped. The delivery package also contains an item package containing an item entity characterizing a quantity of goods in a delivery. The item package further contains a product information package containing information characterizing a product in a delivery item.

The delivery package can further contain a handling unit containing information characterizing units of packaging materials and packaged products. The delivery package can also contain a delivery party package containing a buyer party entity characterizing a party that purchased goods specified in a delivery. The delivery party package can also contain a vendor party entity characterizing is a party that delivers goods. The delivery party package can also contain a product recipient party characterizing is party to whom goods are delivered. The delivery party package can also contain a carrier party entity characterizing a party that transports goods. The delivery party package can also contain a bill to party entity characterizing a party to whom an invoice for delivered goods is sent. The delivery package can also contain a transport information package containing a transport means entity characterizing a transport mechanism for a delivery. The transport information package can also contain a transport tracking entity characterizing information tracking a status of a transport of a delivery. The delivery package can also contain a delivery information package containing information characterizing delivery conditions related to a shipping notification.

The location package can further contain a ship from location entity characterizing a place from which goods are shipped. The location package can also contain a trans-shipment location entity characterizing a location at which goods are to be trans-shipped on their way to a recipient. In addition, the item package can further contain a business transaction document reference package containing a purchase order reference entity characterizing a reference to a purchase order or an item in a purchase order. The business transaction document reference package can also contain an origin purchase order reference entity characterizing a reference to an original purchase order or an item within an original purchase order. The business transaction document reference package can also contain a scheduling agreement reference entity characterizing an outline agreement item. The business transaction document reference package can further contain a sales order reference entity characterizing a reference to an item in a sales order. The location package can further contain a batch package containing information characterizing a batch in a delivery item.

Generating a notification regarding a shipment event associated with a delivery of goods can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating a notification regarding a shipment event associated with a delivery of goods. The received message includes a delivery package containing a delivery entity characterizing goods or a combination of goods to be made available for transportation. The delivery package also contains a location package containing a ship to location entity characterizing a place to which goods are shipped. The delivery package further contains an item package containing an item entity characterizing a quantity of goods in a delivery. The item package also contains a product information package containing information characterizing a product in a delivery item.

Generating a notification regarding a receipt of a delivery of goods can be accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiating transmission of the message to a second application to generate a notification regarding a receipt of a delivery of goods. The generated message includes a delivery package containing a delivery entity characterizing a confirmation of a receipt of a delivery of goods. The delivery package also contains a party package containing a vendor party entity characterizing party that delivered goods or on whose behalf goods were delivered. The delivery package also contains a location package containing information characterizing a place to which goods were delivered. The delivery package further contains an item package containing an item entity characterizing a quantity of goods that were delivered. The item package also contains a product information package containing information characterizing a delivered.

The party package can further contain a product recipient party entity characterizing a party that took delivery of goods. In addition, the item package can further contain a delivery information package containing information characterizing a delivery information for a delivery of goods.

Generating a notification regarding a receipt of a delivery of goods can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating generation of a notification regarding a receipt of a delivery of goods. The received message includes a delivery package containing a delivery entity characterizing goods or a combination of goods to be made available for transportation. The delivery package also contains a location package containing a ship to location entity characterizing a place to which goods are shipped. The delivery package further contains an item package containing an item entity characterizing a quantity of goods in a delivery. The item package also contains a product information package containing information characterizing a product in a delivery item.

An electronic message requesting to generate invoicing information associated with a business transaction can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate invoicing information associated with a business transaction . Responding to the request to generate invoicing information associated with a business transaction can include receiving a message including invoice package and initiating the generation of invoicing information associated with a business transaction. The invoice package can contain an invoice entity and an invoice party package. The invoice entity can characterize payables and receivables for delivered goods and rendered services. The invoice party package can contain a bill to party entity and a bill from party entity. The bill to party entity can characterize a party to which an invoice for deliveries received or services rendered is sent. The bill from party entity can characterize a party initiating an execution of an invoice.

In some variations, the invoice party package can further contain an invoice buyer party entity, an invoice seller party entity, an invoice product recipient party entity, an invoice vendor party entity, an invoice manufacturer party entity, an invoice payer party entity, an invoice payee party entity and an invoice carrier party entity. The invoice buyer party entity can characterize a party authorizing deliveries or services. The invoice seller party entity can characterize a party that sells goods or services. The invoice product recipient party entity can characterize a party to whom goods are delivered or services are provided. The invoice vendor party entity can characterize a party that delivers goods or provides services. The invoice manufacturer party entity can characterize a party that produces goods being invoiced. The invoice payer party entity can characterize a party that pays for goods or services. The invoice payee party entity can characterize a party that receives payment for goods or services. The invoice carrier party entity can characterize a party that transports goods to be invoiced.

The invoice due package can further contain a location package, an invoice delivery information package, an invoice payment information package, an invoice price information package, an invoice tax package, an invoice attachment package, an invoice description package, an invoice item package, an item hierarchy relationship entity, an item product information package, an item price information package, an item tax package, an item package, a business transaction document reference package, an item attachment package, an item description package and an item delivery information package. The location package can contain a ship to location entity and a ship from location entity. The ship to location entity can characterize a place to which goods are shipped or where services are provided. The ship from location entity can characterize a place from which goods are shipped. The invoice delivery information package can contain information that can characterize delivery information for goods being invoiced. The invoice payment information package can contain a cash discount terms entity and a payment form entity. The cash discount terms entity can characterize terms of payment. The payment form entity can characterize a payment form and required data for the payment form. The invoice price information package can contain information that can characterize a total price to be settled for goods or services to be invoiced. The invoice tax package can contain information that can characterize tax price components in an invoice. The invoice attachment package can contain information that can characterize attachment information associated with an invoice. The invoice description package can contain information that can characterize texts associated with an invoice.

The invoice item package can contain an item entity. The item entity can characterize pricing information and taxes for a quantity of product that has been delivered or for a service that has been rendered. The item hierarchy relationship entity can characterize hierarchical relationships between items. The item product information package can contain a product entity and a product category entity. The product entity can characterize a product in an invoice item. The product category entity can characterize a category of a good or service that is being invoiced. The item price information package can contain information that can characterize an amount invoiced for goods delivered or services rendered. The item tax package can contain information that can characterize tax components in a total amount invoiced for goods delivered or services rendered.

The item package can contain an item buyer party entity, an item seller party entity, an item product recipient party entity, an item vendor party entity, an item manufacturer party and a carrier party entity. The item buyer party entity can characterize a party authorizing deliveries or services. The item seller party entity can characterize a party that sells goods or services. The item product recipient party entity can characterize a party to whom goods are delivered or services are provided. The item vendor party entity can characterize a party that delivers goods or provides services. The item manufacturer party can characterize a party that produces goods being invoiced. The carrier party entity can characterize a party that transports goods to be invoiced. The business transaction document reference package can contain a purchase order reference entity, a sales order reference entity, a delivery reference entity, a service acknowledgement reference entity, an origin invoice reference entity, a purchase contract reference entity, a sales contract reference entity, a buyer product catalogue reference entity and a seller product catalogue reference entity. The purchase order reference entity can characterize a purchase order or an item within a purchase order. The sales order reference entity can characterize a sales order or an item within a sales order. The delivery reference entity can characterize a delivery or an item within a delivery. The service acknowledgement reference entity can characterize a confirmation by a seller that a service has been provided. The origin invoice reference entity can characterize a reference to an invoice previously sent. The purchase contract reference entity can characterize a purchase contract or an item within a purchase contract. The sales contract reference entity can characterize a sales contract or an item within a sales contract. The buyer product catalogue reference entity can characterize a product catalogue of a buyer or an item within the catalogue. The seller product catalogue reference entity can characterize a product catalogue of a seller or an item within the catalogue. The item attachment package can contain information that can characterize attachment information associated with an invoice. The item description package can contain information that can characterize texts associated with an invoice. The item delivery information package can characterize delivery information associated with an invoice. In some variations, the item package can further contain an accounting package. The accounting package can contain information that can characterize an assignment of an invoice item net amount or partial amount to a set of account assignment objects.

An electronic message requesting to generate business transaction information can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate business transaction information. Responding to the request to generate business transaction information can include receiving a message including invoice due package and initiating the generation of business transaction information. An invoice due package can contain an invoice due entity, an invoice due party package, an invoice due location package, an invoice due delivery information package, an invoice due payment information package, an invoice due price information package, an invoice due account assignment package, an invoice due attachment package, an invoice due description package and an invoice due item package. The invoice due entity can characterize details of a business transaction relevant for settling the business transaction. The invoice due party package can contain information that can characterize parties to a business transaction. The invoice due location package can contain information that can characterize locales associated with a business transaction. The invoice due delivery information package can contain information that can characterize a delivery of goods associated with a business transaction. The invoice due payment information package can contain information that can characterize payment terms for a business transaction. The invoice due price information package can contain information that can characterize a total price to be settled for goods or services provided under a business transaction. The invoice due account assignment package can contain information that can characterize account assignment information associated with a business transaction. The invoice due attachment package can contain information that can characterize attachment information associated with a settlement of a business transaction. The invoice due description package can contain information that can characterize texts associated with a settlement of a business transaction. The invoice due item package can contain information that can characterize item information for a settlement of a business transaction.

In some variations, the invoice due party package can further contain a buyer party entity, a seller party entity, a product recipient party entity, a vendor party entity, a bill to party entity, a bill from party entity, a payer party entity and a payee party entity. The buyer party entity can characterize a party that purchases goods or services. The seller party entity can characterize a party that sells goods or services. The product recipient party entity can characterize a party to whom goods are delivered or services are provided. The vendor party entity can characterize a party that delivers goods or provides services. The bill to party entity can characterize a party to which an invoice for goods or services is sent. The bill from party entity can characterize a party that draws up an invoice for goods or services. The payer party entity can characterize a party that pays for goods or services. The payee party entity can characterize a party that receives payment for goods or services. The invoice due location package can further contain a ship to location entity and a ship from location. The ship to location entity can characterize a place to which goods are shipped or where services are provided. The ship from location can characterize a place from which goods are shipped. The invoice due payment information package can further contain a cash discount terms entity and a payment form entity. The cash discount terms entity can characterize terms of payment. The payment form entity can characterize a payment form and required data for the payment form.

The item package can further contain an item entity, an item hierarchy relationship entity, an item product information package, an item price information package, a business transaction document reference package, an item attachment package, an item due description package and a delivery information package. The item entity can characterize information from a business document item that is to be taken into account for a settlement of a business transaction. The item hierarchy relationship entity can characterize hierarchical relationships between items. The item product information package can contain a product entity and a product category entity. The product entity can characterize a product for which an invoice is due. The product category entity can characterize a category of a product or service that is being invoiced. The item price information package can contain a price entity and a procurement cost upper limit entity. The price entity can characterize an amount to be settled for a product or service. The procurement cost upper limit entity can characterize a quantity or value-based restriction placed on a product or service to be settled.

The business transaction document reference package can contain a purchase order reference entity, a sales order reference entity, a delivery reference entity, a purchase contract reference entity, a sales contract reference entity, a buyer product catalogue reference entity and a vendor product catalogue reference entity. The purchase order reference entity can characterize a purchase order or an item within a purchase order. The sales order reference entity can characterize a sales order or an item within a sales order. The delivery reference entity can characterize a delivery or an item within a delivery. The purchase contract reference entity can characterize a purchase contract or an item within a purchase contract. The sales contract reference entity can characterize a sales contract or an item within a sales contract. The buyer product catalogue reference entity can characterize a product catalogue of a buyer or an item within the catalogue. The vendor product catalogue reference entity can characterize a product catalogue of a vendor or an item within the catalogue. The item attachment package can contain information that can characterize attachment information associated with a settlement of a business transaction. The item due description package can contain information that can characterize texts associated with a settlement of a business transaction. The delivery information package can characterize delivery information associated with a business transaction.

Requesting a generation of a loan contract can be implemented by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiate transmission of the message to a second application to generate a loan contract or a request associated therewith. The generated message includes a loan contract package. The loan contract package contains a loan contract entity characterizing information required to generate a loan contract. The loan contract package also includes a party package containing information characterizing parties to a loan contract. The loan contract package also contains a product information package containing information characterizing a product upon which a loan contract is based. The loan contract package also contains a payment information package containing information characterizing information associated with payment processing. The loan contract package further contains an item package containing information characterizing conditions of a loan contract.

The party package can contain a lender party entity characterizing a party that grants a loan. The party package can also contain a borrower party entity characterizing a party that is issued a loan. The party package can also contain a payer party entity characterizing a party responsible for repayment of a loan. The party package can also contain a broker party entity characterizing an agent for issuance of a loan. The party package can further contain a bailsman party entity characterizing a party responsible for guaranteeing a loan.

The product information package can further contain a product category entity characterizing a product category of a loan. The product information package can further contain a product entity. In addition, the payment information package can further contain a payment form entity characterizing a form of payment. The product information package can further contain a bank account entity characterizing a bank account. Further, the loan contract package can further contain a loan contract attachment package containing information characterizing documents relevant for a loan. The loan contract package can also contain a loan contract item package. The loan contract item package can contain a loan condition information entity characterizing terms and conditions of a loan. The loan can contain a loan interest condition entity characterizing an interest condition for a loan. The loan can also contain a loan amortizement condition entity characterizing a repayment condition for a loan. The loan can further contain a loan fee condition entity characterizing a fee condition for a loan. The a loan contract item package can further contain a loan contract item party package containing information characterizing all parties to a loan contract.

Requesting a generation of a loan contract can be accomplished by receiving an electronic message and initiating generation of a loan contract in a landscape of computer systems providing message-based services. The received message includes a loan contract package. The loan contract package contains a loan contract entity characterizing information required to generate a loan contract. The loan contract package can also contain a party package containing information characterizing parties to a loan contract. The loan contract package can also contain a product information package containing information characterizing a product upon which a loan contract is based. The loan contract package can also contain a payment information package containing information characterizing information associated with payment processing. The loan contract package can further contain an item package containing information characterizing conditions of a loan contract.

Generating a confirmation of a creation of a loan contract can be accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiating transmission of the message to a second application to generate a confirmation of a creation of a loan contract. The generated message includes a loan contract package. The loan contract package contains a loan contract entity characterizing information regarding a creation of a loan contract. The loan contract package also contains a log package containing information characterizing log messages associated with a creation of al loan contract. The loan contract package further contains a payment information package, and the payment information package contains a bank account entity characterizing information about a bank account to be used to repay a loan.

Generating a confirmation of a creation of a loan contract can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating a generation of a confirmation of a creation of a loan contract. The received message includes a loan contract package. The loan contract package includes a loan contract entity characterizing information regarding a creation of a loan contract. The loan contract package can also include a log package containing information characterizing log messages associated with a creation of al loan contract. The loan contract package can further include a payment information package, and the payment information package contains a bank account entity characterizing information about a bank account to be used to repay a loan.

A notice relating to product activities for a vendor can be created by generating an electronic message characterizing activities associated with goods of a buyer and initiating transmission of the message to an application to generate a notice to a vendor relating to product activities. In another or the same aspect, generating a notice from a buyer to a vendor relating to product activities can include receiving an electronic message characterizing activities associated with goods of a buyer and initiating a generation of a notice to a vendor relating to product activities.

An electronic message can characterize product activities by including a package that characterizes activities associated with goods of a buyer at a ship to location and a package containing an entity package characterizing activities associated with goods of a buyer at a ship to location. Those packages can be a product activity package and item package, respectively, and the entity can be an item entity. The location package can contain a ship to location entity characterizing a location to which goods are to be delivered and the item package can include a product information package characterizing goods to be delivered.

The product activity message can further contain a party package that contains a buyer party entity characterizing a party that purchases goods, a vendor party entity characterizing a party that delivers goods, and a product recipient party entity characterizing a party that receives a delivery of goods. The party package can further contain a business transaction document reference package containing information characterizing references to business documents associated with a product activity notice, and the location package can further contain a ship from location entity characterizing a location from which goods are to be shipped for delivery. The item package can further contain an inventory package containing an inventory entity characterizing stock of a good at a buyer and a consignment inventory entity characterizing goods in possession of a buyer that are owned by a vendor until purchased.

An electronic message requesting to generate a notice of an event affecting product demand can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate a notice of an event affecting product demand. Responding to the request to generate a notice of an event affecting product demand can include receiving a message including product demand influencing event package and initiating a generation of a notice of an event affecting product demand. A product demand influencing event package can contain a product demand influencing event entity, a party package and an item package. The product demand influencing event entity can characterize a product demand influencing event. The party package can contain a buyer party entity and a vendor party entity. The buyer party entity can characterize a party that purchases goods. The vendor party entity can characterize a party that delivers goods. The item package can contain an item entity, a location package and a product information package. The item entity can characterize activities associated with goods of a buyer at a ship to location. The location package can contain a ship to location entity. The ship to location entity can characterize a location to which goods are to be delivered. The product information package can contain information that can characterize goods to be delivered. In some variations, the product demand influencing event package can further contain a scheduling package. The scheduling package can contain information that can characterize time orders utilized to define a schedule for logistics associated with goods affected by a product demand influencing event. The location package can further contain a ship from location entity. The ship from location entity can characterize a location from which goods are to be shipped for delivery. The item package can further contain a product information package. The product information package can contain information that can characterize goods affected by a product demand influencing event.

An electronic message requesting to generate information associated with a purchase order can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate information associated with a purchase order. Responding to the request to generate information associated with a purchase order can include receiving a message including purchase order package and initiating generation of information associated with a purchase order.

The purchase order package can contain a purchase order entity, a purchase order party package, a purchase order location package, a purchase order delivery information package, a purchase order payment information package, a price order price information package, a purchase order attachment package, a purchase order description package, a purchase order follow up message package and a purchase order item package. The purchase order entity can characterize a request by a buyer to a seller to provide certain quantities of products or services. The purchase order party package can contain information characterizing parties to a purchase order. The purchase order location package can contain information characterizing locations associated with a purchase order. The purchase order delivery information package can contain information characterizing a delivery of goods associated with a purchase order. The purchase order payment information package can contain information characterizing payment terms associated with a purchase order. The price order price information package can contain pricing information associated with a purchase order. The purchase order attachment package can contain information characterizing attachments relevant to a purchase order. The purchase order description package can contain information characterizing texts associated with a purchase order. The purchase order follow up message package can contain information characterizing messages associated with a purchase order and occurring subsequent to an issuance of such purchase order. The purchase order item package can contain information characterizing an item associated with a purchase order.

In some variations, the purchase order party package can further contain a buyer party entity, a seller party entity, a product recipient party entity, a vendor party entity, a manufacturer party entity, a bill to party entity, a payer party entity and a carrier party entity. The buyer party entity can characterize a party that buys goods or services. The seller party entity can characterize a party that sells goods or services. The product recipient party entity can characterize a party to which goods are to be delivered or to whom services are to be provided. The vendor party entity can characterize a party that delivers goods or services. The manufacturer party entity can characterize a party that manufactures goods. The bill to party entity can characterize a party to which an invoice for goods or services is sent. The payer party entity can characterize a party that pays for goods or services. The carrier party entity can characterize a party that transports goods. The purchase order location package can further contain a ship to location entity and a ship from location entity. The ship to location entity can characterize a location to which goods are to be delivered or where services are to be provided. The ship from location entity can characterize a location from where goods are to be shipped. The purchase order payment information package can further contain a cash discount terms entity, a payment form entity and a payment card entity. The cash discount terms entity can characterize terms of payment in an ordering process. The payment form entity can characterize a payment form and associated payment information. The payment card entity can characterize a credit card or a customer payment card. The purchase order description package can further contain a description entity and a confirmation description entity. The description entity can characterize text associated with a purchase order. The confirmation description entity can characterize text associated with an order confirmation. The follow up message package can further contain a follow up purchase confirmation entity, a follow up dispatched delivery notification entity and a follow up service acknowledgement request entity. The follow up purchase confirmation entity can characterize information associated with a confirmation to be received by a buyer from a seller in connection with a purchase order. The follow up dispatched delivery notification entity can characterize notification preferences of a buyer relating to outbound deliveries by a seller. The follow up service acknowledgement request entity can characterize notification preferences of a buyer relating to services provided by a seller.

The purchase order item package can further contain a purchase order item entity, a hierarchy relationship entity, a product information package, a price information package, a purchase order item party package, a purchase order location package, a purchase order item delivery information package, a purchase order item business transaction document reference package, a purchase order item attachment package, a purchase order item description package and a schedule line package. The purchase order item entity can characterize a product ordered in a purchase order. The hierarchy relationship entity can characterize a hierarchical relationship between items. The product information package can contain a product entity and a product category entity. The product entity can characterize a commercial description of a product. The product category entity can characterize a commercial categorization of a product. The price information package can contain a price entity, a confirmed price entity, an item buyer party entity, an item seller party entity, an item product recipient party entity, an item vendor party entity, an item manufacturer party entity, an item bill to party entity, an item payer party entity, an item carrier party entity, a ship to location entity and a ship from location entity. The price entity can characterize a purchase order price specified by a buyer. The confirmed price entity can characterize a purchase order price specified by a seller.

The purchase order item party package can contain an item buyer party entity can characterize a party that buys goods or services. The item seller party entity can characterize a party that sells goods or services. The item product recipient party entity can characterize a party to which goods are to be delivered or to whom services are to be provided. The item vendor party entity can characterize a party that delivers goods or services. The item manufacturer party entity can characterize a party that manufactures goods. The item bill to party entity can characterize a party to which an invoice for goods or services is sent. The item payer party entity can characterize a party that pays for goods or services. The item carrier party entity can characterize a party that transports goods. The purchase order location package can contain a ship to location entity and a ship from location entity. The ship to location entity can characterize a location to which goods are to be delivered or where services are to be provided. The ship from location entity can characterize a location from where goods are to be shipped. The purchase order item delivery information package can contain information characterizing a delivery of goods associated with a purchase order. The purchase order item business transaction document reference package can contain a quote reference entity, a purchase contract reference entity, a sales contract reference entity, an origin purchase order reference entity, a buyer product catalogue reference entity and a seller product catalogue reference entity. The quote reference entity can characterize a reference to a quotation or an item within a quotation. The purchase contract reference entity can characterize a purchase contract or an item in a purchase contract. The sales contract reference entity can characterize a sales contract or an item in a sales contract. The origin purchase order reference entity can characterize an origin purchase order to an item within an origin purchase order. The buyer product catalogue reference entity can characterize a product catalogue of a buyer or an item within such catalogue. The seller product catalogue reference entity can characterize a product catalogue of a seller or an item within such catalogue. The purchase order item attachment package can contain information characterizing attachments relevant to a purchase order. The purchase order item description package can contain a description entity and a confirmation description entity. The description entity can characterize texts associated with a purchase order item. The confirmation description entity can characterize texts regarding a purchase order item confirmation. The schedule line package can contain a schedule line entity and a confirmed schedule line entity. The schedule line entity can characterize a line containing a quantity and date of a performance schedule required by a buyer for a purchase order. The confirmed schedule line entity can characterize a quantity and date of a confirmed by a seller for a purchase order.

An electronic message can be generated that characterizes a status of a purchase order and transmission of this message can be initiated so that such status information can be created. In another or the same aspect, an electronic message can be received that can be used to subsequently create status information for a purchase order.

The message can include a purchase order package that contains one or more of a purchase order information package containing one or more of a purchase order information entity characterizing a request by a buyer to a seller to provide certain quantities of products or services, a purchase order information party package containing information characterizing parties to a purchase order, a purchase order information location package containing information characterizing locations associated with a purchase order, a purchase order information payment information package containing information characterizing payment information associated with a purchase order, a price order price information package containing pricing information associated with a purchase order, a purchase order information attachment package containing information characterizing attachments relevant to a purchase order, a purchase order information description package containing information characterizing texts associated with a purchase order, a purchase order information follow up message package containing information characterizing, and a purchase order information item package containing information characterizing an item.

The purchase order information party package can further contain one or more of a buyer party entity characterizing a party that buys goods or services, a seller party entity characterizing a party that sells goods or services, a product recipient party entity characterizing a party to which goods are to be delivered or to whom services are to be provided, a vendor party entity characterizing a party that delivers goods or services, a manufacturer party entity characterizing a party that manufactures goods, a bill to party entity characterizing a party to which an invoice for goods or services is sent, a payer party entity characterizing a party that pays for goods or services, and a carrier party entity characterizing a party that transports goods. The purchase order information location package further can also contain one or both of a ship to location entity characterizing a location to which goods are to be delivered or where services are to be provided and a ship from location entity characterizing a location from where goods are to be shipped. The purchase order information payment information package can additionally contain one or more of a cash discount terms entity characterizing terms of payment in an ordering process, a payment form entity characterizing a payment form and associated payment information, and a payment card entity characterizing a credit card or a customer payment card. The purchase order information description package can further contain one or both of a description entity characterizing text associated with a purchase order and a confirmation description entity characterizing text associated with an order confirmation. The follow up message package can include one or more of a follow up purchase confirmation entity characterizing information associated with a confirmation to be received by a buyer from a seller in connection with a purchase order, a follow up dispatched delivery notification entity characterizing notification preferences of a buyer relating to outbound deliveries by a seller, a follow up service acknowledgement request entity characterizing notification preferences of a buyer relating to services provided by a seller, and a follow up invoice request entity characterizing whether a buyer expects to receive an invoice from a seller.

The purchase order information item package can include one or more of a purchase order information item entity characterizing a product ordered in a purchase order, a hierarchy relationship entity characterizing a hierarchical relationship between items, a product information package, a price information package, a purchase order information item party package, a purchase order information location package, a purchase order information item delivery information package containing information characterizing a delivery of goods associated with a purchase order, a purchase order information item business transaction document reference package, a purchase order information item attachment package containing information characterizing attachments relevant to a purchase order, a purchase order information item description package containing a description entity characterizing texts associated with a purchase order item, and a confirmation description entity characterizing texts regarding a purchase order item confirmation. The product information package can contain one or both of a product entity characterizing a commercial description of a product, and a product category characterizing a commercial categorization of a product. The price information package can contain one or more of a price entity characterizing a purchase order price specified by a buyer, a confirmed price entity characterizing a purchase order price specified by a seller, and a procurement cost upper limit entity characterizing a cost upper limit for one or more types of procurement costs. The purchase order information item party package can contain one or more of an item buyer party entity characterizing a party that buys goods or services, an item seller party entity characterizing a party that sells goods or services, an item product recipient party entity characterizing a party to which goods are to be delivered or to whom services are to be provided, an item vendor party entity characterizing a party that delivers goods or services, an item manufacturer party entity characterizing a party that manufactures goods, an item bill to party entity characterizing a party to which an invoice for goods or services is sent, an item payer party entity characterizing a party that pays for goods or services, and an item carrier party entity characterizing a party that transports goods. The purchase order information location package can contain one or both of a ship to location entity characterizing a location to which goods are to be delivered or where services are to be provided, and a ship from location entity characterizing a location from where goods are to be shipped. The purchase order information item business transaction document reference package can contain one or more of a quote reference entity characterizing a reference to a quotation or an item within a quotation, a purchase contract reference entity characterizing a purchase contract or an item in a purchase contract, a sales contract reference entity characterizing a sales contract or an item in a sales contract, an origin purchase order reference entity characterizing an origin purchase order to an item within an origin purchase order, a buyer product catalogue reference entity characterizing a product catalogue of a buyer or an item within such catalogue, and a seller product catalogue reference entity characterizing a product catalogue of a seller or an item within such catalogue.

Generating a request querying a buyer to procure products or services can be accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiate transmission of the message to a second application. The generated message includes a purchase request package. The purchase request package contains a purchase request entity characterizing requisition requirements. The purchase request package further contains a purchase request item package, and the purchase request item package contains a schedule line package containing information characterizing quantity and date information associated with a requisition.

The purchase request party package can further contain a buyer party entity characterizing a party that buys goods or services. The purchase request party package can also contain a seller party entity characterizing a party that sells goods or services, The purchase request party package can also contain a proposed seller party entity characterizing a preferred party for selling goods or services. The purchase request party package can also contain a requestor party entity characterizing a party that requests procurement of goods or services. The purchase request party package can also contain a product recipient party entity characterizing a party to which goods are to be delivered or to whom services are to be provided. The purchase request party package can further contain a manufacturer party entity characterizing a party that manufactures goods.

The generated message can further contain a purchase request location package grouping information associated with locations relevant for a requisition. The purchase request location package includes a ship to location entity characterizing a location to which goods are to be delivered or where services are to be provided. The purchase request location package also includes a ship from location entity characterizing a location from where goods are to be shipped.

The purchase request item package can further contain a purchase request entity characterizing a requested product. The purchase request item package can also contain a hierarchy relationship entity characterizing relationship between items in an item hierarchy. The purchase request item package can also contain a product information package containing a product entity characterizing a product and a product category entity characterizing a product category. The purchase request item package can also contain a price information package containing a price entity characterizing a specified purchase order price, and a procurement cost upper limit entity characterizing upper procurement limits. The purchase request item package can also contain an item party package containing information characterizing parties to a requisition. The purchase request item package can also contain a location package containing information characterizing location information associated with a requisition. The purchase request item package can also contain an object reference package containing information characterizing business documents relevant for a requisition. The object reference package contains a purchase contract reference entity characterizing a purchase contract or an item in a purchase contract. The object reference package also contains a purchase order reference entity characterizing a purchase order or an item in a purchase order. The object reference package also contains a project reference entity characterizing a project or an element within a project associated with a requisition. The object reference package further contains a project element assignment entity characterizing an assignment between two elements of a project associated with a requisition. The purchase request item package can also contain an accounting object set assignment package containing information characterizing accounting information associated with a requisition. The purchase request item package can also contain an attachment package containing information characterizing attachments relevant to a requisition. The purchase request item package can further contain a description package containing information characterizing texts relating to a requisition.

The schedule line package can further contain a schedule line entity characterizing quantity and dates of a performance period associated with a requisition. The schedule line package can also contain a delivery period entity characterizing a delivery period for a requisition. The schedule line package can further contain a quantity entity characterizing a quantity specified by a requisition.

Generating a request querying a buyer to procure products or services can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating a generation of a request querying a buyer to procure products or services. The received message includes a purchase request package. The purchase request package contains a purchase request entity characterizing requisition requirements. The purchase request package also contains a purchase request item package containing a schedule line package containing information characterizing quantity and date information associated with a requisition.

Generating a confirmation of a fulfillment of a requisition can be accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiate transmission of the message to a second application. The generated message includes a purchase request package containing a purchase request entity characterizing a confirmation of requirements associated with a procurement of products or services. The purchase request package also contains an item package containing an item entity characterizing a product and a purchase order package containing information characterizing a level of fulfillment of a requirement by a purchase order.

Generating a confirmation of a fulfillment of a requisition can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating a generation of a confirmation of a fulfillment of a requisition. The received message includes a purchase request package containing a purchase request entity characterizes a confirmation of requirements associated with a procurement of products or services. The purchase request further includes an item package containing an item entity characterizing a product, and a purchase order package containing information characterizing a level of fulfillment of a requirement by a purchase order.

An electronic message to generate purchasing contract information can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate purchasing contract information.

The message can include a purchasing contract package. The purchasing contract package can contain one or more of a purchasing contract entity characterizing an agreement to order products or provide services within a certain period of time, a purchasing contract party package containing information characterizing parties to a purchasing contract parties to a purchasing contract, a purchasing contract location package containing information characterizing locations associated with a purchasing contract, a purchasing contract delivery information package containing information characterizing a delivery requested in a purchasing contract, a purchasing contract payment information package containing information characterizing payment terms for a purchasing contract, a purchasing contract price information package containing information characterizing pricing of goods or services identified in a purchasing contract, a purchasing contract attachment package containing information characterizing documents referring to a purchasing contract, a purchasing contract description package containing information characterizing texts associated with a purchasing contract, and a purchasing contract item package containing information characterizing a product or service in a purchasing contract.

The purchasing contract party package can include one or more of a buyer party entity characterizing a party that buys goods or services, a seller party entity characterizing a party that sells goods or services, a product recipient party entity characterizing a party to which goods are to be delivered or to whom services are to be provided, and a contract release authorized party entity characterizing a party that is authorized to effect releases from a purchasing contract. The purchasing contract attachment package can also contain one or more of an attachment web address entity characterizing a location of documents referring to a purchasing contract, an internal attachment web address entity characterizing a location of internal documents referring to a purchasing contract, and a legal document attachment entity characterizing legal text of a purchasing contract. The purchasing contract description package can include one or more of a description entity characterizing text associated with a purchasing contract, and an internal description entity characterizing internal text associated with a purchasing contract.

The purchasing contract item package can contain one or more of a purchasing contract item entity characterizing a product or service in a purchasing contract, a purchasing contract item product information package, a purchasing contract item price information package containing information characterizing pricing of goods or services identified in a purchasing contract, a purchasing contract item location package containing information characterizing locations associated with a purchasing contract, a purchasing contract item party package containing information characterizing parties to a purchasing contract parties to a purchasing contract, a purchasing contract item delivery information package containing information characterizing a delivery requested in a purchasing contract, a purchasing contract business document object reference package, a purchasing contract item attachment package containing information characterizing documents referring to a purchasing contract, and a purchasing contract item description package containing information characterizing texts associated with a purchasing contract. The purchasing contract item product information package can contain one or both of a product entity characterizing a product or service, and a product category entity characterizing a category for a product or service. The purchasing contract business document object reference package can contain one or more of a quote reference entity characterizing a bid of a purchaser or a bid to an item within a bid of a purchaser, an operational purchasing contract reference entity characterizing an operational purchasing contract or an item in an operational purchasing contract, and a buyer product catalogue reference entity characterizing a product catalogue of a purchaser or to an item within such a catalogue.

An electronic message to generate a notification of a purchasing contract release can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate a notification of a purchasing contract release.

The message can contain a purchasing contract release package can contain one or more of a purchasing contract release entity characterizing a notification regarding a performed release with reference to a purchasing contract, a purchasing contract release party package containing information characterizing a release of a purchasing contract, a purchasing contract release location package containing information characterizing locations associated with a release of a purchasing contract, and a purchasing contract release item package. The purchasing contract release item can include one or more of a purchasing contract release item entity characterizing an item in a purchasing contract release, a purchasing contract release item location package containing information characterizing locations associated with a contract release item, and a purchasing contract release item business document object package containing information characterizing references to business documents relevant to an item in a purchasing contract release.

An electronic message to generate replenishment order information can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate replenishment order information.

The electronic message can include a replenishment order package containing a replenishment order entity characterizing a replenishment order executed by a vendor for a customer, and a replenishment order item package. The replenishment order item package can contain a replenishment order item entity characterizing an item in a replenishment order, a replenishment order item location package that contains a ship from location entity characterizing a location from which products listed in a replenishment order are to be delivered and a ship to location entity characterizing a location from which products listed in a replenishment order are to be delivered. The replenishment order item package can also include a replenishment order item product information package containing information characterizing a product associated with a replenishment order.

The replenishment order package can contain one or more of a replenishment order party package, a replenishment order delivery information package containing information characterizing a requested delivery for a replenishment order, a replenishment order payment information package containing information characterizing payment information for a replenishment order, and a replenishment order handling unit package containing information characterizing packing requirements for product associated with a replenishment order. The replenishment order party package can include one or more of a buyer party entity characterizing a party that purchases goods associated with a replenishment order, a seller party entity characterizing a party that sells goods associated with a replenishment order, and a vendor party entity characterizing a party to provide a replenishment delivery. In addition, the replenishment order location package can further contain a trans-shipment location entity characterizing a location at product in a replenishment order is transferred from a first transportation mechanism to a second transportation mechanism.

The replenishment order item package can contain one or more of a business transaction documents reference package, a replenishment order item party package, a replenishment order item product information package containing information characterizing a product listed in a replenishment order, a replenishment order item batch package containing information characterizing a batch to be delivered, a replenishment order item promotion package containing information characterizing marketing promotions associated with a replenishment order, a replenishment order item price information package containing pricing information of an item in a replenishment order, and a replenishment order item schedule line package. The business transaction documents reference package can contain on or more of a purchase contract reference entity characterizing a purchase contract or an item in a purchase contract, a scheduling agreement reference entity characterizing a scheduling agreement or an item in a scheduling agreement, a purchase order reference entity characterizing a purchase order of a buyer or a purchase order item created by a vendor, an origin purchase order reference entity characterizing an original purchase order or to an item within an original purchase order, a sales order reference entity characterizing a sales order or an item in a sales order, and an origin sales order reference entity characterizing an original sales order or an item within an original sales order. The replenishment order item party package can contain one or more of a replenishment order item buyer party entity characterizing a party that purchases goods associated with a replenishment order, a replenishment order item product recipient party entity characterizing a party to receive goods associated with a replenishment order, and a replenishment order item bill to party entity characterizing a party to receive an invoice associated with a replenishment order. The replenishment order item schedule line package can contain one or both of a schedule line entity characterizing quantity and scheduling associated with a replenishment order, and a confirmed schedule line entity characterizing a confirmation of quantity and scheduling associated with a replenishment order.

An electronic message to generate replenishment order proposal information can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate replenishment order proposal information.

The message can include a replenishment order proposal package can contain a replenishment order proposal entity characterizing a proposal for an order to replenish product supply and a replenishment order proposal item package. The replenishment order proposal item package can contain a replenishment order proposal item entity characterizing an item in a replenishment order proposal, a replenishment order proposal item location package, and a replenishment order proposal item product information package containing information characterizing a product associated with a replenishment order proposal. The replenishment order proposal location package can contain a ship from location entity characterizing a location from which products listed in a replenishment order proposal are to be delivered and a ship to location entity characterizing a location from which products listed in a replenishment order proposal are to be delivered.

The replenishment order proposal package can contain one or both of a replenishment order proposal party package and a replenishment order proposal business document object reference package containing information characterizing business documents relating to a replenishment order. The replenishment order proposal party package can contain one or more of a buyer party entity characterizing a party that buys goods associated with a replenishment order, a vendor party entity characterizing a party that delivers goods associated with a replenishment order, and a product recipient party entity characterizing a party to which goods associated with a replenishment order are delivered. The product information package can contain one or both of a product category entity characterizing a category of a product associated with a replenishment order proposal, and a vendor product category entity characterizing a vendor category of a product associated with a replenishment order proposal.

The replenishment order proposal item package can contain one or more of a replenishment order proposal item price information package containing information characterizing pricing of a product associated with a proposed replenishment order, a replenishment order proposal item party package containing information characterizing parties associated with a proposed replenishment order a replenishment order proposal item location package, a replenishment order proposal item business document object reference package containing information characterizing business documents relating to a replenishment order, and a schedule line package. The replenishment order proposal item location package can contain one or both of a ship from location entity characterizing a location from which products listed in a replenishment order proposal are to be delivered, and a ship to location entity characterizing a location from which products listed in a replenishment order proposal are to be delivered. The schedule line package can contain one or both of a schedule line entity characterizing quantity and scheduling associated with a replenishment order proposal, and a confirmed schedule line entity characterizing a confirmation of quantity and scheduling associated with a replenishment order proposal.

Generating a notification associated with a return delivery is accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiating transmission of the message to a second application to generate a notification associated with a return delivery. The generated message includes a return delivery instruction package. The included return delivery instruction package further contains a return delivery instruction entity characterizing logistical instructions to a vendor for a future return delivery and a return delivery instruction item package containing a product information package containing information characterizing.

The return delivery instruction package can further include a party package and a location package. A party package can contain a buyer party entity characterizing a party that has purchased goods being returned or has reordered a repurchase of goods. A party package can also contain a vendor entity characterizing a party that sends backs goods to be returned. A party package can further contain a product recipient entity characterizing a company to which goods are returned. In addition, a location package can contains a ship to entity characterizing a location from which goods for return are sent back and a ship to location characterizing a location to which goods for return are sent back.

The return delivery instruction package can further include a return delivery item package and a delivery handling unit package. A return delivery item package can contain a return delivery instruction item entity characterizing a quantity of product to be returned and an associated delivery period. A return delivery item package can also contain a delivery item business transaction document reference package characterizing business document references relevant to a product to be returned A return delivery item package can also contain a party package containing information characterizing business partners relevant to a product to be returned. A return delivery item package can further contain a batch package containing information characterizing a batch of product to be returned. In addition, a delivery handling unit package containing information characterizing handling requirements for a product to be returned.

Generating a notification associated with a return delivery can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating a generation of a notification associated with a return delivery. The message includes a return delivery instruction package. The return delivery instruction package further includes a return delivery instruction entity characterizing logistical instructions to a vendor for a future return delivery, and a return delivery instruction item package containing a product information package containing information characterizing.

Exchanging information associated with a request for quotation is accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiate transmission of the message to a second application.

Exchanging information associated with a request for quotation is accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating an exchange of information associated with a request for quotation.

The generated and received message includes a package that contains various other packages that contain information associated with a request for quotation. The package contains a party package, a location package, a delivery information package, a payment information package, a product information package, a business transaction document reference package, a follow up business transaction document reference package, an attachment package, a description package, and an item package.

Each of the information containing packages contain different information associated with a request for quotation. A party package contains information characterizing parties associated with a request for quotation. A location package contains information characterizing locations associated with a request for quotation. A delivery information package contains information characterizing a required delivery associated with a request for quotation. A payment information package contains information characterizing payment information associated with a request for quotation. A product information package contains information characterizing a product category associated with a request for quotation. A business transaction document reference package contains information characterizing business document references associated with a request for quotation. A follow up business transaction document reference package contains information characterizing business transaction documents expected by a buying party associated with a request for quotation. An attachment package contains information characterizing documents referring to a request for quotation. A description package contains information characterizing text visible to parties to a request for quotation.

An item package also contains various information containing packages including a product information package, a party package, a delivery information package, a business transaction document reference package, an attachment package, a description package, and a schedule line package. A product information package contains information characterizing a product tendered by a request for quotation. A party package contains information characterizing parties associated with a request for quotation. A delivery information package contains information characterizing delivery of a product. A business transaction document reference package contains information characterizing a required delivery associated with a request for quotation. An attachment package contains information characterizing documents referring to a request for quotation. A description package contains information characterizing text visible to parties to a request for quotation. A schedule line package contains information characterizing quantity and date information associated with a request for quotation.

The information contained in the various packages is selected from a group including a request from a buyer to a bidder to start a request for quotation process, a request from a buyer to a bidder to modify a request for quotation during a request for quotation process, a cancellation of a request for quotation, a notification from a bidder to a buyer containing a response by the bidder to an invitation to respond to a request for quotation, a notification of an acceptance of a bid in response to a request for quotation, a notification of a declination of a bid in response to a request for quotation, a confirmation from a bidder to a buyer indicating that the bidder intends to submit a bid in response to a request for quotation, a confirmation from a bidder to a buyer indicating an acceptance or rejection of a quotation accepted by the buyer, a request to generate a legal text document in response to an invitation to bid for quotation, and a notification of a generation of a legal text document in response to an invitation to bid on a request for quotation.

Exchanging information associated with services that have been entered can be accomplished by using a first application executing in a landscape of computer systems providing message-based services to generate an electronic message and initiate transmission of the message to a second application. The generated message includes a service acknowledgement package. The service acknowledgement package contains a service acknowledgement entity characterizing information about a confirmation by a purchase of an entered service and a party package. The party package further contains a buyer party entity characterizing a party that purchases goods or services.

The party package can further contain a seller party entity characterizing a party selling goods or services. The party package can also contain a product recipient party entity characterizing a party to which goods are delivered or for whom services are provided. The party package can also contain vendor party entity characterizing a party that delivers goods or provides services. The party package can further contain a manufacturer party entity characterizing a party that manufactures goods.

The service acknowledgement package can further contain a location package containing information characterizing a location at which products have been delivered or a service provided. The service acknowledgement package can also contain an attachment package containing information characterizing a document referring to a service acknowledgement. The service acknowledgement package can also contain a description package containing information characterizing text regarding a service acknowledgement. Also, the service acknowledgement package can further contain an item package. The item package can contain an item entity characterizing an entered service or service product. The item package can also contain a hierarchy relationship entity characterizing a relationship between items in a hierarchy and a product information package. The product information package can contain a product entity characterizing a product, and a product category entity characterizing a category for a product. The service acknowledgement package can also contain a price information package containing information characterizing price information for a service acknowledgement item. The service acknowledgement package can also contain a party package containing information characterizing parties associated with a service acknowledgement. The service acknowledgement package can also contain a location package containing information characterizing a location at which a products have been delivered or services provided.

The service acknowledgement package can also contain a business document object reference package. The business document object reference package can contain a purchase order reference entity characterizing a purchase order or an item within a purchase order. The business document object reference package can also contain a service acknowledgement reference entity characterizing a previously sent service acknowledgement. The business document object reference package can also contain a purchase contract reference entity characterizing a reference to a purchase contract or an item within a purchase contract. The business document object reference package can also contain a sales contract reference entity characterizing a reference to a sales contract or an item within a sales contract. The business document object reference package can also contain a buyer product catalogue reference entity characterizing a reference to a product catalogue of a buyer or an item within a product catalogue of a buyer. The business document object reference package can further contain a seller product catalogue reference entity characterizing a reference to a product catalogue of a seller or an item within a product catalogue of a seller. The service acknowledgement package can also contain an attachment package containing information characterizing a document referring to a service acknowledgement, The service acknowledgement package can further contain a description package containing information characterizing text regarding a service acknowledgement.

The business document object reference package can further contain a project reference entity characterizing a reference to a project or an element within a project. The business document object reference package can further contain a project element assignment entity characterizing an assignment of two elements within a project that is referenced by an item of a service acknowledgment. In addition, the item package can further contain an accounting package containing information characterizing account assignment information.

Exchanging information associated with services that have been entered can be accomplished by receiving an electronic message in a landscape of computer systems providing message-based services and initiating an exchange of information associated with services that have been entered. The received message includes a service acknowledgement package. The service acknowledgement package includes a service acknowledgement entity characterizing information about a confirmation by a purchase of an entered service. The service acknowledgement package further includes a party package, which contains a buyer party entity characterizing a party that purchases goods or services.

An electronic message to request generation of a supply chain exception notification can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate a supply chain exception notification. Responding to a request to generate the supply chain exception notification can include receiving a message including a supply chain exception package and initiating generation of the supply chain exception notification. The supply chain exception package can contain a supply chain exception report entity, a business transaction document reference package, a location package and a product information package. The supply chain exception report entity can characterize an exception that occurred in a supply chain. The business transaction document reference package can contain a purchaser order entity that can characterize a reference to a purchase order or an item within a purchase order for which an exception in a supply chain has occurred. The location package can contain a ship from location that can characterize a location from which ordered products are delivered. A product information package can characterize a product associated with a supply chain exception.

In some variations, the message requesting generation of a supply chain exception notification can further include a party package containing a buyer party entity, a vendor party entity and a product recipient entity. The buyer party entity can characterize a buyer of goods or services. The vendor party entity can characterize a vendor of goods or services. The product recipient entity can characterize a recipient of goods or services. The business transaction document reference package can further contain a scheduling agreement reference entity, a sales order reference entity, an inbound delivery reference entity and a batch package. The scheduling agreement reference entity can characterize a reference to an item in a scheduling agreement. The sales order reference entity can characterize a reference to a sales order or to an item in a sales order. The inbound delivery reference entity can characterize an inbound delivery or an item of an inbound delivery. The supply chain exception package can further contain a batch package. The batch package can contain a batch entity, a property valuation package and a log package. The batch entity can characterize a batch of products. The property valuation package can characterize properties of a characteristic of a supply chain exception. The log package can contain a validation log entity that can characterize a logistics planning or logistics execution check log. The log package can also contain an item entity. The location package can further contain a ship to location entity that can characterize a location where ordered products are delivered.

An electronic message to generate a tax declaration can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to provide tax declaration information to generate a tax declaration based on a purchase. Responding to a request to generate a tax declaration can include receiving a message including a tax declaration package and initiating a generation of a tax declaration. A tax declaration package can contain a log package and a party package, where the log package can contain a validation log entity characterizing log messages from a tax authority associated with a receipt and validation of a tax return based on a purchase, and the party package can contain a tax payer party entity that characterizes a party liable for tax on a purchase. The party package can also contain a tax authority party entity that characterizes a tax authority that receives a tax declaration. In some variations, a log package can also contain an item entity. The item entity can characterize a log of a receipt and validation of a tax refund based on a purchase. The party package can also contain a tax operator entity that characterizes a party that creates and sends a tax return for tax on purchases. A declaration package can also contain an item package that characterizes reported taxes on purchases.

An electronic message to create information associated with a vendor initiated purchase order can be generated by a first application that executes in a landscape of computer systems providing message-based services. Transmission of the message to a second application can be initiated in order to generate information associated with a vendor initiated purchase order.

The message can include a vendor generated order package containing a vendor generated order entity characterizing a purchaser order that is initiated by a vendor for a customer, a party package, a location package, and a vendor generated order item package. The party package can contain a buyer party entity characterizing a party to receive a goods replenishment delivery, and a vendor party entity characterizing a party to provide a goods replenishment delivery. The location package can contain a ship from location entity characterizing a location from which goods associated with a purchase order is to be delivered, and a ship to location entity characterizing a location at which goods associated with a purchase order is to be delivered. The vendor generated order item package can contain a vendor generated order item entity characterizing quantities of goods and associated delivery and location conditions for goods in a purchase order, and a product information package containing information characterizing goods associated with a purchase order. The location package can further contain a trans-shipment location entity characterizing a location at which delivery of products using a first transport mechanism changes to second transport mechanism. The vendor generated order package can also contain a handling unit containing information characterizing packing requirements for goods associated with a replenishment order.

The vendor generated order item package can further contain one or more of a business transaction document reference package, a promotion package containing information characterizing marketing promotions relevant to goods associated with a purchase order, and a schedule line package. The business transaction document reference package can contain one or both of a purchasing contract reference entity characterizing a purchase contract or an item in a purchase contract and a sales order reference entity characterizing a sales order or an item in a sales order. The schedule line package can contain one or more of a schedule line entity characterizing quantity and scheduling dates for replenishment deliveries of goods associated with a purchase order, and a confirmed schedule line entity characterizing confirmed quantity and scheduling dates for replenishment deliveries of goods associated with a purchase order.

Adapters and other proxies can be utilized such that messages or other data structures that are not in a format compatible with the generated and received messages can be utilized in connection with the subject matter described herein. For example, generating the message can include converting or mapping a non-compatible message format or other data structure into a compatible message type prior to its transmission. Similarly, a received message can be subsequently converted or mapped into a non-compatible message format or other data structure to effect the actions specified by the received message.

Other systems, methods, features and advantages of the subject matter described herein will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that such additional systems, methods, features and advantages be included within this description, be within the scope of the subject matter described herein, and be protected by the accompanying claims.

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an implementation of the subject matter described herein and, together with the description, serve to explain the advantages and principles of the subject matter described herein. In the drawings,

FIGS. 1A-1G depict problems that may arise without the use of consistent interfaces;

FIG. 1 depicts a flow diagram of the overall steps performed by methods and systems consistent with the subject matter described herein;

FIG. 2 depicts a scenario variant model in accordance with methods and systems consistent with the subject matter described herein;

FIG. 3 depicts a process interaction model for invoice processing in accordance with methods and systems consistent with the subject matter described herein;

FIG. 4 depicts a business document flow for an invoice request in accordance with methods and systems consistent with the subject matter described herein;

FIG. 5 depicts data processing systems suitable for practicing methods and systems consistent with the subject matter described herein;

FIG. 6 depicts message categories in accordance with methods and systems consistent with the subject matter described herein;

FIG. 7 depicts a message choreography for a purchase order scenario in accordance with methods and systems consistent with the subject matter described herein;

FIG. 8 depicts a message choreography of a Master Data Management in accordance with methods and systems consistent with the subject matter described herein;

FIG. 9 depicts a message choreography of a Source of Supply, Purchase Requirement, and Purchase Order in accordance with methods and systems consistent with the subject matter described herein;

FIG. 10 depicts a message choreography of a Product Demand, Product Forecast and Product Activity in accordance with methods and systems consistent with the subject matter described herein;

FIG. 11 depicts a message choreography of a RFQ and Quote in accordance with methods and systems consistent with the subject matter described herein;

FIG. 12 depicts a message choreography of Purchasing in accordance with methods and systems consistent with the subject matter described herein;

FIG. 13 depicts a message choreography of Sales in accordance with methods and systems consistent with the subject matter described herein;

FIG. 14 depicts a message choreography of a Vendor Managed Inventory/Responsive Replenishment in accordance with methods and systems consistent with the subject matter described herein;

FIG. 15 depicts a message choreography of an Advanced Shipment Notification and Proof of Delivery in accordance with methods and systems consistent with the subject matter described herein;

FIG. 16 depicts a message choreography of a Service Acknowledgement in accordance with methods and systems consistent with the subject matter described herein;

FIG. 17 depicts a message choreography of an Inventory Change in accordance with methods and systems consistent with the subject matter described herein;

FIG. 18 depicts a message choreography of Billing Due in accordance with methods and systems consistent with the subject matter described herein;

FIG. 19 depicts a message choreography of Invoicing Due in accordance with methods and systems consistent with the subject matter described herein;

FIG. 20 depicts a message choreography of an Invoice in accordance with methods and systems consistent with the subject matter described herein;

FIG. 21 depicts a message choreography of Invoice Accounting and Payment Due in accordance with methods and systems consistent with the subject matter described herein;

FIG. 22 depicts a message choreography of Tax Due in accordance with methods and systems consistent with the subject matter described herein;

FIG. 23 depicts a message choreography of Credit Worthiness, Credit Agency Report, Credit Payment, and Credit Commitment in accordance with methods and systems consistent with the subject matter described herein;

FIG. 24 depicts a message choreography of a Personnel Time Sheet in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 25-251 depict data type structures in accordance with methods and systems consistent with the subject matter described herein;

FIG. 252 depicts an example of a package in accordance with methods and systems consistent with the subject matter described herein;

FIG. 253 depicts another example of a package in accordance with methods and systems consistent with the subject matter described herein;

FIG. 254 depicts a third example of a package in accordance with methods and systems consistent with the subject matter described herein;

FIG. 255 depicts a fourth example of a package in accordance with methods and systems consistent with the subject matter described herein;

FIG. 256 depicts the representation of a package in the XML schema in accordance with methods and systems consistent with the subject matter described herein;

FIG. 257 depicts a graphical representation of cardinalities between two entities in accordance with methods and systems consistent with the subject matter described herein;

FIG. 258 depicts an example of a composition in accordance with methods and systems consistent with the subject matter described herein;

FIG. 259 depicts an example of a hierarchical relationship in accordance with methods and systems consistent with the subject matter described herein;

FIG. 260 depicts an example of an aggregating relationship in accordance with methods and systems consistent with the subject matter described herein;

FIG. 261 depicts an example of an association in accordance with methods and systems consistent with the subject matter described herein;

FIG. 262 depicts an example of a specialization in accordance with methods and systems consistent with the subject matter described herein;

FIG. 263 depicts the categories of specializations in accordance with methods and systems consistent with the subject matter described herein;

FIG. 264 depicts an example of a hierarchy in accordance with methods and systems consistent with the subject matter described herein;

FIG. 265 depicts a graphical representation of a hierarchy in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 266A-B depict a flow diagram of the steps performed to create a business object model in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 267A-NN depict the business object model in accordance with methods and systems consistent with the subject matter described herein;

FIG. 268 depicts the message choreography for the Invoice interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 269A-F depict a flow diagram of the steps performed to generate an interface from the business object model in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 270A-C depict examples of package templates in accordance with methods and systems consistent with the subject matter described herein;

FIG. 271 depicts the package template of FIG. 270A after the removal of a package in accordance with methods and systems consistent with the subject matter described herein;

FIG. 272 depicts an entity template for the party package from the business object model in accordance with methods and systems consistent with the subject matter described herein;

FIG. 273 depicts the entity template for the party package of FIG. 272 after removal of an entity in accordance with methods and systems consistent with the subject matter described herein;

FIG. 274 depicts the party package of FIG. 272 after removal of the nonessential entities for the Invoice Request in accordance with methods and systems consistent with the subject matter described herein;

FIG. 275 depicts a portion of the business object model in accordance with methods and systems consistent with the subject matter described herein;

FIG. 276 depicts a further portion of the business object model in accordance with methods and systems consistent with the subject matter described herein;

FIG. 277 depicts the package template of FIG. 270A after the removal of the nonessential packages for the Invoice Request in accordance with methods and systems consistent with the subject matter described herein;

FIG. 278 depicts package template of FIG. 277 after the “business transaction document” is changed in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 279A-N depict a data model for Invoice interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 280A-K depict an element structure for Invoice interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 281 depicts an example illustrating the transmittal of a business document in accordance with methods and systems consistent with the subject matter described herein;

FIG. 282 depicts an interface proxy in accordance with methods and systems consistent with the subject matter described herein;

FIG. 283 depicts an example illustrating the transmittal of a message using proxies in accordance with methods and systems consistent with the subject matter described herein;

FIG. 284 depicts components of a message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 285 depicts IDs used in a message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 286 depicts a reference to previous messages in accordance with methods and systems consistent with the subject matter described herein;

FIG. 287 depicts a reference to business documents from previous transactions in accordance with methods and systems consistent with the subject matter described herein;

FIG. 288 depicts a message choreography for Purchase Requirement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 289A-H depict a data model for Purchase Requirement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 290A-G depict an element structure for Purchase Requirement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 291 depicts message choreography for a Source of Supply interface in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 292A-C depict a data model for the Source of Supply interface in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 293A-D depict an element structure for the Source of Supply interface in accordance with methods and systems consistent with the subject matter described herein;

FIG. 294 depicts a message choreography for Purchase Order interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 295A-P depict the data model for the Purchase Order interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 296 depicts a data mode for the Purchase Order Cancellation interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 297A-ZA depict an element structure for the Purchase Order interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 298 depicts a message choreography for Service Acknowledgement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 299A-J depict a data model for the Service Acknowledgement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 300A-O depict an element structure for the Service Acknowledgement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 301 depicts a message choreography for RFQ interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 302A-K depict a data model for the RFQ interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 303 depicts a data model for RFQ Cancellation interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 304A-J depict a data model for Quote interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 305A-D depict a data model for RFQ Result interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 306A-R depict an element structure for RFQ interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 307A-C depict an element structure for RFQ Cancellation interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 308A-N depict an element structure for Quote interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 309A-D depict an element structure for RFQ Request interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 310 depicts a message choreography for Order to Invoice in accordance with methods and systems consistent with the subject matter described herein;

FIG. 311 depicts a message choreography for the Order to Invoice provided by RosettaNet;

FIG. 312 depicts a message choreography for the Order to Invoice provided by CIDX;

FIGS. 313-317 depict a hierarchization process in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 318 - 358 QG depict additional data type structures in accordance with methods and systems consistent with the subject matter described herein;

FIG. 359 depicts a message choreography for the Catalogue interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 360A-F depict a data model for Catalogue Update Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 361A-AK depict an element structure for the Catalogue Update Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 362A-F depict a data model for Catalogue Publication Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 363A-AK depict an element structure for Catalogue Publication Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 364 depicts a data model for Catalogue Publication Transmission Package Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 365A-B depict an element structure for the Catalogue Publication Transmission Package Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 366 depicts a data model for Catalogue Publication Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 367A-B depict an element structure for the Catalogue Publication Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 368 depicts a data model for Catalogue Publication Transmission Cancellation Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 369A-B depict an element structure for Catalogue Publication Transmission Cancellation Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 370 depicts a data model for Catalogue Publication Transmission Cancellation Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 371A-B depict an element structure for the Catalogue Publication Transmission Cancellation Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 372 depicts a data model for Catalogue Publication Transmission Item Lock Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 373A-C depict an element structure for the Catalogue Publication Transmission Item Lock Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 374 depicts a data model for Catalogue Publication Transmission Item Lock Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 375A-B depict an element structure for Catalogue Publication Transmission Item Lock Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 375 AA-AB depict a data model for Catalogue Publication Transmission Content Change Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 375 BA depicts a data model for Catalogue Publication Transmission Content Change Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 375 BB depicts an illustration of a Catalog Content Management system in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 375 CA-CL depict the element structure for a CataloguePublicationTransmissionContentChangeRequestMessage in accordance with methods and systems consistent with the subject matter described herein:

FIGS. 375 DA-B depict the element structure for a CataloguePublicationTransmissionContentChangeConfirmationMessage in accordance with methods and systems consistent with the subject matter described herein.

FIG. 376 depicts a message choreography for the Purchase Order Information interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 377A-O depict a data model for Purchase Order Information Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 378A-S depict an element structure for the Purchase Order Information Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 378 AA-AR depict an element structure for Purchase Order Information Legal Document Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 379 depicts a message choreography for Tax Due interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 380A-C depict a data model for Tax Due Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 381A-D depict an element structure for the Tax Due Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 382 depicts a message choreography for Delivery Information interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 383A-G depict a data model for Delivery Information Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 384A-N depict an element structure for the Delivery Information Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 385 depicts a message choreography for Personnel Timesheet Information interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 386 depicts a data model for Personnel Timesheet Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 387A-C depict an element structure for Personnel Timesheet Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 388 depicts a message choreography for Credit Worthiness interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 389 depicts a data model for Credit Worthiness Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 390 depicts a data model for Credit Worthiness Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 391A-E depict an element structure for the Credit Worthiness Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 392A-C depict an element structure for the Credit Worthiness Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 393 depicts a message choreography for Credit Agency Report interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 394 depicts a data model for Credit Agency Report Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 395A-B depict a data model for Credit Agency Report Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 396A-C depict an element structure for the Credit Agency Report Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 397A-E depict an element structure for the Credit Agency Report Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 398 depicts a message choreography for Invoicing Accounting interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 399 depicts a data model for Accounting Cancellation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 400A-B depict an element structure for Accounting Cancellation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 401 depicts a message choreography for Invoice Due interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 402A-M depict a data model for Invoice Due Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 403 depicts a data model for Invoice Due Cancellation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 404A-J depict an element structure for the Invoice Due Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 405 depicts a message choreography for Inventory Change interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 406A-B depict a data model for Inventory Change Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 407A-D depict an element structure for the Inventory Change Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 408 depicts a message choreography for Sales Order Fulfillment interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 409A-L depict a data model for Sales Order Fulfillment Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 410A-M depict an element structure for Sales Order Fulfillment Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 411 depicts a message choreography for Delivery interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 412A-C depict a data model for Despatched Delivery Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 413 depicts a data model for Received Delivery Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 414A-N depict an element structure for Despatched Delivery Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 415A-C depict an element structure for Received Delivery Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 416 depicts a message choreography for Invoice Accounting interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 417A-C depict a data model for Invoice Accounting Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 418A-E depict an element structure for Invoice Accounting Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 419 depicts a message choreography for Delivery Execution Request interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 420A-L depict a data model for Delivery Execution Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 421A-K depict an element structure for the Delivery Execution Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 422 depicts a message choreography for Delivery Schedule interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 423A-C depict a data model for Delivery Schedule Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 424A-V depict an element structure for the Delivery Schedule Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 424 AA-AU depict an element structure for the Delivery Schedule Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 424 BA-BJ depict an element structure for the Delivery Schedule Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 425 depicts a message choreography for Invoice Issued Information interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 426 depicts a data model for Invoice Issued Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 427A-B depict an element structure for the Invoice Issued Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 428 depicts a message choreography for Product Activity interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 429 depicts a data model for Product Activity Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 430A-L depict an element structure for the Product Activity Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 431 depicts a message choreography for Payment Due invoices in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 432A-C depict a data model for Payment Due Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 433A-D depict an element structure for Payment Due Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 434 depicts a message choreography for Order ID Assignment interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 435 depicts a data model for Order ID Assignment Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 436A-E depict an element structure for the Order ID Assignment Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 437 depicts a message choreography for Product Demand Influencing Event interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 438 depicts a data model for ProductDemand Influencing Event Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 439A-L depict an element structure for the ProductDemand Influencing Event Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 440 depicts a message choreography for Product Forecast interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 441 depicts a data model for Product Forecast Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 442A-J depict an element structure for the Product Forecast Notification Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 443 depicts a message choreography for Product Forecast Revision interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 444 depicts a data model for Product Forecast Revision Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 445A-M depict an element structure for the Product Forecast Revision Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 446 depicts a message choreography for Replenishment Order interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 447A-F depict the data model for Replenishment Order Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 448A-FF depict an element structure for the Replenishment Order Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 449 depicts a message choreography for Vendor Generated Order interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 450A-B depict the data model for the Vendor Generated Order Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 451A-O depict an element structure for the Vendor Generated Order Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 452 depicts a message choreography for Bank Account Balance interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 453 depicts a data model for Bank Account Balance Report Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 454 depicts a data model for Bank Account Balance Report Response Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 455A-B depict an element structure for the Bank Account Balance Report Response Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 456A-B depict an element structure for the Bank Account Balance Report Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 457 depicts a message choreography for Bank Account Statement interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 458A-E depict the data model for Bank Account Statement Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 459A-I depict an element structure for the Bank Account Statement Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 460 depicts a message choreography for Business Transaction Document Image Recognition Request interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 461 depicts a data model for Business Transaction Document Image Recognition Request in accordance with methods and systems consistent with the subject matter described herein;

FIG. 462 depicts an element structure for the Business Transaction Document Image Recognition Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 463 depicts a message choreography for Collective Payment Order interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 464A-F depict the data model for Collective Payment Order in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 465A-F depict an element structure for the Collective Payment Order Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 466 depicts a message choreography for Credit Payment Behavior Summary interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 467 depicts a data model for Credit Payment Behavior Summary Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 468A-H depict an element structure for the Credit Payment Behaviour Summary Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 469 depicts a message choreography for Customs Vendor Declaration interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 470 depicts a data model for the Customs Vendor Declaration Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 471A-G depict an element structure for the Customs Vendor Declaration Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 472 depicts a message choreography for Invoice interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 473A-D depict the data model for Supplier Invoice Information Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 474 depicts a data model for Supplier Invoice Settlement Release Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 475 depicts a data model for Supplier Invoice Cancellation Execution Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 476A-D depict the data model for Invoice Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 477A-J depict an element structure for the Invoice Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 478 depicts a message choreography for Loan Contract interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 479 depicts a data model for Loan Calculation Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 480 depicts a data model for Loan Calculation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 481A-C depict the data model for the Loan Contract in accordance with methods and systems consistent with the subject matter described herein;

FIG. 482 depicts a data model for Loan Contract Create Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 483A-E depicts an element structure for Loan Contract Create Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 484A-B depicts an element structure for the Loan Calculation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 485A depicts an element structure for the Loan Contract Create Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 486A-B depict an element structure for the Loan Calculation Query Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 487 depicts a message choreography for Purchase Request interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 488A-D depict the data model for Purchase Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 489 depicts a data model for Purchase Request Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 490A-J depict an element structure for the Purchase Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 491A-B depict an element structure for the Purchase Request Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 492 depicts a message choreography for Purchasing Contract interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 493A-D depict the data model for the Purchasing Contract Use Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 494 depicts a data model for the Purchasing Contract Release Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 495A-D depict an element structure for the Purchasing Contract Release Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 496A-J depict an element structure for the Purchasing Contract Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 497 depicts a message choreography for Replenishment Order Proposal interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 498A-C depict the data model for Replenishment Order Proposal Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 499A-I depict an element structure for the Replenishment Order Proposal Request Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 499 AA-AM depict an element structure for the Replenishment Order Proposal Confirmation Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 500 depicts a message choreography for Return Delivery Instruction interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 501A-C depict the data model for the Return Delivery Instruction Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 502A-L depict an element structure for the Return Delivery Instruction Notification in accordance with methods and systems consistent with the subject matter described herein;

FIG. 503 depicts a message choreography for RFQ Legal Document interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 504A-L depict the data model for the RFQ Legal Document Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 505A-M depict an element structure for the RFQ Legal Document Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 506 depicts a message choreography for Supply Chain Exception interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 507A-C depict the data model for Supply Chain Exception Report Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 508A-P depict an element structure for the Supply Chain Exception Report Message in accordance with methods and systems consistent with the subject matter described herein;

FIG. 509 depicts a message choreography for VATDeclaration interfaces in accordance with methods and systems consistent with the subject matter described herein;

FIG. 510 depicts a data model for VATDeclaration Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 511A-F depict an element structure for the VATDeclaration Message in accordance with methods and systems consistent with the subject matter described herein;

FIGS. 512A-E depict an element structure for the VATDeclaration Request Message in accordance with methods and systems consistent with the subject matter described herein; and,

FIGS. 513A-D depict an element structure for the VATDeclaration Confirmation Message in accordance with methods and systems consistent with the subject matter described herein.

Reference will now be made in detail to an implementation consistent with the subject matter described herein as illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings and the following description to refer to the same or like parts.

A. Overview

Methods and systems consistent with the subject matter described herein facilitate e-commerce by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. To generate consistent interfaces, methods and systems consistent with the subject matter described herein utilize a business object model, which reflects the data that will be used during a given business transaction. An example of a business transaction is the exchange of purchase orders and order confirmations between a buyer and a seller. The business object model is generated in a hierarchical manner to ensure that the same type of data is represented the same way throughout the business object model. This ensures the consistency of the information in the business object model. Consistency is also reflected in the semantic meaning of the various structural elements. That is, each structural element has a consistent business meaning. For example, the location entity, regardless of in which package it is located, refers to a location.

From this business object model, various interfaces are derived to accomplish the functionality of the business transaction. Interfaces provide an entry point for components to access the functionality of an application. For example, the interface for a Purchase Order Request provides an entry point for components to access the functionality of a Purchase Order, in particular, to transmit and/or receive a Purchase Order Request. One skilled in the art will recognize that each of these interfaces may be provided, sold, distributed, utilized, or marketed as a separate product or as a major component of a separate product. Alternatively, a group of related interfaces may be provided, sold, distributed, utilized, or marketed as a product or as a major component of a separate product. Because the interfaces are generated from the business object model, the information in the interfaces is consistent, and the interfaces are consistent among the business entities. Such consistency facilitates heterogeneous business entities in cooperating to accomplish the business transaction.

Without cross-component consistency, different conceptual approaches lead to different interface structures, resulting in incompatible interfaces. For example, FIGS. 1A-C depict three different approaches to a transport condition 102 a , 102 b , 102 c , which specifies how products are to be transported. The transport condition 102 a , 102 b , 102 c , considers a business partner 104 a , 104 b , 104 c , a product 106 a , 106 b , 106 c , and a combination of the business partner and the product 108 a , 108 b , 108 c.

As depicted in FIG. 1A , the transport condition 102 a may depend on the business partner 104 a . Alternatively, as depicted in FIG. 1B , the transport condition 102 b may depend on the product 106 b . As a third alternative, the transport condition 102 c may depend on the combination of the business partner and the product 108 c . These three conceptual models represent three different object models that may be used to derive interfaces.

FIGS. 1D-F depict the resulting consistent interfaces from these object models. In particular, FIG. 1D depicts an interface for quotations 102 d , an interface for purchase orders 104 d and an interface for goods issued 106 d derived using the conceptual model depicted in FIG. 1A . FIG. 1E depicts these same respective interfaces 102 e , 104 e , 106 e derived using the conceptual model depicted in FIG. 1B . FIG. 1F depicts these same respective interfaces 102 f , 104 f , 106 f derived using the conceptual model depicted in FIG. 1C . As depicted in FIG. 1G , inconsistent interfaces 102 g , 104 g , 106 g result without a cross-component understanding of a transport condition.

FIG. 1 depicts a flow diagram of the overall steps performed by methods and systems consistent with the subject matter described herein. Initially, to generate the business object model, design engineers study the details of a business process, and model the business process using a “business scenario” (step 100 ). The business scenario identifies the steps performed by the different business entities during a business process. Thus, the business scenario is a complete representation of a clearly defined business process. For example, in FIG. 2 , a scenario variant model is used to depict an illustrative business scenario for a Maintenance Repair Operation (“MRO”) Procurement 200 . The developers use these scenario variant models to depict the individual process steps performed by the business entities during the business process.

For an MRO Procurement, the customer initially processes an internal request (step 202 ). The internal request corresponds to the customer's internal documentation for the requested maintenance or repair. The customer then processes a purchase request (step 204 ). The purchase request corresponds to the customer's internal documentation for a specific product or service related to the maintenance or repair. Next, the customer processes a purchase order (step 206 ), which is sent to the supplier. This prompts the supplier to process a sales order (step 208 ). The sales order is the supplier's internal documentation regarding the requested product or service. After processing the sales order, the supplier processes an outbound delivery (step 210 ), which is the supplier's internal documentation identifying the products or services that will be provided to the customer. The supplier then sends a goods and services confirmation to the customer (step 212 ). Next, the supplier processes a customer invoice (step 214 ) and sends the invoice to the customer. Upon receiving the invoice, the customer processes the supplier invoice (step 216 ). The customer also processes a due item (step 218 ). The due item summarizes the information regarding the product or service ordered by the customer. Next, the customer processes the payment (step 220 ) by sending the payment information to the business partner and sending the payment information to the house bank. After receiving the payment information, the business partner processes the payment (step 222 ), and the bank processes the payment (step 224 ). The bank also creates a bank statement (step 226 ) and forwards the bank statement information to the customer. During the MRO Procurement, the customer also processes an accounting document (step 228 ). The accounting document is the customer's internal documentation regarding the payment to the supplier.

Returning to the overall process in FIG. 1 , after creating the business scenario, the developers add details to each step of the business scenario (step 102 ). In particular, for each step of the business scenario, the developers identify the complete process steps performed by each business entity. A discrete portion of the business scenario reflects a “business transaction,” and each business entity is referred to as a “component” of the business transaction. The developers also identify the messages that are transmitted between the components. A “process interaction model” represents the complete process steps between two components. For example, FIG. 3 depicts the process interaction model for the invoice processing 230 between the supplier 300 , which processes the customer invoice, and the customer 302 , which processes the supplier invoice.

The supplier uses an Invoice Request Out interface 304 to send an Invoice Request message 306 to the customer. The customer uses the Invoice Request In interface 308 to receive the Invoice Request message (step 310 ), and to create an internal instantiation of the supplier invoice 312 . The customer processes the supplier invoice (step 314 ), and uses an Invoice Confirmation Out interface 316 to send an Invoice Confirmation 318 to the supplier. The supplier uses an Invoice Confirmation In interface 320 to receive the Invoice Confirmation 318 .

Returning to FIG. 1 , after creating the process interaction model, the developers create a “message choreography” (step 104 ), which depicts the messages transmitted between the two components in the process interaction model. The developers then represent the transmission of the messages between the components during a business process in a “business document flow” (step 106 ). Thus, the business document flow illustrates the flow of information between the business entities during a business process.

FIG. 4 depicts an exemplary business document flow 400 for the process of purchasing a product or service. The business entities involved with the illustrative purchase process include Accounting 402 , Payment 404 , Invoicing 406 , Supply Chain Execution (“SCE”) 408 , Supply Chain Planning (“SCP”) 410 , Fulfillment Coordination (“FC”) 412 , Supply Relationship Management (“SRM”) 414 , Supplier 416 , and Bank 418 . The business document flow 400 is divided into four different transactions: Preparation of Ordering (“Contract”) 420 , Ordering 422 , Goods Receiving (“Delivery”) 424 , and Billing/Payment 426 . In the business document flow, arrows 428 represent the transmittal of documents. Each document reflects a message transmitted between entities. One of ordinary skill in the art will appreciate that the messages transferred may be considered to be a communications protocol. The process flow follows the focus of control, which is depicted as a solid vertical line (e.g., 429 ) when the step is required, and a dotted vertical line (e.g., 430 ) when the step is optional.

During the Contract transaction 420 , the SRM 414 sends a Source of Supply Notification 432 to the SCP 410 . This step is optional, as illustrated by the optional control line 430 coupling this step to the remainder of the business document flow 400 .

During the Ordering transaction 422 , the SCP 410 sends a Purchase Requirement Request 434 to the FC 412 , which forwards a Purchase Requirement Request 436 to the SRM 414 . The SRM 414 then sends a Purchase Requirement Confirmation 438 to the FC 412 , and the FC 412 sends a Purchase Requirement Confirmation 440 to the SCP 410 . The SRM 414 also sends a Purchase Order Request 442 to the Supplier 416 , and sends Purchase Order Information 444 to the FC 412 . The FC 412 then sends a Purchase Order Planning Notification 446 to the SCP 410 . The Supplier 416 , after receiving the Purchase Order Request 442 , sends a Purchase Order Confirmation 448 to the SRM 414 , which sends a Purchase Order Information confirmation message 454 to the FC 412 , which sends a message 456 confirming the Purchase Order Planning Notification to the SCP 410 . The SRM 414 then sends an Invoice Due Notification 458 to Invoicing 406 .

During the Delivery transaction 424 , the FC 412 sends a Delivery Execution Request 460 to the SCE 408 . The Supplier 416 could optionally 450 send a Despatched Delivery Notification 452 to the SCE 408 . The SCE 408 then sends a message 462 to the FC 412 notifying the FC 412 that the request for the Delivery Information was created. The FC 412 then sends a message 464 notifying the SRM 414 that the request for the Delivery Information was created. The FC 412 also sends a message 466 notifying the SCP 410 that the request for the Delivery Information was created. The SCE 408 sends a message 468 to the FC 412 when the goods have been set aside for delivery. The FC 412 sends a message 470 to the SRM 414 when the goods have been set aside for delivery. The FC 412 also sends a message 472 to the SCP 410 when the goods have been set aside for delivery.

The SCE 408 sends a message 474 to the FC 412 when the goods have been delivered. The FC 412 then sends a message 476 to the SRM 414 indicating that the goods have been delivered, and sends a message 478 to the SCP 410 indicating that the goods have been delivered. The SCE 408 then sends an Inventory Change Accounting Notification 480 to Accounting 402 , and an Inventory Change Notification 482 to the SCP 410 . The FC 412 sends an Invoice Due Notification 484 to Invoicing 406 , and SCE 408 sends a Received Delivery Notification 486 to the Supplier 416 .

During the Billing/Payment transaction 426 , the Supplier 416 sends an Invoice Request 487 to Invoicing 406 . Invoicing 406 then sends a Payment Due Notification 488 to Payment 404 , a Tax Due Notification 489 to Payment 404 , an Invoice Confirmation 490 to the Supplier 416 , and an Invoice Accounting Notification 491 to Accounting 402 . Payment 404 sends a Payment Request 492 to the Bank 418 , and a Payment Requested Accounting Notification 493 to Accounting 402 . Bank 418 sends a Bank Statement Information 496 to Payment 404 . Payment 404 then sends a Payment Done Information 494 to Invoicing 406 and a Payment Done Accounting Notification 495 to Accounting 402 .

Within a business document flow, business documents having the same or similar structures are marked. For example, in the business document flow 400 depicted in FIG. 4 , Purchase Requirement Requests 434 , 436 and Purchase Requirement Confirmations 438 , 440 have the same structures. Thus, each of these business documents is marked with an “O6.” Similarly, Purchase Order Request 442 and Purchase Order Confirmation 448 have the same structures. Thus, both documents are marked with an “O1.” Each business document or message is based on a message type. The message type is identified within the rectangle within each of the business documents depicted in the business document flow. For example, Source of Supply Notification 432 is based on message type 77, as reflected by “MT 77.” A list of various message types with their corresponding codes and a description of each message type is provided below.

From the business document flow, the developers identify the business documents having identical or similar structures, and use these business documents to create the business object model (step 108 ). The business object model includes the objects contained within the business documents. These objects are reflected as packages containing related information, and are arranged in a hierarchical structure within the business object model, as discussed below.

Methods and systems consistent with the subject matter described herein then generate interfaces from the business object model (step 110 ). The heterogeneous programs use instantiations of these interfaces (called “business document objects” below) to create messages (step 112 ), which are sent to complete the business transaction (step 114 ). Business entities use these messages to exchange information with other business entities during an end-to-end business transaction. Since the business object model is shared by heterogeneous programs, the interfaces are consistent among these programs. The heterogeneous programs use these consistent interfaces to communicate in a consistent manner, thus facilitating the business transactions.

Standardized Business-to-Business (“B2B”) messages are compliant with at least one of the e-business standards (i.e., they include the business-relevant fields of the standard). The e-business standards include, for example, RosettaNet for the high-tech industry, Chemical Industry Data Exchange (“CIDX”), Petroleum Industry Data Exchange (“PIDX”) for the oil industry, UCCnet for trade, PapiNet for the paper industry, Odette for the automotive industry, HR-XML for human resources, and XML Common Business Library (“xCBL”). Thus, B2B messages enable simple integration of components in heterogeneous system landscapes. Application-to-Application (“A2A”) messages exceed the standards, and thus provide the benefit of the full functionality of application components. Although various steps of FIG. 1 were described as being performed manually, one skilled in the art will appreciate that such steps could be computer-assisted or performed entirely by a computer, including being performed by either hardware, software, or any other combination thereof.

B. Implementation Details

As discussed above, methods and systems consistent with the subject matter described herein create consistent interfaces by generating the interfaces from a business object model. Details regarding the creation of the business object model, the generation of an interface from the business object model, and the use of an interface generated from the business object model are provided below.

FIG. 5 depicts two exemplary data processing systems 500 , 550 suitable for practicing methods and systems consistent with the subject matter described herein. Data processing system 500 includes a main memory 502 , a secondary storage device 504 , a processor 506 , and an input/output (I/O) device 508 . Likewise, data processing system 550 includes a main memory 552 , a secondary storage device 554 , a processor 556 , and an input/output (I/O) device 558 . Each data processing system 500 , 550 may further comprise standard input devices, such as a keyboard, a mouse or a speech processing means (each not illustrated). The internal components of each data processing system 500 , 550 exchange information with one another via system buses 510 , 560 . The components are standard in most computer systems suitable for use with practicing methods and configuring systems consistent with the subject matter described herein. One skilled in the art will recognize that data processing systems 500 , 550 may contain additional or different components.

Memory 502 includes program 512 , which is an application program that facilitates the transfer of information between business entities. Memory 552 similarly includes program 562 , which is an application program that facilitates the transfer of information between business entities. For example, program 512 could be an accounting program that transfers information to program 562 , which could be a manufacturing program. Although depicted in two separate data processing systems 500 , 550 , one having skill in the art will appreciate that programs 512 , 562 can reside in the same data processing system, the same computer, and even in the same memory. Each program 512 , 562 may comprise or may be included in one or more code sections containing instructions for performing their respective operations. While programs 512 , 562 are described as being implemented as software, the present implementation may be implemented as a combination of hardware and software or hardware alone.

Memory 502 also includes an exchange infrastructure (“XI”) 514 , which is an infrastructure that supports the technical interaction of business processes across heterogeneous system environments. XI centralizes the communication between components within a business entity and between different business entities. If necessary, XI carries out the mapping between the messages. XI is a publicly available product sold by SAP AG, Walldorf, Germany. Similarly, memory 552 includes an XI 564 . XI 514 , 564 integrates different versions of systems implemented on different platforms (e.g., Java® and ABAP). XI 514 , 564 is based on an open architecture, and makes use of open standards, such as XML™ and Java® environments. XI 514 , 564 offers services that are useful in a heterogeneous and complex system landscape. In particular, XI 514 , 564 offers a runtime infrastructure for message exchange, configuration options for managing business processes and message flow, and options for transforming message contents between sender and receiver systems. XML is a trademark of the Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, and Keio University. Java is a registered trademark of Sun Microsystems, Inc. All names used herein may be trademarks or registered trademarks of their respective companies.

XI 514 , 564 stores data types 516 , 566 , a business object model 518 , 568 , and interfaces 520 , 570 . The details regarding the business object model are described below. Data types 516 , 566 are the building blocks for the business object model 518 , 568 . The business object model 518 , 568 is used to derive consistent interfaces 520 , 570 . XI 514 , 564 allows for the exchange of information from a first company having one computer system to a second company having a second computer system over network connection 525 by using the standardized interfaces 520 , 570 .

Although not shown in FIG. 5 , like all data processing systems, data processing systems 500 , 550 have operating systems that control their operations, including the execution of programs 512 , 562 by processors 506 , 556 . Also, although aspects of one implementation consistent with the principles of the subject matter described herein are described herein with programs 512 , 562 stored in main memories 502 , 552 , one skilled in the art will appreciate that all or part of systems and methods consistent with the subject matter described herein may be stored on or read from other computer-readable media, such as secondary storage devices 504 , 554 , like hard disks, floppy disks, and CD-ROM; a carrier wave received from a network, such as the Internet; or other forms of ROM or RAM, either currently known or later developed. Finally, although specific components of data processing system 500 , 550 have been described, one skilled in the art will appreciate that a data processing system suitable for use with the methods and systems consistent with the subject matter described herein may contain additional or different components.

Methods and systems consistent with the subject matter described herein provide and use interfaces 520 , 570 derived from the business object model 518 , 568 suitable for use with more than one business area, for example different departments within a company such as finance, or marketing. Also, they are suitable across industries and across businesses. Interfaces 520 , 570 are used during an end-to-end business transaction to transfer business process information in an application-independent manner. For example the interfaces can be used for fulfilling a sales order.

1. Message Overview

To perform an end-to-end business transaction, consistent interfaces are used to create business documents that are sent within messages between heterogeneous programs.

a) Message Categories

As depicted in FIG. 6 , the communication between a sender 602 and a recipient 604 can be broken down into basic categories that describe the type of the information exchanged and simultaneously suggest the anticipated reaction of the recipient 604 . A message category is a general business classification for the messages. Communication is sender-driven. In other words, the meaning of the message categories is established or formulated from the perspective of the sender 602 . The message categories include information 606 , notification 608 , query 610 , response 612 , request 614 , and confirmation 616 .

(1) Information

Information 606 is a message sent from a sender 602 to a recipient 604 concerning a condition or a statement of affairs. No reply to information is expected. Information 606 is sent to make business partners or business applications aware of a situation. Information 606 is not compiled to be application-specific. Examples of “information” are an announcement, advertising, a report, planning information, and a message to the business warehouse.

(2) Notification

A notification 608 is a notice or message that is geared to a service. A sender 602 sends the notification 608 to a recipient 604 . No reply is expected for a notification. For example, a billing notification relates to the preparation of an invoice while a dispatched delivery notification relates to preparation for receipt of goods.

(3) Query

A query 610 is a question from a sender 602 to a recipient 604 to which a response 612 is expected. A query 610 implies no assurance or obligation on the part of the sender 602 . Examples of a query 610 are whether space is available on a specific flight or whether a specific product is available. These queries do not express the desire for reserving the flight or purchasing the product.

(4) Response

A response 612 is a reply to a query 610 . The recipient 604 sends the response 612 to the sender 602 . A response 612 generally implies no assurance or obligation on the part of the recipient 604 . The sender 602 is not expected to reply. Instead, the process is concluded with the response 612 . Depending on the business scenario, a response 612 also may include a commitment, i.e., an assurance or obligation on the part of the recipient 604 . Examples of responses 612 are a response stating that space is available on a specific flight or that a specific product is available. With these responses, no reservation was made.

(5) Request

A request 614 is a binding requisition or requirement from a sender 602 to a recipient 604 . Depending on the business scenario, the recipient 604 can respond to a request 614 with a confirmation 616 . The request 614 is binding on the sender 602 . In making the request 614 , the sender 602 assumes, for example, an obligation to accept the services rendered in the request 614 under the reported conditions. Examples of a request 614 are a parking ticket, a purchase order, an order for delivery and a job application.

(6) Confirmation

A confirmation 616 is a binding reply that is generally made to a request 614 . The recipient 604 sends the confirmation 616 to the sender 602 . The information indicated in a confirmation 616 , such as deadlines, products, quantities and prices, can deviate from the information of the preceding request 614 . A request 614 and confirmation 616 may be used in negotiating processes. A negotiating process can consist of a series of several request 614 and confirmation 616 messages. The confirmation 616 is binding on the recipient 604 . For example, 100 units of X may be ordered in a purchase order request; however, only the delivery of 80 units is confirmed in the associated purchase order confirmation.

b) Message Choreography

A message choreography is a template that specifies the sequence of messages between business entities during a given transaction. The sequence with the messages contained in it describes in general the message “lifecycle” as it proceeds between the business entities. If messages from a choreography are used in a business transaction, they appear in the transaction in the sequence determined by the choreography. This illustrates the template character of a choreography, i.e., during an actual transaction, it is not necessary for all messages of the choreography to appear. Those messages that are contained in the transaction, however, follow the sequence within the choreography. A business transaction is thus a derivation of a message choreography. The choreography makes it possible to determine the structure of the individual message types more precisely and distinguish them from one another.

For example, the message choreography 700 for a purchase order scenario between buyer 702 and seller 704 is depicted in FIG. 7 . A Purchase Order Request Message 706 is the request from the buyer 702 to the seller 704 to deliver goods or render services. The message type 708 of the Purchase Order Request Message 706 is 0101, as defined above. The Purchase Order Change Request Message 710 requests a change of a previous purchase order request or purchase order change request message. The message type 712 of the Purchase Order Change Request Message 710 is 0102. The Purchase Order Cancellation Request Message 714 is the cancellation of the request of the buyer 702 to the seller 704 to deliver goods or render services. The message type 716 of the Purchase Order Cancellation Request Message 714 is 0103. The Purchase Order Confirmation Message 718 is a confirmation, a partial confirmation, or a change with respect to the delivery of goods or the rendering of services that were requested or cancelled. The message type 720 of the Purchase Order Confirmation Message 718 is 0104.

Illustrative message choreographies that cover a number of transactions are presented below.

(1) Master Data Management

FIG. 8 depicts the message choreography of a Master Data Management. The Master Data Management choreography involves three components: a Catalogue Provider 802 , a Catalogue Authoring Tool (CAT) 804 , and a Catalogue Search Engine (CSE) 806 . The Catalogue Provider 802 sends a CatalogueUpdateNotification message 808 to the CAT 804 . The message type 810 of the CatalogueUpdateNotification message 808 is 0080, i.e., a notice from a catalogue provider to an interested party about a new catalogue transmitted in the message or about changes to an existing catalogue transmitted in the message. The message type 810 can be divided into multiple messages. The CAT 804 then sends a CataloguePublicationRequest message 812 to the CSE 806 . The message type 814 of the CataloguePublicationRequest message 812 is 0081, i.e., a request from catalogue authoring to the Catalogue Search Engine (the publishing system) to publish a new or changed catalogue or to delete an already published catalogue (the catalogue is possibly split into several transmission packages). The message type 814 also can be divided into multiple messages.

The CSE 806 sends a CataloguePublicationTransmissionPackageNotification message 816 to the CAT 804 . The message type 818 of the CataloguePublicationTransmissionPackageNotification message 816 is 0082, i.e., the notification of the Catalogue Search Engine (the publishing system) to Catalogue Authoring about a package of a catalogue publication transmission and information about the reception of this package and the validity of its content. The message type 818 can be divided into multiple messages.

The CSE 806 sends a CataloguePublicationConfirmation message 820 to the CAT 804 . The message type 822 of the CataloguePublicationConfirmation message 820 is 0083, i.e., the confirmation of the Catalogue Search Engine (the publishing system) to the Catalogue Authoring whether the publication or deletion of a Catalogue requested by a CataloguePublicationRequest 812 was successful or not.

The CAT 804 sends a CataloguePublicationTransmissionCancellationRequest message 824 to the CSE 806 . The message type 826 of the CataloguePublicationTransmissionCancellationRequest message 824 is 0084, i.e., the request of Catalogue Authoring to Catalogue Search Engine (the publishing system) to cancel the transmission of a Catalogue and to restore an earlier published state (if such exists) of the Catalogue. Moreover, no more packages are sent for this transmission.

The CSE 806 sends a CataloguePublicationTransmissionCancellationConfirmation message 828 to the CAT 804 . The message type 830 of the CataloguePublicationTransmissionCancellationConfirmation message 828 is 0085, i.e., the confirmation of Catalogue Search Engine (the publishing system) whether the transmission of a Catalogue has been cancelled successfully and an earlier published state of this catalogue (if such exists) has been restored or not.

The CAT 804 sends a CataloguePublicationTransmissionItemLockRequest message 832 to the CSE 806 . The message type 834 of the CataloguePublicationTransmissionItemLockRequest message 832 is 0086, i.e., the request of Catalogue Authoring to lock single items of the catalogue contained in the catalogue publication transmission.

The CSE 806 sends a CataloguePublicationTransmissionItemLockConfirmation message 836 to the CAT 804 . The message type 838 of the CataloguePublicationTransmissionItemLockConfirmation message 836 is 0087, i.e., the confirmation of Catalogue Search Engine (the publishing system) to Catalogue Authoring whether single items of the catalogue contained in the catalogue publication transmission could be locked or not. If an item of the catalogue is locked and the catalogue is not yet published, the items must not be published. If the catalogue is already published, the publication of these items must be revoked.

(2) Purchasing and Sales

(a) Source of Supply, Purchase Requirement, and Purchase Order

FIG. 9 depicts the message choreography of a Source of Supply, Purchase Requirement, and Purchase Order. The Source of Supply, Purchase Requirement, and Purchase Order choreography involves three components: Supply Chain Planning (SCP) 902 , Purchasing (SRM) 904 , and a Supplier 906 .

The SRM 904 sends a SourceOfSupplyNotification message 908 to the SCP 902 . The message type 910 of the SourceOfSupplyNotification message 908 is 0077, i.e., a notice to Supply Chain Planning about available sources of supply.

The SCP 902 sends a PurchaseRequirementRequest message 912 to the SRM 904 . The message type 914 of the PurchaseRequirementRequest message 912 is 0130, i.e., a request from a requestor to a purchaser to (externally) procure products (materials, services) (external procurement).

The SRM 904 sends a PurchaseOrderRequest message 916 to the Supplier 906 . The message type 918 of the PurchaseOrderRequest message 916 is 0101, i.e., a request from a purchaser to a seller to deliver goods or provide services.

The SRM 904 sends a PurchaseOrderChangeRequest message 920 to the Supplier 906 . The message type 922 of the PurchaseOrderChangeRequest message 920 is 0102, i.e., a change to a purchaser's request to the seller to deliver goods or provide services.

The SRM 904 sends a PurchaseOrderCancellationRequest message 924 to the Supplier 906 . The message type 926 of the PurchaseOrderCancellationRequest message 924 is 0103, i.e., the cancellation of a purchaser's request to the seller to deliver goods or provide services.

The Supplier 906 sends a PurchaseOrderConfirmation message 928 to the SRM 904 . The message type 930 of the PurchaseOrderConfirmation message 928 is 0104, i.e., a confirmation, partial confirmation, or change from a seller to the purchaser, regarding the requested delivery of goods or provision of services.

The SRM 904 sends a PurchaseRequirementConfirmation message 932 to the SCP 902 . The message type 934 of the PurchaseRequirementConfirmation message 932 is 0131, i.e., a notice from the purchaser to the requestor about the degree of fulfillment of a requirement.

(b) Product Demand, Product Forecast and Product Activity

FIG. 10 depicts the message choreography of a Product Demand, Product Forecast and Product Activity. The Product Demand, Product Forecast and Product Activity choreography involves two components: a Buyer (ERP) 1002 and a Vendor (SCM) 1004 .

The Buyer 1002 sends a ProductDemandInfluencingEventNotification message 1006 to the Vendor 1004 . The message type 1008 of the ProductDemandInfluencingEventNotification message 1006 is 0140, i.e., a notification about an event which influences the supply or demand of products.

The Buyer 1002 sends a ProductForecastNotification message 1010 to the Vendor 1004 . The message type 1012 of the ProductForecastNotification message 1010 is 0141, i.e., a notification about future product demands (forecasts).

The Buyer 1002 sends a ProductActivityNotification message 1014 to the Vendor 1004 . The message type 1016 of the ProductActivityNotification message 1014 is 0145, i.e., a message which communicates product-related activities of a buyer to a vendor. Based on this, the vendor can perform supply planning for the buyer.

The Vendor 1004 sends a ProductForecastRevisionNotification message 1018 to the Buyer 1002 . The message type 1020 of the ProductForecastRevisionNotification message 1018 is 0142, i.e., a notification about the revision of future product demands (forecasts).

The Buyer 1002 sends the ProductForecastRevisionNotification message 1022 to the Vendor 1004 . The message type 1024 of the ProductForecastRevisionNotification message 1022 is 0142.

(c) RFQ and Quote

FIG. 11 depicts the message choreography of a RFQ and Quote. The RFQ and Quote choreography involves two components: Purchasing (SRM) 1102 and a Supplier 1104 .

The SRM 1102 sends a RFQRequest message 1106 to the Supplier 1104 . The message type 1108 of the RFQRequest message 1106 is 0151, i.e., the request from a purchaser to a bidder to participate in a request for quotation for a product.

The Supplier 1104 sends a RFQAcceptanceConfirmation message 1110 to the SRM 1102 . The message type of the RFQAcceptanceConfirmation message 1110 can be any conventional RFQ Acceptance Confirmation 1112 .

The SRM 1102 sends a RFQChangeRequest message 1114 to the Supplier 1104 . The message type 1116 of the RFQChangeRequest message 1114 is 0152, i.e., a change to the purchaser's request for a bidder to participate in the request for quotation for a product.

The SRM 1102 sends a RFQCancellationRequest message 1118 to the Supplier 1104 . The message type 1120 of the RFQCancellationRequest message 1118 is 0153, i.e., a cancellation by the purchaser of a request for quotation for a product.

The Supplier 1104 sends a QuoteNotification message 1122 to the SRM 1102 . The message type 1124 of the QuoteNotification message 1122 is 0155, i.e., the quote of a bidder communicated to a purchaser concerning the request for quotation for a product by the purchaser.

The SRM 1102 sends a RFQResultNotification message 1126 to the Supplier 1104 . The message type 1128 of the RFQResultNotification message 1126 is 0154, i.e., a notification by a purchaser to a bidder about the type and extent of the acceptance of a quote or about the rejection of the quote.

The Supplier 1104 sends a RFQResultAcceptanceConfirmation message 1130 to the SRM 1102 . The message type of the RFQResultAcceptanceConfirmation message 1130 can be any conventional RFQ Result Acceptance Confirmation 1132 .

(d) Purchasing

FIG. 12 depicts the message choreography of Purchasing. The Purchasing choreography involves five components: Sales (CRM) 1202 , Purchasing (SRM) 1204 , Fulfillment Coordination (FC) 1206 , Supply Chain Planning (SCP) 1208 , and Supply Chain Execution (SCE) 1210 . Line 1212 denotes a company border. Thus, one company includes Sales 1202 , while another company includes SRM 1204 , FC 1206 , SCP 1208 , and SCE 1210 .

The SRM 1204 sends a PurchaseOrderRequest message 1214 to the CRM 1202 . The message type 1216 of the PurchaseOrderRequest message 1214 is 0101, i.e., a request from a purchaser to a seller to deliver goods or provide services.

The SRM 1204 sends a PurchaseOrderInformation message 1218 to the FC 1206 . The message type 1220 of the PurchaseOrderInformation message 1218 is 0120, i.e., information from a purchasing system for interested recipients about the current state of a purchase order when creating or changing a purchase order, confirming a purchase order or canceling a purchase order.

The FC 1206 sends the PurchaseOrderInformation message 1222 to the SCP 1208 . The message type 1224 of the PurchaseOrderInformation message 1222 is message type 0120.

The CRM 1202 sends a PurchaseOrderConfirmation message 1226 to the SRM 1204 . The message type 1228 of the PurchaseOrderConfirmation message 1226 is 0104, i.e., a confirmation, partial confirmation, or change from a seller to the purchaser, regarding the requested delivery of goods or provision of services.

The SRM 1204 sends a PurchaseOrderInformation message 1230 to the FC 1206 . The message type 1232 of the PurchaseOrderInformation message 1230 is 0120, described above.

The FC 1206 sends the PurchaseOrderInformation message 1234 to the SCP 1208 . The message type 1236 of the PurchaseOrderInformation message 1234 is 0120.

The FC 1206 sends a DeliveryExecutionRequest message 1238 to the SCE 1210 , as depicted by line 1242 . Alternatively, the SRM 1204 may send the DeliveryExecutionRequest message 1238 to the SCE 1210 , as depicted by broken line 1240 . The message type 1244 of the DeliveryExecutionRequest message 1238 is 0200, i.e., a request to a warehouse or supply chain execution to prepare and execute the outbound delivery of goods or the acceptance of an expected or announced inbound delivery.

The SCE 1210 sends a DeliveryInformation message 1246 to the FC 1206 . The message type 1248 of the DeliveryInformation message 1246 is 0201, i.e., a message about the creation, change, and execution status of a delivery.

The FC 1206 sends a DeliveryInformation message 1250 to the SCP 1208 . The message type 1252 of the DeliveryInformation message is 0201.

The FC 1206 sends a DeliveryInformation message 1254 to the SRM 1204 . The message type 1256 of the DeliveryInformation message 1254 is 0201.

(e) Sales

FIG. 13 depicts the message choreography of Sales. The Sales choreography involves five components: Purchasing (SRM) 1302 , Sales (CRM) 1304 , Fulfillment Coordination (FC) 1306 , Supply Chain Planning (SCP) 1308 , and Supply Chain Execution (SCE) 1310 . Line 1312 denotes a company border. Thus, one company includes SRM 1302 , while another company includes CRM 1304 , FC 1306 , SCP 1308 , and SCE 1310 .

The SRM 1302 sends a PurchaseOrderRequest message 1314 to the CRM 1304 . The message type 1316 of the PurchaseOrderRequest message 1314 is 0101, i.e., a request from a purchaser to a seller to deliver goods or provide services.

The CRM 1304 sends a SalesOrderFulfillmentRequest message 1318 to the FC 1306 . The message type 1320 of the SalesOrderFulfillmentRequest message 1318 is 0160, i.e., a request (or change or cancellation of such a request) from a selling component to a procuring component, to fulfill the logistical requirements (for example, available-to-promise check, scheduling, requirements planning, procurement, and delivery) of a sales order.

The FC 1306 sends the SalesOrderFulfillmentRequest message 1322 to the SCP 1308 . The message type 1324 of the SalesOrderFulfillmentRequest message 1322 is 0160.

The SCP 1308 sends a SalesOrderFulfillmentConfirmation message 1326 to the FC 1306 . The message type 1328 of the SalesOrderFulfillmentConfirmation message 1326 is 0161, i.e., a confirmation, partial confirmation or change from the procuring component to the selling component, regarding a sales order with respect to which procurement has been requested.

The FC 1306 sends the SalesOrderFulfillmentConfirmation message 1330 to the CRM 1304 . The message type 1332 of the SalesOrderFulfillmentConfirmation message 1330 is 0161.

The CRM 1304 sends a PurchaseOrderConfirmation message 1334 to the SRM 1302 . The message type 1336 of the PurchaseOrderConfirmation message 1334 is 0104, i.e., a confirmation, partial confirmation, or change from a seller to the purchaser, regarding the requested delivery of goods or provision of services.

The FC 1306 sends a DeliveryExecutionRequest message 1338 to the SCE 1310 . The message type 1340 of the DeliveryExecutionRequest message 1338 is 0200, i.e., a request to a warehouse or supply chain execution to prepare and execute the outbound delivery of goods or the acceptance of an expected or announced inbound delivery.

The SCE 1310 sends a DeliveryInformation message 1344 to the FC 1306 . The message type 1346 of the DeliveryInformation message 1344 is 0201, i.e., a message about the creation, change, and execution status of a delivery.

The FC 1306 sends the DeliveryInformation message 1348 to the SCP 1308 . The message type 1350 of the DeliveryInformation message 1348 is 0201, i.e., a message about the creation, change, and execution status of a delivery.

The FC 1306 also sends the DeliveryInformation message 1352 to the CRM 1304 . The message type 1354 of the DeliveryInformation message 1352 is 0201.

(f) Vendor Managed Inventory/Responsive Replenishment

FIG. 14 depicts the message choreography of a Vendor Managed Inventory/Responsive Replenishment. The Vendor Managed Inventory/Responsive Replenishment choreography involves three components: a Buyer 1402 , Supply Chain Planning 1404 , and Supply Chain Execution 1406 . Line 1408 denotes a company border. Thus, one company includes Buyer 1402 , while another company includes Supply Chain Planning 1404 and Supply Chain Execution 1406 .

The Buyer 1402 sends an OrderIDAssignmentNotification message 1410 to Supply Chain Planning 1404 . The message type 1412 of the OrderIDAssignmentNotification message 1410 is 0185, i.e., a message that allows a buyer to assign a vendor order numbers for identifying “purchase orders generated by the vendor.”

Supply Chain Planning 1404 sends a ReplenishmentOrderNotification message 1414 to Supply Chain Execution 1406 . The message type 1416 of the ReplenishmentOrderNotification message 1414 is 0216, i.e., a message that is used by Logistics Planning (SCP, vendor) to transfer a replenishment order planned for a customer/buyer to Logistics Execution (SCE, vendor) in order to trigger further processing for the order and prepare the outbound delivery.

Supply Chain Execution 1406 sends a ReplenishmentOrderConfirmation message 1418 to Supply Chain Planning 1404 . The message type 1420 of the ReplenishmentOrderConfirmation message 1418 is 0217, i.e., a message that is used by Logistics Execution (SCE, vendor) to confirm to Logistics Planning (SCP, vendor) that a replenishment order that is planned for a customer/buyer can be fulfilled.

Supply Chain Planning 1404 sends a VendorGeneratedOrderNotification message 1422 to the Buyer 1402 . The message type 1424 of the VendorGeneratedOrderNotification message 1422 is 0213, i.e., a message that is used by a vendor/seller to transfer the replenishment order that he has initiated and planned to a customer/buyer so that the latter can create a purchase order. The notification sent by the vendor/seller to the customer/buyer regarding the planned replenishment order can be regarded as a “purchase order generated by the seller.”

The Buyer 1402 sends a VendorGeneratedOrderConfirmation message 1426 to Supply Chain Planning 1404 . The message type 1428 of the VendorGeneratedOrderConfirmation message 1426 is 0214, i.e., VendorGeneratedOrderConfirmation is the confirmation from a customer/buyer that a purchase order has been created for the replenishment order initiated and planned by his vendor/seller. This confirmation from the customer/buyer for a “purchase order generated by the seller” can be regarded as a “purchase order” in the traditional sense, which, in turn, triggers the corresponding fulfillment process at the vendor/seller.

(3) Delivery and Goods Movement

(a) Advanced Shipment Notification and Proof of Delivery

FIG. 15 depicts the message choreography of an Advanced Shipment Notification and Proof of Delivery. The Advanced Shipment Notification and Proof of Delivery choreography involves two components: a Vendor 1502 and a Product Recipient 1504 .

The Vendor 1502 sends a DespatchedDeliveryNotification message 1506 to the Product Recipient 1504 . The message type 1508 of the DespatchedDeliveryNotification message 1506 is 0202, i.e., a notification communicated to a product recipient about the planned arrival, pickup, or issue date of a ready-to-send delivery, including details about the content of the delivery.

The Product Recipient 1504 sends a ReceivedDeliveryNotification message 1510 to the Vendor 1502 . The message type 1512 of the ReceivedDeliveryNotification message 1510 is 0203, i.e., a notification communicated to a vendor about the arrival of the delivery sent by him to the product recipient, including details about the content of the delivery.

(b) Service Acknowledgement

FIG. 16 depicts the message choreography of a Service Acknowledgement. The Service Acknowledgement choreography involves two components: Purchasing (SRM) 1602 and a Supplier 1604 .

The Supplier 1604 sends a ServiceAcknowledgementRequest message 1606 to the SRM 1602 . The message type 1608 of the ServiceAcknowledgementRequest message 1606 is 0240, i.e., a request by a seller to a purchaser to confirm the services recorded.

The SRM 1602 sends a ServiceAcknowledgementConfirmation message 1610 to the Supplier 1604 . The message type 1612 of the ServiceAcknowledgementConfirmation message 1610 is 0241, i.e., a confirmation (or rejection) of the services recorded.

(c) Inventory Change

FIG. 17 depicts the message choreography of an Inventory Change. The Inventory Change choreography involves three components: Inventory Management (SCE) 1702 , Logistic Planning (SCP) 1704 and Financial Accounting 1706 .

The SCE 1702 sends an InventoryChangeNotification message 1708 to the SCP 1704 . The message type 1710 of the InventoryChangeNotification message 1708 is 0250, i.e., a summery of detailed information about inventory changes in inventory management, which is required for logistics planning.

The SCE 1702 sends an InventoryChangeAccountingNotification message 1712 to Financial Accounting 1706 . The message type 1714 of the InventoryChangeAccountingNotification message 1712 is 0251, i.e., a summary of aggregated information about inventory changes in inventory management, which is required for financials.

The SCE 1702 sends an InventoryChangeAccountingCancellationRequest message 1716 to Financial Accounting 1706 . The message type 1718 of the InventoryChangeAccountingCancellationRequest message 1716 is 0252, i.e., a request for the full cancellation of posting information previously sent to financials with respect to a goods movement.

(4) Invoice and Payment and Financials

(a) Billing Due

FIG. 18 depicts the message choreography of Billing Due. The Billing Due choreography involves three components: Sales (CRM) 1802 , Supply Chain Execution (SCE) 1804 , and Billing 1806 .

The CRM 1802 sends a BillingDueNotification message 1808 to Billing 1806 . The message type 1810 of the BillingDueNotification message 1808 is 0290, i.e., a notification about billing-relevant data communicated to an application in which the subsequent operative processing of billing takes place.

The SCE 1804 sends a BillingDueNotification message 1816 to Billing 1806 . The message type 1818 of the BillingDueNotification message 1816 is 0290, i.e., a notification about billing-relevant data communicated to an application in which the subsequent operative processing of billing takes place.

(b) Invoicing Due

FIG. 19 depicts the message choreography of Invoicing Due. The Invoicing Due choreography involves three components: Purchasing (SRM) 1902 , Supply Chain Execution (SCE) 1904 , and Invoicing 1906 .

The SRM 1902 sends an InvoicingDueNotification message 1908 to Invoicing 1906 . The message type 1910 of the InvoicingDueNotification message 1908 is 0291, i.e., a notification about invoicing-relevant data communicated to an application in which the operative verification and creation of invoices takes place, and/or in which “self billing” invoices (evaluated receipt settlement) are created.

The SCE 1904 sends an InvoicingDueNotification message 1916 to Invoicing 1906 . The message type 1918 of the InvoicingDueNotification message 1916 is 0291, i.e., a notification about invoicing-relevant data communicated to an application in which the operative verification and creation of invoices takes place, and/or in which “self billing” invoices (evaluated receipt settlement) are created.

(c) Invoice

FIG. 20 depicts the message choreography of an Invoice. The Invoice choreography involves four components: Purchasing (SRM) 2002 , Invoicing 2004 , Billing 2006 , and Sales (CRM) 2008 . Line 2010 denotes a company border. Thus, one company includes SRM 2002 and Invoicing 2004 , while another company includes Billing 2006 and CRM 2008 .

Billing 2006 sends an InvoiceRequest message 2012 to Invoicing 2004 . The message type 2014 of the InvoiceRequest message 2012 is 0401, i.e., a legally binding notice about accounts receivable or accounts payable for delivered goods or provided services—typically a request that payment be made for these goods or services.

Invoicing 2004 sends an InvoiceReceivedInformation message 2016 to the SRM 2002 . The message type 2018 of the InvoiceReceivedInformation message 2016 can be a conventional Invoice Received Information.

Billing 2006 sends an InvoiceIssuedInformation message 2020 to Sales 2008 . The message type 2022 of the InvoiceIssuedInformation message 2020 is 0410, i.e., information about provided services, delivered products, or credit or debit memo request items that have been billed, the items of an invoice that have been used for this, and the extent to which they have been billed.

Invoicing 2004 sends an InvoiceConfirmation message 2024 to Billing 2006 . The message type 2026 of the InvoiceConfirmation message 2024 is 0402, i.e., the repose of a recipient of an invoice to the bill-from-party by which the invoice as a whole is confirmed, rejected, or classified as ‘not yet decided.’

(d) Invoice Accounting and Payment Due

FIG. 21 depicts the message choreography of Invoice Accounting and Payment Due. The Invoice Accounting and Payment Due choreography involves three components: Invoicing/Billing 2102 , Accounting 2104 and Payment 2106 .

Invoicing/Billing 2102 sends an InvoiceAccountingNotification message 2108 to Accounting 2104 . The message type 2110 of the InvoiceAccountingNotification message 2108 is 0411, i.e., a notification to financials about information on incoming or outgoing invoices from invoice verification or billing.

Invoicing/Billing 2102 sends an InvoiceAccountingCancellationRequest message 2112 to Accounting 2104 . The message type 2114 of the InvoiceAccountingCancellationRequest message 2112 is 0412, i.e., a request for the full cancellation of posting information previously sent to financials, regarding an incoming or outgoing invoice or credit memo.

Invoicing/Billing 2102 sends a PaymentDueNotification message 2116 to Payment 2106 . The message type 2118 of the PaymentDueNotification message 2116 is 0430, i.e., the PaymentDueNotification notifies an application (Payment), in which subsequent operative processing of payments take place, about due dates (accounts receivable and accounts payable) of business partners.

Invoicing/Billing 2102 sends a PaymentDueCancellationRequest message 2120 to Payment 2106 . The message type 2122 of the PaymentDueCancellationRequest message 2120 can be any conventional Payment Due Cancellation Request.

(e) Tax Due

FIG. 22 depicts the message choreography of Tax Due. The Tax Due choreography involves two components: Tax Calculation 2202 and Tax Register 2204 .

Tax Calculation 2202 sends a TaxDueNotification message 2206 to the Tax Register 2204 . The message type 2208 of the TaxDueNotification message 2206 is 0420, i.e., the TaxDueNotification communicates data from tax determination and calculation relevant for tax reports and tax payments to the tax register of a company.

Tax Calculation 2202 sends a TaxDueCancellationRequest message 2210 to the Tax Register 2204 . The message type 2212 of the TaxDueCancellationRequest message 2210 can be any conventional Tax Due Cancellation Request.

(f) Credit Worthiness, Credit Agency Report, Credit Payment, and Credit Commitment

FIG. 23 depicts the message choreography of Credit Worthiness, Credit Agency Report, Credit Payment, and Credit Commitment. The Credit Worthiness, Credit Agency Report, Credit Payment, and Credit Commitment choreography involves five components: Payment or Accounting 2302 , Sales or Financials 2304 , a Billing System (e.g., Telco) 2306 , Credit Management 2308 , and Credit Agency 2310 .

Sales or Financials 2304 sends a CreditCommitmentRecordNotification message 2312 to Credit Management 2308 . The message type 2314 of the CreditCommitmentRecordNotification message 2312 is 0457, i.e., a notice to credit management about existing payment obligations of business partners.

Payment or Accounting 2302 sends a CreditPaymentRecordNotification message 2316 to Credit Management 2308 . The message type 2318 of the CreditPaymentRecordNotification message 2316 is 0460, i.e., a notice to credit management about the payment behavior of business partners.

Sales or Financials 2304 sends a CreditWorthinessQuery message 2320 to Credit Management 2308 . The message type 2322 of the CreditWorthinessQuery message 2320 is 0452, i.e., an inquiry to credit management concerning the credit worthiness of a business partner.

Credit Management 2308 sends a CreditAgencyReportQuery message 2324 to Credit Agency 2310 . The message type 2326 of the CreditAgencyReportQuery message 2324 is 0450, i.e., an inquiry to a credit agency concerning the credit report for a business partner.

Credit Agency 2310 sends a CreditAgencyReportResponse message 2328 to Credit Management 2308 . The message type 2330 of the CreditAgencyReportResponse message 2328 is 0451, i.e., a response from a credit agency concerning the inquiry about the credit report for a business partner.

Credit Management 2308 sends a CreditCommitmentQuery message 2332 to the Billing System 2306 . The message type 2334 of the CreditCommitmentQuery message 2332 is 0455, i.e., an inquiry from credit management concerning existing payment obligations of a business partner.

The Billing System 2306 sends a CreditCommitmentResponse message 2336 to Credit Management 2308 . The message type 2338 of the CreditCommitmentResponse message 2336 is 0456, i.e., a response concerning an inquiry from credit management about existing payment obligations of a business partner.

Credit Management 2308 sends a CreditWorthinessResponse message 2340 to Sales or Financials 2304 . The message type 2342 of the CreditWorthinessResponse message 2340 is 0453, i.e., a response from credit management concerning the inquiry about the credit worthiness of a business partner.

Credit Management 2308 sends a CreditWorthinessChangeInformation message 2344 to Sales or Financials 2304 . The message type 2346 of the CreditWorthinessChangeInformation message 2344 is 0454, i.e., information about changes of the credit worthiness of a business partner.

Sales or Financials 2304 sends a CreditWorthinessCriticalPartiesQuery message 2348 to Credit Management 2308 . The message type 2350 of the CreditWorthinessCriticalPartiesQuery message 2348 is 0458, i.e., an inquiry to credit management about business partners, for which the credit worthiness has been rated as critical.

Credit Management 2308 sends a CreditWorthinessCriticalPartiesResponse message 2352 to Sales or Financials 2304 . The message type 2354 of the CreditWorthinessCriticalPartiesResponse message 2352 is 0459, i.e., a response from credit management concerning an inquiry about business partners, for which the credit worthiness has been rated as critical.

(5) Human Capital Management

(a) Personnel Time Sheet

FIG. 24 depicts the message choreography of a Personnel Time Sheet. The Personnel Time Sheet choreography involves two components: Personnel Time Recording 2402 and Personnel Time Management 2404 .

Personnel Time Recording 2402 sends a PersonalTimeSheetInformation message 2406 to Personnel Time Management 2404 . The message type 2408 of the PersonalTimeSheetInformation message 2406 is 0601, i.e., the PersonnelTimeSheetInformation communicates recorded personnel times and personnel time events from an upstream personnel time recording system to personnel time management.

2. Components of the Business Object Model

The overall structure of the business object model ensures the consistency of the interfaces that are derived from the business object model. The derivation ensures that the same business-related subject matter or concept is represented and structured in the same way in all interfaces.

The business object model defines the business-related concepts at a central location for a number of business transactions. In other words, it reflects the decisions made about modeling the business entities of the real world acting in business transactions across industries and business areas. The business object model is defined by the business objects and their relationship to each other (the overall net structure).

A business object is a capsule with an internal hierarchical structure, behavior offered by its operations, and integrity constraints. Business objects are semantically disjoint, i.e., the same business information is represented once. In the business object model, the business objects are arranged in an ordering framework. From left to right, they are arranged according to their existence dependency to each other. For example, the customizing elements may be arranged on the left side of the business object model, the strategic elements may be arranged in the center of the business object model, and the operative elements may be arranged on the right side of the business object model. Similarly, the business objects are arranged from the top to the bottom based on defined order of the business areas, e.g., finance could be arranged at the top of the business object model with CRM below finance and SRM below CRM.

To ensure the consistency of interfaces, the business object model may be built using standardized data types as well as packages to group related elements together, and package templates and entity templates to specify the arrangement of packages and entities within the structure.

“The following sections © SAP AG.”

a) Data Types

Data types are used to type object entities and interfaces with a structure. This typing can include business semantic. For example, the data type BusinessTransactionDocumentID is a unique identifier for a document in a business transaction. Also, as an example, Data type BusinessTransactionDocumentParty contains the information that is exchanged in business documents about a party involved in a business transaction, and includes the party's identity, the party's address, the party's contact person and the contact person's address. BusinessTransactionDocumentParty also includes the role of the party, e.g., a buyer, seller, product recipient, or vendor.

The data types are based on Core Component Types (“CCTs”), which themselves are based on the World Wide Web Consortium (“W3C”) data types. “Global” data types represent a business situation that is described by a fixed structure. Global data types include both context-neutral generic data types (“GDTs”) and context-based context data types (“CDTs”). GDTs contain business semantics, but are application-neutral, i.e., without context. CDTs, on the other hand, are based on GDTs and form either a use-specific view of the GDTs, or a context-specific assembly of GDTs or CDTs. A message is constructed with reference to a use, and is thus a use-specific assembly of GDTs and CDTs. The data types can be aggregated to complex data types.

To achieve a harmonization across business objects and interfaces, the same subject matter is always typed with the same data type. For example, the data type “GeoCoordinates” is built using the data type “Measure” so that the measures in a GeoCoordinate (i.e., the latitude measure and the longitude measure) are represented the same as other “Measures” that appear in the business object model.

(1) CoreComponentTypes (CCTs)

(a) Amount

A CCT Amount 2500 is used to represent amounts, costs, remunerations, and fees. A CCT Amount 2500 includes an amount with the corresponding currency unit. An example of the CCT Amount 2500 is: <Amount currencyCode=“EUR”>777.95</Amount>, which represents the amount 777.95 Euros.

The structure of CCT Amount 2500 is depicted in FIG. 25 . CCT Amount 2500 includes the attribute currencyCode 2502 . For CCT Amount 2500 , the Category is complexType 2504 , the Property is Amount 2510 , the Representation/Association is Content 2514 , the Type is xsd 2518 , the Type Name is decimal 2522 , and the Length can have a maximum 22 predecimal places and 6 decimal places 2626 .

For the currencyCode 2502 , the Category is Attribute 2506 , the Object Class is Amount 2508 , the Property is Currency 2512 , the Representation/Association is Code 2516 , the Type is xsd 2520 , the Type Name is token 2524 , and the Length is three 2528 . The Cardinality between CCT Amount 2500 and currencyCode 2502 is one 2530 . CurrencyCode 2502 is mandatory 2532 . CurrencyCode 2502 requires the currency to always be specified.

(b) BinaryObject

A CCT BinaryObject 2600 includes a finite data stream of any number of characters in binary notation (octets). CCT BinaryObject 2600 can be delivered to a partner using two methods: (1) an implicit representation as an element value; or (2) as a MIME attachment within a message, with a unique URI-based reference to the corresponding attachment. An example for CCT BinaryObject 2600 is a representation of CCT BinaryObject 2600 as an element value based on base64 encoding is:

An example of a reference to CCT BinaryObject 2600 that is delivered as a MIME attachment within a message is:

<BinaryObject uri=“cid:a34ccrt@15.4.9.92/s445”/>.

The element value of CCT BinaryObject 2600 is based on the XML-scheme-specific built-in data type xsd: base64binary. This enables any binary data to be represented using base64 encoding. This is done using the base64 Content-Transfer-Encoding procedure.

The structure of CCT BinaryObject 2600 is depicted in FIG. 26 . CCT BinaryObject 2600 includes attributes mimeCode 2602 , charSetCode 2604 , format 2606 , filename 2608 , and URI 2610 . For CCT BinaryObject 2600 , the Category is complexType 2612 , the Property is Binary-Object 2634 , the Representation/Association is Content 2646 , the Type is xsd 2658 , and the Type Name is base64binary 2670 .

MimeCode 2602 identifies the medium type (image, audio, video, application) of the binary content according to the MIME type definition in IETF RFC 2046 and the corresponding MIME type recommendations. For mimeCode 2602 , the Category is Attribute 2614 , the Object Class is Binary-Object 2625 , the Property is mime 2636 , the Representation/Association is Code 2648 , the Type is xsd 2660 , the Type Name is token 2672 , and the Cardinality may be 0 or 1 2680 . Mimecode 2602 is necessary when CCT BinaryObject 2600 is represented as an element value (see 2688 ).

CharSetCode 2604 identifies the specific character set of text data. For CharSetCode 2604 , the Category is Attribute 2616 , the Object Class is Binary-Object 2626 , the Property is Character Set 2638 , the Representation/Association is Code 2650 , the Type is xsd 2662 , the Type Name is token 2674 , and the Cardinality may be 0 or 1 2680 . CharSetCode 2604 is necessary when CCT BinaryObject 2600 is represented as an element value and comprises text data (see 2690 ).

Format 2606 describes the format of the binary content if the format is not clear or unique from the “mimeCode.” For Format 2606 , the Category is Attribute 2618 , the Object Class is Binary-Object 2628 , the Property is Format 2640 , the Representation/Association is Text 2652 , the Type is xsd 2664 , the Type Name is token 2675 , and the Cardinality may be 0 or 1 2684 . Format 2606 may be optional (see 2692 ).

Filename 2608 contains the corresponding name or file name of the binary content according to the MIME protocol. For filename 2608 , the Category is Attribute 2620 , the Object Class is Binary-Object 2630 , the Property is Filename 2642 , the Representation/Association is Text 2654 , the Type is xsd 2666 , the Type Name is string 2676 , and the Cardinality is may be 0 or 1 2686 . Filename 2608 is not defined in ebXML CCTS 1.8, but it is to be submitted. Filename 2608 also conforms with IETF RFC 1341 (see 2694 ).

URI 2610 references the physical location of CCT BinaryObject 2600 if this is represented as a MIME attachment in a SOAP message or in an ebXML-MSG message. The syntax of the URI is defined in the IETF RFC 2396 recommendation and is as follows: <scheme>.<scheme-specific part>. For URI 2610 , the Category is Attribute 2622 , the Object Class is Binary-Object 2632 , the Property is Uniform Resource 2644 , the Representation/Association is Identifier 2656 , the Type is xsd 2668 , and the Type Name is any URI 2678 . URI 2610 is necessary when referencing a remote CCT BinaryObject 2600 (see 2696 ).

As enumerated by the Internet Assigned Numbers Authority (IANA), November 2002 , various MIME types are available for mimeCode 2602 . For example one MIME type may be iso-8859-n, where n is a placeholder for the number of the relevant ISO character set from 1 to 9. Another example MIME type is us-ascii.

Various URI schemes are also available for the scheme-specific part in the URI, as enumerated by the IANA. For example, one available scheme is cid which is a content identifier. Another available scheme is uuid, which is a Universal Unique Identifier Scheme.

CCT BinaryObject 2600 can be used for binary data and all types of binary files. This includes graphics (such as diagrams, mathematic curves, and the like), pictures (such as photos, passport photos, and the like), sound recordings, video recordings, and documents in binary notation (such as PDF, DOC, and XLS files). The primary Representation/Association for CCT BinaryObject 2600 is BinaryObject. Additional secondary Representation/Associations may be Graphic, Picture, Sound and Video.

The useful data in Binary Object 2600 may be delivered either as an element value using base64 octet representation or as a MIME attachment. In certain variations, CCT BinaryObject 2600 is not used to reference a file that is located on a Web server. The global data type “WebAddress” is available for this purpose. If CCT BinaryObject 2600 is in a MIME attachment, the URI 2610 may reference the corresponding “Content ID” of the respective MIME attachment. For this purpose, URI scheme cid may be used, which identifies a freely defined “Content ID”. URI scheme uuid may also be used for this purpose. Uuid identifies a unique identification in accordance with UUID guidelines.

It is not necessary to specify the “typeCode” and “fileName” attributes in a MIME attachment, since this information is contained in the MIME attachment itself.

(c) Code

A CCT Code 2700 is a character string of letters, numbers, special characters (except escape sequences), and symbols. It represents a definitive value, a method, or a property description in an abbreviated or language-independent form. An example for the CCT Code 2700 is: a Standard Code/Standard Agency is <SecurityErrorCode listID=“DE 0571” listAgencyID=“6”>4</SecurityErrorCode>.

An example of a Proprietary Code/Standard Agency is <SecurityErrorCode listID=“SEC” listAgencyID=“065055766” listAgencySchemeID=“DUNS” listAgencySchemeAgencyID=“016”>ANS</SecurityErrorCode>.

An example of a Proprietary Code/Proprietary Agency is <SecurityErrorCode listID=“SEC” listAgencyID=“4711” listAgencySchemeID=“PartyA” listAgencySchemeAgencyID=“ZZZ”>ER05</SecurityErrorCode>

The structure of CCT Code 2700 is depicted in FIG. 27 . CCT Code 2700 includes Attributes listID 2702 , listVersionID 2704 , listAgencyID 2706 , listAgency-SchemeID 2708 , and listAgency-SchemeAgencyID 2710 . For CCT Code 2700 , the Category is complexType 2712 , the Property is Code 2734 , the Representation/Association is Content 2746 , the Type is xsd 2758 , and the Type Name is token 2770 .

ListID 2702 identifies a list of the codes that belong together. ListID 2702 is unique within the agency that manages this code list. For listID 2702 , the Category is Attribute 2714 , the Object Class is CodeList 2724 , the Property is Identification 2736 , the Representation/Association is Identifier 2748 , the Type is xsd 2760 , the Type Name is token 2772 , and the Cardinality is may be 0 or 1 2782 . The attribute ListID may be optional (see 2792 ).

ListVersionID 2704 identifies the version of a code list. For listVersionID 2704 , the Category is Attribute 2716 , the Object Class is CodeList 2726 , the Property is Version 2738 , the Representation/Association is Identifier 2750 , the Type is xsd 2762 , the Type Name is token 2774 , and the Cardinality may be 0 or 1 2784 . The attribute ListVersionID may be optional (see 2792 ).

ListAgencyID 2706 identifies the agency that manages the code list. The agencies from DE 3055 are used as the default (without roles). For listAgencyID 2706 , the Category is Attribute 2718 , the Object Class is CodeListAgency 2728 , the Property is Identification 2740 , the Representation/Association is Identifier 2752 , the Type is xsd 2764 , the Type Name is token 2776 , and the Cardinality is may be 0 or 1 2786 . The attribute ListAgencyID may be optional (see 2796 ).

ListAgencySchemeID 2708 identifies the identification scheme that represents the context that is used to identify the agency. For listAgencySchemeID 2708 , the Category is Attribute 2720 , the Object Class is CodeListAgency 2730 , the Property is Scheme 2742 , the Representation/Association is Identifier 2754 , the Type is xsd 2766 , the Type Name is token 2778 , and the Cardinality is may be zero or one 2788 . The attribute ListVersionAgencyID may be optional (see 2797 ).

ListAgencySchemeAgencyID identifies the agency that manages the listAgencySchemeID. This attribute can contain values from DE 3055 (excluding roles). For listAgencySchemeAgencyID 2710 , the Category is Attribute 2722 , the Object Class is CodeListAgency 2732 , the Property is SchemeAgency 2744 , the Representation/Association is Identifier 2756 , the Type is xsd 2768 , the Type Name is token 2780 , and the Cardinality may be zero or one 2790 . The attribute listAgencySchemeAgencyID may be optional (see 2798 ).

The CCT Code 2700 data type is used for elements that are used in the communication between partners or systems to enable a common coded value representation in place of texts, methods, or properties. This code list should be relatively stable, and not subject to frequent or significant changes (for example, CountryCode, LanguageCode, and so on). If the agency that manages the code list is not named explicitly, but is specified by using a role, this is done in the tag name.

Standardized codes and proprietary codes may be represented by CCT Code 2700 . For standardized codes whose code lists are managed by an agency from the DE 3055 code list, listID 2702 identifies the code list for the standard code, listVersionID 2704 identifies the version of the code list, and listAgencyID 2706 identifies the agency from DE 3055 (excluding roles). For proprietary codes whose code lists are managed by an agency that is identified using a standard, listID 2702 identifies a code list for the proprietary code, listVersionID 2704 identifies a version of the code list, listAgencyID 2706 identifies standardized ID for the agency (such as the company that manages the proprietary code list), listAgencySchemeID 2708 identifies the identification scheme for the schemeAgencyID, and listAgencySchemeAgencyID 2710 identifies the agency from DE 2055 that manages the standardized ID ‘listAgencyID’. For proprietary codes whose code lists are managed by an agency that is identified without the use of a standard, list ID 2702 identifies a code list for the proprietary code, listVersionID 2704 identifies a version of the code list, listAgencyID 2706 identifies a proprietary ID for the agency (such as the company that manages the proprietary code list), list AgencySchemeID 2708 identifies the identification scheme for the schemeAgencyID, and listAgencySchemeAgencyID 2710 identifies ‘ZZZ’ which is mutually defined from DE 3055 .

For proprietary codes whose code lists are managed by an agency that is specified using a role or not at all, listID 2702 identifies an identification scheme for the proprietary identifier, and listVersionID 2704 identifies a version of the identification scheme. The role is specified as a prefix in the tag name. If there is more than one code list, listID and listVersionID can be used as attributes. No attributes are required if there is only one code list.

The representation term for the CCT Code 2700 is Code.

If CCT Code 2700 is used as a basis to define a specific code GDT that combines parts of standard code lists of different standardization organizations, and the complied lists are not disjunctive, attributes listID 2702 , listVersionID 2704 , and listAgencyID 2706 may be included in the GDT. However, these attributes may not be required in the GDT if the compiled lists are not disjunctive but, in each interface that uses the GDT, the lists supported by the interface are disjunctive.

To be able to represent values, methods, and property descriptions as code, the corresponding code list may be consistent and, unlike identifier lists, subject to very few changes to its content. In certain variations, CCT Code 2700 is not used to uniquely identify any logical or real objects. In some cases it may not be possible to differentiate clearly between Identifier and Code for coded values. This is particularly applicable if a coded value is used to uniquely identify an object and, at the same time, this coded value is used to replace a longer text. For example, this includes the coded values for “Country,” “Currency,” “Organization,” “Region,” and the like. If the list of coded values in this case is consistent, then the GDT Code can be used for the individual coded values.

For example, a passport number (PassportId) is an “Identifier,” because a) it identifies a (real) object, namely, a natural person, and b) the list of passport numbers is constantly growing as new passport numbers are issued. A country code (CountryCode or CountryId) may be either an Identifier or a Code. The country code uniquely identifies a real object, namely, the country. However, the country code itself is also a replacement for the respective (unique) country name. Therefore, it is also a Code. Since the code list is relatively consistent, the country name should be represented as a Code. Changes are caused by political events and such changes are few in comparison to those relating to natural persons. A process code (ProcessCode) is a Code, because a) it describes a method type and not an object, and b) the list of process codes seldom changes.

(d) DateTime

A CCT DateTime 2800 is the time stamp, accurate to the second, of a calendar day. An example for CCT DateTime 2800 is: the following code represents Apr. 19, 2002 at 3:30, in Berlin:

<DateTime>2002-04-19T15:30:00+01:00</DateTime>.

The structure of CCT DateTime 2800 is depicted in FIG. 28 . The Category for CCT DateTime 2800 is simpleType 2802 , the Property is DateTime 2804 , the Representation/Association is Content 2806 , the Type is xsd 2808 , and the Type Name is dateTime 2810 .

The CCT DateTime 2800 core component type uses the W3C built-in data type xsd: dateTime. This is structured in accordance with the extended representation of ISO 8601. However, unlike in xsd: date, in certain variations, negative years or years are not represented with more than 4 numeric values in “Date.” The extended representation may be represented as CCYY-MM-DDThh:mm:ss(.sss)Z or CCYY-MM-DDThh:mm:ss(.sss)(+/−)hh:mm (for example, 2002-04-19T15:30:00Z or 2002-04-19T10:30:00+05:00, respectively).

The extended representation uses CC for century (00-99); YY for year (00-99); MM for month (01-12); DD for day (01-28 for month 02; 01-29 for month 02 when the year is a leap year; 01-30 for months 04, 06, 09, and 11; 01-31 for months 01, 03, 05, 07, 08, 10, and 12); a hyphen between the year, month, and day; a separator “T” between the date and time; hh for hours (00-23); mm for minutes (00-59); ss for seconds (00-59); sss for one or more characters after the decimal point to represent fractions of a second; a colon between the hours, minutes, and seconds; Z to specify when the represented time is also the UTC time; +hh:mm to specify when the represented time is a local time that is ahead of UTC time; and −hh:mm to specify when the represented time is a local time that is behind UTC time.

The time stamp may be indicated without additional information (Z, +hh:mm, −hh:mm) relative to the coordinated world time (UTC time). In certain variations, this time stamp is not then be converted to the respective local time and is therefore for information purposes.

Ranges Day, Time, Minutes, Seconds, and Time Zone are defined for DateTime. Day represents all dates from the Gregorian calendar. Time represents exactly 24 hours (0-23). Minutes represents exactly 60 minutes (0-59). Seconds represents exactly 60 seconds (0-59). Time zone may be expressed in UTC (Coordinated Universal Time). If DateTime represents a local time, the time difference with respect to UTC time may also be specified.

CCT DateTime 2800 is used for exact time stamps that may contain the day and time. It may be, the creation date/time, receipt date/time, processing date/time, delivery date/time, expiry date/time, and the like. The primary representation term for the CCT DateTime 2800 is DateTime. Additional secondary representation terms are Date and Time. Date is a calendar representation of a particular day. The Built-In Data Type of Date is xsd: date and a restriction is length=10. Time is a time stamp, accurate to the second, of a particular time. The Built-In Data Type for Time is xsd: time.

The coordinated world time or coordinated universal time (UTC) is currently the uniform basis for time specifications that are used internationally. It is based on the route of the sun and is an extremely constant time unit. The mean solar time at the Greenwich meridian can be used as an approximate guide value for UTC.

The Gregorian calendar is currently used primarily in the western world and is an approximation of the complicated calculation of a “tropical year.” The mean of the “tropical year” is 365.2422 days. The Gregorian calendar, in use since 1582, defines the rules for leap years.

(e) ElectronicAddress

A CCT ElectronicAddress 2900 is a unique digital address that is represented by the Unified Resource Identifier (URI). An example for CCT ElectronicAddress 2900 in http format is:

The structure of CCT ElectronicAddress 2900 is depicted in FIG. 29 . CCT ElectronicAddress 2900 includes attributes protocolID 2902 and languageCode 2904 . The Category for CCT ElectronicAddress 2900 is complexType 2906 , the Property is ElectronicAddress 2916 , the Representation/Association is Content 2922 , the Type is xsd 2928 and the Type Name is any URI 2934 .

For protocolID 2902 , the Category is Attribute 2908 , the Object Class is ElectronicAddress 2912 , the Property is Protocol 2918 , the Representation/Association is Identifier 2924 , the Type is xsd 2930 , the Type Name is token 2936 , and the Cardinality between the CCT Electronic Address 2900 and protocolID 2902 is zero or one 2942 . The protocolID Attribute 2902 may be optional (see 2946 ).

For languageCode 2904 , the Category is Attribute 2908 , the Object Class is ElectronicAddress 2914 , the Property is Language 2920 , the Representation/Association is Code 2926 , the Type is xsd 2932 , the Type Name is language 2938 , the Length is from two to nine 2940 , and the Cardinality between CCT Electronic Address 2900 and languageCode 2904 is zero or one 2944 . The languageCode Attribute 2904 may be optional (see 2948 ).

The syntax for CCT Electronic Address 2900 is specified in the IETF RFC 2396. A URI consists of the scheme (in other words, how to access a resource), followed by a colon and the scheme-specific part. The scheme-specific part is relevant for the service that is connected to the particular scheme. A resource can have multiple URIs. One reason may be that a resource exists physically at multiple locations, due to mirroring, or it may be addressed using different protocols, which are specified by the scheme name. For example, a file can be referenced using http and ftp.

A URI is therefore generally constructed as <scheme>:<scheme-specific part>. The following is an example of a URL with typical partial expression types:

<scheme>://<user>:<password>@<host>:<port>/<path>?<query>;

<argument>=<value>&<argument>=<value>#<fragment>.

URI schemes that are available include ftp, http, mailto, File, cid, mid, nfs, https, uuid. Additional URI schemes that are currently not required include Gopher, News, nntp, telnet, wais, prospere, z39.50s, z39.50r, vemmi, service, imap, acap, rtsp, tip, pop, data, dav, opaquelocktoken, sip, tel, fax, modem, Idap, soap.beep, soap.beeps, urn, go, afs, tn3270, and mailserver.

If the above-listed URI schemes are not sufficient to determine the address protocol, one can either apply for another URI scheme in accordance with the guidelines of IETF RFC 2717, or define the corresponding protocol type more exactly by specifying the “protocolID” attribute as well. For this protocol type, the codes from the UN/EDIFACT DE 3155 “Communication Address Code Qualifier” code list are used. These codes include AB, AF, AN, AO, EM, El, FT, GM, IM, SW, and XF. AB refers to Communications number assigned by Societe Internationale de Telecommunications Aeronaufiques (SITA). AD refers to the AT&T mailbox identifier. AF refers to the switched telecommunications network of the United States Department of Defense. AN refers to the ODETTE File Transfer Protocol. AO refers to identification of the Uniform Resource Location (URL) Synonym: World wide web address. EM refers to the Electronic Mail Exchange of mail by electronic means (SMTP). EI refers to the number identifying the service and service user of an EDI transmission. FT refers to the file transfer access method according to ISO. GM refers to the GEIS (General Electric Information Service) mailbox. IM refers to the Internal mail address/number. SW refers to communications address assigned by Society for Worldwide Interbank Financial Telecommunications s.c. XF refers to the X.400 address.

No codings currently exist for ms (Microsoft Mail) and ccmail protocols, although respective coding proposals are expected to be submitted to the UN/CEFACT Forum for standardization.

If the attachment is a document or text, attribute languageCode 2904 may be used to represent the language of the attachment in accordance with IETF RFC 1766 or IETF RFC 3066.

CCT ElectronicAddress 2900 is a core component type that can be used to represent global data types (GDTS) for email addresses, Web sites, and documents or information provided on Web sites. The representation term for the CCT ElectronicAddress 2900 is ElectronicAddress.

In certain variations, CCT ElectronicAddress 2900 is not used as a reference component for binary data that is sent as an additional MIME attachment. The CCT BinaryObject 2900 is available for this purpose.

(f) Identifier

A CCT Identifier 3000 is a unique identification of an object within an identification scheme that is managed by an agency. There may be multiple identification schemes for identifying an object. An example for CCT Identifier 3000 is: a Standard Identifier/Standard Agency is <ProductID schemeID=“GTIN” schemeAgencyID=“113”>10614141000415</ProductId>. One example of a Proprietary Identifier/Standard Agency is <ProductID schemeID=“householdappliance” schemeAgencyID=“065055766” schemeAgencySchemeID=“DUNS” schemeAgencySchemeAgencyID=“016”>123</ProductId>. One example of a Proprietary Identifier/Proprietary Agency is <ProductID schemeID=“householdappliance” schemeAgencyID=“4711” schemeAgencySchemeID=“PartyA” schemeAgencySchemeAgencyID=“ZZZ”>456</ProductId>.

The structure of CCT Identifier 3000 is depicted in FIG. 30 . CCT Identifier 3000 includes Attributes schemeID 3002 , schemeVersionID 3004 , schemeAgencyID 3006 , schemeAgency-SchemeID 3008 , and schemeAgency-SchemeAgencyID 3010 . For CCT Identifier 3000 , the Category is complexType 3012 , the Object Class is Identifier 3024 , the Property is identifier 3036 , the Representation/Association is Content 3048 , the Type is xsd 3060 , and the Datatype is token 3072 .

SchemeID 3002 identifies an identification scheme. The identification scheme represents the context that is used to identify an object. SchemeID is unique within the agency that manages this identification scheme. For schemeID, the Category is Attribute 3014 , the Object Class is IdentificationScheme 3026 , the Property is Identification 3038 , the Representation/Association is Identifier 3050 , the Type is xsd 3062 , the Datatype is token 3074 , and the Length is from one to sixty 3084 . The Cardinality between the CCT Identifier 3000 and schemeID 3002 is zero or one 3090 . The schemeID attribute 3002 may be optional (see 3095 ).

SchemeVersionID 3004 identifies the version of an identification scheme. For schemeVersionID, the Category is Attribute 3016 , the Object Class is IdentificationScheme 3028 , the Property is Version 3040 , the Representation/Association is Identifier 3052 , the Type is xsd 3064 , the Data-type is token 3076 , and the Length is from one to fifteen 3086 . The Cardinality between the CCT Identifier 3000 and SchemeVersion ID is zero or one 3091 . The schemeVersionID attribute 3004 may be optional (see 3096 ).

SchemeAgencyID 3006 identifies the agency that manages an identification scheme. The agencies from DE 3055 are used as the default, but in certain variations the roles defined in DE 3055 are not used. For schemeAgencyID, the Category is Attribute 3018 , the Object Class is IdentificationScheme-Agency 3030 , the Property is Identification 3042 , the Representation/Association is Identifier 3054 , the Type is xsd 3066 , the Datatype is token 3078 , and the Length is between one to sixty 3087 . The Cardinality between the CCT Identifier 3000 and schemeAgencyID 3006 is zero or one 3092 . The schemeAgencyID attribute 3006 may be optional (see 3097 ).

SchemeAgencySchemeID 3008 identifies the identification scheme that represents the context that is used to identify the agency. For schemeAgencySchemeID, the Category is Attribute 3020 , the Object Class is IdentificationScheme-Agency 3032 , the Property is Scheme 3044 , the Representation/Association is Identifier 3056 , the Type is xsd 3068 , the Datatype is token 3080 , and the Length is from one to sixty 3088 . The Cardinality between CCT Identifier 3000 and schemeAgencySchemeID 3008 is zero or one 3093 . The SchemeAgencySchemeID attribute 3008 may be optional (see 3098 ).

SchemeAgencySchemeAgencyID 3010 identifies the agency that manages the SchemeAgencySchemeID. This attribute can contain values from DE 3055 (excluding roles). For SchemeAgencySchemeAgencyID, the Category is Attribute 3022 , the Object Class is IdentificationScheme-Agency 3034 , the Property is SchemeAgency 3046 , the Representation/Association is Identifier 3058 , the Type is xsd 3070 , the Data-type is token 3082 , and the Length is three 3089 . The Cardinality between the CCT Identifier and SchemeAgencySchemeAgencyID 3010 is zero or one 3099 . The SchemeAgencySchemeAgencyID attribute 3010 may be optional (see 3099 ).

The CCT Identifier 3000 data type is used for elements or attributes that are used in the communication between partners or systems to enable unique identification of logical or real objects. The number of types should not be limited, but continues to grow (e.g., ProductId, OrderId, . . . ). New IDs are continually added.

If the agency that manages the identification scheme is not explicitly identified, but is specified using a role, this is done in the tag name.

Standardized and proprietary identifiers can be represented. For standardized identifiers whose identification schemes are managed by an agency from the DE 3055 code list, schemeID 3002 identifies an identification scheme for the standard identifier, schemeVersionID 3004 identifies a version of the identification scheme, and schemeAgencyID 3006 identifies an agency from DE 3055 (excluding roles). For proprietary identifiers whose identification schemes are managed by an agency that is identified using a standard, schemeID 3002 identifies an identification scheme for the proprietary identifier, schemeVersionID 3004 identifies a version of the identification scheme, schemeAgencyID 3006 identifies a standardized ID for the agency (normally the company that manages the proprietary identifier), schemeAgencySchemeID 3008 identifies an identification scheme for the schemeAgencyID, and schemeAgencySchemeAgencyID 3010 identifies an agency from DE 3055 that manages standardized ID ‘schemeAgencyID’. For proprietary identifiers whose identification schemes are managed by an agency that is identified without the use of a standard, schemeID 3002 identifies an identification scheme for the proprietary identifier, schemeVersionID 3004 identifies a version of the identification scheme, schemeAgencyID 3006 identifies a proprietary ID for the agency (normally the company that manages the proprietary identifier), schemeAgencySchemeID 3008 identifies an identification scheme for the schemeAgencyID, and schemeAgencySchemeAgencyID 3010 identifies ‘ZZZ’ which is mutually defined from DE 3055 .

For proprietary identifiers whose identification schemes are managed by an agency that is specified using a role or not at all, schemeID 3002 identifies an identification scheme for the proprietary identifier and schemeVersionID 3004 identifies a version of the identification scheme. The role is specified as a prefix in the tag name. If there is more than one identification scheme, schemeID 3002 and schemeVersionID 3004 can be used as attributes. No attributes are required if there is one identification scheme.

The representation term for the CCT “Identifier” is Identifier.

(g) Indicator

A CCT Indicator 3100 is the binary encoded specification of a fact that has the value ‘0’ or ‘1’, i.e., ‘true’ or ‘false’. An example for the CCT Indicator 3100 is: <Indicator>true</Indicator>.

The structure of CCT Indicator 3100 is depicted in FIG. 31 . The Category for CCT Indicator 3100 is simpleType 3102 , the Property is Indicator 3104 , the Representation/Association is Content 3106 , the Type is xsd 3108 , and the Type Name is Boolean 3110 .

CCT Indicator 3100 can have either the value ‘true’ (‘1’) or ‘false’ (‘0’). CCT Indicator 3100 is used for binary classifications, indicators, flags, and the like. The representation term for the CCT “Indicator” is Indicator.

(h) Measure

CCT Measure 3200 is a physical measure value with the corresponding measurement unit. One example of CCT Measure 3200 is <Measure unitCode=“KG”>100</Measure>

The structure of Measure 3200 is depicted in FIG. 32 . The Category for CCT Measure 3200 is complex Type 3204 , the Property is Measure 3210 , the Representation/Association is Content 3214 , the Datatype is xsd: decimal 3218 , and the length is 13 predecimal digits and 6 decimal values. Measure 3200 also includes attribute unitCode 3202 . For Attribute unitCode 3202 , the Category is Attribute 3206 , the Object Class is Quantity 3206 , the Property is Unit 3212 , the representation term is Code 3216 , the Datatype is xsd: token 3220 , the length is 1 to 3 3224 , and the Cardinality is one 3226 .

Positive and negative quantities can be used by using the built-in data type “xsd: decimal.” Negative values may be prefixed with a negative sign (“−”). However, positive values do not require a positive sign “+” prefix. Measurement units are represented in the attribute “unitCode,” in accordance with UN/ECE Recommendation #20.

Measure is used for the representation of measure values with physical sizes (meters, centimeters, kilograms). The Representation/Association for the CCT “Measure” is Measure.

Measure should not be confused with Quantity. In contrast to Measure, Quantity is used for the definition of quantity values or units. Quantities can on the one hand be piece sizes, such as packets, containers, and the like. but also physical sizes (meters, centimeters, kilograms).

(i) Numeric

A CCT Numeric 3300 is a decimal value. An example of the CCT Numeric 3300 is: <Numeric>123.345</Numeric>.

The structure of CCT Numeric 3300 is depicted in FIG. 33 . The Category for CCT Numeric 3300 is complexType 3302 , the Property is Numeric 3304 , the Representation/Association is Content 3306 , and the Datatype is xsd: decimal 3308 .

Positive and negative numeric values can be used by using the built-in data type “xsd: decimal.” Negative values may be prefixed with a negative sign (“−”). However, positive values do not require a positive sign “+” prefix. The decimal sign may be represented as a period (“.”).

The primary representation term for CCT Numeric 3300 is Numeric. Other secondary representation terms are Value, Rate, and Percent.

In certain variations, CCT Numeric 3300 is not used for an indication of quantity, measure or amount.

(j) Quantity

A CCT Quantity 3400 is a quantity with the corresponding quantity unit. An example of the CCT Quantity 3400 is: <Quantity unitCode=“CT”>100</Quantity>(CT=Carton).

The structure of CCT Quantity 3400 is depicted in FIG. 34 . CCT Quantity 3400 includes attribute unitCode 3402 . For the CCT Quantity 3400 , the Category is Complex Type 3404 , the Property is Quantity 3410 , the Representation/Association is Content 3414 , the Data Type is xsd: decimal 3418 , and the Length is thirteen predecimal and six decimal places 3422 .

For the Attribute unitCode 3402 , the Category is Attribute 3406 , the Object Class is Quantity 3406 , the Property is Unit 3412 , the Representation/Association is Code 3416 , the Datatype is xsd: token 3420 , and the Length is from one to three 3424 . The Cardinality between the CCT Quantity 3400 and unitCode 3402 is one 3426 . The attribute unitCode 3402 is mandatory (see 3428 ).

Positive and negative quantities can be used by using the built-in data type “xsd: decimal.” Negative values may be prefixed with a negative sign (“−”). However, positive values do not require a positive sign “+” prefix. Measurement units are represented in the attribute “unitCode,” in accordance with UN/ECE Recommendation #20 or X12 355.

CCT Quantity 3400 is used for the representation of quantity values or units. This can involve physical sizes (meters, centimeters, kilograms) or piece sizes, such as packets, containers, and the like. The representation term for the CCT Quantity 3400 is Quantity.

CCT Quantity 3400 should not be confused with Measure. In contrast to Quantity, Measure is used for the definition of physical properties, such as sizes (temperature, lengths, and the like.) and weights of a part, product or article.

(k) Text

A CCT Text 3500 is a character string with an optional language specification. An example for CCT Text 3500 is: <Text languageCode=“DE”>Text is a character string with optional language specification.</Text>.

The structure of CCT Text 3500 is depicted in FIG. 35 . CCT Text 3500 includes Attribute languageCode 3502 . For CCT Text 3500 , the Category is complexType 3504 , the Property is Text 3508 , the Representation/Association is Content 3512 , the Type is xsd 3516 , the Type Name is string 3520 , and the Length is infinity 3524 .

If the attachment is a document or text, languageCode 3502 can be used to show the language of the attachment in accordance with IETF RFC 1766 or IETF RFC 3066. For languageCode 3502 , the Category is Attribute 3506 , the Property is Language 3510 , the Type is xsd 3518 , the Type Name is language 3522 , and the Length is from two to nine 3526 . The Cardinality between the CCT Text 3500 and languageCode 3502 is zero or one 3528 . Attribute languageCode 3502 may be optional (see 3530 ).

The primary representation term for the CCT Text 3500 include Amount, BinaryObject, Code, DateTime, Identifier, Indicator, Measure, Numeric, Quantity, and Text. Additional secondary representation terms include Graphic, Picture, Sound, Video, Date, Time, Value, Rate, Percent, and Name. The character length for CCT Text 3500 is not defined.

(2) Global Data Types

(a) AcceptanceStatusCode

The GDT AcceptanceStatusCode 3600 is a coded representation of the status of the acceptance by a communication partner regarding a business transaction that has been transmitted to that partner. An example for GDT AcceptanceStatusCode 3600 is: <AcceptanceStatusCode>AP</AcceptanceStatusCode>.

The structure of GDT AcceptanceStatusCode 3600 is depicted in FIG. 36 . For GDT AcceptanceStatusCode 3600 , the Property is Acceptance Status Code 3602 , the Representation/Association is Code 3604 , the Type is CCT 3606 , the Type Name is Code 3608 , and the Length is two 3610 . AcceptanceStatusCode CCT 3600 may be restricted (see 3612 ).

The possible values for GDT AcceptanceStatusCode 3600 may be a selection from the UN/EDIFACT code list DE 4343 . Three codes that may be used are AP, AJ, and RE. AP means the business transaction transmitted by the communication partner has been accepted, AJ means a decision regarding the business transaction transmitted by the communication partner has not (yet) been made, and RE means the business transaction transmitted by the communication partner has been rejected.

GDT AcceptanceStatusCode 3600 may be used as a business status instead of as a technical acknowledgment of a message. GDT AcceptanceStatusCode 3600 also may be used as an immediate response to individual messages in bilateral negotiation processes between communication partners.

In a variation, GDT AcceptanceStatusCode 3600 is a proprietary selection from the UN/EDIFACT code list DE 4343 . Addition of codes to this selection from the code list may require the approval of the Process Integration Council (PIC).

(b) AccountingObjectSet

A GDT AccountingObjectSet 3700 is a set of different account assignment objects. An account assignment object is a business object to which changes in value from business transactions may be assigned in accounting. An example of GDT AccountingObjectSet 3700 is:

The structure of GDT AccountingObjectSet 3700 is depicted in FIG. 37 . GDT AccountingObjectSet 3700 includes an element CostCenterID 3702 . For GDT AccountingObjectSet 3700 , the Object Class is Accounting Object Set 3706 and the Representation/Association is Details 3712 .

For CostCenterID 3702 , the Category is Element 3704 , the Object Class is Cost Center 3708 , the Property is Identification 3710 , the Representation/Association is identifier 3714 , the Type is CCT 3716 , the Type is identifier 3718 , and the Length is from one to thirty-two 3720 . The Cardinality between the GDT AccountingObjectSet 3700 and CostCenterID 3702 is zero or one 3722 .

The data type GDT AccountingObjectSet 3700 provides the identifier for multiple types of account assignment objects including cost center (organizational unit for which costs arise), sales order, project, asset, task, funds center, and profit center. Identifiers are optional, but at least one identifier may be specified.

The data type GDT AccountingObjectSet 3700 may be used for account assignment, i.e., to assign an amount or quantity to a set of account assignment objects. The amount or quantity is assigned to account assignment objects of the GDT AccountingObjectSet 3700 according to accounting rules. For example, expenses from the purchase of office materials can be transferred to Accounting once the incoming invoice for the materials has been checked and then assigned to a cost center CC 1000 and a profit center PC 3050 there.

Applications that distribute an amount to several AccountingObjectSets (e.g., as percentages) may perform this distribution themselves and transfer the partial amounts, each with a separate AccountingObjectSet, to accounting. An example of a percentage distribution to several AccountingObjectSets is 40% to cost center CC 1000 and profit center PC 3050 , 20% to cost center CC 2000 and task IO 0815 , and 40% to cost center CC 3000

(c) ActionCode

A GDT ActionCode 3802 is a coded representation of an instruction to the recipient of a message about how to process a transmitted business object.

An example for GDT ActionCode 3802 is:

The structure of ActionCode 3802 is depicted in FIG. 38 . For GDT ActionCode 3802 , the Property is Action 3804 , the Representation/Association is Code 3806 , the Type is CCT 3808 , the Type Name is Code, and the Length is two 3812 . GDT ActionCode 3802 may be a restricted GDT (see 3814 ).

In a variation, GDT ActionCode 3802 can have a value from 01 to 06. The name for code 01 is Create and means that the element is to be created at the recipient. The element does not exist at the recipient. The element ID and data is transferred. The name for code 02 is Change and means that the element is to be changed at the recipient. The element exists at the recipient. The element ID and data is transferred. The name for the code 03 is Delete and means the element is to be deleted at the recipient. The element exists at the recipient. The element ID is transferred; data is transferred with the exception of elements that are mandatory due to their cardinality. The name for the code 04 is Save and means the element is to be saved at the recipient. The element can exist at the recipient. If the element already exists there, it is changed. If it does not exist there, it is created. The name for code 05 is Remove and means the element is to be deleted at the recipient. The element can exist at the recipient. If it exists, it is deleted. The element ID is transferred; data is not transferred with the exception of elements that are mandatory due to their cardinality. The name for code 06 is No Action and means that no action is to be carried out for the element at the recipient. The element exists at the recipient. The element ID and data is transferred.

ActionCodes may be used under one another in a hierarchy of elements. The following table lists the combinations that may be allowed (X) and not allowed (−).

For the table above, note (1) indicates that the code can have the meaning of the code “01” (Create). Note (2) in the table indicates that, to ensure compatibility with regard to enhancements, code “04” (Save) is allowed because this code is the default code if no code is transferred. A sender preferably does not set this code. A recipient preferably handles this code as a code “06” (No Action).

Also, regarding the table above, no further codes occur under code “03” (Delete) or “05” (Remove) because, apart from the element ID, no further data is transferred. A recipient checks the existence of an element using the rules described for the individual codes and generates an error if necessary. A recipient checks the validity of the codes in a hierarchy of elements according to the rules described and generates an error if necessary. A recipient ignores elements and ActionCodes transferred under a code “03” (Delete) or “05 (Remove) and behaves as if these elements and ActionCodes had not been transferred. A syntax check is allowed for these elements.

The actions requested at the recipient can have names that are typically used in the business context of a message, as long as this does not change the semantics of the ActionCodes defined above. For example, “Annul” or “Cancel” can be used instead of “Delete”. An ActionCode is an attribute of the element to which it refers.

The ActionCodes “01” (Create), “02” (Change), “03” (Delete), and “06” (No Action) may model strict semantics that lead to errors at the recipient if the elements corresponding to the actions requested by the sender exist (“01”) or do not exist (“02”, “03”, “06”) at the recipient. Using strict semantics, therefore, may require that the sender have and use information about the messages it has already sent. The ActionCodes “04” (Save) and “05” (Remove) model soft semantics that, in a variation, do not lead to errors if the respective elements do not exist at the recipient. These soft semantics, therefore, do not require that the sender have and use information about the messages it has already sent. In a variation, an ActionCode that is not filled in a message instance or does not exist in an interface may be assumed to be “04” (Save). This ensures compatibility when enhancing interfaces to include an ActionCode.

In some messages, the action at the top level may be represented in the name of the message type rather than by an ActionCode. These messages behave semantically as if the ActionCode were at the level of the transferred BusinessTransactionDocument (for example: a message of the message type PurchaseOrderChangeRequest behaves semantically as if an ActionCode “02” (Change) were specified at the PurchaseOrder level).

An ActionCode may be used with a CompleteTransmissionIndicator for the parent element. For information about the combined use of CompleteTransmissionIndicator and ActionCode, see the description herein for the CompleteTransmissionIndicator. The ActionCode, can also be used for an element whose parent element does not have a CompleteTransmissionIndicator. In this case, the child elements of the parent element are transferred, not just the changed child elements.

The ActionCode may be used for elements that remain uniquely identifiable across several messages in a business process or that can only occur once in a message (cardinality 0 . . . 1 or 1). If an element cannot be clearly identified, it is documented explicitly when the ActionCode is used.

In a variation, the ActionCodes “03” (Delete) and “05” (Remove) do not stipulate that the recipient delete the respective element physically. However, once the element has been deleted, the recipient application handles further transmitted ActionCodes as if the element has been physically deleted. For example, in the case of the ActionCode “01” (Create), it is possible to create a new element with the same identification as the deleted element. Exceptions to this ActionCode behavior are explained and documented in the corresponding description of the interface or message type.

(d) ActiveIndicator

A GDT ActiveIndicator 3902 indicates whether an object is commercially active and whether it can be used in a process or not. An example of GDT ActiveIndicator 3902 is: <ActiveIndicator>true</ActiveIndicator>.

The structure of GDT ActiveIndicator 3902 is depicted in FIG. 39 . For the GDT ActiveIndicator 3902 , the Property is Active Indicator 3904 , the Representation/Association is Indicator 3906 , and the Type is CCT: Indicator 3908 . GDT ActiveIndicator 3902 can have values 1 (true) or 0 (false). True means the object is active and false means the object is not active.

GDT ActiveIndicator 3902 is used to label objects that can be commercially active or inactive, for example, sources of supply. In the context of an interface, there may be a description of which object the GDT ActiveIndicator 3902 refers to and what it means in terms of business.

(e) Address

A GDT Address 4000 a contains structured information about types of addresses. This information includes details about addressees, the postal address, and the physical location and communication connections.

The structure of GDT Address 4000 a is depicted in FIG. 40 . GDT Address 4000 a includes elements OrganisationFormattedName 4002 a , PersonName 4003 a , FunctionalTitleName 4004 a , DepartmentName 4005 a , Office 4006 a , PhysicalAddress 4012 a , TaxJurisdictionCode 4036 a , TimeZoneDifferenceValue 4037 a , GeoCoordinates 4038 a , and Communication 4039 a . For the GDT Address 4000 a , the Object Class is Address 4000 b and the Representation/Association is Details 4000 c.

Within the global data type GDT Address 4000 a , OrganisationFormattedName 4002 a contains the name of an organization (for example, a company or corporate body) as a part of the address. For example, this might be the address of a business partner. For OrganisatoinFormattedName 4002 a , the Category is Element 4002 b , the Object Class is Address 4002 c , the Property is Organisation Formatted Name 4002 d , the Representation/Association is Name 4002 e , the Type is CCT 4002 f , the Type Name is text 4002 g , and the Length is from zero to forty 4002 h . The Cardinality between the GDT Address 4000 a and OrganisatoinFormattedName 4002 b is from zero to four 4003 i . OrganisationFormattedName may be restricted (see 4002 j ).

PersonName 4003 a contains the parts of a natural person's name. For PersonName 4003 a , the Category is Element 4003 b , the Object Class is Address 4003 c , the Property is Person Name 4003 d , the Representation/Association is Person Name 4003 e , the Type is GDT 4003 f , and the Type Name is Person Name 4003 g . The Cardinality between the GDT Address 4000 a and PersonName 4003 a is zero or one 4003 h.

FunctionalTitleName 4004 a contains the function of a contact person and can be a part of the address of the contact person in the organization. For the FunctionalTitleName 4004 a , the Category is Element 4004 b , the Object Class is Address 4004 c , the Property is Functional Title Name 4004 d , the Representation/Association is Name 4004 e , the Type is CCT 4004 f , the Type Name is Text 4004 g , and the Length is from zero to forty 4004 h . The Cardinality between the GDT Address 4000 a and FunctionalTitleName 4004 a is zero or one 4004 i . FunctionalTitleName may be restricted (see 4004 j ).

DepartmentName 4005 a contains the department of a contact person and can be a part of the address of the contact person in the organization. For the DepartmentName 4005 a , the Category is Element 4005 b , the Object Class is Address 4005 c , the Property is Department Name 4005 d , the Representation/Association is Name 4005 e , the Type is CCT 4005 f , the Type Name is text 4005 g , and the Length is from zero to forty 4005 h . The Cardinality between the GDT Address 4000 a and DepartmentName 4005 a is zero or one 4005 i . DepartmentName may be restricted (see 4005 j ).

Office 4006 a contains information that describes the working environment of a contact person as well as information for addressing or identifying this person within the organization. For Office 4006 a , the Category is Element 4006 b , the Object Class is Address 4006 c , the Property is Office 4006 d , and the Representation/Association is Details 4006 e . The Cardinality between the GDT Address 4000 a and Office 4006 a is zero or one 4006 f . Office can also comprise BuildingID 4007 a , FloorID 4008 a , RoomID 4009 a , InhouseMailID 4010 a , and CorrespondenceShortName 4011 a.

BuildingID 4007 a is the number or ID of the building in the address of a contact person. For BuildingID 4007 a , the Category is Element 4007 b , the Object Class is Office 4007 c , the Property is Building Identification 4007 d , the Representation/Association is Identifier 4007 e , the Type is CCT 4007 f , the Type Name is identifier 4007 g , and the Length is from one to ten 4007 h . The Cardinality between the GDT Address 4000 a and BuildingID 4007 a is zero or one 4007 i . BuildingID may be restricted (see 4007 j ).

FloorID 4008 a refers to the floor of the building in the address of a contact person. For FloorID 4008 a , the Category is Element 4008 b , the Object Class is Office 4008 c , the Property is Floor Identification 4008 d , the Representation/Association is Identifier 4008 e , the Type is CCT 4008 f , the Type Name is Identifier 4008 g , and the Length is from one to ten 4008 h . The Cardinality between the GDT Address 4000 a and FloorID 4008 a is zero or one 4008 i . FloorID may be restricted (see 4008 j ).

RoomID 4009 a specifies the room number in the address of a contact person. For RoomID 4009 a , the Category is Element 4009 b , the Object Class is Office 4009 c , the Property is Room Identification 4009 d , the Representation/Association is Identifier 4009 e , the Type is CCT 4009 f , the Type Name is Identifier 4009 g , and the Length is from one to ten 4009 h . The Cardinality between the GDT Address 4000 a and RoomID 4009 a is zero or one 4009 i . RoomID may be restricted (see 4009 j ).

InhouseMailID 4010 a specifies an internal mail address. For InhouseMailID 4010 a , the Category is Element 4010 b , the Object Class is Office 4010 c , the Property is Inhouse Identification 4010 d , the Representation/Association is Identifier 4010 e , the Type is CCT 4010 f , the Type Name is Identifier 4010 g , and the Length is from one to ten 4010 h . The Cardinality between the GDT Address 4000 a and InhouseMailID 4010 a is zero or one 4010 i . InHouseMailID may be restricted (see 4010 j ).

CorrespondenceShortName 4011 a is the short name of the contact person for use in correspondence. This short name can be used both internally and externally. For CorrespondenceShortName 4011 a , the Category is Element 4011 b , the Object Class is Office 4011 c , the Property is Correspondence Short Name 4011 d , the Representation/Association is Name 4011 e , the Type is CCT 4011 f , the Type Name is text 4011 g , and the Length is from zero to ten 4011 h . The Cardinality between the GDT Address 4000 a and CorrespondenceShortName 4011 a is zero or one 4011 i . CorrespondenceShortName may be restricted (see 4011 j ).

PhysicalAddress 4012 a contains the postal address data of a physical location. For the PhysicalAddress 4012 a , the Category is Element 4012 b , the Object Class is Address 4012 c , the Property is Physical Address 4012 d , and the Representation/Association is Details 4012 e . The Cardinality between the GDT Address 4000 a and PhysicalAddress 4012 a is zero or one 4012 f.

PhysicalAddress 4012 a also comprises CountryCode 4013 a , RegionCode 4014 a , StreetPostalCode 4015 a , POBox PostalCode 4016 a , CompanyPostalCode 4017 a , CityName 4018 a , AdditionalCityName 4019 a , DistrictName 4020 a , POBoxID 4021 a , POBoxIndicator 4022 a , POBoxCountryCode 4023 a , POBoxRegionCode 4034 a , POBoxCityName 4035 a , StreetName 4036 a , StreetPrefixName 4037 a , StreetSuffixName 4038 a , HouseID 4039 a , AdditionalHouseID 4040 a , BuildingID 4041 a , FloorID 4042 a , RoomID 4043 a , CareOfName 4044 a , and Description 4045 a . For each, the category is Element ( 4013 b - 4045 b ) and the Object Class is Physical Address ( 4013 c - 4045 c ).

CountryCode 4013 a is the country code of the address in accordance with ISO 3166-1. For the CountryCode 4013 a , the Property is CountryCode 4013 d , the Representation/Association is Code 4013 e , the Type is GDT 4013 f , and the Type Name is CountryCode 4013 g . The Cardinality between the GDT Address 4000 a and CountryCode 4013 a is zero or one 4013 h.

RegionCode 4014 a is the code for the region of the country in the address. This specification may be part of the address, e.g., in the US. For RegionCode 4014 a , the Property is RegionCode 4014 d , the Representation/Association is Code 4014 e , the Type is GDT 4014 f , and the Type Name is RegionCode 4014 g . The Cardinality between the GDT Address 4000 a and RegionCode 4014 a is zero or one 4014 h.

StreetPostalCode 4015 a is the zip code in the street address. The rules for zip codes are country-specific. For StreetPostalCode 4015 a , the Property is Street Zip Code 4015 d , the Representation/Association is Code 4015 e , the Type is CCT 4015 f , the Type Name is Code 4015 g , and the Length is from one to ten 4015 h . The Cardinality between GDT Address 4000 a and StreetPostalCode 4015 a is zero or one 4015 i . StreetPostalCode 4015 a may be restricted (see 4015 j ).

POBoxPostalCode 4016 a is the box zip code. For POBoxPostalCode 4016 a , the Property is PO Box Zip Code 4016 d , the Representation/Association is Code 4016 e , the Type is CCT 4016 f , the Type Name is Code 4016 g , and the Length is from one to ten 4016 h . The Cardinality between GDT Address 4000 a and POBoxPostalCode 4016 a is zero or one 4016 i . POBoxPostalCode 4016 a may be restricted (see 4016 j ).

CompanyPostalCode 4017 a is the zip code of the company when the receiver is an organization with its own zip code. For CompanyPostalCode 4017 a , the Property is Company Zip Code 4017 d , the Representation/Association is Code 4017 e , the Type is CCT 4017 f , the Type Name is Code 4017 g , and the Length is from one to ten 4017 h . The Cardinality between GDT Address 4000 a and CompanyPostalCode 4017 a is zero or one 4017 i . CompanyPostalCode 4015 a may be restricted (see 4017 j ).

CityName 4018 a is the name of the city in the address. For the CityName 4018 a , the Property is City Name 4018 d , the Representation/Association is Name 4018 e , the Type is CCT 4018 f , the Type Name is Text 4018 g , and the Length is from zero to forty 4018 h . The Cardinality between GDT Address 4000 a and CityName 4018 a is zero or one 4018 i . CityName 4018 a may be restricted (see 4018 j ).

AdditionalCityName 4019 a is the name of the city of residence if it differs from the city in the postal address. AdditionalCityName may have different semantics (field HOME_CITY in the ADRC) and therefore may not be handled using Cardinality. It is analogous to AdditionalHouseID. For AdditionalCityName 4019 a , the Property is Additional City Name 4019 d , the Representation/Association is Name 4019 e , the Type is CCT 4019 f , the Type Name is Text 4019 g , and the Length is from zero to forty 4019 h . The Cardinality between the GDT Address 4000 a and AdditionalCityName 4019 a is zero or one 4019 i . AdditionalCityName 4019 a may be restricted (see 4019 j ).

DistrictName 4020 a is the name of the district. For DistrictName 4020 a , the Property is District Name 4020 d , the Representation/Association is Name 4020 e , the Type is CCT 4020 f , the Type Name is Text 4020 g , and the Length is from zero to forty 4020 h . The Cardinality between the GDT Address 4000 a and DistrictName 4020 a is zero or one 4020 i . DistrictName 4020 a may be restricted (see 4020 j ).

POBoxID 4021 a is the number of the post-office box. For POBoxID 4021 a , the Property is PO Box Identification 4021 d , the Representation/Association is Identifier 4021 e , the Type is CCT 4021 f , the Type Name is Identifier 4021 g , and the Length is from one to ten 4021 h . The Cardinality between the GDT Address 4000 a and POBoxID 4021 a is zero or one 4021 i . CityName 4021 a may be restricted (see 4021 j ).

POBoxIndicator 4022 a specifies whether the post-office box has a number that is unknown. For POBoxIndicator 4018 a , the Property is PO Box Indicator 4018 d , the Representation/Association is Indicator 4018 e , the Type is CCT 4018 f , and the Type Name is Indicator 4018 g . The Cardinality between GDT Address 4000 a and POBoxIndicator 4022 is zero or one 4018 h.

POBoxCountryCode 4023 a is the country code for the post-office box in the address. For POBoxCountryCode 4023 a , the Property is PO Box Country Code 4023 d , the Representation/Association is Code 4023 e , the Type is GDT 4023 f , and the Type Name is CountryCode 4023 g . The Cardinality between GDT Address 4000 a and POBoxCountryCode 4023 a is zero or one 4023 h.

POBoxRegionCode 4024 a is the code for the region of the country for the post-office box in the address. For the POBoxRegionCode 4024 a , the Property is PO Box Region Code 4024 d , the Representation/Association is Code 4024 e , the Type is GDT 4024 f , and the Type Name is Region Code 4024 g . The Cardinality between GDT Address 4000 a and POBoxRegionCode 4024 a is zero or one 4024 h.

POBoxCityName 4025 a is the name of the city for the post-office box in the address. For the POBoxCityName 4025 a , the Property is PO Box City name 4025 d , the Representation/Association is Name 4025 e , the Type is CCT 4025 f , the Type Name is Text 4025 g , and the Length is from zero to forty 4025 h . The Cardinality between GDT Address 4000 a and POBoxCityName 4025 a is zero or one 4025 i . POBoxCityName 4025 a may be restricted (see 4025 j ).

StreetName 4026 a is the name of the street in the address. For the StreetName 4026 a , the Property is Street name 4026 d , the Representation/Association is Name 4026 e , the Type is CCT 4026 f , the Type Name is Text 4026 g , and the Length is from zero to sixty 4026 h . The Cardinality between GDT Address 4000 a and StreetName 4026 a is zero or one 4026 i . POBoxCityName 4026 a may be restricted (see 4026 j ).

StreetPrefixName 4027 a is an additional prefix in the address and precedes the street name in the previous line. For the StreetPrefixName 4027 a , the Property is Street Prefix Name 4027 d , the Representation/Association is Name 4027 e , the Type is CCT 4027 f , the Type Name is Text 4027 g , and the Length is from zero to forty 4027 h . The Cardinality between GDT Address 4000 a and StreetPrefixName 4027 a is from zero to two 4027 i . StreetPrefixName 4027 a may be restricted (see 4027 j )

StreetSuffixName 4028 a is an additional suffix in the address and comes after the street name in the subsequent line. For the StreetSuffixName 4028 a , the Property is Street Suffix Name 4028 d , the Representation/Association is Name 4028 e , the Type is CCT 4028 f , the Type Name is Text 4028 g , and the Length is from zero to forty 4028 h . The Cardinality between GDT Address 4000 a and StreetSuffixName 4028 a is from zero to two 4028 i . StreetPrefixName 4028 a may be restricted (see 4028 j ).

HouseID 4029 a is the house number for the street in the address. For the HouseID 4029 a , the Property is House Identification 4029 d , the Representation/Association is Identifier 4029 e , the Type is CCT 4029 f , the Type Name is Identifier 4029 g , and the Length is from one to ten 4029 h . The Cardinality between GDT Address 4000 a and HouseID 4029 a is zero or one 4029 i . HouseID 4029 a may be restricted (see 4029 j ).

AdditionalHouseID 4030 a is an addition to the house number, e.g., apartment number. For the AdditionalHouseID 4030 a , the Property is Additional House Identification 4030 d , the Representation/Association is Identifier 4030 e , the Type is CCT 4030 f , the Type Name is Identifier 4030 g , and the Length is from one to ten 4030 h . The Cardinality between GDT Address 4000 a and AdditionalHouseID is zero or one 4030 i . AdditionalHouseID 4030 a may be restricted (see 4030 j ).

BuildingID 4031 a is the number or abbreviation for a building, e.g., WDF03. For the BuildingID 4030 a , the Property is Building Identification 4030 d , the Representation/Association is Identifier 4030 e , the Type is CCT 4030 f , the Type Name is Identifier 4030 g , the Length is from one to twenty 4030 h . The Cardinality between GDT Address 4000 a and BuildingID 4031 a is zero or one 4030 i . BuildingID 4030 a may be restricted (see 4030 j ).

FloorID 4032 a is the number of the floor in the building. For the FloorID 4032 a , the Property is Floor Identification 4032 d , the Representation/Association is Identifier 4032 e , the Type is CCT 4032 f , the Type Name is Identifier 4032 g , and the Length is from one to ten 4032 h . The Cardinality between GDT Address 4000 a and FloorID 4032 a is zero or one 4032 i . FloorID 4032 a may be restricted (see 4032 j ).

RoomID 4033 a is the number of the room in the building. For the RoomID 4033 a , the Property is Room Identification 4033 d , the Representation/Association is Identifier 4033 e , the Type is CCT 4033 f , the Type Name is Identifier 4033 g , and the Length is from one to ten 4033 h . The Cardinality between GDT Address 4000 a and RoomID 4033 a is zero or one 4033 i . RoomID 4033 a may be restricted (see 4033 j ).

CareOfName 4034 a is a different receiver when the receiver is not the same as the addressee. For the CareofName 4034 a , the Property is Care of name 4034 d , the Representation/Association is Name 4034 e , the Type is CCT 4034 f , the Type Name is Text 4034 g , and the Length is from zero to ten 4034 h . The Cardinality between the GDT Address 4000 a and CareOfName 4034 a is zero or one 4034 i . CareofName 4034 a may be restricted (see 4034 j ).

Description 4035 a is an addition to the address that refers to any special details. For the Description 4030 a , the Property is Description 4030 d , the Representation/Association is Text 4030 e , the Type is GDT 4030 f , and the Type Name is Description 4030 g . The Cardinality between GDT Address 4000 a and Description 4035 a is unbounded 4030 h.

TaxJurisdictionCode 4036 a is the tax jurisdiction code belonging to the address. This code is used in various countries and can normally be derived uniquely from the address. However, it is dependent on the code list of the provider. A country can have multiple code-list providers. For the TaxJurisdictionCode 4036 a , the Category is Element 4036 b , the Object Class is Address 4036 c , the Property is Tax Jurisdiction Code 4036 d , the Representation/Association is Code 4036 e , the Type is GDT 4046 f , and the Type Name is TaxJurisdictionCode 4036 g . The Cardinality between the GDT Address 4000 a and TaxJurisdictionCode 4036 a is zero or one 4036 h.

TimeZoneDifferenceValue 4037 a is the difference (in hours) between the local time zone of the location defined by PhysicalAddress 4012 a and UTC (Coordinated Universal Time). For the TimeZoneDifferenceValue 4037 a , the Category is Element 4037 b , the Object Class is Address 4037 c , the Property is Time Zone Difference Value 4037 d , the Representation/Association is Value 4037 e , the Type is GDT 4037 f , and the Type Name is TimeZoneDifferenceValue 4037 g . The Cardinality between the GDT Address 4000 a and TimeZoneDifference Value 4037 a is zero or one 4037 h.

GeoCoordinates 4038 a contains the geographic data, i.e., longitude and latitude, specified in accordance with the WGS84 reference system, with which a location on the globe can be determined. LatitudeMeasure is the geographic latitude in degrees. LongitudeMeasure is the Geographic longitude in degrees. The measurement unit degrees for each is specified by the attribute “unitCode” Southern latitudes are generally negative and northern latitudes are generally positive. Also, western longitudes are negative and eastern longitudes are positive. Positive values do not require a positive sign (+) for a prefix. However, negative values may have a negative sign (−) for a prefix. The unitCode “DD” corresponds to the unit for the degree of an angle (UN/CEFACT Rec. #20). For the GeoCoordinates 4038 a , the Category is Element 4038 b , the Object Class is Address 4038 c , the Property is GeoCoordinates 4038 d , the Representation/Association is GeoCoordinates 4038 e , the Type is GDT 4038 f , and the Type Name is GeoCoordinates 4038 g . The Cardinality between the GDT Address 4000 a and GeoCoordinates 4038 a is zero or one 4038 h.

Communication 4049 a contains information about communication paths with which a person or organization can be reached. For the Communication 4049 a , the Category is Element 4049 b , the Object Class is Address 4049 c , the Property is Communication 4049 d , and the Representation/Association is Details 4049 e . The Cardinality between the GDT Address 4000 a and Communication 4049 is zero or one 4049 f . Communication 4049 a is comprised of CorrespondenceLanguageCode 4040 a , Telephone 4042 a , MobilePhone 4047 a , Facsimile 4052 a , email 4058 a , and Web 4063 a.

CorrespondenceLanguageCode 4040 a specifies the language for written correspondence. For CorrespondenceLanguageCode 4040 a , the Category is Element 4040 b , the Object Class is Communication 4040 c , the Property is Correspondence Language Code 4040 d , the Representation/Association is Code 4040 e , the Type is GDT 4040 f , and the Type Name is LanguageCode 4040 g . The Cardinality may be zero or one 4040 h.

Telephone 4042 a contains one telephone number in each instance. For Telephone 4042 a , the Category is Element 4042 b , the Object Class is Communication 4042 c , the Property is Telephone 4042 d , and the Representation/Association is Details 4042 e . The Cardinality between the GDT Address 4000 a and Telephone 4042 a is unbounded 4042 f . Telephone is comprised of Number 4043 a , NumberDefaltIndicator 4044 a , NumberDescription 4045 a , and NumberUsageDenialIndicator 4046 a.

For Number 4043 a , the Category is Element 4043 b , the Object Class is telephone 4043 c , the Property is Phone Number 4043 d , the Representation/Association is Phone Number 4043 e , the Type is GDT 4043 f , and the Type Name is Phone Number 4043 g . The Cardinality between the GDT Address 4000 a and Number 4043 a is one 4043 h.

NumberDefaultIndicator 4044 a indicates whether a telephone number is the default number for the address. In certain variations, there may be a default telephone number, provided the address contains a telephone number. The default value is “false.” For NumberDefaultIndicator 4044 a , the Category is Element 4044 b , the Object Class is Telephone 4044 c , the Property is Number Default Indicator 4044 d , the Representation/Association is Indicator 4044 e , the Type is CCT 4044 f , and the Type Name is Indicator 4044 g . The Cardinality between the GDT Address 4000 a and NumberDefaultIndicator 4044 a is one 4044 h.

NumberDescription 4045 a is an addition to the telephone number that refers to special details or that contains other unstructured information. For NumberDescription 4045 a , the Category is Element 4045 b , the Object Class is telephone 4045 c , the Property is Number Description 4045 d , the Representation/Association is Text 4045 e , the Type is GDT 4045 f , and the Type Name is Description 4045 g . The Cardinality between the GDT Address 4000 a and NumberDescription 4045 a is unbounded 4045 h.

NumberUsageDenial 4046 a indicates whether the telephone number may be used or not. If this indicator is set to “true,” this means that, in accordance with the legal requirements of the respective country, the telephone number may not be used. There are exceptions, however. For example, return calls requested by the business partner or calls made for service purposes may still be permitted. Furthermore, it is advisable to save telephone numbers so that calls from business partners can still be identified, even if this indicator is set. The default is “false.” For NumberUsageDenial 4046 a , the Category is Element 4046 b , the Object Class is telephone 4046 c , the Property is Number Usage Denial Indicator 4046 d , the Representation/Association is Indicator 4046 e , the Type is CCT 4046 f , and the Type Name is Indicator 4046 g . The Cardinality between the GDT Address 4000 a and NumberUsageDenial 4046 a is one 4046 h.

MobilePhone 4047 a contains a mobile phone number in each instance. For MobilePhone 4047 a , the Category is Element 4047 b , the Object Class is Communication 4047 c , the Property is Mobile Phone 4047 d , and the Representation/Association is Details 4047 e . The Cardinality between the GDT Address 4000 a and MobilePhone 4047 a is unbounded 4047 f . MobilePhone 4047 a is also comprised of Number 4048 a , NumberDefaultIndicator 4049 a , NumberDescription 4050 a , and NumberUsageDenialIndicator 4051 a.

For Number 4048 a , the Category is Element 4048 b , the Object Class is Mobilephone 4048 c , the Property is Phone Number 4048 d , the Representation/Association is Phone Number 4048 e , the Type is GDT 4048 f , and the Type Name is Phone Number 4048 g . The Cardinality between the GDT Address 4000 a and Number 4048 a is one 4048 h.

NumberDefaultIndicator 4049 a indicates whether a mobile phone number is the default mobile phone number for the address. In certain variations, there may be a default mobile phone number, provided the address contains a mobile phone number. For NumberDefaultIndicator 4049 a , the Category is Element 4049 b , the Object Class is Mobilephone 4049 c , the Property is Number Default Indicator 4049 d , the Representation/Association is Indicator 4049 e , the Type is CCT 4049 f , and the Type Name is Indicator 4049 g . The Cardinality between the GDT Address 4000 a and NumberDefaultIndicator 4049 a is one 4049 h.

NumberDescription 4050 a is an addition to the mobile phone number that refers to special details or that contains other unstructured information. For NumberDescription 4050 a , the Category is Element 4050 b , the Object Class is Mobilephone 4050 c , the Property is Number Description 4050 d , the Representation/Association is Text 4050 e , the Type is GDT 4050 f , and the Type Name is Description 4050 g . The Cardinality between the GDT Address 4000 a and NumberDescription 4050 a is unbounded 4050 h.

NumberUsageDenialIndicator 4051 a indicates whether the mobile phone number may be used or not. If this indicator is set to “true,” this means that, in accordance with the legal requirements of the respective country, the mobile phone number may not be used. There are exceptions, however. For example, return calls requested by the business partner or calls made for service purposes may still be permitted. Further, mobile phone numbers may be saved so that calls from business partners and the like can still be identified, even if the indicator is set. For NumberUsageDenial 4051 a , the Category is Element 4051 b , the Object Class is Mobilephone 4051 c , the Property is Number Usage Denial Indicator 4051 d , the Representation/Association is Indicator 4051 e , the Type is CCT 4051 f , and the Type Name is Indicator 4051 g . The Cardinality between the GDT Address 4000 a and NumberUsageDenialIndicator 4051 a is one 4051 h.

Facsimile 4052 a contains a fax number in each instance. For Facsimile 4052 a , the Category is Element 4052 b , the Object Class is Communication 4052 c , the Property is Facsimile 4052 d , and the Representation/Association is Details 4052 e . The Cardinality between the GDT Address 4000 a and Facsimile 4052 a is unbounded 4052 f . Facsimile 4052 a is also comprised of Number 4053 a , NumberDefaultIndicator 4054 a , NumberDescription 4055 a , and NumberUsageDenialIndicator 4056 a.

For Number 4053 a , the Category is E 4053 b , the Object Class is Facsimile 4053 c , the Property is Phone Number 4053 d , the Representation/Association is Phone Number 4053 e , the Type is GDT 4053 f , the Type Name is Phone Number 4053 g , and the Cardinality between the GDT Address 4000 a and Number 4053 a is one 4053 h.

NumberDefaultIndicator 4054 a indicates whether a fax number is the default number for the address. In certain variations, there is a default fax number, provided the address contains a fax number. For NumberDefaultIndicator 4054 a , the Category is Element 4054 b , the Object Class is Facsimile 4054 c , the Property is Number Default Indicator 4054 d , the Representation/Association is Indicator 4054 e , the Type is CCT 4054 f , and the Type Name is Indicator 4054 g . The Cardinality between the GDT Address 4000 a and NumberDefaultIndicator 4054 a is one 4054 h.

NumberDescription 4055 a is an addition to the fax number that refers to special details or that contains other unstructured information. For NumberDescription 4055 a , the Category is Element 4055 b , the Object Class is Facsimile 4055 c , the Property is Number Description 4055 d , the Representation/Association is Text 4055 e , the Type is GDT 4055 f , and the Type Name is Description 4055 g . The Cardinality between the GDT Address 4000 a and NumberDescription 4055 a is unbounded 4055 h.

NumberUsageDenial 4056 a indicates whether the fax number may be used or not. If this indicator is set to “true,” this means that, in accordance with the legal requirements of the respective country, the fax number may not be used. There are exceptions, however. For example, response faxes requested by the business partner or faxes sent for service purposes and the like may still be permitted. Furthermore, it is advisable to save fax numbers so that faxes sent by business partners and the like can still be identified, even if the indicator is set. For NumberUsageDenial 4056 a , the Category is Element 4056 b , the Object Class is Facsimile 4056 c , the Property is Number Usage Denial Indicator 4056 d , the Representation/Association is Indicator 4056 e , the Type is CCT 4056 f , and the Type Name is Indicator 4056 g . The Cardinality between the GDT Address 4000 a and NumberUsageDenial 4056 a is one 4056 h.

Email 4058 a contains an email address in each instance. For Email 4058 a , the Category is Element 4058 b , the Object Class is Communication 4058 c , the Property is Email 4058 d , and the Representation/Association is Details 4058 e . The Cardinality between the GDT Address 4000 a and Email 4058 a is unbounded 4058 h . Email 4058 also comprises Address 4059 a , AddressDefaultIndicator 4060 a , AddressDescription 4061 a , and AddressUsageDenialIndicator 4062 a.

Address 4059 a specifies the email address. For Address 4059 a , the Category is Element 4059 b , the Object Class is Email 4059 c , the Property is Email Address 4059 d , the Representation/Association is Email Address 4059 e , the Type is GDT 4059 f , and the Type Name is Email Address 4059 g . The Cardinality between the GDT Address 4000 a and Address 4059 a is one 4053 h.

AddressDefaultIndicator 4060 a indicates whether an email address is the default email address for this address. There may be a default email address, provided there are any email addresses for this address. For AddressDefaultIndicator 4060 a , the Category is Element 4060 b , the Object Class is Email 4060 c , the Property is Email Address Default Indicator 4060 d , the Representation/Association is Indicator 4060 e , the Type is CCT 4060 f , and the Type Name is Indicator 4060 g . The Cardinality between the GDT Address 4000 a and AddressDefaultIndicator 4060 a is one 4060 h.

AddressDescription 4061 a is an addition to the email address that refers to special details or that contains other unstructured information. For AddressDescription 4061 a , the Category is Element 4061 b , the Object Class is Email 4061 c , the Property is Email Address Description 4061 d , the Representation/Association is Text 4061 e , the Type is GDT 4061 f , and the Type Name is Description 4061 g . The Cardinality between the GDT Address 4000 a and AddressDescription 4061 a is unbounded 4061 h.

AddressUsageDenialIndicator 4062 a indicates whether the e-mail address may be used or not. If this indicator is set to “true,” this means that, in accordance with the legal requirements of the respective country, the email address may not be used. There are exceptions, for example, responses to email enquiries may still be permitted. Furthermore, email addresses may be saved so that emails sent by business partners and the like can still be identified, even if the indicator is set. For AddressUsageDenialIndicator 4062 a , the Category is Element 4062 b , the Object Class is Email 4062 c , the Property is Email address Usage Denial Indicator 4062 d , the Representation/Association is Indicator 4062 e , the Type is CCT 4062 f , and the Type Name is Indicator 4062 g . The Cardinality between the GDT Address 4000 a and AddressUsageDenialIndicator 4062 a is one 4062 h.

Web 4063 a contains a Web address in each instance. For Web 4063 a , the Category is Element 4063 b , the Object Class is Communication 4063 c , the Property is Web 4063 d , and the Representation/Association is Details 4063 e . The Cardinality between the GDT Address 4000 a and Web 4063 a is unbounded 4063 f . Web 4063 a is also comprised of Address 4064 a , AddressDefaultIndicator 4065 a , and AddressDescription 4066 a.

Address 4064 a specifies the URI of a Web site. The length is long enough to accommodate a generated URI. For Address 4064 a , the Category is Element 4064 b , the Object Class is Web 4064 c , the Property is Web Address 4064 d , the Representation/Association is Address 4064 e , the Type is GDT 4064 f , and the Type Name is Web Address 4064 g . The Cardinality between the GDT Address 4000 a and Address 4064 a is one 4064 h.

AddressDefaultIndicator 4065 a indicates whether a Web address is the default Web address for this address. There may be a default Web address, provided the address contains a Web address. For AddressDefaultIndicator 4065 a , the Category is Element 4065 b , the Object Class is Web 4065 c , the Property is Address Default Indicator 4065 d , the Representation/Association is Indicator 4065 e , the Type is CCT 4065 f , and the Type Name is Indicator 4065 g . The Cardinality between the GDT Address 4000 a and AddressDefaultIndicator 4065 a is one 4065 h.

Address Description 4066 a is an addition to the Web address that refers to special details or that contains other unstructured information. For AddressDescription 4066 a , the Category is Element 4066 b , the Object Class is Web 4066 c , the Property is Address Description 4066 d , the Representation/Association is Text 4066 e , the Type is GDT 4066 f , and the Type Name is Description 4066 g . The Cardinality between the GDT Address 4000 a and Address Description 4066 a is unbounded 4066 h.

An example of GDT Address 4000 a is:

<Address>

<OrganisationFormattedName>Systems, Applications

and Products</OrganisationFormattedName>

<OrganisationFormattedName>in Data

Processing</OrganisationFormattedName>

<PersonName>

<FormattedName>Mr. Paul John Tester</FormattedName>

<LegalName>Paul John Tester</LegalName>

<GivenName></GivenName>

<PreferredGivenName>Paul</PreferredGivenName>

<MiddleName>John</MiddleName>

<Family>

<FamilyName>Tester</FamilyName>

<PrimaryIndicator>true</PrimaryIndicator>

<FamilyNamePrefix></FamilyNamePrefix>

</Family>

<Affix>

<AffixName>Mr.</AffixName>

<AffixCode>FormOfAddress</AffixCode>

</Affix>

</PersonName>

<FunctionalTitleName>Sales Manager</FunctionalTitleName>

<DepartmentName>Sales Department</DepartmentName>

<Office>

<BuildingID>WDF01</BuildingID>

<FloorID>2</FloorID>

<RoomID>G2.01</RoomID>

<InhouseMailID>SCM IBD 2</ InhouseMailID >

<CorrespondenceShortName>TeP</CorrespondenceShortName>

</Office>

<PhysicalAddress>

<CountryCode>MX</CountryCode>

<RegionCode>DIF</RegionCode>

<StreetPostalCode>01210</StreetPostalCode>

<CityName>Mexico</CityName>

<DistrictName> Santa Fé</DistrictName>

<StreetName>Piso Col Pena Blanca</StreetName>

<StreetPrefixName>Edificio Plaza Reforma Santy

Fé</StreetPrefixName>

<StreetPrefixName>Prologacion Paseo de la

Reforma</StreetPrefixName>

<HouseID>No 600-2°</HouseID>

</PhysicalAddress>

<TaxJurisdictionCode listID=“,” listVersionID=“,” listAgencyID =“,”

listAgencySchemeID=

“,”listAgencySchemeAgencyID=““>123456789101112

</TaxJurisdictionCode>

<TimeZoneDifferenceValue>+08:00</TimeZoneDifferenceValue>

<GeoCoordinates>

<LatitudeMeasure

unitCode=“DD”>40.23232300000</LatitudeMeasure>

<LongitudeMeasure

unitCode=“DD”>123.12121200000</LongitudeMeasure>

</GeoCoordinates>

<Communication>

<Telephone>

<TelephoneNumber>

<AreaID>6227</AreaID>

<SubscriberID>7</SubscriberID>

<ExtensionID>47474</ExtensionID>

<CountryCode>DE</ CountryCode>

</TelephoneNumber>

<TelephoneNumberDefaultIndicator>1

</TelephoneNumberDefaultIndicator>

<Description></ Description>

<UsageDenialIndicator>0</UsageDenialIndicator>

</Telephone>

<MobilePhone>

<MobilePhoneNumber>

<AreaID>170</AreaID>

<SubscriberID>1234567</SubscriberID>

<ExtensionID></ExtensionID>

<CountryCode>DE</ CountryCode>

</MobilePhoneNumber>

<MobilePhoneNumberDefaultIndicator>1

</MobilePhoneNumberDefaultIndicator>

<Description></Description>

<UsageDenialIndicator>0</UsageDenialIndicator>

</MobilePhone>

<Facsimile>

<FacsimileNumber>

<AreaID>6227</AreaID>

<SubscriberID>78</SubscriberID>

<ExtensionID>99999</ExtensionID>

<CountryCode>DE</ CountryCode >

</FacsimileNumber>

<FacsimileNumberDefaultIndicator>1

</FacsimileNumberDefaultIndicator>

<Description>Secretary</Description>

<UsageDenialIndicator>0</UsageDenialIndicator>

</Facsimile>

<EmailAddress>paul.tester@sap.com</EmailAddress>

<EmailAddressDefaultIndicator>1</EmailAddressDefaultIndicator>

<Description></Description>

<UsageDenialIndicator>0</UsageDenialIndicator>

<Web>

<WebAddress>www.sap.com</WebAddress>

<WebAddressDefaultIndicator>1</WebAddressDefaultIndicator>

<Description>Official information</Description>

</Web>

</Communication>

</Address>.

This example address produces the following result, which can be printed out for a label:

Systems, Applications and Products

in Data Processing

Mr. Paul John Tester

Sales Manager

Edificio Plaza Reforma Santa Fé

Prolongacion Paseo de la Reforma

No 600-2° Piso Col Pena Blanca

Santa Fé 01210

Mexico, DIF.

Note that some fields, such as TaxJurisdictionCode and TimeZoneValueDifference, may not be used even if they have been completed. If BuyerParty is an organization then PersonName may be empty. If BuyerParty is a natural person then OrganisationFormattedName may be empty.

The addresses of technical objects, which describe a physical location, are represented by an appropriate field selection, e.g., the address of the organization without OrganisationFormattedName and Communication.

(f) AdjustmentReasonCode

The GDT AdjustmentReasonCode 4100 is a coded representation for the reason for an adjustment. An example of GDT AdjustmentReasonCode 4100 is: <AdjustmentReasonCode>CANCELED_PROMOTION</AdjustmentReasonCode>.

The structure of GDT AdjustmentReasonCode 4100 is depicted in FIG. 41 .

The illustrative code is general and can be used in many contexts. The standard code list to be used in an interface depends on the particular context. In a variation, a standard code list is used. If an interface supports one of the lists or if the supported code lists are disjunctive, none of the attributes may be required for identification of the particular standard code lists.

For the use of GDTs in revisions of forecast time series, the possible code values are subsets of the “Adjustment Reason Code List” of the “EAN.UCC XML Business Message Standards, version 1.3 (July 2003).” These include CANCELED_PROMOTION, DISCONTINUED_PRODUCT, DISTRIBUTION_ISSUE, EXPANDED_PROMOTION, FORWARD_BUY, INVENTORY_POLICY_CHANGE, NEW_LOCATION, NEW_PRODUCT, NEW_PROMOTION, ORDER_POLICY_CHANGE, OVERSTOCK_CONDITION, PRICE_CHANGE, PRODUCT_CHANGEOVER, PRODUCTION_ISSUE, REDUCED_PROMOTION, REVISED_PLAN, REVISED_PROMOTION, STORE_CLOSURE, TRANSPORTATION_ISSUE and WEATHER_RELATED_EVENT. For each use of the above, the context and code list used may be documented.

(g) AllowedIndicator

A GDT AllowedIndicator 4200 indicates whether something, such as a specific procedure, operation or status, is allowed or not. An example of GDT AllowedIndicator 4200 is: <LowerCaseAllowedIndicator>true</LowerCaseAllowedIndicator>.

The structure of GDT Allowed Indicator 4200 is depicted in FIG. 42 . For the GDT Allowed Indicator 4200 , the Property is Allowed 4202 , the Representation/Association is Indicator 4204 , the Type is CCT 4206 , and the Type Name is Indicator 4208 .

The GDT AllowedIndicator 4200 can have the values true or false. True means that something is allowed while false means that something is not allowed. For each GDT AllowedIndicator 4200 , what is allowed or not allowed may be indicated precisely. This is reflected in an appropriate name prefix. For example, a NegativeValueAllowedIndicator specifies whether negative numeric values are allowed, while a LowerCaseAllowedIndicator specifies whether lower-case letters are allowed.

The GDT AllowedIndicator 4200 may be used to indicate whether a customer is allowed to submit an online purchase order in lower-case letters. In the context of an interface, the business significance of “what is allowed” may be described for the AllowedIndicator in addition to using the name prefix.

(h) Amount

A GDT Amount 4300 is an amount with the corresponding currency unit. An example of GDT Amount 4300 is: <OrderedAmount currencyCode=“EUR”>777.95</OrderedAmount>.

The structure of GDT Amount 4300 is depicted in FIG. 43 . For the GDT Amount 4300 , the Property is Amount 4302 , the Representation/Association is Amount 4304 , the Type is CCT 4306 , and the Type Name is Amount 4308 .

GDT Amount 4300 is used to represent amounts, costs, remunerations, and fees. The amount value in GDT Amount 4300 may be represented with a maximum of 22 predecimal places and 6 decimal places. Both positive and negative amounts can be used. Amount 4300 may also include the attribute currencyCode which refers to the currency unit in accordance with the ISO 4217 three-character code. A currency may be specified.

(i) AmountBalanceIndicator

A GDT AmountBalanceIndicator 4400 indicates whether an amount is a balance or not. An example of GDT AmountBalanceIndicator 4400 is: <AmountBalanceIndicator>true</AmountBalanceIndicator>.

The structure of GDT AmountBalanceIndicator 4400 is depicted in FIG. 44 . For the GDT AmountBalanceIndicator 4400 , the Property is Amount Balance 4402 , the Representation/Association is Indicator 4404 , the Type is CCT 4406 , and the Type Name Indicator is 4408 .

BalanceIndicator can have either the value true or false. True signifies that the amount specified is a balance. False signifies that the amount specified is not a balance. GDT Amount 4400 can be used to indicate whether the balance of all open receivables is transferred in a message to a party or whether the amount transferred is an individual receivable. A balance amount may also be positive or negative. In the context of an interface, the amount to which the GDT Amount 4400 refers and the business significance of the balance may be described.

(j) AspectID

A GDT AspectID 4500 is a unique identifier for an aspect. An aspect determines a selection of attributes relevant for the aspect for a predefined object type. An example of GDT AspectID 4500 is: <AspectID>DETAIL</AspectID>.

The structure of GDT AspectID 4500 is depicted in FIG. 45 . For the GDT AspectID 4500 , the Object Class is Aspect 4502 , the Property is Identification 4504 , the Representation/Association is Identifier 4506 , the Type is CCT 4508 , the Type Name is Identifier 4510 and the length is from one to forty 4512 .

In one variation, when a catalog is published, a GDT AspectID 4500 can be used as the CatalogueItemAspectID to specify which properties (and their values) are to be displayed in the view for a catalog item. For example, in a product catalog, the “LIST” aspect contains those product properties that are required to select a product from a list quickly. The “DETAIL” aspect contains all the properties, while the “COMPARISON” aspect contains those that are useful for comparing the details of two products.

A distinction should also be made between an aspect and a “view.” A view of a predefined object is a restriction of the object's attributes. An aspect is a semantic criterion that is used to decide which attributes belong to a particular object view. When a given aspect is applied to various object types, the result is a view. For this reason, an aspect usually has many different views.

(k) Attachment

A CCT Attachment 4600 is an arbitrary document type that is related to either the whole message or just a particular part. An example of CCT Attachment 4600 is: <Attachment id=“sampleAttachment.xml”>Some Attachment</Attachment>.

The structure of CCT Attachment 4600 is depicted in FIG. 46 . The CCT Attachment 4600 includes attributes id 4612 and filename 4632 . For the CCT Attachment 4600 , the Property is Attachment 4602 , the Representation/Association is Binary Object 4604 , the Type is xsd 4606 , the Type Name is normalizedString 4608 . The CCT Attachment 4600 is Title 4610 .

Attribute id 4612 uniquely identifies the binary content within the message that corresponds to the SOAP or ebXML messaging protocols. For the CCT Id 4612 , the Category is Attribute 4614 , the Object Class is Attachment 4616 , the Property is Identification 4618 , the Representation/Association is Identifier 4620 , the Type is xsd 4622 , the Type Name is string 4624 , the Length is from one to thirty five 4626 , the Cardinality is one 4628 . The CCT Id 4612 may be unique as used for references using the manifest 4630 .

Attribute filename 4632 contains the relevant name or file name of the binary content. The structure of CCT Filename 4632 is depicted in FIG. 46 . For the CCT Filename 4632 , the Category is Attribute 4634 , the Object Class is Attachment 4636 , the Property is Filename 4638 , the Representation/Association is Text 4640 , the Type is xsd 4642 , the Type Name is String 4644 , the length is up to seventy 4646 , and the Cardinality is zero or one 4648 .

The element value of CCT BinaryObject 4600 is based on the XML-scheme-specific built-in data type xsd: normalizedString and can be used to represent an intelligible title or name of the binary object.

The attachment may be sent in the same message in the form of a MIME attachment. The technical referencing is done using the manifest of the respective message protocol (SOAP or ebXML messaging). The value from the “id” attribute is used as the referencing code. Every attachment may have this attribute and the identifiers may be unique in the same document instance.

Attachments are similar to the attachments in electronic message transfer (for example, STMP). The attachments may be documents that can be read by humans, such as word-processing documents, spreadsheet documents, presentation documents, and the like. These documents can be in many different formats (e.g., doc, pdf, ppt, xls, and the like.).

The binary data streams of Attachment should not be stored on a Web server as a file. The global data type “WebAddress” is available for this purpose.

(l) AttachmentWebAddress

A CDT AttachmentWebAddress 4700 is a Web address for a document of any type that is related to the transmitted message or part of the message, but is not itself transmitted as part of the message. An example of CDT AttachmentWebAddress 4700 is: <AttachmentWebAddress>www.abc.com/Attachments/HelloWorld.txt</AttachmentWebAddress>.

The structure of CDT AttachmentWebAddress 4700 is depicted in FIG. 47 . For the CDT Attachment Web Address 4700 , the Object Class Qualification is Attachment 4702 , the Object Class is Web Address 4704 , the Property is Address 4706 , the Representation/Association is Electronic Address 4708 , the Type is GDT 4710 , and the Type Name is Web Address 4712 .

The specification of an CDT AttachmentWebAddress 4700 may support http and https URI schemes. The CDT AttachmentWebAddress 4700 may also be used to transmit a link to an attachment, instead of transmitting the attachment itself. The recipient can use the transmitted link to access the attachment.

When using an CDT AttachmentWebAddress 4700 in an interface or GDT, how the link is to be interpreted may be described. For example, as a simple link to enable the user to display the attachment on the interface, as a request to the recipient system to load the attachment from the specified address as soon as possible, whether there are restrictions on how long the attachment is available at the specified URL, or whether and by whom the attachment can be changed.

(m) BatchID

A GDT BatchID 4800 is a unique identifier for one batch in the context of a material number. Batches are non-reproducible, homogenous subsets of a product, whose characteristics lie within the batch characteristics defined for the product. An example of GDT BatchID 4800 is: <BatchID>CH20021015</BatchID>.

The structure of GDT BatchID 4800 is depicted in FIG. 48 . For the GDT BatchID 4800 , the Category is Complex Type 4802 , the Object Class is Batch 4804 , the Property is Identification 4806 , the Representation/Association is Identifier 4808 , the Type is CCT 4810 , the Data Type is Identifier 4812 , the Length is from one to ten 4814 .

The GDT BatchID 4800 may comprise letters, numbers, and displayable special characters, with the possible exception of “*,” “&,” and “,”. The identifier may be uppercase and the GDT BatchID 4800 may not begin with blank characters or contain consecutive blank characters. The GDT BatchID 4800 value range includes combinations of the permitted characters up to a maximum length of 10 characters.

SchemeID identifies an identification scheme. The identification scheme represents the context that is used to identify an object. SchemeID may be unique within the agency that manages this identification scheme. The structure of GDT schemeID 4816 is depicted in FIG. 48 . For the GDT schemeID 4816 , the Category is Attribute 4818 , the Object Class is Identification Scheme 4820 , the Property is Identification 4822 , the Representation/Association is Identifier 4824 , the Type is xsd 3126 , the Data Type is Token 4828 , the Cardinality is zero or one 4830 . The GDT schemeID 4816 may be Optional 4832 .

SchemeVersionID identifies the version of an identification scheme. The structure of GDT schemeVersionID 4834 is depicted in FIG. 48 . For the GDT schemeVersionID 4834 , the Category is Attribute 4836 , the Object Class is Identification Scheme 4838 , the Property is Version 4840 , the Representation/Association is Identifier 4842 , the Type is xsd 4844 , the Data Type is Token 4846 , and the Cardinality is zero or one 4848 . The GDT schemeVersionID 4834 may be optional 4850 .

SchemeAgencyID identifies the agency that manages an identification scheme. The agencies from DE 3055 may be used as the default, but the roles defined in DE 3055 may not be used. GDT BatchID 4800 may be unique within the identification scheme that is managed by schemeAgencyID. For the GDT schemeAgencyID 4852 , the Category is Attribute 4854 , the Object Class is IdentificationSchemeAgency 4856 , the Property is Identification 4858 , the Representation/Association is Identifier 4860 , the Type is xsd 4862 , the Data Type is Token 4864 , and the Cardinality is zero or one 4866 . The GDT schemeAgencyID 4852 may be optional 4868 .

SchemeAgencySchemeID identifies the identification scheme that represents the context for agency identification. For the GDT schemeAgencySchemeID 4870 , the Category is Attribute 4872 , the Object Class is IdentificationSchemeAgency 4874 , the Property is Scheme 4876 , the Representation/Association is Identifier 4878 , the Type is xsd 4880 , the Data Type is Token 4882 , and the Cardinality is zero or one 4884 . The GDT schemeAgencySchemeID 4870 may be optional 4886 .

SchemeAgencySchemeAgencyID identifies the agency that manages the SchemeAgencySchemeID. This attribute may contain values from DE 3055 (excluding roles). For the GDT schemeAgencySchemeAgencyID 4888 , the Category is Attribute 4890 , the Object Class is IdentificationSchemeAgency 4892 , the Property is SchemeAgency 4894 , the Representation/Association is Identifier 4896 , the Type is xsd 4898 , the Data Type is Token 4899 , and the Cardinality is zero or one 4801 A. The GDT schemeAgencySchemeAgencyID 4888 may be optional 4802 A.

The GDT BatchID 4800 may be used to identify batches. Specifying attributes may be optional. By default, the system may assume that the batch identified by the GDT BatchID 4800 is a manufacturer batch and therefore no attributes are required.

(n) BiddingConditionCode

The GDT BiddingConditionCode 4900 is a coded representation of the bidding conditions for a bid invitation property. An example of GDT BiddingConditionCode 4900 is: <QuoteQuantityBiddingConditionCode>01</QuoteQuantityBiddingConditionCode>.

The structure of GDT Bidding Condition Code 4900 is depicted in FIG. 49 . For the GDT Bidding Condition Code 4900 , the Object Class is Bidding 4902 , the Property is Condition 4904 , the Representation/Association is Code 4906 , the Type is CCT 4908 , the Type Name is Code 4910 , and the Length is two 4912 .

The GDT BiddingConditionCode 4900 may have the values 01 through 04. 01 means that a bid is mandatory for a bid invitation property, and the property valuation may not be changed. 02 means a bid is mandatory for a bid invitation property, and the property valuation can be changed. 03 means a bid may be optional for a bid invitation property, and the property valuation cannot be changed. 04 means a bid may be optional for a bid invitation property, and the property valuation can be changed

Illustrative bid invitation properties for which bidding conditions can be specified may include quantity, price, and terms of delivery. When the GDT BiddingConditionCode 4900 is applied to a bid invitation property, it is identified in the prefix, e.g., QuoteQuantityBiddingConditionCode. A default procedure should be specified for each usage of a GDT BiddingConditionCode 4900 .

The GDT BiddingConditionCode 4900 may be a proprietary code list with fixed predefined values. Changes to the permitted values may involve changes to the interface.

(o) BusinessDocumentMessageHeader

A GDT BusinessDocumentMessageHeader 5000 comprises business information from the perspective of the sender application for identifying a business document within a message (if applicable, with a reference to a previous instance of a business document within a previous message), information about the sender, and any information about the receiver. An example of GDT BusinessDocumentMessageHeader 5000 is:

<PurchaseOrderRequest>

<MessageHeader>

<ID schemeID=“INVOIC”>00000000123456</ID>

<ReferenceID

schemeID=“ORDER”>00000000123455</ReferenceID>

<CreationDateTime>2003-10-21T12:21Z+01:00</ID>

<SenderParty>

<StandardID schemeAgencyID=“016”>4711</StandardID>

<ContactPerson>

<InternalID schemeID=“PartyID”

schemeAgencyID=“MPL_002”>820</InternalID>

<Address> . . .</Address>

</ContactPerson>

</SenderParty>

<RecipientParty>

<InternalID schemeID=“PartyID”

schemeAgencyID=“BPL_300”>747</InternalID>

<ContactPerson>

<InternalID schemeID=“PartyID”

schemeAgencyID=“BPL_300”>737</InternalID>

<Address> . . .</Address>

</ContactPerson>

</RecipientParty>

</MessageHeader>

. . .

</PurchaseOrderRequest>.

The structure of GDT Business Document Message Header 5000 is depicted in FIG. 50 . The GDT Business Document Message Header 5000 includes elements ID 5010 , ReferenceID 5028 , CreationDateTime 5046 , SenderParty 5062 , and RecipientParty 5078 . For the GDT Business Document Message Header 5000 , the Object Class is Business Document Message 5002 , the Property is Header 5004 , the Representation/Association is Details 5006 , the Type is GDT 5008 .

ID 5010 is the identifier for the instance of the business document within a (technical) message that is generated by the business application level at the sender. For the ID 5010 , the Category is Element 5012 , the Object Class is Business Document Message 5014 , the Property is Identification 5016 , the Representation/Association is Identifier 5018 , the Type is GDT 5020 , the Type Name is Business Document Message ID 5022 , the Length is from one to thirty-five 5024 , and Cardinality is zero or one 5026 .

ReferenceID 5028 is the identifier of another instance of a business document in another (technical) message that the BusinessDocument references (a BusinessDocument can link to another BusinessDocumentMessage to represent a business interrelation or a dependency). For the Reference ID 5028 , the Category is Element 5030 , the Object Class is Business Document Message 5032 , the Property is Reference Identification 5034 , the Representation/Association is Identifier 5036 , the Type is GDT 5038 , the Type Name is Business Document Message ID 5040 , the Length is from one to thirty-five 5042 , and the Cardinality is zero or one 5044 .

CreationDateTime 5046 is a date and time stamp (to the second) for when a message is created for the business document within the business application. For the GDT Creation Date Time 5046 , the Category is Element 5048 , the Object Class is Business Document Message 5050 , the Property is Creation Date Time 5052 , the Representation/Association is Date Time 5054 , the Type is GDT 5056 , the Type Name is Date Time 5058 , the Cardinality is one 5060 .

SenderParty 5062 is the party that creates and sends the BusinessDocument at business application level. SenderParty contains a unique sender identification. The identifiers contained in SenderParty can also be used for internal forwarding at application level. The contact person in it contains the necessary direct contact information in case there are problems or errors during processing of the respective BusinessDocument. For the GDT Sender Party 5062 , the Category is Element 5064 , the Object Class is Business Document Message 5066 , the Property is Sender 5068 , the Representation/Association is Party 5070 , the Type is GDT 5072 , the Type Name is Business Document Message Header Party 5074 , the Cardinality is zero or one 5076 .

RecipientParty 5078 is the party that receives and processes the BusinessDocument at business application level. RecipientParty may contain a unique receiver identification. The identifiers contained in RecipientParty can also be used for internal forwarding at application level. The contact person in it contains the contact information in case there are problems or errors during processing of the respective BusinessDocument. The structure of GDT Recipient Party 5078 is depicted in FIG. 50 . For the GDT Recipient Party 5078 , the Category is Element 5080 , the Object Class is Business Document Message 5082 , the Property is Recipient 5084 , the Representation/Association is Party 5086 , the Type is GDT 5088 , the Type Name is Business Document Message Header Party 5090 , the Cardinality is from zero to n 5092 .

BusinessDocuments used for B2B scenarios may use the GDT BusinessDocumentMessageHeader 5000 . If required, GDT BusinessDocumentMessageHeader 5000 can also be used in BusinessDocuments intended for A2A scenarios.

GDT BusinessDocumentMessageHeader 5000 may be used for numerous purposes. For example, GDT BusinessDocumentMessageHeader 5000 may be used for forwarding to the relevant position or target person within a business application, for tracing and monitoring of a BusinessDocument and its processing status at business application level, and for managing and monitoring business processes.

GDT BusinessDocumentMessageHeader 5000 may also be used for administration and error handling. The unique identification can be used for referencing and in the case of errors at business application level, the contact person in SenderParty or RecipientParty can be contacted directly. The name, telephone number, e-mail address, fax number, and the like. can be transmitted by the GDT BusinessDocumentMessageHeader 5000 for this purpose.

GDT BusinessDocumentMessageHeader 5000 may also be used for converting general information to other standards, such as IDoc, UN/CEFACT, ANSI X.12, ODETTE, TRADACOMMS, xCBL, OAG BODs, and RosettaNet-PIPs. These are standards that represent reference data for the business application level according to predefined conventions. In a variation, this may be guaranteed if the general header information of a BusinessDocument is identical to the envelope or header information of the respective default message.

The ReferenceID is used to represent references that originate from the succession of BusinessDocuments in the BusinessDocument choreography. This may include query/response or request/confirmation messages. The respective interface document may identify the previous BusinessDocument to which the ReferenceID refers, i.e., what the reference specified by the BusinessDocument reference means.

Comparing GDT BusinessDocumentMessageHeader 5000 to the header information from the message transfer protocols such as “Reliable Messaging,” “OASIS ebXML MSG,” “OASIS ebXML CPP/CPA,” and “Rosetta Net RNIF 2.0,” demonstrates that the GDT BusinessDocumentMessageHeader 5000 may contain redundant information compared to these technical transfer protocols. However, the GDT BusinessDocumentMessageHeader 5000 may be used at business application level instead of at a technical level. The information in this case is information that can be sent, received, and processed at this level.

GDT BusinessDocumentMessageHeader 5000 may be based on UN/CEFACT Standard BusinessDocumentMessage Header Technical Specification—Working Draft—Revision 2.2.5” dated 26 Nov. 2003. The ID (BusinessDocumentMessageID) of the GDT BusinessDocumentMessageHeader 5000 may be distinguishable from the technical Messaged (the XI message). Specifically the BusinessDocumentMessageID is issued by the business application and is stable over the entire lifetime of the BusinessDocument. It also remains unchanged even when the message is sent via multiple, successive middleware systems. The technical Messaged is issued at the level of the technical middleware system and generally changes each time the BusinessDocument is resent or forwarded by a middleware system and when the BusinessDocument is split into multiple technical messages by a middleware system.

(p) BusinessDocumentMessageHeaderParty

A GDT BusinessDocumentMessageHeaderParty 5100 is information about a party that is responsible for sending or receiving a BusinessDocument at a business application level. GDT BusinessDocumentMessageHeaderParty 5100 contains the necessary general business information about an involved sender or receiver party. A party is typically a natural person, organization, or business partner group in which a company has a business or intra-enterprise interest. This could be a person, organization, or group within or outside of the company. An example of GDT BusinessDocumentMessageHeaderParty 5100 is:

<PurchaseOrderRequest>

<MessageHeader>

<SenderParty>

<StandardID schemeAgencyID=“016”>4711</StandardID>

<ContactPerson>

<InternalID schemeID=“PartyID”

schemeAgencyID=“MPL_002”>820</InternalID>

<Address> . . .</Address>

</ContactPerson>

</SenderParty>

<RecipientParty>

<InternalID schemeID=“PartyID”

schemeAgencyID=“BPL_300”>747</InternalID>

<ContactPerson>

<InternalID schemeID=“PartyID”

schemeAgencyID=“BPL_300”>737</InternalID>

<Address> . . .</Address>

</ContactPerson>

</RecipientParty>

. . .

</MessageHeader>

. . .

</PurchaseOrderRequest>.

In the above example, for SenderParty, schemeAgencyID=“016” can correspond to Dun & Bradstreet according to the code list DE 3055 . For RecipientParty: schemeID=“PartyID” specifies that the scheme “PartyID” was used to identify the party. schemeAgencyID=“BPL — 300” specifies that the scheme was assigned by the SAP CMDM system “BPL — 300.”

The structure of GDT Business Document Message Header Party 5100 is depicted in FIG. 51 . For the GDT Business Document Message Header Party 5100 , the Object Class is Business Document Message Header Party 5102 and the Property is Details 5104 .

InternalID 5106 refers to the proprietary identifier used when SenderParty or RecipientParty use common master data (Extended Enterprise) or when they are in alignment with regard to the semantics and use of InternalID. For the GDT Internal ID 5106 , the Category is Element 5108 , the Object Class is Business Document Message Header Party 5110 , the Property is Internal Identification 5112 , the Representation/Association is Identifier 5114 , the Type is GDT 5116 , the Type Name is Party Internal ID 5118 , and the Cardinality is zero or one 5120 .

StandardID 5122 refers to the standardized identifier for SenderParty or RecipientParty of the organization based on the code list DE 3055 . For the GDT Standard ID 5122 , the Category is Element 5124 , the Object Class is Business Document Message Header Party 5126 , the Property is Standard Identification 5128 , the Representation/Association is Identifier 5130 , the Type is GDT 5132 , the Type Name is Party Standard ID 5134 , and the Cardinality is from zero to n 5136 .

ContactPerson refers to the contact person of the party. For the GDT Contact Person 5138 , the Category is Element 5140 , the Object Class is Business Document Message Header Party 5142 , the Property is Contact Person 5144 , the Representation/Association is Contact Person 5146 , the Type is GDT 5148 , the Type Name is Contact Person 5150 , and the Cardinality is zero or one 5152 .

The GDT BusinessDocumentMessageHeaderParty 5100 may be used in the BusinessDocumentMessageHeader of a BusinessDocument. This GDT is meant for defining the SenderParty or RecipientParty. The different IDs of a GDT BusinessDocumentMessageHeaderParty 5100 may identify the same party.

A party may be identified using an InternalID or Standard ID. InternalID is when SenderParty and RecipientParty use common master data or are in alignment with regard to the semantics and use of InternalID. StandardID is when SenderParty and RecipientParty can manage standardized identifiers. Of all of the IDs available to the SenderParty, generally those IDs the RecipientParty is expected to understand are used in a BusinessDocument. Either company-internal ID or a standardized ID can be used for identification.

GDT BusinessDocumentMessageHeaderParty 5100 can be used for the details and identification of the sender or recipient of a BusinessDocument. Furthermore, additional information about the contact person, including address, can be defined, which makes it possible to contact this person directly should any problems or errors occur when validating or processing the inbound BusinessDocument.

(q) BusinessDocumentMessageID

A GDT BusinessDocumentMessageID 5200 may be a unique identifier of a business document in a message that is issued by the sender business application. An example of GDT BusinessDocumentMessageID 5200 is:

<PurchaseOrderRequest>

<MessageHeader>

<ID

schemeID=“ORDER”

schemeAgencyID=“124224”

schemeAgencySchemeAgencyID=“12232344”>

00000000000001

</ID>

. . .

</MessageHeader>

. . .

</PurchaseOrderRequest>.

The structure of GDT Business Document Message ID 5200 is depicted in FIG. 52 . For the GDT Business Document Message ID 5200 , the Category is Complex Type 5202 , the Object Class is Business Document Message 5204 , the Property is Identification 5206 , the Representation/Association is Identifier 5208 , the Type is CCT 5210 , the Type Name is Identifier 5212 , the Length is from one to thirty-five 5214 . The GDT Business Document Message ID 5200 may be a restricted GDT.

SchemeID 5218 identifies an identification scheme. These identification schemes may be provided by a code list, such as the SAP MessageTypes. The “schemeID” attribute is not required if the GDT BusinessDocumentMessageID 5200 is unique within a schemeAgencyID. For the GDT Scheme ID 5218 , the Category is Attribute 5220 , the Object Class is Identification Scheme 5222 , the Property is Identification 5224 , the Representation/Association is Identifier 5226 , the Type is xsd 5228 , the Type Name is Token 5230 , the Length is from one to sixty 5232 , and the Cardinality is zero or one 5234 .

SchemeAgencyID 5236 may be covered by the agency ID of the sender. If this agency manages multiple business systems, the schemeAgencyID contains the unique identification of the respective business system from which the BusinessDocument was sent. For the GDT Scheme Agency ID 5236 , the Category is Attribute 5238 , the Object Class is Identification Scheme Agency 5240 , the Property is Identification 5242 , the Representation/Association is Identifier 5244 , the Type is xsd 5246 , the Type Name is Token 5248 , and the Length is from one to sixty 5250 . The Cardinality between the GDT BusinessDocumentMessageID 5200 and SchemeAgencyID is zero or one 5252 .

SchemeAgencySchemeAgencyID contains the unique identification of the agency that manages the schemeAgencyID. This attribute may contain values from DE 3055 (excluding roles). This attribute is not required if this information comes unequivocally from the sender.

The format of GDT BusinessDocumentMessageID 5200 identification is a sequential number comprising a maximum of 35 characters. The number may be positive. This representation complies with the UN/EDIFACT conventions (see DE 0340 (Interactive Message Reference Number)).

The GDT BusinessDocumentMessageID 5200 is a unique identification for at least the entire lifetime of a BusinessDocument. The identification is generated by the respective business application of the creator and, in a variation, may not be created or interpreted by the technical message transfer systems.

The technical MessageID depends on the respective technical transfer protocol and may not be associated with the GDT BusinessDocumentMessageID 5200 . When a technical message is sent, the BusinessDocument is the payload in the message. The MessageID can change as a result of the forwarding mechanisms of the respective middleware systems or the different transfer protocols used.

In the inbound direction, mapping can be performed to the in-house message code. In the outbound direction, there are various scenarios. If a Sender is known because it is given by SenderParty, schemeID 5202 identifies the message type. If a Sender is unknown because it is not given by SenderParty and Identification of business level at the sender is standardized, then schemeID 5202 identifies the message type, schemeAgencyID 5204 identifies the standardized ID for the agency that generates the MessageID, and schemeAgencySchemeAgencyID 5206 identifies the agency from DE 3055 that manages the standardized ID schemeAgencyId. If a Sender is unknown because it is not given by SenderParty and identification of business level at the sender is proprietary, then schemeID 5202 identifies the message type, schemeAgencyID 5204 identifies the proprietary ID for the agency that generates the MessageID, and schemeAgencySchemeAgencyID 5206 identifies ‘ZZZ’ which is mutually defined from DE 3055 .

If a Sender has multiple business systems that are unique within an agency (for example: System Landscape Directory), then schemeID 5202 identifies the message type and schemeAgencyID 5204 identifies the unique ID of the business system that may be unique within an agency. In this scenario, uniqueness is ensured by the sender and the Sender is not required in internal communication.

(r) BusinessTransactionBlockedIndicator

A GDT BusinessTransactionBlockedIndicator 5300 indicates whether or not the execution of a business transaction is blocked. An example of GDT BusinessTransactionBlockedIndicator 5300 is: <DeliveryExecutionBlockedIndicator>true</DeliveryExecutionBlockedIndicator>.

The structure of GDT Business Transaction Blocked Indicator 5300 is depicted in FIG. 53 . For the GDT Business Transaction Blocked Indicator 5300 , the Object Class is Business Transaction 5302 , the Property is Blocked Indicator 5304 , the Representation/Association is Indicator 5306 , the Type is CCT 5308 , and the Type Name is Indicator 5310 .

GDT BusinessTransactionBlockedIndicator 5300 may have the value true or false. True indicates that the execution of a business transaction is blocked. False indicates that the execution of a business transaction is not blocked.

The GDT BusinessTransactionBlockedIndicator 5300 can be used in various environments, such as in delivery and in billing. In a delivery environment, this data type is used by a requesting application (e.g., Sales) to send a delivery request to Supply Chain Execution (e.g., for planning purposes) at an early stage, but, at the same time, to inform Supply Chain Execution that the delivery should not be executed yet since several points still have to be clarified with the customer, necessary papers are missing, or the customer's credit limit has been exceeded or has not yet been checked.

In a billing environment, this data type is used by a requesting application (e.g., Sales) to set up a billing due list in billing but, at the same time, to specify that billing may not yet be executed. It is possible that the requesting application first executes a release procedure, that the customer-specific prices have not yet been determined, that certain necessary documents have not yet been received (letter of credit procedure), or that the customer's credit limit has been exceeded.

(s) CompletedIndicator

A GDT CompletedIndicator 5400 indicates whether an object is completed in a business sense or not. GDT CompletedIndicator 5400 may relate to business translations (for example, invoice creation, delivery, sourcing) or to objects that have the character of a transaction (for example, product catalog transfer in multiple steps). An example of GDT CompletedIndicator 5400 is: <CompletedIndicator>false</CompletedIndicator>.

The structure of GDT CompletedIndicator 5400 is depicted in FIG. 54 . For GDT CompletedIndicator 5400 , the Property is Completed Indicator 5402 , the Representation/Association is Indicator 5404 , the Type is CCT 5406 , and the Type Name is Indicator 5408 .

The GDT CompletedIndicator 5400 can have the values true or false. True indicates that an object is completed. False indicates that an object is not completed.

The GDT CompletedIndicator 5400 is used to indicate that the processing of an object has been completed, even if further processing steps are being run in a different context (for example, sourcing for a requirement may be completed but procurement of the requirement calls for further process steps). In various variations, for various objects a CompletedIndicator or a CancelledIndicator can be used depending on whether it is desired to emphasize that processing of the object has been completed properly (CompletedIndicator) or that the object has been canceled in the sense of an exception situation (CancelledIndicator).

From the context of the interface in which a GDT CompletedIndicator 5400 is used, the object to which the CompletedIndicator refers is described, its business significance is described, and whether a set CompletedIndicator can be undone in a follow-on message is described.

(t) BusinessTransactionDocumentGroupID

A GDT BusinessTransactionDocumentGroupID 5500 may uniquely identify a group of business documents that are to be considered as one group within a business process. An example of GDT BusinessTransactionDocumentGroupID 5500 is: <DeliveryGroupID>4711</DeliveryGroupID>.

The structure of GDT Business Transaction Document Group ID 5500 is depicted in FIG. 55 . For the GDT Business Transaction Document Group ID 5500 , the Object Class is Business Transaction Document 5502 , the Property is Group Identification 5504 , the Representation/Association is Indicator 5506 , the Type is CCT 5508 , the Type Name is Identifier 5510 , the Length is from one to ten 5512 . The GDT Business Transaction Document Group ID 5500 may be a restricted GDT.

GDT BusinessTransactionDocumentGroupID 5500 is used to identify documents that belong together to enable them to be processed together by the application. “BusinessTransactionDocument” is replaced by the description of each document in the XML instance, e.g., “PurchaseOrder” for a purchase order, “Delivery” for a delivery, and the like.

(u) BusinessTransactionDocumentID

A GDT BusinessTransactionDocumentID 5600 is a unique identifier for a document in a business transaction. An example for GDT BusinessTransactionDocumentID 5600 is: <OrderID schemeID=‘Orders’ schemeAgencyID=‘123456789’schemeAgencySchemeAgencyID=‘16’>5400000012</OrderID>which assigns the identifier 5400000012 to the OrderID having an “Orders” identification scheme, “123456789” as the agency managing the identification scheme, and 16 as the identification scheme that represents the context that is used to identify the agency.

The structure of GDT Business Transaction Document ID 5600 is depicted in FIG. 56 . For the GDT Business Transaction Document ID 5600 , the Object Class is Business Transaction Document 5602 , the Property is Identification 5604 , the Representation/Association is Identifier 5606 , the Type is CCT 5608 , the Type Name is Identifier 5610 , and the Length is from one to thirty-five 5612 . The GDT Business Transaction Document ID 5600 may be a restricted GDT.

For the GDT Scheme ID 5616 , the Category is Attribute 5618 , the Object Class is Identification Scheme 5620 , the Property is Identification 5622 , the Representation/Association is Identifier 5624 , the Type is xsd 5626 , the Type Name is Token 5628 , and the Length is from one to sixty 5630 . The Cardinality is zero or one 5632 .

For the GDT Scheme Agency ID 5634 , the Category is Attribute 5636 , the Object Class is Identification Scheme Agency 5638 , the Property is Identification 5640 , the Representation/Association is Identifier 5642 , the Type is xsd 5644 , the Type Name is Token 5646 , the Length is from one to sixty 5648 , and the Cardinality is zero or one 5650 .

For the GDT Scheme ID 5616 , the Category is Attribute 5618 , the Object Class is Identification Scheme 5620 , the Property is Identification 5622 , the Representation/Association is Identifier 5624 , the Type is xsd 5626 , the Type Name is Token 5628 , and the Length is from one to sixty 5630 . The Cardinality is zero or one 5632 .

For the GDT Scheme Agency Scheme ID 5652 , the Category is Attribute 5654 , the Object Class is Identification Scheme Agency 5656 , the Property is Scheme 5658 , the Representation/Association is Identifier 5660 , the Type is xsd 5662 , the Type Name is Token 5664 , and the Length is from one to sixty 5666 . The Cardinality is zero or one 5668 .

For the GDT Scheme Agency ID 5670 , the Category is Attribute 5672 , the Object Class is Identification Scheme Agency 5674 , the Property is Scheme Agency 5676 , the Representation/Association is Identifier 5678 , the Type is xsd 5680 , the Type Name is Token 5682 , and the Length is three 5684 . The Cardinality is zero or one 5686 .

A business process uses GDT BusinessTransactionDocumentID 5600 to uniquely identify a document, such as a purchase order or an invoice in a business transaction. A partner uses a GDT BusinessTransactionDocumentID 5600 to inform another partner of the identification of a business transaction document in an initial step, e.g., when creating data for the business transaction or sending it for the first time. The second partner can use this identifier to reference the business transaction document in the subsequent process.

In a variation, there may be no standardized IDs for transaction data. The attributes schemeID, schemeAgencyID, schemeAgencySchemeID, and schemeAgencySchemeAgencyID are used in the same way as for the CCT Identifier to define the context for which a GDT BusinessTransactionDocumentID 5600 is guaranteed to be unique.

In the XML instance, “BusinessTransactionDocument” is replaced by the description of the respective document, e.g., “PurchaseOrder” for a purchase order, “Delivery” for a delivery, and the like.

(v) BusinessTransactionDocumentItemGroupID

A GDT BusinessTransactionDocumentationGroupID 5700 uniquely identifies a group of business document items that are to be characterized as a group within a business document. An example of GDT BusinessTransactionDocumentationGroupID 5700 is: <DeliveryItemGroupID>123</DeliveryItemGroupID>.

The structure of GDT Business Transaction Document Item Group ID 5700 is depicted in FIG. 57 . For the GDT Business Transaction Document Item Group ID 5700 , the Object Class is Business Transaction Document Item 5702 , the Property is Group Identification 5704 , the Representation/Association is Identifier 5706 , the Type is CCT 5708 , the Type Name is Identifier 5710 , and the Length is three 5712 . The GDT Business Transaction Document Item Group ID 5700 may be restricted.

A freely-definable numeric sequence may be used for display purposes. In a variation, it is a 3-digit, numeric text field. Leading zeros are also displayed. However, according to the current definition in R/3 in the processing applications “order” and “delivery,” a 3-figure, numeric text field (NUMC3) having a freely-definable 3-character string using the character set {“0,” “1,” “2,” “3,” “4,” “5,” “6,” “7,” “8,” “9”} may be used. Otherwise, a corresponding mapping may be necessary, but it might not be unique due to the use of a larger number of characters. In this case, the uniqueness may have to be ensured explicitly. This requirement, however, may not be ensured explicitly per definition/data type and therefore may be documented.

The GDT BusinessTransactionDocumentationGroupID 5700 is used to indicate the items of a business document that belong together for a unique identification of this item grouping in subsequent steps. For example, delivery groups are used to check the availability of materials that may be delivered together. Items that belong to the same delivery group may be delivered at the same time. Therefore, from the point of view of the availability check, the products/materials selected in the highlighted items may be available in sufficient quantities at the same time on the requested date so that the requirement can be fulfilled.

In the XML instance, the “BusinessTransactionDocument” is replaced by the description of the respective document, e.g., “PurchaseOrder” for a purchase order, “Delivery” for a delivery, and the like.

(w) BusinessTransactionDocumentItemHierarchyRelationshipTypeCode

A CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 is a coded representation of the business type of a hierarchical relationship between items of a BusinessTransactionDocument. An example of CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 in the context of a purchase order item is: <HierarchyRelationshipTypeCode>001</HierarchyRelationshipTypeCode>.

The structure of CDT Business Transaction Document Item Hierarchy Relationship Type Code 5800 is depicted in FIG. 58 . For the CDT Business Transaction Document Item Hierarchy Relationship Type Code 5800 , the Object Class Qualification is Business Transaction Document Item Hierarchy 5802 , the Object Class is Relationship 5804 , the Property is Type Code 5806 , the Representation/Association is Code 5808 , the Type is GDT 5810 , the Type is Relationship Type Code 5812 , and the Length is three 5814 . The CDT Business Transaction Document Item Hierarchy Relationship Type Code 5800 may be restricted.

The GDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 is based on the GDT ObjectStructureRelationshipTypeCode. Elements of type BusinessTransactionDocumentItemHierarchyTypeCode can have values 001, 002, 003, or 006. 001 means that the relationship is a bill of material relationship, 002 means the relationship is a grouping relationship (one object in this relationship is part of a logical grouping to another object), 003 means the relationship is a discount in kind relationship, and 006 means the relationship is a substitution product relationship.

The CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 is used together with a ParentItemID to map item hierarchies. An item hierarchy is a tree of subordinated items, where the BusinessTransactionDocumentHierarchyRelationshipTypeCode 5800 describes the meaning of the hierarchical level of an item.

When using the CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 , which types of lower-level items are permitted in each use context and which integrity conditions apply to items in a hierarchy of a particular CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 may be explicitly defined. In particular, it may be specified how hierarchies with different BusinessTransactionDocumentItemHierarchyRelationshipTypeCodes can be combined with each other. For example: When a bill of material hierarchy and a grouping hierarchy exist for one item, and when a grouping hierarchy exists for an item.

In a variation, there may be one hierarchy for each item, that is, the same CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 is specified for lower-level items. However, there are exceptions to this rule. A purchase order can contain items that have both a bill of material hierarchy and a discount in kind hierarchy. In a variation, the CDT BusinessTransactionDocumentItemHierarchyRelationshipTypeCode 5800 may be a proprietary code list with fixed predefined values. In that case, changes to the permitted values may involve changes to the interface.

In the XML instance, “BusinessTransactionDocument” is replaced by the description of the specific business transaction document, for example “PurchaseOrder” for a purchase order, “Delivery” for a delivery, and the like.

(x) BusinessTransactionDocumentItemID

A GDT BusinessTransactionDocumentItemID 5900 is a unique identifier of an item or sub item of a document within a business transaction and is unique in the context of the business transaction. An example of BusinessTransactionDocumentItemID is: <ItemID>13</ItemID>.

The structure of GDT Business Transaction Document Item ID 5900 is depicted in FIG. 59 . For the GDT Business Transaction Document Item ID 5900 , the Object Class is Business Transaction Document Item 5902 , the Property is Identification 5904 , the Representation/Association is Identifier 5906 , the Type is CCT 5908 , the Type Name is Identifier 5910 , and the Length is from one to ten 5912 . The GDT Business Transaction Document Item ID 5900 may be restricted 5914 .

GDT BusinessTransactionDocumentItemID 5900 is a sequence of numbers with a maximum of ten characters. Leading zeros may not be significant at the recipient and may not be sent.

Business transactions, such as purchase orders or invoices, may be divided into items and sub items. GDT BusinessTransactionDocumentItemID 5900 is used in a business process to identify uniquely an item or sub item within a business transaction. A partner uses its GDT BusinessTransactionDocumentItemID 5900 to inform the other partner of its identification of the item in an initial step, for example, when creating an item or transmitting it for the first time. The second partner can then use this identifier to reference the respective item of the document in the subsequent process.

In the XML instance, “BusinessTransactionDocument” is replaced by the description of the respective document, e.g., “PurchaseOrder” for a purchase order, “Delivery” for a delivery, and the like.

(y) BusinessTransactionDocumentItemScheduleLineID

A GDT BusinessTransactionDocumentItemScheduleLineID 6000 is a unique identifier that uses a deadline to identify the schedule line of a document item within a business transaction. An example of GDT BusinessTransactionDocumentItemScheduleLineID 6000 is: <PurchaseOrderItemScheduleLineID>0001</PurchaseOrderItemScheduleLineID>.

The structure of GDT Business Transaction Document Item Schedule Line ID 6000 is depicted in FIG. 60 . For the GDT Business Transaction Document Item Schedule Line ID 6000 , the Object Class is Business Transaction Document Item Schedule Line 6002 , the Property is Identification 6004 , the Representation/Association is Identifier 6006 , the Type is CCT 6008 , the Type Name is Identifier 6010 , the Length is from one to four 6012 . The GDT Business Transaction Document Item Schedule Line ID 6000 may be restricted 6014 .

Documents such as purchase orders, sales orders, or invoices are divided into items. Items are then further divided according to schedule lines. Each of these schedule lines specifies a deadline and relevant product quantities for this deadline.

“BusinessTransactionDocument” is replaced by the description of each document in the XML instance, e.g., “PurchaseOrder” for a purchase order, “Delivery” for a delivery, and the like.

(z) ThirdPartyIndicator

A GDT ThirdPartyIndicator 6100 indicates whether or not a document item is used in the context of a third-party deal. An example of GDT ThirdPartyIndicator 6100 in the context of a document item is: <ThirdPartyDealIndicator>true</ThirdPartyDealIndicator>.

The structure of GDT Third Party Indicator 6100 is depicted in FIG. 61 . For the GDT Third Party Indicator 6100 , the Object Class is Business Transaction Document Item 6102 , the Property is third Party Deal Indicator 6104 , the Representation/Association term is Indicator 6106 , the Type is CCT 6108 , and the Type Name is Identifier 6110 . The GDT ThirdPartyIndicator 6100 can have the values true or false. True indicates that the object is used in the context of a third-party deal. False indicates that the object is not used in the context of a third-party deal.

The GDT ThirdPartyIndicator 6100 is used to indicate that a document item is used in the context of a third-party deal. A third-party deal may be a process in which a company processes a sales order via a third party rather than fulfilling it directly itself. The context to which the BusinessTransactionDocumentItemThirdPartyDealIndicator refers may be clear from the usage of the GDT.

(aa) BusinessTransactionDocumentItemTypeCode

The GDT BusinessTransactionDocumentItemTypeCode 6200 is a coded representation of the type of an item in a document that occurs in business transactions. The document item type describes the business nature of similar document items and defines the basic features of the document items of this type. An example of GDT BusinessTransactionDocumentItemTypeCode 6200 is: <BusinessTransactionDocumentItemTypeCode>001</BusinessTransactionDocumentItemTypeCode>.

The structure of GDT Business Transaction Document Item Type Code 6200 is depicted in FIG. 62 . For the GDT Business Transaction Document Item Type Code 6200 , the Object Class is Business Transaction Document Item 6202 , the Property is Type 6204 , the Representation/Association is Code 6206 , the Type is CCT 6208 , the Type Name is Code 6210 , and the Length is three 6212 . The GDT Business Transaction Document Item Type Code 6200 may be restricted 6214 .

GDT BusinessTransactionDocumentItemTypeCode 6200 can have a value from 001 to 004. 001 identifies a purchase order item that specifies an ordered product or additional information on ordered products. This includes information on free goods, substitute products and value limits. 002 identifies an invoice item that specifies prices and taxes for a delivered product (including completed work) and, if necessary, more information on this product. 003 identifies a credit memo item that specifies refunded prices and taxes for a delivered product (including completed work) and, if necessary, more information on this product. 004 identifies a delivery cost item that specifies delivery costs incurred by the purchaser on top of the actual product costs. There may be a differentiation between shipping costs, customs duty costs, and miscellaneous costs, such as packaging and insurance.

Certain combinations of a GDT BusinessTransactionDocumentItemTypeCode 6200 and a BusinessTransactionDocumentTypeCode may be allowed. For example, if BusinessTransactionDocumentTypeCode is 001, BusinessTransactionDocumentItemTypeCode may be 001. If BusinessTransactionDocumentTypeCode is 004, BusinessTransactionDocumentItemTypeCode may be 002, 003, or 004. If BusinessTransactionDocumentTypeCode is 005, BusinessTransactionDocumentItemTypeCode may be 001.

The GDT BusinessTransactionDocumentItemTypeCode 6200 categorizes an item in a document that is sent if the concrete semantic meaning of the item or sub-item is not defined by the message itself or if semantically different items can occur in one message. In particular, there are documents in applications that contain items with different types so that it may not be enough to specify the type of the complete document. For example, in addition to a “standard” invoice item for an ordered product, an invoice can contain a delivery costs item that is to be shown separately.

In an example, in R/3, the BusinessTransactionDocumentItemTypeCode 6200 corresponds to VBTYP+POSAR in Sales or BSTYP in Purchasing or MRM_REFERENZBELEG in Invoice Verification, and the like, at a less detailed level.

(bb) BusinessTransactionDocumentLocation

A CDT BusinessTransactionDocumentLocation 6300 contains the information that is exchanged in business documents about a location relevant for business transactions. This information identifies the location and its address. The identification may be a company-internal ID, a standardized ID, or one or several partner-specific IDs. A location is a logical or a physical place. An ID for a location assigned by a party identifies in the name the role the assigning party plays in the business transaction. At present, the role descriptions are Buyer, Seller, ProductRecipient, Vendor, BillTo, and BillFrom. An example of CDT BusinessTransactionDocumentLocation 6300 is:

<InventoryChange>

. . .

<Location>

<StandardID schemeAgencyID=“016”>4711 </StandardID>

<BuyerID>9873</BuyerID>

<Address> . . .</Address>

<Location>

<InventoryChange>.

The structure of CDT Business Transaction Document Location 6300 is depicted in FIG. 63 . For the CDT Business Transaction Document Location 6300 , the Object Class is Business Transaction Document Location 6302 and the Representation/Association is Details 6304 .

For the Internal ID 6306 , the Category is Element 6308 , the Object Class is Business Transaction Document Location 6310 , the Property Qualifier is Internal 6312 , the Property is Identification 6314 , the Representation/Association is Identifier 6316 , the Type is CDT 6318 , and the Type Name is Location Internal ID 6320 . The Cardinality is zero or one 6322 .

For the Standard ID 6324 , the Category is Element 6326 , the Object Class is Business Transaction Document Location 6328 , the Property Qualifier is Standard 6330 , the Property is Identification 6332 , the Representation/Association is Identifier 6334 , the Type is CDT 6336 , and the Type Name is Location Standard ID 6338 . The Cardinality is from zero to n. 6340 .

For the Buyer ID 6342 , the Category is Element 6344 , the Object Class is Business Transaction Document Location 6346 , the Property Qualifier is Buyer 6363 , the Property is Identification 6350 , the Representation/Association is Identifier 6352 , the Type is CDT 6354 , and the Type Name is Location Party ID 6356 . The Cardinality is zero or one 6358 .

For the Seller ID 6360 , the Category is Element 6362 , the Object Class is Business Transaction Document Location 6364 , the Property Qualifier is Seller 6366 , the Property is Identification 6368 , the Representation/Association is Identifier 6370 , the Type is CDT 6372 , and the Type Name is Location Party ID 6374 . The Cardinality is zero or one 6376 .

For the Seller ID 6360 , the Category is Element 6362 , the Object Class is Business Transaction Document Location 6364 , the Property Qualifier is Seller 6366 , the Property is Identification 6368 , the Representation/Association is Identifier 6370 , the Type is CDT 6372 , and the Type Name is Location Party ID 6374 . The Cardinality is zero or one 6376 .

For the Product Recipient ID 6378 , the Category is Element 6380 , the Object Class is Business Transaction Document Location 6390 , the Property Qualifier is Product Recipient 6392 , the Property is Identification 6394 , the Representation/Association is Identifier 6396 , the Type is CDT 6398 , and the Type Name is Location Party ID 6399 . The Cardinality is zero or one 6301 A.

For the Vendor ID 6302 A, the Category is Element 6303 A, the Object Class is Business Transaction Document Location 6304 A, the Property Qualifier is Vendor 6305 A, the Property is Identification 6306 A, the Representation/Association is Identifier 6307 A, the Type is CDT 6308 A, and the Type Name is Location Party ID 6309 A. The Cardinality is zero or one 6310 A.

For the Bill To ID 6311 A, the Category is Element 6312 A, the Object Class is Business Transaction Document Location 6313 A, the Property Qualifier is Bill To 6314 A, the Property is Identification 6315 A, the Representation/Association is Identifier 6316 A, the Type is CDT 6317 A, and the Type Name is Location Party ID 6318 A. The Cardinality is zero or one 6319 A.

For the Bill From ID 6320 A, the Category is Element 6321 A, the Object Class is Business Transaction Document Location 6322 A, the Property Qualifier is Bill From 6323 A, the Property is Identification 6324 A, the Representation/Association is Identifier 6325 A, the Type is CDT 6326 A, and the Type Name is Location Party ID 6327 A. The Cardinality is zero or one 6328 A.

For the Bidder ID 6329 A, the Category is Element 6330 A, the Object Class is Business Transaction Document Location 6331 A, the Property Qualifier is Bidder 6332 A, the Property is Identification 6333 A, the Representation/Association is Identifier 6334 A, the Type is CDT 6335 A, and the Type Name is Location Party ID 6336 A. The Cardinality is zero or one 6337 A.

For the Address 6338 A, the Category is Element 6339 A, the Object Class is Business Transaction Document Location 6340 A, the Property is Address 6341 A, the Representation/Association is Address 6342 A, the Type is GDT 6343 A, and the Type Name is Address 6344 A. The Cardinality is zero or one 6345 A.

For the Note 6346 A, the Category is Element 6347 A, the Object Class is Business Transaction Document Location 6348 A, the Property is Note 6349 A, the Representation/Association is Text 6350 A, the Type is GDT 6351 A, and the Type Name is Note 6352 A. The Cardinality is zero or one 6353 A.

InternalID refers to a proprietary identifier that is used when both sender and recipient can access shared master data (extended enterprise). Standard ID refers to a standardized identifier, whose identification schemes may be managed by an agency from the DE 3055 code list. Buyer ID refers to an identifier that is used by the BuyerParty proprietarily for this location. SellerID refers to an identifier that is used by the SellerParty proprietarily for this location. ProductRecipientID refers to an identifier that is used by the ProductRecipientParty proprietarily for this location. VendorID refers to an identifier that is used by the VendorParty proprietarily for this location. BillToID refers to an identifier that is used by the BillToParty proprietarily for this location. BillFromID refers to an identifier that is used by the BillFromParty proprietarily for this location. BidderID refers to an identifier that is used by the BidderParty proprietarily for this location. Address is an address that describes the location by specifying information such as postal address, geographic coordinates, or any other information that specifies a location. Note refers to an additional information such as direction.

When defining addresses, organization addresses may be supported. The different IDs of a CDT BusinessTransactionDocumentLocation 6300 identify the same location. A location may be identified by the InternalID when sender and recipient can access shared master data, by the StandardID when sender and recipient can manage standardized identifiers, or by the PartyIDs: when sender and recipient are interested in the PartyIDs assigned by the parties involved. From all of the IDs available to the sender, the IDs that the recipient is expected to understand may be used.

(cc) BusinessTransactionDocumentParty

A CDT BusinessTransactionDocumentParty 6400 contains the information that is exchanged—in accordance with common business understanding—in business documents about a party involved in business transactions. This information is used to identify the party and the party's address, as well as the party's contact person and the contact person's address. This identification can take place using an internal ID, a standardized ID, or IDs assigned by the parties involved. A party is a natural person, organization, or business partner group in which a company has a business or intra-enterprise interest. This could be a person, organization, or group within or outside of the company. An ID assigned by a party identifies in the name the role the assigning party plays in the business transaction. At present, the roles are Buyer, Seller, ProductRecipient, Vendor, BillTo, BillFrom and Bidder. An example of CDT BusinessTransactionDocumentParty 6400 is:

<PurchaseOrder>

. . .

<BuyerParty>

<StandardID schemeAgencyID=“016”>4711</StandardID>

<BuyerID>9873</BuyerID>

<SellerID>487847</SellerID>

<Address> . . .</Address>

<ContactPerson>

<BuyerID>9874</BuyerID>

<SellerID>487848</SellerID>

<Address> . . .</Address>

</ContactPerson>

</BuyerParty>

</PurchaseOrder>.

In this example, schemeAgencyID=“016” corresponds to Dun&Bradstreet according to code list D 3055 that means that the DUNS number is assigned by Dun&Bradstreet. The following is a second example of BusinessTransactionDocumentParty:

In this example, schemeID=“PartyID” indicates that the scheme “PartyID” was used to identify the party and schemeAgencyID=“BPL — 300” indicates that the scheme was assigned by the SAP CMDM system “BPL — 300.”

The examples above show the XML instance of the GDT BusinessTransactionDocumentParty within a purchase order for different identification types (standard ID, party IDs, internal ID). In this scenario, the party assumes the role of Buyer.

The structure of CDT Business Transaction Document Party 6400 is depicted in FIG. 64 . For the CDT Business Transaction Document Party 6400 , the Category is Element 6408 , the Object Class is Business Transaction Document Party 6402 , and the Representation/Association is Details 6404 .

For the Internal ID 6406 , the Category is Element 6408 , the Object Class is Business Transaction Document Party 6470 , the Property Qualifier is Internal 6412 , the Property is Identification 6414 , the Representation/Association is Identifier 6416 , the Type is CDT 6418 , and the Type Name is Party Internal ID 6420 . The Cardinality is zero or one 6422 .

For the Standard ID 6424 , the Category is Element 6426 , the Object Class is Business Transaction Document Party 6428 , the Property Qualifier is Standard 6430 , the Property is Identification 6432 , the Representation/Association is Identifier 6434 , the Type is CDT 6436 , and the Type Name is Party Standard ID 6438 . The Cardinality is from zero to n. 6440 .

For the Buyer ID 6442 , the Category is Element 6444 , the Object Class is Business Transaction Document Party 6446 , the Property Qualifier is Buyer 6448 , the Property is Identification 6450 , the Representation/Association is Identifier 6452 , the Type is CDT 6454 , and the Type Name is Party ID 6456 . The Cardinality is zero or one 6458 .

For the Seller ID 6460 , the Category is Element 6462 , the Object Class is Business Transaction Document Party 6464 , the Property Qualifier is Seller 6466 , the Property is Identification 6468 , the Representation/Association is Identifier 6470 , the Type is CDT 6472 , and the Type Name is Party Party ID 6474 . The Cardinality is zero or one 6476 .

For the Product Recipient ID 6478 , the Category is Element 6480 , the Object Class is Business Transaction Document Party 6482 , the Property Qualifier is Product Recipient 6484 , the Property is Identification 6486 , the Representation/Association is Identifier 6488 , the Type is CDT 6490 , and the Type Name is Party Party ID 6492 . The Cardinality is zero or one 6494 .

For the Vendor ID 6496 , the Category is Element 6498 , the Object Class is Business Transaction Document Party 6499 , the Property Qualifier is Vendor 6401 A, the Property is Identification 6402 A, the Representation/Association is Identifier 6403 A, the Type is CDT 6404 A, and the Type Name is Party Party ID 6405 A. The Cardinality is zero or one 6406 A.

For the Bill To ID 6407 A, the Category is Element 6408 A, the Object Class is Business Transaction Document Party 6409 A, the Property Qualifier is Bill To 6410 A, the Property is Identification 6411 A, the Representation/Association is Identifier 6412 A, the Type is CDT 6413 A, and the Type Name is Party Party ID 6414 A. The Cardinality is zero or one 6415 A.

For the Bill From ID 6416 A, the Category is Element 6417 A, the Object Class is Business Transaction Document Party 6418 A, the Property Qualifier is Bill From 6419 A, the Property is Identification 6420 A, the Representation/Association is Identifier 6421 A, the Type is CDT 6422 A, and the Type Name is Party Party ID 6423 A. The Cardinality is zero or one 6424 A.

For the Bidder ID 6425 A, the Category is Element 6426 A, the Object Class is Business Transaction Document Party 6427 A, the Property Qualifier is Bidder 6428 A, the Property is Identification 6429 A, the Representation/Association is Identifier 6430 A, the Type is CDT 6431 A, and the Type Name is Party Party ID 6432 A. The Cardinality is zero or one 6433 A.

For the Address 6434 A, the Category is Element 6435 A, the Object Class is Business Transaction Document Party 6436 A, the Property is Address 6437 A, the Representation/Association is Address 6438 A, the Type is GDT 6440 A, and the Type Name is Address 6441 A. The Cardinality is zero or one 6424 A.

For the Contact Person 6443 A, the Category is Element 6444 A, the Object Class is Business Transaction Document Party 6445 A, the Property is Contact Person 6446 A, the Representation/Association is Contact Person 6447 A, the Type is CDT 6448 A, and the Type Name is Contact Person 6464 A. The Cardinality is zero or one 6450 A.

InternalID refers to a proprietary identifier that is used when both sender and recipient can access shared master data (extended enterprise). StandardID refers to a standardized identifier for this party, whose identification scheme may be managed by an agency from the DE 3055 code list. BuyerID refers to an identifier that is used by the BuyerParty for this party. SellerID refers to an identifier that is used by the SellerParty for this party. ProductRecipientID refers to an identifier that is used by the ProductRecipientParty for this party. VendorID refers to an identifier that is used by the VendorParty for this party. BillToID refers to an identifier that is used by the BillToParty for this party. BillFromID refers to an identifier that is used by the BillFromParty for this party. BidderID refers to an identifier that is used by the BidderParty for this party. Address refers to the address of the party. ContactPerson refers to a contact person of the party.

The different IDs of a CDT BusinessTransactionDocumentParty 6400 may identify the same party. A party may be identified by InternalID when sender and recipient can access shared master data, by StandardID when sender and recipient can manage standardized identifiers, or by PartytPartyIDs when sender and recipient are interested in the PartyIDs assigned by the parties involved. Of the IDs available to the sender, IDs that the recipient is expected to understand may be used in a message.

The parties involved in a business transaction assume a specific role that is also specified for them in the corresponding business documents. For example, BuyerParty is a party that buys goods or services, SellerParty is a party that sells goods or services, CreditorParty is a party that is authorized to claim goods, services or payment for a debt owed to it, DebtorParty is a party that is obliged to provide goods, services or payment for a debt it owes, ProductRecipientParty is a party to which goods are delivered or for which services are provided, VendorParty is a party that delivers goods or provides services, ManufacturerParty is a party that manufactures goods, PayerParty is a party that pays for goods or services, PayeeParty is a party that receives a payment for goods or services, BillToParty is a party to which the invoice for goods or services is sent, BillFromParty is a party that creates the invoice for goods or services, CarrierParty is a party that transports goods, RequestorParty is a party that requests the procurement of goods or services, PortalProviderParty is a party that runs a portal that brings business partners together for a business transaction, CatalogueProviderParty is a party that compiles a catalogue, BidderParty is a party that bids for goods or services, and OwnerParty is a party that has tangible or intangible assets as property.

The CDT BusinessTransactionDocumentParty 6400 is used in messages for internal and external communication to transmit required information about the parties involved.

(dd) BusinessTransactionDocumentPricingIndicator

The GDT BusinessTransactionDocumentPricingIndicator 6500 indicates whether pricing/price determination should be performed for all items or for selected items in a business transaction. An example of GDT BusinessTransactionDocumentPricingIndicator 6500 is: <BusinessTransactionDocumentPricingIndicator>true</BusinessTransactionDocumentPricingIndicator>.

The structure of GDT Business Transaction Document Pricing Indicator 6500 is depicted in FIG. 65 . For the GDT Business Transaction Document Pricing Indicator 6500 , the Object Class is Business Transaction Document 6502 , the Property is Pricing Indicator 6504 , the Representation/Association is Indicator 6506 , the Type is CCT 6508 , and the Type Name is Indicator 6510 .

The GDT BusinessTransactionDocumentPricingIndicator 6500 can have the values true or false. True indicates that the pricing/price determination should be performed. False indicates that the pricing/price determination should not be performed.

Business documents or items in business documents for which pricing/price determination can be performed are linked to the purchase or sale of products. Illustrative examples are order, delivery and transport documents and their items.

(ee) BusinessTransactionDocumentProduct

A CDT BusinessTransactionDocumentProduct 6600 contains the information that is exchanged—for example, in accordance with common business understanding—in business documents about a product. This information identifies the product and product type, and describes the product. This identification can occur using an internal ID, a standardized ID, or IDs assigned by the parties involved. A product is either a tangible or intangible good, and is a part of the business activities of a company. It can be traded and contributes directly or indirectly to value added. An ID assigned by a party identifies in the name the role the assigning party plays in the business transaction. At present, the roles are Buyer, Seller, ProductRecipient, Vendor, Manufacturer, BillTo, BillFrom and Bidder. An example of CDT BusinessTransactionDocumentProduct 6600 is: