Results for “gmf_validate_account”

48 results




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

Overview

APPS.GMF_VALIDATE_ACCOUNT is a PL/SQL package that provides cross-validation services for Oracle Process Manufacturing (OPM) accounting flexfield combinations. Its central purpose is to validate the concatenated accounting unit and account segments against the OPM accounting flexfield definition, ensuring that any combination passed to the General Ledger is a valid, enabled account. The package header carries the version marker $Header: gmfactvb.pls 120.1 2006/07/11 19:30:08 rseshadr noship $, and the packaging was originally created under Bug 2468906 in June 2002, with a subsequent revision (Bug 5384550) that changed queries against FND_ID_FLEX_STRUCTURES to reference GL# explicitly.

In EBS 12.1.1 and 12.2.2 environments that include OPM modules, this package acts as the bridge between OPM accounting data and the standard FND key flexfield cross-validation engine. It belongs to the "OTHER" API classification in the ETRM repository, meaning it is not a formally published public API but is nonetheless a documented, dependency-bearing object referenced by two other packages.

Key Procedures and Functions

  • VALIDATE_SEGMENTS — The primary routine. It cross-validates the concatenated segments of the OPM accounting unit and account against the accounting flexfield structure. It accepts the company code, accounting unit ID, account ID, and their corresponding display numbers, and returns the resulting code combination identifier (CCID), the concatenated segment string, a status flag, and an error message. It supports an optional flag indicating whether a new combination should be created, and is designed to be called directly from the Subledger update program as well as from a wrapper in this package.
  • CROSS_VALIDATE — A wrapper routine that invokes the underlying FND cross-validation logic, applying the delimiter obtained from the flex structure definition rather than the policy master delimiter.
  • GET_ACCU_ACCT_IDS — Resolves the accounting unit and account identifiers used as inputs to validation.
  • GET_ACCT_NO — Retrieves the account number for a given account identifier.
  • GET_ACCTG_UNIT_NO — Retrieves the accounting unit number for a given accounting unit identifier.
  • GET_ERROR_MESSAGES — Returns the formatted error message associated with a failed validation attempt.

A private msg_log function and the CONC_PROGRAM constant ('C') support internal error logging and identify callers originating from concurrent programs.

Tables Accessed

  • GL_PLCY_MST — Source of the company code and the policy-level segment delimiter used when parsing concatenated segments.
  • GL_ACCU_MST — OPM accounting unit master, providing accounting unit IDs and numbers.
  • GL_ACCT_MST — OPM account master, providing account IDs and numbers.
  • FND_ID_FLEX_STRUCTURES — The key flexfield structure definition, queried with an explicit GL# reference to obtain the structure delimiter and cross-validation context.
  • FND_APPLICATION — Used to resolve the application context for the flexfield definitions.
  • GL_ACCU_MAP — Mapping between OPM accounting units and GL entities.
  • PLITBLM — The FND message/error table used by the message logging helper.

Notably, the source excerpt selects the delimiter from both the policy master and the flex structure because the two may differ; the policy delimiter is used to parse the concatenated string, while the flex structure delimiter is passed to the FND cross-validation routine.

Usage Notes

GMF_VALIDATE_ACCOUNT is typically invoked from the OPM Subledger update program during accounting generation, where each accounting unit/account combination must be validated before posting. It is also called through a wrapper procedure inside the same package and from custom extensions that require programmatic validation of OPM accounts. Because it writes only to FND message structures and returns status through OUT parameters rather than raising unhandled exceptions, it is suited to batch and concurrent processing contexts. The CONC_PROGRAM constant indicates awareness of concurrent-program callers. Custom code should always inspect the returned status and error message rather than assuming success, since invalid combinations will be reported through the output parameters.