Search Results get_objects_for_type
Overview
FND_OAM_DSCFG_OBJECTS_PKG is the object-level data access package within the Oracle E-Business Suite Diagnostic Configuration (DSCFG) subsystem of the OAM (Applications Manager) product family. Its business purpose is to persist, retrieve, and remove individual diagnostic configuration objects that belong to a diagnostic configuration instance, together with the source metadata that identifies where each object originated and any error or message diagnostics captured during collection. The package header revision carries the identifier AFOAMDSCOBJB.pls 120.2, dated 2006/01/17, confirming it as a long-standing component present in both the 12.1.1 and 12.2.2 releases.
The package body is documented as stateless beyond a table handler that inserts new objects with no properties. It depends on FND_OAM_DSCFG_INSTANCES_PKG to resolve the currently active configuration instance and, where available, on FND_OAM_DSCFG_PROCS_PKG to stamp each object with the import or collection process that created it. Debug tracing is emitted through FND_OAM_DEBUG.
Key Procedures and Functions
The API classification is OTHER and four documented members are exposed. The user search term get_objects_for_type corresponds directly to the retrieval routine in this package.
- ADD_OBJECT — Inserts a new row into FND_OAM_DSCFG_OBJECTS. It receives an object type, an optional parent object identifier, source type and source identifier, an errors-found flag, and a message, and returns the newly generated object ID to the caller. The record's configuration instance context is taken from FND_OAM_DSCFG_INSTANCES_PKG.GET_CURRENT_ID, and the source process is populated only when FND_OAM_DSCFG_PROCS_PKG.IS_INITIALIZED returns true. Audit columns are set from FND_GLOBAL.USER_ID and SYSDATE.
- GET_OBJECTS_FOR_TYPE — Returns diagnostic configuration objects filtered by object type, allowing callers to enumerate the members of a configuration instance that match a given category. It is the primary read path for consumers that need to iterate objects of a specific kind rather than the entire object set.
- DELETE_OBJECT — Removes a previously recorded diagnostic configuration object, used when a configuration instance is being purged, re-collected, or corrected.
The remaining fourth documented member is a supporting routine within the package body and is not part of the externally published surface.
Tables Accessed
The package operates on two documented database objects accessed through APPS synonyms:
- FND_OAM_DSCFG_OBJECTS — the base transactional table holding one row per diagnostic configuration object, including its instance, type, parentage, source process, source identity, error flag, and message.
- FND_OAM_DSCFG_OBJECTS_S — the sequence supplying unique OBJECT_ID values on insert, referenced as FND_OAM_DSCFG_OBJECTS_S.NEXTVAL.
The metadata also lists DBMS_SQL among the referenced objects, indicating that dynamic SQL may be constructed within the package for portions of the retrieval logic. FND_OAM_DSCFG_OBJECTS is the only table directly written by ADD_OBJECT and directly targeted by DELETE_OBJECT; GET_OBJECTS_FOR_TYPE reads from it.
Usage Notes
This package is invoked indirectly rather than from end-user forms. Diagnostic configuration collection is driven by the OAM diagnostic framework, which calls ADD_OBJECT as each discovered object is recorded and GET_OBJECTS_FOR_TYPE when a consumer needs to process objects by category. Two other packages in the ETRM inventory reference FND_OAM_DSCFG_OBJECTS_PKG, confirming its role as a shared low-level handler in the DSCFG object hierarchy.
Custom code integrating with diagnostic configuration should call ADD_OBJECT before populating any object-level properties, since the documented behavior is an insert of an object with no attached properties. Callers must ensure a current configuration instance exists, because FND_OAM_DSCFG_INSTANCES_PKG.GET_CURRENT_ID raises an error when the instance is not initialized. Updates to existing objects are not exposed by this package; modification of object properties is handled elsewhere in the DSCFG subsystem.
-
PACKAGE BODY: APPS.FND_OAM_DSCFG_OBJECTS_PKG
12.1.1
-
PACKAGE BODY: APPS.FND_OAM_DSCFG_OBJECTS_PKG
12.2.2
-
PACKAGE: APPS.FND_OAM_DSCFG_OBJECTS_PKG
12.1.1
-
PACKAGE: APPS.FND_OAM_DSCFG_OBJECTS_PKG
12.2.2
-
PACKAGE: APPS.FND_OAM_DSCFG_API_PKG
12.1.1
-
PACKAGE: APPS.FND_OAM_DSCFG_API_PKG
12.2.2
-
PACKAGE BODY: APPS.FND_OAM_DSCFG_API_PKG
12.1.1
-
PACKAGE BODY: APPS.FND_OAM_DSCFG_API_PKG
12.2.2
-
APPS.FND_OAM_DSCFG_OBJECTS_PKG dependencies on DBMS_SQL
12.1.1
-
APPS.FND_OAM_DSCFG_OBJECTS_PKG dependencies on DBMS_SQL
12.2.2
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on DBMS_SQL
12.1.1
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on DBMS_SQL
12.1.1
-
APPS.FND_OAM_DSCFG_OBJECTS_PKG dependencies on DBMS_SQL
12.2.2
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on DBMS_SQL
12.2.2
-
APPS.FND_OAM_DSCFG_OBJECTS_PKG dependencies on DBMS_SQL
12.1.1
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on DBMS_SQL
12.2.2
-
APPS.FND_OAM_DSCFG_OBJECTS_PKG dependencies on FND_OAM_DEBUG
12.2.2
-
APPS.FND_OAM_DSCFG_OBJECTS_PKG dependencies on FND_OAM_DEBUG
12.1.1
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on FND_OAM_DSCFG_OBJECTS_PKG
12.1.1
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on FND_OAM_DSCFG_OBJECTS_PKG
12.2.2
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on FND_OAM_DSCFG_OBJECTS
12.1.1
-
APPS.FND_OAM_DSCFG_API_PKG dependencies on FND_OAM_DSCFG_OBJECTS
12.2.2