Results for “igs_fi_p_sa_notes”

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

Overview

IGS_FI_P_SA_NOTES is a transactional child table within the Oracle E-Business Suite Student System (IGS) product family. IGS is documented as an obsolete module in Release 12.1.1 and 12.2.2, meaning the table remains physically present in legacy installations but is not part of any current implementation or upgrade path. The table stores free-text notes associated with a sub account and a person (party) context, and it preserves each note against an effective date so that the historical progression of annotations can be reconstructed.

Functionally, the table acts as a bridge between three master entities: a party record in HZ_PARTIES, a sub account record in IGS_FI_SUBACCTS_ALL, and a note definition or note reference in IGS_GE_NOTE. It therefore carries contextual commentary rather than transactional balances. Under the heuristic Data Vault classification mined from its foreign key structure, the object is best modeled as a link — it resolves a many-to-many-style association among parties, sub accounts, and notes, with the effective date supplying the temporal qualifier.

Key Information Stored

The documented physical schema contains ten columns and two unique indexes. The most important columns are:

• PARTY_SA_NOTES_ID — the surrogate primary key, enforced by IGS_FI_P_SA_NOTES_PK and mirrored by unique index IGS_FI_P_SA_NOTES_U1. It uniquely identifies each note row and is the value downstream objects would use for point lookups.
• PARTY_ID — foreign key to HZ_PARTIES, identifying the person or organization whose sub account is being annotated.
• SUBACCOUNT_ID — foreign key to IGS_FI_SUBACCTS_ALL, identifying the student financial sub account that the note concerns.
• EFFECTIVE_DATE — the date from which the note applies. Together with PARTY_ID and REFERENCE_NUMBER it forms the business-key candidate IGS_FI_P_SA_NOTES_U2, which prevents duplicate note assignments for the same party, note reference, and effective date.
• REFERENCE_NUMBER — foreign key to IGS_GE_NOTE, linking the row to the general note reference definition that supplies the note text or note type context.

The remaining documented columns are standard Oracle EBS audit and concurrency attributes: LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE. These are populated automatically by the Forms or concurrent processing layer and should be used for lineage and change-tracking audits rather than business logic.

Common Use Cases and Queries

Because the table is obsolete, use cases are largely historical reporting and data migration. Typical reporting joins party, sub account, and note reference to reconstruct annotation history:

• Retrieving all notes for a specific party and sub account, ordered by EFFECTIVE_DATE, to display an audit trail of annotations.
• Joining to HZ_PARTIES to resolve the party name, and to IGS_FI_SUBACCTS_ALL to resolve the sub account context for a financial statement reconciliation.
• Driving point-in-time queries that select the note with the greatest EFFECTIVE_DATE less than or equal to a reporting date, using the U2 index on (PARTY_ID, EFFECTIVE_DATE, REFERENCE_NUMBER) for efficient retrieval.
• Identifying duplicate or conflicting notes by counting rows grouped by PARTY_ID, REFERENCE_NUMBER, and EFFECTIVE_DATE.

A canonical pattern is a three-way join: IGS_FI_P_SA_NOTES n JOIN HZ_PARTIES p ON n.PARTY_ID = p.PARTY_ID JOIN IGS_FI_SUBACCTS_ALL s ON n.SUBACCOUNT_ID = s.SUBACCOUNT_ID, filtered by effective date range, with the note text resolved through IGS_GE_NOTE via REFERENCE_NUMBER.

Related Objects

The principal related objects are the three foreign-key targets and the primary-key dependents:

• HZ_PARTIES — referenced via PARTY_ID; supplies the person or organization identity for the note context.
• IGS_FI_SUBACCTS_ALL — referenced via SUBACCOUNT_ID; supplies the student financial sub account the note annotates.
• IGS_GE_NOTE — referenced via REFERENCE_NUMBER; supplies the note definition or reference text.

No child tables reference IGS_FI_P_SA_NOTES through the documented foreign keys, so the object behaves as a leaf-level link. Any integration or upgrade assessment involving this table must account for its obsolete status and the possibility that it is not implemented in a given database, as indicated in the source documentation.