Results for “psa_gvtmb”

18 results




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

Overview

PSA_GVTMB is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its name follows the PSA module prefix associated with Oracle Public Sector Applications, and the "GVT" component suggests a government-oriented utility. The package is classified in the ETRM repository as an OTHER API, meaning it is not exposed as a public, supported integration interface but rather serves as an internal worker routine within the PSA product family. It is not a declarative API in the sense of a create/update entity handler; instead it functions as a procedural driver whose single documented entry point, MAIN, is designed to be scheduled or called from a hosting construct such as a concurrent program.

The header comment identifies the source file as psagvtms.pls, version 120.0.12010000.2, last revised in May 2009. The package is declared with AUTHID CURRENT_USER, the prevailing convention in EBS for packages that must execute with the privileges of the invoking session and resolve unqualified object references through the APPS synonym layer.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure:

  • MAIN — The sole entry point of the package. It conforms to the standard concurrent program signature, returning error buffer and return code values to the concurrent manager. Its purpose is to orchestrate the package's work: reading configuration and metadata from the FND data dictionary and lookup tables, applying the package's government-specific logic, and reporting completion status back through the standard OUT parameters.

No other procedures or functions are exposed or documented. The metadata does not publish a parameter list beyond the standard concurrent program interface, and no parameter details should be assumed beyond those two OUT parameters.

Tables Accessed

All table access occurs through APPS synonyms and involves Oracle Application Object Library (FND) metadata tables rather than transactional PSA business tables. This pattern indicates a configuration-driven or introspection-driven process:

  • FND_APPLICATION — Resolves application identifiers and short names, typically to scope the process to a specific product or to validate installation context.
  • FND_PRODUCT_INSTALLATIONS — Confirms which products and schemas are installed, so the routine can tailor its behavior to the actual deployment.
  • FND_TABLES and FND_COLUMNS — Provide table and column metadata, consistent with a routine that discovers or validates database objects at runtime.
  • FND_FLEX_VALUE_SETS — Supplies key flexfield and value set definitions, used to interpret or validate coded values.
  • FND_LOOKUP_VALUES — Delivers lookup codes and meanings for translating and validating reference data.

Because all six are FND repository tables, PSA_GVTMB is best characterized as a metadata and configuration utility rather than a transactional processor. The metadata does not document any inserts, updates, or deletes.

Usage Notes

PSA_GVTMB is not referenced by any other documented package, indicating that it sits at the top of its own call tree rather than being embedded in a broader API chain. Its MAIN procedure follows the concurrent program contract (error buffer, return code), so the routine is most plausibly registered as a concurrent program executable and submitted from a responsibility menu or a request set.

It may also be invoked directly from SQL*Plus or from custom PL/SQL, binding the two OUT parameters to local variables and checking the return code. Because the package is classified as OTHER rather than a public API, it should be treated as internal to Oracle's PSA implementation; customizations that call it directly may be affected by patching. Both 12.1.1 and 12.2.2 retain the same package specification and FND dependency set.