Search Results pa_rbs_txn_accum_map




Overview
Explore in AI Chat

Overview

PA_RBS_TXN_ACCUM_MAP is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mapping information between resource breakdown structure (RBS) elements and transaction accum headers. In practical terms, it functions as a cross-reference or association table: it records which RBS element from a specific RBS structure version applies to a given transaction accumulation header record. Transaction accumulation headers, in turn, are used by Project Resource Management and related costing processes to aggregate summarized transaction data against the resource breakdown structure.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification rather than a pure hub or link. This is a heuristic: the table carries descriptive context (element identity and structure version) attached to a header, plus the standard EBS audit columns, which is characteristic of a satellite structure. It should be treated as a modeling suggestion rather than a canonical Data Vault designation.

Key Information Stored

The table contains eight documented columns, of which the following are the most significant:

  • TXN_ACCUM_HEADER_ID — The identifier of the transaction accumulation header to which the RBS element mapping applies. This column participates in the unique business key.
  • STRUCT_VERSION_ID — The RBS structure version to which the mapped element belongs. This is a foreign key to PA_RBS_VERSIONS_B and also participates in the unique business key.
  • ELEMENT_ID — The specific resource breakdown structure element being mapped to the transaction accumulation header.
  • LAST_UPDATE_DATE — Standard EBS audit column recording when the row was last modified.
  • LAST_UPDATED_BY — Standard EBS audit column identifying the user who last updated the row.
  • CREATION_DATE — Standard EBS audit column recording when the row was created.
  • CREATED_BY — Standard EBS audit column identifying the user who created the row.
  • LAST_UPDATE_LOGIN — Standard EBS audit column capturing the login session associated with the last update.

The unique index PA_RBS_TXN_ACCUM_MAP_U1 on (TXN_ACCUM_HEADER_ID, STRUCT_VERSION_ID) represents the business-key candidate: a given structure version may be mapped to a given transaction accumulation header only once. The table has no documented single-column surrogate primary key exposed in the columns list, so the composite of TXN_ACCUM_HEADER_ID and STRUCT_VERSION_ID is the practical unique identifier. The ELEMENT_ID column is the descriptive payload that identifies which RBS element the mapping denotes.

Common Use Cases and Queries

Typical use cases include reconciling summarized transaction accumulations to the resource breakdown structure, validating RBS version usage across transaction headers, and reporting on which elements are associated with accumulated transaction data.

  • Mapping lookup for a header: SELECT STRUCT_VERSION_ID, ELEMENT_ID FROM PA_RBS_TXN_ACCUM_MAP WHERE TXN_ACCUM_HEADER_ID = :header_id;
  • RBS version usage: Join to PA_RBS_VERSIONS_B on STRUCT_VERSION_ID to resolve structure version attributes for a set of accum headers.
  • Integrity checks: Identify headers mapped to multiple structure versions, or structure versions with no mapped elements, to confirm data consistency after RBS maintenance.
  • Reporting: Drive RBS-based summaries by joining ELEMENT_ID to RBS element definitions and TXN_ACCUM_HEADER_ID to the corresponding transaction accumulation tables.

Because the table is narrow and audit-heavy, queries should filter by TXN_ACCUM_HEADER_ID or STRUCT_VERSION_ID to leverage the unique index rather than performing full scans.

Related Objects

  • PA_RBS_VERSIONS_B — Referenced by the foreign key PA_RBS_TXN_ACCUM_MAP.STRUCT_VERSION_ID. This is the primary parent object for RBS structure version attributes.
  • Transaction accumulation header tables — The TXN_ACCUM_HEADER_ID points to the transaction accumulation header entity within the Projects module; joins resolve header-level context.
  • RBS element definition tables — The ELEMENT_ID resolves to RBS element definitions used to describe the resource breakdown structure.
  • PA_RBS_VERSIONS_TL — Typically the translated table accompanying PA_RBS_VERSIONS_B, useful for multilingual reporting of version names.
  • Project resource management and costing APIs — Processes that create or consume transaction accumulations may insert, query, or depend on this mapping table as part of their execution.

As with all direct table access in EBS, modifications should be performed through supported APIs or concurrent programs rather than by manual DML, and any reporting should respect the standard audit columns for change tracking.