2-2 Concepts and Technologies Guide for Oracle Application Integration Architecture
primary business components; Sales Order Line and Sales Order Schedule are examples of supplementary business components. The following sections describe the
various components that form the EBO.
2.1.1 Business Component
An EBO business component is a subset of an EBO that has complex content many properties and exists only within the context of the EBO. These components are the
high-level building blocks of any EBO.
Examples include Sales Order Header and Invoice Line. Each EBO is built from one or more EBO business components.
An EBO business component may have a primary or a supplementary role in defining an EBO. Each EBO is built from one or more EBO business components. Business
components that can be used across various context-specific definitions for a single EBO are defined within the EBO schema module.
2.1.2 Common Components
These are reusable common components that are used by many EBO business components. A common business component is a subset of an EBO business
component that has complex content many properties. Examples of common business components include concepts such as tax, charge, status, address, and so
forth. Generally speaking, the content within a common business component is complete enough to both identify and define the component. This implies that
applications could use the common components associated with an EBO to create or update application objects. For example, Address is a common business component
that is used by many different EBOs. The content model of Address contains sufficient information for an application to identify as well as create and update the address as
necessary when the address is supplied as part of an EBOs content. Note that for this to happen, the application that creates the EBO instance must ensure that the address
information is complete. No one-to-one relationship exists between a data model entity such as table or a foreign key relationship to a common business component. A
set of attributes or a foreign key relationship in a table could resolve to a common business component. Foreign keys by themselves could resolve to either common
business components, reference business components, or other business components within the EBO definition.
A customization to one of these common objects is automatically reflected in all EBOs that reference that object. An example would be an Address definition type. If your
implementation requires customizing this address format by adding a third address line, the modification of the Address definition type automatically affects the
addresses referenced in EBOs. This design philosophy significantly reduces the design, development, and maintenance of common objects.
Components that are applicable to all EBOs are defined in a common components schema module.
2.1.3 Reference Components
