Results for “approver_id”

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

Overview

The SO_LINE_APPROVALS table is an Order Entry (OE) transactional table that captures order line-level approval activity within Oracle E-Business Suite. Stored in the OE schema with status VALID in both 12.1.1 and 12.2.2, it records the outcome of approval workflow processing applied to individual sales order lines. While order header approvals are tracked through related structures, this table specifically supports the granularity of line-level review, which is required when orders contain lines subject to differing approval rules — for example, lines exceeding credit thresholds, non-standard items, or lines requiring exception handling.

Under the heuristic Data Vault classification mined from its foreign key structure, SO_LINE_APPROVALS is best modeled as a link table. It does not represent an independent business entity; rather, it resolves and records the association between a sales order line, the approver, the approval action, and the result. Practitioners designing analytical or warehouse models should treat it as a relationship/event table connected to hub-like entities such as SO_LINES_ALL, SO_HEADERS_ALL, FND_USER, SO_ACTIONS, and SO_RESULTS_B.

Key Information Stored

The table contains 29 documented columns. The most significant include:

• LINE_APPROVAL_ID — surrogate primary key (SO_LINE_APPROVALS_PK), also enforced by unique index SO_LINE_APPROVALS_U1. This is the technical identifier, not a business key.
• HEADER_ID — foreign key to SO_HEADERS_ALL, identifying the parent order.
• LINE_ID — foreign key to SO_LINES_ALL, identifying the specific order line under approval.
• APPROVER_ID — foreign key to FND_USER, indicating the user who performed or is assigned the approval.
• ACTION_ID — foreign key to SO_ACTIONS, referencing the approval action performed.
• RESULT_ID — foreign key to SO_RESULTS_B, capturing the outcome or disposition of the action.
• DATE_APPROVED — timestamp of the approval event, critical for audit and cycle-time reporting.
• APPROVAL_COMMENT — free-text remarks entered by the approver.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns available for client-specific extensibility.

No independent business-key candidate is documented beyond the surrogate key; unique identification is achieved solely through LINE_APPROVAL_ID.

Common Use Cases and Queries

Typical uses include approval audit trails, approver productivity reporting, and order hold/approval cycle-time analysis. A representative query joining the principal relationships:

• SELECT sla.line_approval_id, sla.header_id, sla.line_id, sla.approver_id, sla.date_approved, sla.approval_comment FROM oe.so_line_approvals sla WHERE sla.header_id = :p_header_id;
• Join to FND_USER on APPROVER_ID to resolve approver names: ... JOIN fnd_user fu ON sla.approver_id = fu.user_id.
• Join to SO_LINES_ALL on LINE_ID and SO_HEADERS_ALL on HEADER_ID to enrich with ordered item and customer context.
• Join to SO_ACTIONS on ACTION_ID and SO_RESULTS_B on RESULT_ID to classify the approval outcome for status dashboards.

Report consumers frequently aggregate on DATE_APPROVED and APPROVER_ID to measure approval throughput and bottleneck patterns.

Related Objects

The following objects are directly referenced through documented foreign keys and are the most significant dependencies:

• SO_HEADERS_ALL — joined via SO_LINE_APPROVALS.HEADER_ID; provides order-level context.
• SO_LINES_ALL — joined via SO_LINE_APPROVALS.LINE_ID; provides the approved line detail.
• FND_USER — joined via SO_LINE_APPROVALS.APPROVER_ID; resolves the approving user.
• SO_ACTIONS — joined via SO_LINE_APPROVALS.ACTION_ID; defines the action taken.
• SO_RESULTS_B — joined via SO_LINE_APPROVALS.RESULT_ID; supplies the result definition.

These five relationships constitute the complete documented FK footprint and should guide any integration, extract, or data-modeling effort involving SO_LINE_APPROVALS.