Results for “default_payment_method_code”

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

Overview

IBY_TEMP_EXT_PAYEES is a staging and interface table in the Oracle Payments (IBY) module of Oracle E-Business Suite, present and documented at both the 12.1.1 and 12.2.2 release levels. The table holds external payee records that are loaded into the Payments subsystem, typically from an external source system such as a feeder application, a third-party payroll provider, or an Oracle Payables batch import. Rows are transient by nature: they carry payment function, party, organization, and payment instruction attributes through a temporary staging population before they are validated and promoted into the permanent payee and payment instruction model.

Because the table exists to receive and stage externally sourced payee data, its design is firmly attribute-oriented rather than transactional. The heuristic Data Vault classification mined from its foreign-key structure is satellite-leaning. In modeling terms, it is best regarded as an attribute satellite attached to a party/payee hub-equivalent, since nearly all of its non-key columns describe the payee rather than assert relationships between separate business entities. The one relationship-bearing column, TEMP_EXT_PARTY_ID in the child table IBY_TEMP_PMT_INSTR_USES, is held on the dependent table rather than here.

Key Information Stored

The table is documented with 28 columns. The surrogate primary key is IBY_TEMP_EXT_PAYEES_PK, implemented on TEMP_EXT_PAYEE_ID, which uniquely identifies each staged payee row and is populated by the standard sequence mechanism. No separate unique business key is documented at the table level; the closest business-key candidates are the combination of PAYMENT_FUNCTION with PARTY_ID, PARTY_SITE_ID, ORG_TYPE, and ORG_ID, which together identify a paying organization/payee site context.

• TEMP_EXT_PAYEE_ID — surrogate primary key and the value referenced as a child key by IBY_TEMP_PMT_INSTR_USES.TEMP_EXT_PARTY_ID.
• PAYMENT_FUNCTION — the payment role context (for example, payee versus payer) for which the staged record applies.
• PARTY_ID, PARTY_SITE_ID — the trading party and party site the record describes; the primary business identifiers for the payee.
• ORG_TYPE, ORG_ID — the operating unit or organization context owning the payee record.
• SUPPLIER_SITE_ID — the supplier site association when the payee originates from the Payables supplier model.
• DEFAULT_PAYMENT_METHOD_CODE — foreign key to IBY_PAYMENT_METHODS_B; the default disbursement method for the payee.
• BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE, BANK_INSTRUCTION_DETAILS — foreign keys to IBY_BANK_INSTRUCTIONS_B plus free-form detail describing bank instruction sets to apply.
• DELIVERY_CHANNEL_CODE — foreign key to IBY_DELIVERY_CHANNELS_B; how payment advice is transmitted.
• PAYMENT_FORMAT_CODE — foreign key to IBY_FORMATS_B; the payment format associated with the payee.
• PAYMENT_REASON_CODE, PAYMENT_REASON_COMMENTS — foreign key to IBY_PAYMENT_REASONS_B plus commentary on the payment reason.
• PAYMENT_TEXT_MESSAGE1 through PAYMENT_TEXT_MESSAGE3 — remittance and instruction text carried onto the payment.
• ECE_TP_LOCATION_CODE — trading partner location code used for e-commerce/Automated Clearing House style remittance routing.
• EXCLUSIVE_PAYMENT_FLAG, INACTIVE_DATE — lifecycle controls indicating exclusivity of the payee’s payment instructions and the date the record ceases to apply.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, with the latter enforcing optimistic locking during concurrent interface processing.

Common Use Cases and Queries

The principal scenario is troubleshooting and validating an external payee load. A support or implementation query typically filters the staging table by organization and joins to the referenced setup tables to verify that valid payment methods and formats were assigned:

• Listing staged payees for an operating unit: SELECT TEMP_EXT_PAYEE_ID, PARTY_ID, PARTY_SITE_ID, DEFAULT_PAYMENT_METHOD_CODE, PAYMENT_FORMAT_CODE FROM IBY_TEMP_EXT_PAYEES WHERE ORG_TYPE = :org_type AND ORG_ID = :org_id.
• Detecting incomplete or stale records via the audit and lifecycle columns: filter on INACTIVE_DATE IS NULL together with LAST_UPDATE_DATE ranges to isolate rows still pending promotion.
• Reporting which payment instructions are attached to a staged payee, by joining to IBY_TEMP_PMT_INSTR_USES on TEMP_EXT_PARTY_ID = TEMP_EXT_PAYEE_ID.
• Validating setup references by outer-joining IBY_PAYMENT_METHODS_B, IBY_FORMATS_B, IBY_DELIVERY_CHANNELS_B, and IBY_BANK_INSTRUCTIONS_B to identify codes that do not resolve.
• Reconciling a batch interface load by counting PARTY_ID distinct values and comparing against the expected incoming population.

Because these rows are staged prior to promotion, reporting against the table reflects in-flight interface data rather than settled, permanent payee configuration.

Related Objects

The table participates in a well-defined foreign-key neighborhood within the IBY schema:

• IBY_TEMP_PMT_INSTR_USES — the dependent child table, joined via TEMP_EXT_PARTY_ID to TEMP_EXT_PAYEE_ID, holding the payment instruction usage rows associated with each staged external payee.
• IBY_PAYMENT_METHODS_B — resolved from DEFAULT_PAYMENT_METHOD_CODE; supplies the valid payment method names.
• IBY_FORMATS_B — resolved from PAYMENT_FORMAT_CODE; supplies payment format definitions.
• IBY_DELIVERY_CHANNELS_B — resolved from DELIVERY_CHANNEL_CODE; supplies advice delivery channel definitions.
• IBY_BANK_INSTRUCTIONS_B — referenced twice, from BANK_INSTRUCTION1_CODE and BANK_INSTRUCTION2_CODE; supplies bank instruction set definitions.
• IBY_PAYMENT_REASONS_B — resolved from PAYMENT_REASON_CODE; supplies payment reason definitions.

These relationships confirm the table’s role as a staging satellite whose references are exclusively to Payments setup entities, and whose own dependent data is held in IBY_TEMP_PMT_INSTR_USES.