Results for “territory_code”

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

Overview

IBY_BANK_INSTRUCTIONS_B is the base (non-translated) table in the Oracle Payments (IBY) module that stores bank instruction codes used as lookup values for payment process profiles and external payee setup. It corresponds to the Bank Instruction Codes page in the Oracle E-Business Suite user interface, and it functions as a supplemental attribute of the payment instruction model rather than as a transactional record. Bank instruction codes describe the format or convention by which a payment is to be transmitted to a supplier or payee — for example, standardized remittance-delivery conventions used in certain regions.

From a modeling perspective, the ETRM heuristic classifies this object as hub-leaning. This is a suggestion rather than a prescription: the table carries a single-column primary key on BANK_INSTRUCTION_CODE and only one outbound foreign key, to FND_TERRITORIES, which is the pattern of an independent reference entity. The absence of outbound foreign keys to transaction-level tables reinforces the hub interpretation, since all cross-table references to this object originate from dependent tables.

Key Information Stored

ETRM 12.2.2 documents twelve columns for this table. The most significant are:

• BANK_INSTRUCTION_CODE — the primary key (IBY_BANK_INSTRUCTIONS_B_PK) and the business identifier of the instruction. This is also the first column of the unique index.
• TERRITORY_CODE — the outbound foreign key to FND_TERRITORIES, indicating the country or territory to which the instruction applies; this scopes instruction codes geographically.
• FORMAT_VALUE — the format value associated with the instruction, used when applying the code to a payment.
• SEEDED_FLAG — indicates whether the row was delivered as Oracle seed data versus user-created.
• INACTIVE_DATE — the date from which the instruction code ceases to be selectable.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• ZD_EDITION_NAME — the editioning column (the second column of the unique index IBY_BANK_INSTRUCTIONS_B_U1) supporting online patching in 12.2.

The four standard WHO audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE — plus LAST_UPDATE_LOGIN complete the column list. The surrogate key is thus BANK_INSTRUCTION_CODE, which is simultaneously the business key, qualified by ZD_EDITION_NAME in the unique index.

Common Use Cases and Queries

Typical uses include validating that a bank instruction assigned to a payee or profile is still active, and driving Lists of Values for the Bank Instruction Codes setup page. A representative query joining to a dependent payee table is:

SELECT bi.bank_instruction_code, bi.territory_code, bi.format_value
FROM   iby_bank_instructions_b bi, iby_external_payees_all ep
WHERE  ep.bank_instruction1_code = bi.bank_instruction_code
AND    bi.inactive_date IS NULL;

For reporting on lookup contents scoped by territory, IBY_BANK_INSTRUCTIONS_B can be joined to FND_TERRITORIES on TERRITORY_CODE. To detect payees configured with retired instructions, filter on INACTIVE_DATE while joining IBY_EXTERNAL_PAYEES_ALL or IBY_TEMP_EXT_PAYEES through BANK_INSTRUCTION1_CODE and BANK_INSTRUCTION2_CODE.

Related Objects

• IBY_BANK_INSTRUCTIONS_TL — the translation table, related one-to-many on BANK_INSTRUCTION_CODE.
• FND_TERRITORIES — referenced by IBY_BANK_INSTRUCTIONS_B.TERRITORY_CODE.
• IBY_EXTERNAL_PAYEES_ALL — references this table via BANK_INSTRUCTION1_CODE and BANK_INSTRUCTION2_CODE.
• IBY_PAYMENTS_H — the payment history table, which carries both instruction code columns.
• IBY_SYS_PMT_PROFILES_B — the system payment profile table, also carrying both instruction code columns.
• IBY_TEMP_EXT_PAYEES — the temporary external payee staging table, referencing BANK_INSTRUCTION1_CODE and BANK_INSTRUCTION2_CODE.

The breadth of these references confirms the table's role as a shared reference hub for payment configuration and payee data across the IBY schema.