Managing Consistent Interfaces for Goods Tag, Production Bill of Material Hierarchy, and Release Order Template Business Objects across Heterogeneous Systems

TECHNICAL FIELD

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

BACKGROUND

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.

Currently, many standards exist that 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.

SUMMARY

In a first aspect, a tangible computer readable medium includes program code for providing a message-based interface for exchanging goods tag-related information for an electronic device or other small piece, part or label that is attached to a product or package and that contains selected information about the product or package. The medium comprises program code for receiving via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry and from a heterogeneous application executing in an environment of computer systems providing message-based services, a first message for requesting to form mixed content package tag notification that includes a first message package derived from the common business object model and hierarchically organized in memory as a form mixed content package tag notification message entity and a goods tag package comprising a goods tag entity, a delivery package, a business transaction document references package and a site package, where the goods tag entity includes an identifier (ID), a creation context depending date, an output request creation date time and an output request creation identity ID, where the delivery package includes a delivery entity, where the business transaction document references package includes a business transaction document references entity, where the site package includes a site entity, and further where the site entity includes a site ID and a site description.

The medium further comprises program code for processing the first message according to the hierarchical organization of the first message package, where processing the first message includes unpacking the first message package based on the common business object model.

The medium further comprises program code for sending a second message to the heterogeneous application responsive to the first message, where the second message includes a second message package derived from the common business object model to provide consistent semantics with the first message package.

Implementations can include the following. The goods tag entity further comprises at least one of the following: a production date, a shipping date, a goods receipt date, a shipping package attached indicator, a gross weight measure, a gross weight measure type code, a gross weight measure type name, a gross weight measure unit code name, a gross volume measure, a gross volume measure type code, a gross volume measure type name, a gross volume measure unit code name, an output request creation business partner formatted name, an image file content binary object, and a transport tracking. The goods tag package further comprises at least one of the following: a text collection package, a logistic unit package, and an identified logistic unit package.

In another aspect, a distributed system operates in a landscape of computer systems providing message-based services defined in a service registry. The system comprises a graphical user interface comprising computer readable instructions, embedded on tangible media, for a request to form a mixed content package tag notification for goods tag-related information for an electronic device or other small piece, part or label that is attached to a product or package and that contains selected information about the product or package using a request.

The system further comprises a first memory storing a user interface controller for processing the request and involving a message including a message package derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based service interfaces and message packages, the message package hierarchically organized as a form mixed content package tag notification message entity and a goods tag package comprising a goods tag entity, a delivery package, a business transaction document references package and a site package, where the goods tag entity includes an identifier (ID), a creation context depending date, an output request creation date time and an output request creation identity ID, where the delivery package includes a delivery entity, where the business transaction document references package includes a business transaction document references entity, where the site package includes a site entity, and further where the site entity includes a site ID and a site description.

The system further comprises a second memory, remote from the graphical user interface, storing a plurality of message-based service interfaces derived from the common business object model to provide consistent semantics with messages derived from the common business object model, where one of the message-based service interfaces processes the message according to the hierarchical organization of the message package, where processing the message includes unpacking the first message package based on the common business object model.

Implementations can include the following. The first memory is remote from the graphical user interface. The first memory is remote from the second memory.

In another aspect, a tangible computer readable medium includes program code for providing a message-based interface for exchanging information for a hierarchy of production bills of material. The medium comprises program code for receiving via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry and from a heterogeneous application executing in an environment of computer systems providing message-based services, a first message for a request to form information for a production bill of material hierarchy that includes a first message package derived from the common business object model and hierarchically organized in memory as a form production bill of material hierarchy request message entity and a production bill of material hierarchy package comprising a production bill of material hierarchy entity and an item package, where the production bill of material hierarchy entity includes a production bill of material ID, a production bill of material variant ID, a material ID, an explosion date and a quantity, and where the item package includes an item entity, and further where the item entity includes a hierarchy level ordinal number value, an ordinal number value, a material ID, a quantity and a production bill of material item group item change state quantity fixed indicator.

Implementations can include the following. The production bill of material hierarchy entity further comprises at least one of the following: a production bill of material description, a production bill of material variant description, a material description, and a maximum hierarchy level ordinal number value.

The system further comprises a first memory storing a user interface controller for processing the request and involving a message including a message package derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based service interfaces and message packages, the message package hierarchically organized as a form production bill of material hierarchy request message entity and a production bill of material hierarchy package comprising a production bill of material hierarchy entity and an item package, where the production bill of material hierarchy entity includes a production bill of material ID, a production bill of material variant ID, a material ID, an explosion date and a quantity, and where the item package includes an item entity, and further where the item entity includes a hierarchy level ordinal number value, an ordinal number value, a material ID, a quantity and a production bill of material item group item change state quantity fixed indicator.

Implementations can include the following. The first memory is remote from the graphical user interface. The first memory is remote from the second memory.

In another aspect, a tangible computer readable medium includes program code for providing a message-based interface for exchanging information for a template that includes a maximal possible set of nodes, relationships, attributes and operations for a procurement release order and other objects derived from the template. The medium comprises program code for receiving via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry and from a heterogeneous application executing in an environment of computer systems providing message-based services, a first message for requesting a procurement release order that includes a first message package derived from the common business object model and hierarchically organized in memory as a procurement release order request message entity and a procurement release order package comprising a procurement release order entity, where the procurement release order entity includes an action code, an ID, a creation date time, an ordered date time, and an item list complete transmission indicator.

Implementations can include the following. The procurement release order package further comprises at least one of the following: a business transaction document reference package, a party package, an attachment folder package, a text collection package, and an item package. The procurement release order entity further comprises a reconciliation period counter value.

In another aspect, a distributed system operates in a landscape of computer systems providing message-based services defined in a service registry. The system comprises a graphical user interface comprising computer readable instructions, embedded on tangible media, for requesting a procurement release order that is based on a template that includes a maximal possible set of nodes, relationships, attributes and operations for a procurement release order and other objects derived from the template using a request.

Implementations can include the following. The first memory is remote from the graphical user interface. The first memory is remote from the second memory.

BRIEF DESCRIPTION OF THE DRAWINGS

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 business document flow for an invoice request in accordance with methods and systems consistent with the subject matter described herein.

FIGS. 3A-B illustrate example environments implementing the transmission, receipt, and processing of data between heterogeneous applications in accordance with certain embodiments included in the present disclosure.

FIG. 4 illustrates an example application implementing certain techniques and components in accordance with one embodiment of the system of FIG. 1.

FIG. 5A depicts an example development environment in accordance with one embodiment of FIG. 1.

FIG. 5B depicts a simplified process for mapping a model representation to a runtime representation using the example development environment of FIG. 5A or some other development environment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

FIGS. 21A-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. 22A-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.

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

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

FIG. 25 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. 26A depicts components of a message in accordance with methods and systems consistent with the subject matter described herein.

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

FIGS. 27A-E depict a hierarchization process in accordance with methods and systems consistent with the subject matter described herein.

FIG. 28 illustrates an example method for service enabling in accordance with one embodiment of the present disclosure.

FIG. 29 is a graphical illustration of an example business object and associated components as may be used in the enterprise service infrastructure system of the present disclosure.

FIG. 30 illustrates an example method for managing a process agent framework in accordance with one embodiment of the present disclosure.

FIG. 31 illustrates an example method for status and action management in accordance with one embodiment of the present disclosure.

FIGS. 32-1 through 32-7 depict an example object model for a business object Goods Tag.

FIG. 33 depicts an example Form Mixed Content Package Tag Notification Message Data Type.

FIGS. 34-1 through 34-2 depict an example Form Serialised Material Tag Notification Message Data Type.

FIGS. 35-1 through 35-2 depict an example Form Uniform Content Package Tag Notification Message Data Type.

FIG. 36 depicts an example Form Unspecified Content Package Tag Notification Message Data Type.

FIGS. 37-1 through 37-26 show an example configuration of an Element Structure that includes a FormMixedContentPackageTagNotification package.

FIGS. 38-1 through 38-24 show an example configuration of an Element Structure that includes a FormSerialisedMaterialTagNotification package.

FIGS. 39-1 through 39-27 show an example configuration of an Element Structure that includes a FormUniformContentPackageTagNotification package.

FIGS. 40-1 through 40-21 show an example configuration of an Element Structure that includes a FormUnspecifiedContentPackageTagNotification package.

FIGS. 41-1 through 41-4 depict an example object model for a business object Production Bill of Material Hierarchy.

FIG. 42 depicts an example Form Production Bill of Material Hierarchy Information Message Data Type.

FIGS. 43-1 through 43-6 show an example configuration of an Element Structure that includes a FormProductionBillOfMaterialHierarchy package.

FIGS. 44-1 through 44-21 depict an example object model for a business object ReleaseOrder_Template.

FIGS. 45-1 through 45-4 depict an example Form Procurement Release Order Request Message Data Type.

FIGS. 46-1 through 46-4 depict an example ProcurementReleaseOrderRequest Message Data Type.

FIGS. 47-1 through 47-64 show an example configuration of an Element Structure that includes a FormProcurementReleaseOrderRequest package.

FIGS. 48-1 through 48-237 show an example configuration of an Element Structure that includes a ProcurementReleaseOrderRequest package.

DETAILED DESCRIPTION

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.

Generally, the business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. In the architecture, processes may typically operate on business objects. Business objects represent a specific view on some well-defined business content. In other words, business objects represent content, which a typical business user would expect and understand with little explanation. Business objects are further categorized as business process objects and master data objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time). The term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.

The architectural elements also include the process component. The process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. In general, the process component contains one or more semantically related business objects. Often, a particular business object belongs to no more than one process component. Interactions between process component pairs involving their respective business objects, process agents, operations, interfaces, and messages are described as process component interactions, which generally determine the interactions of a pair of process components across a deployment unit boundary. Interactions between process components within a deployment unit are typically not constrained by the architectural design and can be implemented in any convenient fashion. Process components may be modular and context-independent. In other words, process components may not be specific to any particular application and as such, may be reusable. In some implementations, the process component is the smallest (most granular) element of reuse in the architecture. An external process component is generally used to represent the external system in describing interactions with the external system; however, this should be understood to require no more of the external system than that able to produce and receive messages as required by the process component that interacts with the external system. For example, process components may include multiple operations that may provide interaction with the external system. Each operation generally belongs to one type of process component in the architecture. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. The operation is often the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters serving as a signature.

The architectural elements may also include the service interface, referred to simply as the interface. The interface is a named group of operations. The interface often belongs to one process component and process component might contain multiple interfaces. In one implementation, the service interface contains only inbound or outbound operations, but not a mixture of both. One interface can contain both synchronous and asynchronous operations. Normally, operations of the same type (either inbound or outbound) which belong to the same message choreography will belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.

The architectural elements also include the message. Operations transmit and receive messages. Any convenient messaging infrastructure can be used. A message is information conveyed from one process component instance to another, with the expectation that activity will ensue. Operation can use multiple message types for inbound, outbound, or error messages. When two process components are in different deployment units, invocation of an operation of one process component by the other process component is accomplished by the operation on the other process component sending a message to the first process component.

The architectural elements may also include the process agent. Process agents do business processing that involves the sending or receiving of messages. Each operation normally has at least one associated process agent. Each process agent can be associated with one or more operations. Process agents can be either inbound or outbound and either synchronous or asynchronous. Asynchronous outbound process agents are called after a business object changes such as after a “create”, “update”, or “delete” of a business object instance. Synchronous outbound process agents are generally triggered directly by business object. An outbound process agent will generally perform some processing of the data of the business object instance whose change triggered the event. The outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system. The outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component. Alternatively, the process agent may be inbound. For example, inbound process agents may be used for the inbound part of a message-based communication. Inbound process agents are called after a message has been received. The inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. Inbound process agent is not generally the agent of business object but of its process component. Inbound process agent can act on multiple business objects in a process component. Regardless of whether the process agent is inbound or outbound, an agent may be synchronous if used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work.

The architectural elements also include the deployment unit. Each deployment unit may include one or more process components that are generally deployed together on a single computer system platform. Conversely, separate deployment units can be deployed on separate physical computing systems. The process components of one deployment unit can interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit deployed on a platform belonging to one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to-business communication. More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by the deployment unit to be scaled to meet demand by creating as many instances as needed.

Since interaction between deployment units is through process component operations, one deployment unit can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units as HI appropriate. Thus, while deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interaction within other deployment units. Similarly, process components that interact with other process components or external systems only through messages, e.g., as sent and received by operations, can also be replaced as long as the replacement generally supports the operations of the original.

Services (or interfaces) may be provided in a flexible architecture to support varying criteria between services and systems. The flexible architecture may generally be provided by a service delivery business object. The system may be able to schedule a service asynchronously as necessary, or on a regular basis. Services may be planned according to a schedule manually or automatically. For example, a follow-up service may be scheduled automatically upon completing an initial service. In addition, flexible execution periods may be possible (e.g. hourly, daily, every three months, etc.). Each customer may plan the services on demand or reschedule service execution upon request.

FIG. 1 depicts a flow diagram 100 showing an example technique, perhaps implemented by systems similar to those disclosed 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 102). 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.

After creating the business scenario, the developers add details to each step of the business scenario (step 104). 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.

After creating the process interaction model, the developers create a “message choreography” (step 106), 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 108). Thus, the business document flow illustrates the flow of information between the business entities during a business process.

FIG. 2 depicts an example business document flow 200 for the process of purchasing a product or service. The business entities involved with the illustrative purchase process include Accounting 202, Payment 204, Invoicing 206, Supply Chain Execution (“SCE”) 208, Supply Chain Planning (“SCP”) 210, Fulfillment Coordination (“FC”) 212, Supply Relationship Management (“SRM”) 214, Supplier 216, and Bank 218. The business document flow 200 is divided into four different transactions: Preparation of Ordering (“Contract”) 220, Ordering 222, Goods Receiving (“Delivery”) 224, and Billing/Payment 226. In the business document flow, arrows 228 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., 229) when the step is required, and a dotted vertical line (e.g., 230) when the step is optional.

During the Contract transaction 220, the SRM 214 sends a Source of Supply Notification 232 to the SCP 210. This step is optional, as illustrated by the optional control line 230 coupling this step to the remainder of the business document flow 200. During the Ordering transaction 222, the SCP 210 sends a Purchase Requirement Request 234 to the FC 212, which forwards a Purchase Requirement Request 236 to the SRM 214. The SRM 214 then sends a Purchase Requirement Confirmation 238 to the FC 212, and the FC 212 sends a Purchase Requirement Confirmation 240 to the SCP 210. The SRM 214 also sends a Purchase Order Request 242 to the Supplier 216, and sends Purchase Order Information 244 to the FC 212. The FC 212 then sends a Purchase Order Planning Notification 246 to the SCP 210. The Supplier 216, after receiving the Purchase Order Request 242, sends a Purchase Order Confirmation 248 to the SRM 214, which sends a Purchase Order Information confirmation message 254 to the FC 212, which sends a message 256 confirming the Purchase Order Planning Notification to the SCP 210. The SRM 214 then sends an Invoice Due Notification 258 to Invoicing 206.

During the Delivery transaction 224, the FC 212 sends a Delivery Execution Request 260 to the SCE 208. The Supplier 216 could optionally (illustrated at control line 250) send a Dispatched Delivery Notification 252 to the SCE 208. The SCE 208 then sends a message 262 to the FC 212 notifying the FC 212 that the request for the Delivery Information was created. The FC 212 then sends a message 264 notifying the SRM 214 that the request for the Delivery Information was created. The FC 212 also sends a message 266 notifying the SCP 210 that the request for the Delivery Information was created. The SCE 208 sends a message 268 to the FC 212 when the goods have been set aside for delivery. The FC 212 sends a message 270 to the SRM 214 when the goods have been set aside for delivery. The FC 212 also sends a message 272 to the SCP 210 when the goods have been set aside for delivery.

The SCE 208 sends a message 274 to the FC 212 when the goods have been delivered. The FC 212 then sends a message 276 to the SRM 214 indicating that the goods have been delivered, and sends a message 278 to the SCP 210 indicating that the goods have been delivered. The SCE 208 then sends an Inventory Change Accounting Notification 280 to Accounting 202, and an Inventory Change Notification 282 to the SCP 210. The FC 212 sends an Invoice Due Notification 284 to Invoicing 206, and SCE 208 sends a Received Delivery Notification 286 to the Supplier 216.

During the Billing/Payment transaction 226, the Supplier 216 sends an Invoice Request 287 to Invoicing 206. Invoicing 206 then sends a Payment Due Notification 288 to Payment 204, a Tax Due Notification 289 to Payment 204, an Invoice Confirmation 290 to the Supplier 216, and an Invoice Accounting Notification 291 to Accounting 202. Payment 204 sends a Payment Request 292 to the Bank 218, and a Payment Requested Accounting Notification 293 to Accounting 202. Bank 218 sends a Bank Statement Information 296 to Payment 204. Payment 204 then sends a Payment Done Information 294 to Invoicing 206 and a Payment Done Accounting Notification 295 to Accounting 202.

Within a business document flow, business documents having the same or similar structures are marked. For example, in the business document flow 200 depicted in FIG. 2, Purchase Requirement Requests 234, 236 and Purchase Requirement Confirmations 238, 240 have the same structures. Thus, each of these business documents is marked with an “O6.” Similarly, Purchase Order Request 242 and Purchase Order Confirmation 248 have the same structures. Thus, both documents are marked with an “O1.” Each business document or message is based on a message type.

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 110). 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 112). The heterogeneous programs use instantiations of these interfaces (called “business document objects” below) to create messages (step 114), which are sent to complete the business transaction (step 116). 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 often exceed the standards and thus may 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.

Turning to the illustrated embodiment in FIG. 3A, environment 300 includes or is communicably coupled (such as via a one-, bi- or multi-directional link or network) with server 302, one or more clients 304, one or more or vendors 306, one or more customers 308, at least some of which communicate across network 312. But, of course, this illustration is for example purposes only, and any distributed system or environment implementing one or more of the techniques described herein may be within the scope of this disclosure. Server 302 comprises an electronic computing device operable to receive, transmit, process and store data associated with environment 300. Generally, FIG. 3A provides merely one example of computers that may be used with the disclosure. Each computer is generally intended to encompass any suitable processing device. For example, although FIG. 3A illustrates one server 302 that may be used with the disclosure, environment 300 can be implemented using computers other than servers, as well as a server pool. Indeed, server 302 may be any computer or processing device such as, for example, a blade server, general-purpose personal computer (PC), Macintosh, workstation, Unix-based computer, or any other suitable device. In other words, the present disclosure contemplates computers other than general purpose computers as well as computers without conventional operating systems. Server 302 may be adapted to execute any operating system including Linux, UNIX, Windows Server, or any other suitable operating system. According to one embodiment, server 302 may also include or be communicably coupled with a web server and/or a mail server.

As illustrated (but not required), the server 302 is communicably coupled with a relatively remote repository 335 over a portion of the network 312. The repository 335 is any electronic storage facility, data processing center, or archive that may supplement or replace local memory (such as 327). The repository 335 may be a central database communicably coupled with the one or more servers 302 and the clients 304 via a virtual private network (VPN), SSH (Secure Shell) tunnel, or other secure network connection. The repository 335 may be physically or logically located at any appropriate location including in one of the example enterprises or off-shore, so long as it remains operable to store information associated with the environment 300 and communicate such data to the server 302 or at least a subset of plurality of the clients 304.

Illustrated server 302 includes local memory 327. Memory 327 may include any memory or database module and may take the form of volatile or non-volatile memory including, without limitation, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory component. Illustrated memory 327 includes an exchange infrastructure (“XI”) 314, which is an infrastructure that supports the technical interaction of business processes across heterogeneous system environments. XI 314 centralizes the communication between components within a business entity and between different business entities. When appropriate, XI 314 carries out the mapping between the messages. XI 314 integrates different versions of systems implemented on different platforms (e.g., Java and ABAP). XI 314 is based on an open architecture, and makes use of open standards, such as eXtensible Markup Language (XML)™ and Java environments. XI 314 offers services that are useful in a heterogeneous and complex system landscape. In particular, XI 314 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.

XI 314 stores data types 316, a business object model 318, and interfaces 320. The details regarding the business object model are described below. Data types 316 are the building blocks for the business object model 318. The business object model 318 is used to derive consistent interfaces 320. XI 314 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 312 by using the standardized interfaces 320.

While not illustrated, memory 327 may also include business objects and any other appropriate data such as services, interfaces, VPN applications or services, firewall policies, a security or access log, print or other reporting files, HTML files or templates, data classes or object interfaces, child software applications or sub-systems, and others. This stored data may be stored in one or more logical or physical repositories. In some embodiments, the stored data (or pointers thereto) may be stored in one or more tables in a relational database described in terms of SQL statements or scripts. In the same or other embodiments, the stored data may also be formatted, stored, or defined as various data structures in text files, XML documents, Virtual Storage Access Method (VSAM) files, flat files, Btrieve files, comma-separated-value (CSV) files, internal variables, or one or more libraries. For example, a particular data service record may merely be a pointer to a particular piece of third party software stored remotely. In another example, a particular data service may be an internally stored software object usable by authenticated customers or internal development. In short, the stored data may comprise one table or file or a plurality of tables or files stored on one computer or across a plurality of computers in any appropriate format. Indeed, some or all of the stored data may be local or remote without departing from the scope of this disclosure and store any type of appropriate data.

Server 302 also includes processor 325. Processor 325 executes instructions and manipulates data to perform the operations of server 302 such as, for example, a central processing unit (CPU), a blade, an application specific integrated circuit (ASIC), or a field-programmable gate array (FPGA). Although FIG. 3A illustrates a single processor 325 in server 302, multiple processors 325 may be used according to particular needs and reference to processor 325 is meant to include multiple processors 325 where applicable. In the illustrated embodiment, processor 325 executes at least business application 330.

At a high level, business application 330 is any application, program, module, process, or other software that utilizes or facilitates the exchange of information via messages (or services) or the use of business objects. For example, application 330 may implement, utilize or otherwise leverage an enterprise service-oriented architecture (enterprise SOA), which may be considered a blueprint for an adaptable, flexible, and open IT architecture for developing services-based, enterprise-scale business solutions. This example enterprise service may be a series of web services combined with business logic that can be accessed and used repeatedly to support a particular business process. Aggregating web services into business-level enterprise services helps provide a more meaningful foundation for the task of automating enterprise-scale business scenarios Put simply, enterprise services help provide a holistic combination of actions that are semantically linked to complete the specific task, no matter how many cross-applications are involved. In certain cases, environment 300 may implement a composite application 330, as described below in FIG. 4. Regardless of the particular implementation, “software” may include software, firmware, wired or programmed hardware, or any combination thereof as appropriate. Indeed, application 330 may be written or described in any appropriate computer language including C, C++, Java, Visual Basic, assembler, Perl, any suitable version of 4GL, as well as others. For example, returning to the above mentioned composite application, the composite application portions may be implemented as Enterprise Java Beans (EJBs) or the design-time components may have the ability to generate run-time implementations into different platforms, such as J2EE (Java 2 Platform, Enterprise Edition), ABAP (Advanced Business Application Programming) objects, or Microsoft's .NET. It will be understood that while application 330 is illustrated in FIG. 4 as including various sub-modules, application 330 may include numerous other sub-modules or may instead be a single multi-tasked module that implements the various features and functionality through various objects, methods, or other processes. Further, while illustrated as internal to server 302, one or more processes associated with application 330 may be stored, referenced, or executed remotely. For example, a portion of application 330 may be a web service that is remotely called, while another portion of application 330 may be an interface object bundled for processing at remote client 304. Moreover, application 330 may be a child or sub-module of another software module or enterprise application (not illustrated) without departing from the scope of this disclosure. Indeed, application 330 may be a hosted solution that allows multiple related or third parties in different portions of the process to perform the respective processing.

More specifically, as illustrated in FIG. 4, application 330 may be a composite application, or an application built on other applications, that includes an object access layer (OAL) and a service layer. In this example, application 330 may execute or provide a number of application services, such as customer relationship management (CRM) systems, human resources management (HRM) systems, financial management (FM) systems, project management (PM) systems, knowledge management (KM) systems, and electronic file and mail systems. Such an object access layer is operable to exchange data with a plurality of enterprise base systems and to present the data to a composite application through a uniform interface. The example service layer is operable to provide services to the composite application. These layers may help the composite application to orchestrate a business process in synchronization with other existing processes (e.g., native processes of enterprise base systems) and leverage existing investments in the IT platform. Further, composite application 330 may run on a heterogeneous IT platform. In doing so, composite application may be cross-functional in that it may drive business processes across different applications, technologies, and organizations. Accordingly, composite application 330 may drive end-to-end business processes across heterogeneous systems or sub-systems. Application 330 may also include or be coupled with a persistence layer and one or more application system connectors. Such application system connectors enable data exchange and integration with enterprise sub-systems and may include an Enterprise Connector (EC) interface, an Internet Communication Manager/Internet Communication Framework (ICM/ICF) interface, an Encapsulated PostScript (EPS) interface, and/or other interfaces that provide Remote Function Call (RFC) capability. It will be understood that while this example describes a composite application 330, it may instead be a standalone or (relatively) simple software program. Regardless, application 330 may also perform processing automatically, which may indicate that the appropriate processing is substantially performed by at least one component of environment 300. It should be understood that automatically further contemplates any suitable administrator or other user interaction with application 330 or other components of environment 300 without departing from the scope of this disclosure.

Returning to FIG. 3A, illustrated server 302 may also include interface 317 for communicating with other computer systems, such as clients 304, over network 312 in a client-server or other distributed environment. In certain embodiments, server 302 receives data from internal or external senders through interface 317 for storage in memory 327, for storage in DB 335, and/or processing by processor 325. Generally, interface 317 comprises logic encoded in software and/or hardware in a suitable combination and operable to communicate with network 312. More specifically, interface 317 may comprise software supporting one or more communications protocols associated with communications network 312 or hardware operable to communicate physical signals.

Network 312 facilitates wireless or wireline communication between computer server 302 and any other local or remote computer, such as clients 304. Network 312 may be all or a portion of an enterprise or secured network. In another example, network 312 may be a VPN merely between server 302 and client 304 across wireline or wireless link. Such an example wireless link may be via 802.11a, 802.11b, 802.11g, 802.20, WiMax, and many others. While illustrated as a single or continuous network, network 312 may be logically divided into various sub-nets or virtual networks without departing from the scope of this disclosure, so long as at least portion of network 312 may facilitate communications between server 302 and at least one client 304. For example, server 302 may be communicably coupled to one or more “local” repositories through one sub-net while communicably coupled to a particular client 304 or “remote” repositories through another. In other words, network 312 encompasses any internal or external network, networks, sub-network, or combination thereof operable to facilitate communications between various computing components in environment 300. Network 312 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses. Network 312 may include one or more local area networks (LANs), radio access networks (RANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of the global computer network known as the Internet, and/or any other communication system or systems at one or more locations. In certain embodiments, network 312 may be a secure network associated with the enterprise and certain local or remote vendors 306 and customers 308. As used in this disclosure, customer 308 is any person, department, organization, small business, enterprise, or any other entity that may use or request others to use environment 300. As described above, vendors 306 also may be local or remote to customer 308. Indeed, a particular vendor 306 may provide some content to business application 330, while receiving or purchasing other content (at the same or different times) as customer 308. As illustrated, customer 308 and vendor 06 each typically perform some processing (such as uploading or purchasing content) using a computer, such as client 304.

Client 304 is any computing device operable to connect or communicate with server 302 or network 312 using any communication link. For example, client 304 is intended to encompass a personal computer, touch screen terminal, workstation, network computer, kiosk, wireless data port, smart phone, personal data assistant (PDA), one or more processors within these or other devices, or any other suitable processing device used by or for the benefit of business 308, vendor 306, or some other user or entity. At a high level, each client 304 includes or executes at least GUI 336 and comprises an electronic computing device operable to receive, transmit, process and store any appropriate data associated with environment 300. It will be understood that there may be any number of clients 304 communicably coupled to server 302. Further, “client 304,” “business,” “business analyst,” “end user,” and “user” may be used interchangeably as appropriate without departing from the scope of this disclosure. Moreover, for ease of illustration, each client 304 is described in terms of being used by one user. But this disclosure contemplates that many users may use one computer or that one user may use multiple computers. For example, client 304 may be a PDA operable to wirelessly connect with external or unsecured network. In another example, client 304 may comprise a laptop that includes an input device, such as a keypad, touch screen, mouse, or other device that can accept information, and an output device that conveys information associated with the operation of server 302 or clients 304, including digital data, visual information, or GUI 336. Both the input device and output device may include fixed or removable storage media such as a magnetic computer disk, CD-ROM, or other suitable media to both receive input from and provide output to users of clients 304 through the display, namely the client portion of GUI or application interface 336.

GUI 336 comprises a graphical user interface operable to allow the user of client 304 to interface with at least a portion of environment 300 for any suitable purpose, such as viewing application or other transaction data. Generally, GUI 336 provides the particular user with an efficient and user-friendly presentation of data provided by or communicated within environment 300. For example, GUI 336 may present the user with the components and information that is relevant to their task, increase reuse of such components, and facilitate a sizable developer community around those components. GUI 336 may comprise a plurality of customizable frames or views having interactive fields, pull-down lists, and buttons operated by the user. For example, GUI 336 is operable to display data involving business objects and interfaces in a user-friendly form based on the user context and the displayed data. In another example, GUI 336 is operable to display different levels and types of information involving business objects and interfaces based on the identified or supplied user role. GUI 336 may also present a plurality of portals or dashboards. For example, GUI 336 may display a portal that allows users to view, create, and manage historical and real-time reports including role-based reporting and such. Of course, such reports may be in any appropriate output format including PDF, HTML, and printable text. Real-time dashboards often provide table and graph information on the current state of the data, which may be supplemented by business objects and interfaces. It should be understood that the term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Indeed, reference to GUI 336 may indicate a reference to the front-end or a component of business application 330, as well as the particular interface accessible via client 304, as appropriate, without departing from the scope of this disclosure. Therefore, GUI 336 contemplates any graphical user interface, such as a generic web browser or touchscreen, that processes information in environment 300 and efficiently presents the results to the user. Server 302 can accept data from client 304 via the web browser (e.g., Microsoft Internet Explorer or Netscape Navigator) and return the appropriate HTML or XML responses to the browser using network 312.

More generally in environment 300 as depicted in FIG. 3B, a Foundation Layer 375 can be deployed on multiple separate and distinct hardware platforms, e.g., System A 350 and System B 360, to support application software deployed as two or more deployment units distributed on the platforms, including deployment unit 352 deployed on System A and deployment unit 362 deployed on System B. In this example, the foundation layer can be used to support application software deployed in an application layer. In particular, the foundation layer can be used in connection with application software implemented in accordance with a software architecture that provides a suite of enterprise service operations having various application functionality. In some implementations, the application software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used from multiple deployment units. These entities can be process components, business objects, and reuse service components. A reuse service component is a piece of software that is reused in different transactions. A reuse service component is used by its defined interfaces, which can be, e.g., local APIs or service interfaces. As explained above, process components in separate deployment units interact through service operations, as illustrated by messages passing between service operations 356 and 366, which are implemented in process components 354 and 364, respectively, which are included in deployment units 352 and 362, respectively. As also explained above, some form of direct communication is generally the form of interaction used between a business object, e.g., business object 358 and 368, of an application deployment unit and a business object, such as master data object 370, of the Foundation Layer 375.

Various components of the present disclosure may be modeled using a model-driven environment. For example, the model-driven framework or environment may allow the developer to use simple drag-and-drop techniques to develop pattern-based or freestyle user interfaces and define the flow of data between them. The result could be an efficient, customized, visually rich online experience. In some cases, this model-driven development may accelerate the application development process and foster business-user self-service. It further enables business analysts or IT developers to compose visually rich applications that use analytic services, enterprise services, remote function calls (RFCs), APIs, and stored procedures. In addition, it may allow them to reuse existing applications and create content using a modeling process and a visual user interface instead of manual coding.

FIG. 5A depicts an example modeling environment 516, namely a modeling environment, in accordance with one embodiment of the present disclosure. Thus, as illustrated in FIG. 5A, such a modeling environment 516 may implement techniques for decoupling models created during design-time from the runtime environment. In other words, model representations for GUIs created in a design time environment are decoupled from the runtime environment in which the GUIs are executed. Often in these environments, a declarative and executable representation for GUIs for applications is provided that is independent of any particular runtime platform, GUI framework, device, or programming language.

According to some embodiments, a modeler (or other analyst) may use the model-driven modeling environment 516 to create pattern-based or freestyle user interfaces using simple drag-and-drop services. Because this development may be model-driven, the modeler can typically compose an application using models of business objects without having to write much, if any, code. In some cases, this example modeling environment 516 may provide a personalized, secure interface that helps unify enterprise applications, information, and processes into a coherent, role-based portal experience. Further, the modeling environment 516 may allow the developer to access and share information and applications in a collaborative environment. In this way, virtual collaboration rooms allow developers to work together efficiently, regardless of where they are located, and may enable powerful and immediate communication that crosses organizational boundaries while enforcing security requirements. Indeed, the modeling environment 516 may provide a shared set of services for finding, organizing, and accessing unstructured content stored in third-party repositories and content management systems across various networks 312. Classification tools may automate the organization of information, while subject-matter experts and content managers can publish information to distinct user audiences. Regardless of the particular implementation or architecture, this modeling environment 516 may allow the developer to easily model hosted business objects 140 using this model-driven approach.

In certain embodiments, the modeling environment 516 may implement or utilize a generic, declarative, and executable GUI language (generally described as XGL). This example XGL is generally independent of any particular GUI framework or runtime platform. Further, XGL is normally not dependent on characteristics of a target device on which the graphic user interface is to be displayed and may also be independent of any programming language. XGL is used to generate a generic representation (occasionally referred to as the XGL representation or XGL-compliant representation) for a design-time model representation. The XGL representation is thus typically a device-independent representation of a GUI. The XGL representation is declarative in that the representation does not depend on any particular GUI framework, runtime platform, device, or programming language. The XGL representation can be executable and therefore can unambiguously encapsulate execution semantics for the GUI described by a model representation. In short, models of different types can be transformed to XGL representations.

The XGL representation may be used for generating representations of various different GUIs and supports various GUI features including full windowing and componentization support, rich data visualizations and animations, rich modes of data entry and user interactions, and flexible connectivity to any complex application data services. While a specific embodiment of XGL is discussed, various other types of XGLs may also be used in alternative embodiments. In other words, it will be understood that XGL is used for example description only and may be read to include any abstract or modeling language that can be generic, declarative, and executable.

Turning to the illustrated embodiment in FIG. 5A, modeling tool 340 may be used by a GUI designer or business analyst during the application design phase to create a model representation 502 for a GUI application. It will be understood that modeling environment 516 may include or be compatible with various different modeling tools 340 used to generate model representation 502. This model representation 502 may be a machine-readable representation of an application or a domain specific model. Model representation 502 generally encapsulates various design parameters related to the GUI such as GUI components, dependencies between the GUI components, inputs and outputs, and the like. Put another way, model representation 502 provides a form in which the one or more models can be persisted and transported, and possibly handled by various tools such as code generators, runtime interpreters, analysis and validation tools, merge tools, and the like. In one embodiment, model representation 502 maybe a collection of XML documents with a well-formed syntax.

Illustrated modeling environment 516 also includes an abstract representation generator (or XGL generator) 504 operable to generate an abstract representation (for example, XGL representation or XGL-compliant representation) 506 based upon model representation 502. Abstract representation generator 504 takes model representation 502 as input and outputs abstract representation 506 for the model representation. Model representation 502 may include multiple instances of various forms or types depending on the tool/language used for the modeling. In certain cases, these various different model representations may each be mapped to one or more abstract representations 506. Different types of model representations may be transformed or mapped to XGL representations. For each type of model representation, mapping rules may be provided for mapping the model representation to the XGL representation 506. Different mapping rules may be provided for mapping a model representation to an XGL representation.

This XGL representation 506 that is created from a model representation may then be used for processing in the runtime environment. For example, the XGL representation 506 may be used to generate a machine-executable runtime GUI (or some other runtime representation) that may be executed by a target device. As part of the runtime processing, the XGL representation 506 may be transformed into one or more runtime representations, which may indicate source code in a particular programming language, machine-executable code for a specific runtime environment, executable GUI, and so forth, which may be generated for specific runtime environments and devices. Since the XGL representation 506, rather than the design-time model representation, is used by the runtime environment, the design-time model representation is decoupled from the runtime environment. The XGL representation 506 can thus serve as the common ground or interface between design-time user interface modeling tools and a plurality of user interface runtime frameworks. It provides a self-contained, closed, and deterministic definition of all aspects of a graphical user interface in a device-independent and programming-language independent manner. Accordingly, abstract representation 506 generated for a model representation 502 is generally declarative and executable in that it provides a representation of the GUI of model representation 502 that is not dependent on any device or runtime platform, is not dependent on any programming language, and unambiguously encapsulates execution semantics for the GUI. The execution semantics may include, for example, identification of various components of the GUI, interpretation of connections between the various GUI components, information identifying the order of sequencing of events, rules governing dynamic behavior of the GUI, rules governing handling of values by the GUI, and the like. The abstract representation 506 is also not GUI runtime-platform specific. The abstract representation 506 provides a self-contained, closed, and deterministic definition of all aspects of a graphical user interface that is device independent and language independent.

Abstract representation 506 is such that the appearance and execution semantics of a GUI generated from the XGL representation work consistently on different target devices irrespective of the GUI capabilities of the target device and the target device platform. For example, the same XGL representation may be mapped to appropriate GUIs on devices of differing levels of GUI complexity (i.e., the same abstract representation may be used to generate a GUI for devices that support simple GUIs and for devices that can support complex GUIs), the GUI generated by the devices are consistent with each other in their appearance and behavior.

Abstract representation generator 504 may be configured to generate abstract representation 506 for models of different types, which may be created using different modeling tools 340. It will be understood that modeling environment 516 may include some, none, or other sub-modules or components as those shown in this example illustration. In other words, modeling environment 516 encompasses the design-time environment (with or without the abstract generator or the various representations), a modeling toolkit (such as 340) linked with a developer's space, or any other appropriate software operable to decouple models created during design-time from the runtime environment. Abstract representation 506 provides an interface between the design time environment and the runtime environment. As shown, this abstract representation 506 may then be used by runtime processing.

As part of runtime processing, modeling environment 516 may include various runtime tools 508 and may generate different types of runtime representations based upon the abstract representation 506. Examples of runtime representations include device or language-dependent (or specific) source code, runtime platform-specific machine-readable code, GUIs for a particular target device, and the like. The runtime tools 508 may include compilers, interpreters, source code generators, and other such tools that are configured to generate runtime platform-specific or target device-specific runtime representations of abstract representation 506. The runtime tool 508 may generate the runtime representation from abstract representation 506 using specific rules that map abstract representation 506 to a particular type of runtime representation. These mapping rules may be dependent on the type of runtime tool, characteristics of the target device to be used for displaying the GUI, runtime platform, and/or other factors. Accordingly, mapping rules may be provided for transforming the abstract representation 506 to any number of target runtime representations directed to one or more target GUI runtime platforms. For example, XGL-compliant code generators may conform to semantics of XGL, as described below. XGL-compliant code generators may ensure that the appearance and behavior of the generated user interfaces is preserved across a plurality of target GUI frameworks, while accommodating the differences in the intrinsic characteristics of each and also accommodating the different levels of capability of target devices.

For example, as depicted in example FIG. 5A, an XGL-to-Java compiler 508A may take abstract representation 506 as input and generate Java code 510 for execution by a target device comprising a Java runtime 512. Java runtime 512 may execute Java code 510 to generate or display a GUI 514 on a Java-platform target device. As another example, an XGL-to-Flash compiler 508B may take abstract representation 506 as input and generate Flash code 526 for execution by a target device comprising a Flash runtime 518. Flash runtime 518 may execute Flash code 516 to generate or display a GUI 520 on a target device comprising a Flash platform. As another example, an XGL-to-DHTML (dynamic HTML) interpreter 508C may take abstract representation 506 as input and generate DHTML statements (instructions) on the fly which are then interpreted by a DHTML runtime 522 to generate or display a GUI 524 on a target device comprising a DHTML platform.

It should be apparent that abstract representation 506 may be used to generate GUIs for Extensible Application Markup Language (XAML) or various other runtime platforms and devices. The same abstract representation 506 may be mapped to various runtime representations and device-specific and runtime platform-specific GUIs. In general, in the runtime environment, machine executable instructions specific to a runtime environment may be generated based upon the abstract representation 506 and executed to generate a GUI in the runtime environment. The same XGL representation may be used to generate machine executable instructions specific to different runtime environments and target devices.

According to certain embodiments, the process of mapping a model representation 502 to an abstract representation 506 and mapping an abstract representation 506 to some runtime representation may be automated. For example, design tools may automatically generate an abstract representation for the model representation using XGL and then use the XGL abstract representation to generate GUIs that are customized for specific runtime environments and devices. As previously indicated, mapping rules may be provided for mapping model representations to an XGL representation. Mapping rules may also be provided for mapping an XGL representation to a runtime platform-specific representation.

Since the runtime environment uses abstract representation 506 rather than model representation 502 for runtime processing, the model representation 502 that is created during design-time is decoupled from the runtime environment. Abstract representation 506 thus provides an interface between the modeling environment and the runtime environment. As a result, changes may be made to the design time environment, including changes to model representation 502 or changes that affect model representation 502, generally to not substantially affect or impact the runtime environment or tools used by the runtime environment. Likewise, changes may be made to the runtime environment generally to not substantially affect or impact the design time environment. A designer or other developer can thus concentrate on the design aspects and make changes to the design without having to worry about the runtime dependencies such as the target device platform or programming language dependencies.

FIG. 5B depicts an example process for mapping a model representation 502 to a runtime representation using the example modeling environment 516 of FIG. 5A or some other modeling environment. Model representation 502 may comprise one or more model components and associated properties that describe a data object, such as hosted business objects and interfaces. As described above, at least one of these model components is based on or otherwise associated with these hosted business objects and interfaces. The abstract representation 506 is generated based upon model representation 502. Abstract representation 506 may be generated by the abstract representation generator 504. Abstract representation 506 comprises one or more abstract GUI components and properties associated with the abstract GUI components. As part of generation of abstract representation 506, the model GUI components and their associated properties from the model representation are mapped to abstract GUI components and properties associated with the abstract GUI components. Various mapping rules may be provided to facilitate the mapping. The abstract representation encapsulates both appearance and behavior of a GUI. Therefore, by mapping model components to abstract components, the abstract representation not only specifies the visual appearance of the GUI but also the behavior of the GUI, such as in response to events whether clicking/dragging or scrolling, interactions between GUI components and such.

One or more runtime representations 550a, including GUIs for specific runtime environment platforms, may be generated from abstract representation 506. A device-dependent runtime representation may be generated for a particular type of target device platform to be used for executing and displaying the GUI encapsulated by the abstract representation. The GUIs generated from abstract representation 506 may comprise various types of GUI elements such as buttons, windows, scrollbars, input boxes, etc. Rules may be provided for mapping an abstract representation to a particular runtime representation. Various mapping rules may be provided for different runtime environment platforms.

Methods and systems consistent with the subject matter described herein provide and use interfaces 320 derived from the business object model 318 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 320 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 or modules.

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.

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).

