Results for “temp_ext_party_id”

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

Overview

IBY_TEMP_PMT_INSTR_USES is a temporary staging table residing in the IBY (Payments) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It holds working copies of payment instrument usage records associated with temporary external payees during payment processing. The table supports the construction and validation of instrument selection data — that is, the mapping of a payee to the specific payment instruments (for example, bank accounts, payment cards, or other disbursement instruments) that may be applied to fund a payment — before those records are committed to the permanent payee and instrument tables.

Because Oracle Payments builds payment instruction data through a series of temporary and permanent staging areas, IBY_TEMP_PMT_INSTR_USES occupies the transient layer of that pipeline. Records are written and consumed within a processing run and are not intended to persist as an authoritative source of instrument history. Its presence in the data model is functionally transactional rather than reference-oriented.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is satellite-leaning. The single documented foreign key targets IBY_TEMP_EXT_PAYEES, which suggests the table carries descriptive and attribute-like context about a parent temporary entity rather than serving as a central hub or a many-to-many link resolver. This classification is a modeling suggestion only; the table is a staging construct and would typically be treated as transient rather than modeled as a durable Data Vault satellite.

Key Information Stored

The documented physical schema comprises fifteen columns. The most operationally significant are:

• TEMP_EXT_PARTY_ID — the foreign key referencing IBY_TEMP_EXT_PAYEES; ties each instrument usage row to its temporary external payee record.
• EXT_PARTY_ID — the corresponding permanent external party identifier, allowing reconciliation between staging and production payee data.
• TEMP_INSTRUMENT_ID — identifier of the temporary payment instrument to which the usage applies.
• INSTRUMENT_TYPE — the category of instrument (for example, bank account or card).
• PAYMENT_FUNCTION — the function the instrument serves, such as supplier payment or refund.
• ORDER_OF_PREFERENCE — priority ranking that governs which instrument is selected first.
• STATUS — lifecycle state of the usage record during processing.
• START_DATE / END_DATE — effective dating for the instrument usage assignment.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who created and last modified each row.

The metadata does not document a named surrogate primary key or unique business key index for this table. In practice, staging tables in the IBY module typically rely on internal sequence-generated identifiers or composite business columns, but no explicit constraint detail is provided in the ETRM excerpt.

Common Use Cases and Queries

The principal use case is diagnostic: tracing how an instrument was selected, ranked, and applied for a temporary payee during a payment run. A typical reconciliation query joins the staging table to its parent payee staging table:

• Select instrument usage rows for a given temporary payee: SELECT u.temp_instrument_id, u.instrument_type, u.order_of_preference, u.status FROM iby_temp_pmt_instr_uses u WHERE u.temp_ext_party_id = :party_id;
• Compare temporary versus permanent party linkage by selecting TEMP_EXT_PARTY_ID and EXT_PARTY_ID together to identify unresolved staging rows.
• Review preference ordering and effective-date ranges to confirm that the expected instrument was selected ahead of alternatives.
• Audit stale staging records by filtering on STATUS and the CREATION_DATE / LAST_UPDATE_DATE audit columns for rows left behind after a failed payment process.

Because the table is staging-only, reporting should generally target permanent instrument tables once records are promoted; queries against this table are best scoped to active or recently completed processing windows.

Related Objects

The most significant related object documented is the parent of its foreign key:

• IBY_TEMP_EXT_PAYEES — joined via IBY_TEMP_PMT_INSTR_USES.TEMP_EXT_PARTY_ID = IBY_TEMP_EXT_PAYEES.TEMP_EXT_PARTY_ID; the governing temporary payee entity.

Beyond the documented relationship, the table interacts conceptually with the permanent external payee tables (IBY_EXTERNAL_PAYEES) and the permanent payment instrument tables in the IBY schema, which receive promoted rows. The Oracle Payments setup and processing logic that governs instrument selection and preference ordering also references this staging structure during payment instruction creation.