Results for “pn_rec_expcl_type_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_REC_EXPCL_TYPE_ALL is a Property Manager (PN) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store expense class types associated with an expense class. In practice, the table acts as the classification layer that qualifies an expense class record: each row associates one expense class type with a parent expense class, and it carries the descriptive code (EXPENSE_TYPE_CODE) that identifies the type of expense being tracked or recovered.

The object is owned by the PN schema and is reported as VALID in the ETRM metadata. The documented physical schema contains 25 columns and exposes a single named unique index, PN_REC_EXPCL_TYPE_U1, defined on EXPENSE_CLASS_TYPE_ID. The primary key constraint is PN_REC_EXPCL_TYPE_PK, which is also defined on EXPENSE_CLASS_TYPE_ID. Under the heuristic Data Vault classification derived from the foreign key structure, this table is characterized as satellite-leaning. That classification is a modeling suggestion rather than a fixed EBS attribute: the table behaves like a descriptive satellite attached to the expense class hub, qualified by the operating unit.

Key Information Stored

The most significant column is EXPENSE_CLASS_TYPE_ID, the surrogate primary key. It is the column on which both PN_REC_EXPCL_TYPE_PK and the unique index PN_REC_EXPCL_TYPE_U1 are defined, and it therefore serves as the stable identifier referenced by dependent records.

EXPENSE_CLASS_ID is the principal business-key foreign key. It links each type row back to the owning expense class record in PN_REC_EXPCL_ALL and effectively establishes the parent-child relationship between an expense class and its types. EXPENSE_TYPE_CODE holds the type classification itself, expressed as a code value, and is the descriptive column most often selected in reporting.

ORG_ID identifies the operating unit to which the row belongs and joins to HR_ALL_ORGANIZATION_UNITS, supporting multi-organization data access and security. The standard EBS audit columns are present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The table also carries the attribute flexfield set ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15, which are available for customer-specific extensions and are frequently populated by localization or customizations.

Common Use Cases and Queries

The primary use case is resolving the expense types configured against a given expense class within a specific operating unit. A typical query joins the table to its parent expense class and filters by organization:

• SELECT t.expense_class_type_id, t.expense_class_id, t.expense_type_code FROM pn_rec_expcl_type_all t WHERE t.expense_class_id = :expense_class_id AND t.org_id = :org_id;
• Listing all types belonging to an expense class for configuration validation or setup review.
• Joining to PN_REC_EXPCL_INC_ALL on EXPENSE_CLASS_TYPE_ID to determine which types have recovery or inclusion records defined.
• Reporting on expense type distribution by operating unit by joining ORG_ID to HR_ALL_ORGANIZATION_UNITS.

Because the table is keyed by a surrogate identifier and carries a code description, most reporting extracts select EXPENSE_CLASS_TYPE_ID and EXPENSE_TYPE_CODE together, then resolve the parent description from PN_REC_EXPCL_ALL.

Related Objects

• PN_REC_EXPCL_ALL — parent expense class table; joined on EXPENSE_CLASS_ID.
• PN_REC_EXPCL_INC_ALL — dependent table; references this table via EXPENSE_CLASS_TYPE_ID, forming the inclusion detail for each expense class type.
• HR_ALL_ORGANIZATION_UNITS — organization/operating unit reference; joined on ORG_ID.

These relationships establish PN_REC_EXPCL_TYPE_ALL as the junction between an expense class definition and its inclusion or recovery detail, with organization context supplied by the HR organization hierarchy.