Results for “iby_instruct_source_apps”

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

Overview

IBY_INSTRUCT_SOURCE_APPS is a table in the IBY schema (Oracle Payments) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the list of source products, or calling applications, that submitted documents to be paid under each payment instruction. In the Oracle Payments data model, a payment instruction is the central object that groups payable documents from one or more source applications (for example, Payables, Receivables, Payroll, or other subledgers) so they can be processed through a single payment run. IBY_INSTRUCT_SOURCE_APPS records the many-to-many association between a payment instruction and the calling applications that contributed documents to it, allowing the payments engine to identify the originating products for a given instruction.

From a heuristic Data Vault classification mined from its foreign key structure, the table is satellite-leaning (with link characteristics). It carries two-part keys from both the payment instruction and the calling application, so it can also be viewed as an associative or link structure anchored to IBY_PAY_INSTRUCTIONS_ALL. This classification is a modeling suggestion only and should be treated as guidance rather than a strict architectural designation.

Key Information Stored

• PAYMENT_INSTRUCTION_ID — Foreign key to IBY_PAY_INSTRUCTIONS_ALL; identifies the payment instruction to which the source application contributed documents.
• CALLING_APP_ID — Identifier of the source product or application that submitted documents for payment under the instruction.
• CREATED_BY, CREATION_DATE — Standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns capturing the most recent modification of the row.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle EBS framework to detect concurrent updates.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update, supporting audit tracking.

The primary key is IBY_INSTRUCT_SOURCE_APPS_PK, defined on the composite of PAYMENT_INSTRUCTION_ID and CALLING_APP_ID. A corresponding unique index, IBY_INSTRUCT_SOURCE_APPS_U1, enforces this business-key pair, ensuring each calling application appears at most once per payment instruction. The documented table contains eight columns. The primary key is composite and consists of natural business identifiers rather than a single surrogate value.

Common Use Cases and Queries

The table is primarily used to determine which source applications participated in a given payment instruction, for reporting and reconciliation across subledgers. A typical query joins to IBY_PAY_INSTRUCTIONS_ALL by PAYMENT_INSTRUCTION_ID to list source applications for an instruction:

SELECT isa.PAYMENT_INSTRUCTION_ID, isa.CALLING_APP_ID
FROM   IBY.IBY_INSTRUCT_SOURCE_APPS isa
WHERE  isa.PAYMENT_INSTRUCTION_ID = :p_instruction_id;

Reverse lookups identify all payment instructions touched by a specific calling application:

SELECT isa.PAYMENT_INSTRUCTION_ID
FROM   IBY.IBY_INSTRUCT_SOURCE_APPS isa
WHERE  isa.CALLING_APP_ID = :p_app_id;

Because the table tracks the origin of documents within an instruction, it supports use cases such as counting instructions per source product, validating that expected applications are represented before payment processing, and auditing cross-application payment runs. Reporting against this table is common when reconciling payments across Payables, Receivables, and other subledgers that feed the Payments engine.

Related Objects

• IBY_PAY_INSTRUCTIONS_ALL — Parent table referenced by PAYMENT_INSTRUCTION_ID; holds the payment instruction header.
• IBY_PAY_INSTRUCTIONS_ALL_PK — Primary key constraint on the payment instructions table that anchors the foreign key relationship.
• IBY_DOCS_PAYABLE_ALL — Stores payable documents tied to instructions; complements the source-application view.
• IBY_PAY_SERVICE_REQUESTS — Tracks service requests generated during payment processing for an instruction.
• IBY_PAYMENTS_ALL — Holds payment records associated with instructions.
• IBY_INSTRUCT_SOURCE_APPS_PK and IBY_INSTRUCT_SOURCE_APPS_U1 — Key constraints and unique index enforcing the composite business key.

Joins from IBY_INSTRUCT_SOURCE_APPS should always proceed through PAYMENT_INSTRUCTION_ID to the instruction header to obtain context such as instruction status, payment method, and dates.