Results for “pa_exp_orgs_it”

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

Overview

PA_EXP_ORGS_IT is a Project Accounting (PA) base table that stores information about expenditure organizations used by the Oracle Project Analysis Collection Pack. In Oracle E-Business Suite 12.1.1 and 12.2.2, the table acts as a shared reference master: an expenditure organization identifies the organizational unit against which project-related expenditure, commitments, and Payables transactions are attributed. Because multiple subledgers validate expenditure items against this table, it functions as a central validation source for Projects, Payables, and Tax data.

The ETRM physical schema documents the object under the PA schema with 23 columns and status VALID. Its primary key is PA_EXP_ORGS_IT_PK on ORGANIZATION_ID, and it also carries the unique index PA_EXP_ORGS_IT_U1 on the same column. From a Data Vault modelling perspective (a heuristic derived from the foreign-key structure), the table is classified as hub-leaning: it holds a stable, uniquely identified business entity (the expenditure organization), keyed by its own identifier and related upward to a business group. It is not primarily a transactional fact or a link table, although it participates in several dependent relationships as the parent of foreign keys in other modules.

Key Information Stored

The following columns are the most significant for identification and operational use, based on the documented metadata and ETRM schema listing:

• ORGANIZATION_ID — the surrogate primary key and the value propagated to dependent subledger tables. Uniquely identifies each expenditure organization row and is enforced by both PA_EXP_ORGS_IT_PK and the unique index PA_EXP_ORGS_IT_U1.
• ORGANIZATION — the descriptive organization value used in reporting and user-facing views of expenditure organization data.
• BUSINESS_GROUP — foreign key to PA_EXP_BUSINESS_GRPS_IT, establishing the higher-level business group to which the expenditure organization belongs.
• STATUS_CODE — indicates whether the expenditure organization is active or inactive; this drives validation in downstream transactions.
• LAST_UPDATE_DATE and LAST_UPDATED_BY — audit columns recording when and by whom the record was most recently changed.
• CREATION_DATE and CREATED_BY — audit columns recording record creation.
• LAST_UPDATE_LOGIN — login context associated with the most recent update.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — concurrent program and request context used for traceability of automated loads and updates.
• USER_COL1 through USER_COL10 — generic extension attributes reserved for customer-specific or rollout configuration data.

Note that the surrogate primary key (ORGANIZATION_ID) and the business-key candidate (PA_EXP_ORGS_IT_U1) coincide on the same column in the documented schema; the distinguishing business attribute set in the wider model includes organization, business group, and status.

Common Use Cases and Queries

Typical use cases include resolving the expenditure organization on project commitments and Payables distributions, validating organization activity status, and producing cross-module reporting of spend by expenditure organization. Common query patterns join this table to its business group or to dependent transaction tables on ORGANIZATION_ID.

• Listing active expenditure organizations: SELECT ORGANIZATION_ID, ORGANIZATION, BUSINESS_GROUP, STATUS_CODE FROM PA_EXP_ORGS_IT WHERE STATUS_CODE = 'A';
• Resolving Payables invoice distributions to their expenditure organization: SELECT ai.INVOICE_NUM, aid.DISTRIBUTION_LINE_NUMBER, eob.ORGANIZATION FROM AP_INVOICE_DISTRIBUTIONS_ALL aid JOIN PA_EXP_ORGS_IT eob ON eob.ORGANIZATION_ID = aid.EXPENDITURE_ORGANIZATION_ID JOIN AP_INVOICES_ALL ai ON ai.INVOICE_ID = aid.INVOICE_ID;
• Reporting project commitment activity by expense organization: join PA_PRJ_ACT_CMT_IT_ALL or PA_TSK_ACT_CMT_IT_ALL to PA_EXP_ORGS_IT on EXPENSE_ORGANIZATION_ID.
• Validating the business-group hierarchy: join PA_EXP_BUSINESS_GRPS_IT on BUSINESS_GROUP.
• Auditing automated maintenance by filtering on REQUEST_ID and PROGRAM_ID.

Related Objects

The table is referenced by several significant objects across Projects, Payables, and Tax through explicitly documented foreign keys:

• PA_EXP_BUSINESS_GRPS_IT — parent business-group table, joined via BUSINESS_GROUP.
• AP_DISTRIBUTION_SET_LINES_ALL — references this table via EXPENDITURE_ORGANIZATION_ID.
• AP_EXPENSE_REPORT_LINES_ALL — references this table via EXPENDITURE_ORGANIZATION_ID.
• AP_INVOICES_ALL — references this table via EXPENDITURE_ORGANIZATION_ID.
• AP_INVOICE_DISTRIBUTIONS_ALL — references this table via EXPENDITURE_ORGANIZATION_ID.
• PA_PRJ_ACT_CMT_IT_ALL and PA_TSK_ACT_CMT_IT_ALL — project and task commitment tables referencing via EXPENSE_ORGANIZATION_ID.
• ZX_REC_NREC_DIST — Tax recovery/non-recoverable distribution table referencing via EXPENDITURE_ORGANIZATION_ID.

Collectively, these relationships confirm that PA_EXP_ORGS_IT serves as a shared reference hub for expenditure organization validation across Oracle Project Analysis Collection Pack and adjacent subledger processing.