Results for “iby_pay_instructions_sec_v”

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

Overview

IBY_PAY_INSTRUCTIONS_SEC_V is a security-constrained view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IBY (Payments) product family. It presents payment instruction records — the grouping construct under which one or more payment documents are transmitted, acknowledged, and reconciled with a payment system — while applying Oracle EBS row-level access control. Unlike IBY_PAY_INSTRUCTIONS_ALL, which exposes the complete set of instruction rows, this view filters results according to the operating unit, legal entity, and payment function privileges available to the running session. It is therefore the appropriate access point for custom reports, OAF pages, and integration extracts that must respect the same data security rules enforced by the standard Payments workbench.

The view has been a standard component across both release 12.1.1 and 12.2.2, and the column list is materially identical in each. The object name and the embedded definition confirm it is layered directly over the instruction entity and is intended for read access; inserts, updates, and deletes must be issued against IBY_PAY_INSTRUCTIONS_ALL.

Underlying Base Objects

The view selects its columns from IBY_PAY_INSTRUCTIONS_ALL (referenced through a synonym in the APPS schema) and joins or filters against the following documented objects:

• IBY_USER_PAY_FUNS_SEC_V — the user-to-payment-function security view, restricting rows to functions assigned to the current user.
• IBY_PROCESS_ORGS and IBY_PROCESS_FUNCTIONS — define which operating units and payment functions a given instruction belongs to.
• MO_GLOBAL — provides multi-org (operating unit) context for the session.
• FND_GLOBAL, FND_PROFILE, and FND_ACCESS_CONTROL_UTIL — supply user identity, responsibility profile values, and access-control utilities.
• XTR_USER_ACCESS and CE_SECURITY_PROFILES_V — supplement bank account and treasury-level security filtering.

The dependency on MO_GLOBAL and FND_GLOBAL means the view must be queried from a context in which an application session is initialized; direct SQL without a valid FND_GLOBAL session will fail or return no rows.

Key Columns

Among the columns returned, several are of primary importance when auditing or reporting payment instructions:

• PAYMENT_INSTRUCTION_ID — primary key identifying the instruction header.
• PAYMENT_INSTRUCTION_STATUS and PAYMENTS_COMPLETE_CODE — track the lifecycle state of the instruction and whether all its payments have completed.
• BILL_PAYABLE_FLAG — the column most frequently referenced in user searches. It indicates whether the instruction is eligible for bill payable processing, distinguishing instructions destined for a bill payable workflow from those settled directly.
• PAYMENT_DATE, TRANSMISSION_DATE, and ACKNOWLEDGEMENT_DATE — support settlement timing and reconciliation analysis.
• PAYMENT_CURRENCY_CODE, INTERNAL_BANK_ACCOUNT_ID, PAYMENT_PROFILE_ID, and LEGAL_ENTITY_ID — support cross-currency and account-level reporting.
• PAY_ADMIN_ASSIGNED_REF_CODE and BANK_ASSIGNED_REF_CODE — reconcile internal and bank-assigned references.
• ORG_ID and ORG_TYPE — identify the owning operating unit and organisation context.
• POSITIVE_PAY_FILE_CREATED_FLAG, REGULATORY_REPORT_CREATED_FLAG, and REMITTANCE_ADVICE_CREATED_FLAG — indicate downstream file generation status.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the DFF/context columns available for custom extensions.

Common Use Cases and Queries

The view is frequently used to build payment reconciliation extracts and to answer questions about which instructions are bill payable. A representative query retrieving bill payable instructions for the current user's accessible organisations:

SELECT payment_instruction_id, payment_instruction_status, bill_payable_flag, payment_date, payment_currency_code FROM iby_pay_instructions_sec_v WHERE bill_payable_flag = 'Y' AND payment_date BETWEEN :p_start AND :p_end;

To summarise instructions by legal entity and status:

SELECT legal_entity_id, payment_instruction_status, COUNT(*) FROM iby_pay_instructions_sec_v GROUP BY legal_entity_id, payment_instruction_status;

To isolate instructions awaiting acknowledgement or positive pay file creation:

SELECT payment_instruction_id, transmission_date, acknowledgement_date FROM iby_pay_instructions_sec_v WHERE acknowledgement_date IS NULL AND positive_pay_file_created_flag = 'N';

Because the view applies security predicates internally, no additional organisation filter is required when invoked from an initialized EBS session; adding an explicit ORG_ID clause is still recommended for performance on large data volumes. In direct database integration scenarios, the session context must be established prior to querying.