Results for “as_ref_short_notes”

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

Overview

AS_REF_SHORT_NOTES is a table registered in the Oracle E-Business Suite ETRM (E-Business Suite Technical Reference Manual) under the AS - Sales Foundation product family. Within the ETRM metadata it carries the explicit description "No Longer Used," and its implementation status is recorded as "Not implemented in this database." These two facts dominate any practical reading of the object: AS_REF_SHORT_NOTES is a legacy, obsolete or placeholder table that is not shipped or populated in the target 12.1.1 / 12.2.2 environment. It appears in the repository only because remnants of its definition survive in the data model lineage, not because it plays an active role in Sales Foundation processing.

From a Data Vault modeling perspective, the heuristic classification supplied in the metadata is satellite-leaning. This suggestion is derived from the observed foreign-key topology: the table carries a single surrogate primary key (SHORT_NOTE_ID) and a foreign key to HZ_REFERENCES, plus an event-style descriptive identity. A satellite-leaning classification implies the object was originally intended to hold descriptive or historical attributes attaching to a parent reference rather than to act as an independent hub or a pure relationship link. Because the table is documented as unused, this classification is a modeling suggestion for historical reconstruction only, not a description of live EBS behavior.

Key Information Stored

The documented column inventory for AS_REF_SHORT_NOTES is intentionally minimal; the metadata identifies only those columns needed to express the primary and foreign key structure. The most important documented attributes are:

• SHORT_NOTE_ID — the surrogate primary key, defined by the constraint AS_REF_SHORT_NOTES_PK. It provides the unique row identifier for each short-note record.
• REFERENCE_ID — the foreign key column that would have associated each short note with a row in HZ_REFERENCES, linking note content to a referenced entity.

No unique business-key indexes are documented in the supplied metadata. SHORT_NOTE_ID is a system-generated surrogate; no alternate natural key is recorded. Because the table is marked "No Longer Used" and "Not implemented in this database," no further columns are attested. Any short-note descriptive text, timestamp, or type columns that may have existed in earlier releases are not part of the current documented structure and should not be assumed present in 12.1.1 / 12.2.2.

Common Use Cases and Queries

Because the object is not implemented, there is no supported operational use case. The primary practical scenario is impact analysis and custom-code remediation: identifying whether legacy extensions, reports, or interfaces still reference AS_REF_SHORT_NOTES so they can be retired. A typical diagnostic query is:

• SELECT * FROM all_tables WHERE table_name = 'AS_REF_SHORT_NOTES'; — confirm absence in the target instance.
• SELECT * FROM all_constraints WHERE table_name = 'AS_REF_SHORT_NOTES'; — verify whether the AS_REF_SHORT_NOTES_PK constraint exists.
• SELECT * FROM dba_dependencies WHERE referenced_name = 'AS_REF_SHORT_NOTES'; — locate dependent views, packages, or synonyms.
• SELECT * FROM all_objects WHERE object_name = 'AS_REF_SHORT_NOTES'; — enumerate any residual objects.

Where the table is genuinely absent, queries will return no rows, and any custom SQL that selects from it will fail with ORA-00942. Reports requiring short-note functionality should be redirected to the supported reference or note tables in the Trading Community Model.

Related Objects

The documented foreign-key relationship ties AS_REF_SHORT_NOTES to the Trading Community reference model:

• HZ_REFERENCES — joined via AS_REF_SHORT_NOTES.REFERENCE_ID = HZ_REFERENCES.REFERENCE_ID. This is the sole documented parent relationship.
• AS_REF_SHORT_NOTES_PK — the primary key constraint on SHORT_NOTE_ID.

Beyond the recorded FK, the most significant related objects in the AS / HZ foundation area are the reference and note tables that superseded this structure, along with HZ_REF_ENTITIES and related TCA reference entities and the public APIs that manage them. Analysts should validate each candidate against the live data dictionary, since the ETRM does not document any view, synonym, or API as directly bound to AS_REF_SHORT_NOTES. In summary, the object should be treated as an obsolete artifact and excluded from new development on 12.1.1 and 12.2.2.