Results for “d_access”

4 results




Overview
Explore in AI Chat

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

Overview

The APPS.IBY_FD_USER_API_PUB package body is the public API layer for Funds Disbursement user-level processing within Oracle Payments (IBY) in Oracle E-Business Suite 12.1.1 and 12.2.2. It supplies the business logic that validates payment methods against applicable payment method drivers and payment profiles, evaluates the completeness and transmission state of payment instructions, and determines whether payment instructions, instruction sections, and payment process requests may be terminated or acted upon. The package header IBY_FD_USER_API_PUB is classified as a public (PUB) API, meaning its procedures are supported for invocation by external consumers such as Oracle Payables, Oracle Receivables, and custom extensions. Because it is referenced by three other packages, it functions as a shared utility for instruction lifecycle decisions rather than as an end-user entry point.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. Their names describe their contractual purpose; parameter lists are intentionally omitted here.

  • VALIDATE_METHOD_AND_PROFILE — Validates that a given payment method code and payment profile are applicable for a specified driver type and driver value, using internal cursors over the applicable payment methods and profiles tables. It returns the standard EBS API return status, message count, and message data.
  • PAYMENT_INSTRUCTION_ACTION — Performs a state-changing action on a payment instruction, such as submission or cancellation, subject to the package's validation rules.
  • PMT_INSTR_TERMINATE_ENABLED — Indicates whether termination is currently permitted for a payment instruction.
  • INSTR_SEC_TERMINATE_ENABLED — Indicates whether termination is permitted for a payment instruction section.
  • PMT_INSTR_ACTION_ENABLED — Reports whether an action may be performed against a payment instruction given its present status.
  • RETRIEVE_DEFAULT_SRA_FORMAT — Returns the default remittance advice format configured in the remittance advice setup, used when generating remittance advice output.
  • IS_PMT_INSTR_COMPLETE — Determines whether a payment instruction has reached a complete state, supporting downstream processing gates.
  • PMT_INSTR_TERMINATE_ALLOWED — Evaluates the conditions under which a payment instruction may be terminated, complementing the corresponding ENABLED indicator.
  • PMT_INSTR_SEC_TERM_ALLOWED — Evaluates whether a payment instruction section satisfies the conditions for termination.
  • PPR_SEC_TERM_ALLOWED — Evaluates whether a payment process request section satisfies the conditions for termination.
  • IS_TRANSMITTED_PMT_INST_COMPL — Determines whether a transmitted payment instruction is complete, guarding against modification of instructions already sent to the payment system.

Tables Accessed

The package operates against several IBY tables through APPS synonyms. IBY_APPLICABLE_PMT_MTHDS and IBY_APPLICABLE_PMT_PROFS provide the applicability rules consulted by VALIDATE_METHOD_AND_PROFILE and the termination and action checks. IBY_PAY_INSTRUCTIONS_ALL stores the payment instruction records whose state, completeness, and transmission status the package evaluates. IBY_PAYMENTS_ALL holds the underlying payment records, including transmission information. IBY_REMIT_ADVICE_SETUP supplies the remittance advice configuration used by RETRIEVE_DEFAULT_SRA_FORMAT. DUAL and PLITBLM are referenced for scalar evaluation and PL/SQL table manipulation respectively.

Usage Notes

In practice, IBY_FD_USER_API_PUB is invoked by Oracle Payments forms and concurrent programs — particularly the Funds Disbursement and payment instruction management flows — and by the three packages that reference it. Custom code intended to build or extend payment instruction processing should call these public procedures rather than manipulating the underlying tables directly, and should honor the returned return status, message count, and message data. Where a caller encounters the string "creation_error," it originates from the calling application's error handling rather than from this package body itself; nonetheless, failures returned by VALIDATE_METHOD_AND_PROFILE or PAYMENT_INSTRUCTION_ACTION are common upstream contributors and should be diagnosed by inspecting the message stack associated with the API response.