Search Results get_base_org_id




Overview
Explore in AI Chat

Overview

APPS.GCS_UTILITY_PKG is a shared PL/SQL utility package in Oracle E-Business Suite that provides the consolidated data-access and caching layer for the ETRM (Enterprise Tax, Risk, and Management) consolidation engine, internally known as GCS. In EBS 12.1.1 and 12.2.2, the package serves as the central source of truth for GCS dimensionality metadata: it loads and caches dimension definitions, dimension attributes, attribute versions, calendar period details, conversion rates, and organization context that the consolidation programs require before they can build, validate, or translate financial data. The package is classified as an OTHER API and is not an end-user interface; it is infrastructure code consumed by other GCS packages and by the consolidation application logic.

Global constants declared in the package expose the standard GCS return codes (g_ret_sts_success, g_ret_sts_error, g_ret_sts_unexp_error, g_ret_sts_warn) and logging conventions (g_module_enter, g_module_success, g_module_failure, g_nl). Two global associative arrays—g_dimension_attr_info and g_gcs_dimension_info—act as in-memory caches so that dimension and attribute definitions are resolved once per session rather than repeatedly queried.

Key Procedures and Functions

  • INIT_DIMENSION_ATTR_INFO — Populates the global dimension-attribute cache (g_dimension_attr_info) from the FEM dimension and dimension-attribute tables.
  • INIT_DIMENSION_INFO — Populates the global dimensionality cache (g_gcs_dimension_info), including column names, associated and detail value sets, and required-for-GCS/FEM flags.
  • GET_DIMENSION_ATTRIBUTE — The accessor most directly associated with the searched term. It returns the cached attribute information for a given dimension, resolving the record defined by r_dimension_attr_info.
  • GET_DIMENSION_REQUIRED — Indicates whether a dimension is required for GCS processing.
  • GET_FEM_DIM_REQUIRED — Indicates whether a dimension is required for FEM processing.
  • GET_HRATE_DIM_REQUIRED — Indicates whether a dimension is required for historical-rate processing (bugfix 5707630 added historical-rate dimensionality handling).
  • GET_DEFAULT_VALUE — Returns the configured default value for a dimension.
  • GET_ASSOCIATED_VALUE_SET_ID — Returns the value set associated with a dimension.
  • GET_CAL_PERIOD_DETAILS — Retrieves calendar period attributes for a period.
  • GET_CONVERSION_RATE — Retrieves the applicable conversion rate for GCS translation.
  • GET_ENTRY_HEADER — Returns entity header information.
  • GET_ORG_ID and GET_BASE_ORG_ID — Return the current operating unit identifier and the base organization identifier, respectively.
  • POPULATE_CALENDAR_MAP_DETAILS — Builds calendar mapping detail rows used by the consolidation calendar logic.

Tables Accessed

All underlying objects are referenced through APPS synonyms. Dimension definition and attribute metadata is read from FEM_DIMENSIONS_B, FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_VERSIONS_B, FEM_DIMENSION_GRPS_B, FEM_TAB_COLUMNS_B, and FEM_TAB_COLUMN_PROP. Value-set and exclusion configuration is read from FEM_VALUE_SETS_B, FEM_GLOBAL_VS_COMBO_DEFS, FEM_APP_GRP_COL_EXCLSNS, and FEM_APP_GRP_DIM_EXCLSNS. Entity and time information is sourced from FEM_ENTITIES_TL, FEM_ENTITIES_ATTR, FEM_TIME_GRP_TYPES_ATTR, FEM_CAL_PERIODS_B, and FEM_CAL_PERIODS_ATTR. The package is predominantly read-oriented; it materializes cached values into PL/SQL collections rather than persisting state back to these tables.

Usage Notes

GCS_UTILITY_PKG is invoked internally by GCS consolidation programs and is referenced by 47 other packages, making it one of the more widely depended-upon utilities in the ETRM schema. Callers typically execute INIT_DIMENSION_INFO and INIT_DIMENSION_ATTR_INFO once at session or program start, then use the GET_* accessors throughout processing. Because the caches are package-level globals, a session must not assume cached dimensionality reflects changes committed by other sessions after initialization. Custom code extending GCS should use these accessors rather than querying the FEM tables directly, ensuring consistent handling of the required-for-GCS, required-for-FEM, and required-for-historical-rate flags.