Each business object is generally 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.

a) Data Types

Data types are used to type object entities and interfaces with a structure. This typing can include business semantic. Such data types may include those generally described at pages 96 through 1642 (which are incorporated by reference herein) of U.S. patent application Ser. No. 11/803,178, filed on May 11, 2007 and entitled “Consistent Set Of Interfaces Derived From A Business Object Model.” 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 typically 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 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.

b) Entities

Entities are discrete business elements that are used during a business transaction. Entities are not to be confused with business entities or the components that interact to perform a transaction. Rather, “entities” are one of the layers of the business object model and the interfaces. For example, a Catalogue entity is used in a Catalogue Publication Request and a Purchase Order is used in a Purchase Order Request. These entities are created using the data types defined above to ensure the consistent representation of data throughout the entities.

c) Packages

Packages group the entities in the business object model and the resulting interfaces into groups of semantically associated information. Packages also may include “sub”-packages, i.e., the packages may be nested.

Packages may group elements together based on different factors, such as elements that occur together as a rule with regard to a business-related aspect. For example, as depicted in FIG. 7, in a Purchase Order, different information regarding the purchase order, such as the type of payment 702, and payment card 704, are grouped together via the PaymentInformation package 700.

Packages also may combine different components that result in a new object. For example, as depicted in FIG. 8, the components wheels 804, motor 806, and doors 808 are combined to form a composition “Car” 802. The “Car” package 800 includes the wheels, motor and doors as well as the composition “Car.”

Another grouping within a package may be subtypes within a type. In these packages, the components are specialized forms of a generic package. For example, as depicted in FIG. 9, the components Car 904, Boat 906, and Truck 908 can be generalized by the generic term Vehicle 902 in Vehicle package 900. Vehicle in this case is the generic package 910, while Car 912, Boat 914, and Truck 916 are the specializations 918 of the generalized vehicle 910.

Packages also may be used to represent hierarchy levels. For example, as depicted in FIG. 10, the Item Package 1000 includes Item 1002 with subitem xxx 1004, subitem yyy 1006, and subitem zzz 1008.

Packages can be represented in the XML schema as a comment. One advantage of this grouping is that the document structure is easier to read and is more understandable. The names of these packages are assigned by including the object name in brackets with the suffix “Package.” For example, as depicted in FIG. 11, Party package 1100 is enclosed by <PartyPackage> 1102 and </PartyPackage> 1104. Party package 1100 illustratively includes a Buyer Party 1106, identified by <BuyerParty> 1108 and </BuyerParty> 1110, and a Seller Party 1112, identified by <SellerParty> 1114 and </SellerParty>, etc.

d) Relationships

Relationships describe the interdependencies of the entities in the business object model, and are thus an integral part of the business object model.

(1) Cardinality of Relationships

FIG. 12 depicts a graphical representation of the cardinalities between two entities. The cardinality between a first entity and a second entity identifies the number of second entities that could possibly exist for each first entity. Thus, a 1:c cardinality 1200 between entities A 1202 and X 1204 indicates that for each entity A 1202, there is either one or zero 1206 entity X 1204. A 1:1 cardinality 1208 between entities A 1210 and X 1212 indicates that for each entity A 1210, there is exactly one 1214 entity X 1212. A 1:n cardinality 1216 between entities A 1218 and X 1220 indicates that for each entity A 1218, there are one or more 1222 entity Xs 1220. A 1:cn cardinality 1224 between entities A 1226 and X 1228 indicates that for each entity A 1226, there are any number 1230 of entity Xs 1228 (i.e., 0 through n Xs for each A).

(2) Types of Relationships

(a) Composition

A composition or hierarchical relationship type is a strong whole-part relationship which is used to describe the structure within an object. The parts, or dependent entities, represent a semantic refinement or partition of the whole, or less dependent entity. For example, as depicted in FIG. 13, the components 1302, wheels 1304, and doors 1306 may be combined to form the composite 1300 “Car” 1308 using the composition 1310. FIG. 14 depicts a graphical representation of the composition 1410 between composite Car 1408 and components wheel 1404 and door 1406.

(b) Aggregation

An aggregation or an aggregating relationship type is a weak whole-part relationship between two objects. The dependent object is created by the combination of one or several less dependent objects. For example, as depicted in FIG. 15, the properties of a competitor product 1500 are determined by a product 1502 and a competitor 1504. A hierarchical relationship 1506 exists between the product 1502 and the competitor product 1500 because the competitor product 1500 is a component of the product 1502. Therefore, the values of the attributes of the competitor product 1500 are determined by the product 1502. An aggregating relationship 1508 exists between the competitor 1504 and the competitor product 1500 because the competitor product 1500 is differentiated by the competitor 1504. Therefore the values of the attributes of the competitor product 1500 are determined by the competitor 1504.

An association or a referential relationship type describes a relationship between two objects in which the dependent object refers to the less dependent object. For example, as depicted in FIG. 16, a person 1600 has a nationality, and thus, has a reference to its country 1602 of origin. There is an association 1604 between the country 1602 and the person 1600.

The values of the attributes of the person 1600 are not determined by the country 1602.

(3) Specialization

Entity types may be divided into subtypes based on characteristics of the entity types. For example, FIG. 17 depicts an entity type “vehicle” 1700 specialized 1702 into subtypes “truck” 1704, “car” 1706, and “ship” 1708. These subtypes represent different aspects or the diversity of the entity type.

Subtypes may be defined based on related attributes. For example, although ships and cars are both vehicles, ships have an attribute, “draft,” that is not found in cars. Subtypes also may be defined based on certain methods that can be applied to entities of this subtype and that modify such entities. For example, “drop anchor” can be applied to ships. If outgoing relationships to a specific object are restricted to a subset, then a subtype can be defined which reflects this subset.

As depicted in FIG. 18, specializations may further be characterized as complete specializations 1800 or incomplete specializations 1802. There is a complete specialization 1800 where each entity of the generalized type belongs to at least one subtype. With an incomplete specialization 1802, there is at least one entity that does not belong to a subtype. Specializations also may be disjoint 1804 or nondisjoint 1806. In a disjoint specialization 1804, each entity of the generalized type belongs to a maximum of one subtype. With a nondisjoint specialization 1806, one entity may belong to more than one subtype. As depicted in FIG. 18, four specialization categories result from the combination of the specialization characteristics.

e) Structural Patterns

(1) Item

An item is an entity type which groups together features of another entity type. Thus, the features for the entity type chart of accounts are grouped together to form the entity type chart of accounts item. For example, a chart of accounts item is a category of values or value flows that can be recorded or represented in amounts of money in accounting, while a chart of accounts is a superordinate list of categories of values or value flows that is defined in accounting.

The cardinality between an entity type and its item is often either 1:n or 1:cn. For example, in the case of the entity type chart of accounts, there is a hierarchical relationship of the cardinality 1:n with the entity type chart of accounts item since a chart of accounts has at least one item in all cases.

(2) Hierarchy

A hierarchy describes the assignment of subordinate entities to superordinate entities and vice versa, where several entities of the same type are subordinate entities that have, at most, one directly superordinate entity. For example, in the hierarchy depicted in FIG. 19, entity B 1902 is subordinate to entity A 1900, resulting in the relationship (A,B) 1912. Similarly, entity C 1904 is subordinate to entity A 1900, resulting in the relationship (A,C) 1914. Entity D 1906 and entity E 1908 are subordinate to entity B 1902, resulting in the relationships (B,D) 1916 and (B,E) 1918, respectively. Entity F 1910 is subordinate to entity C 1904, resulting in the relationship (C,F) 1920.

Because each entity has at most one superordinate entity, the cardinality between a subordinate entity and its superordinate entity is 1:c. Similarly, each entity may have 0, 1 or many subordinate entities. Thus, the cardinality between a superordinate entity and its subordinate entity is 1:cn. FIG. 20 depicts a graphical representation of a Closing Report Structure Item hierarchy 2000 for a Closing Report Structure Item 2002. The hierarchy illustrates the 1:c cardinality 2004 between a subordinate entity and its superordinate entity, and the 1:cn cardinality 2006 between a superordinate entity and its subordinate entity.

3. Creation of the business object Model

FIGS. 21A-B depict the steps performed using methods and systems consistent with the subject matter described herein to create a business object model. Although some steps are described as being performed by a computer, these steps may alternatively be performed manually, or computer-assisted, or any combination thereof. Likewise, although some steps are described as being performed by a computer, these steps may also be computer-assisted, or performed manually, or any combination thereof.

As discussed above, the designers create message choreographies that specify the sequence of messages between business entities during a transaction. After identifying the messages, the developers identify the fields contained in one of the messages (step 2100, FIG. 21A). The designers then determine whether each field relates to administrative data or is part of the object (step 2102). Thus, the first eleven fields identified below in the left column are related to administrative data, while the remaining fields are part of the object.

MessageID
Admin

ReferenceID

CreationDate

SenderID

AdditionalSenderID

ContactPersonID

SenderAddress

RecipientID

AdditionalRecipientID

ContactPersonID

RecipientAddress

ID
Main Object

AdditionalID

PostingDate

LastChangeDate

AcceptanceStatus

Note

CompleteTransmission Indicator

Buyer

BuyerOrganisationName

Person Name

FunctionalTitle

DepartmentName

CountryCode

StreetPostalCode

POBox Postal Code

Company Postal Code

City Name

DistrictName

PO Box ID

PO Box Indicator

PO Box Country Code

PO Box Region Code

PO Box City Name

Street Name

House ID

Building ID

Floor ID

Room ID

Care Of Name

AddressDescription

Telefonnumber

MobileNumber

Facsimile

Email

Seller

SellerAddress

Location

LocationType

DeliveryItemGroupID

DeliveryPriority

DeliveryCondition

TransferLocation

NumberofPartialDelivery

QuantityTolerance

MaximumLeadTime

TransportServiceLevel

TranportCondition

TransportDescription

CashDiscountTerms

PaymentForm

PaymentCardID

PaymentCardReferenceID

SequenceID

Holder

ExpirationDate

AttachmentID

AttachmentFilename

DescriptionofMessage

ConfirmationDescriptionof Message

FollowUpActivity

ItemID

ParentItemID

HierarchyType

ProductID

ProductType

ProductNote

ProductCategoryID

Amount

BaseQuantity

ConfirmedAmount

ConfirmedBaseQuantity

ItemBuyer

ItemBuyerOrganisationName

Person Name

FunctionalTitle

DepartmentName

CountryCode

StreetPostalCode

POBox Postal Code

Company Postal Code

City Name

DistrictName

PO Box ID

PO Box Indicator

PO Box Country Code

PO Box Region Code

PO Box City Name

Street Name

House ID

Building ID

Floor ID

Room ID

Care Of Name

AddressDescription

Telefonnumber

MobilNumber

Facsimile

Email

ItemSeller

ItemSellerAddress

ItemLocation

ItemLocationType

ItemDeliveryItemGroupID

ItemDeliveryPriority

ItemDeliveryCondition

ItemTransferLocation

ItemNumberofPartialDelivery

ItemQuantityTolerance

ItemMaximumLeadTime

ItemTransportServiceLevel

ItemTranportCondition

ItemTransportDescription

ContractReference

QuoteReference

CatalogueReference

ItemAttachmentID

ItemAttachmentFilename

ItemDescription

ScheduleLineID

DeliveryPeriod

Quantity

ConfirmedScheduleLineID

ConfirmedDeliveryPeriod

ConfirmedQuantity

Next, the designers determine the proper name for the object according to the ISO 11179 naming standards (step 2104). In the example above, the proper name for the “Main Object” is “Purchase Order.” After naming the object, the system that is creating the business object model determines whether the object already exists in the business object model (step 2106). If the object already exists, the system integrates new attributes from the message into the existing object (step 2108), and the process is complete.

If at step 2106 the system determines that the object does not exist in the business object model, the designers model the internal object structure (step 2110). To model the internal structure, the designers define the components. For the above example, the designers may define the components identified below.

ID
Purchase

AdditionalID
Order

PostingDate

LastChangeDate

AcceptanceStatus

Note

CompleteTransmission

Indicator

Buyer

Buyer

BuyerOrganisationName

Person Name

FunctionalTitle

DepartmentName

CountryCode

StreetPostalCode

POBox Postal Code

Company Postal Code

City Name

DistrictName

PO Box ID

PO Box Indicator

PO Box Country Code

PO Box Region Code

PO Box City Name

Street Name

House ID

Building ID

Floor ID

Room ID

Care Of Name

AddressDescription

Telefonnumber

MobileNumber

Facsimile

Email

Seller

Seller

SellerAddress

Location

Location

LocationType

DeliveryItemGroupID

Delivery

DeliveryPriority

Terms

DeliveryCondition

TransferLocation

NumberofPartialDelivery

QuantityTolerance

MaximumLeadTime

TransportServiceLevel

TranportCondition

TransportDescription

CashDiscountTerms

PaymentForm

Payment

PaymentCardID

PaymentCardReferenceID

SequenceID

Holder

ExpirationDate

AttachmentID

AttachmentFilename

DescriptionofMessage

ConfirmationDescriptionof

Message

FollowUpActivity

ItemID

Purchase

ParentItemID

Order

HierarchyType

Item

ProductID

Product

ProductType

ProductNote

ProductCategoryID

ProductCategory

Amount

BaseQuantity

ConfirmedAmount

ConfirmedBaseQuantity

ItemBuyer

Buyer

ItemBuyerOrganisation Name

Person Name

FunctionalTitle

DepartmentName

CountryCode

StreetPostalCode

POBox Postal Code

Company Postal Code

City Name

DistrictName

PO Box ID

PO Box Indicator

PO Box Country Code

PO Box Region Code

PO Box City Name

Street Name

House ID

Building ID

Floor ID

Room ID

Care Of Name

AddressDescription

Telefonnumber

MobilNumber

Facsimile

Email

ItemSeller

Seller

ItemSellerAddress

ItemLocation

Location

ItemLocationType

ItemDeliveryItemGroupID

ItemDeliveryPriority

ItemDeliveryCondition

ItemTransferLocation

ItemNumberofPartial

Delivery

ItemQuantityTolerance

ItemMaximumLeadTime

ItemTransportServiceLevel

ItemTranportCondition

ItemTransportDescription

ContractReference

Contract

QuoteReference

Quote

CatalogueReference

Catalogue

ItemAttachmentID

ItemAttachmentFilename

ItemDescription

ScheduleLineID

DeliveryPeriod

Quantity

ConfirmedScheduleLineID

ConfirmedDeliveryPeriod

ConfirmedQuantity

During the step of modeling the internal structure, the designers also model the complete internal structure by identifying the compositions of the components and the corresponding cardinalities, as shown below.

PurchaseOrder

1

Buyer

0 . . . 1

Address

0 . . . 1

ContactPerson

0 . . . 1

Address
0 . . . 1

Seller

0 . . . 1

Location

0 . . . 1

Address

0 . . . 1

DeliveryTerms

0 . . . 1

Incoterms

0 . . . 1

PartialDelivery

0 . . . 1

QuantityTolerance

0 . . . 1

Transport

0 . . . 1

CashDiscount

0 . . . 1

Terms

MaximumCashDiscount

0 . . . 1

NormalCashDiscount

0 . . . 1

PaymentForm

0 . . . 1

PaymentCard

0 . . . 1

Attachment

0 . . . n

Description

0 . . . 1

Confirmation

0 . . . 1

Description

Item

0 . . . n

HierarchyRelationship

0 . . . 1

Product

0 . . . 1

ProductCategory

0 . . . 1

Price

0 . . . 1

NetunitPrice
0 . . . 1

ConfirmedPrice

0 . . . 1

NetunitPrice
0 . . . 1

Buyer

0 . . . 1

Seller

0 . . . 1

Location

0 . . . 1

DeliveryTerms

0 . . . 1

Attachment

0 . . . n

Description

0 . . . 1

ConfirmationDescription

0 . . . 1

ScheduleLine

0 . . . n

DeliveryPeriod
1

ConfirmedScheduleLine

0 . . . n

After modeling the internal object structure, the developers identify the subtypes and generalizations for all objects and components (step 2112). For example, the Purchase Order may have subtypes Purchase Order Update, Purchase Order Cancellation and Purchase Order Information. Purchase Order Update may include Purchase Order Request, Purchase Order Change, and Purchase Order Confirmation. Moreover, Party may be identified as the generalization of Buyer and Seller. The subtypes and generalizations for the above example are shown below.

PurchaseOrder

1

PurchaseOrder

Update

PurchaseOrder Request

PurchaseOrder Change

PurchaseOrder

Confirmation

PurchaseOrder

Cancellation

PurchaseOrder

Information

Party

BuyerParty

0 . . . 1

Address

0 . . . 1

ContactPerson

0 . . . 1

Address
0 . . . 1

SellerParty

0 . . . 1

Location

ShipToLocation

0 . . . 1

Address

0 . . . 1

ShipFromLocation

0 . . . 1

Address

0 . . . 1

DeliveryTerms

0 . . . 1

Incoterms

0 . . . 1

PartialDelivery

0 . . . 1

QuantityTolerance

0 . . . 1

Transport

0 . . . 1

CashDiscount Terms

0 . . . 1

MaximumCash Discount

0 . . . 1

NormalCashDiscount

0 . . . 1

PaymentForm

0 . . . 1

PaymentCard

0 . . . 1

Attachment

0 . . . n

Description

0 . . . 1

Confirmation

0 . . . 1

Description

Item

0 . . . n

HierarchyRelationship

0 . . . 1

Product

0 . . . 1

ProductCategory

0 . . . 1

Price

0 . . . 1

NetunitPrice

0 . . . 1

ConfirmedPrice

0 . . . 1

NetunitPrice

0 . . . 1

Party

BuyerParty

0 . . . 1

SellerParty

0 . . . 1

Location

ShipTo

0 . . . 1

Location

ShipFrom

0 . . . 1

Location

DeliveryTerms

0 . . . 1

Attachment

0 . . . n

Description

0 . . . 1

Confirmation Description

0 . . . 1

ScheduleLine

0 . . . n

Delivery

1

Period

ConfirmedScheduleLine

0 . . . n

After identifying the subtypes and generalizations, the developers assign the attributes to these components (step 2114). The attributes for a portion of the components are shown below.

Purchase

1

Order

ID

1

SellerID

0 . . . 1

BuyerPosting

0 . . . 1

DateTime

BuyerLast

0 . . . 1

ChangeDate

Time

SellerPosting

0 . . . 1

DateTime

SellerLast

0 . . . 1

ChangeDate

Time

Acceptance

0 . . . 1

StatusCode

Note

0 . . . 1

ItemList

0 . . . 1

Complete

Transmission

Indicator

BuyerParty

0 . . . 1

StandardID

0 . . . n

BuyerID

0 . . . 1

SellerID

0 . . . 1

Address

0 . . . 1

ContactPerson

0 . . . 1

BuyerID

0 . . . 1

SellerID

0 . . . 1

Address

0 . . . 1

SellerParty

0 . . . 1

Product

0 . . . 1

RecipientParty

VendorParty

0 . . . 1

Manufacturer

0 . . . 1

Party

BillToParty

0 . . . 1

PayerParty

0 . . . 1

CarrierParty

0 . . . 1

ShipTo

0 . . . 1

Location

StandardID

0 . . . n

BuyerID

0 . . . 1

SellerID

0 . . . 1

Address

0 . . . 1

ShipFrom

0 . . . 1

Location

The system then determines whether the component is one of the object nodes in the business object model (step 2116, FIG. 21B). If the system determines that the component is one of the object nodes in the business object model, the system integrates a reference to the corresponding object node from the business object model into the object (step 2118). In the above example, the system integrates the reference to the Buyer party represented by an ID and the reference to the ShipToLocation represented by an into the object, as shown below. The attributes that were formerly located in the PurchaseOrder object are now assigned to the new found object party. Thus, the attributes are removed from the PurchaseOrder object.

PurchaseOrder
ID

SellerID

BuyerPostingDateTime

BuyerLastChangeDateTime

SellerPostingDateTime

SellerLastChangeDateTime

AcceptanceStatusCode

Note

ItemListComplete

TransmissionIndicator

BuyerParty

ID

SellerParty

ProductRecipientParty

VendorParty

ManufacturerParty

BillToParty

PayerParty

CarrierParty

ShipToLocation

ID

ShipFromLocation

During the integration step, the designers classify the relationship (i.e., aggregation or association) between the object node and the object being integrated into the business object model. The system also integrates the new attributes into the object node (step 2120). If at step 2116, the system determines that the component is not in the business object model, the system adds the component to the business object model (step 2122).

Regardless of whether the component was in the business object model at step 2116, the next step in creating the business object model is to add the integrity rules (step 2124). There are several levels of integrity rules and constraints which should be described. These levels include consistency rules between attributes, consistency rules between components, and consistency rules to other objects. Next, the designers determine the services offered, which can be accessed via interfaces (step 2126). The services offered in the example above include PurchaseOrderCreateRequest, PurchaseOrderCancellationRequest, and PurchaseOrderReleaseRequest. The system then receives an indication of the location for the object in the business object model (step 2128). After receiving the indication of the location, the system integrates the object into the business object model (step 2130).

4. Structure of the Business Object Model

The business object model, which serves as the basis for the process of generating consistent interfaces, includes the elements contained within the interfaces. These elements are arranged in a hierarchical structure within the business object model.

5. Interfaces Derived from Business Object Model

Interfaces are the starting point of the communication between two business entities. The structure of each interface determines how one business entity communicates with another business entity. The business entities may act as a unified whole when, based on the business scenario, the business entities know what an interface contains from a business perspective and how to fill the individual elements or fields of the interface. As illustrated in FIG. 27A, communication between components takes place via messages that contain business documents (e.g., business document 27002). The business document 27002 ensures a holistic business-related understanding for the recipient of the message. The business documents are created and accepted or consumed by interfaces, specifically by inbound and outbound interfaces. The interface structure and, hence, the structure of the business document are derived by a mapping rule. This mapping rule is known as “hierarchization.” An interface structure thus has a hierarchical structure created based on the leading business object 27000. The interface represents a usage-specific, hierarchical view of the underlying usage-neutral object model.

As illustrated in FIG. 27B, several business document objects 27006, 27008, and 27010 as overlapping views may be derived for a given leading object 27004. Each business document object results from the object model by hierarchization.

To illustrate the hierarchization process, FIG. 27C depicts an example of an object model 27012 (i.e., a portion of the business object model) that is used to derive a service operation signature (business document object structure). As depicted, leading object X 27014 in the object model 27012 is integrated in a net of object A 27016, object B 27018, and object C 27020. Initially, the parts of the leading object 27014 that are required for the business object document are adopted. In one variation, all parts required for a business document object are adopted from leading object 27014 (making such an operation a maximal service operation). Based on these parts, the relationships to the superordinate objects (i.e., objects A, B, and C from which object X depends) are inverted. In other words, these objects are adopted as dependent or subordinate objects in the new business document object.

For example, object A 27016, object B 27018, and object C 27020 have information that characterize object X. Because object A 27016, object B 27018, and object C 27020 are superordinate to leading object X 27014, the dependencies of these relationships change so that object A 27016, object B 27018, and object C 27020 become dependent and subordinate to leading object X 27014. This procedure is known as “derivation of the business document object by hierarchization.”

Business-related objects generally have an internal structure (parts). This structure can be complex and reflect the individual parts of an object and their mutual dependency. When creating the operation signature, the internal structure of an object is strictly hierarchized. Thus, dependent parts keep their dependency structure, and relationships between the parts within the object that do not represent the hierarchical structure are resolved by prioritizing one of the relationships.

Relationships of object X to external objects that are referenced and whose information characterizes object X are added to the operation signature. Such a structure can be quite complex (see, for example, FIG. 27D). The cardinality to these referenced objects is adopted as 1:1 or 1:C, respectively. By this, the direction of the dependency changes. The required parts of this referenced object are adopted identically, both in their cardinality and in their dependency arrangement.

The newly created business document object contains all required information, including the incorporated master data information of the referenced objects. As depicted in FIG. 27D, components Xi in leading object X 27022 are adopted directly. The relationship of object X 27022 to object A 27024, object B 27028, and object C 27026 are inverted, and the parts required by these objects are added as objects that depend from object X 27022. As depicted, all of object A 27024 is adopted. B3 and B4 are adopted from object B 27028, but B1 is not adopted. From object C 27026, C2 and C1 are adopted, but C3 is not adopted.

FIG. 27E depicts the business document object X 27030 created by this hierarchization process. As shown, the arrangement of the elements corresponds to their dependency levels, which directly leads to a corresponding representation as an XML structure 27032.

The following provides certain rules that can be adopted singly or in combination with regard to the hierarchization process. A business document object always refers to a leading business document object and is derived from this object. The name of the root entity in the business document entity is the name of the business object or the name of a specialization of the business object or the name of a service specific view onto the business object. The nodes and elements of the business object that are relevant (according to the semantics of the associated message type) are contained as entities and elements in the business document object.

The name of a business document entity is predefined by the name of the corresponding business object node. The name of the superordinate entity is not repeated in the name of the business document entity. The “full” semantic name results from the concatenation of the entity names along the hierarchical structure of the business document object.

The structure of the business document object is, except for deviations due to hierarchization, the same as the structure of the business object. The cardinalities of the business document object nodes and elements are adopted identically or more restrictively to the business document object. An object from which the leading business object is dependent can be adopted to the business document object. For this arrangement, the relationship is inverted, and the object (or its parts, respectively) are hierarchically subordinated in the business document object.

Nodes in the business object representing generalized business information can be adopted as explicit entities to the business document object (generally speaking, multiply TypeCodes out). When this adoption occurs, the entities are named according to their more specific semantic (name of TypeCode becomes prefix). Party nodes of the business object are modeled as explicit entities for each party role in the business document object. These nodes are given the name <Prefix><Party Role>Party, for example, BuyerParty, ItemBuyerParty. BTDReference nodes are modeled as separate entities for each reference type in the business document object. These nodes are given the name <Qualifier><BO><Node>Reference, for example SalesOrderReference, OriginSalesOrderReference, SalesOrderItemReference. A product node in the business object comprises all of the information on the Product, ProductCategory, and Batch. This information is modeled in the business document object as explicit entities for Product, ProductCategory, and Batch.

Entities which are connected by a 1:1 relationship as a result of hierarchization can be combined to a single entity, if they are semantically equivalent. Such a combination can often occurs if a node in the business document object that results from an assignment node is removed because it does not have any elements.

The message type structure is typed with data types. Elements are typed by GDTs according to their business objects. Aggregated levels are typed with message type specific data types (Intermediate Data Types), with their names being built according to the corresponding paths in the message type structure. The whole message type structured is typed by a message data type with its name being built according to the root entity with the suffix “Message.” For the message type, the message category (e.g., information, notification, query, response, request, confirmation, etc.) is specified according to the suited transaction communication pattern.

In one variation, the derivation by hierarchization can be initiated by specifying a leading business object and a desired view relevant for a selected service operation. This view determines the business document object. The leading business object can be the source object, the target object, or a third object. Thereafter, the parts of the business object required for the view are determined. The parts are connected to the root node via a valid path along the hierarchy. Thereafter, one or more independent objects (object parts, respectively) referenced by the leading object which are relevant for the service may be determined (provided that a relationship exists between the leading object and the one or more independent objects).

Once the selection is finalized, relevant nodes of the leading object node that are structurally identical to the message type structure can then be adopted. If nodes are adopted from independent objects or object parts, the relationships to such independent objects or object parts are inverted. Linearization can occur such that a business object node containing certain TypeCodes is represented in the message type structure by explicit entities (an entity for each value of the TypeCode). The structure can be reduced by checking all 1:1 cardinalities in the message type structure. Entities can be combined if they are semantically equivalent, one of the entities carries no elements, or an entity solely results from an n:m assignment in the business object.

After the hierarchization is completed, information regarding transmission of the business document object (e.g., CompleteTransmissionIndicator, ActionCodes, message category, etc.) can be added. A standardized message header can be added to the message type structure and the message structure can be typed. Additionally, the message category for the message type can be designated.

Invoice Request and Invoice Confirmation are examples of interfaces. These invoice interfaces are used to exchange invoices and invoice confirmations between an invoicing party and an invoice recipient (such as between a seller and a buyer) in a B2B process. Companies can create invoices in electronic as well as in paper form. Traditional methods of communication, such as mail or fax, for invoicing are cost intensive, prone to error, and relatively slow, since the data is recorded manually. Electronic communication eliminates such problems. The motivating business scenarios for the Invoice Request and Invoice Confirmation interfaces are the Procure to Stock (PTS) and Sell from Stock (SFS) scenarios. In the PTS scenario, the parties use invoice interfaces to purchase and settle goods. In the SFS scenario, the parties use invoice interfaces to sell and invoice goods. The invoice interfaces directly integrate the applications implementing them and also form the basis for mapping data to widely-used XML standard formats such as RosettaNet, PIDX, xCBL, and CIDX.

The invoicing party may use two different messages to map a B2B invoicing process: (1) the invoicing party sends the message type InvoiceRequest to the invoice recipient to start a new invoicing process; and (2) the invoice recipient sends the message type InvoiceConfirmation to the invoicing party to confirm or reject an entire invoice or to temporarily assign it the status “pending.”

An InvoiceRequest is a legally binding notification of claims or liabilities for delivered goods and rendered services—usually, a payment request for the particular goods and services. The message type InvoiceRequest is based on the message data type InvoiceMessage. The InvoiceRequest message (as defined) transfers invoices in the broader sense. This includes the specific invoice (request to settle a liability), the debit memo, and the credit memo.

InvoiceConfirmation is a response sent by the recipient to the invoicing party confirming or rejecting the entire invoice received or stating that it has been assigned temporarily the status “pending.” The message type InvoiceConfirmation is based on the message data type InvoiceMessage. An InvoiceConfirmation is not mandatory in a B2B invoicing process, however, it automates collaborative processes and dispute management.

Usually, the invoice is created after it has been confirmed that the goods were delivered or the service was provided. The invoicing party (such as the seller) starts the invoicing process by sending an InvoiceRequest message. Upon receiving the InvoiceRequest message, the invoice recipient (for instance, the buyer) can use the InvoiceConfirmation message to completely accept or reject the invoice received or to temporarily assign it the status “pending.” The InvoiceConfirmation is not a negotiation tool (as is the case in order management), since the options available are either to accept or reject the entire invoice. The invoice data in the InvoiceConfirmation message merely confirms that the invoice has been forwarded correctly and does not communicate any desired changes to the invoice. Therefore, the InvoiceConfirmation includes the precise invoice data that the invoice recipient received and checked. If the invoice recipient rejects an invoice, the invoicing party can send a new invoice after checking the reason for rejection (AcceptanceStatus and ConfirmationDescription at Invoice and InvoiceItem level). If the invoice recipient does not respond, the invoice is generally regarded as being accepted and the invoicing party can expect payment.

FIGS. 22A-F depict a flow diagram of the steps performed by methods and systems consistent with the subject matter described herein to generate an interface from the business object model. Although described as being performed by a computer, these steps may alternatively be performed manually, or using any combination thereof. The process begins when the system receives an indication of a package template from the designer, i.e., the designer provides a package template to the system (step 2200).

Package templates specify the arrangement of packages within a business transaction document. Package templates are used to define the overall structure of the messages sent between business entities. Methods and systems consistent with the subject matter described herein use package templates in conjunction with the business object model to derive the interfaces.

The system also receives an indication of the message type from the designer (step 2202). The system selects a package from the package template (step 2204), and receives an indication from the designer whether the package is required for the interface (step 2206). If the package is not required for the interface, the system removes the package from the package template (step 2208). The system then continues this analysis for the remaining packages within the package template (step 2210).

If, at step 2206, the package is required for the interface, the system copies the entity template from the package in the business object model into the package in the package template (step 2212, FIG. 22B). The system determines whether there is a specialization in the entity template (step 2214). If the system determines that there is a specialization in the entity template, the system selects a subtype for the specialization (step 2216). The system may either select the subtype for the specialization based on the message type, or it may receive this information from the designer. The system then determines whether there are any other specializations in the entity template (step 2214). When the system determines that there are no specializations in the entity template, the system continues this analysis for the remaining packages within the package template (step 2210, FIG. 22A).

