Search Results igi_exp_apprv_profiles_pk

Overview

IGI.IGI_EXP_APPRV_PROFILES_ALL is a table within the IGI (Public Sector Financials International) product family of Oracle E-Business Suite. It stores the definition and configuration details of workflow approval profiles that are created and maintained through the Workflow Approval Profile form. In the ETRM context, an approval profile serves as a reusable routing definition that governs how expenditure items, task assignments, and related transactions are approved before they proceed through the workflow engine.

The table resides in the IGI schema and is designated VALID in the 12.1.1 and 12.2.2 releases. It is multi-organization aware, as evidenced by the presence of ORG_ID and the _ALL suffix, meaning rows are partitioned by operating unit and typically filtered through the MO security profile in reporting and transactional queries.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table carries a stable surrogate primary key that is referenced by dependent transactional and header tables, positioning it as a core reference or hub entity rather than a pure satellite of another subject.

Key Information Stored

The documented physical schema defines twelve columns. The most important for functional and reporting purposes are:

• APPRV_PROFILE_ID — the surrogate primary key, uniquely generated per profile. It is also the basis of unique index IGI_EXP_APPRV_PROFILES_PK and IGI_EXP_APPRV_PROFILES_U1.
• APPRV_PROFILE_NAME — the user-facing name of the approval profile. Together with ORG_ID it forms business-key candidate IGI_EXP_APPRV_PROFILES_U2, enforcing uniqueness of profile names within an operating unit.
• PROFILE_ENABLED — flag indicating whether the profile is active and available for use in approval processing.
• POS_HIERARCHY_ID — identifies the position hierarchy applied when determining approval routing.
• FINAL_APPRV_POS_ID — the position that performs final approval in the workflow.
• LEGAL_NUM_POS_ID — the position responsible for legal number or coding validation steps.
• ORG_ID — the operating unit that owns the profile, supporting multi-org data segregation.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture who created and last maintained the profile, which is essential for change auditing and compliance reporting.

The distinction between the surrogate key (APPRV_PROFILE_ID) and the business-key candidate (APPRV_PROFILE_NAME + ORG_ID) is critical when integrating with external systems, since the surrogate should be used for joins while the business key is used for verification and de-duplication.

Common Use Cases and Queries

Typical scenarios include identifying all enabled profiles for an operating unit, reviewing the final approver for a given profile, and auditing recently modified profiles. Representative SQL patterns:

• List active profiles by operating unit: SELECT APPRV_PROFILE_ID, APPRV_PROFILE_NAME FROM IGI_EXP_APPRV_PROFILES_ALL WHERE ORG_ID = :org AND PROFILE_ENABLED = 'Y';
• Resolve a profile by business key: ... WHERE APPRV_PROFILE_NAME = :name AND ORG_ID = :org;
• Audit recent changes: SELECT APPRV_PROFILE_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGI_EXP_APPRV_PROFILES_ALL ORDER BY LAST_UPDATE_DATE DESC;
• Join to dependent transaction tables using APPRV_PROFILE_ID to report which task assignments or task type headers are governed by each profile.

These queries support approval-routing analysis, segregation-of-duties reviews, and configuration migration reconciliations.

Related Objects

The following documented dependents reference this table through APPRV_PROFILE_ID:

• IGI_EXP_TUS_ALL — via IGI_EXP_TUS_ALL.APPRV_PROFILE_ID, linking task assignments to the approval profile that governs them.
• IGI_EXP_TU_TYPE_HEADERS_ALL — via IGI_EXP_TU_TYPE_HEADERS_ALL.APPRV_PROFILE_ID, associating task type headers with an approval profile.
• The Workflow Approval Profile form — the primary maintenance UI that creates and updates records in this table.
• Oracle Workflow engine components and position hierarchy definitions (referenced through POS_HIERARCHY_ID, FINAL_APPRV_POS_ID, and LEGAL_NUM_POS_ID) that consume the profile during runtime routing.

Together these objects form the approval configuration layer for IGI expenditure processing.