Glossary

Batch

A collection of data operations that are processed during import at one time. The size is determined by a configurable parameter. Upon failure, an entire batch of data operations is rolled back.

Bundle

A collection of import files, one file per data type, stored as a compressed archive containing a manifest. It is expected that the retailer or implementation team is responsible for delivering to the store the bundle along with manifest for all data feeds to the store. MOM applications can package the bundle but do not provide delivery functions.

Corporate

Used interchangeably with enterprise. The enterprise environment of the retailer where enterprise applications are deployed. Central Office is deployed in the enterprise.

Data Access Object (DAO)

A Java class that can retrieve and persist data to and from a data source. DAO is well-known JEE development pattern.

Data Distribution Infrastructure (DDI )

The infrastructure and application components that are responsible for distributing seed data from enterprise applications to Store applications, ODS at Corporate (or enterprise), and Store Database at the stores.

Data Transfer Object (DTO)

A class that contains data records from a received payload. The DTO's attributes are populated with the parsed data.

DIMP

Data Import. Specifically, the background data import mechanism supported by Back Office, Central Office and Returns Management.

Incremental

There are two types of update operation, full incremental and delta incremental. Full incremental assumes that all the fields for a data type are supplied in the XML. A delta incremental import contains only the fields that are being changed.

ISP

In-Store-Processor

JEE/J2EE

Java Enterprise Edition is a set of APIs designed to support tier 1 type business models.

Java Database Connectivity (JDBC)

An API used to communicate with relational databases.

Kill And Fill

Kill And Fill refers to a data operation where all the existing data in a table is deleted (kill) and then replaced with new data (fill).

Limit (discount rule)

The maximum price allowed for a source or target to be part of a deal. Used most often when the source or target is a classification or department where many different priced items exist.

Manifest

A file within a bundle that lists the data files in the bundle and their interdependencies.

Minimum Data

Minimum data is defined as the minimum set of data necessary to support the deployment of Stores applications.

If the user attempts to select any function or log in, an error may occur in the application without sample data loaded. See Sample Data.

Operational Data Store (ODS)

The corporate data repository that services Central Office.

POS Suite

The Oracle Retail business unit that assumes responsibility for applications running in the Store environment.

Sample Data

A set of data used to demonstrate application features.

Store Applications

Oracle Retail applications that run in the store environment include the following:

Oracle Retail Back Office
Oracle Retail Point-of-Service
Oracle Retail Store Inventory Management
Oracle Retail Central Office
Oracle Retail Returns Management

Even though Central Office and Returns Management run in the corporate environment, they are classified as store applications.

Store Database (SDB)

The data repository for store applications.

Threshold (discount rule)

The minimum price allowed for a source or target to be part of a deal. Used most often when the source or target is a classification or department where many different priced items exist.