At step 2210, after the system completes its analysis for the packages within the package template, the system selects one of the packages remaining in the package template (step 2218, FIG. 22C), and selects an entity from the package (step 2220). The system receives an indication from the designer whether the entity is required for the interface (step 2222). If the entity is not required for the interface, the system removes the entity from the package template (step 2224). The system then continues this analysis for the remaining entities within the package (step 2226), and for the remaining packages within the package template (step 2228).

If, at step 2222, the entity is required for the interface, the system retrieves the cardinality between a superordinate entity and the entity from the business object model (step 2230, FIG. 22D). The system also receives an indication of the cardinality between the superordinate entity and the entity from the designer (step 2232). The system then determines whether the received cardinality is a subset of the business object model cardinality (step 2234). If the received cardinality is not a subset of the business object model cardinality, the system sends an error message to the designer (step 2236). If the received cardinality is a subset of the business object model cardinality, the system assigns the received cardinality as the cardinality between the superordinate entity and the entity (step 2238). The system then continues this analysis for the remaining entities within the package (step 2226, FIG. 22C), and for the remaining packages within the package template (step 2228).

The system then selects a leading object from the package template (step 2240, FIG. 22E). The system determines whether there is an entity superordinate to the leading object (step 2242). If the system determines that there is an entity superordinate to the leading object, the system reverses the direction of the dependency (step 2244) and adjusts the cardinality between the leading object and the entity (step 2246). The system performs this analysis for entities that are superordinate to the leading object (step 2242). If the system determines that there are no entities superordinate to the leading object, the system identifies the leading object as analyzed (step 2248).

The system then selects an entity that is subordinate to the leading object (step 2250, FIG. 22F). The system determines whether any non-analyzed entities are superordinate to the selected entity (step 2252). If a non-analyzed entity is superordinate to the selected entity, the system reverses the direction of the dependency (step 2254) and adjusts the cardinality between the selected entity and the non-analyzed entity (step 2256). The system performs this analysis for non-analyzed entities that are superordinate to the selected entity (step 2252). If the system determines that there are no non-analyzed entities superordinate to the selected entity, the system identifies the selected entity as analyzed (step 2258), and continues this analysis for entities that are subordinate to the leading object (step 2260). After the packages have been analyzed, the system substitutes the BusinessTransactionDocument (“BTD”) in the package template with the name of the interface (step 2262). This includes the “BTD” in the BTDItem package and the “BTD” in the BTDItemScheduleLine package.

6. Use of an Interface

The XI stores the interfaces (as an interface type). At runtime, the sending party's program instantiates the interface to create a business document, and sends the business document in a message to the recipient. The messages are preferably defined using XML. In the example depicted in FIG. 23, the Buyer 2300 uses an application 2306 in its system to instantiate an interface 2308 and create an interface object or business document object 2310. The Buyer's application 2306 uses data that is in the sender's component-specific structure and fills the business document object 2310 with the data. The Buyer's application 2306 then adds message identification 2312 to the business document and places the business document into a message 2302. The Buyer's application 2306 sends the message 2302 to the Vendor 2304. The Vendor 2304 uses an application 2314 in its system to receive the message 2302 and store the business document into its own memory. The Vendor's application 2314 unpacks the message 2302 using the corresponding interface 2316 stored in its XI to obtain the relevant data from the interface object or business document object 2318.

From the component's perspective, the interface is represented by an interface proxy 2400, as depicted in FIG. 24. The proxies 2400 shield the components 2402 of the sender and recipient from the technical details of sending messages 2404 via XI. In particular, as depicted in FIG. 25, at the sending end, the Buyer 2500 uses an application 2510 in its system to call an implemented method 2512, which generates the outbound proxy 2506. The outbound proxy 2506 parses the internal data structure of the components and converts them to the XML structure in accordance with the business document object. The outbound proxy 2506 packs the document into a message 2502. Transport, routing and mapping the XML message to the recipient 28304 is done by the routing system (XI, modeling environment 516, etc.).

When the message arrives, the recipient's inbound proxy 2508 calls its component-specific method 2514 for creating a document. The proxy 2508 at the receiving end downloads the data and converts the XML structure into the internal data structure of the recipient component 2504 for further processing.

As depicted in FIG. 26A, a message 2600 includes a message header 2602 and a business document 2604. The message 2600 also may include an attachment 2606. For example, the sender may attach technical drawings, detailed specifications or pictures of a product to a purchase order for the product. The business document 2604 includes a business document message header 2608 and the business document object 2610. The business document message header 2608 includes administrative data, such as the message ID and a message description. As discussed above, the structure 2612 of the business document object 2610 is derived from the business object model 2614. Thus, there is a strong correlation between the structure of the business document object and the structure of the business object model. The business document object 2610 forms the core of the message 2600.

In collaborative processes as well as Q&A processes, messages should refer to documents from previous messages. A simple business document object ID or object ID is insufficient to identify individual messages uniquely because several versions of the same business document object can be sent during a transaction. A business document object ID with a version number also is insufficient because the same version of a business document object can be sent several times. Thus, messages require several identifiers during the course of a transaction.

As depicted in FIG. 26B, the message header 2618 in message 2616 includes a technical ID (“ID4”) 2622 that identifies the address for a computer to route the message. The sender's system manages the technical ID 2622.

The administrative information in the business document message header 2624 of the payload or business document 2620 includes a BusinessDocumentMessageID (“ID3”) 2628. The business entity or component 2632 of the business entity manages and sets the BusinessDocumentMessageID 2628. The business entity or component 2632 also can refer to other business documents using the BusinessDocumentMessageID 2628. The receiving component 2632 requires no knowledge regarding the structure of this ID. The BusinessDocumentMessageID 2628 is, as an ID, unique. Creation of a message refers to a point in time. No versioning is typically expressed by the ID. Besides the BusinessDocumentMessageID 2628, there also is a business document object ID 2630, which may include versions.

The component 2632 also adds its own component object ID 2634 when the business document object is stored in the component. The component object ID 2634 identifies the business document object when it is stored within the component. However, not all communication partners may be aware of the internal structure of the component object ID 2634. Some components also may include a versioning in their ID 2634.

7. Use of Interfaces Across Industries

Methods and systems consistent with the subject matter described herein provide interfaces that may be used across different business areas for different industries. Indeed, the interfaces derived using methods and systems consistent with the subject matter described herein may be mapped onto the interfaces of different industry standards. Unlike the interfaces provided by any given standard that do not include the interfaces required by other standards, methods and systems consistent with the subject matter described herein provide a set of consistent interfaces that correspond to the interfaces provided by different industry standards. Due to the different fields provided by each standard, the interface from one standard does not easily map onto another standard. By comparison, to map onto the different industry standards, the interfaces derived using methods and systems consistent with the subject matter described herein include most of the fields provided by the interfaces of different industry standards. Missing fields may easily be included into the business object model. Thus, by derivation, the interfaces can be extended consistently by these fields. Thus, methods and systems consistent with the subject matter described herein provide consistent interfaces or services that can be used across different industry standards.

For example, FIG. 28 illustrates an example method 2800 for service enabling. In this example, the enterprise services infrastructure may offer one common and standard-based service infrastructure. Further, one central enterprise services repository may support uniform service definition, implementation and usage of services for user interface, and cross-application communication. In step 2801, a business object is defined via a process component model in a process modeling phase. Next, in step 2802, the business object is designed within an enterprise services repository. For example, FIG. 29 provides a graphical representation of one of the business objects 2900. As shown, an innermost layer or kernel 2901 of the business object may represent the business object's inherent data. Inherent data may include, for example, an employee's name, age, status, position, address, etc. A second layer 2902 may be considered the business object's logic. Thus, the layer 2902 includes the rules for consistently embedding the business object in a system environment as well as constraints defining values and domains applicable to the business object. For example, one such constraint may limit sale of an item only to a customer with whom a company has a business relationship. A third layer 2903 includes validation options for accessing the business object. For example, the third layer 2903 defines the business object's interface that may be interfaced by other business objects or applications. A fourth layer 2904 is the access layer that defines technologies that may externally access the business object.

Accordingly, the third layer 2903 separates the inherent data of the first layer 2901 and the technologies used to access the inherent data. As a result of the described structure, the business object reveals only an interface that includes a set of clearly defined methods. Thus, applications access the business object via those defined methods. An application wanting access to the business object and the data associated therewith usually includes the information or data to execute the clearly defined methods of the business object's interface. Such clearly defined methods of the business object's interface represent the business object's behavior. That is, when the methods are executed, the methods may change the business object's data. Therefore, an application may utilize any business object by providing the information or data without having any concern for the details related to the internal operation of the business object. Returning to method 2800, a service provider class and data dictionary elements are generated within a development environment at step 2803. In step 2804, the service provider class is implemented within the development environment.

FIG. 30 illustrates an example method 3000 for a process agent framework. For example, the process agent framework may be the basic infrastructure to integrate business processes located in different deployment units. It may support a loose coupling of these processes by message based integration. A process agent may encapsulate the process integration logic and separate it from business logic of business objects. As shown in FIG. 30, an integration scenario and a process component interaction model are defined during a process modeling phase in step 3001. In step 3002, required interface operations and process agents are identified during the process modeling phase also. Next, in step 3003, a service interface, service interface operations, and the related process agent are created within an enterprise services repository as defined in the process modeling phase. In step 3004, a proxy class for the service interface is generated. Next, in step 3005, a process agent class is created and the process agent is registered. In step 3006, the agent class is implemented within a development environment.

FIG. 31 illustrates an example method 3100 for status and action management (S&AM). For example, status and action management may describe the life cycle of a business object (node) by defining actions and statuses (as their result) of the business object (node), as well as, the constraints that the statuses put on the actions. In step 3101, the status and action management schemas are modeled per a relevant business object node within an enterprise services repository. In step 3102, existing statuses and actions from the business object model are used or new statuses and actions are created. Next, in step 3103, the schemas are simulated to verify correctness and completeness. In step 3104, missing actions, statuses, and derivations are created in the business object model with the enterprise services repository. Continuing with method 3100, the statuses are related to corresponding elements in the node in step 3105. In step 3106, status code GDT's are generated, including constants and code list providers. Next, in step 3107, a proxy class for a business object service provider is generated and the proxy class S&AM schemas are imported. In step 3108, the service provider is implemented and the status and action management runtime interface is called from the actions.

Regardless of the particular hardware or software architecture used, the disclosed systems or software are generally capable of implementing business objects and deriving (or otherwise utilizing) consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business in accordance with some or all of the following description. In short, system 100 contemplates using any appropriate combination and arrangement of logical elements to implement some or all of the described functionality.

Moreover, the preceding flowcharts and accompanying description illustrate example methods. The present services environment contemplates using or implementing any suitable technique for performing these and other tasks. It will be understood that these methods are for illustration purposes only and that the described or similar techniques may be performed at any appropriate time, including concurrently, individually, or in combination. In addition, many of the steps in these flowcharts may take place simultaneously and/or in different orders than as shown. Moreover, the services environment may use methods with additional steps, fewer steps, and/or different steps, so long as the methods remain appropriate.

FIGS. 32-1 through 32-7 depict an example object model for a business object Goods Tag 32000. The business object 32000 has relationships with other objects 32002-32048, as shown with lines and arrows. The business object 32000 hierarchically comprises elements 32050-32068. The other objects 32002-32048 include respective elements 32070-32140 as shown.

The business object Goods Tag is an electronic device, a small piece or part, or a label that is attached to a product or package and that includes selected information about this product or package. It can present this information to a reader. The process component Goods Tag Processing includes the business object Goods Tag. The selected information can include descriptive and/or identification data. The observer can be a person or a technical device, such as, a bar code reader, a camera, or an RFID reader. Goods tags can be paper tags with or without bar codes, or RFID tags or transponders. They can be used for manual processes and/or in conjunction with bar code or RFID technology. In some implementations, Goods tags may not be used for tagging objects other than products or packages.

The Goods Tag business object includes information that will be printed on the tag, as well as a reference to the business transaction document that was the basis for the creation of the goods tag. It includes additional references to business transaction documents whose identifiers could be additionally printed on the label. It includes a text and an attachment that can be printed on the label.

The Goods Tag business object is involved in the Goods Tag ProcessingGoods Tag Processing process component interaction model. The technical name for Service Interface Goods Tag Output Out is GoodsTagProcessingGoodsTagOutputOut. The Service Interface Goods Tag Output Out is part of the Goods Tag ProcessingGoods Tag Processing process component interaction model. The Service Interface Goods Tag Output Out is an interface to group the operations that request the output of goods tags.

The technical name for Notify of Uniform Content Package Tag is GoodsTagProcessingGoodsTagOutputOut.NotifyOfUniformContentPackageTag. The Notify of Uniform Content Package Tag can request the output of goods tags of the type “uniform content package tag.” The operation can be based on message type Form Uniform Content Package Tag Notification (derived from business object Goods Tag).

The technical name for Notify of Unspecified Content Package Tag is GoodsTagProcessingGoodsTagOutputOut.NotifyOfUnspecifiedContentPackageTag. The Notify of Unspecified Content Package Tag can request the output of goods tags of the type “unspecified content package tag.” The operation can be based on message type Form Unspecified Content Package Tag Notification (derived from business object Goods Tag).

The technical name for Notify of Serialised Material Tag is GoodsTagProcessingGoodsTagOutputOut.NotifyOfSerialisedMaterialTag. The Notify of Serialised Material Tag can request the output of goods tags of the type “serialised material tag.” The operation can be based on message type Form Serialised Material Tag Notification (derived from business object Goods Tag).

The business object Goods Tag is an electronic device, a small piece or part, or a label that includes selected information about a product or package. The Goods Tag can occur in the following specializations: Unspecified Content Package Tag, Uniform Content Package Tag, Serialised Material Tag, and Mixed Content Package Tag. In some implementations, specialization type Goods Tag can be implemented by Type Attribute.

The elements located at the node Goods Tag can be defined by the data type GoodsTagElements. These elements include: UUID, ID, PartySerialID, IndividualMaterialUUID, TypeCode, CreationContextCode, MaterialQuantity, MaterialQuantityTypeCode, BaseBusinessTransactionDocumentReference, ShippingDate ProductionDate, ReceiptDate, MaterialUUID, GlobalTradeItemNumberID, IdentifiedStockUUID, ProductRequirementSpecificationVersionUUID, LogisticUnitUUID, LogisticUnitStandardMaterialContentUUID, ResourceUUID, SiteUUID, LogisticsAreaUUID, BuyerPartyUUID, SellerPartyUUID, RecipientPartyUUID, VendorPartyUUID, CarrierPartyUUID, FreightForwarderPartyUUID, GrossWeightMeasure, GrossWeightMeasureTypeCode, GrossVolumeMeasure, GrossVolumeMeasureTypeCode, ShippingPackageAttachedIndicator, Incoterms, ProductSellerID, SystemAdministrativeData, GoodsTagAssignmentObjectNodeReference, IdentifiedLogisticUnitUUID, and TransportTracking.

UUID is a globally unique identifier and alternative key for a goods tag. It may be based on datatype GDT: UUID. In some implementations, UUID is used as an alternative key. ID is an identifier and alternative key for a goods tag. It may be based on datatype GDT: GoodsTagID. In some implementations, ID is used as an alternative key. PartySerialID is an identifier for an individual piece of material that is defined by an external system or party. It may be based on datatype GDT: SerialID, Qualifier: Party. IndividualMaterialUUID is a globally unique identifier for an individual piece of material. It may be based on datatype GDT: UUID. TypeCode is a coded representation of the type of the goods tag. It may be based on datatype GDT: GoodsTagTypeCode. CreationContextCode is a coded representation of the context within which the goods tag was created, for example, Inbound, Outbound, or Production. It may be based on datatype GDT: GoodsTagCreationContextCode. MaterialQuantity is a quantity of the tagged product or package content. It may be based on datatype GDT: Quantity, Qualifier: Material. MaterialQuantityTypeCode is a coded representation of the quantity type of the tagged product or package content. It may be based on datatype GDT: QuantityTypeCode, Qualifier: Material. BaseBusinessTransactionDocumentReference is a reference to the business transaction document that was the basis for the creation of the goods tag. It may be based on datatype GDT: BusinessTransactionDocumentReference, Qualifier: Base. ShippingDate represents a point in time at which the tagged product or package is shipped. It may be based on datatype GDT: Date, Qualifier: Shipping. ProductionDate represents a point in time at which the tagged product or package content is produced. It may be based on datatype GDT: Date, Qualifier: Production. ReceiptDate represents a point in time at which the tagged product or package is received. It may be based on datatype GDT: Date, Qualifier: Receipt. MaterialUUID is a globally unique identifier for the material that is tagged by the goods tag or that is included in the tagged package. It may be based on datatype GDT: UUID. GlobalTradeItemNumberID is a quantity-dependent identifier for the product following the European Article Numbering and Uniform Code Council system. It may be based on datatype GDT: ProductStandardID. IdentifiedStockUUID is a globally unique identifier for the identified stock of the tagged product or of the content of the tagged package. It may be based on datatype GDT: UUID. ProductRequirementSpecificationVersionUUID is a globally unique identifier for the product requirement specification version that specifies the tagged product or the content of the tagged package. It may be based on datatype GDT: UUID. LogisticUnitUUID is a globally unique identifier for the logistic unit of the package that is tagged by the goods tag. It may be based on datatype GDT: UUID. LogisticUnitStandardMaterialContentUUID is a globally unique identifier for the standard material content of the assigned logistic unit for the assigned material. It may be based on datatype GDT: UUID. ResourceUUID is a globally unique identifier for the resource that was used to produce the tagged product or the content of the tagged package. It may be based on datatype GDT: UUID. SiteUUID is a globally unique identifier for the site that is assigned to the goods tag. It may be based on datatype GDT: UUID. LogisticsAreaUUID is a globally unique identifier for the logistics area that is assigned to the goods tag. It may be based on datatype GDT: UUID. BuyerPartyUUID is a globally unique identifier for the party who buys the tagged product or package. It may be based on datatype GDT: UUID. SellerPartyUUID is a globally unique identifier for the party who sells the tagged product or package. It may be based on datatype GDT: UUID. RecipientPartyUUID is a globally unique identifier for the party who receives the tagged product or package. It may be based on datatype GDT: UUID. VendorPartyUUID is a globally unique identifier for the party who delivers the tagged product or package. It may be based on datatype GDT: UUID. CarrierPartyUUID is a globally unique identifier for the party responsible for the transportation of the tagged product or package. It may be based on datatype GDT: UUID. FreightForwarderPartyUUID is a globally unique identifier for the party responsible for organizing the transportation of the tagged product or package. It may be based on datatype GDT: UUID. GrossWeightMeasure is a measure for the gross weight of the tagged product or package. It may be based on datatype GDT: Measure, Qualifier: GrossWeight. GrossWeightMeasureTypeCode is a coded representation of the gross weight type of the tagged product or package. It may be based on datatype GDT: MeasureTypeCode, Qualifier: GrossWeight. GrossVolumeMeasure is a measure for the gross volume of the tagged product or package. It may be based on datatype GDT: Measure, Qualifier: GrossVolume. GrossVolumeMeasureTypeCode is a coded representation of the gross volume type of the tagged product or package. It may be based on datatype GDT: MeasureTypeCode, Qualifier: GrossVolume. ShippingPackageAttachedIndicator is an indicator that specifies whether the goods tag is attached to a shipping package. It may be based on datatype GDT: Indicator, Qualifier: Attached. Incoterms represents contract formulations for the delivery of the tagged product or package. It may be based on datatype GDT: Incoterms. ProductSellerID is an identifier for the tagged product that was defined by the seller of the tagged product or package. It may be based on datatype GDT: ProductPartyID. ProductBuyerID is an identifier for the tagged product that was defined by the buyer of the tagged product or package. It may be based on datatype GDT: ProductPartyID. SystemAdministrativeData is administrative data recorded by the system. This data includes system users and change dates or times. It may be based on datatype GDT: SystemAdministrativeData. GoodsTagAssignmentObjectNodeReference is a generic reference to the node to which the goods tag shall be assigned automatically. It may be based on datatype GDT: ObjectNodeReference. IdentifiedLogisticUnitUUID is a globally unique identifier for the identified logistic unit that is tagged by the goods tag. It may be based on datatype GDT: UUID. TransportTracking is transport-related information that can be used for tracking the tagged product or package. It may be based on datatype GDT: TransportTracking.

A composition relationship to a BusinessTransactionDocumentReference subordinate node can exist with a 1:CN cardinality relationship. This relationship may be filtered. The filter elements can be defined by the data type GoodsTagBusinessTransactionDocumentReferenceFilterElements. These elements include BusinessTransactionDocumentTypeCode and BusinessTransactionDocumentItemTypeCode. BusinessTransactionDocumentTypeCode may be based on datatype GDT: BusinessTransactionDocumentTypeCode. BusinessTransactionDocumentItemTypeCode may be based on datatype GDT: BusinessTransactionDocumentItemTypeCode. A composition relationship to a Location subordinate node can exist in a 1:CN cardinality relationship. A composition relationship to a ControlledOutputRequest subordinate node can exist in a 1:1 cardinality relationship. A composition relationship to a TextCollection subordinate node can exist in a 1:C cardinality relationship.

An inbound aggregation relationship may exist from the business object Identified Logistic Unit/node Identified Logistic Unit to IdentifiedLogisticUnit with a cardinality of C:CN, which may represent an identified logistic unit that is tagged by the goods tag. An inbound aggregation relationship may exist from the business object Identified Stock/node Identified Stock to IdentifiedStock with a cardinality of C:CN, which may represent an identified stock of the product or the content of the package that is tagged by the goods tag. An inbound aggregation relationship may exist from the business object Individual Material/node Individual Material to IndividualMaterial with a cardinality of C:CN, which may represent an individual material that is directly tagged by the goods tag. An inbound aggregation relationship may exist from the business object Location/node Location to Site with a cardinality of C:CN, which may represent a site to which the goods tag is assigned. An inbound aggregation relationship may exist from the business object Logistic Unit/node Logistic Unit to LogisticUnit with a cardinality of C:CN, which may represent a logistic unit of the package that is tagged by the goods tag. An inbound aggregation relationship may exist from the business object Logistic Unit/node Standard Material Content to LogisticUnitStandardMaterialContent with a cardinality of C:CN, which may represent a logistic unit standard material content for the assigned material and logistic unit. An inbound aggregation relationship may exist from the business object Logistics Area/node Logistics Area to LogisticsArea with a cardinality of C:CN, which may represent a logistics area to which the goods tag is assigned. An inbound aggregation relationship may exist from the business object Material/node Material to Material with a cardinality of C:CN, which may represent material included in the tagged package or the material that is directly tagged by the goods tag. An inbound aggregation relationship may exist from the business object Party/node Party to VendorParty with a cardinality of C:CN, which may represent a vendor party of the product or package. An inbound aggregation relationship may exist from the business object Party/node Party to BuyerParty with a cardinality of C:CN, which may represent a buyer party of the product or package. An inbound aggregation relationship may exist from the business object Party/node Party to RecipientParty with a cardinality of C:CN, which may represent a recipient party of the product or package. An inbound aggregation relationship may exist from the business object Party/node Party to CarrierParty with a cardinality of C:CN, which may represent a carrier party of the product or package. An inbound aggregation relationship may exist from the business object Party/node Party to SellerParty with a cardinality of C:CN, which may represent a seller party of the product or package. An inbound aggregation relationship may exist from the business object Party/node Party to FreightForwarderParty with a cardinality of C:CN, which may represent a freight forwarder of the product or package. An inbound aggregation relationship may exist from the business object Product Requirement Specification/node Product Requirement Specification to ProductRequirementSpecification with a cardinality of C:CN, which may represent a product requirement specification that specifies the content of the tagged package or the tagged product. An inbound aggregation relationship may exist from the business object Resource/node Resource to Resource with a cardinality of C:CN, which may represent the last resource on which the tagged product or package was produced.

An inbound association relationship may exist from the business object Identity/node Identity to CreationIdentity with a cardinality of 1:CN, which may represent the identity that created the goods tag. An inbound association relationship may exist from the business object Inbound Delivery/node Item to InboundDeliveryItem with a cardinality of C:CN, which may represent the inbound delivery item that was the basis document for the creation of the goods tag. An inbound association relationship may exist from the business object Outbound Delivery/node Item to OutboundDeliveryItem with a cardinality of C:CN, which may represent an outbound delivery item that was the basis document for the creation of the goods tag. An inbound association relationship may exist from the business object Outbound Delivery/node Material to OutboundDeliveryMaterial with a cardinality of C:CN, which may represent a material node of an outbound delivery for which a goods tag assignment will be created. An inbound association relationship may exist from the business object Outbound Delivery/node Outbound Delivery to OutboundDelivery with a cardinality of C:CN, which may represent an outbound delivery for which a goods tag assignment will be created. An inbound association relationship may exist from the business object Production Lot/node Material Output to ProductionLotMaterialOutput with a cardinality of C:CN, which may represent a material output node of a production lot for which a goods tag assignment will be created. An inbound association relationship may exist from the business object Production Lot/node Production Lot to ProductionLot with a cardinality of C:CN, which may represent a production lot that was the basis document for the creation of the goods tag. An inbound association relationship may exist from the business object Site Logistics Lot/node Material Output to SiteLogisticsLotMaterialOutput with a cardinality of C:CN, which may represent a material output node of a site logistics lot for which a goods tag assignment will be created. An inbound association relationship may exist from the business object Site Logistics Lot/node Site Logistics Lot to SiteLogisticsLot with a cardinality of C:CN, which may represent a site logistics lot that was the basis document for the creation of the goods tag.

A specialization association for navigation relationship may exist from the business object Material/node Overview to MaterialOverview with a target cardinality of :CN, which may represent an overview of the Material contained by the tagged package or the Material that is directly tagged by the GoodsTag. A specialization association for navigation relationship may exist from the business object IndividualMaterial/node Overview to IndividualMaterialOverview with a target cardinality of :CN, which may represent an overview of the Individual Material that is directly tagged by the GoodsTag. A specialization association for navigation relationship may exist from the business object UsedAddress/node Root to ShipFromAddress with a target cardinality of :CN, which may represent an address of the location from which the tagged product or package is shipped. A specialization association for navigation relationship may exist from the business object UsedAddress/node Root to ShipToAddress with a target cardinality of :CN, which may represent an address of the location to which the tagged product or package is shipped.

Units of measure and factor are both maintained or both initial for measures and quantities. No identified stock is maintained if no material is maintained. If an identified stock is maintained, it exists for the maintained material. The quantity type code can be convertible to the base quantity type code of the material.

Goods Tag may be associated with the following enterprise service infrastructure actions: ApplyIdentifiedLogisticUnitChanges, and RemoveFromIdentifiedLogisticUnit. ApplyIdentifiedLogisticUnitChanges applies changes of identified logistic unit to the assigned goods tags. Gross weight, gross volume and the shipping package attached indicator of the goods tag are adapted based on the changes of the respective identified logistic unit. If there are changes to the object, gross weight, gross volume and the shipping package attached indicator are adapted based on the information of the identified logistic units. RemoveFromIdentifiedLogisticUnit removes a goods tag from an identified logistic unit. If there are changes to the object, the universally unique identified logistic unit identifier in the goods tag that denotes the identified logistic unit that the goods tag is attached to gets reset. Goods Tag may be associated with a Query By Elements query. Query By Elements returns a list of all goods tags according to the specified selection elements. The goods tags that fulfill the selection conditions for the following attributes include: ID, External Serial ID, Type Code, Creation Context Code, Quantity, Quantity Type Code, Creation Business Transaction Document Reference, Business Transaction Document Reference, Shipping Date, Production Date, Receipt Date, Material ID, Global Trade Item Number ID, Identified Stock ID, Product Requirement Specification ID, Logistic Unit ID, Resource ID, Logistic Area ID, Buyer Party ID, Seller Party ID, Vendor Party ID, Recipient Party ID, Carrier Party ID, Freight Forwarder ID, Gross Weight, Gross Weight Type Code, Gross Volume, Gross Volume Type Code, Shipping Package Attached Indicator, Incoterms, Product Seller ID, Product Buyer ID, System-Administratrive Data.

The query elements can be defined by the data type GoodsTagElementsQueryElements. These elements include: ID, PartySerialID, SerialID, TypeCode, CreationContextCode, MaterialQuantity, MaterialQuantityTypeCode, BaseBusinessTransactionDocumentReference, BusinessTransactionDocumentReference, ShippingDate, ProductionDate, ReceiptDate, MaterialKey, GlobalTradeItemNumberID, IdentifiedStockKey, ProductRequirementSpecificationKey, LogisticUnitID, ResourceID, LogisticsAreaKey, BuyerPartyKey, SellerPartyKey, VendorPartyKey, RecipientPartyKey, FreightForwarderPartyKey, CarrierPartyKey, GrossWeightMeasure, GrossWeightMeasureTypeCode, GrossVolumeMeasure, GrossVolumeMeasureTypeCode, ShippingPackageAttachedIndicator, Incoterms, ProductSellerID, ProductBuyerID, SystemAdministrativeData, IdentifiedLogisticUnitInternalID, and TransportTracking. MaterialKey includes the ProductTypeCode, ProductIdentifierTypeCode, the ProductID elements. IdentifiedStockKey includes the IdentifiedStockID and MaterialKey elements. ProductRequirementSpecificationKey includes the RequirementSpecificationID and RequirementSpecificationVersionID elements. LogisticsAreaKey includes the ID, SiteID, elements. BuyerPartyKey, SellerPartyKey, VendorPartyKey, RecipientPartyKey, FreightForwarderPartyKey, and CarrierPartyKey, include the PartyTypeCode and PartyID elements. SystemAdministrativeData includes the CreationDateTime, CreationIdentityUUID, CreationIdentityID, CreationIdentityBusinessPartnerinternalID, CreationIdentityBusinessPartnerPersonFamilyName, CreationIdentityBusinessPartnerPersonGivenName, CreationIdentityEmployeeID, LastChangeDateTime, LastChangeIdentityUUID, LastChangeIdentityID, LastChangeIdentityBusinessPartnerInternalID, LastChangeIdentityBusinessPartnerPersonFamilyName, LastChangeIdentityBusinessPartnerPersonGivenName, and LastChangeIdentityEmployeeID elements. ID may be based on datatype GDT: GoodsTagID. PartySerialID may be based on datatype GDT: SerialID, Qualifier: Party. SerialID may be based on datatype GDT: SerialID. TypeCode may be based on datatype GDT: GoodsTagTypeCode. CreationContextCode may be based on datatype GDT: GoodsTagCreationContextCode. MaterialQuantity may be based on datatype GDT: Quantity, Qualifier: Material. MaterialQuantityTypeCode may be based on datatype GDT: QuantityTypeCode, Qualifier: Material. BaseBusinessTransactionDocumentReference may be based on datatype GDT: BusinessTransactionDocumentReference, Qualifier: Base. BusinessTransactionDocumentReference may be based on datatype GDT: BusinessTransactionDocumentReference. ShippingDate may be based on datatype GDT: Date, Qualifier: Shipping. ProductionDate may be based on datatype GDT: Date, Qualifier: Production. ReceiptDate may be based on datatype GDT: Date, Qualifier: Receipt. MaterialKey is a grouping of elements that uniquely identifies a material, a sub-quantity of which is identified by the identified stock. It may be based on datatype KDT: ProductKey. ProductTypeCode is a coded representation of a product type such as a material or service. It may be based on datatype GDT: ProductTypeCode. ProductIdentifierTypeCode is a coded representation of a product identifier type. It may be based on datatype GDT: ProductIdentifierTypeCode. ProductID is an identifier for a product. It may be based on datatype GDT: ProductID. GlobalTradeItemNumberID may be based on datatype GDT: ProductStandardID. IdentifiedStockKey may be based on datatype KDT: IdentifiedStockKey. IdentifiedStockID is an identifier for the identified stock in the context of a material ID. It may be based on datatype GDT: IdentifiedStockID. ProductRequirementSpecificationKey may be based on datatype KDT: RequirementSpecificationKey. RequirementSpecificationID is an identifier for a requirement specification that is unique within one system. It may be based on datatype GDT: RequirementSpecificationID. RequirementSpecificationVersionID is an identifier for the version of a requirement specification. It may be based on datatype GDT: VersionID. LogisticUnitID may be based on datatype GDT: LogisticUnitID. ResourceID may be based on datatype GDT: ResourceID. LogisticsAreaKey may be based on datatype KDT: LogisticsAreaKey. ID is an identifier for the logistics area. It may be based on datatype GDT: LogisticsAreaID. SiteID is an identifier for the site at which the logistics area is located. It may be based on datatype GDT: LocationID. BuyerPartyKey may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. SellerPartyKey may be based on datatype KDT: PartyKey. VendorPartyKey may be based on datatype KDT: PartyKey. RecipientPartyKey may be based on datatype KDT: PartyKey. FreightForwarderPartyKey may be based on datatype KDT: PartyKey. CarrierPartyKey may be based on datatype KDT: PartyKey. GrossWeightMeasure may be based on datatype GDT: Measure, Qualifier: GrossWeight. GrossWeightMeasureTypeCode may be based on datatype GDT: MeasureTypeCode, Qualifier: GrossWeight. GrossVolumeMeasure may be based on datatype GDT: Measure, Qualifier: GrossVolume. GrossVolumeMeasureTypeCode may be based on datatype GDT: MeasureTypeCode, Qualifier: GrossVolume. ShippingPackageAttachedIndicator may be based on datatype GDT: Indicator, Qualifier: Attached. Incoterms may be based on datatype GDT: Incoterms. ProductSellerID may be based on datatype GDT: ProductPartyID. ProductBuyerID may be based on datatype GDT: ProductPartyID. SystemAdministrativeData may be based on datatype QueryIDT: QueryElementSystemAdministrativeData. CreationDateTime represents the point in time (e.g., date and time stamp) of the creation. It may be based on datatype GDT: GLOBAL_DateTime. CreationIdentityUUID is a globally unique identifier for the identity who did the creation. It may be based on datatype GDT: UUID. CreationIdentityID is an identifier for the identity who did the creation. It may be based on datatype GDT: IdentityID. CreationIdentityBusinessPartnerInternalID is a proprietary identifier for the business partner that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on datatype GDT: BusinessPartnerInternalID. CreationIdentityBusinessPartnerPersonFamilyName is the family name of the business partner of the category person that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on datatype GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. CreationIdentityBusinessPartnerPersonGivenName is the given name of the business partner of the category person that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on datatype GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. CreationIdentityEmployeeID is an identifier for the employee that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on datatype GDT: EmployeeID. LastChangeDateTime represents the point in time (e.g., date and time stamp) of the last change. It may be based on datatype GDT: GLOBAL_DateTime. LastChangeIdentityUUID is a globally unique identifier for an identity who made the last changes. It may be based on datatype GDT: UUID. LastChangeIdentityID is an identifier for an identity who made the last changes. It may be based on datatype GDT: IdentityID. LastChangeIdentityBusinessPartnerinternalID is a proprietary identifier for the business partner that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on datatype GDT: BusinessPartnerInternalID. LastChangeIdentityBusinessPartnerPersonFamilyName is the family name of the business partner of the category person that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on datatype GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. LastChangeIdentityBusinessPartnerPersonGivenName is the given name of the business partner of the category person that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on datatype GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. LastChangeIdentityEmployeeID is an identifier for the employee that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on datatype GDT: EmployeeID. IdentifiedLogisticUnitInternalID may be based on datatype GDT: IdentifiedLogisticUnitInternalID. TransportTracking may be based on datatype GDT: TransportTracking The Select All query returns the node IDs of all instances of this node.

Unspecified Content Package Tag is a label that includes selected information about a package and that does not contain a material identifier. In some implementations, Material UUID, Quantity and quantity type code may be initial. Uniform Content Package Tag is an electronic device, a small piece or part, or a label that includes selected information about a package with a uniform content and that also includes a material identifier. In some implementations, Material UUID may not be initial. Serialised Material Tag is an electronic device, a small piece or part, or a label that is attached to one piece of a material and that includes a material identifier. In some implementations, Material UUID may not be initial, and quantity factor may be 1 and quantity type code may be “each.” Mixed Content Package Tag is as an electronic device, a small piece or part, or a label that includes selected information about a package with a mixed content and that can include an identified logistic unit identifier. In some implementations, Material UUID, quantity and quantity type code may be initial.

Business Transaction Document Reference is a unique reference between the business object and another business transaction document or business transaction document item. The referenced documents record the process of transportation or production. The identifiers of these documents can be printed on the goods tag. The elements located directly at the node Business Transaction Document Reference can be defined by the data type GoodsTagBusinessTransactionDocumentReferenceElements. These elements include BusinessTransactionDocumentReference. BusinessTransactionDocumentReference is a business transaction document that is referenced by the goods tag. It may be based on datatype GDT: BusinessTransactionDocumentReference.

