Results for “workflow_item_key”

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

Overview

PV_GE_TEMP_APPROVERS is a transactional table in the PV (Partner Management) module of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. It serves as a container for approver-related information associated with a given entity, storing the staging and working data used during partner enrollment and related approval workflows. The table bridges the gap between the entity being approved and the FND_USER responsible for acting on it, making it central to the approval routing logic in the Partner Management product family.

Under a heuristic Data Vault classification mined from its foreign-key structure, this object is best modeled as a link. It resolves the many-to-many relationship between approvers (FND_USER) and approval-bearing entities (PV_PG_ENRL_REQUESTS), carrying its own descriptive and workflow-status attributes rather than functioning as a pure hub or satellite. This classification is a modeling suggestion derived from the FK topology, not a declaration in the source documentation.

Key Information Stored

The table is documented with thirteen physical columns. The most significant are:

• ENTITY_APPROVER_ID — the surrogate primary key, uniquely defined by PV_GE_TEMP_APPROVERS_PK and reinforced by the unique index PV_GE_TEMP_APPROVERS_U1, which serves as the business-key candidate.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
• ARC_APPR_FOR_ENTITY_CODE — an archival or archive-indicator column relating to the entity the approver is scoped against.
• APPR_FOR_ENTITY_ID — foreign key to PV_PG_ENRL_REQUESTS, identifying the enrollment request that this approver row pertains to.
• APPROVER_ID — foreign key to FND_USER, identifying the individual user designated as approver.
• APPROVER_TYPE_CODE — classifies the approver (for example, an approver role or category).
• APPROVAL_STATUS_CODE — the current disposition of the approver's response (for example, pending, approved, or rejected).
• WORKFLOW_ITEM_KEY — the Oracle Workflow item key that correlates the approval row with the specific running workflow process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

Typical usage centers on determining who must approve a given enrollment request and the state of that approval. A common reporting query joins the approver table to FND_USER to resolve approver names:

• Pending approvals by user: SELECT a.APPR_FOR_ENTITY_ID, u.USER_NAME, a.APPROVAL_STATUS_CODE FROM PV_GE_TEMP_APPROVERS a, FND_USER u WHERE a.APPROVER_ID = u.USER_ID AND a.APPROVAL_STATUS_CODE = 'PENDING';
• Approvers per enrollment request: join APPR_FOR_ENTITY_ID to PV_PG_ENRL_REQUESTS to list all approvers associated with a specific request.
• Workflow reconciliation: correlate WORKFLOW_ITEM_KEY against WF_ITEMS to trace stalled or errored approval processes.
• Audit and history reporting: use the CREATED_BY / LAST_UPDATED_BY columns to report approval activity over time.

Because the table is a working container, rows may be transient; queries should be scoped by status and entity to avoid stale records.

Related Objects

The following objects are most significant to PV_GE_TEMP_APPROVERS, based on documented foreign-key relationships:

• FND_USER — referenced via PV_GE_TEMP_APPROVERS.APPROVER_ID; supplies the approver identity.
• PV_PG_ENRL_REQUESTS — referenced via PV_GE_TEMP_APPROVERS.APPR_FOR_ENTITY_ID; the enrollment request being approved.
• Oracle Workflow (WF_ITEMS / WF_NOTIFICATIONS) — correlated through WORKFLOW_ITEM_KEY for approval routing.

Applications and concurrent programs in the Partner Management module that drive enrollment approval logic consume this table directly, and any custom reporting or workflow extensions should treat the primary key ENTITY_APPROVER_ID as the reliable row identity.