Search Results get_segment_info

Overview

GMF_FND_SEGMENT_INFO is an Oracle Applications (APPS) PL/SQL package that belongs to the Oracle Process Manufacturing (OPM) family of modules, as indicated by the GMF prefix. Its documented purpose is to resolve accounting flexfield segment metadata for a given set of books and segment name within a defined effective date range. In Oracle EBS 12.1.1 and 12.2.2, the package is registered with the APPS schema and is declared with AUTHID CURRENT_USER, meaning that its unqualified references resolve against the privileges of the calling schema rather than the definer.

The package addresses a recurring requirement in OPM and Financials integration: determining the correct segment number and its associated status for a specific Accounting Key Flexfield (Accounting Flexfield / GL chart of accounts) structure. Because segment configurations can change over time, the API accepts a start date and end date so that the lookup is constrained to the effective configuration applicable on the relevant accounting date. This makes the routine useful for validating, translating, or defaulting cost account segment values in OPM transactions, inventory valuations, and cost rollups that must reconcile to the General Ledger.

Key Procedures and Functions

The documented package exposes a single procedure:

• GET_SEGMENT_INFO — Returns segment information for a specified set of books and segment name. The procedure accepts an effective start date and end date, the set of books name, and a segment name, and returns the resolved segment name, the segment number, and a status code. The segment name parameter is declared as an IN OUT NOCOPY parameter, allowing the caller to supply a name that the routine may resolve or normalize, while the segment number and status code are returned as OUT values. Callers use the status code to determine whether the lookup succeeded and whether the segment was enabled or otherwise available for the requested effective period.

The package specification header indicates a relatively stable code line (version 115.2, last shipped in 2002), which is consistent with the long-standing segment configuration model that has persisted across the 12.1.1 and 12.2.2 releases.

Tables Accessed

The package accesses a single documented table through APPS synonyms:

• FND_ID_FLEX_SEGMENTS — The standard Oracle Application Object Library (AOL) table that stores the definition of individual segments belonging to an ID flexfield structure. GET_SEGMENT_INFO reads this table to map a segment name to its segment number and to evaluate the segment's enabled or status state for the given set of books and effective date range.

No other tables are documented as referenced by this package, and it is not referenced by any other documented packages, indicating a narrow, utility-oriented scope.

Usage Notes

GMF_FND_SEGMENT_INFO is typically invoked from OPM cost and accounting logic that requires segment resolution against the Accounting Flexfield. It may be called from PL/SQL-based transaction processing, cost calculation routines, or custom extensions that need to translate a human-readable segment name into its numeric position for a specific set of books. Because the procedure takes explicit start and effective dates, callers should pass the accounting date of the transaction rather than the system date to obtain historically accurate segment metadata.

The AUTHID CURRENT_USER declaration requires that the invoking database user have the necessary privileges on FND_ID_FLEX_SEGMENTS; custom code that calls this package under a restricted schema should verify that synonym access and grants are in place. The presence of an IN OUT NOCOPY segment name parameter means custom wrappers should declare a local variable rather than passing a literal, ensuring that any normalization performed by the routine is captured by the caller. Given its age and stability, the package is considered a low-risk dependency, but its return values should always be checked against the status code before the segment number is used in downstream account generation. The search term "GLAD section FNZ" does not correspond to any documented element of this package; the documented functionality centers exclusively on Accounting Flexfield segment resolution.