Results for “igw_implementations_all”

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

Overview

IGW_IMPLEMENTATIONS_ALL is the Oracle Grants Proposal (IGW) implementation-parameters table, owned by the IGW schema. It stores the set of setup decisions that govern how the Grants Proposal application behaves for a given operating unit: how proposals are numbered, which expenditure category schemes are used for overhead and unallowable costs, and which HR organization structures and versions drive approval and proposal routing. Because Grants Proposal is licensed and configured per operating unit, the table carries ORG_ID and is registered with the _ALL designation, making it a multi-organization reference table.

The table is a low-volume configuration object. In a typical EBS 12.1.1 or 12.2.2 installation it holds one row per operating unit that has enabled Grants Proposal, and it is queried constantly by the proposal and award forms at runtime to resolve numbering and accounting defaults. The heuristic Data Vault classification mined from the foreign-key structure is link: the table predominantly records relationships between organizational and expenditure classification entities rather than holding descriptive or transactional detail.

Key Information Stored

The documented physical schema contains twenty columns. The most functionally significant are:

• ORG_ID — the operating unit identifier and the sole documented unique index column (IGW_IMPLEMENTATIONS_ALL_U1). Although the ETRM card lists IGW_IMPLEMENTATIONS_ALL as the primary key, ORG_ID is the effective business key that drives multi-org filtering in every query.
• PROPOSAL_NUMBERING_METHOD and MANUAL_PROPOSAL_NUMB_METHOD — control whether proposal numbers are generated automatically or entered by the user, and which manual entry mode applies.
• NEXT_AUTOMATIC_PROPOSAL_NUMBER — the next value assigned by the automatic numbering engine.
• OH_EXPENDITURE_CATEGORY_TYPE and OH_EXPENDITURE_FLAG — the overhead category scheme and the flag that enables or disables its use.
• UNM_EXPENDITURE_CATEGORY_TYPE and UNM_EXPENDITURE_FLAG — the equivalent configuration for unallowable (UNM) expenditure processing.
• PRP_ORG_STRUCTURE_ID, PRP_ORG_STRUCTURE_VERSION_ID, PRP_ORG_STRUCTURE_START_ID — the HR organization structure, version, and start reference used for proposal routing and review.
• APR_ORG_STRUCTURE_ID, APR_ORG_STRUCTURE_VERSION_ID, APR_ORG_STRUCTURE_START_ID — the corresponding structure and version used for approval routing.
• BUSINESS_GROUP_ID — the HR business group under which the referenced organizations reside.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO audit columns.

Common Use Cases and Queries

Typical development and support scenarios include verifying that Grants Proposal setup exists for an operating unit before attempting to create proposals, diagnosing incorrect proposal numbers, and validating that overhead and unallowable category options are configured as expected.

• Implementation verification: SELECT org_id, proposal_numbering_method, next_automatic_proposal_number FROM igw_implementations_all ORDER BY org_id;
• Numbering diagnostics: inspect NEXT_AUTOMATIC_PROPOSAL_NUMBER against the highest proposal number in the proposal tables to detect drift.
• Expenditure configuration reporting: return OH_EXPENDITURE_CATEGORY_TYPE, OH_EXPENDITURE_FLAG, UNM_EXPENDITURE_CATEGORY_TYPE, and UNM_EXPENDITURE_FLAG for each operating unit to document how overhead and unallowable costs are treated.
• Organization-routing audit: join PRP_ and APR_ structure columns to PER_ORGANIZATION_STRUCTURES and PER_ORG_STRUCTURE_VERSIONS to confirm which hierarchy is active.
• Post-clone or post-patch checks: because this is a per-org configuration row, it is a common omission after database refreshes and should be validated explicitly.

Related Objects

• PER_ORGANIZATION_STRUCTURES — referenced via APR_ORG_STRUCTURE_ID and PRP_ORG_STRUCTURE_ID; resolves the organization hierarchy definitions.
• PER_ORG_STRUCTURE_VERSIONS — referenced via APR_ORG_STRUCTURE_VERSION_ID and PRP_ORG_STRUCTURE_VERSION_ID; identifies the dated version of each structure.
• HR_ALL_ORGANIZATION_UNITS — referenced via BUSINESS_GROUP_ID; supplies the business group context.
• PA_EXPENDITURE_CATEGORIES — referenced by both OH_EXPENDITURE_CATEGORY_TYPE and UNM_EXPENDITURE_CATEGORY_TYPE.
• PA_EXPENDITURE_TYPES — also referenced by the OH_ and UNM_EXPENDITURE_CATEGORY_TYPE columns.
• IGW proposal and award tables — the functional consumers of the numbering and routing parameters defined here.

No dedicated public API is documented for this table; configuration is normally maintained through the Grants Proposal setup responsibility rather than direct DML. Because the table is a foreign-key parent in no relationships of its own, it sits at the configuration end of the model, supplying values that downstream proposal, approval, and cost-processing logic read at runtime.