Search Results ppr_sec_term_allowed

Overview

IBY_FD_USER_API_PUB is a public PL/SQL API package in the APPS schema that supports the Funds Disbursement (IBY) module of Oracle E-Business Suite. Its role is to expose validation, enablement, and authorisation logic for payment instructions and payment methods to user-facing interfaces such as the Disbursement Instruction UI and payment processing utilities. The package is classified as a PUB (public) API, indicating it is intended for external invocation and is not restricted to internal use.

Rather than creating or executing payments, IBY_FD_USER_API_PUB provides the decision-support layer that determines whether a given payment instruction, method, or profile is valid, complete, or eligible for a specific action. Interactive forms and other modules call these routines to render buttons, raise errors, and enforce business rules before a disbursement record is committed. The package is VALID in both 12.1.1 and 12.2.2, and depends on the standard FND_API and SYS.STANDARD packages.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, all concerned with validating or gating payment instruction activity:

• VALIDATE_METHOD_AND_PROFILE — Confirms that a payment method and payment profile combination is consistent and usable.
• PAYMENT_INSTRUCTION_ACTION — Performs the action logic associated with a payment instruction, applying the appropriate business rules.
• PMT_INSTR_TERMINATE_ENABLED — Indicates whether a payment instruction may be terminated.
• INSTR_SEC_TERMINATE_ENABLED — Determines whether termination is permitted at the instruction section level.
• PMT_INSTR_ACTION_ENABLED — Signals whether an action can be performed against a payment instruction.
• RETRIEVE_DEFAULT_SRA_FORMAT — Returns the default remittance advice (SRA) format for the applicable setup.
• IS_PMT_INSTR_COMPLETE — Tests whether a payment instruction has been fully completed.
• PMT_INSTR_TERMINATE_ALLOWED — Confirms termination is allowed under current conditions.
• PMT_INSTR_SEC_TERM_ALLOWED — Confirms section-level termination is allowed.
• PPR_SEC_TERM_ALLOWED — Confirms termination is allowed for a payment process request section.
• IS_TRANSMITTED_PMT_INST_COMPL — Determines whether a transmitted payment instruction is complete.

Together these routines form the enablement and validation checks that dictate the availability of termination and action options to the user.

Tables Accessed

The package reads and validates against several IBY tables through APPS synonyms:

• IBY_APPLICABLE_PMT_MTHDS and IBY_APPLICABLE_PMT_PROFS — supply the permitted payment methods and payment profiles used by VALIDATE_METHOD_AND_PROFILE.
• IBY_PAYMENTS_ALL — the disbursement payment records examined for instruction status and completeness.
• IBY_PAY_INSTRUCTIONS_ALL — the payment instruction header and section data used by the termination and completion checks.
• IBY_REMIT_ADVICE_SETUP — the remittance advice configuration used by RETRIEVE_DEFAULT_SRA_FORMAT.
• DUAL and PLITBLM — auxiliary references used within the PL/SQL logic.

Usage Notes

IBY_FD_USER_API_PUB is typically invoked by the Disbursement Instruction user interface and by surrounding infrastructure packages. ETRM metadata shows it is referenced by AP_PAYMENT_UTIL_PKG, IBY_DISBURSE_UI_API_PUB_PKG, IBY_UTILITY_PVT, and by itself. Custom code that needs to mimic the standard termination or action enablement behaviour should call these routines rather than reimplementing the rules, ensuring consistency with funds disbursement processing. Because it is a PUB API, it is a supported integration point, though callers should treat the underlying tables as read sources and avoid direct DML.