An inbound association relationship may exist from the business object Confirmed Inbound Delivery/node Confirmed Inbound Delivery to ConfirmedInboundDelivery with a cardinality of C:CN, which may represent a confirmed inbound delivery to which the goods tag is assigned. An inbound association relationship may exist from the business object Customer Return/node Item to CustomerReturnItem with a cardinality of C:CN, which may represent a customer return item to which the goods tag is assigned. An inbound association relationship may exist from the business object Inbound Delivery/node Item to InboundDeliveryItem with a cardinality of C:CN, which may represent an inbound delivery item to which the goods tag is assigned. An inbound association relationship may exist from the business object Outbound Delivery/node Item to OutboundDeliveryItem with a cardinality of C:CN, which may represent an outbound delivery item to which the goods tag is assigned. An inbound association relationship may exist from the business object Production Lot/node Production Lot to ProductionLot with a cardinality of C:CN, which may represent a production lot to which the goods tag is assigned. An inbound association relationship may exist from the business object Production Order/node Production Order to ProductionOrder with a cardinality of C:CN, which may represent a production order to which the goods tag is assigned. An inbound association relationship may exist from the business object Production Task/node Production Task to ProductionTask with a cardinality of C:CN, which may represent a production task to which the goods tag is assigned. An inbound association relationship may exist from the business object Purchase Order/node Item to PurchaseOrderItem with a cardinality of C:CN, which may represent a purchase order item to which the goods tag is assigned. An inbound association relationship may exist from the business object Sales Order/node Item to SalesOrderItem with a cardinality of C:CN, which may represent a sales order item to which the goods tag is assigned. An inbound association relationship may exist from the business object Site Logistics Lot/node Site Logistics Lot to SiteLogisticsLot with a cardinality of C:CN, which may represent a site logistics lot to which the goods tag is assigned. An inbound association relationship may exist from the business object Site Logistics Task/node Site Logistics Task to SiteLogisticsTask with a cardinality of C:CN, which may represent a site logistics task to which the goods tag is assigned.

Location represents a physical or logical location that can be printed on a goods tag in a location role. A physical location can be determined using spatial coordinates, for example, an address containing the street and house number. A logical location may not be determined by spatial coordinates, for example, a PO box or an e-mail address. It may not be necessary to know the physical location of a logical location. A goods tag location can be a reference to one of the following: a location, the address of a party, representative of a business partner and an organizational unit, the address of an installed base, or the address of an installation point.

The elements located directly at the node Location can be defined by the data type GoodsTagLocationElements. These elements include: LocationID, LocationUUID, AddressReference, RoleCode, and RoleCategoryCode. AddressReference includes the AddressHostUUID, BusinessObj ectTypeCode, AddressHostTypeCode, PartyKey, InstalledBaseID, and InstallationPointID elements. PartyKey includes the PartyTypeCode and PartyID elements.

LocationID is an identifier for the business object Location. It may be based on datatype GDT: LocationID. LocationUUID is a globally unique identifier for the business object Location. It may be based on datatype GDT: UUID. AddressReference is a reference to the address of a party, an installed base, or an installation point. It may be based on datatype BOIDT: ObjectNodeLocationAddressReference. AddressHostUUID is a universally unique identifier for the address of the business partner, the organizational unit or its specializations, the business object InstalledBase, or the business object InstallationPoint. It may be based on datatype GDT: UUID. BusinessObjectTypeCode is a coded representation of the type of the business object, in which the address referenced in the LocationAddressUUID is integrated as a dependent object. It may be based on datatype GDT: BusinessObjectTypeCode. AddressHostTypeCode is a coded representation of the address host type of the address referenced by the AddressUUID or the address included using the Location Address composition. It may be based on datatype GDT: AddressHostTypeCode. PartyKey is an alternative identifier of a party, which represents a business partner or an organizational unit, which references the address using the AddressUUID. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. InstalledBaseID is an identifier for an installed base that references the address using the AddressUUID. It may be based on datatype GDT: InstalledBaseID. InstallationPointID is an identifier for an installation point that references the address using the AddressUUID. It may be based on datatype GDT: InstallationPointID. RoleCode is a coded representation of the role of the goods tag location in the business document or the master data object. It may be based on datatype GDT: LocationRoleCode. RoleCategoryCode is a coded representation of the role category of the goods tag location in the business document or the master data object. It may be based on datatype GDT: LocationRoleCategoryCode.

A composition relationship to subordinate LocationAddress node may exist in a 1:C cardinality relationship. An inbound aggregation relationship may exist from the business object Installation Point/node Address Information to InstallationPointAddressInformation with a cardinality of C:CN, which may represent address information of an installation point corresponding to the goods tag location. An inbound aggregation relationship may exist from the business object Installed Base/node Address Information to InstalledBaseAddressInformation with a cardinality of C:CN, which may represent address information of an installed base corresponding to the goods tag location. An inbound aggregation relationship may exist from the business object Location/node Location to Location with a cardinality of C:CN, which may represent a location corresponding to the goods tag location. An inbound aggregation relationship may exist from the business object Party/node Address Information to PartyAddressInformation with a cardinality of C:CN, which may the represent address information of a representative of a business partner or organizational centre corresponding to the goods tag location.

A specialization association for navigation relationship may exist from UsedAddress/node Root to UsedAddress with a target cardinality of :CN, which may represent a referenced address of a master data object or the address that is integrated via the composition relationship LocationAddress. Which address applies can be determined by looking at the element AddressHostTypeCode. The instance of the TO UsedAddress represents this address. The association is implemented. The referenced address of a master data object is used if the elements AddressBusinessObjectTypeCode, AddressUUID and AddressHostTypeCode are used to determine the Node ID of the node in the master data object, which holds the composition relationship with DO Address, which is to be represented by TO Used Address. Also, the following information is sent to the TO Used Address in the implemented address: that it is a master data address, and the BusinessObjectTypeCode, BusinessObjectNodeTypeCode and Node ID of an object node Location node. In some implementations, this is required if changes are made to the TO Used Address. The TO Used Address copies the master data address, the changes are applied and the corresponding DO Address is generated on the <Object Node> Location node via the composition relationship Location Address. The address that is integrated via the composition relationship LocationAddress is used if the BusinessObjectTypeCode, BusinessObjectNodeTypeCode and Node ID of the own <Object Node> Location are communicated to the TO Used Address. Whether or not it is a referenced address is also included. The TO Used Address may represent the DO Address that is integrated via the composition relationship on the <Object Node> Location.

In some implementations, there can be either just one aggregation or composition relationship to the dependent object. If there is an aggregation relationship to the BO Location, the LocationID attribute can be filled with the ID of BO Location. All other ID fields (e.g., PartyID, InstalledBaseID and InstallationPointID) remain blank. If the address of a party is referenced, representative of a BusinessPartners or an OrganisationalCentre, the PartyID attribute can be filled with the ID of the Party. All other ID fields (e.g., LocationID, InstalledBaseID and InstallationPointID) remain blank. The reference is kept in the AddressUUID attribute. If there is an aggregation relationship to the address of an InstalledBase, the InstalledBaseID attribute can be filled with the ID of the InstalledBase. All other ID fields (e.g., LocationID, PartyID and InstallationPointID) remain blank. The reference is kept in the AddressUUID InstalledBaseAddressInformationUUID attribute. If there is an aggregation relationship to the address of an InstallationPoint, the InstallationPointID attribute can be filled with the ID of the InstallationPoint. All other ID fields (e.g., LocationID, PartyID and InstalledBaseID) remain blank. The reference is kept in the AddressUUID attribute. In some implementations, if an address is referenced via the element AddressUUID, then elements AddressBusinessObjectTypeCode and AddressHostTypeCode may also be filled.

The Location Address includes data necessary to describe a physical or logical location. The Controlled Output Request is a controller of output requests and output history entries. Text Collection is a collection of natural-language text with additional information about the product or package.

FIG. 33 depicts an example Form Mixed Content Package Tag Notification Message Data Type 33000, which comprises elements 33002-33018, hierarchically related as shown. For example, the Form Mixed Content Package Tag Notification 33002 includes a Message Header 33004.

The message type Form Mixed Content Package Tag Notification is derived from the business object GoodsTag leading object together with its operation signature. Form Mixed Content Package Tag Notification is a notification about the printing or creation of package tags of the type “mixed content.” The “mixed content” package tag is a label for an identified logistics unit which includes data such as weight and other measurements but also content information. A mixed content package tag can be used for packages or pallets with a mixed content or for tracking the package material itself. The structure of this message type can be determined by the message data type FormMixedContentPackageTagNotificationMessage.

The FormMixedContentPackageTagNotificationMessage message data type includes an object GoodsTag which is included in a business document, and business information that is relevant for sending a business document in a message. It includes the MessageHeader and GoodsTag packages. This message data type provides the structure for the Form Mixed Content Package Tag Notification message types and the operations that are based on it.

The MessageHeader package is a grouping of business information that is relevant for sending a business document in a message. It includes the Message Header node. The MessageHeader is a grouping of business information from the perspective of the sending application. It includes information to identify the business document in a message, information about the sender, and optionally, information about the recipient. The MessageHeader includes the SenderParty and RecipientParty elements. The MessageHeader may be based on the datatype GDT:BusinessDocumentMessageHeader. The elements of the GDT used include RecipientParty, BusinessScope, SenderParty, SenderBusinessSystemID, TestDataIndicator, RecipientBusinessSystemID, ReferenceID, ReferenceUUID, ReconciliationIndicator, ID, UUID, and CreationDateTime.

The SenderParty is a partner responsible for sending a business document at a business application level. The RecipientParty may be based on the datatype GDT:BusinessDocumentMessageHeaderParty. RecipientParty is a partner responsible for receiving a business document at a business application level. The SenderParty may be based on the datatype GDT:BusinessDocumentMessageHeaderParty.

The GoodsTag package is the grouping of GoodsTag with its packages. The packages include: TextCollection, LogisticUnit, Delivery, BusinessTransactionDocumentReferences, Site, and IdentifiedLogisticUnit. It also includes a GoodsTag entity. The GoodsTag entity represents an electronic device, a small piece or part, or a label that contains selected information about a product or package. GoodsTag includes the non-node elements: ID, PartySerialID, ProductionDate, ShippingDate, GoodsReceiptDate, ShippingPackageAttachedIndicator, CreationContextDependingDate, GrossWeightMeasure, GrossWeightMeasureTypeCode, GrossWeightMeasureTypeName, GrossWeightMeasureUnitCodeName, GrossVolumeMeasure, GrossVolumeMeasureTypeCode, GrossVolumeMeasureTypeName, GrossVolumeMeasureUnitCodeName, OutputRequestCreationDateTime, OutputRequestCreationIdentityID, OutputRequestCreationBusinessPartnerFormattedName, ImageFileContentBinaryObject, and TransportTracking ID may be based on datatype GDT:GoodsTagID. PartySerialID may be based on datatype GDT:SerialID with Qualifier:Party. ProductionDate may be based on datatype CDT:Date. ShippingDate may be based on datatype CDT:Date. GoodsReceiptDate may be based on datatype CDT:Date. ShippingPackageAttachedIndicator may be based on datatype CDT:Indicator. CreationContextDependingDate may be based on datatype CDT:Date. GrossWeightMeasure may be based on datatype CDT:Measure. GrossWeightMeasureTypeCode may be based on datatype GDT:MeasureTypeCode. GrossWeightMeasureTypeName may be based on datatype CDT:LONG_Name. GrossWeightMeasureUnitCodeName may be based on datatype CDT:Name. GrossVolumeMeasure may be based on datatype CDT:Measure. GrossVolumeMeasureTypeCode may be based on datatype GDT:MeasureTypeCode. GrossVolumeMeasureTypeName may be based on datatype CDT:LONG_Name.

GrossVolumeMeasureUnitCodeName may be based on datatype CDT:Name. OutputRequestCreationDateTime may be based on datatype CDT:LOCAL_DateTime. OutputRequestCreationIdentityID may be based on datatype GDT:IdentityID. OutputRequestCreationBusinessPartnerFormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. ImageFileContentBinaryObject may be based on datatype CDT:BinaryObject. TransportTracking may be based on datatype GDT:TransportTracking. The GoodsTag package includes a node element TextCollection in a 1:C cardinality relationship, a node element LogisticUnit in a 1:C cardinality relationship, a node element Delivery in a 1:1 cardinality relationship, a BusinessTransactionDocumentReferences in a 1:1 cardinality relationship, a node element Site in a 1:1 cardinality relationship, and a node element IdentifiedLogisticUnit in a 1:C cardinality relationship.

The GoodsTagTextCollection package includes the TextCollection entity. TextCollection is a collection of natural-language text with additional information about a product or package. TextCollection includes a non-node element TextCollection. TextCollection may be based on datatype MAGDT:TextCollection.

The GoodsTagLogisticUnit package includes a LogisticUnit entity. LogisticUnit denotes the logistic unit of the package that is tagged by the goods tag. LogisticUnit includes the non-node elements: LogisticUnitID, LogisticUnitDescription, LogisticUnitQuantity, LogisticUnitQuantityTypeCode, and LogisticUnitQuantityTypeName. LogisticUnitID may be based on datatype GDT:LogisticUnitID. LogisticUnitDescription may be based on datatype GDT: SHORT_Description. LogisticUnitQuantity may be based on datatype CDT:Quantity. LogisticUnitQuantityTypeCode may be based on datatype GDT: QuantityTypeCode. LogisticUnitQuantityTypeName may be based on datatype CDT:SHORT_Name.

The GoodsTagDelivery package includes a Delivery entity. Delivery denotes the delivery to which the goods tag is assigned. Delivery includes the non-node elements: ShipToAddress, ShipToAddressPostalCode, ShipToCountryCode, ShipToCountryName, ShipFromAddress, ShipFromCountryCode, ShipFromCountryName, Incoterms, BuyerPartyID, BuyerPartyFormattedName, SellerPartyID, SellerPartyFormattedName, RecipientPartyID, RecipientPartyFormattedName, VendorPartyID, VendorPartyFormattedName, FreightForwarderPartyID, and FreightForwarderPartyFormattedName. Incoterms includes the elements ClassificationCode, ClassificationName, and TransferLocationName. ShipToAddress may be based on datatype GDT:FormAddress. ShipToAddressPostalCode may be based on datatype GDT:PostalCode with Qualifier:Address. ShipToCountryCode may be based on datatype GDT:CountryCode. ShipToCountryName may be based on datatype CDT:MEDIUM_Name. ShipFromAddress may be based on datatype GDT:FormAddress. ShipFromCountryCode may be based on datatype GDT:CountryCode. ShipFromCountryName may be based on datatype CDT:MEDIUM_Name. Incoterms may be based on datatype FMIDT:FormIncoterms. ClassificationCode may be based on datatype GDT:IncotermsClassificationCode. ClassificationName may be based on datatype CDT:Name. TransferLocationName may be based on datatype GDT:IncotermsTransferLocationName. BuyerPartyID may be based on datatype GDT:PartyID. BuyerPartyFormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. SellerPartyID may be based on datatype GDT:PartyID. SellerPartyFormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. RecipientPartyID may be based on datatype GDT:PartyID. RecipientPartyFormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. VendorPartyID may be based on datatype GDT:PartyID. VendorPartyFormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. FreightForwarderPartyID may be based on datatype GDT:PartyID. FreightForwarderPartyFormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name.

The GoodsTagBusinessTransactionDocumentReferences package includes a BusinessTransactionDocumentReferences entity. BusinessTransactionDocumentReferences is a unique reference between a business object and another business transaction document or business transaction document item. The referenced documents record a process of transportation or production. The identifiers of these documents can be printed on the goods tag. BusinessTransactionDocumentReferences includes the non-node elements: InboundDeliveryID, InboundDeliveryItemID, ConfirmedInboundDeliveryID, ConfirmedInboundDeliveryItemID, OutboundDeliveryID, OutboundDeliveryItemID, CreationContextDependingDeliveryID, CreationContextDependingDeliveryItemID, SalesOrderID, SalesOrderItemID, PurchaseOrderID, PurchaseOrderItemID, CustomerReturnID, CustomerReturnItemID, OriginPurchaseOrderID, and OriginPurchaseOrderItemID. InboundDeliveryID may be based on datatype GDT:BusinessTransactionDocumentID. InboundDeliveryItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. ConfirmedInboundDeliveryID may be based on datatype GDT:BusinessTransactionDocumentID. ConfirmedInboundDeliveryItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. OutboundDeliveryID may be based on datatype GDT:BusinessTransactionDocumentID. OutboundDeliveryItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. CreationContextDependingDeliveryID may be based on datatype GDT:BusinessTransactionDocumentID. CreationContextDependingDeliveryItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. SalesOrderID may be based on datatype GDT:BusinessTransactionDocumentID. SalesOrderItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. PurchaseOrderID may be based on datatype GDT:BusinessTransactionDocumentID. PurchaseOrderItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. CustomerReturnID may be based on datatype GDT:BusinessTransactionDocumentID. CustomerReturnItemID may be based on datatype GDT:BusinessTransactionDocumentItemID. OriginPurchaseOrderID may be based on datatype GDT:BusinessTransactionDocumentID. OriginPurchaseOrderItemID may be based on datatype GDT:BusinessTransactionDocumentItemID.

The GoodsTagSite package includes a Site entity. Site denotes the site to which the goods tag is assigned. Site includes the non-node elements SiteID and SiteDescription. SiteID may be based on datatype GDT:LocationID. SiteDescription may be based on datatype GDT: SHORT_Description.

The GoodsTagIdentifiedLogisticUnit package includes an IdentifiedLogisticUnit entity. IdentifiedLogisticUnit denotes the identified logistic unit that is tagged by the goods tag. IdentifiedLogisticUnit includes the non-node elements: IdentifiedLogisticUnitInternalID, GrossVolumeMeasure, GrossWeightMeasure, NetVolumeMeasure, NetWeightMeasure, HeightMeasure, WidthMeasure, LengthMeasure, and TareWeightMeasure. GrossVolumeMeasure, GrossWeightMeasure, NetVolumeMeasure, NetWeightMeasure, HeightMeasure, WidthMeasure, LengthMeasure, and TareWeightMeasure include the elements Measure and MeasureUnitCodeName. IdentifiedLogisticUnitInternalID may be based on datatype GDT:IdentifiedLogisticUnitInternalID. GrossVolumeMeasure may be based on datatype FMIDT:FormMeasure. GrossWeightMeasure may be based on datatype FMIDT:FormMeasure. NetVolumeMeasure may be based on datatype FMIDT:FormMeasure. NetWeightMeasure may be based on datatype FMIDT:FormMeasure. HeightMeasure may be based on datatype FMIDT:FormMeasure. WidthMeasure may be based on datatype FMIDT:FormMeasure. LengthMeasure may be based on datatype FMIDT:FormMeasure. TareWeightMeasure may be based on datatype FMIDT:FormMeasure. Measure may be based on datatype CDT:Measure. MeasureUnitCodeName may be based on datatype CDT:Name.

FIGS. 34-1 through 34-2 depict an example Form Serialised Material Tag Notification Message Data Type 34000, which comprises elements 34002-34026, hierarchically related as shown. For example, the Form Serialised Material Tag Notification 34002 includes a Message Header 34004.

The message type Form Serialised Material Tag Notification is derived from the business object Goods Tag leading object together with its operation signature. Form Serialised Material Tag Notification is a notification about the printing or creation of material tags of the type “serialised.” The “serialised” material tag is a label or a tag that clearly identifies a unique product. A field for the external serial number is available on the label in addition to the tag ID. The structure of the Form Serialised Material Tag Notification message type can be determined by the message data type FormSerialisedMaterialTagNotificationMessage.

The FormSerialisedMaterialTagNotificationMessage message data type includes an object GoodsTag which is included in the business document, and business information that is relevant for sending a business document in a message. It includes the MessageHeader and GoodsTag packages. This message data type can provide the structure for the Form Serialised Material Tag Notification message type and the operations that are based on it.

The MessageHeader package is a grouping of business information that is relevant for sending a business document in a message. It includes the MessageHeader node. A MessageHeader is a grouping of business information from the perspective of the sending application. It includes information to identify the business document in a message, information about the sender, and optionally, information about the recipient.

The MessageHeader includes the SenderParty and RecipientParty elements. MessageHeader may be based on the datatype GDT:BusinessDocumentMessageHeader. The elements of the GDT used include: RecipientParty, BusinessScope, SenderParty, SenderBusinessSystemID, TestDataIndicator, RecipientBusinessSystemID, ReferenceID, ReferenceUUID, ReconciliationIndicator, ID, UUID, and CreationDateTime. The SenderParty is a partner responsible for sending a business document at a business application level. The SenderParty may be based on the datatype GDT:BusinessDocumentMessageHeaderParty. The RecipientParty is a partner responsible for receiving a business document at a business application level. The RecipientParty may be based on the datatype GDT: BusinessDocumentMessageHeaderParty.

The GoodsTag package is the grouping of GoodsTag with its packages. It includes the packages TextCollection, Product, ProductRequirementSpecification, IdentifiedStock, LogisticsArea, Delivery, BusinessTransactionDocumentReferences, and Site. It also includes a GoodsTag entity. The GoodsTag entity represents an electronic device, a small piece or part, or a label that includes selected information about a product or package. GoodsTag includes the non-node elements: ID, ExternalSerialID, SerialID, Quantity, QuantityTypeCode, QuantityTypeName, QuantityMeasureUnitCodeName, ProductionDate, ShippingDate, GoodsReceiptDate, ShippingPackageAttachedIndicator, CreationContextDependingDate, GrossWeightMeasure, GrossWeightMeasureTypeCode, GrossWeightMeasureTypeName, GrossWeightMeasureUnitCodeName, GrossVolumeMeasure, GrossVolumeMeasureTypeCode, GrossWeightMeasureTypeName, GrossVolumeMeasureUnitCodeName, OutputRequestCreationDateTime, OutputRequestCreationIdentityID, OutputRequestCreationBusinessPartnerFormattedName, ImageFileContentBinaryObject, and TransportTracking ID may be based on GDT:GoodsTagID. ExternalSerialID may be based on GDT:SerialID. SerialID may be based on GDT:SerialID. Quantity may be based on CDT: Quantity. QuantityTypeCode may be based on GDT:QuantityTypeCode. QuantityTypeName may be based on CDT:LONG_Name. QuantityMeasureUnitCodeName may be based on CDT:Name. ProductionDate may be based on CDT:Date. ShippingDate may be based on CDT:Date. GoodsReceiptDate may be based on CDT:Date. ShippingPackageAttachedIndicator may be based on CDT:Indicator. CreationContextDependingDate may be based on CDT:Date. GrossWeightMeasure may be based on CDT:Measure. GrossWeightMeasureTypeCode may be based on GDT:MeasureTypeCode. GrossWeightMeasureTypeName may be based on CDT:LONG_Name. GrossWeightMeasureUnitCodeName may be based on CDT:Name. GrossVolumeMeasure may be based on CDT:Measure. GrossVolumeMeasureTypeCode may be based on GDT:MeasureTypeCode. GrossVolumeMeasureTypeName may be based on CDT:LONG_Name. GrossVolumeMeasureUnitCodeName may be based on CDT:Name. OutputRequestCreationDateTime may be based on CDT:LOCAL_DateTime. OutputRequestCreationIdentityID may be based on GDT:IdentityID. OutputRequestCreationBusinessPartnerFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. ImageFileContentBinaryObject may be based on CDT:BinaryObject. TransportTracking may be based on GDT:TransportTracking

The GoodsTag package includes a node element TextCollection in a 1:C cardinality relationship, a node element Product in a 1:C cardinality relationship, a node element ProductRequirementSpecification in a 1:C cardinality relationship, a node element IdentifiedStock in a 1:C cardinality relationship, a node element LogisticsArea in a 1:C cardinality relationship, a node element Delivery in a 1:1 cardinality relationship, a node element BusinessTransactionDocumentReferences in a 1:1 cardinality relationship, and a node element Site in a 1:1 cardinality relationship.

The GoodsTagTextCollection package includes a TextCollection entity. TextCollection is a collection of natural-language text with additional information about a product or package. TextCollection includes a non-node element TextCollection. TextCollection may be based on MAGDT:TextCollection.

The GoodsTagProduct package includes a Product entity. Product includes the non-node elements: ProductID, ProductDescription, GlobalTradeItemNumberID, GlobalTradeItemNumberQuantityTypeCode, GlobalTradeItemNumberQuantityTypeName, ProductSellerID, and ProductBuyerID. ProductID may be based on GDT:ProductID. ProductDescription may be based on GDT: SHORT_Description. GlobalTradeItemNumberID may be based on GDT:ProductStandardID. GlobalTradeItemNumberQuantityTypeCode may be based on GDT: QuantityTypeCode. GlobalTradeItemNumberQuantityTypeName may be based on CDT:SHORT_Name. ProductSellerID may be based on GDT:ProductPartyID. ProductBuyerID may be based on GDT:ProductPartyID.

The GoodsTagProductRequirementSpecification package includes a ProductRequirementSpecification entity. ProductRequirementSpecification denotes a product requirement specification that specifies the content of the tagged package or the tagged product. ProductRequirementSpecification includes the non-node elements: ProductRequirementSpecificationID, ProductRequirementSpecificationVersionID, and ProductRequirementSpecificationDescription. ProductRequirementSpecificationID may be based on GDT:RequirementSpecificationID. ProductRequirementSpecificationVersionID may be based on GDT:VersionID. ProductRequirementSpecificationDescription may be based on GDT:MEDIUM_Description.

The GoodsTagIdentifiedStock package includes an IdentifiedStock entity. IdentifiedStock denotes the identified stock of the product or the content of the package that is tagged by the goods tag. IdentifiedStock includes the non-node elements: IdentifiedStockID, IdentifiedStockPartyID, IdentifiedStockDescription, and ExpirationDateTime. IdentifiedStockID may be based on GDT:IdentifiedStockID. IdentifiedStockPartyID may be based on GDT:IdentifiedStockPartyID. IdentifiedStockDescription may be based on GDT:MEDIUM_Description. ExpirationDateTime may be based on CDT:LOCAL_DateTime.

The GoodsTagLogisticsArea package includes a LogisticsArea entity. LogisticsArea denotes a logistics area to which the goods tag is assigned. LogisticsArea includes the non-node elements LogisticsAreaID and LogisticsAreaDescription. LogisticsAreaID may be based on GDT:LogisticsAreaID. LogisticsAreaDescription may be based on GDT: SHORT_Description.

The GoodsTagDelivery package includes a Delivery entity. Delivery denotes the delivery to which the goods tag is assigned. Delivery includes the non-node elements: ShipToAddress, ShipToAddressPostalCode, ShipToCountryCode, ShipToCountryName, ShipFromAddress, ShipFromCountryCode, ShipFromCountryName, Incoterms, BuyerPartyID, BuyerPartyFormattedName, SellerPartyID, SellerPartyFormattedName, RecipientPartyID, RecipientPartyFormattedName, VendorPartyID, VendorPartyFormattedName, FreightForwarderPartyID, and FreightForwarderPartyFormattedName. Incoterms includes the elements ClassificationCode, ClassificationName, and TransferLocationName. ShipToAddress may be based on GDT:FormAddress. ShipToAddressPostalCode may be based on GDT:PostalCode. ShipToCountryCode may be based on GDT:CountryCode. ShipToCountryName may be based on CDT:MEDIUM_Name. ShipFromAddress may be based on GDT:FormAddress. ShipFromCountryCode may be based on GDT:CountryCode. ShipFromCountryName may be based on CDT:MEDIUM_Name. Incoterms may be based on FMIDT:FormIncoterms. ClassificationCode may be based on GDT:IncotermsClassificationCode. ClassificationName may be based on CDT:Name. TransferLocationName may be based on GDT:IncotermsTransferLocationName. BuyerPartyID may be based on GDT:PartyID. BuyerPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. SellerPartyID may be based on GDT:PartyID. SellerPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. RecipientPartyID may be based on GDT:PartyID. RecipientPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. VendorPartyID may be based on GDT:PartyID. VendorPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. FreightForwarderPartyID may be based on GDT:PartyID. FreightForwarderPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name.

The GoodsTagBusinessTransactionDocumentReferences package includes a BusinessTransactionDocumentReferences entity. BusinessTransactionDocumentReferences is a unique reference between a business object and another business transaction document or business transaction document item. The referenced documents record a process of transportation or production. The identifiers of these documents can be printed on the goods tag. BusinessTransactionDocumentReferences includes the non-node elements: ProductionLotID, SiteLogisticsLotID, InboundDeliveryID, InboundDeliveryItemID, OutboundDeliveryID, OutboundDeliveryItemID, ConfirmedInboundDeliveryID, ConfirmedInboundDeliveryItemID, CreationContextDependingDeliveryID, CreationContextDependingDeliveryItemID, SalesOrderID, SalesOrderItemID, PurchaseOrderID, PurchaseOrderItemID, CustomerReturnID, CustomerReturnItemID, OriginPurchaseOrderID, and OriginPurchaseOrderItemID. ProductionLotID may be based on GDT:BusinessTransactionDocumentID. SiteLogisticsLotID may be based on GDT:BusinessTransactionDocumentID. InboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. InboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. OutboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. OutboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. ConfirmedInboundDeliveryID may be based on may be based on GDT:BusinessTransactionDocumentID. ConfirmedInboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. CreationContextDependingDeliveryID may be based on GDT:BusinessTransactionDocumentID. CreationContextDependingDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. SalesOrderID may be based on GDT:BusinessTransactionDocumentID. SalesOrderItemID may be based on GDT:BusinessTransactionDocumentItemID. PurchaseOrderID may be based on GDT:BusinessTransactionDocumentID. PurchaseOrderItemID may be based on GDT:BusinessTransactionDocumentItemID. CustomerReturnID may be based on GDT:BusinessTransactionDocumentID. CustomerReturnItemID may be based on GDT:BusinessTransactionDocumentItemID). OriginPurchaseOrderID may be based on GDT:BusinessTransactionDocumentID. OriginPurchaseOrderItemID may be based on GDT:BusinessTransactionDocumentItemID.

The GoodsTagSite package includes a Site entity. Site denotes the site to which the goods tag is assigned. Site includes the non-node elements SiteID and SiteDescription. SiteID may be based on GDT:LocationID. SiteDescription may be based on GDT: SHORT_Description.

FIGS. 35-1 through 35-2 depict an example Form Uniform Content Package Tag Notification Message Data Type 35000, which comprises elements 35002-35024, hierarchically related as shown. For example, the Form Uniform Content Package Tag Notification 35002 includes a Message Header 35004.

The message type Form Uniform Content Package Tag Notification is derived from the business object Goods Tag leading object together with its operation signature. Form Uniform Content Package Tag Notification is a notification about the printing or creation of package tags of the type “uniform content.” The “uniform content” package tag is a label for a package with a uniform content. Such a package includes one material type with one identified stock. On an uniform content label quantity information can be printed. In addition, it can include data derived from a logistics unit such as measurements. The structure of the Form Uniform Content Package Tag Notification message type can be determined by the message data type FormUniformContentPackageTagNotificationMessage.

The FormUniformContentPackageTagNotificationMessage message data type includes an object GoodsTag which is included in the business document, and business information that can be relevant for sending a business document in a message. The FormUniformContentPackageTagNotificationMessage includes the MessageHeader and GoodsTag packages. This message data type can provide the structure for the Form Uniform Content Package Tag Notification message type and the operations that are based on it.

The MessageHeader package is a grouping of business information that is relevant for sending a business document in a message. It includes a MessageHeader node. The MessageHeader is a grouping of business information from the perspective of the sending application. It includes information to identify the business document in a message, information about the sender, and optionally, information about the recipient. The MessageHeader includes the SenderParty and RecipientParty elements. The MessageHeader may be based on the datatype GDT:BusinessDocumentMessageHeader. The elements of the GDT used include RecipientParty, BusinessScope, SenderParty, SenderBusinessSystemID, TestDataIndicator, RecipientBusinessSystemID, ReferenceID, ReferenceUUID, ReconciliationIndicator, ID, UUID, and CreationDateTime.

The GoodsTag package is the grouping of GoodsTag with its packages. It includes the packages: TextCollection, Product, ProductRequirementSpecification, IdentifiedStock, LogisticsArea, Delivery, BusinessTransactionDocumentReferences, Site, and LogisticUnit. It includes a GoodsTag entity.

The GoodsTag package is the grouping of GoodsTag with its packages. GoodsTag includes the non-node elements: ID, ExternalSerialID, Quantity, QuantityTypeCode, QuantityTypeName, QuantityMeasureUnitCodeName, ProductionDate, ShippingDate, GoodsReceiptDate, ShippingPackageAttachedIndicator, CreationContextDependingDate, GrossWeightMeasure, GrossWeightMeasureTypeCode, GrossWeightMeasureTypeName, GrossWeightMeasureUnitCodeName, GrossVolumeMeasure, GrossVolumeMeasureTypeCode, GrossVolumeMeasureTypeName, GrossVolumeMeasureUnitCodeName, OutputRequestCreationDateTime, OutputRequestCreationIdentityID, OutputRequestCreationBusinessPartnerFormattedName, ImageFileContentBinaryObject, and TransportTracking ID may be based on GDT:GoodsTagID. ExternalSerialID may be based on GDT:SerialID. Quantity may be based on CDT:Quantity. QuantityTypeCode may be based on GDT: QuantityTypeCode. QuantityTypeName may be based on CDT:LONG_Name. QuantityMeasureUnitCodeName may be based on CDT:Name. ProductionDate may be based on CDT:Date. ShippingDate may be based on CDT:Date. GoodsReceiptDate may be based on CDT:Date. ShippingPackageAttachedIndicator may be based on CDT:Indicator. CreationContextDependingDate may be based on CDT:Date. GrossWeightMeasure may be based on CDT:Measure. GrossWeightMeasureTypeCode may be based on GDT:MeasureTypeCode. GrossWeightMeasureTypeName may be based on CDT:LONG_Name. GrossWeightMeasureUnitCodeName may be based on CDT:Name. GrossVolumeMeasure may be based on CDT:Measure. GrossVolumeMeasureTypeCode may be based on GDT:MeasureTypeCode. GrossVolumeMeasureTypeName may be based on CDT:LONG_Name. GrossVolumeMeasureUnitCodeName may be based on CDT:Name. OutputRequestCreationDateTime may be based on CDT:LOCAL_DateTime. OutputRequestCreationIdentityID may be based on GDT:IdentityID. OutputRequestCreationBusinessPartnerFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. ImageFileContentBinaryObject may be based on CDT:BinaryObject. TransportTracking may be based on GDT:TransportTracking. The GoodsTag package includes a node element TextCollection in a 1:C cardinality relationship, Product in a 1:C cardinality relationship, ProductRequirementSpecification in a 1:C cardinality relationship, IdentifiedStock in a 1:C cardinality relationship, LogisticsArea in a 1:C cardinality relationship, Delivery in a 1:1 cardinality relationship, BusinessTransactionDocumentReferences in a 1:1 cardinality relationship, Site in a 1:1 cardinality relationship, LogisticUnit in a 1:C cardinality relationship.

The GoodsTagDelivery package includes a Delivery entity. Delivery denotes the delivery to which the goods tag is assigned. Delivery includes the non-node elements: ShipToAddress, ShipToAddressPostalCode, ShipToCountryCode, ShipToCountryName, ShipFromAddress, ShipFromCountryCode, ShipFromCountryName, Incoterms, BuyerPartyID, BuyerPartyFormattedName, SellerPartyID, SellerPartyFormattedName, RecipientPartyID, RecipientPartyFormattedName, VendorPartyID, VendorPartyFormattedName, FreightForwarderPartyID, and FreightForwarderPartyFormattedName. Incoterms includes the elements ClassificationCode, ClassificationName, and TransferLocationName. ShipToAddress may be based on GDT:FormAddress. ShipToAddressPostalCode may be based on GDT:PostalCode. ShipToCountryCode may be based on GDT:CountryCode. ShipToCountryName may be based on CDT:MEDIUM_Name. ShipFromAddress may be based on GDT:FormAddress. ShipFromCountryCode may be based on GDT:CountryCode. ShipFromCountryName may be based on CDT:MEDIUM_Name. Incoterms may be based on FMIDT:FormIncoterms. ClassificationCode may be based on GDT:IncotermsClassificationCode. ClassificationName may be based on CDT:Name. TransferLocationName may be based on GDT:IncotermsTransferLocationName. BuyerPartyID may be based on GDT:PartyID. BuyerPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. SellerPartyID may be based on GDT:PartyID. SellerPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. RecipientPartyID may be based on GDT:PartyID. RecipientPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. VendorPartyID may be based on GDT:PartyID. VendorPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. FreightForwarderPartyID may be based on GDT:PartyID. FreightForwarderPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name.

The GoodsTagBusinessTransactionDocumentReferences package includes a BusinessTransactionDocumentReferences entity. BusinessTransactionDocumentReferences is a unique reference between a business object and another business transaction document or business transaction document item. The referenced documents record a process of transportation or production. The identifiers of these documents can be printed on the goods tag. BusinessTransactionDocumentReferences includes the non-node elements: ProductionLotID, SiteLogisticsLotID, InboundDeliveryID, InboundDeliveryItemID, OutboundDeliveryID, OutboundDeliveryItemID, ConfirmedInboundDeliveryID, ConfirmedInboundDeliveryItemID, CreationContextDependingDeliveryID, CreationContextDependingDeliveryItemID, SalesOrderID, SalesOrderItemID, PurchaseOrderID, PurchaseOrderItemID, CustomerReturnID, CustomerReturnItemID, OriginPurchaseOrderID, and OriginPurchaseOrderItemID. ProductionLotID may be based on GDT:BusinessTransactionDocumentID. SiteLogisticsLotID may be based on GDT:BusinessTransactionDocumentID. InboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. InboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. OutboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. OutboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. ConfirmedInboundDeliveryID may be based on may be based on GDT:BusinessTransactionDocumentID. ConfirmedInboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. CreationContextDependingDeliveryID may be based on GDT:BusinessTransactionDocumentID. CreationContextDependingDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. SalesOrderID may be based on GDT:BusinessTransactionDocumentID. SalesOrderItemID may be based on GDT:BusinessTransactionDocumentItemID. PurchaseOrderID may be based on GDT:BusinessTransactionDocumentID. PurchaseOrderItemID may be based on GDT:BusinessTransactionDocumentItemID. CustomerReturnID may be based on GDT:BusinessTransactionDocumentID. CustomerReturnItemID may be based on GDT:BusinessTransactionDocumentItemID). OriginPurchaseOrderID may be based on GDT:BusinessTransactionDocumentID. OriginPurchaseOrderItemID may be based on GDT:BusinessTransactionDocumentItemID.

