Results for “rcs_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_IMP_DEPOBJECTS is a table in the APPLSYS schema owned by the FND – Application Object Library product. It records dependency objects captured during an Oracle E-Business Suite snapshot, storing metadata about the files, object identifiers, and version-control characteristics that participate in an implementation or patching snapshot. In EBS 12.1.1 and 12.2.2, this table underpins snapshot and dependency-tracking operations coordinated through the Application Object Library (AD/FND) utilities, linking implementation metadata to a specific snapshot definition.

The table is documented with 28 columns and carries two unique indexes that establish its business keys: FND_IMP_DEPOBJECTS_U1 on (SNAPSHOT_ID, OBJECT_TYPE, OBJECT_NAME) and FND_IMP_DEPOBJECTS_U2 on (OBJECT_ID). From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning it behaves like a self-contained hub/link construct that does not map into a broader dependent-child hierarchy in the mined FK structure. The classification is a modeling suggestion; it does not imply referential requirements outside the documented foreign keys.

Key Information Stored

The most significant columns fall into three groups: identity, object description, and audit/versioning.

• Identity and keys: OBJECT_ID is the surrogate unique key enforced by U1’s companion index FND_IMP_DEPOBJECTS_U2. The composite FND_IMP_DEPOBJECTS_U1 supplies the business-key candidate across SNAPSHOT_ID, OBJECT_TYPE, and OBJECT_NAME.
• Snapshot association: SNAPSHOT_ID links each dependency row to a parent snapshot (foreign key to AHL_SNAPSHOTS).
• Object descriptors: OBJECT_NAME, OBJECT_TYPE, APP_SHORT_NAME, FILE_DIRECTORY, FILENAME, and FILE_TYPE describe the artifact tracked within the snapshot.
• Version/checksum: RCS_ID, OCHKSUM, and FCHKSUM hold revision-control identity and object/file checksums; OBJECT_VERSION_NUMBER supports optimistic locking.
• Flexible attributes: ATTRIB0 through ATTRIB9 provide ten generic descriptive slots.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN; SECURITY_GROUP_ID references FND_SECURITY_GROUPS for data segregation.

Common Use Cases and Queries

Typical scenarios include identifying which files belong to a given snapshot, reconciling checksums after patch application, and auditing object dependencies per application short name.

SELECT d.object_type, d.object_name, d.filename, d.ochksum
FROM   applsys.fnd_imp_depobjects d
WHERE  d.snapshot_id = :snapshot_id
ORDER  BY d.object_type, d.object_name;

To find a specific tracked object across snapshots:

SELECT snapshot_id, object_type, object_name, rcs_id, file_directory
FROM   applsys.fnd_imp_depobjects
WHERE  object_id = :object_id;

Reporting joins to FND_SECURITY_GROUPS and AHL_SNAPSHOTS support dependency and snapshot-coverage reports. Checksum comparisons between OCHKSUM and FCHKSUM flag file-conversion mismatches.

Related Objects

• AHL_SNAPSHOTS — joined via FND_IMP_DEPOBJECTS.SNAPSHOT_ID.
• FND_SECURITY_GROUPS — joined via FND_IMP_DEPOBJECTS.SECURITY_GROUP_ID.
• FND_IMP_SNAPSHOTS — companion snapshot definition table.
• FND_OBJECTS / FND_OBJECT_INSTANCES — object registration metadata supporting snapshot membership.
• FND_FILE_VERSIONS — file versioning context for FILENAME and checksum columns.
• AD utilities (adpatch, adop / Online Patching in 12.2) — consuming snapshot dependency metadata during patch application.

The table’s narrow, standalone FK footprint keeps it well isolated; most integration is through its SNAPSHOT_ID and SECURITY_GROUP_ID relationships.