Glossary

capable to deliver: CTD (Capable to Deliver) refers to considering the transportation resources and transportation lead time to meet your customers delivery needs. In this release, only transportation lead time is being considered. Transportation resources will be added in a future release.

Package level tags: Package level tags can appear anywhere after a “CREATE OR REPLACE” statement and before any uncommented package contents, including variables, program units, etc. For example, --<TPA_LAYER=layer name>indicates that the package belongs to the specified Trading Partner Layer.

Program Unit Level Tags: Program unit level tags must appear immediately after keyword 'IS'.TPS Program Unit: --<TPA_TPS>

Public Program Unit: Those program units published as customizable by Oracle Development teams. Layers can be built only on those program units that are designated by an Oracle Development team as public. These may also be referred to as published or customizable program units.

subinventory: Subdivision of an organization, representing either a physical area or a logical grouping of items, such as a storeroom or receiving dock.

TPA metadata file: Contains information extracted from the TPA repository about TPA enabled program units and layers built on top of them. This file is used to ship the TPA registry, or repository, and merge layers at the customer site. This file must be shipped with any patch that contains TPA enabled program units.

TPA package: The package containing TPA program units. This package is always generated from the TPA repository.

TPA program unit: The mirror program unit for a public program unit. For every public program unit, Oracle developers will designate a TPA program unit. TPA program units are generated by the architecture to insulate generic code from custom code. All calls to customizable generic code and custom code are made through the TPA program unit.

TPA repository: The registry which stores data required for the functioning of the Trading Partner Architecture. It includes information about public program units, TPA program units, TPS program units and complete definition of the layers including the Oracle Base Layer.

TPA tag: One-line hyphen comments which appear at the beginning of a new line and provide information about customizable program units within Oracle code. The syntax for a TPA tag is:--<tag name=tag value>For example, a label is specified as follows,--<TPA_LABEL=label>

Trading Partner Architecture (TPA): The framework that supports PL/SQL based layer development and deployment.

trading partner flexfield: Descriptive flexfields reserved on several base tables for capturing additional attributes applicable to specific trading partners. They are provided for most of the base tables in Oracle Release Management, Shipping, and Order Management.

trading partner layer: The trading partner specific code created to replace Base Layer code. The layer consists of a set of PL/SQL program units that perform trading partner specific processing or validations in place of the generic code provided by Oracle Development.Layer Providers develop this code and populate the Trading Partner Layers by importing the trading partner specific code into the TPA repository. In this way, Layer Providers can develop Trading Partner Layers composed of trading partner specific code for various trading partners.

Trading Partner Selector (TPS): A program unit which accepts context information for the business transaction and derives trading partner entities being processed in the current transaction instance.All TPS Program units must have the following five output (OUT/IN OUT) arguments:

trip planning stop: The process of planning the necessary vehicles and grouping the scheduled shipments that will be included in a given trip. Planning the trip requires consideration of vehicle load capacities, container capacities and, in certain cases, the loading order for the customer's specified unload order.