The GoodsTagSite package includes a Site entity. Site denotes the site to which the goods tag is assigned. Site includes the non-node elements SiteID and SiteDescription. SiteID may be based on GDT:LocationID. SiteDescription may be based on GDT: SHORT_Description.

The GoodsTagLogisticUnit package includes a LogisticUnit entity. LogisticUnit denotes the logistic unit of the package that is tagged by the goods tag. LogisticUnit includes the non-node elements: LogisticUnitID, LogisticUnitDescription, LogisticUnitQuantity, LogisticUnitQuantityTypeCode, and LogisticUnitQuantityTypeName. LogisticUnitID may be based on GDT:LogisticUnitID. LogisticUnitDescription may be based on GDT: SHORT_Description. LogisticUnitQuantity may be based on CDT:Quantity. LogisticUnitQuantityTypeCode may be based on GDT: QuantityTypeCode. LogisticUnitQuantityTypeName may be based on CDT:SHORT_Name.

FIG. 36 depicts an example Form Unspecified Content Package Tag Notification Message Data Type 36000, which comprises elements 36002-36016, hierarchically related as shown. For example, the Form Unspecified Content Package Tag Notification 36002 includes a Message Header 36004.

The message type Form Unspecified Content Package Tag Notification is derived from the business object Goods Tag leading object together with its operation signature. Form Unspecified Content Package Tag Notification is a notification about the printing or creation of package tags of the type “unspecified content.” The “unspecified content” package tag is a label for a logistics unit which includes data such as weight and other measurements but does not include any content information. An unspecified content package tag can be used for packages or pallets with a mixed content or for tracking the package material itself. As the content of the package is unknown to the system it can be called unspecified.

The FormUnspecifiedContentPackageTagNotificationMessage message data type includes an object GoodsTag that is included in the business document and business information relevant for sending a business document in a message. It includes the MessageHeader and GoodsTag packages. This message data type can provide the structure for the Form Unspecified Content Package Tag Notification message type and the operations that are based on it.

The SenderParty is a partner responsible for sending a business document at a business application level. The RecipientParty may be based on the datatype GDT:BusinessDocumentMessageHeaderParty. RecipientParty is the partner responsible for receiving a business document at a business application level. The SenderParty may be based on the datatype GDT:BusinessDocumentMessageHeaderParty.

The GoodsTag package is the grouping of GoodsTag with its packages. It includes the packages: TextCollection, LogisticUnit, Delivery, BusinessTransactionDocumentReferences, and Site. It includes a GoodsTag entity. GoodsTag includes the non-node elements: ID, ExternalSerialID, ProductionDate, ShippingDate, GoodsReceiptDate, ShippingPackageAttachedIndicator, CreationContextDependingDate, GrossWeightMeasure, Gross WeightMeasureTypeCode, GrossWeightMeasureTypeName, GrossWeightMeasureUnitCodeName, GrossVolumeMeasure, GrossVolumeMeasureTypeCode, GrossVolumeMeasureTypeName, GrossVolumeMeasureUnitCodeName, OutputRequestCreationDateTime, OutputRequestCreationIdentityID, OutputRequestCreationBusinessPartnerFormattedName, ImageFileContentBinaryObject, and TransportTracking ID may be based on GDT:GoodsTagID. ExternalSerialID may be based on GDT:SerialID. ProductionDate may be based on CDT:Date. ShippingDate may be based on CDT:Date. GoodsReceiptDate may be based on CDT:Date. ShippingPackageAttachedIndicator may be based on CDT:Indicator. CreationContextDependingDate may be based on CDT:Date. GrossWeightMeasure may be based on CDT:Measure. GrossWeightMeasureTypeCode may be based on GDT:MeasureTypeCode. GrossWeightMeasureTypeName may be based on CDT:LONG_Name. GrossWeightMeasureUnitCodeName may be based on CDT:Name. GrossVolumeMeasure may be based on CDT:Measure. GrossVolumeMeasureTypeCode may be based on GDT:MeasureTypeCode. GrossVolumeMeasureTypeName may be based on CDT:LONG_Name. GrossVolumeMeasureUnitCodeName may be based on CDT:Name.

OutputRequestCreationDateTime may be based on CDT:LOCAL_DateTime. OutputRequestCreationIdentityID may be based on GDT:IdentityID. OutputRequestCreationBusinessPartnerFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. ImageFileContentBinaryObject may be based on CDT:BinaryObject. TransportTracking may be based on GDT:TransportTracking. The GoodsTag package includes a node element TextCollection in a 1:C cardinality relationship, LogisticUnit in a 1:C cardinality relationship, Delivery in a 1:1 cardinality relationship, BusinessTransactionDocumentReferences in a 1:1 cardinality relationship, and Site in a 1:1 cardinality relationship.

The GoodsTagLogisticUnit package includes a LogisticUnit entity. LogisticUnit denotes the logistic unit of the package that is tagged by the goods tag. LogisticUnit includes the non-node elements: LogisticUnitID, LogisticUnitDescription, LogisticUnitQuantity, LogisticUnitQuantityTypeCode, and LogisticUnitQuantityTypeName. LogisticUnitID may be based on GDT:LogisticUnitID. LogisticUnitDescription may be based on GDT: SHORT_Description. LogisticUnitQuantity may be based on CDT:Quantity. LogisticUnitQuantityTypeCode may be based on GDT: QuantityTypeCode. LogisticUnitQuantityTypeName may be based on CDT:SHORT_Name.

The GoodsTagDelivery package includes a Delivery entity. Delivery denotes the delivery to which the goods tag is assigned. Delivery includes the non-node elements: ShipToAddress, ShipToAddressPostalCode, ShipToCountryCode, ShipToCountryName, ShipFromAddress, ShipFromCountryCode, ShipFromCountryName, Incoterms, BuyerPartyID, BuyerPartyFormattedName, SellerPartyID, SellerPartyFormattedName, RecipientPartyID, RecipientPartyFormattedName, VendorPartyID, VendorPartyFormattedName, FreightForwarderPartyID, and FreightForwarderPartyFormattedName. Incoterms includes the elements ClassificationCode, ClassificationName, and TransferLocationName. ShipToAddress may be based on GDT:FormAddress. ShipToAddressPostalCode may be based on GDT:PostalCode. ShipToCountryCode may be based on GDT:CountryCode. ShipToCountryName may be based on CDT:MEDIUM_Name. ShipFromAddress may be based on GDT:FormAddress. ShipFromCountryCode may be based on GDT:CountryCode. ShipFromCountryName may be based on CDT:MEDIUM_Name. Incoterms may be based on FMIDT:FormIncoterms. ClassificationCode may be based on GDT:IncotermsClassificationCode. ClassificationName may be based on CDT:Name. TransferLocationName may be based on GDT:IncotermsTransferLocationName. BuyerPartyID may be based on GDT:PartyID. BuyerPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. SellerPartyID may be based on GDT:PartyID. SellerPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. RecipientPartyID may be based on GDT:PartyID. RecipientPartyFormattedName CDT:LANGUAGEINDEPENDENT_LONG_Name. VendorPartyID may be based on GDT:PartyID. VendorPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name. FreightForwarderPartyID may be based on GDT:PartyID. FreightForwarderPartyFormattedName may be based on CDT:LANGUAGEINDEPENDENT_LONG_Name.

The GoodsTagBusinessTransactionDocumentReferences package includes a BusinessTransactionDocumentReferences entity. BusinessTransactionDocumentReferences is a unique reference between a business object and another business transaction document or business transaction document item. The referenced documents record a process of transportation or production. The identifiers of these documents can be printed on the goods tag. BusinessTransactionDocumentReferences includes the non-node elements: InboundDeliveryID, InboundDeliveryItemID, ConfirmedInboundDeliveryID, ConfirmedInboundDeliveryItemID, OutboundDeliveryID, OutboundDeliveryItemID, CreationContextDependingDeliveryID, CreationContextDependingDeliveryItemID, SalesOrderID, SalesOrderItemID, PurchaseOrderID, PurchaseOrderItemID, CustomerReturnID, CustomerReturnItemID, OriginPurchaseOrderID, and OriginPurchaseOrderItemID. InboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. InboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. ConfirmedInboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. ConfirmedInboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. OutboundDeliveryID may be based on GDT:BusinessTransactionDocumentID. OutboundDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. CreationContextDependingDeliveryID may be based on GDT:BusinessTransactionDocumentID. CreationContextDependingDeliveryItemID may be based on GDT:BusinessTransactionDocumentItemID. SalesOrderID may be based on GDT:BusinessTransactionDocumentID. SalesOrderItemID may be based on GDT:BusinessTransactionDocumentItemID. PurchaseOrderID may be based on GDT:BusinessTransactionDocumentID. PurchaseOrderItemID may be based on GDT:BusinessTransactionDocumentItemID. CustomerReturnID may be based on GDT:BusinessTransactionDocumentID. CustomerReturnItemID may be based on GDT:BusinessTransactionDocumentItemID. OriginPurchaseOrderID may be based on GDT:BusinessTransactionDocumentID. OriginPurchaseOrderItemID may be based on GDT:BusinessTransactionDocumentItemID.

The GoodsTagSite package includes a Site entity. Site denotes the site to which the goods tag is assigned. Site includes the non-node elements SiteID and SiteDescription. SiteID may be based on GDT:LocationID. SiteDescription may be based on GDT: SHORT_Description.

FIGS. 37-1 through 37-26 show an example configuration of an Element Structure that includes a FormMixedContentPackageTagNotification 370000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 370000 through 370840. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the FormMixedContentPackageTagNotification 370000 includes, among other things, a FormMixedContentPackageTagNotification 370002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 38-1 through 38-24 show an example configuration of an Element Structure that includes a FormSerialisedMaterialTagNotification 380000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 380000 through 380814. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the FormSerialisedMaterialTagNotification 380000 includes, among other things, a FormSerialisedMaterialTagNotification 380002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 39-1 through 39-27 show an example configuration of an Element Structure that includes a FormUniformContentPackageTagNotification 390000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 390000 through 390846. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the FormUniformContentPackageTagNotification 390000 includes, among other things, a FormUniformContentPackageTagNotification 390002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 40-1 through 40-21 show an example configuration of an Element Structure that includes a FormUnspecifiedContentPackageTagNotification 400000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 400000 through 400682. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the FormUnspecifiedContentPackageTagNotification 400000 includes, among other things, a FormUnspecifiedContentPackageTagNotification 400002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 41-1 through 41-4 depict an example object model for a business object Production Bill of Material Hierarchy 41000. The business object 41000 has relationships with other objects 41002-41010, as shown with lines and arrows. The business object 41000 hierarchically comprises elements 41012, 41014. The other objects 41002-41010 include respective elements 41016-41032 as shown.

The business object Production Bill of Material Hierarchy is a hierarchy of production bills of material that are needed to produce a given material. The business object Production Bill of Material Hierarchy belongs to the process component Production Model Management. A production bill of material represents a single level of the assembly of a material. The hierarchy starts at a given production bill of material variant and includes the production bill of materials of all levels below. The production bill of material hierarchy allows for reviewing the complete structure of a complex product. For example, the production bill of material of a bicycle may consist of a frame, a saddle, a front wheel (with tire), a back wheel (with tire), and handlebars. There may be production bill of materials on the second level for the two wheels. The production bill of material of the front wheel (with tire) may consist of a wheel, an inner tube, and a tire. The production bill of material of the front wheel (without tire) may consist of a hub, spokes, and a rim. The production bill of material hierarchy for the bicycle consists of all four production bill of materials. The production bill of material hierarchy of the front wheel with tire consists of the production bill of material of the front wheel with tire and the production bill of material of the front wheel without tire.

The Production Bill of Material Hierarchy business object includes an item that can represent the top-level output of a hierarchy, items at intermediate levels that originate from merging a bill of material input with a bill of material output, and items representing the bottom-level components. The business object Production Bill of Material Hierarchy is a hierarchy of production bills of material needed to produce a given material. It includes detailed information about each element of the hierarchy, (represented in items) such as validity and quantity that were determined for a certain date for a certain output quantity and were calculated to a defined depth.

The elements located at the node Production Bill of Material Hierarchy can be defined by the data type ProductionBillOfMaterialHierarchyElements. These elements include: ProductionBillOfMaterialUUID, ProductionBillOfMaterialVariantUUID, ProductionBillOfMaterialVariantKey, MaterialUUID, LogisticsPreparationFunctionalUnitUUID, LogisticsPreparationFunctionalUnitID, ProductRequirementSpecificationVersionUUID, ProductRequirementSpecificationKey, ExplosionDate, Quantity, QuantityTypeCode, and MaximumHierarchyLevelOrdinalNumberValue. ProductionBillOfMaterialVariantKey includes the elements BillOfMaterialVariantID and BillOfMaterialID. ProductRequirementSpecificationKey includes the elements RequirementSpecificationID and RequirementSpecificationVersionID. ProductionBillOfMaterialUUID is a globally unique identifier for a production bill of material to which the production bill of variant belongs. It may be based on datatype GDT: UUID. ProductionBillOfMaterialVariantUUID is a globally unique identifier for a production bill of material variant for which the multi level hierarchy of parts necessary to produce the material of the variant is presented. It may be based on datatype GDT: UUID. In some implementations, ProductionBillOfMaterialVariantUUID is used as an alternative key. ProductionBillOfMaterialVariantKey is a grouping of elements that uniquely identifies a variant of a bill of material for which the multi level hierarchy of parts necessary to produce the material of the variant is presented. It may be based on datatype KDT: BillOfMaterialVariantKey. BillOfMaterialVariantID is an identifier for the variant of a bill of material. It may be based on datatype GDT: BillOfMaterialVariantID. BillOfMaterialID is an identifier for a bill of material. It may be based on datatype GDT: BillOfMaterialID. MaterialUUID is a globally unique identifier for the material to be assembled. It may be based on datatype GDT: UUID. LogisticsPreparationFunctionalUnitUUID is a globally unique identifier for the functional unit responsible for logistics preparation of the top-level production bill of material. It may be based on datatype GDT: UUID. LogisticsPreparationFunctionalUnitID is an identifier for the functional unit responsible for logistics preparation of the top-level production bill of material. It may be based on datatype GDT: OrganisationalCentreID. ProductRequirementSpecificationVersionUUID is a globally unique identifier for the version of the product requirement specification that is used in the production process for which the production bill of material variant is relevant. It may be based on datatype GDT: UUID. ProductRequirementSpecificationKey is a grouping of elements that uniquely identify the product requirement specification that is used in the production process for which the production bill of material variant is relevant. It may be based on datatype KDT: RequirementSpecificationKey. RequirementSpecificationID is an identifier for a requirement specification that is unique within one system. It may be based on datatype GDT: RequirementSpecificationID. RequirementSpecificationVersionID is an identifier for the version of a requirement specification. It may be based on datatype GDT: VersionID. ExplosionDate represents the point in time when the bill of material is exploded. The explosion date of the root node lies within the validity period of any hierarchy item. The explosion date is used as filter condition for the hierarchy. The current date can be set as the default value for the explosion date. It may be based on datatype GDT: Date, Qualifier: Explosion. Quantity is a quantity of the material used in the calculation of the quantities in the hierarchy items. The quantity of the production bill of material variant can be set as the default value for this quantity. It may be based on datatype GDT: Quantity. QuantityTypeCode is a coded representation of a type of quantity used to uniquely identify the quantity. It may be based on datatype GDT: QuantityTypeCode. MaximumHierarchyLevelOrdinalNumberValue is a number defining the restriction of maximum item levels relevant for the depth calculation of the hierarchy. If the number is empty or equal to zero then it is interpreted as no restriction. It may be based on datatype GDT: OrdinalNumberValue, Qualifier: Level.

A composition relationship to subordinate Item node may exist in a 1:N cardinality relationship. An inbound aggregation relationship may exist from the business object Production Bill of Material/node Variant to ProductionBillOfMaterialVariant with a cardinality of 1:1, which may represent a production bill of material variant which defines the top level of the hierarchy. An inbound association relationship may exist from the business object Functional Unit/node Functional Unit to LogisticsPreparationFunctionalUnit with a cardinality of C:CN, which may represent a Logistics Preparation Functional Unit for the top level of Production Bill Of Material Hierarchy. An inbound association relationship may exist from the business object Material/node Material to Material with a cardinality of 1:CN, which may represent an assembly material which is defined at the top level of production bill of material hierarchy. An inbound association relationship may exist from the business object Product Requirement Specification/node Product Requirement Specification to Product Requirement Specification with a cardinality of C:CN, which may represent the product requirement specification that is assigned to the production bill of material variant. A specialization association for navigation relationship may exist from own business object/node Item to TopLevelItem with a target cardinality of 1, which may represent an item at the top level of the hierarchy. A specialization association for navigation relationship may exist from the business object Material/node Overview to MaterialOverview with a target cardinality of 1, which may represent an overview of the Material. A specialization association for navigation relationship may exist from the business object Production Bill of Material/node Root to ProductionBillOfMaterial with a target cardinality of 1, which may represent a production bill of material to which the variant belongs.

Item details the production bill of material item change state (if the item appears as a component in the hierarchy) and details of the production bill of material variant (if the item appears as an assembly in the hierarchy). It can be time dependent based on Validity Period. A component in a bill of material can be a piece of equipment or material used as part of the bill of material. An assembly can be the output part of a bill of material that can be produced with the usage of component of the bill of material.

The elements located at the node Item can be defined by the data type ProductionBillOfMaterialHierarchyItemElements. These elements include: MaterialUUID, ProductionBillOfMaterialItemGroupItemChangeStateUUID, ProductionBillOfMaterialItemGroupItemKey, ProductionBillOfMaterialUUID, ProductionBillOfMaterialVariantUUID, ProductionBillOfMaterialVariantKey ProductionBillOfMaterialItemGroupItemChangeStateEngineeringChangeOrderUUID, ProductionBillOfMaterialItemGroupItemChangeStateEngineeringChangeOrderID, ProductionBillOfMaterialVariantProductRequirementSpecificationVersionUUID, ProductionBillOfMaterialVariantProductRequirementSpecificationKey, HierarchyLevelOrdinalNumberValue, OrdinalNumberValue, ParentItemOrdinalNumberValue, ValidityDatePeriod, Quantity, QuantityTypeCode, ProductionBillOfMaterialItemGroupItemChangeStateQuantityFixedIndicator, and ChildItemActiveIndicator. ProductionBillOfMaterialItemGroupItemKey includes the elements BillOfMaterialItemGroupItemID and BillOfMaterialItemGroupKey. BillOfMaterialItemGroupKey includes the elements BillOfMaterialItemGroupID and BillOfMaterialID. ProductionBillOfMaterialVariantKey includes the elements ProductionBillOfMaterialVariantKey BillOfMaterialID. ProductionBillOfMaterialVariantProductRequirementSpecificationKey includes the elements RequirementSpecificationID and RequirementSpecificationVersionID. MaterialUUID is a globally unique identifier for the material to be assembled or required as a component for a material to be assembled. It may be based on datatype GDT: UUID. ProductionBillOfMaterialItemGroupItemChangeStateUUID is a globally unique identifier for the production bill of material item group item change state of the hierarchy item. It may be based on datatype GDT: UUID. ProductionBillOfMaterialItemGroupItemKey is a grouping of elements that uniquely identifies the production bill of material item group item to which the represented production bill of material change state of a hierarchy item belongs. It may be based on datatype KDT: BillOfMaterialItemGroupItemKey. BillOfMaterialItemGroupItemID is an identifier for an item group item. It is unique within a bill of material item group. It may be based on datatype GDT: BillOfMaterialItemGroupItemID. BillOfMaterialItemGroupKey is a grouping of elements that uniquely identifies an item group. If an item appears in the hierarchy as a component, then ProductionBillOfMaterialItemGroupItemKey is filled. It may be based on datatype KDT: BillOfMaterialItemGroupKey. BillOfMaterialItemGroupID is an identifier for an item group. It is unique within a bill of material. It may be based on datatype GDT: BillOfMaterialItemGroupID. BillOfMaterialID is an identifier for a bill of material. It may be based on datatype GDT: BillOfMaterialID. ProductionBillOfMaterialUUID is a globally unique identifier for the production bill of material to which the variant of a hierarchy item belongs. It may be based on datatype GDT: UUID. ProductionBillOfMaterialVariantUUID is a globally unique identifier for the production bill of material variant of a hierarchy item. It may be based on datatype GDT: UUID. ProductionBillOfMaterialVariantKey is a grouping of elements that uniquely identifies the production bill of material variant of a hierarchy item. If an item appears in the hierarchy as an assembly, then ProductionBillOfMaterialVariantKey is filled. It may be based on datatype KDT: BillOfMaterialVariantKey. ProductionBillOfMaterialVariantKey is an identifier for the variant of a bill of material. It may be based on datatype GDT: BillOfMaterialVariantID. BillOfMaterialID is an identifier for a bill of material. It may be based on datatype GDT: BillOfMaterialID. ProductionBillOfMaterialItemGroupItemChangeStateEngineeringChangeOrderUUID is a globally unique identifier for the engineering change order that is assigned to the production bill of material item group item change state of a hierarchy item. It may be based on datatype GDT: UUID. ProductionBillOfMaterialItemGroupItemChangeStateEngineeringChangeOrderID is an identifier for the engineering change order that is assigned to the production bill of material item group item change state of a hierarchy item. It may be based on datatype GDT: EngineeringChangeOrderID. ProductionBillOfMaterialVariantProductRequirementSpecificationVersionUUID is a globally unique identifier for the version of the product requirement specification that is used in the production process for which the production bill of material variant is relevant. In some implementations, ProductRequirementSpecification may be the same ProductRequirementSpecification that is assigned to the production bill of material hierarchy. It may be based on datatype GDT: UUID. ProductionBillOfMaterialVariantProductRequirementSpecificationKey is a grouping of elements that uniquely identify the product requirement specification that is used in the production process for which the production bill of material variant is relevant. In some implementations, the ProductRequirementSpecification may be the same ProductRequirementSpecification that is assigned to the production bill of material hierarchy. It may be based on datatype KDT: RequirementSpecificationKey, Qualifier: Product. RequirementSpecificationID is an identifier for a requirement specification that is unique within one system. It may be based on datatype GDT: RequirementSpecificationID. RequirementSpecificationVersionID is an identifier for the version of a requirement specification. It may be based on datatype GDT: VersionID. HierarchyLevelOrdinalNumberValue represents a level number in the hierarchy at which an item is located. In some implementations, the level number of the top-level item is equal to zero. It may be based on datatype GDT: OrdinalNumberValue, Qualifier: HierarchyLevel. OrdinalNumberValue represents an ordinal number of an item in the hierarchy. It may be based on datatype GDT: OrdinalNumberValue. ParentItemOrdinalNumberValue represents the ordinal number of the parent item. It may be based on datatype GDT: OrdinalNumberValue. ValidityDatePeriod represents a period in which an item is valid. In some implementations, the explosion date of the root node lies within the validity period of any hierarchy item. The validity period can be derived from an engineering change order assigned to the production bill of material item group item change state. It may be based on datatype GDT: CLOSED_DatePeriod, Qualifier: Validity. Quantity is a calculated quantity of an item based on the root quantity. It may be based on datatype GDT: Quantity. QuantityTypeCode is a coded representation of a type of quantity used to uniquely identify the quantity. It may be based on datatype GDT: QuantityTypeCode. ProductionBillOfMaterialItemGroupItemChangeStateQuantityFixedIndicator is an indicator that specifies whether or not the quantity of a production bill of material item group item change state, represented by the hierarchy item, of the assigned component material is fixed and independent of the quantity of the material to be assembled. It may be based on datatype GDT: Indicator, Qualifier: Fixed. ChildItemActiveIndicator is an indicator that specifies whether or not the child items of an item are active. In some implementations, if the HierarchyOrdinalLevelNumberValue of the item is smaller than the MaximumHierarchyOrdinalLevelNumber and the item exists as a production bill of material variant, then its child items are active. It may be based on datatype GDT: Indicator, Qualifier: Active.

An inbound association relationship may exist from the business object Engineering Change Order/node Engineering Change Order to EngineeringChangeOrder with a cardinality of C:CN, which may represent an engineering change order that controls the validity conditions of the change states of the production bill of material item of the hierarchy item. An inbound association relationship may exist from the business object Material/node Material to Material with a cardinality of 1:CN, which may represent material to be assembled or required as a component for a material to be assembled. An inbound association relationship may exist from the business object Product Requirement Specification/node Product Requirement Specification to Product Requirement Specification with a cardinality of C:CN, which may represent a product requirement specification that is assigned to the production bill of material variant of the hierarchy item. An inbound association relationship may exist from the business object Production Bill of Material/node Item Group Item Change State to ProductionBillOfMaterialItemGroupItemChangeState with a cardinality of C:CN, which may represent a production bill of material item group item change state of a hierarchy item which is a component. An inbound association relationship may exist from the business object Production Bill of Material/node Variant to ProductionBillOfMaterialVariant with a cardinality of C:CN, which may represent a production bill of material variant of a hierarchy item which an assembly. An inbound association relationship may exist from the business object Production Bill of Material Hierarchy/node Item to ParentItem with a cardinality of C:CN, which may represent a parent of an item. A specialization association for navigation relationship may exist from own business object/node Item to ChildItem with a target cardinality of CN, which may represent items which are children of a certain item. A specialization association for navigation relationship may exist from business object Material/node Overview to MaterialOverview with a target cardinality of 1, which may represent an overview of the material. A specialization association for navigation relationship may exist from business object Production Bill of Material/node Root to ProductionBillOfMaterial with a target cardinality of C, which may represent a production bill of material to which the item variant belongs.

In some implementations, there is exactly one item that has no parent (concerning the association ParentItem), which is the top-level item. This item can represent the final assembly of the hierarchy. The top-level item and the root include the same production bill of material variant key. In some implementations, the top-level item does not include any production bill of material item group item or item change state information. In some implementations, for any other item the production bill of material item group item change state data is optional. If an item includes production bill of material item group item change state data, it can also include the details for the production bill of material item group item and engineering change order.

FIG. 42 depicts an example Form Production Bill of Material Hierarchy Information Message Data Type 42000, which comprises elements 42002-42006, hierarchically related as shown. For example, the Form Production Bill of Material Hierarchy Information 42002 includes a Production Bill Of Material Hierarchy 42004.

The message type Form Production Bill of Material Hierarchy Information is derived from the business object ProductionBillOfMaterialHierarchy leading object together with its operation signature. Form Production Bill of Material Hierarchy Information is a form for preview and output of a production bill of material hierarchy. The structure of the Form Production Bill of Material Hierarchy Information message type can be determined by the message data type FormProductionBillOfMaterialHierarchyMessage.

The FormProductionBillOfMaterialHierarchyMessage message data type includes the object ProductionBillOfMaterialHierarchy which is included in the business document, and the business information that is relevant for sending a business document in a message. It includes the MessageHeader and ProductionBillOfMaterialHierarchy packages. This message data type provides the structure for the Form Production Bill of Material Hierarchy Information message type and the operations that are based on it.

The MessageHeader package is a grouping of business information that is relevant for sending a business document in a message. It includes the MessageHeader node. MessageHeader is a grouping of business information from the perspective of the sending application. It includes information to identify the business document in a message, information about the sender, and optionally, information about the recipient.

The ProductionBillOfMaterialHierarchy package is a grouping of ProductionBillOfMaterialHierarchy with its packages. It includes the Item package and the ProductionBillOfMaterialHierarchy entity. ProductionBillOfMaterialHierarchy is the hierarchy of production bills of material that are needed to get an overview of all assembly levels required to produce a material.

ProductionBillOfMaterialHierarchy includes the non-node elements: ProductionBillOfMaterialID, ProductionBillOfMaterialDescription, ProductionBillOfMaterialVariantID, ProductionBillOfMaterialVariantDescription, MaterialID, MaterialDescription, ExplosionDate, MaximumHierarchyLevelOrdinalNumberValue, and Quantity. Quantity includes the elements Quantity, QuantityMeasureUnitCodeName, QuantityTypeCode, and QuantityTypeCodeName. ProductionBillOfMaterialID may be based on datatype GDT:BillOfMaterialID. ProductionBillOfMaterialDescription may be based on datatype GDT:MEDIUM_Description. ProductionBillOfMaterialVariantID may be based on datatype GDT:BillOfMaterialVariantID. ProductionBillOfMaterialVariantDescription may be based on datatype GDT:MEDIUM_Description. MaterialID may be based on datatype GDT:ProductID. MaterialDescription may be based on datatype GDT:SHORT_Description. ExplosionDate may be based on datatype CDT:Date. MaximumHierarchyLevelOrdinalNumberValue may be based on datatype GDT:OrdinalNumberValue. Quantity may be based on datatype IDT:FormQuantity. The element Quantity may be based on datatype CDT:Quantity. QuantityMeasureUnitCodeName may be based on datatype CDT:Name. QuantityTypeCode may be based on datatype GDT:QuantityTypeCode. QuantityTypeCodeName may be based on datatype CDT:Name. The

ProductionBillOfMaterialHierarchy package includes a node element Item in a 1:N cardinality relationship. The ProductionBillOfMaterialHierarchyItem package includes the Item entity. Item of the Production Bill of Material Hierarchy holds details of the production bill of material item change state (if the item appears as a component in the hierarchy) and details of the production bill of material variant (if the item appears as a sub-assembly in the hierarchy). Item includes the non-node elements: HierarchyLevelOrdinalNumberValue, OrdinalNumberValue, ParentItemOrdinalNumberValue, MaterialID, MaterialDescription, ProductionBillOfMaterialID, ProductionBillOfMaterialDescription, ProductionBillOfMaterialDescription, ProductionBillOfMaterialVariantID, ProductionBillOfMaterialVariantDescription, ProductionBillOfMaterialItemGroupID, ProductionBillOfMaterialItemGroupItemID, ProductionBillOfMaterialItemGroupItemChangeStateEngineeringChangeOrderID, Quantity, ValidityDatePeriod, and ProductionBillOfMaterialItemGroupItemChangeStateQuantityFixedIndicator. Quantity includes the elements Quantity, QuantityMeasureUnitCodeName, QuantityTypeCode, and QuantityTypeCodeName. HierarchyLevelOrdinalNumberValue may be based on datatype GDT: OrdinalNumberValue. OrdinalNumberValue may be based on datatype GDT:OrdinalNumberValue. ParentItemOrdinalNumberValue may be based on datatype GDT:OrdinalNumberValue. MaterialID may be based on datatype GDT:ProductID. MaterialDescription may be based on datatype GDT:SHORT_Description. ProductionBillOfMaterialID may be based on datatype GDT: BillOfMaterialID. ProductionBillOfMaterialDescription may be based on datatype GDT:MEDIUM_Description. ProductionBillOfMaterialVariantID may be based on datatype GDT:BillOfMaterialVariantID. ProductionBillOfMaterialVariantDescription may be based on datatype GDT:MEDIUM_Description. ProductionBillOfMaterialItemGroupID may be based on datatype GDT:BillOfMaterialItemGroupID. ProductionBillOfMaterialItemGroupItemID may be based on datatype GDT:BillOfMaterialItemGroupItemID. ProductionBillOfMaterialItemGroupItemChangeStateEngineeringChangeOrderID may be based on datatype GDT:EngineeringChangeOrderID. Quantity may be based on datatype IDT:FormQuantity. The element Quantity may be based on datatype CDT:Quantity. QuantityMeasureUnitCodeName may be based on datatype CDT:Name. QuantityTypeCode may be based on datatype GDT:QuantityTypeCode. QuantityTypeCodeName may be based on datatype CDT:Name. ValidityDatePeriod may be based on datatype GDT:CLOSED_DatePeriod. ProductionBillOfMaterialItemGroupItemChangeStateQuantityFixedIndicator may be based on datatype CDT:Indicator.

FIGS. 43-1 through 43-6 show an example configuration of an Element Structure that includes a FormProductionBillOfMaterialHierarchy 430000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 430000 through 430212. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the FormProductionBillOfMaterialHierarchy 430000 includes, among other things, a FormProductionBillOfMaterialHierarchy 430002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 44-1 through 44-21 depict an example object model for a business object ReleaseOrder_Template 44000. The business object 44000 has relationships with other objects 44002-44022, as shown with lines and arrows. The business object 44000 hierarchically comprises elements 44024-44096. The other objects 44002-44022 include respective elements 44098-44134 as shown.

The business object ReleaseOrder_Template is a template that includes the maximal possible set of nodes, relationships, attributes, and operations for a procurement release order and similar objects derived from the template. A release order is a request to release a specified quantity of material for delivery within a specified time. This request includes information about the material flow. If the material flow represents a sales process, the financial conditions can be specified by referring to an outline agreement.

The business object is used within Third-Party Direct Ship by a buyer to request that a seller delivers a specified quantity of material within a specified time. It is used during Intra Company Stock Transfer as a means to control the shipment of goods from one location to another within a company.

The ReleaseOrder_Template includes the main parts the Root and the Item. The Root includes information on parties, locations, and status with information on the ordered goods or the goods to be delivered. The Item includes information on the product to be delivered and its quantities, as well as on parties and status.

The Business Object is involved in the Process Component Interaction Models: External Procurement Trigger and Response_Accounting, External Procurement Trigger and Response_Outbound Delivery Processing, External Procurement Trigger and Response_Supplier Invoice Processing, and External Procurement Trigger Response_Customer Requirement Processing at Supplier.

The technical name for Service Interface Sales and Purchasing Accounting Out is ExternalProcurementTriggerAndResponseSalesAndPurchasingAccountingOut. The Service Interface Sales and Purchasing Accounting Out is part of the External Procurement Trigger and Response_Accounting Process Component Interaction Models. It is an interface that informs accounting about the creation or cancellation of a procurement release order, or of accounting-relevant changes to a procurement release order.

The technical name for Notify of Procurement Release Order is ExternalProcurementTriggerAndResponseSalesAndPurchasingAccountingOut.NotifyOfProcurementReleaseOrder. It notifies accounting that a procurement release order has been created, changed, or canceled. The operation can be based on message type Sales And Purchasing Accounting Notification (derived from business object Accounting Notification).

The technical name for Service Interface Delivery Fulfilment In is ExternalProcurementTriggerAndResponseDeliveryFulfilmentIn. The Service Interface Delivery Fulfilment In is part of the External Procurement Trigger and Response_Outbound Delivery Processing Process Component Interaction Models. It is an interface that performs the update of a procurement release order based on delivery fulfillment confirmation and reconciliation.

The technical name for Change Procurement Release Order based on Delivery Fulfilment Confirmation is ExternalProcurementTriggerAndResponseDeliveryFulfilmentInChgProcmtReleaseOrderBasedOnDeliveryFulfilmentConfirmation. It updates a procurement release order with fulfillment confirmation data from an outbound delivery request. The operation can be based on message type Delivery Request Fulfilment Confirmation (derived from business object Delivery Request_Template).

The technical name for Service Interface Delivery Fulfilment Out is ExternalProcurementTriggerAndResponseDeliveryFulfilmentOut. The Service Interface Delivery Fulfilment Out is part of the External Procurement Trigger and Response_Outbound Delivery Processing Process Component Interaction Models. It is an interface to request delivery fulfillment.

The technical name for Request Delivery Fulfilment is ExternalProcurementTriggerAndResponseDeliveryFulfilmentOut.RequestDeliveryFulfilment. It can create or update an outbound delivery request. The operation can be based on message type Delivery Request Fulfilment Request (derived from business object Delivery Request_Template).

The technical name for Service Interface Invoice Verification Out is ExternalProcurementTriggerAndResponseInvoiceVerificationOut. The Service Interface Invoice Verification Out is part of the External Procurement Trigger and Response_Supplier Invoice Processing Process Component Interaction Models. It is an interface that informs supplier invoice processing that a procurement release order expects a supplier invoice, as a follow-on document. It provides supplier invoice processing with the data necessary to create a supplier invoice request.

The technical name for Notify of Invoicing Due is ExternalProcurementTriggerAndResponseInvoiceVerificationOut.NotifyOfInvoicingDue. It notifies supplier invoice processing about a new, changed, or canceled procurement release order. The operation can be based on message type Invoicing Due Notification (derived from business object Supplier Invoice Request).

The technical name Service Interface Releasing In is ExternalProcurementTriggerAndResponseReleasingIn. The Service Interface Releasing In is part of the External Procurement Trigger Response_Customer Requirement Processing at Supplier Process Component Interaction Models. It is an interface to update a procurement release order.

The technical name for Change Procurement Release Order based on Procurement Release Order Confirmation is ExternalProcurementTriggerAndResponseReleasingIn.ChangeProcurementReleaseOrderBasedOnProcurementReleaseOrderConfirmation. It updates a procurement release order based on confirmation received from customer requirement processing at a supplier. The operation can be based on message type Procurement Release Order Confirmation (derived from business object Procurement Release Order).

The technical name for Service Interface Releasing Out is ExternalProcurementTriggerAndResponseReleasingOut. The Service Interface Releasing Out is part of the External Procurement Trigger Response_Customer Requirement Processing at Supplier Process Component Interaction Models. It is an interface to request creation, update, or cancelation of a procurement release order.

The technical name for Request Release Order is ExternalProcurementTriggerAndResponseReleasingOut.RequestReleaseOrder. It can create, update, or request the cancelation of a procurement release order. The operation is based on message type Form Procurement Release Order Request (derived from business object Procurement Release Order).

