Search Results ce_cp_worksheet_headers_pk

Overview

CE_CP_WORKSHEET_HEADERS is a Cash Management (CE) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the Cash Position worksheet header definitions. Each row in this table represents a single named worksheet layout that users can select or save when working with the Cash Position feature of Oracle Cash Management, which is used to project, monitor, and reconcile cash balances across bank accounts and internal sources.

The table functions as the top-level definitional object for Cash Position worksheets. A worksheet header captures the identity of the worksheet (its name) and its display configuration, most notably the set of columns shown. This makes the table a configuration/master-data object rather than a transactional one; it does not itself store calculated cash position balances, but instead drives how those balances are presented and grouped when a worksheet is run.

From a Data Vault modeling perspective, the heuristic classification provided in the metadata is standalone. This is a sensible modeling suggestion: the table carries no documented foreign-key relationships to other tables, and its primary key is a single surrogate column. In a Data Vault design it would therefore most naturally be modeled as a hub (or as a small reference/configuration hub) for worksheet header identity, keyed on the surrogate identifier, with the descriptive attributes treated as satellite-style attributes.

Key Information Stored

The documented physical schema for 12.2.2 contains nine columns. The most important are:

• WORKSHEET_HEADER_ID — the surrogate primary key of the table, defined by the constraint CE_CP_WORKSHEET_HEADERS_PK. It uniquely identifies each worksheet header and is also exposed through the unique index CE_CP_WORKSHEET_HEADERS_U1.
• WORKSHEET_NAME — the user-facing business name of the worksheet. It is a business-key candidate, enforced by the unique index CE_CP_WORKSHEET_HEADERS_U2. This is the value users see and select when choosing a saved Cash Position worksheet.
• COLUMNS_DISPLAYED — the stored configuration describing which columns are presented on the worksheet, governing the layout and level of detail displayed.
• PD_FLAG — a flag column, typically used to distinguish predefined (seeded) worksheet definitions from user-defined ones.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO audit columns capturing when and by whom the record was last modified.
• CREATION_DATE, CREATED_BY — the standard creation audit columns recording the original insert date and user.

The distinction between the surrogate primary key (WORKSHEET_HEADER_ID) and the business-key candidates (the unique indexes on WORKSHEET_HEADER_ID and WORKSHEET_NAME) is important for any integration or data-migration work: WORKSHEET_NAME is the natural key that must remain unique and stable, while WORKSHEET_HEADER_ID is the internally generated identifier used for joins and referential integrity.

Common Use Cases and Queries

Typical scenarios include auditing which Cash Position worksheets exist, identifying seeded versus custom worksheets, and reporting on worksheet layout configuration. A basic listing query is:

• SELECT worksheet_header_id, worksheet_name, columns_displayed, pd_flag FROM ce.ce_cp_worksheet_headers ORDER BY worksheet_name;

To find predefined (seeded) definitions: SELECT worksheet_name FROM ce.ce_cp_worksheet_headers WHERE pd_flag = 'Y';

To resolve a worksheet by its natural business key, query on the unique business-key column: SELECT worksheet_header_id FROM ce.ce_cp_worksheet_headers WHERE worksheet_name = :p_name;

Because WORKSHEET_NAME is uniquely indexed, it is safe to treat it as the lookup key in interface or conversion scripts, while WORKSHEET_HEADER_ID should be captured as the foreign key when populating downstream worksheet line or detail structures. Reporting use cases include generating an inventory of available worksheet layouts for a Cash Position implementation, validating that no duplicate worksheet names exist before import, and tracking who created or last modified each worksheet definition for change-control purposes.

Related Objects

The metadata describes this object as standalone, with no FK relationships mined from its key structure. In practice, the worksheet header is the parent definition that is referenced by downstream Cash Position worksheet line and column detail objects within the CE module. Significant related objects to consider when working with this table include:

• CE_CP_WORKSHEET_LINES (or equivalent worksheet detail table) — referenced by WORKSHEET_HEADER_ID, storing the line-level content of a worksheet.
• CE_CP_WORKSHEET_COLUMNS (or equivalent column-configuration table) — referenced by WORKSHEET_HEADER_ID, defining the individual columns represented in COLUMNS_DISPLAYED.
• CE_CP_WORKSHEET_VALUES (or equivalent values table) — holding the data shown per column and source for a given worksheet header.
• CE_BANK_ACCOUNTS — the bank account source records whose cash positions feed the worksheets.
• CE_CASH_POOLS and cash pool member tables — the pooling structures that supply aggregated cash position data to worksheets.

Because no explicit FK relationships are documented for this table, join columns should be verified against the actual worksheet detail objects in the deployment. The primary join column throughout is WORKSHEET_HEADER_ID, which links the header to all of its detail rows.