Results for “to_object_id”

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

Overview

CSS_DEF_EXTERNAL_LINKS is a cross-reference (association) table in the Oracle E-Business Suite CSS – Support module. It records the linkage between a defect recorded in the defect-tracking schema and an external or downstream object elsewhere in the EBS data model. In practical terms, the table answers the question: "which external EBS entity is associated with a given defect?" The TO_OBJECT_CODE / TO_OBJECT_ID pair provides a generic, polymorphic foreign key into the JTF object registry, while FROM_DEFECT_ID anchors the association to a specific defect.

The supplied metadata classifies the object heuristically as a link table within a Data Vault modeling scheme. This is appropriate: the table holds no descriptive attributes of its own and exists to resolve a many-to-many style relationship between CSS_DEF_DEFECTS_B and JTF_OBJECTS_B. Both participating keys are foreign key columns rather than business attributes, confirming the table's role as a pure relationship carrier.

Note that the CSS – Support product is documented as obsolete, and the ETRM entry states the object is "not implemented in this database." Implementations on Oracle EBS 12.1.1 and 12.2.2 should verify presence before writing dependent code.

Key Information Stored

The table is narrow and its meaningful content is concentrated in a small set of columns:

• EXTERNAL_LINK_ID — surrogate primary key defined by the constraint CSS_DEF_EXTERNAL_LINKS_PK. Generated internally; not a business identifier.
• FROM_DEFECT_ID — foreign key to CSS_DEF_DEFECTS_B, identifying the source defect. This column participates in the unique index CSS_DEF_EXTERNAL_LINKS_UK1, making it part of the documented business-key candidate.
• TO_OBJECT_CODE — foreign key to JTF_OBJECTS_B, indicating the object type (for example, a service request, task, or other JTF-registered entity). Also part of CSS_DEF_EXTERNAL_LINKS_UK1.
• TO_OBJECT_ID — the identifier of the specific target instance within the object type designated by TO_OBJECT_CODE. Also part of CSS_DEF_EXTERNAL_LINKS_UK1.

The combination of FROM_DEFECT_ID, TO_OBJECT_CODE, and TO_OBJECT_ID forms the unique business key. This enforces that a defect can be linked at most once to any given external object instance, while permitting the same defect to point to multiple distinct targets.

Common Use Cases and Queries

The primary use case is defect-to-object traceability. A typical query joins the link table to the defect base table to list external references for a defect:

• SELECT l.to_object_code, l.to_object_id FROM css_def_external_links l WHERE l.from_defect_id = :defect_id;
• Counting links per defect to identify defects with broad downstream impact.
• Reverse lookup: given a target object (to_object_code, to_object_id), find all defects that reference it.
• Reporting on unresolved defects that have no external links, using an outer join against CSS_DEF_DEFECTS_B.

Because TO_OBJECT_CODE is polymorphic, queries that need target detail must resolve the object type through JTF_OBJECTS_B before joining to the concrete entity table. This two-step resolution is a standard pattern when working with JTF-based cross references and should be built into any reporting view over this table.

Related Objects

The following objects are directly implicated by the documented key relationships:

• CSS_DEF_DEFECTS_B — base table for defects; joined on FROM_DEFECT_ID. Provides all descriptive defect attributes.
• JTF_OBJECTS_B — the JTF object registry; joined on TO_OBJECT_CODE. Supplies the object type definition used to interpret TO_OBJECT_ID.
• CSS_DEF_DEFECTS_TL — translated defect names and descriptions, typically joined through CSS_DEF_DEFECTS_B for multilingual reporting.
• Other CSS_DEF_* support tables that reference CSS_DEF_DEFECTS_B and therefore share the same defect key space.
• Concrete target tables registered in JTF_OBJECTS_B, resolved dynamically via the object code rather than by a fixed foreign key.

Together these objects support full defect-link lineage: from a defect row, through CSS_DEF_EXTERNAL_LINKS, into the generic JTF object registry and onward to the specific referenced entity.