ReleaseOrder_Template root node is a composition of goods provided for shipping by a vendor. ReleaseOrder_Template has a Procurement Release Order projection. The projection is a request sent to a goods supplier from a procurement officer to deliver a specified quantity of material within a specified time. The elements located at the ReleaseOrder_Template node can be defined by the datatype ReleaseOrderElements. These elements include: UUID, ID, TypeCode, ProcessingTypeCode, OrderingDateTime, OrderedDateTime, FulfilmentBlockStartDateTime, SystemAdministrativeData, and Status. Status includes OrderingStatusCode, FulfilmentBlockingStatusCode, and ItemListLifeCycleStatusCode elements. UUID is a universal unique identifier for a business object derived from ReleaseOrder_Template. It may be based on datatype GDT: UUID. In some implementations, UUID is used as an alternative key. ID is an identifier for ReleaseOrder_Template. It may be based on datatype GDT: BusinessTransactionDocumentID. In some implementations, ID is used as an alternative key. TypeCode is a coded representation of the release order object type. It may be based on datatype GDT: ObjectTypeCode. ProcessingTypeCode is a coded representation of the processing of a release order. It may be based on datatype GDT: BusinessTransactionDocumentProcessingTypeCode. OrderingDateTime represents a point in time when the release order has to be ordered. It may be based on datatype GDT: LOCALNORMALISED_DateTime with Qualifier: Ordering. OrderedDateTime represents a point in time when the release order was ordered. It may be based on datatype GDT: LOCALNORMALISED_DateTime with Qualifier: Ordered. FulfilmentBlockStartDateTime represents a point in time when the fulfillment of a release order is blocked. After this time, the fulfillment of a release order may be blocked. It may be based on datatype GDT: GLOBAL_DateTime with Qualifier: Start. SystemAdministrativeData represents administrative data recorded by the system. This data includes system users and change times. It may be based on datatype GDT: SystemAdministrativeData. Status represents the current status of a release order. It may be based on datatype BOIDT: ReleaseOrderStatus. OrderingStatusCode describes the ordering status of a release order. It may be based on datatype GDT: OrderingStatusCode. FulfilmentBlockingStatusCode describes the fulfillment blocking status of a release order. It may be based on datatype GDT: NOTBLOCKEDBLOCKED_BlockingStatusCode with Qualifier: Fulfilment. ItemListLifeCycleStatusCode describes the lifecycle status of the item list of release order. The life cycle status of the list of items indicates the state of the release order in its life cycle. It may be based on datatype GDT: ReleaseOrderItemListLifeCycleStatusCode. The elements of the present node can be used in every derived BO.

A composition relationship to a BusinessProcessVariantType subordinate node can exist with a 1:N cardinality relationship. A composition relationship to a BusinessTransactionDocumentReference subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a Party subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a Location subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to an Item subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a AttachmentFolder subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a TextCollection subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ControlledOutputRequest subordinate node can exist with a 1:C cardinality relationship. An inbound association relationship may exist from the business object Identity/node Identity to LastChangeIdentity with a cardinality of 1:CN, which may identify the identity that has last changed the release order. An inbound association relationship may exist from the business object Identity/node Identity to CreationIdentity with a cardinality of 1:CN, which may identify the identity that has created the release order.

The following specialization associations for navigation may exist to the node Party: BuyerParty with a target cardinality of C, EndBuyerParty with a target cardinality of C, SellerParty with a target cardinality of C, FreightForwarderParty with a target cardinality of C and LogisticsRequestResponsibleParty with a target cardinality of C. The following specialization associations for navigation may exist to the node Location: BuyerParty with a target cardinality of C and ShipFromLocation with a target cardinality of C. A BusinessDocumentFlow specialization association for navigation may exist to the business object Business BusinessDocumentFlow/node Root with a target cardinality of 1. The following specialization associations for navigation may exist to the node BusinessTransactionDocumentReference: BaseBusinessTransactionDocumentReference with a target cardinality of C, SalesOrderReference with a target cardinality of C, OriginPurchaseOrderReference with a target cardinality of C, and CustomerRequirementReference with a target cardinality of C. A BuyerParty specialization association for navigation may exist to the node BusinessProcessVariantType with a target cardinality of C.

Release Order_Template may be associated with the following enterprise service infrastructure actions: Order, Block Fulfilment, and Unblock Fulfilment. The Order action can be used to order all items of the release order. In some implementations, this action is applicable only for release orders that are not yet ordered. In response to the Order action, the action sets the “Ordering” status variable to “Ordered.” The Block Fulfilment action can be used to block the release order for delivery by setting a delivery block. In some implementations, this action is valid only for those items that are relevant for delivery. In response to the Block Fulfilment action, the action sets the “Fulfilment blocking” status variable to “Blocked.” The Unblock Fulfilment action can be used to reset the delivery block. In some implementations, this action is applicable for only those delivery-relevant items for which a delivery block has been set. In response to the Unblock Fulfilment action the action changes the “Fulfilment blocking” status variable from “Blocked” to “Not Blocked.”

Release Order_Template may be associated with Query By Elements and Select All queries. The Query By Elements query returns a list of all release orders that satisfy the selection criteria. The query elements can be defined by the datatype ReleaseOrderElementsQueryElements. These elements include: ID, OrderingDateTime, OrderedDateTime, CustomerRequirementAvailabilityConfirmationitemReference, SalesOrderItemReference, PurchasingContractItemReference, OriginPurchaseOrderItemReference, SellerPartyKey, EndBuyerPartyKey, BuyerPartyKey, ItemProductRecipientPartyKey, ItemProductKey, ProductCategoryIDKey, Status, ItemCancellationInitiatorCode, ItemBaseBusinessTransactionDocumentCancellationRequestedIndicator, ItemFulfilmentBlockedIndicator, ItemOpenQuantityCancelledIndicator, ItemConfirmationScheduleLineArrivalDateTimePeriod, ItemRequestScheduleLineRequestedArrivalDateTimePeriod, ItemProductRequirementSpecificationKey, SystemAdministrativeData, and SearchText. SellerPartyKey, EndBuyerPartyKey, BuyerPartyKey, ItemProductRecipientPartyKey, and ItemProductKey include PartyTypeCode and PartyID elements. ItemProductKey includes the ProductTypeCode, ProductIdentifierTypeCode, and ProductID elements. ProductCategoryIDKey includes ProductCategoryHierarchyID and ProductCategoryInternalID elements. Status includes OrderingStatusCode, ItemListLifeCycleStatusCode, ItemOrderingStatusCode, ItemCancellationStatusCode, ItemFulfilmentProcessingStatusCode, ItemFulfilmentStatusCode, ItemProductAvailabilityConfirmationStatusCode, and ItemLifeCycleStatusCode elements. ItemProductRequirementSpecificationKey includes RequirementSpecificationID and RequirementSpecificationVersionID elements. SystemAdministrativeData includes CreationDateTime, CreationIdentityUUID, CreationIdentityID, CreationIdentityBusinessPartnerinternalID, CreationIdentityBusinessPartnerPersonFamilyName, CreationIdentityBusinessPartnerPersonGivenName, CreationIdentityEmployeeID, LastChangeDateTime, LastChangeIdentityUUID, LastChangeIdentityID, LastChangeIdentityBusinessPartnerInternalID, LastChangeIdentityBusinessPartnerPersonFamilyName, LastChangeIdentityBusinessPartnerPersonGivenName, and LastChangeIdentityEmployeeID elements.

The ID of the release order matches the query element ID. It may be based on datatype GDT: BusinessTransactionDocumentID. The OrderingDateTime of the release order matches the query element OrderingDateTime. It may be based on GDT: LOCALNORMALISED_DateTime with Qualifier: Ordering. The OrderedDateTime of the release order matches the query element OrderedDateTime. It may be based on GDT: LOCALNORMALISED_DateTime with Qualifier: Ordered. CustomerRequirementAvailabilityConfirmationitemReference may be based on GDT: BusinessTransactionDocumentReference. SalesOrderItemReference may be based on GDT: BusinessTransactionDocumentReference. PurchasingContractItemReference may be based on GDT: BusinessTransactionDocumentReference. OriginPurchaseOrderItemReference may be based on GDT: BusinessTransactionDocumentReference. SellerPartyKey may be based on KDT: PartyKey. EndBuyerPartyKey may be based on KDT: PartyKey. BuyerPartyKey may be based on KDT: PartyKey. ItemProductRecipientPartyKey may be based on KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on GDT: PartyID. ItemProductKey may be based on KDT: ProductKey. ProductTypeCode is a coded representation of a product type such as a material or service. It may be based on GDT: ProductTypeCode. ProductIdentifierTypeCode is a coded representation of a product identifier type. It may be based on GDT: ProductIdentifierTypeCode. ProductID is an identifier for a product. It may be based on GDT: ProductID. ProductCategoryIDKey may be based on KDT: ProductCategoryHierarchyProductCategoryIDKey. In some implementations, it can be used only for searching in the context of an item product. ProductCategoryHierarchyID is an identifier for a product category hierarchy. It may be based on GDT: ProductCategoryHierarchyID. ProductCategoryInternalID is an identifier for a product category. It may be based on GDT: ProductCategoryInternalID. Status may be based on QueryIDT: QueryElementReleaseOrderStatus. OrderingStatusCode describes the ordering status of a release order. It may be based on GDT: OrderingStatusCode. ItemListLifeCycleStatusCode describes the lifecycle status of the item list of release order. The life cycle status of the list of items indicates the state of the release order in its life cycle. It may be based on GDT: ReleaseOrderItemListLifeCycleStatusCode. ItemOrderingStatusCode describes the ordering status of a release order item. It may be based on GDT: OrderingStatusCode. ItemCancellationStatusCode describes the cancellation status of a release order item. It may be based on GDT: CancellationStatusCode. ItemFulfilmentProcessingStatusCode describes the fulfillment processing status of a release order item. It may be based on GDT: NOTSTARTEDINPROCESSFINISHED_ProcessingStatusCode with Qualifier: Fulfilment. ItemFulfilmentStatusCode describes the fulfillment status of a release order item. It may be based on GDT: ReleaseOrderItemFulfilmentStatusCode. ItemProductAvailabilityConfirmationStatusCode describes the product availability confirmation status of a release order item. It may be based on GDT: ProductAvailabilityConfirmationStatusCode. ItemLifeCycleStatusCode describes the life cycle status of a release order item. It may be based on GDT: ReleaseOrderItemLifeCycleStatusCode. ItemCancellationInitiatorCode may be based on GDT: CancellationInitiatorCode. ItemBaseBusinessTransactionDocumentCancellationRequestedIndicator may be based on GDT: Indicator with Qualifier: Requested. ItemFulfilmentBlockedIndicator may be based on GDT: Indicator with Qualifier: Blocked. ItemOpenQuantityCancelledIndicator may be based on GDT: Indicator with Qualifier: Cancelled. ItemConfirmationScheduleLineArrivalDateTimePeriod may be based on GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Arrival. ItemRequestScheduleLineRequestedArrivalDateTimePeriod may be based on GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Arrival. ItemProductRequirementSpecificationKey may be based on KDT: RequirementSpecificationKey. RequirementSpecificationID is an identifier for a requirement specification that is unique within one system. It may be based on GDT: RequirementSpecificationID. RequirementSpecificationVersionID is an identifier for the version of a requirement specification. It may be based on GDT: VersionID. SystemAdministrativeData may be based on QueryIDT: QueryElementSystemAdministrativeData. CreationDateTime represents the point in time (e.g., date and time stamp) of the creation. It may be based on GDT: GLOBAL_DateTime. CreationIdentityUUID is a globally unique identifier for the identity who did the creation. It may be based on GDT: UUID. CreationIdentityID is an identifier for the identity who did the creation. It may be based on GDT: IdentityID. CreationIdentityBusinessPartnerInternalID is a proprietary identifier for the business partner that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on GDT: BusinessPartnerInternalID. CreationIdentityBusinessPartnerPersonFamilyName represents a family name of the business partner of the category person that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on GDT: LANGUAGEINDEPENDENT_MEDIUM_Name.

CreationIdentityBusinessPartnerPersonGivenName represents a given name of the business partner of the category person that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. CreationIdentityEmployeeID is an identifier for the employee that is attributed to the creation identity and that can be reached following the relationships of the creation identity. It may be based on GDT: EmployeeID. LastChangeDateTime represents the point in time (e.g., date and time stamp) of the last change. It may be based on GDT: GLOBAL_DateTime. LastChangeIdentityUUID is a globally unique identifier for an identity who made the last changes. It may be based on GDT: QUID. LastChangeIdentityID is an identifier for an identity who made the last changes. It may be based on GDT: IdentityID. LastChangeIdentityBusinessPartnerInternalID is a proprietary identifier for the business partner that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on GDT: BusinessPartnerInternalID. LastChangeIdentityBusinessPartnerPersonFamilyName represents a family name of the business partner of the category person that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. LastChangeIdentityBusinessPartnerPersonGivenName represents a given name of the business partner of the category person that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on GDT: LANGUAGEINDEPENDENT_MEDIUM_Name. LastChangeIdentityEmployeeID is an identifier for the employee that is attributed to the last change identity and that can be reached following the relationships of the last change identity. It may be based on GDT: EmployeeID. SearchText represents free text including one or several words (e.g., search terms) to search for Release Orders. It may be based on GDT: SearchText.

In some implementations, for every query that includes the SearchText as query parameter, an application-specific subset of the other query parameters is defined. The query result is calculated in a series of steps. The search terms are assigned to the subset of query parameters in such a way that every search term is used exactly once in the assignment. Several search terms may be assigned to the same query parameter. For each of these assignments the query result is calculated. The total result is the union of the results calculated per assignment. The query parameters can be used in every derived BO.

The Select All query provides the NodeIDs of all instances of this node. This query is used to enable the initial load of data for the Fast Search Infrastructure. The actions and queries of the present node can be used in every derived BO.

Business Process Variant Type is the processing of a release order within a process component from a business point of view. A Business Process Variant is a configuration of a process component. In some implementations, a Business Process Variant belongs to exactly one process component. A process component is a software package that realizes a business process and exposes its functionality as services. The functionality includes business transactions. A process component includes one or more semantically related business objects. In some implementations, a business object belongs to exactly one process component.

The elements located at the Business Process Variant Type node can be defined by the datatype ReleaseOrderBusinessProcessVariantTypeElements. These elements include BusinessProcessVariantTypeCode and MainIndicator. BusinessProcessVariantTypeCode is a coded representation of a business process variant type of a ReleaseOrderBusinessProcessVariantType. It may be based on datatype GDT: BusinessProcessVariantTypeCode. MainIndicator is an indicator that specifies if the current BusinessProcessVariantTypeCode is the main one. It may be based on datatype GDT: Indicator with Qualifier: Main. The elements of the present node can be used in every derived BO.

Business Transaction Document Reference is a unique reference to a different business document or the business document relevant to the release order. The elements located at the Business Transaction Document Reference node can be defined by the datatype ReleaseOrderBusinessTransactionDocumentReferenceElements. These elements include BusinessTransactionDocumentReference and BusinessTransactionDocumentRelationshipRoleCode. BusinessTransactionDocumentReference is a unique reference to another business transaction document or business transaction document item. It may be based on datatype GDT: BusinessTransactionDocumentReference. BusinessTransactionDocumentRelationshipRoleCode is a coded representation of the role the referenced document plays in relation to the release order. It may be based on datatype GDT: BusinessTransactionDocumentRelationshipRoleCode. The elements of the present node can be used in every derived BO.

An inbound association relationship may exist from the business object Customer Requirement/node Customer Requirement to CustomerRequirement with a cardinality of C:CN, which may represent the association to the Customer Requirement in the Procurement Release Order. An inbound association relationship may exist from the business object Purchase Order/node Purchase Order to OriginPurchaseOrder with a cardinality of C:CN, which may represent the association to the origin purchase order, the purchase order that was posted by the end-buyer. An inbound association relationship may exist from the business object Sales Order/node Sales Order to SalesOrder with a cardinality of C:CN, which may represent the association to the sales order that triggered the creation of the Procurement Release Order. The inbound aggregation relationship of the BusinessTransactionDocumentReference may depend on the business object derived from the release order template.

Party is a natural or legal person, organization, organizational unit, or group that is involved in a release order processing in a party role. The elements located at the node Party can be defined by the datatype ReleaseOrderPartyElements. These elements include: PartyKey, PartyUUID, RoleCategoryCode, RoleCode, AddressReference, DeterminationMethodCode, MainIndicator, and Name. PartyKey includes the PartyTypeCode and PartyID elements. PartyKey represents a Key of the Party in this PartyRole in the business document or the master data object. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. PartyUUID is a unique identifier for a business partner, the organizational unit, or their specializations. It may be based on datatype GDT: UUID. RoleCategoryCode is a Party Role Category of the Party in the business document or the master data object. It may be based on datatype GDT: PartyRoleCategoryCode. RoleCode is a Party Role of the Party in the business document or the master data object. It may be based on datatype GDT: PartyRoleCode. AddressReference represents information to reference the address of a Party. It may be based on datatype GDT: PartyAddressReference. DeterminationMethodCode is a coded representation of the PartyDeterminationMethod. It may be based on datatype GDT: PartyDeterminationMethodCode. MainIndicator indicates whether or not an ItemParty is emphasized in a group of parties with the same PartyRole. It may be based on datatype GDT: Indicator with Qualifier: Main. Name is a Name of the Party. It may be based on datatype GDT: LONG_Name. The elements of the present node can be used in every derived BO.

A composition relationship to a PartyContactParty subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a PartyAlternativeIdentification subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a PartyAddress subordinate node can exist with a 1:C cardinality relationship. An inbound aggregation relationship may exist from the business object Party/node Party to Party with a cardinality of C:CN, which may represent the Referenced Party in master data.

A MainContactParty specialization association for navigation may exist to the node PartyContactParty with a target cardinality of C. A UsedAddress specialization association for navigation may exist to the business object Business UsedAddress/node Root with a target cardinality of CN.

The address used for the Party can be a referenced address of the master data object, or the PartyAddress integrated via the composition relationship. Which address applies can be determined by looking at the PartyAddressHostTypeCode element. The instance of the TO UsedAddress represents this address. The association is implemented. The referenced address of the master data object is used if the node ID of the node in the master data object is determined via the PartyTypeCode, PartyAddressUUID, and PartyAddressHostTypeCode elements, that have the composition relationship to the dependent object address that is to be represented by the TO UsedAddress. The TO UsedAddress in the implemented association is provided with the following information: that this is an example of a master data address, and BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object. Party node. In some implementations, this is required in case changes where the TO UsedAddress take place. The master data address is copied by the TO UsedAddress, the changes take place to the copy, and a corresponding DO Address is created at the business object node Party via the PartyAddress composition relationship. The PartyAddress integrated via the composition relationship is used if the TO UsedAddress is informed of the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object-Party. Information is provided that this is not an example of a referenced address. The TO UsedAddress represents the dependent object address used at the business object node-Party via the PartyAddress composition relationship.

An IdentifiedByFreightForwarderParty specialization association for navigation may exist to the node PartyAlternativeIdentification with a target cardinality of C. An IdentifiedByEndBuyerParty specialization association for navigation may exist to the node PartyAlternativeIdentification with a target cardinality of C. An IdentifiedByBuyerParty specialization association for navigation may exist to the node PartyAlternativeIdentification with a target cardinality of C. An IdentifiedBySellerParty specialization association for navigation may exist to the node PartyAlternativeIdentification with a target cardinality of C. A UsedAddressOverview specialization association for navigation may exist to the business object UsedAddress/node Overview with a target cardinality of CN. This association may be equal to the association to UsedAddress-Root.

Party Contact Party is a natural person or organizational unit that can be contacted for the party. The contact may be a contact person or, for example, a secretary's office. Communication data for the contact may be available. The elements located at the Party Contact Party node can be defined by the datatype ReleaseOrderPartyContactPartyElements. These elements include: PartyKey, PartyUUID, AddressReference, MainIndicator, and Name. PartyKey includes the PartyTypeCode and PartyID elements. PartyKey represents the Key of the Party in this PartyRole in the business document or the master data object. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. PartyUUID is a unique identifier of the contact in this PartyRole in the business document or the master data object. It may be based on datatype GDT: UUID. AddressReference represents information to reference the address of a Party. It may be based on datatype GDT: PartyAddressReference. MainIndicator indicates whether or not a PartyContactParty is emphasized in a group of contact parties with the same PartyRole. It may be based on datatype GDT: Indicator with Qualifier: Main. Name represents a Name of the PartyContactParty. It may be based on datatype GDT: LONG_Name. The elements of the present node can be used in every derived BO.

A composition relationship to a PartyContactPartyAddress subordinate node can exist with a 1:C cardinality relationship. An inbound aggregation relationship may exist from the business object Party/node Party to Party with a cardinality of C:CN, which may represent the Referenced Party in master data. A UsedAddress specialization association for navigation may exist to the business object UsedAddress/node Root with a target cardinality of CN. Address may be used for Party. This may be the referenced address of a master data object or an address referenced via the composition to PartyAddress. A UsedAddressOverview specialization association for navigation may exist to the business object UsedAddress/node Overview with a target cardinality of CN. This association may be equal to the association to UsedAddress-Root. In some implementations, there may only be one of the associations to the address. This address is a master data address of the business partner, organizational unit, or their specializations referenced by PartyUUID.

Party Contact Party Address (Dependent Object Inclusion Node) is a dependent object address including the document specific address of the contact party. The data can be defined by the dependent object address.

Party Alternative Identification is an alternative identification to the identified party in Party node. The elements located at the node Party Alternative Identification can be defined by the datatype ReleaseOrderPartyAlternativeIdentificationElements. These elements include: PartyID, PartyIdentifierTypeCode, IdentifiedByPartyRoleCode, and IdentifiedByPartyRoleCategoryCode. PartyID is an ID of the alternative identified party. It may be based on datatype GDT: NOALPHANUMERICCONVERSION_PartyID. PartyIdentifierTypeCode is a coded representation of a type of identifier for a party. It may be based on datatype GDT: PartyIdentifierTypeCode. IdentifiedByPartyRoleCode is a role code that identifies the party. It may be based on datatypeGDT: PartyRoleCode with Qualifier: IdentifiedBy. IdentifiedByPartyRoleCategoryCode is a role category code that identifies the party. It may be based on datatype GDT: PartyRoleCategoryCode with Qualifier: IdentifiedBy. The elements of the present node can be used in every derived BO.

Party Address is a dependent object address containing the document specific address of the party. The data can be defined by the dependent object address.

Location represents a physical or logical location that is part of the release order process in a location role. A location may keep a reference to a business object location, keep a reference to an address, keep a reference to a business partner or one of its specializations (for example customer, supplier, or employee), or keep a reference to a Reporting Line Unit specialization of an organizational unit. The location role describes the role of a location in the release order process.

The elements located at the node Location can be defined by the datatype ReleaseOrderLocationElements. These elements include: LocationID, LocationUUID, AddressReference, RoleCode, and RoleCategoryCode. AddressReference includes AddressHostUUID, BusinessObj ectTypeCode, AddressHostTypeCode, PartyKey, InstalledBaseID, and InstallationPointID elements. PartyKey includes PartyTypeCode PartyID and elements. LocationID is an identifier of the Location in this LocationRole. It may be based on datatype GDT: LocationID. LocationUUID is a unique identifier for a location, business partner, organizational unit, or their specializations. It may be based on datatype GDT: UUID. AddressReference represents the information to reference the address of a Location. It may be based on datatype BOIDT: ObjectNodeLocationAddressReference. AddressHostUUID is a universally unique identifier for the address of the business partner, the organizational unit or its specializations, the business object InstalledBase, or the business object InstallationPoint. It may be based on datatype GDT: UUID. BusinessObjectTypeCode is a coded representation of the type of the business object, in which the address referenced in the LocationAddressUUID is integrated as a dependent object. It may be based on datatype GDT: BusinessObjectTypeCode. AddressHostTypeCode is a coded representation of the address host type of the address referenced by the AddressUUID or the address included using the Location Address composition. It may be based on datatype GDT: AddressHostTypeCode. PartyKey is an alternative identifier of a party, representing a business partner or an organizational unit, that references the address using the AddressUUID. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. InstalledBaseID is an identifier for an installed base that references the address using the AddressUUID. It may be based on datatype GDT: InstalledBaseID. InstallationPointID is an identifier for an installation point that references the address using the AddressUUID. It may be based on datatype GDT: InstallationPointID. RoleCode represents a Location Role of the Location. It may be based on datatype GDT: LocationRoleCode. RoleCategoryCode represents a Location Role Category of the Location. It may be based on datatype GDT: LocationRoleCategoryCode. The elements of the present node can be used in every derived BO.

A composition relationship to a LocationAddress subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a LocationAlternativeIdentification subordinate node can exist with a 1:CN cardinality relationship. An inbound aggregation relationship may exist from the business object Location/node Location to Location with a cardinality of C:CN, which may represent a Location corresponding to the Location. An inbound aggregation relationship may exist from the business object Party/node Address Information to PartyAddressInformation with a cardinality of C:CN, which may represent AddressInformation of a representative of a Business Partner or Organizational Centre corresponding to the Location. A UsedAddressOverview specialization association for navigation may exist to the business object UsedAddress/node Overview with a target cardinality of CN. This association may be equal to the association to UsedAddress-Root. A UsedAddress specialization association for navigation may exist to the business object UsedAddress/node Root with a target cardinality of CN. Address can be used for this location. This can be either a referenced address of a master data object, or an address that is integrated via the composition relationship LocationAddress. Which address applies can be determined by looking at the element AddressHostTypeCode. The instance of the TO UsedAddress represents this address. The association is implemented. The referenced address of a master data object is used if the elements AddressBusinessObjectTypeCode, AddressUUID, and AddressHostTypeCode are used to determine the Node ID of the node in the master data object that holds the composition relationship with Dependent Object Address that is represented by TO UsedAddress. The following information is sent to the TO UsedAddress in the implemented address: the fact that it is a master data address, the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object node Location node. In some implementations, this is required if changes are made to the TO UsedAddress. The TO UsedAddress copies the master data address, the changes are applied, and the corresponding DO Address is generated on the business object nodeLocation node via the composition relationship LocationAddress. The address that is integrated via the composition relationship LocationAddress is used if the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object node Location are communicated to the TO UsedAddress. Information as to whether or not it is a referenced address is also included. The TO UsedAddress represents the DO Address that is integrated via the composition relationship on the business object node Location node. An IdentifiedByProductRecipientParty specialization association for navigation may exist to the node LocationAlternativeIdentification with a target cardinality of C.

In some implementations, there can only be one aggregation or composition relationship to the dependent object. If there is an aggregation relationship to the BO Location, the LocationID attribute can be filled with the ID of the BO Location. All other ID fields, such as PartyID, InstalledBaseID, and InstallationPointID, remain blank. If the address of a party is referenced, representative of a BusinessPartners or an OrganisationalCentre, the PartyID attribute can be filled with the ID of the Party. All other ID fields, such as LocationID, InstalledBaseID, and InstallationPointID, remain blank. The reference can be kept in the AddressUUID attribute. If there is an aggregation relationship to the address of an InstalledBase, the InstalledBaseID attribute can be filled with the ID of the InstalledBase. All other ID fields, such as LocationID, PartyID, and InstallationPointID, remain blank. The reference can be kept in the AddressUUID InstalledBaseAddressInformationUUID attribute. If there is an aggregation relationship to the address of an InstallationPoint, the InstallationPointID attribute can be filled with the ID of the InstallationPoint. All other ID fields, such as LocationID, PartyID, and InstalledBaseID, remain blank. The reference can be kept in the AddressUUID attribute. In some implementations, if an address is referenced via the element AddressUUID, the elements AddressBusinessObjectTypeCode and AddressHostTypeCode may also be filled. All locations may exist in all derived business objects if necessary. In some implementations, at least one location is used.

Location Address represents an address of a physical or logical location. Location Alternative Identification is an alternative identification to the identified location in Location node. The elements located at the node Location Alternative Identification can be defined by the datatype ReleaseOrderLocationAlternativeIdentificationElements. These elements include: LocationID, LocationIdentifierTypeCode, IdentifiedByPartyRoleCode, and IdentifiedByPartyRoleCategoryCode. LocationID is an alternative identifier of the location identified in Location. It may be based on datatype GDT: LocationID. LocationIdentifierTypeCode is a coded representation of the type of Location identifier. It may be based on datatype GDT: LocationIdentifierTypeCode. IdentifiedByPartyRoleCode represents a party role code that identifies the location. It may be based on datatype GDT: PartyRoleCode with Qualifier: IdentifiedBy. IdentifiedByPartyRoleCategoryCode represents a party role category code that identifies the location. It may be based on datatype GDT: PartyRoleCategoryCode with Qualifier: IdentifiedBy. The elements of the present node can be used in every derived BO. In some implementations, at least the attribute LocationIdentifierTypeCode, the attribute UsedByPartyRoleCategoryCode, or the attribute UsedByPartyRoleCode has to be filled.

Item represents a quantity of a product included in the release order with additional information on the ordering status, any existing references to preceding business documents, an ID, and information in textual form regarding the order. The elements located at the node Item can be defined by the datatype ReleaseOrderItemElements. These elements include: UUID, ID, TypeCode, ProcessingTypeCode, SourceOfSupplyLogisticRelationshipUUID, SourceOfSupplyLogisticRelationshipBaseObjectNodeReference, BaseBusinessTransactionDocumentItemCancellationRequestedIndicator, CancellationInitiatorCode, FulfilmentBlockedIndicator, OrderingDateTime, FulfilmentBlockStartDateTime, SystemAdministrativeData, Status, Key, and BusinessTransactionDocumentItemID. Status includes OrderingStatusCode, CancellationStatusCode, FulfilmentProcessingStatusCode, FulfilmentStatusCode, ProductAvailabilityConfirmationDateStatusCode, ProductAvailabilityConfirmationQuantityStatusCode, ProductAvailabilityConfirmationStatusCode, ProductAvailabilityConfirmationUpToDatenessStatusCode, and LifeCycleStatusCode elements. Key includes a BusinessTransactionDocumentKey element. BusinessTransactionDocumentKey includes BusinessTransactionDocumentID and BusinessTransactionDocumentTypeCode elements. UUID is a universal unique identifier of Item. It can be used to refer to Item. In some implementations, UUID is used as an alternative key. It may be based on datatype GDT: UUID. ID is an identifier for Item, and can be used to refer to Item. It may be based on datatype GDT: BusinessTransactionDocumentItemID. TypeCode is a coded representation of the type of a release order item. It may be based on datatype GDT: BusinessTransactionDocumentItemTypeCode. ProcessingTypeCode is a coded representation of the processing of an item of a release order. It may be based on datatype GDT: BusinessTransactionDocumentItemProcessingTypeCode. SourceOfSupplyLogisticRelationshipUUID is a unique identifier of the logistic relationship within a source of supply that models the goods movement from the ship-from location to the ship-to location or transportation zone. It may be based on datatype GDT: UUID. SourceOfSupplyLogisticRelationshipBaseObjectNodeReference is a reference to the logistic relationship within a source of supply that represents the item of a purchasing contract. The BaseObjectNodeReference of Source of Supply Logistic Relationship is a reference of the object from which the logistic relationship was replicated. A logistic relationship may be replicated from a material specific transportation lane, from an item of a purchasing contract or a released planning production model. It may be based on datatype GDT: ObjectNodeReference with Qualifier: Base. BaseBusinessTransactionDocumentItemCancellationRequestedIndicator indicates if the base business transaction document requested a cancellation of the item. It may be based on datatype GDT: Indicator with Qualifier: Requested. CancellationInitiatorCode is a coded representation of the initiator of the cancellation of a release order item. Allowed code values include: Requestor, Planner and Seller. It may be based on datatype GDT: CancellationInitiatorCode. FulfilmentBlockedIndicator indicates if the item was blocked. It may be based on datatype GDT: Indicator with Qualifier: Blocked. OrderingDateTime represents the point in time when an item has to be ordered. It may be based on datatype GDT: LOCALNORMALISED_DateTime with Qualifier: Ordering. FulfilmentBlockStartDateTime represents the point in time when the fulfillment of a release order item is blocked. After this time, the fulfillment of an item can be blocked. It may be based on datatype GDT: GLOBAL_DateTime with Qualifier: Start. SystemAdministrativeData represents administrative data that is stored in the system that describes who created the release order item and when. It may be based on datatype GDT: SystemAdministrativeData. Status represents the current status of a release order item. It may be based on datatype BOIDT: ReleaseOrderItemStatus. OrderingStatusCode describes the ordering status of a release order item. It may be based on datatype GDT: OrderingStatusCode. CancellationStatusCode describes the cancellation status of a release order item. It may be based on datatype GDT: CancellationStatusCode. FulfilmentProcessingStatusCode describes the fulfillment processing status of a release order item. It may be based on datatype GDT: NOTSTARTEDINPROCESSFINISHED_ProcessingStatusCode with Qualifier: Fulfilment. FulfilmentStatusCode describes the fulfillment status of a release order item. It may be based on datatype GDT: ReleaseOrderItemFulfilmentStatusCode. ProductAvailabilityConfirmationDateStatusCode describes the product availability confirmation status of a release order item date. It may be based on datatype GDT: AvailabilityConfirmationDateStatusCode with Qualifier: Product. ProductAvailabilityConfirmationQuantityStatusCode describes the product availability confirmation status of a release order item quantity. It may be based on datatype GDT: AvailabilityConfirmationQuantityStatusCode with Qualifier: Product. ProductAvailabilityConfirmationStatusCode describes the product availability confirmation status of a release order item. It may be based on datatype GDT: ProductAvailabilityConfirmationStatusCode. ProductAvailabilityConfirmationUpToDatenessStatusCode describes the product availability up to dateness status of a release order item confirmation. It may be based on datatype GDT: UPTODATEOUTOFDATE_UpToDatenessStatusCode with Qualifier: Confirmation. LifeCycleStatusCode describes the life cycle status of a release order item. It may be based on datatype GDT: ReleaseOrderItemLifeCycleStatusCode. Key is a unique human-readable item key for referencing purposes. It may be based on datatype KDT: BusinessTransactionDocumentItemKey. In some implementations, Key is used as an alternative key. BusinessTransactionDocumentKey represents a key for the BusinessTransactionDocument. It may be based on datatype KDT: BusinessTransactionDocumentKey. BusinessTransactionDocumentID is a unique identifier for a business transaction document. It may be based on datatype GDT: BusinessTransactionDocumentID. BusinessTransactionDocumentTypeCode is a coded representation of the document type that occurs in business transactions. The document type describes the business nature of similar documents and defines the basic features of this type of documents. It may be based on datatype GDT: BusinessTransactionDocumentTypeCode. BusinessTransactionDocumentItemID 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. It may be based on datatype GDT: BusinessTransactionDocumentItemID. The elements of the present node can be used in every derived BO.

A composition relationship to a ItemBusinessTransactionDocumentReference subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemParty subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemLocation subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemProduct subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ItemCurrentItemRequestReference subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ItemRequest subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemCurrentItemConfirmationReference subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ItemConfirmation subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemFulfilment subordinate node can exist with a 1:1 cardinality relationship. A composition relationship to a ItemAttachmentFolder subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ItemTextCollection subordinate node can exist with a 1:C cardinality relationship.

An inbound aggregation relationship may exist from the business object Source of Supply/node Logistic Relationship to SourceOfSupplyLogisticRelationship with a cardinality of C:CN, which may represent a Source of Supply logistic relationship corresponding to the Item. An inbound association relationship may exist from the business object Identity/node Identity to LastChangeIdentity with a cardinality of 1:CN, which may identify the identity that has last changed the Item. An inbound association relationship may exist from the business object Identity/node Identity to CreationIdentity with a cardinality of 1:CN, which may identify the identity that has created the Item.

A ProductRecipientItemParty specialization association for navigation may exist to the node ItemParty with a target cardinality of C. A ShipToItemLocation specialization association for navigation may exist to the node ItemLocation with a target cardinality of C. An ItemCurrentItemRequestReference specialization association for navigation may exist to the node ItemCurrentItemRequestReference with a target cardinality of C. An ItemCurrentItemConfirmationReference specialization association for navigation may exist to the node ItemCurrentItemConfirmationReference with a target cardinality of C. A CurrentItemRequest specialization association for navigation may exist to the node ItemRequest with a target cardinality of C. A CurrentItemConfirmation specialization association for navigation may exist to the node ItemConfirmation with a target cardinality of C. A BusinessDocumentFlow specialization association for navigation may exist to the business object BusinessDocumentFlow/node Root with a target cardinality of 1.

A BaseItemBusinessTransactionDocumentReference specialization association for navigation may exist to the node ItemBusinessTransactionDocumentReference with a target cardinality of C. A SalesOrderItemReference specialization association for navigation may exist to the node ItemBusinessTransactionDocumentReference with a target cardinality of C. A OriginPurchaseOrderItemReference specialization association for navigation may exist to the node ItemBusinessTransactionDocumentReference with a target cardinality of C. A CustomerRequirementItemReference specialization association for navigation may exist to the node ItemBusinessTransactionDocumentReference with a target cardinality of C. A PurchasingContractItemReference specialization association for navigation may exist to the node ItemBusinessTransactionDocumentReference with a target cardinality of C.

Release Order_Template may be associated with the following enterprise service infrastructure actions: Order, Request Cancellation, Revoke Cancellation Request, Cancel, Revoke Cancellation, Discard Cancellation, Request Cancellation And Cancel, Request And Discard Cancellation, Revoke Cancellation Discarded And Cancellation Request, Finish Fulfilment Processing, Resume Fulfilment Processing, Confirm Delivery Request Fulfilment, Check Fulfilment, Check Product Availability Confirmation Up To Dateness, Check Product Availability Confirmation Date, Check Product Availability Confirmation Quantity, Create Item Confirmation With Reference To Current Item Request, and Create Item Request With Reference To Current Item Request.

