Search Results add_property_raw




Overview
Explore in AI Chat

Overview

APPS.FND_OAM_DSCFG_PROPERTIES_PKG is an Oracle E-Business Suite server-side PL/SQL package that manages the name-value property model used by the Applications DBA (AD) Diagnostics Configuration (DSCFG) framework. The package persists configuration properties associated with DSCFG object instances, which include configuration instances, domains, hosts, and related diagnostic targets. Each property is stored as a canonical VARCHAR2 representation of a typed value, allowing the framework to capture heterogeneous settings — such as list-valued properties like ADDITIONAL_DOMAIN — within a single consistent storage model.

The package is declared AUTHID CURRENT_USER, so its unqualified references resolve through the calling user's schema and synonyms. It is classified as an OTHER API rather than a public interface, which reflects its intended role as an internal building block for the DSCFG framework rather than a general-purpose extension point. Property datatype and property name constants are not defined locally; they are owned by DSCFG_API_PKG (the G_TYPE_*, G_PROP_*, and G_DATATYPE_* constants), which keeps property semantics centralized. The package is referenced by two other packages and therefore participates in a shared internal call graph within the AD diagnostics stack.

Key Procedures and Functions

The documented interface comprises 17 procedures and functions, of which the following are the principal entries:

  • ADD_PROPERTY — Adds a new property for a given parent type and parent ID. The procedure does not test for pre-existence of the property, which deliberately permits multi-valued properties that downstream processing compiles into lists. It performs no autonomous commit, allowing atomic commit together with the parent transaction. It raises NO_DATA_FOUND if the configuration instance has not been initialized. A convenience overload is provided specifically for the VARCHAR2 datatype.
  • SET_OR_ADD_PROPERTY — The procedure matched by the user's search term. It applies an upsert semantic: if the named property already exists for the parent object it is updated, and if it does not exist it is created. This is the routine of choice when the caller cannot guarantee prior state, contrasting with the pure insert behavior of ADD_PROPERTY.
  • ADD_PROPERTY_ROWID — Inserts a property while also returning or operating against the row identifier of the affected property row, useful for subsequent direct row addressing.
  • ADD_PROPERTY_RAW — Adds a property using a raw datatype representation rather than the canonical VARCHAR2 form.
  • GET_PROPERTY_VALUE — Retrieves the typed value of a named property for a given parent object.
  • GET_PROPERTY_CANONICAL_VALUE — Retrieves the stored canonical VARCHAR2 representation of a property value.
  • DELETE_PROPERTY — Removes a single named property from a parent object.
  • DELETE_PROPERTIES — Removes multiple properties in a single call, typically all properties belonging to a given parent object.

All write routines observe the framework invariant that a configuration instance must first be created or set and an object created or queried before properties may be attached.

Tables Accessed

The package operates against two base tables through APPS synonyms:

  • FND_OAM_DSCFG_PROPERTIES — the primary property store. It holds the parent type, parent ID, property name, datatype, and canonical value for each property row. All add, set, get, and delete operations target this table.
  • FND_OAM_DSCFG_PROPERTIES_S — the associated sequence or supplemental object for the property store, supplying identifiers used as x_property_id values and supporting row-level addressing such as that needed by ADD_PROPERTY_ROWID.

No commit or rollback is issued inside the package; transaction control remains with the caller so that property changes commit atomically with the parent diagnostic configuration change.

Usage Notes

FND_OAM_DSCFG_PROPERTIES_PKG is invoked from within the AD Diagnostics Configuration framework rather than directly from Oracle EBS forms or standard concurrent programs. Typical callers are other DSCFG packages — the metadata records two referencing packages — which first establish or query a configuration instance, create or locate the target object, and then call ADD_PROPERTY or SET_OR_ADD_PROPERTY to attach properties. Custom code should treat SET_OR_ADD_PROPERTY as the safe default when the presence of a property is uncertain, and reserve ADD_PROPERTY for deliberately multi-valued properties such as ADDITIONAL_DOMAIN.

Callers must use the DSCFG_API_PKG constants for parent types, property names, and datatypes; literal strings will compile but bypass the framework's centralized definitions. Because the package is AUTHID CURRENT_USER and uncommitted, custom callers should invoke it from within a transaction they control and should handle NO_DATA_FOUND as an indication that initialization steps were skipped. Direct DML against the underlying property tables is not recommended, as it bypasses the canonical-value conventions and invariant checks enforced by this package.