Search Results psb_ae_headers_all_pk

Overview

PSB_AE_HEADERS_ALL is a transactional table within the Oracle E-Business Suite Public Sector Budgeting (PSB) module, documented as "Accounting Entry Headers." It serves as the header-level container for accounting entries generated during public sector budgeting activity, grouping the individual debit and credit distribution lines that constitute a complete accounting event. In this role the table sits between the upstream event capture layer and the downstream line-detail layer, providing the grouping key by which balanced accounting entries are assembled, validated, and ultimately transferred to the General Ledger.

The ETRM relationship metadata carries a heuristic Data Vault classification of satellite-leaning for this object. Read as a modeling suggestion rather than a physical constraint, this reflects the fact that the table's own descriptive attributes hang off a parent key (ACCOUNTING_EVENT_ID) and that the table itself is referenced as a parent by its line-level child. In Data Vault terms the header behaves less as an independent hub and more as a descriptive or linkage structure owned by the accounting event.

The ETRM excerpt records the object as "Not implemented in this database" for the sampled environment. This status should be read as an environment-specific observation rather than a statement of product-wide existence; the table's definition, primary key, and foreign key relationships are fully documented, indicating it is a legitimate PSB schema object that may be absent from the queried instance when the Public Sector Budgeting accounting-entry flow is not enabled or populated.

Key Information Stored

• AE_HEADER_ID — The surrogate primary key, defined by the constraint PSB_AE_HEADERS_ALL_PK. Every accounting entry header is uniquely identified by this system-generated numeric identifier, which is propagated to the associated accounting entry lines.
• ACCOUNTING_EVENT_ID — The foreign key column referencing PSB_ACCOUNTING_EVENTS_ALL. This is the principal business-key candidate, since it ties each header back to the parent accounting event that triggered the entry.

The documented metadata identifies only these two columns by name. Notably, ACCOUNTING_EVENT_ID functions as a business-key candidate because it establishes the mandatory link to the accounting event, whereas AE_HEADER_ID is purely a surrogate and carries no business meaning. Because the ETRM excerpt does not enumerate the remaining descriptive columns (such as entry status, accounting date, ledger, and period attributes that are typical of an accounting header structure), the columns above should be treated as the authoritative documented set, with any additional attributes confirmed directly against the deployed dictionary.

Common Use Cases and Queries

The dominant use case is reconstructing a complete accounting entry from its event source down to its individual lines. A representative pattern joins the header to its parent event and its child lines:

• Retrieve all headers for a given accounting event: SELECT * FROM PSB_AE_HEADERS_ALL WHERE ACCOUNTING_EVENT_ID = :event_id;
• Build the full entry hierarchy: SELECT h.AE_HEADER_ID, h.ACCOUNTING_EVENT_ID, l.* FROM PSB_AE_HEADERS_ALL h JOIN PSB_AE_LINES_ALL l ON l.AE_HEADER_ID = h.AE_HEADER_ID WHERE h.ACCOUNTING_EVENT_ID = :event_id;
• Match headers back to their originating events: SELECT h.AE_HEADER_ID, e.* FROM PSB_AE_HEADERS_ALL h JOIN PSB_ACCOUNTING_EVENTS_ALL e ON h.ACCOUNTING_EVENT_ID = e.ACCOUNTING_EVENT_ID;

Reporting scenarios include reconciliation of budget-generated accounting entries, auditing the completeness of header-to-line generation, and confirming that each accounting event produced the expected number of headers before GL transfer. Because the header is the natural grouping level, aggregate checks (such as counting lines per header) are best anchored on AE_HEADER_ID.

Related Objects

• PSB_ACCOUNTING_EVENTS_ALL — The parent event table; joined via PSB_AE_HEADERS_ALL.ACCOUNTING_EVENT_ID = PSB_ACCOUNTING_EVENTS_ALL.ACCOUNTING_EVENT_ID. Every header belongs to exactly one accounting event.
• PSB_AE_LINES_ALL — The child line table; joined via PSB_AE_LINES_ALL.AE_HEADER_ID = PSB_AE_HEADERS_ALL.AE_HEADER_ID. Each header owns one or more accounting entry lines.
• PSB_AE_HEADERS_ALL_PK — The primary key constraint enforcing uniqueness of AE_HEADER_ID.

Together these three objects — the event, the header, and the line — form the core accounting-entry structure within Public Sector Budgeting. Analysts should treat PSB_AE_HEADERS_ALL as the middle tier of this hierarchy, always resolving it in conjunction with its documented parent and child to obtain a complete and balanced picture of a budget accounting entry.