Results for “partner_transaction_id”

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

Overview

AS_TRANSFER_DETAILS is a table owned by the OSM schema within the Oracle E-Business Suite Sales Foundation (AS) product family. Its documented purpose is to support lead sharing functionality, where sales leads are distributed or transferred between sales representatives, organizations, or partner entities. The table operates as a dependent detail structure: while it is classified heuristically as a standalone object within the Data Vault model, its foreign key relationship to AS_TRANSFER_QUES suggests that, from a modeling perspective, it behaves more like a link-satellite hybrid — a child structure whose rows exist only in the context of a parent transfer transaction. This classification should be treated as a modeling suggestion rather than a normative definition.

Key Information Stored

The documented physical schema for release 12.2.2 contains five columns:

• PARTNER_TRANSACTION_DETAIL_ID — The surrogate primary key of the table, enforced by the AS_TRANSFER_DETAILS_PK constraint and backed by the unique index AS_TRANSFER_DETAILS_U1. Because the unique index and the primary key target the same column, this column is the only documented business-key candidate in the schema.
• PARTNER_TRANSACTION_ID — The foreign key linking each detail row to its parent record in AS_TRANSFER_QUES. This is the join column that binds the detail set to the governing transfer transaction.
• COLUMN_NAME — Identifies the attribute, field, or target element being recorded for the transfer line, enabling a generic name/value pairing model.
• COLUMN_VALUE — Stores the actual value associated with the named column, allowing the table to capture flexible, attribute-style metadata per transfer detail.
• GROUP_ID — Groups related detail rows together, supporting the segmentation of detail records within a single partner transaction.

The name/value structure (COLUMN_NAME plus COLUMN_VALUE) indicates the table is used as a flexible extension store rather than a fixed-attribute entity, allowing lead-sharing logic to record variable characteristics without schema changes.

Common Use Cases and Queries

Typical scenarios include auditing how a lead was shared, resolving which values were applied to a transfer, and reporting on detail attributes grouped by transfer. A straightforward detail lookup by parent transaction follows standard pattern:

• Retrieve all detail rows for a transaction: SELECT PARTNER_TRANSACTION_DETAIL_ID, COLUMN_NAME, COLUMN_VALUE, GROUP_ID FROM OSM.AS_TRANSFER_DETAILS WHERE PARTNER_TRANSACTION_ID = :transaction_id;
• Pivot a transfer's attributes: grouping by COLUMN_NAME within a GROUP_ID produces a sideways view of the detail values.
• Join to the parent to obtain full transfer context: SELECT d.COLUMN_NAME, d.COLUMN_VALUE FROM OSM.AS_TRANSFER_DETAILS d, OSM.AS_TRANSFER_QUES q WHERE d.PARTNER_TRANSACTION_ID = q.PARTNER_TRANSACTION_ID;
• Reconciliation and validation queries verify that each detail row is anchored to a valid transaction and that GROUP_ID values are internally consistent.

Related Objects

The documented relationship set is narrow, centered on the parent transfer entity:

• AS_TRANSFER_QUES — The parent table referenced via PARTNER_TRANSACTION_ID. Every detail row must resolve to a transaction in this table, making it the primary join partner for transfer detail queries.
• AS_TRANSFER_DETAILS_PK and AS_TRANSFER_DETAILS_U1 — The primary key constraint and unique index on PARTNER_TRANSACTION_DETAIL_ID that enforce row identity.

No additional foreign keys or dependent objects are documented in the ETRM metadata for this table. Because the schema is compact and oriented toward name/value capture, integrators working with lead sharing should treat AS_TRANSFER_QUES as the controlling header and AS_TRANSFER_DETAILS as its attribute child.