Search Results fnd_oam_dscfg_objects_n2

Overview

APPLSYS.FND_OAM_DSCFG_OBJECTS is a transactional configuration table within the Oracle E-Business Suite Applications Object Library (FND_OAM) schema. It stores the Data Scrambling Intermediate Configuration Object definitions used by the Oracle EBS Data Scrambling engine. The table is registered in the FND design data repository as FND.FND_OAM_DSCFG_OBJECTS and is created with a status of VALID across both 12.1.1 and 12.2.2 releases. Each row represents a discrete operation that the Data Scrambling engine must perform, with one or more associated properties that define the operation type and its runtime parameters. Physically, the table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, while its three supporting indexes are placed in APPS_TS_TX_IDX.

Under a heuristic data-vault classification mined from the foreign-key structure, FND_OAM_DSCFG_OBJECTS is treated as a standalone table. It does not participate as a conventional hub, link, or satellite in a star or snowflake model; rather, it functions as a self-referencing configuration hierarchy whose parent-child relationships are expressed internally through PARENT_OBJECT_ID. This design supports nested operation definitions without requiring an external dimension join.

Key Information Stored

The table contains sixteen documented columns. The surrogate primary key is OBJECT_ID (NUMBER 15), which is enforced by the unique index FND_OAM_DSCFG_OBJECTS_U1 in the APPS_TS_TX_IDX tablespace. This column is the sole documented unique business-key candidate; no composite natural key is defined.

• OBJECT_ID — Surrogate identifier for each scrambling operation object; primary key.
• CONFIG_INSTANCE_ID — Associates the object with a specific data scrambling configuration instance. Appears as the leading column of both nonunique indexes.
• OBJECT_TYPE — Classifies the operation type; second column of index FND_OAM_DSCFG_OBJECTS_N2.
• PARENT_OBJECT_ID — References the parent object within the same table, forming the configuration hierarchy.
• SOURCE_PROC_ID, SOURCE_TYPE, SOURCE_ID — Describe the source process and entity the operation acts upon; all three participate in index FND_OAM_DSCFG_OBJECTS_N1.
• TARGET_TYPE, TARGET_ID — Identify the destination entity. TARGET_ID carries a documented foreign-key relationship to AMS_DM_TARGETS_B.
• ERRORS_FOUND_FLAG and MESSAGE (VARCHAR2 4000) — Capture failure state and diagnostic text produced during execution.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.

Common Use Cases and Queries

The primary operational use case is diagnostics of the Data Scrambling engine. Administrators query rows where ERRORS_FOUND_FLAG is set and inspect MESSAGE to resolve failed operations. A second use case is configuration reporting: listing all objects belonging to a configuration instance by OBJECT_TYPE, or reconstructing the parent-child hierarchy.

A query to isolate failed operations might read:

• SELECT OBJECT_ID, OBJECT_TYPE, SOURCE_ID, TARGET_ID, MESSAGE FROM APPLSYS.FND_OAM_DSCFG_OBJECTS WHERE ERRORS_FOUND_FLAG IS NOT NULL AND CONFIG_INSTANCE_ID = :instance_id;
• SELECT OBJECT_ID, PARENT_OBJECT_ID, OBJECT_TYPE FROM APPLSYS.FND_OAM_DSCFG_OBJECTS WHERE CONFIG_INSTANCE_ID = :instance_id ORDER BY PARENT_OBJECT_ID, OBJECT_ID;

Because OBJECT_ID is indexed uniquely, point lookups on the primary key are efficient. The nonunique indexes on (CONFIG_INSTANCE_ID, SOURCE_PROC_ID, SOURCE_TYPE, SOURCE_ID) and (CONFIG_INSTANCE_ID, OBJECT_TYPE) support filtered scans by instance and by operation category. The table is not exposed through a public concurrent program API, so direct SQL against the APPLSYS schema remains the standard access path for support and tuning activity.

Related Objects

Despite its standalone classification, the table participates in one documented foreign-key relationship and reaches several surrounding objects physically:

• APPLSYS.FND_OAM_DSCFG_OBJECTS — Self-referencing through PARENT_OBJECT_ID; also appears in the dependency list as referenced by the APPS synonym of the same name.
• AMS_DM_TARGETS_B — Referenced by the TARGET_ID column, linking each scrambling operation to a defined marketing target.
• FND_OAM_DSCFG_OBJECTS_U1, _N1, _N2 — The unique and nonunique indexes that define the access paths on OBJECT_ID and the CONFIG_INSTANCE_ID-based combinations.
• FND.FND_OAM_DSCFG_OBJECTS — The FND design data registration record that governs the object's deployment.
• APPS.FND_OAM_DSCFG_OBJECTS — The APPS-schema synonym used for runtime access under the applications user.

Collectively these objects form the storage and access layer through which the Data Scrambling engine records, indexes, and reports its intermediate configuration operations.