Search Results submission_failed
Overview
The APPS.GCS_CREATE_LEVELS_PKG package body is a component of the Oracle E-Business Suite Consolidation and Hierarchy Management infrastructure (GCS module). Its primary business function is the creation and registration of hierarchy levels within the Enterprise Performance Foundation / dimensional hierarchy model. A "level" in this context represents a named position within a dimensional hierarchy (for example, a consolidation level along the User_Dim or another dimension), which downstream consolidation, reporting, and analysis processes rely upon to organize parent-child relationships across members.
The package header identifies a single public entry point, GCS_CREATE_LEVEL, which performs the orchestration required to materialize a level definition: resolving the dimension, resolving or creating the associated value set, determining the hierarchy depth and sequence position, and validating the parent member from which the level is derived. The package uses the FND_LOG diagnostic framework (statement, procedure, exception, error, and unexpected levels) so that execution can be traced when the profile option FND: Debug Log Enabled is active. The embedded $Header tag (gcslevelb.pls 120.2 2005/09/15) indicates a stable, legacy code line that has not required functional revision since the mid-2000s, consistent with its role as a low-level hierarchy utility.
Key Procedures and Functions
- GCS_CREATE_LEVEL — The sole documented procedure in the package body. It is the public API for creating a single hierarchy level. Its IN/OUT signature follows the standard concurrent-program convention (an
errbufandretcodepair), and it returns a flag (p_level_exists) indicating whether the requested level already existed before invocation. Inputs describe the sequence number, dimension, hierarchy name, and analysis flag that together uniquely identify the level to be created. Internally the procedure declares exception types such asSUBMISSION_FAILED,REQUEST_ERROR, andNO_VALUE_SET_FOUND, and it uses a cursor (get_parent) to resolve the child display code where the parent and child display codes coincide at the specified sequence number.
No additional documented functions or procedures are exposed by this package body.
Tables Accessed
The package reads and writes the following application tables through their APPS synonyms:
- FEM_DIMENSIONS_B — resolves the dimensional metadata and dimension identifier used to anchor the level.
- FEM_DIMENSION_GRPS_B_T and FEM_DIMENSION_GRPS_TL_T — the base and translated tables for dimension group definitions; used to relate the level to its owning dimension group.
- FEM_HIER_DIM_GRPS_T — associates hierarchies with dimension groups, supporting hierarchy-name resolution.
- GCS_EPB_LEVELS_GT — the global temporary staging table where level definitions are assembled before being persisted.
- GCS_HIER_MEMBERS_T — the persisted hierarchy membership table; the
get_parentcursor selects from here to identify the parent/child display code for the requested sequence number.
Usage Notes
Because GCS_CREATE_LEVEL accepts the concurrent-manager errbuf/retcode interface, it is most commonly invoked from an Oracle EBS concurrent program or from the GCS hierarchy setup forms that create and maintain dimensional levels. The procedure is not referenced by any other documented package (referenced-by count of zero), which indicates it is an entry-point API rather than a shared utility. Practically, it is called when a user or process defines a new level against a dimension hierarchy — for example, establishing consolidation levels on the User_Dim dimension that a user searched for. When invoked, callers should supply a valid dimension, hierarchy name, analysis flag, and sequence number; the procedure sets p_level_exists if a matching level is already present, allowing the caller to treat the call idempotently. Debug output is emitted through FND_LOG at the level governed by the runtime log setting, making it straightforward to diagnose value-set or submission failures in a development or test environment.
-
Lookup Type: AHL_OSP_LINE_STATUS_TYPE
12.1.1
product: AHL - Complex Maintenance Repair and Overhaul , meaning: AHL_OSP_LINE_STATUS , description: OSP Order Line Status ,
-
Lookup Type: AHL_OSP_LINE_STATUS_TYPE
12.2.2
product: AHL - Complex Maintenance Repair and Overhaul , meaning: AHL_OSP_LINE_STATUS , description: OSP Order Line Status ,
-
Lookup Type: AHL_OSP_STATUS_TYPE
12.1.1
product: AHL - Complex Maintenance Repair and Overhaul , meaning: AHL_OSP_STATUS , description: AHL OSP Order Status ,
-
Lookup Type: AHL_OSP_STATUS_TYPE
12.2.2
product: AHL - Complex Maintenance Repair and Overhaul , meaning: AHL_OSP_STATUS , description: AHL OSP Order Status ,
-
PACKAGE BODY: APPS.GCS_CREATE_LEVELS_PKG
12.1.1
-
PACKAGE BODY: APPS.PO_ONLINE_REPORT
12.2.2
-
PACKAGE BODY: APPS.PO_ONLINE_REPORT
12.1.1
-
PACKAGE BODY: APPS.PO_CONTROL_CHECKS
12.1.1
-
PACKAGE BODY: APPS.PO_CONTROL_CHECKS
12.2.2
-
PACKAGE BODY: APPS.FV_AP_CANCEL_PKG
12.2.2
-
PACKAGE BODY: APPS.FV_AP_CANCEL_PKG
12.1.1
-
PACKAGE BODY: APPS.PO_ACTIONS
12.1.1
-
PACKAGE BODY: APPS.PO_ACTIONS
12.2.2
-
PACKAGE: APPS.AHL_OSP_ORDERS_PVT
12.1.1
-
PACKAGE: APPS.AHL_OSP_ORDERS_PVT
12.2.2
-
APPS.GCS_CREATE_LEVELS_PKG dependencies on FND_MESSAGE
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_PO_PVT
12.1.1
-
APPS.PO_CONTROL_CHECKS dependencies on FND_LOG
12.1.1
-
APPS.PO_CONTROL_CHECKS dependencies on FND_LOG
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_PO_PVT
12.2.2
-
PACKAGE BODY: APPS.PO_DOCUMENT_CANCEL_PVT
12.1.1
-
APPS.GCS_CREATE_LEVELS_PKG dependencies on FND_LOG
12.1.1
-
APPS.AHL_OSP_PO_PVT dependencies on AHL_OSP_ORDERS_B
12.2.2
-
APPS.AHL_OSP_PO_PVT dependencies on AHL_OSP_ORDERS_B
12.1.1
-
PACKAGE BODY: APPS.PO_DOCUMENT_ACTION_PVT
12.2.2
-
APPS.AHL_OSP_PO_REQ_PVT dependencies on AHL_OSP_ORDERS_B
12.1.1
-
APPS.AHL_OSP_PO_REQ_PVT dependencies on AHL_OSP_ORDERS_B
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_PO_REQ_PVT
12.2.2
-
APPS.PO_DOCUMENT_ACTION_CLOSE dependencies on PO_CORE_S
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_PO_REQ_PVT
12.1.1
-
APPS.PO_DOCUMENT_ACTION_CLOSE dependencies on PO_CORE_S
12.1.1
-
APPS.PO_DOCUMENT_CANCEL_PVT dependencies on FND_LOG
12.1.1
-
PACKAGE BODY: APPS.PO_DOCUMENT_ACTION_CLOSE
12.1.1
-
APPS.PO_DOCUMENT_CONTROL_PVT dependencies on FND_MESSAGE
12.2.2
-
PACKAGE BODY: APPS.PO_DOCUMENT_ACTION_CLOSE
12.2.2
-
APPS.PO_DOCUMENT_CONTROL_PVT dependencies on FND_MESSAGE
12.1.1
-
PACKAGE BODY: APPS.PO_DOCUMENT_ACTION_PVT
12.1.1
-
APPS.AHL_OSP_ORDERS_PVT dependencies on AHL_OSP_ORDERS_B
12.1.1
-
APPS.AHL_OSP_ORDERS_PVT dependencies on AHL_OSP_ORDERS_B
12.2.2
-
PACKAGE BODY: APPS.AHL_OSP_ORDERS_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_OSP_ORDERS_PVT
12.2.2
-
APPS.PO_DOCUMENT_CONTROL_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.PO_DOCUMENT_CONTROL_PVT dependencies on FND_MSG_PUB
12.2.2
-
PACKAGE BODY: APPS.AP_APPROVAL_MATCHED_PKG
12.1.1
-
PACKAGE BODY: APPS.PO_DOCUMENT_CONTROL_PVT
12.2.2
-
PACKAGE BODY: APPS.PO_DOCUMENT_CONTROL_PVT
12.1.1
-
APPS.AP_APPROVAL_MATCHED_PKG dependencies on AP_DEBUG_PKG
12.1.1
-
PACKAGE BODY: APPS.AP_APPROVAL_MATCHED_PKG
12.2.2
-
APPS.AP_APPROVAL_MATCHED_PKG dependencies on AP_DEBUG_PKG
12.2.2
-
APPS.AHL_OSP_PO_PVT dependencies on FND_LOG
12.2.2