The Order action orders a release order item. In some implementations, this action is applicable only for release orders items that are not yet ordered. If the status changes, the action sets the “Ordering” status variable to “Ordered.” The Request Cancellation action requests the cancellation of an item. In some implementations, this action is only applicable for those items that are not cancelled. If the object is changed, the action sets CancellationInitiatorCode at the item. If the status changes, the action sets the “Cancellation” status variable to “Cancellation Requested.” The Revoke Cancellation Request action revokes the cancellation request of an item. In some implementations, this action is only applicable for those items that are requested to be cancelled. If the object is changed, the action resets the CancellationInitiatorCode at the item. If the status is changed, the action sets the “Cancellation” status variable to “Not Canceled.” The Cancel action cancels an item. In some implementations, this action is only applicable for those items for which a cancellation has been requested, or has not been cancelled. If the object is changed, the action sets the OpenQuantityCancellationIndicator for the current item confirmation to true. If the status is changed, the action sets the “Cancellation” status variable to “Canceled.” The Revoke Cancellation action revokes the cancellation of an item. In some implementations, this action is only applicable for those items that are cancelled. If the object is changed, the action sets the OpenQuantityCancellationIndicator for the current item confirmation to false. If the status is changed, the action sets the “Cancellation” status variable to “Not Canceled.” The Discard Cancellation action discards a request for cancellation of an item. In some implementations, this action is only applicable for those items that are requested to be cancelled. If the status is changed, the action sets the “Cancellation” status variable to “Canceled Discarded.” The Request Cancellation And Cancel action requests the cancellation and cancels an item. It combines the actions Request Cancellation and Cancel for an item. The Request And Discard Cancellation action requests and discards the cancellation of an item. It combines the actions Request Cancellation and Discard Cancellation for an item. The Revoke Cancellation Discarded And Cancellation Request revokes the discarded cancellation and the cancellation request of an item. It combines the actions Request Cancellation and Revoke Cancellation Request for an item. The Finish Fulfilment Processing action finishes the fulfillment processing when the item is completely fulfilled, and/or no further fulfillment is expected. In some implementations, this action is only applicable for those items that are ordered. If the status is changed, the action sets the “Fulfilment Processing” status variable. The Resume Fulfilment Processing action resumes fulfillment processing after fulfillment processing has already been finished. In some implementations, this action is applicable for only those items where fulfillment processing was finished. If the status is changed, the action sets the “Fulfilment Processing” status variable. The Confirm Delivery Request Fulfilment action confirms the fulfillment of a delivery request. In some implementations, this action is only applicable for those items that are ordered. If the status is changed, the action sets the “Fulfilment Processing” status variable. The Check Fulfilment action checks if the request is fulfilled by the confirmation. In some implementations, this action is only applicable for those items that are ordered. If the status is changed, the action sets the “Fulfilment” status variable. The Check Product Availability Confirmation Up To Dateness action checks if the product availability confirmation refers to the current request. If the status is changed, the action sets the “Product Availability Confirmation Up To Dateness” status variable. The Check Product Availability Confirmation Date action checks if the product availability for the requested quantities is confirmed on time. If the status is changed, the action sets the “Product Availability Confirmation Date” status variable. The Check Product Availability Confirmation Quantity action checks if the product availability for the requested quantities is confirmed completely. If the status is changed, the action sets the “Product Availability Confirmation Quantity” status variable. The Create Item Confirmation With Reference To Current Item Request action creates an item confirmation with reference to the current item request. The Create Item Request With Reference To Current Item Request action creates an item request with reference to the current item request.

Release Order_Template may be associated with a Query By Elements Query. The Query By Elements query returns a list of all release orders items that satisfy the selection criteria. The query elements can be defined by the datatype: ReleaseOrderItemElementsQueryElements. These elements include a SourceOfSupplyLogisticRelationshipID element. SourceOfSupplyLogisticRelationshipID matches the query element SourceOfSupplyLogisticRelationshipID. Items that have a relationship to the Source of Supply Logistic Relationship identified by that ID will be found by the query. It may be based on datatype GDT: SourceOfSupplyLogisticRelationshipID. The query parameters can be used in every derived BO. The actions and queries of the present node can be used in every derived BO.

Item Business Transaction Document Reference is a unique reference to a different business document or the business document item relevant to the release order item. The elements located at the node Item Business Transaction Document Reference can be defined by the datatype ReleaseOrderItemBusinessTransactionDocumentReferenceElements. These elements include BusinessTransactionDocumentReference and BusinessTransactionDocumentRelationshipRoleCode. BusinessTransactionDocumentReference is a unique reference to another business transaction document or business transaction document item. It may be based on datatype GDT: BusinessTransactionDocumentReference. BusinessTransactionDocumentRelationshipRoleCode is a coded representation of the role the referenced document or referenced document item plays in relation to the release order. It may be based on datatype GDT: BusinessTransactionDocumentRelationshipRoleCode. The elements of the present node can be used in every derived BO.

An inbound association relationship may exist from the business object Customer Requirement/node Availability Confirmation Item to CustomerRequirementAvailabilityConfirmationitem with a cardinality of C:C, which may represent the association to the Customer Requirement Availability Confirmation Item in the Procurement Release Order. An inbound association relationship may exist from the business object Purchase Order/node Item to OriginPurchaseOrderItem with a cardinality of C:C, which may represent the association to the item in the origin purchase order, the purchase order item that was posted by the end-buyer. An inbound association relationship may exist from the business object Purchasing Contract/node Item to PurchasingContractItem with a cardinality of C:C, which may represent the association to the Purchasing Contract Item of the Procurement Release Order Item. An inbound association relationship may exist from the business object Sales Order/node Item to SalesOrderItem with a cardinality of C:C, which may represent the association to the item in a sales order item that triggered the creation of the Procurement Release Order.

Item Party represents a natural or legal person, organization, organizational unit, or group that is involved in a release order item processing in a party role. An item party may keep a reference to a business partner or one of its specializations, for example, customer, supplier, or employee. It can also keep a reference to the Company, CostCentre, or ReportingLineUnit specializations of an organizational unit. An item party may exist without reference to a business partner or an organizational unit.

The elements located at the node Item Party can be defined by the datatype ReleaseOrderItemPartyElements. These elements include: PartyKey, PartyUUID, RoleCategoryCode, RoleCode, AddressReference, DeterminationMethodCode, MainIndicator, and Name. PartyKey includes PartyTypeCode and PartyID elements. PartyKey represents a Key of the Party in this PartyRole in the business document or the master data object. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. PartyUUID is a unique identifier for a business partner, the organizational unit, or their specializations. It may be based on datatype GDT: UUID. RoleCategoryCode represents a Party Role Category of the ItemParty in the business document or the master data object. It may be based on datatype GDT: PartyRoleCategoryCode. RoleCode represents a Party Role of the ItemParty in the business document or the master data object. It may be based on datatype GDT: PartyRoleCode. AddressReference represents the information to reference the address of a Party. It may be based on datatype GDT: PartyAddressReference. DeterminationMethodCode is a coded representation of the PartyDeterminationMethod. It may be based on datatype GDT: PartyDeterminationMethodCode. MainIndicator indicates if an ItemParty is emphasized in a group of parties with the same PartyRole. It may be based on datatype GDT: Indicator with Qualifier: Main. Name represents a Name of the ItemParty. It may be based on datatype GDT: LONG_Name. The elements of the present node can be used in every derived BO.

A composition relationship to a ItemPartyContactParty subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemPartyAlternativeIdentification subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemPartyAddress subordinate node can exist with a 1:C cardinality relationship. An inbound aggregation relationship may exist from the business object Party/node Party to Party with a cardinality of C:CN, which may represent the Referenced Party in master data.

A MainContactParty specialization association for navigation may exist to the node ItemPartyContactParty with a target cardinality of C. A UsedAddress specialization association for navigation may exist to the business object UsedAddress/node Root with a target cardinality of CN. The address can be used for the Party. This can be one of the following: a referenced address of the master data object or the PartyAddress integrated via the composition relationship. Which address applies can be determined by looking at the PartyAddressHostTypeCode element. The instance of the TO UsedAddress represents this address. The association is implemented. The referenced address of the master data object is used if the node ID of the node in the master data object is determined via the PartyTypeCode, PartyAddressUUID, and PartyAddressHostTypeCode elements, that have the composition relationship to the DO address that is to be represented by the TO UsedAddress. The TO UsedAddress in the association is provided with the following information: that this is an example of a master data address, and the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object node-Party node. In some implementations, these are required in case changes to the TO UsedAddress take place. The master data address is copied by the TO UsedAddress, the changes take place to the copy, and a corresponding DO Address is created at the business object nodeParty via the PartyAddress composition relationship. The PartyAddress integrated via the composition relationship is used if the TO UsedAddress is informed of the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object node-Party. Additionally, information is provided that this is not an example of a referenced address. In this case, the TO UsedAddress represents the DO address used at the business object node-Party via the PartyAddress composition relationship.

An IdentifiedByProductRecipientParty specialization association for navigation may exist to the node ItemPartyAlternativeIdentification with a target cardinality of C. An IdentifiedByEndBuyerParty specialization association for navigation may exist to the node ItemPartyAlternativeIdentification with a target cardinality of C. An IdentifiedByBuyerParty specialization association for navigation may exist to the node ItemPartyAlternativeIdentification with a target cardinality of C. An IdentifiedBySellerParty specialization association for navigation may exist to the node ItemPartyAlternativeIdentification with a target cardinality of C.

A UsedAddressOverview specialization association for navigation may exist to the business object UsedAddress/node Overview with a target cardinality of CN. This association may be equal to the association to UsedAddress-Root.

In some implementations, there may only be one aggregation relationship to the business partner, the organizational unit, or their specializations. If the PartyUUID exists, the PartyTypeCode may exist as well. Parties may only be referenced via the Transformed Object Party that represents at least one of the following business objects: Company, CostCentre, SalesUnit, ServiceUnit, PurchasingUnit, ReportingLineUnit, Supplier, Customer, Employee, or BusinessPartner. There may only be one association to the address. This address is a master data address of the business partner, organizational unit, or their specializations referenced by PartyUUID. The parties in their various roles can be optionally used in the business objects derived from the delivery_template.

Item Party Contact Party is a natural person or organizational unit that can be contacted for the item party. The contact may be a contact person or, for example, a secretary's office. Usually, communication data for the contact is available. The elements located at the node Item Party Contact Party can be defined by the datatype ReleaseOrderItemPartyContactPartyElements. These elements include: PartyKey, PartyUUID, AddressReference, DeterminationMethodCode, MainIndicator, and Name. PartyKey includes PartyTypeCode and PartyID elements. PartyKey represents a Key of the ItemPartyContactParty in this PartyRole within the ReleaseOrder. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. PartyUUID is a unique identifier of the contact in this PartyRole in the business document or the master data object. It may be based on datatype GDT: UUID. AddressReference represents the information to reference the address of a Party. It may be based on datatype GDT: PartyAddressReference. MainIndicator indicates if a PartyContactParty is emphasized in a group of contact parties with the same PartyRole. It may be based on datatype GDT: Indicator with Qualifier: Main. Name represents a Name of the PartyContactParty. It may be based on datatype GDT: LONG_Name. The elements of the present node can be used in every derived BO.

A composition relationship to subordinate node ItemPartyContactPartyAddress exists in a 1:C cardinality relationship. An inbound aggregation relationship may exist from the business object Party/node Party to Party with a cardinality of C:CN, which may represent the Referenced Party in master data.

A UsedAddress specialization association for navigation may exist to business object UsedAddress/node Root with a target cardinality of CN. Address can be used for Party. This may be the referenced address of a master data object or an address referenced via the composition to PartyAddress. A UsedAddressOverview specialization association for navigation may exist to the business object UsedAddress/node Overview with a target cardinality of CN. This association may be equal to the association to UsedAddress-Root. In some implementations, there may only be one of the associations to the address. This address is a master data address of the business partner, organizational unit, or their specializations referenced by PartyUUID.

Item Party Contact Party Address (Dependent Object Inclusion Node) is a document-specific address of the item contact party. The data can be defined by the dependent object address.

Item Party Alternative Identification is an alternative identification to the identified party in ItemParty node. The elements located at the node Item Party Alternative Identification can be defined by the datatype ReleaseOrderItemPartyAlternativeIdentificationElements. These elements include: PartyID, PartyIdentifierTypeCode, IdentifiedByPartyRoleCode, and IdentifiedByPartyRoleCategoryCode. PartyID represents an ID of the alternative identified party. It may be based on datatype GDT: NOALPHANUMERICCONVERSION_PartyID. PartyIdentifierTypeCode is a coded representation of a type of identifier for a party. It may be based on datatype GDT: PartyIdentifierTypeCode. IdentifiedByPartyRoleCode represents a role code that identifies the party. It may be based on datatype GDT: PartyRoleCode with Qualifier: IdentifiedBy. IdentifiedByPartyRoleCategoryCode represents a role category code that identifies the party. It may be based on datatype GDT: PartyRoleCategoryCode with Qualifier: IdentifiedBy. The elements of the present node can be used in every derived BO.

Item Party Address (Dependent Object Inclusion Node) is a dependent object address containing the document specific address of the item party. The data can be defined by the dependent object address.

Item Location is a physical or logical location that is part of the release order process in a LocationRole. A location may keep a reference to a business object location, keep a reference to an address, keep a reference to a business partner or one of its specializations, for example, customer, supplier, or employee, or keep a reference to a Reporting Line Unit specialization of an organizational unit. The location role describes the role of a location in the release order process.

The elements located at the node Item Location can be defined by the datatype ReleaseOrderItemLocationElements. These elements include: LocationID, LocationUUID, AddressReference, RoleCode, and RoleCategoryCode. AddressReference includes AddressHostUUID, BusinessObj ectTypeCode, AddressHostTypeCode, PartyKey, InstalledBaseID, and InstallationPointID elements. PartyKey includes PartyTypeCode and PartyID elements. LocationID is an identifier of the Location in this LocationRole. It may be based on datatype GDT: LocationID. LocationUUID is a unique identifier for a location, business partner, the organizational unit, or their specializations. It may be based on datatype GDT: UUID. AddressReference represents the information to reference the address of a Business Object. It may be based on datatype BOIDT: ObjectNodeLocationAddressReference. AddressHostUUID is a universally unique identifier for the address of the business partner, the organizational unit or its specializations, the business object InstalledBase, or the business object InstallationPoint. It may be based on datatype GDT: UUID. BusinessObjectTypeCode is a coded representation of the type of the business object, in which the address referenced in the LocationAddressUUID is integrated as a dependent object. It may be based on datatype GDT: BusinessObjectTypeCode. AddressHostTypeCode is a coded representation of the address host type of the address referenced by the AddressUUID or the address included using the Location Address composition. It may be based on datatype GDT: AddressHostTypeCode. PartyKey is an alternative identifier of a party, which represents a business partner or an organizational unit, which references the address using the AddressUUID. It may be based on datatype KDT: PartyKey. PartyTypeCode is a coded representation of a type of party. It may be based on datatype GDT: BusinessObjectTypeCode. PartyID is an identifier for a party. It may be based on datatype GDT: PartyID. InstalledBaseID is an identifier for an installed base that references the address using the AddressUUID. It may be based on datatype GDT: InstalledBaseID. InstallationPointID is an identifier for an installation point that references the address using the AddressUUID. It may be based on datatype GDT: InstallationPointID. RoleCode is a coded representation of the role of the Item Location in the business document or the master data object. It may be based on datatype GDT: LocationRoleCode. RoleCategoryCode represents a Location Role Category of the Location. It may be based on datatype GDT: LocationRoleCategoryCode. The elements of the present node can be used in every derived BO.

A composition relationship to a ItemLocationAddress subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ItemLocationAlternativeIdentification subordinate node can exist with a 1:CN cardinality relationship. An inbound aggregation relationship may exist from the business object Location/node Location to Location with a cardinality of C:CN, which may represent a Location corresponding to the Item Location. An inbound aggregation relationship may exist from the business object Party/node Address Information to PartyAddressInformation with a cardinality of C:CN, which may represent AddressInformation of a representative of a Business Partner or Organizational Centre corresponding to the ItemLocation.

A UsedAddressOverview specialization association for navigation may exist to business object UsedAddress/node Overview with a target cardinality of CN. This association may be equal to the association to UsedAddress-Root. A UsedAddress specialization association for navigation may exist to business object UsedAddress/node Root with a target cardinality of CN. Address can be used for this location. This can be one of the following: a referenced address of a master data object, or the address that is integrated via the composition relationship LocationAddress. Which address applies can be determined by looking at element AddressHostTypeCode. The instance of the TO UsedAddress represents this address. The association is implemented. The referenced address of a master data object is used if the elements AddressBusinessObjectTypeCode, AddressUUID, and AddressHostTypeCode are used to determine the Node ID of the node in the master data object, that holds the composition relationship with DO Address that is to be represented by TO UsedAddress. The following information is sent to the TO UsedAddress in the implemented address: The fact that it is a master data address, and the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of the business object node Location node. In some implementations, this is required if changes are made to the TO UsedAddress. The TO UsedAddress copies the master data address, the changes are applied and the corresponding DO Address is generated on the business object nodeLocation node via the composition relationship LocationAddress. The address that is integrated via the composition relationship LocationAddress is used if the BusinessObjectTypeCode, BusinessObjectNodeTypeCode, and Node ID of then business object node Location are communicated to the TO UsedAddress. Information as to whether or not it is a referenced address is also included. The TO UsedAddress represents the DO Address that is integrated via the composition relationship on the business object node Location node.

An IdentifiedByProductRecipientParty specialization association for navigation may exist to node ItemLocationAlternativeIdentification with a target cardinality of C.

In some implementations, there can be just one aggregation or composition relationship to the dependent object. If there is an aggregation relationship to the BO Location, the LocationID attribute can be filled with the ID of BO Location. All other ID fields, such as PartyID, InstalledBaseID, and InstallationPointID, remain blank. If the address of a party is referenced, representative of a BusinessPartners or an OrganisationalCentre, then the PartyID attribute can be filled with the ID of the Party. All other ID fields, such as LocationID, InstalledBaseID, and InstallationPointID, remain blank. The reference can be kept in the AddressUUID attribute. If there is an aggregation relationship to the address of an InstalledBase, the InstalledBaseID attribute can be filled with the ID of the InstalledBase. All other ID fields, such as LocationID, PartyID, and InstallationPointID, remain blank. The reference can be kept in the AddressUUID InstalledBaseAddressInformationUUID attribute. If there is an aggregation relationship to the address of an InstallationPoint, the InstallationPointID attribute can be filled with the ID of the InstallationPoint. All other ID fields, such as LocationID, PartyID, and InstalledBaseID, remain blank. The reference can be kept in the AddressUUID attribute. In some implementations, if an address is referenced via the element AddressUUID, then elements AddressBusinessObjectTypeCode and AddressHostTypeCode may also be filled. All locations may exist in all derived business objects. In some implementations, at least one location is used.

Item Location Address (Dependent Object Inclusion Node) is an address of a physical or logical location of an item. Item Location Alternative Identification is an alternative identification to the identified location in Item Location node. The elements located at the node Item Location Alternative Identification can be defined by the datatype ReleaseOrderItemLocationAlternativeIdentificationElements. These elements include: LocationID, LocationIdentifierTypeCode, IdentifiedByPartyRoleCode, and IdentifiedByPartyRoleCategoryCode. LocationID is an alternative identifier of the location identified in Item Location. It may be based on datatype GDT: LocationID. LocationIdentifierTypeCode is a coded representation of the type of Item Location identifier. It may be based on datatype GDT: LocationIdentifierTypeCode. IdentifiedByPartyRoleCode represents a party role code that identifies the location. It may be based on datatype GDT: PartyRoleCode with Qualifier: IdentifiedBy. IdentifiedByPartyRoleCategoryCode represents a party role category code that identifies the location. It may be based on datatype GDT: PartyRoleCategoryCode with Qualifier: IdentifiedBy. The elements of the present node can be used in every derived BO. In some implementations, at least the attribute LocationIdentifierTypeCode, the attribute UsedByPartyRoleCategoryCode or the attribute UsedByPartyRoleCode has to be filled.

Item Product is an identifier, description, and classification of the product in the release order item. The elements located at the node Item Product can be defined by the datatype ReleaseOrderItemProductElements. These elements include: ProductKey, ProductUUID, ProductStandardID, ProductBuyerID, ProductSellerID, ProductProductRecipientID, ProductRequirementSpecificationVersionUUID, and ProductRequirementSpecificationKey. ProductKey includes ProductTypeCode, ProductIdentifierTypeCode, and ProductID elements. ProductRequirementSpecificationKey includes RequirementSpecificationID and RequirementSpecificationVersionID elements. ProductKey represents a unique identifier of the product. It may be based on datatype KDT: ProductKey. ProductTypeCode is a coded representation of a product type such as a material or service. It may be based on datatype GDT: ProductTypeCode. ProductIdentifierTypeCode is a coded representation of a product identifier type. It may be based on datatype GDT: ProductIdentifierTypeCode. ProductID is an identifier for a product. It may be based on datatype GDT: ProductID. ProductUUID is a universal unique identifier of the product in the release order item. It may be based on datatype GDT: UUID. ProductStandardID is a unique identifier of a product whereby the identification sheet used is managed by an agency. It may be based on datatype GDT: ProductStandardID. ProductBuyerID is an identifier of the product assigned by the buyer. It may be based on datatype GDT: ProductPartyID. ProductSellerID is an identifier of the product assigned by the seller. It may be based on datatype GDT: ProductPartyID. ProductProductRecipientID is an identifier of the product assigned by the product recipient. It may be based on datatype GDT: ProductPartyID. ProductRequirementSpecificationVersionUUID is a universally unique identifier of the product requirement specification for the material that will be produced. It may be based on datatype GDT: UUID. ProductRequirementSpecificationKey is a unique identifier of the product requirement specification for the material that will be produced. It may be based on datatype KDT: RequirementSpecificationKey. RequirementSpecificationID is an identifier for a requirement specification that is unique within one system. It may be based on datatype GDT: RequirementSpecificationID. RequirementSpecificationVersionID is an identifier for the version of a requirement specification. It may be based on datatype GDT: VersionID. The elements of the present node can be used in every derived BO.

An inbound aggregation relationship may exist from the business object Material/node Material to Material with a cardinality of C:C. The ItemProduct may represent the Product specialization Material if an item includes a material. An inbound aggregation relationship may exist from the business object Product Requirement Specification/node Product Requirement Specification to ProductRequirementSpecification with a cardinality of C:CN, which may denote the product requirement specification that specifies the product to be produced in detail. A MaterialOverview specialization association for navigation may exist to business object Material/node Overview with a target cardinality of CN.

Item Current Item Request Reference is a unique reference to the current item request. The elements located at the node Item Current Item Request Reference can be defined by the datatype ReleaseOrderItemCurrentItemRequestReferenceElements. These elements include an ItemRequestUUID element. ItemRequestUUID is a universal unique identifier of the current item request. It may be based on datatype GDT: UUID. The elements of the present node can be used in every derived BO. A CurrentItemRequest specialization association for navigation may exist to node ItemRequest with a target cardinality of C.

Item Request is a request to order a product. In some implementations, Item Request is Time dependent based on Time Point. The elements located at the node Item Request can be defined by the datatype ReleaseOrderItemRequestElements. These elements include: UUID, ID, PredecessorItemRequestID, PredecessorItemRequestUUID, CumulatedRequestedQuantity, CumulatedRequestedQuantityTypeCode, Status, and SystemAdministrativeData. Status includes a ProcurementReleaseOrderRequestIssuingStatusCode element. UUID is a universally unique identifier of Item Request. In some implementations, UUID is used as an alternative key. It may be based on datatype GDT: UUID. ID represents an identification for Item Request. It may be based on datatype GDT: ReleaseOrderItemRequestID. PredecessorItemRequestID is an identifier of the predecessor item request. It may be based on datatype GDT: BusinessTransactionDocumentID. PredecessorItemRequestUUID is a unique identifier of the predecessor item request. It may be based on datatype GDT: UUID. CumulatedRequestedQuantity represents the cumulated requested quantity with the corresponding unit of measure. It may be based on datatype GDT: Quantity with Qualifier: Requested. CumulatedRequestedQuantityTypeCode is a coded representation of the type of the cumulated requested quantity value. It may be based on datatype GDT: QuantityTypeCode with Qualifier: Requested. Status represents the current status of a release order item request. It may be based on datatype BOIDT: ReleaseOrderItemRequestStatus. ProcurementReleaseOrderRequestIssuingStatusCode describes the issuing status of a procurement release order request. In some implementations, allowed code values are Not Issued and Issued. It may be based on datatype GDT: IssuingStatusCode with Qualifier: ProcurementReleaseOrderRequest. SystemAdministrativeData represents administrative data stored in the system that describes who created the release order item request, and when it was created. It may be based on datatype GDT: SystemAdministrativeData. The elements of the present node can be used in every derived BO.

A composition relationship to a ItemRequestScheduleLine subordinate node can exist with a 1:C cardinality relationship. An inbound association relationship may exist from the business object Identity/node Identity to LastChangeIdentity with a cardinality of 1:CN, which may identify the identity that has last changed the Item Request. An inbound association relationship may exist from the business object Identity/node Identity to CreationIdentity with a cardinality of 1:CN, which may identify the identity that has created the Item Request. An inbound association relationship may exist from the business object Release Order_Template/node Item Request to PredecessorItemRequest with a cardinality of C:C, which may represent the association from the predecessor item request.

A PlannedItemRequestScheduleLine specialization association for navigation may exist to node ItemRequestScheduleLine with a target cardinality of CN. The association may filter all schedule lines of type Planned. A RequestedItemRequestScheduleLine specialization association for navigation may exist to node ItemRequestScheduleLine with a target cardinality of CN. The association may filter all schedule lines of type Requested.

Release Order_Template may be associated with a Notify Of Procurement Release Order Request Issue enterprise service infrastructure action. The action notifies the procurement release order item request that a procurement release order request message was sent. The action also determines the ProcurementReleaseOrderRequestIssuingStatus of the procurement release order item request. In some implementations, this action is only applicable for procurement release orders items that are not yet issued. If the object is changed, only the status variable is set. If the status is changed, the action can set the “ProcurementReleaseOrderRequestIssuingStatusCode” status variable to “Issued.” The action may not be triggered by a user. It may be executed by a compound service or a core service of the same or a different business object. The actions and queries of the present node can be used in every derived BO.

Item Request Schedule Line is a schedule line included in the item request covering a partial quantity of the product specified in the item and specifying the delivery date. In some implementations, Item Request Schedule Line is Time dependent based on Schedule Line Date.

The elements located at the node Item Request Schedule Line can be defined by the datatype ReleaseOrderItemRequestScheduleLineElements. These elements include: UUID, ID, TypeCode, RequestedArrivaIDateTimePeriod, RequestedQuantity, and RequestedQuantityTypeCode. UUID is a universally unique identifier of the schedule line in a ReleaseOrderItemRequest. In some implementations, UUID is used as an alternative key. It may be based on datatype GDT: UUID. ID is a unique identifier of the schedule line in a ReleaseOrderItemRequest. It may be based on datatype GDT: ReleaseOrderItemRequestScheduleLineID. TypeCode is a coded representation of the type of schedule line of the requested quantity. It may be based on datatype GDT: BusinessTransactionDocumentItemScheduleLineTypeCode. RequestedArrivalDateTimePeriod represents the time period within which the goods are requested to arrive at the receiver. GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Arrival. RequestedQuantity represents the requested quantity. It may be based on datatype GDT: Quantity with Qualifier: Requested. RequestedQuantityTypeCode is a coded representation of the type of the requested quantity. It may be based on datatype GDT: QuantityTypeCode with Qualifier: Requested. The elements of the present node can be used in every derived BO.

Item Current Item Confirmation Reference is a unique reference to the current item confirmation. The elements located at the node Item Current Item Confirmation Reference can be defined by the datatype ReleaseOrderItemCurrentItemConfirmationReferenceElements. These elements include an ItemConfirmationUUID element. ItemConfirmationUUID is a universally unique identifier of the current item confirmation. It may be based on datatype GDT: UUID. The elements of the present node can be used in every derived BO. A CurrentItemConfirmation specialization association for navigation may exist to node ItemConfirmation with a target cardinality of C.

Item Confirmation is a confirmation to deliver an ordered product. In some implementations, Item Confirmation is Time dependent based on Time Point. The elements located at the node Item Confirmation can be defined by the datatype: ReleaseOrderItemConfirmationElements. These elements include: UUID, ID, ItemRequestID, ItemRequestUUID, ConfirmedDateTime, CumulatedConfirmedQuantity, CumulatedConfirmedQuantityTypeCode, OpenQuantityCancelledIndicator, and SystemAdministrativeData. UUID is a universally unique identifier of Item Confirmation. In some implementations, UUID is used as an alternative key. It may be based on datatype GDT: UUID. ID is an identification for Item Confirmation. It may be based on datatype GDT: ReleaseOrderItemConfirmationID. ItemRequestID is an identifier of the item request, which is confirmed by the item confirmation. It may be based on datatype GDT: BusinessTransactionDocumentID. ItemRequestUUID is a universally unique identifier of the item request, which is confirmed by the item confirmation. It may be based on datatype GDT: UUID. ConfirmedDateTime represents a point in time when the release order item was confirmed. It may be based on datatype GDT: LOCALNORMALISED_DateTime with Qualifier: Confirmed. CumulatedConfirmedQuantity represents the cumulated confirmed quantity with the corresponding unit of measure. It may be based on datatype GDT: Quantity with Qualifier: Confirmed. CumulatedConfirmedQuantityTypeCode is a coded representation of the type of the cumulated confirmed quantity value. It may be based on datatype GDT: QuantityTypeCode with Qualifier: Confirmed. OpenQuantityCancelledIndicator indicates the cancellation of the open quantity. It may be based on datatype GDT: Indicator with Qualifier: Cancelled. SystemAdministrativeData represents administrative data stored in the system that describes who created the release order item confirmation, and when it was created. It may be based on datatype GDT: SystemAdministrativeData. The elements of the present node can be used in every derived BO.

A composition relationship to a ItemConfirmationScheduleLine subordinate node can exist with a 1:CN cardinality relationship. A composition relationship to a ItemConfirmationAttachmentFolder subordinate node can exist with a 1:C cardinality relationship. A composition relationship to a ItemConfirmationTextCollection subordinate node can exist with a 1:C cardinality relationship. An inbound aggregation relationship may exist from the business object Release Order_Template/node Item Request to Item Request with a cardinality of C:CN, which may represent an Item request, which is confirmed by the item confirmation. An inbound association relationship may exist from the business object Identity/node Identity to CreationIdentity with a cardinality of 1:CN, which may identify the identity that has created the Item Confirmation. An inbound association relationship may exist from the business object Identity/node Identity to LastChangeIdentity with a cardinality of 1:CN, which may identify the identity that has last changed the Item Confirmation.

A PlannedItemConfirmationScheduleLine specialization association for navigation may exist to node ItemConfirmationScheduleLine with a target cardinality of CN. The association may filter all schedule lines of type Planned. A ConfirmedItemConfirmationScheduleLine specialization association for navigation may exist to node ItemConfirmationScheduleLine with a target cardinality of CN. The association may filter all schedule lines of type Confirmed.

Item Confirmation Schedule Line is a schedule line included in the item confirmation covering a partial quantity of the product specified in the item and specifying the delivery date. In some implementations, Item Confirmation Schedule Line is Time dependent based on Schedule Line Date. The elements located at the node Item Confirmation Schedule Line can be defined by the datatype ReleaseOrderItemConfirmationScheduleLineElements. These elements include: UUID, ID, TypeCode, ArrivalDateTimePeriod, ShippingDateTimePeriod, ConfirmedQuantity, and ConfirmedQuantityTypeCode. UUID is a universally unique identifier of the schedule line in a ReleaseOrderItemConfirmation. In some implementations, UUID is used as an alternative key. It may be based on datatype GDT: UUID. ID is a unique identifier of the schedule line in a ReleaseOrderItemConfirmation. It may be based on datatype GDT: ReleaseOrderItemConfirmationScheduleLineID. TypeCode is a coded representation of the type of the confirmed quantity. It may be based on datatype GDT: BusinessTransactionDocumentItemScheduleLineTypeCode. ArrivalDateTimePeriod represents the time period within which the goods will arrive at the receiver. It may be based on datatype GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Arrival. ShippingDateTimePeriod represents the time period within which the goods are shipped to the receiver. It may be based on datatype GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Shipping. ConfirmedQuantity represents the confirmed quantity. It may be based on datatype GDT: Quantity with Qualifier: Confirmed. ConfirmedQuantityTypeCode is a coded representation of the type of the confirmed quantity. It may be based on datatype GDT: QuantityTypeCode with Qualifier: Confirmed. The elements of the present node can be used in every derived BO.

Item Confirmation Attachment Folder (Dependent Object Inclusion Node) is a folder including one or more documents in electronic form including additional information about an item confirmation. Item Confirmation Text Collection (Dependent Object Inclusion Node) is a natural language text linked to the release order item confirmation that supports release order processing.

Item Fulfilment represents the fulfillment of an item relevant to the release order. In some implementations, Item Fulfilment is Time dependent based on Time Point. The elements located at the node Item Fulfilment can be defined by the datatype ReleaseOrderItemFulfilmentElements. These elements include: CumulatedOutboundDeliveryQuantity, CumulatedOutboundDeliveryQuantityTypeCode, CompletedIndicator, and SystemAdministrativeData. CumulatedOutboundDeliveryQuantity represents the cumulated delivered quantity. It may be based on datatype GDT: Quantity with Qualifier: Delivery. CumulatedOutboundDeliveryQuantityTypeCode is a coded representation of the type of the cumulated delivered quantity. It may be based on datatype GDT: QuantityTypeCode with Qualifier: Delivery. CompletedIndicator indicates the completion of a release order item for which no more deliveries are expected. It may be based on datatype GDT: Indicator with Qualifier: Completed. SystemAdministrativeData is administrative data recorded by the system. This data includes system users and change times. It may be based on datatype GDT: SystemAdministrativeData. The elements of the present node can be used in every derived BO.

A composition relationship to a ItemFulfilmentActualValue subordinate node can exist with a 1:CN cardinality relationship. An inbound association relationship may exist from the business object Identity/node Identity to LastChangeIdentity with a cardinality of 1:CN, which may identify the identity that has last changed the release order item fulfillment. An inbound association relationship may exist from the business object Identity/node Identity to CreationIdentity with a cardinality of 1:CN, which may identify the identity that has created the release order item fulfillment.

Item Fulfilment Actual Value is a value that represents actual order fulfillment in terms of quantity and dates for an item business transaction document reference. The elements located at the node Item Fulfilment Actual Value can be defined by the datatype ReleaseOrderItemFulfilmentActualValueElements. These elements include: BusinessTransactionDocumentReference, BusinessTransactionDocumentRelationshipRoleCode, ShippingDateTimePeriod, ArrivalDateTimePeriod, FulfilledQuantity, and FulfilledQuantityTypeCode. BusinessTransactionDocumentReference is a unique reference to another business transaction document or business transaction document item. It may be based on datatype GDT: BusinessTransactionDocumentReference. BusinessTransactionDocumentRelationshipRoleCode is a coded representation of the role the referenced document or referenced document item plays in relation to the release order. It may be based on datatype GDT: BusinessTransactionDocumentRelationshipRoleCode. ShippingDateTimePeriod represents the time period within which the goods were shipped to the receiver. It may be based on datatype GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Shipping. ArrivalDateTimePeriod represents the time period within which the goods will arrive at the receiver. It may be based on datatype GDT: UPPEROPEN_LOCALNORMALISED_DateTimePeriod with Qualifier: Arrival. FulfilledQuantity represents the fulfilled quantity with the corresponding unit of measure. It may be based on datatype GDT: Quantity with Qualifier: Fulfilled. FulfilledQuantityTypeCode is a coded representation of the type of the fulfilled quantity value. It may be based on datatype GDT: QuantityTypeCode with Qualifier: Fulfilled. The elements of the present node can be used in every derived BO.

An inbound association relationship may exist from the business object Outbound Delivery/node Item to Item with a cardinality of C:C, which may represent the item in an outbound delivery.

Item Attachment Folder (Dependent Object Inclusion Node) is a folder for one or more documents in electronic form including information about a release order item. Item Text Collection (Dependent Object Inclusion Node) is a collection of natural-language texts with additional information about a release order item. Attachment Folder (Dependent Object Inclusion Node) is a folder for one or more documents in electronic form including information about a release order. Text Collection (Dependent Object Inclusion Node) is a collection of natural-language texts with additional information about a release order. Controlled Output Request (Dependent Object Inclusion Node) is a controller of output requests and output history entries.

Some or all of the nodes of the business object Template Release Order_Template may be used in a derived business object (e.g., in Procurement Release Order). Business Object Procurement Release Order is a procurement request to release a specified quantity of material for delivery within a specified time. The business object Procurement Release Order belongs to the process component External Procurement Trigger and Response. This request only includes information about the material flow. If the material flow represents a sales process, the financial conditions can be specified by referring to an outline agreement. Procurement Release Order is used within Third-Party Direct Ship by a buyer to request that a seller delivers a specified quantity of material within a specified time. It is also used during Intra Company Stock Transfer as a means to control the shipment of goods from one location to another within a company. The Procurement Release Order includes the following main parts, the Root, and the Item. The Root includes information on parties, locations, and status with information on the ordered goods or the goods to be delivered. The Item includes information on the product to be delivered and its quantities, as well as on parties and status.

FIGS. 45-1 through 45-4 depict an example Form Procurement Release Order Request Message Data Type 45000, which comprises elements 45002-45044, hierarchically related as shown. For example, the Form Procurement Release Order Request Message 45002 includes a Procurement Release Order 45004.

