Search Results gmf_ap_get_payment_methods

Overview

GMF_AP_GET_PAYMENT_METHODS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in ETRM as an "OTHER" API (no formal public API designation). It belongs to the Oracle Process Manufacturing (OPM) family of applications, indicated by the "GMF" prefix, and is specifically concerned with exposing Oracle Payables payment method information for use within OPM financial processing flows.

The package is declared with AUTHID CURRENT_USER, meaning its stored procedures execute with the privileges of the calling user rather than the defining user. This design choice is typical of utility packages that resolve object names dynamically, such as through APPS synonyms, at runtime under the invoker's security context. The package header carries an original version marker of 115.0 dated 1999, reflecting the long lineage of the OPM codebase and its continuity into EBS 12.1.1 and 12.2.2.

Business users do not invoke this package interactively. It exists to provide OPM-side logic with a controlled mechanism for retrieving payment method lookup codes and their descriptions, typically as part of a broader data extraction or synchronization process between OPM and Oracle Payables.

Key Procedures and Functions

ETRM documents a single procedure in this package:

• AP_GET_PAYMENT_METHODS — The sole documented entry point. It retrieves payment method lookup information, returning a lookup code and description alongside a status code, and uses an in-out row counter to support iterative, row-at-a-time fetching. Based on the package signature, the procedure accepts a start and end date, a payment method filter argument, and returns output parameters for the lookup code, description, row position, and status. Its name follows the OPM convention of prefixing the module context ("AP") before the action.

No other procedures or functions are registered for this package in the ETRM repository. The package exposes no reusable business logic beyond this single lookup routine, which is consistent with its narrow scope.

Tables Accessed

The ETRM record does not list any referenced tables accessed through APPS synonyms. No direct table dependencies are documented for this package, and it is referenced by zero other packages, confirming that it is a terminal utility rather than a shared library. In practice, a procedure of this name and signature would read Oracle Payables payment method definitions from the standard Payables lookup and payment method tables, but no such dependency is confirmed in the supplied metadata. Consultants performing impact analysis should treat the table access path as undocumented and verify it against the actual package body in the target instance rather than relying on the repository record.

Usage Notes

Because the package is classified as OTHER and has no dependent packages, it is not part of any documented call hierarchy in ETRM. It is most likely invoked from legacy OPM forms, concurrent programs, or custom extensions that need to present or process valid payment methods when integrating OPM transactions with Oracle Payables. The date range and row counter parameters suggest a reporting or batch extraction pattern rather than an online validation pattern, meaning callers iterate through result sets instead of performing single-value lookups.

Two cautions apply. First, the absence of APPS synonym table references means the runtime data sources must be confirmed in each environment. Second, since the package is not a formal API, Oracle support does not guarantee signature stability across releases; any custom code calling AP_GET_PAYMENT_METHODS should be reviewed when upgrading between 12.1.1 and 12.2.2. Developers extending this functionality should call it only for read-only retrieval and should not assume transactional behavior.