The message type Form Procurement Release Order Request is derived from the business object Procurement Release Order leading object together with its operation signature. Form Procurement Release Order Request is a message type to enable form-based output for a procurement release order request. The structure of this message type can be determined by the message data type FormProcurementReleaseOrderRequestMessage. The FormProcurementReleaseOrderRequestMessage message data type includes the object ProcurementReleaseOrder which is included in the business document, and the business information that is relevant for sending a business document in a message. It also includes the MessageHeader and ProcurementReleaseOrder packages. The FormProcurementReleaseOrderRequestMessage message data type can provide the structure for the Form Procurement Release Order Request message type and the operations that are based on it.

The MessageHeader package is a grouping of business information that is relevant for sending a business document in a message. It includes a MessageHeader node. MessageHeader is a grouping of business information from the perspective of the sending application. It includes information to identify the business document in a message, information about the sender, and optionally, information about the recipient. The MessageID can be set by the sending application. With the ReferencedMessageID, reference is made in the current BusinessDocument to a previous BusinessDocument.

The SenderParty can be specified by the sending application. It can name a contact person for any problems that arise with the message. This can be useful when there is an additional infrastructure, such as a marketplace, between the sender and the recipient. The SenderParty plays an auxiliary role during message transfer, and can be ignored by the recipient application. It can be filled by the sender if the PurchaseOrder package cannot be used to transfer the participating parties.

The RecipientParty can be specified by the sending application. It can name a recipient contact person for any problems that arise with the message. This can be useful when there is an additional infrastructure, such as a marketplace, between the sender and the recipient. The RecipientParty plays an auxiliary role during message transfer, and can be ignored by the recipient application. It can be filled by the sender if the PurchaseOrder package cannot be used to transfer the participating parties.

The MessageHeader includes SenderParty and RecipientParty elements. It can be of the type GDT:BusinessDocumentMessageHeader. The elements of the GDT used include: RecipientParty, BusinessScope, SenderParty, SenderBusinessSystemID, TestDataIndicator, RecipientBusinessSystemID, ReferenceID, ReferenceUUID, ReconciliationIndicator, ID, UUID, and CreationDateTime. SenderParty is a partner responsible for sending a business document at a business application level. The SenderParty may be based on datatype GDT:BusinessDocumentMessageHeaderParty. RecipientParty is a partner responsible for receiving a business document at a business application level. The RecipientParty may be based on datatype GDT:BusinessDocumentMessageHeaderParty.

The ProcurementReleaseOrder package is the grouping of ProcurementReleaseOrder with its packages. The packages include BusinessTransactionDocumentReference, Party, AttachmentFolder, TextCollection, and Item. It also includes a ProcurementReleaseOrder entity. ProcurementReleaseOrder is used by a customer to notify a supplier about the quantity of a material from a purchasing contract item that is to be delivered and at what time. ProcurementReleaseOrder includes ActionCode and ReconciliationPeriodCounterValue attributes. ActionCode is a coded representation of an instruction to the message recipient how to process the ProcurementReleaseOrderRequest message. It may be based on datatype GDT:ActionCode. ReconciliationPeriodCounterValue is a sequence number that identifies the reconciliation period this message refers to. For AP (Accounts Payable) internal communication, the ReconciliationPeriodCounterValue may be used. It may be based on datatype GDT: CounterValue.

ProcurementReleaseOrder includes the non-node elements: WatermarkName, ID, CreationDateTime, OrderedDateTime, LastChangeDateTime, and ItemListCompleteTransmissionIndicator. WatermarkName represents the name of the watermark. The watermark can be used to mark a form in a preview as a copy. It may be based on datatype CDT:LANGUAGEINDEPENDENT_MEDIUM_Name. ID is a unique identifier for the ProcurementReleaseOrder. It may be based on datatype GDT:BusinessTransactionDocumentID. CreationDateTime represents the creation time of the procurement release order. It may be based on datatype CDT:LOCALNORMALISED_DateTime. OrderedDateTime represents the first time a procurement release order was sent to the supplier. It may be based on datatype CDT:LOCALNORMALISED_DateTime. LastChangeDateTime represents the last change time of the procurement release order. It may be based on datatype CDT:LOCALNORMALISED_DateTime. ItemListCompleteTransmissionIndicator indicates if all items are transmitted in the message. It may be based on datatype CDT:Indicator.

ProcurementReleaseOrder includes a node element SalesOrderReference in a 1:C cardinality relationship, a node element OriginPurchaseOrderReference in a 1:C cardinality relationship, a node element BuyerParty in a 1:C cardinality relationship, a node element SellerParty in a 1:1 cardinality relationship, a node element LogisticsRequestResponsibleParty in a 1:C cardinality relationship, a node element FreightForwarderParty in a 1:C cardinality relationship, a node element AttachmentFolder in a 1:C cardinality relationship, a node element TextCollection in a 1:C cardinality relationship, a node element Item in a 1:CN cardinality relationship.

The ProcurementReleaseOrderBusinessTransactionDocumentReference package includes SalesOrderReference and OriginPurchaseOrderReference entities. The SalesOrderReference is a reference to the sales order which initiated the creation of the procurement release order. SalesOrderReference can be typed by BusinessTransactionDocumentReference. In some implementations, the reference is used in a third party direct ship scenario. The OriginPurchaseOrderReference is a reference to the customer's purchase order which initiated the sales order in a third party direct ship scenario. OriginPurchaseOrderReference can be typed by BusinessTransactionDocumentReference.

The ProcurementReleaseOrderParty package includes BuyerParty, SellerParty, LogisticsRequestResponsibleParty, and FreightForwarderParty entities. BuyerParty is a party that buys goods or services. BuyerParty includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, PaymentTransactionInitiatorID, PaymentTransactionDestinatedID, TaxID, TypeCode, FormattedName, and FormAddress. InternalID may be based on datatype GDT:PartyInternalID. StandardID may be based on datatype GDT:PartyStandardID. BuyerID may be based on datatype GDT:PartyPartyID. SellerID may be based on datatype GDT:PartyPartyID. ProductRecipientID may be based on datatype GDT:PartyPartyID. VendorID may be based on datatype GDT:PartyPartyID. BillToID may be based on datatype GDT:PartyPartyID. BillFromID may be based on datatype GDT:PartyPartyID. BidderID may be based on datatype GDT:PartyPartyID. PaymentTransactionInitiatorID may be based on datatype GDT:PartyPartyID. PaymentTransactionDestinatedID may be based on datatype GDT:PartyPartyID. TaxID may be based on datatype GDT:PartyTaxID. TypeCode may be based on datatype GDT:BusinessObjectTypeCode. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. FormAddress may be based on datatype GDT:FormAddress. BuyerParty includes a node element ContactPerson in a 1:C cardinality relationship.

For intra-enterprise communication, use the InternalID for all party entities. For inter-enterprise communication, use the StandardID or the partner-role-specific ID of the receiving partner for all party entities. Use the BuyerID for Supplier Collaboration scenarios, and use the SellerID for Customer Collaboration scenarios. Due to the different possibilities for ID use, all ID elements of the particular party are optional. The address of the BuyerParty is not intended to be used as the delivery address. The ShipToLocation is provided for this purpose.

ContactPerson includes the non-node elements: InternalID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, FormAddress, and FormattedName. InternalID is a proprietary identifier that can be used when both sender and recipient access shared master data. It may be based on datatype GDT:ContactPersonInternalID with Qualifier:Internal. BuyerID may be based on datatype GDT:ContactPersonPartyID. SellerID is a proprietary identifier that is used by the SellerParty for this location. It may be based on datatype GDT: ContactPersonPartyID with Qualifier:Seller. ProductRecipientID is a proprietary identifier that is used by the ProductRecipientParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Product Recipient. VendorID may be based on datatype GDT:ContactPersonPartyID. BillToID may be based on datatype GDT:ContactPersonPartyID. BillFromID may be based on datatype GDT: ContactPersonPartyID. BidderID may be based on datatype GDT: ContactPersonPartyID. FormAddress may be based on datatype GDT:FormAddress. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name.

The SellerParty is a company or person who sells the goods described in the ProcurementReleaseOrder. SellerParty includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, PaymentTransactionInitiatorID, PaymentTransactionDestinatedID, TaxID, TypeCode, FormattedName, and FormAddress. InternalID may be based on datatype GDT:PartyInternalID. StandardID may be based on datatype GDT:PartyStandardID. BuyerID may be based on datatype GDT:PartyPartyID. SellerID may be based on datatype GDT:PartyPartyID. ProductRecipientID may be based on datatype GDT:PartyPartyID. VendorID may be based on datatype GDT:PartyPartyID. BillToID may be based on datatype GDT:PartyPartyID. BillFromID may be based on datatype GDT:PartyPartyID. BidderID may be based on datatype GDT:PartyPartyID. PaymentTransactionInitiatorID may be based on datatype GDT:PartyPartyID. PaymentTransactionDestinatedID may be based on datatype GDT:PartyPartyID. TaxID may be based on datatype GDT:PartyTaxID. TypeCode may be based on datatype GDT:BusinessObjectTypeCode. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. FormAddress may be based on datatype GDT:FormAddress. SellerParty includes a node element ContactPerson in a 1:C cardinality relationship.

ContactPerson includes the non-node elements: InternalID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, FormAddress, and FormattedName. InternalID represents a proprietary identifier that is used when both sender and recipient access shared master data. It may be based on datatype GDT:ContactPersonInternalID with Qualifier:Internal. BuyerID may be based on datatype GDT:ContactPersonPartyID. SellerID represents a proprietary identifier that is used by the SellerParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Seller. ProductRecipientID represents a proprietary identifier that is used by the ProductRecipientParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Product Recipient. VendorID may be based on datatype GDT:ContactPersonPartyID. BillToID may be based on datatype GDT:ContactPersonPartyID. BillFromID may be based on datatype GDT:ContactPersonPartyID. BidderID may be based on datatype GDT:ContactPersonPartyID. FormAddress may be based on datatype GDT:FormAddress. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name.

LogisticsRequestResponsibleParty is a company or person responsible for logistics requests. LogisticsRequestResponsibleParty includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, PaymentTransactionInitiatorID, PaymentTransactionDestinatedID, TaxID, TypeCode, FormattedName, and FormAddress. InternalID may be based on datatype GDT:PartyInternalID. StandardID may be based on datatype GDT:PartyStandardID. BuyerID may be based on datatype GDT:PartyPartyID). SellerID may be based on datatype GDT:PartyPartyID. ProductRecipientID may be based on datatype GDT:PartyPartyID. VendorID may be based on datatype GDT:PartyPartyID. BillToID may be based on datatype GDT:PartyPartyID. BillFromID may be based on datatype GDT:PartyPartyID. BidderID may be based on datatype GDT:PartyPartyID. PaymentTransactionInitiatorID may be based on datatype GDT:PartyPartyID. PaymentTransactionDestinatedID may be based on datatype GDT:PartyPartyID. TaxID may be based on datatype GDT:PartyTaxID. TypeCode may be based on datatype GDT:BusinessObjectTypeCode. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. FormAddress may be based on datatype GDT:FormAddress. LogisticsRequestResponsibleParty includes a node element ContactPerson in a 1:C cardinality relationship.

ContactPerson includes the non-node elements: InternalID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, FormAddress, and FormattedName. InternalID is a proprietary identifier that is used when both sender and recipient can access shared master data. It may be based on datatype GDT:ContactPersonInternalID with Qualifier:Internal. BuyerID may be based on datatype GDT:ContactPersonPartyID. SellerID is a proprietary identifier that is used by the SellerParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Seller. ProductRecipientID is a proprietary identifier that is used by the ProductRecipientParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Product Recipient. VendorID may be based on datatype GDT:ContactPersonPartyID. BillToID may be based on datatype GDT:ContactPersonPartyID. BillFromID may be based on datatype GDT: ContactPersonPartyID. BidderID may be based on datatype GDT: ContactPersonPartyID. FormAddress may be based on datatype GDT:FormAddress. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name.

FreightForwarderParty is a company or person responsible for organizing the shipment. FreightForwarderParty includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, PaymentTransactionInitiatorID, PaymentTransactionDestinatedID, TaxID, TypeCode, FormattedName, and FormAddress. InternalID may be based on datatype GDT:PartyInternalID. StandardID may be based on datatype GDT:PartyStandardID. BuyerID may be based on datatype GDT:PartyPartyID. SellerID may be based on datatype GDT:PartyPartyID. ProductRecipientID may be based on datatype GDT:PartyPartyID. VendorID may be based on datatype GDT:PartyPartyID. BillToID may be based on datatype GDT:PartyPartyID. BillFromID may be based on datatype GDT:PartyPartyID. BidderID may be based on datatype GDT:PartyPartyID. PaymentTransactionInitiatorID may be based on datatype GDT:PartyPartyID. PaymentTransactionDestinatedID may be based on datatype GDT:PartyPartyID. TaxID may be based on datatype GDT:PartyTaxID. TypeCode may be based on datatype GDT:BusinessObjectTypeCode. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. FormAddress may be based on datatype GDT:FormAddress. FreightForwarderParty includes a node element ContactPerson in a 1:C cardinality relationship.

ContactPerson includes the non-node elements: InternalID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, FormAddress, and FormattedName. InternalID is a proprietary identifier that is used when both sender and recipient can access shared master data. It may be based on datatype GDT:ContactPersonInternalID with Qualifier:Internal. BuyerID may be based on datatype GDT:ContactPersonPartyID. SellerID is a proprietary identifier that is used by the SellerParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Seller. ProductRecipientID is a proprietary identifier that is used by the ProductRecipientParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Product Recipient. VendorID may be based on datatype GDT:ContactPersonPartyID. BillToID may be based on datatype GDT:ContactPersonPartyID. BillFromID may be based on datatype GDT: ContactPersonPartyID. BidderID may be based on datatype GDT: ContactPersonPartyID. FormAddress may be based on datatype GDT:FormAddress. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name.

The ProcurementReleaseOrderAttachmentFolder package includes the AttachmentFolder entity. AttachmentFolder can be typed by AttachmentFolder. The ProcurementReleaseOrderTextCollection package includes the TextCollection entity. TextCollection includes the Text non-node element. Text includes the TypeCode, TypeName, and SystemAdministrativeData elements. Text may be based on datatype FMIDT:FormTextCollectionText. TypeCode may be based on datatype GDT:TextCollectionTextTypeCode. TypeName may be based on datatype CDT:LANGUAGEINDEPENDENT_MEDIUM_Name. SystemAdministrativeData may be based on datatype FMIDT:FormSystemAdministrativeData.

The ProcurementReleaseOrderItem package includes an Item entity. ProcurementReleaseOrderItem is a statement regarding the requirement for a specific product at a ship-to location with reference to a purchasing contract item. Item includes an ActionCode attribute. ActionCode is a coded representation of an instruction to the message recipient as to how they should process the message item. It may be based on datatype GDT:ActionCode.

Item includes the non-node elements: ID, TypeCode, and CancellationDocumentIndicator. ID is a sequential number for the item in the ProcurementReleaseOrder document. It may be based on datatype GDT:BusinessTransactionDocumentItemID. TypeCode is a coded representation of the item's type. It may be based on datatype GDT:BusinessTransactionDocumentItemTypeCode. CancellationDocumentIndicator indicates whether this message cancels previous requests of the ProcurementReleaseOrderItem. It may be based on datatype CDT:Indicator.

Item includes a node element PurchasingContractReference in a 1:1 cardinality relationship, a node element SalesOrderReference in a 1:1 cardinality relationship, a node element OriginPurchaseOrderReference in a 1:1 cardinality relationship, a node element ProductRecipientParty in a 1:C cardinality relationship, a node element ShipToLocation in a 1:C cardinality relationship, a node element Production a 1:1 cardinality relationship, a node element ProductRequirementSpecification in a 1:C cardinality relationship, a node element TextCollection in a 1:C cardinality relationship, a node element AttachmentFolder in a 1:C cardinality relationship, and a node element Request in a 1:1 cardinality relationship.

The ProcurementReleaseOrderItemBusinessTransactionDocumentReference package includes PurchasingContractReference, SalesOrderReference, and OriginPurchaseOrderReference entities. PurchasingContractReference is a reference to an item in a purchasing contract. PurchasingContractReference can be typed by BusinessTransactionDocumentReference. In some instances, the reference may always includes the ItemID (purchasing contract item). SalesOrderReference is a reference to the sales order which initiated the creation of the procurement release order. SalesOrderReference can be typed by BusinessTransactionDocumentReference. In some instances, the reference may always include the ItemID (sales order item). OriginPurchaseOrderReference is a reference to the customer's purchase order which initiated the sales order in a third party direct ship scenario. OriginPurchaseOrderReference can be typed by BusinessTransactionDocumentReference. In some instances, the reference may always include the ItemID (purchasing contract item).

The ProcurementReleaseOrderItemParty package includes a ProductRecipientParty entity. The ProductRecipientParty is the company or person that receives the goods delivery. ProductRecipientParty includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, PaymentTransactionInitiatorID, PaymentTransactionDestinatedID, TaxID, TypeCode, FormattedName, and FormAddress. InternalID may be based on datatype GDT:PartyInternalID. StandardID may be based on datatype GDT:PartyStandardID. BuyerID may be based on datatype GDT:PartyPartyID. SellerID may be based on datatype GDT:PartyPartyID. ProductRecipientID may be based on datatype GDT:PartyPartyID. VendorID may be based on datatype GDT:PartyPartyID. BillToID may be based on datatype GDT:PartyPartyID. BillFromID may be based on datatype GDT:PartyPartyID. BidderID may be based on datatype GDT:PartyPartyID. PaymentTransactionInitiatorID may be based on datatype GDT:PartyPartyID. PaymentTransactionDestinatedID may be based on datatype GDT:PartyPartyID. TaxID may be based on datatype GDT:PartyTaxID. TypeCode may be based on datatype GDT:BusinessObjectTypeCode. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name. FormAddress may be based on datatype GDT:FormAddress. ProductRecipientParty includes a node elements ContactPerson in a 1:C cardinality relationship.

For intra-enterprise communication with common master data, use InternalID for all party entities. For inter-enterprise communication with business-partner-specific master data, use the StandardID or the partner-role-specific ID of the receiving partner for all party entities. Use the BuyerID for Supplier Collaboration scenarios, and use the VendorID for Customer Collaboration scenarios. Due to the different possibilities for ID use, all ID elements of the particular “Party” are optional.

ContactPerson includes the non-node elements: InternalID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, FormAddress, and FormattedName. InternalID is a proprietary identifier that is used when both sender and recipient can access shared master data. It may be based on datatype GDT:ContactPersonInternalID with Qualifier:Internal. BuyerID may be based on datatype GDT:ContactPersonPartyID. SellerID is a proprietary identifier that is used by the SellerParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Seller. ProductRecipientID is a proprietary identifier that is used by the ProductRecipientParty for this location. It may be based on datatype GDT:ContactPersonPartyID with Qualifier:Product Recipient. VendorID may be based on datatype GDT:ContactPersonPartyID. BillToID may be based on datatype GDT:ContactPersonPartyID. BillFromID may be based on datatype GDT: ContactPersonPartyID. BidderID may be based on datatype GDT: ContactPersonPartyID. FormAddress may be based on datatype GDT:FormAddress. FormattedName may be based on datatype CDT:LANGUAGEINDEPENDENT_LONG_Name.

The ProcurementReleaseOrderItemLocation package includes a ShipToLocation entity. ShipToLocation represents the place to which the ordered products are delivered. ShipToLocation includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, and Note. InternalID is a proprietary identifier that is used when both sender and recipient can access shared master data. It may be based on datatype GDT:LocationInternalID with Qualifier:Internal. StandardID is a standardized identifier for this location, whose identification scheme is managed by an agency from a code list. It may be based on datatype GDT:LocationStandardID. BuyerID is a proprietary identifier used by the BuyerParty for this location. It may be based on datatype GDT:LocationPartyID with Qualifier:Buyer. SellerID is a proprietary identifier that is used by the SellerParty for this location. It may be based on datatype GDT:LocationPartyID with Qualifier:Seller. ProductRecipientID is a proprietary identifier that is used by the ProductRecipientParty for this location. It may be based on datatype GDT:LocationPartyID with Qualifier:Product Recipient. VendorID is a proprietary Identifier that is used by the VendorParty for this location. It may be based on datatype GDT:LocationPartyID with Qualifier:Vendor. Note indicates additional information. It may be based on datatype GDT:Note. ShipToLocation includes a node element Address in a 1:C cardinality relationship and a node element UnloadingLocation in a 1:C cardinality relationship.

For intra-enterprise communication, use the InternalID for all location entities. For inter-enterprise communication, use for all location entities either the StandardID or the partner-role-specific ID of the sending or receiving partner. Due to the different possibilities for ID use, all the ID elements of each location are optional.

The ProcurementReleaseOrderItemLocationAddress package includes an Address entity. The Address identifies the location by indicating e.g., postal address, or geographic coordinates. Address can be typed by FormAddress.

The ProcurementReleaseOrderItemLocationUnloading Location package includes an UnloadingLocation entity. UnloadingLocation represents a location where the delivered product is taken from the means of transport (e.g., a truck or a ship). UnloadingLocation includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, BillToID, BillFromID, BidderID, Note, and FormAddress. InternalID may be based on datatype GDT:LocationInternalID. StandardID may be based on datatype GDT:LocationStandardID. BuyerID may be based on datatype GDT:LocationPartyID. SellerID may be based on datatype GDT:LocationPartyID. ProductRecipientID may be based on datatype GDT:LocationPartyID. VendorID may be based on datatype GDT:LocationPartyID. BillToID may be based on datatype GDT:LocationPartyID. BillFromID may be based on datatype GDT:LocationPartyID. BidderID may be based on datatype GDT:LocationPartyID. Note may be based on datatype GDT:Note. FormAddress may be based on datatype GDT:FormAddress.

The ProcurementReleaseOrderItemProductInformation package includes Product and ProductRequirementSpecification entities. Product can be either a tangible or intangible good that is a part of the business activities of a company. It can be traded and contributes directly or indirectly to value added. Product includes the non-node elements: InternalID, StandardID, BuyerID, SellerID, ProductRecipientID, VendorID, ManufacturerID, BillToID, BillFromID, BidderID, TypeCode, TypeName, and Note. InternalID may be based on datatype GDT:LocationInternalID. StandardID may be based on datatype GDT:LocationStandardID. BuyerID may be based on datatype GDT:LocationPartyID. SellerID may be based on datatype GDT:LocationPartyID. ProductRecipientID may be based on datatype GDT:LocationPartyID. VendorID may be based on datatype GDT:LocationPartyID. ManufacturerID may be based on datatype GDT:ProductPartyID. BillToID may be based on datatype GDT:LocationPartyID. BillFromID may be based on datatype GDT:LocationPartyID. BidderID may be based on datatype GDT:LocationPartyID. TypeCode may be based on datatype GDT:ProductTypeCode. TypeName may be based on datatype CDT:Name. Note may be based on datatype GDT:Note.

For intra-enterprise communication, use the InternalID for all product entities. For inter-enterprise communication, use the StandardID or the partner-role-specific ID of the sending or receiving partner for all product entities. Due to the different possibilities for ID use, all ID elements of each particular product are optional.

ProductRequirementSpecification is a collection of requirements for a product used in a specific business context, for example, in a prototype, development project, or sales order. It also includes corresponding specifications for fulfilling these requirements.

ProductRequirementSpecification includes the non-node elements: InternalID, VersionInternalID, and Description. InternalID is a proprietary identifier of a product requirement specification. It may be based on datatype GDT:RequirementSpecificationID. VersionInternalID is a proprietary identifier of the version of a product requirement specification. It may be based on datatype GDT:VersionID. Description is a description of a product requirement specification. It may be based on datatype GDT:MEDIUM_Description with Qualifier:RequirementSpecification.

ProcurementReleaseOrderItemTextCollection package includes a TextCollection entity. TextCollection includes a non-node element Text. Text includes the elements TypeCode, TypeName, and SystemAdministrativeData. Text may be based on datatype FMIDT:FormTextCollectionText. TypeCode may be based on datatype GDT:TextCollectionTextTypeCode. TypeName may be based on datatype CDT:LANGUAGEINDEPENDENT_MEDIUM_Name. SystemAdministrativeData may be based on datatype FMIDT:FormSystemAdministrativeData.

ProcurementReleaseOrderItemAttachmentFolder package includes an AttachmentFolder entity. AttachmentFolder can be typed by AttachmentFolder.

The ProcurementReleaseOrderItemRequest package includes a Request entity. Request includes the non-node elements: ID, CreationDateTime, and PreviousItemRequestID. ID is a unique identifier for the request instance transferred in the procurement release order item. The ReleaseID is valid across all messages and is assigned for a release period such as a fiscal year or quarter. The ReleaseID does not identify a release order item. It may be based on datatype GDT:ReleaseOrderItemRequestID. CreationDateTime represents the reaction date and time of the release instance. It may be based on datatype CDT:LOCALNORMALISED_DateTime. PreviousItemRequestID is a unique identifier for the request instance transferred in the previous message. It may be based on datatype GDT:ReleaseOrderItemRequestID. Request includes a node element ScheduleLine in a 1:CN cardinality relationship. In some instances, Request may always be specified.

The ProcurementReleaseOrderItemRequestScheduleLine package includes a ScheduleLine entity. ScheduleLine is a statement about the quantity of a product to be delivered within a certain period of time. ScheduleLine includes the non-node elements ID and RequestedArrivalDateTimePeriod. ID is a unique identifier for the request schedule line instance transferred in the procurement release order. It may be based on datateype GDT: ReleaseOrderItemRequestScheduleLineID. RequestedArrivalDateTimePeriod represents the period in which the product is to be delivered. It may be based on datateype GDT:UPPEROPEN_LOCALNORMALISED_DateTimePeriod. ScheduleLine includes a node element RequestedQuantity in a 1:1 cardinality relationship.

RequestedQuantity represents the quantity of a product to be delivered. RequestedQuantity includes the non-node elements: Quantity, QuantityMeasureUnitCodeName, QuantityTypeCode, and QuantityTypeCodeName. Quantity may be based on datatype CDT:Quantity. QuantityMeasureUnitCodeName may be based on datatype CDT:Name. QuantityTypeCode may be based on datatype GDT: QuantityTypeCode. QuantityTypeCodeName may be based on datatype CDT:Name.

FIGS. 46-1 through 46-4 depict an example ProcurementReleaseOrderRequest Message Data Type 46000, which comprises elements 46002-46042, hierarchically related as shown. For example, the ProcurementReleaseOrderRequest 46002 includes a Message Header 46004.

The message type ProcurementReleaseOrderRequest is derived from the business object ReleaseOrderTemplate leading object together with its operation signature. A ProcurementReleaseOrderRequest is a request from a buyer to a seller about the quantities of products to be delivered on certain dates according to purchasing contract items. The structure of this message type can be determined by the message data type ProcurementReleaseOrderRequestMessage.

The ProcurementReleaseOrderRequestMessage message data type includes an object ProcurementReleaseOrder which is included in the business document, and business information that is relevant for sending a business document in a message. It includes MessageHeader and ProcurementReleaseOrder packages. This message data type can provide the structure for the ProcurementReleaseOrderRequest message type and the operations that are based on it.

MessageHeader Package is a grouping of business information that is relevant for sending a business document in a message. It includes the MessageHeader node. MessageHeader is a grouping of business information from the perspective of the sending application. It includes information to identify the business document in a message, information about the sender, and optionally, information about the recipient.

The MessageHeader includes SenderParty and RecipientParty elements. It can be of the type GDT:BusinessDocumentMessageHeader, and the elements of the GDT used include: RecipientParty, BusinessScope, SenderParty, SenderBusinessSystemID, TestDataIndicator, RecipientBusinessSystemID, ReferenceID, ReferenceUUID, ReconciliationIndicator, ID, UUID, and CreationDateTime.

SenderParty is a partner responsible for sending a business document at a business application level. The SenderParty may be based on datatype GDT:BusinessDocumentMessageHeaderParty. RecipientParty is a partner responsible for receiving a business document at a business application level. The RecipientParty may be based on datatype GDT:BusinessDocumentMessageHeaderParty.

The ProcurementReleaseOrder package is a grouping of ProcurementReleaseOrder with its packages. It includes BusinessTransactionDocumentReference, Party, AttachmentFolder, TextCollection, and Item packages, and a ProcurementReleaseOrder entity.

ProcurementReleaseOrder is a tool that is used by a customer to notify a supplier about the quantity of a material from a purchasing contract item that is to be delivered and at what time. ProcurementReleaseOrder includes the ActionCode and ReconciliationPeriod CounterValue attributes. ActionCode is a coded representation of an instruction to the message recipient how to process the ProcurementReleaseOrderRequest message. It may be based on datatype GDT:ActionCode. ReconciliationPeriod CounterValue represents a sequence number that identifies the reconciliation period this message refers to. It may be based on datatype GDT: CounterValue.

ProcurementReleaseOrder includes the non-node elements: ID, CreationDateTime, OrderedDateTime, and ItemListCompleteTransmissionIndicator. ID is a unique identifier for the ProcurementReleaseOrder. It may be based on datatype GDT:BusinessTransactionDocumentID. CreationDateTime represents the creation time of the procurement release order. It may be based on datatype CDT:LOCALNORMALISED_DateTime. OrderedDateTime represents the first time a procurement release order was sent to the supplier. It may be based on datatype CDT:LOCALNORMALISED_DateTime. ItemListCompleteTransmissionIndicator indicates if all items are transmitted in the message. It may be based on datatype CDT:Indicator.

ProcurementReleaseOrder includes a node element SalesOrderReference in a 1:C cardinality relationship, a node element OriginPurchaseOrderReference in a 1:C cardinality relationship, a node element BuyerParty in a 1:C cardinality relationship, a node element SellerParty in a 1:1 cardinality relationship, a node element LogisticsRequestResponsibleParty in a 1:C cardinality relationship, a node element FreightForwarderParty in a 1:C cardinality relationship, a node element AttachmentFolder in a 1:C cardinality relationship, a node element TextCollection in a 1:C cardinality relationship, and a node element Item in a 1:CN cardinality relationship.

The ProcurementReleaseOrderBusinessTransactionDocumentReference package includes SalesOrderReference and OriginPurchaseOrderReference entities. SalesOrderReference is a reference to the sales order which initiated the creation of the procurement release order. SalesOrderReference can be typed by BusinessTransactionDocumentReference. In some implementations, the reference is used in a third party direct ship scenario. OriginPurchaseOrderReference is a reference to the customer's purchase order which initiated the sales order in a third party direct ship scenario. OriginPurchaseOrderReference can be typed by BusinessTransactionDocumentReference.

The ProcurementReleaseOrderParty package includes BuyerParty, SellerParty, LogisticsRequestResponsibleParty, and FreightForwarderParty entities. A BuyerParty is a party that buys goods or services. BuyerParty can be typed by BusinessTransactionDocumentParty. The address of the BuyerParty is not intended to be used as the delivery address. The ShipToLocation is provided for this purpose. The SellerParty is a company or the person to sell the goods described in the ProcurementReleaseOrder. SellerParty can be typed by BusinessTransactionDocumentParty. LogisticsRequestResponsibleParty is a company or person that is responsible for logistics request. LogisticsRequestResponsibleParty can be typed by BusinessTransactionDocumentParty. FreightForwarderParty is a company or person that is responsible for organizing the shipment. FreightForwarderParty can be typed by BusinessTransactionDocumentParty.

The ProcurementReleaseOrderAttachmentFolder package is the grouping of the Document package. AttachmentFolder can be typed by AttachmentFolder.

The ProcurementReleaseOrderAttachmentFolderDocument package includes a Document entity. Document is an attachment, may be assigned, and includes unstructured information and additional control and monitoring information. A document includes unstructured information, as well as additional control and monitoring information. Document can be typed by Document.

The ProcurementReleaseOrderTextCollection package is the grouping of the Text package. TextCollection can be typed by TextCollection.

The ProcurementReleaseOrderTextCollectionText package includes a Text entity. Text is unstructured, readable information that includes additional formatting information within TextCollection. A text is recorded in a specific language and is characterized by its text type. Text can be typed by TextCollectionText.

The ProcurementReleaseOrderItem package is the grouping of BusinessTransactionDocumentReference, Party, Location, ProductInformation, TextCollection, AttachmentFolder, and Request packages.

ProcurementReleaseOrderItem is a statement regarding the requirement for a specific product at a ship-to location with reference to a purchasing contract item. Item includes an ActionCode attribute. ActionCode is a coded representation of an instruction to the message recipient as to how they should process the message item. It may be based on datatype GDT:ActionCode.

ProcurementReleaseOrderItem includes the non-node elements: ID, TypeCode, and CancellationDocumentIndicator. ID is a sequential number for the item in the ProcurementReleaseOrder document. It may be based on datatype GDT:BusinessTransactionDocumentItemID. TypeCode is a coded representation of the item's type. It may be based on datatype GDT:BusinessTransactionDocumentItemTypeCode. CancellationDocumentIndicator indicates whether this message cancels previous requests of the ProcurementReleaseOrderItem. It may be based on datatype CDT:Indicator.

ProcurementReleaseOrderItem includes a node element PurchasingContractReference in a 1:1 cardinality relationship, a node element SalesOrderReference in a 1:1 cardinality relationship, a node element OriginPurchaseOrderReference in a 1:1 cardinality relationship, a node element ProductRecipientParty in a 1:C cardinality relationship, a node element ShipToLocation in a 1:C cardinality relationship, a node element Product in a 1:1 cardinality relationship, a node element TextCollection in a 1:C cardinality relationship, a node element AttachmentFolder in a 1:C cardinality relationship, and a node element Request in a 1:1 cardinality relationship.

The ProcurementReleaseOrderItemBusinessTransactionDocumentReference package includes PurchasingContractReference, SalesOrderReference, and OriginPurchaseOrderReference entities. PurchasingContractReference is a reference to an item in a purchasing contract. In some implementations, the reference may always include the ItemID (purchasing contract item). SalesOrderReference is a reference to the sales order which initiated the creation of the procurement release order. In some implementations, the reference may always include the ItemID (sales order item). OriginPurchaseOrderReference is a reference to the customer's purchase order which initiated the sales order in a third party direct ship scenario. In some implementations, the reference may always include the ItemID (purchasing contract item).

The ProcurementReleaseOrderItemParty package includes a ProductRecipientParty entity. The ProductRecipientParty is a company or person that receives the goods delivery. ProductRecipientParty can be typed by BusinessTransactionDocumentParty.

The ProcurementReleaseOrderItemLocation package includes a ShipToLocation entity. ShipToLocation represents a place to which the ordered products are delivered. ShipToLocation can be typed by BusinessTransactionDocumentShipToLocation.

The ProcurementReleaseOrderItemProductInformation package includes a Product entity. Product can be either a tangible or intangible good that is a part of the business activities of a company. It can be traded and contributes directly or indirectly to value added. Product can be typed by BusinessTransactionDocumentProduct.

The ProcurementReleaseOrderItemTextCollection package includes a TextCollection entity. TextCollection can be typed by TextCollection.

The ProcurementReleaseOrderItemAttachmentFolder package includes an AttachmentFolder entity. AttachmentFolder can be typed by AttachmentFolder.

The ProcurementReleaseOrderItemRequest package includes a Request entity. Request includes the non-node elements: ID, CreationDateTime, and PreviousItemRequestID. ID is a unique identifier for the request instance transferred in the procurement release order item. The ReleaseID is valid across all messages and is assigned for a release period such as a fiscal year or quarter. The ReleaseID does not identify a release order item. It may be based on datatype GDT:ReleaseOrderItemRequestID. CreationDateTime represents the creation date and time of the release instance. It may be based on datatype CDT:DateTime. PreviousItemRequestID is a unique identifier for the request instance transferred in the previous message. It may be based on datatype GDT:ReleaseOrderItemRequestID. Request includes a node element ScheduleLine in a 1:CN cardinality relationship. In some implementations, request may always be specified.

The ProcurementReleaseOrderItem package includes a ScheduleLine entity. ProcurementReleaseOrderItemScheduleLine is a statement about the quantity of a product to be delivered within a certain period of time. ScheduleLine includes the non-node elements: ID, RequestedArrivalDateTimePeriod, RequestedQuantity, and RequestedQuantityTypeCode. ID is a unique identifier for the request schedule line instance transferred in the procurement release order. It may be based on datatype GDT:ReleaseOrderItemRequestScheduleLineID. RequestedArrivalDateTimePeriod represents the period in which the product is to be delivered. It may be based on datatype GDT:DateTimePeriod. RequestedQuantity represents the quantity of a product to be delivered or picked up. It may be based on datatype CDT:Quantity. RequestedQuantityTypeCode is a coded representation of schedule line's requested quantity type. It may be based on datatype GDT:QuantityTypeCode.

FIGS. 47-1 through 47-64 show an example configuration of an Element Structure that includes a FormProcurementReleaseOrderRequest 470000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 470000 through 472112. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the FormProcurementReleaseOrderRequest 470000 includes, among other things, a FormProcurementReleaseOrderRequest 470002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 48-1 through 48-237 show an example configuration of an Element Structure that includes a ProcurementReleaseOrderRequest 480000 package. Specifically, these figures depict the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as 480000 through 486426. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, the ProcurementReleaseOrderRequest 480000 includes, among other things, a ProcurementReleaseOrderRequest 480002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims.

Managing Consistent Interfaces for Goods Tag, Production Bill of Material Hierarchy, and Release Order Template Business Objects across Heterogeneous Systems

Information

Publication Number

Date Filed

Date Published

Inventors

CPC

US Classifications

International Classifications

Abstract

Description

Claims