Search Results party_sa_notes_id
Overview
The IGS_FI_P_SA_NOTES table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle's Higher Education product) Financials module. Its primary function is to maintain a historical record of textual notes associated with a person (party) in a specific financial context. As indicated by its design, it tracks these notes with an effective date, allowing for a chronological audit of comments or annotations related to a party's financial subaccount. This table is critical for storing contextual information that supplements transactional financial data, supporting compliance and audit trails within the institution's financial operations.
Key Information Stored
The table's structure is designed to link notes to specific entities and track standard audit information. The key columns include:
- PARTY_SA_NOTES_ID: The primary key, a system-generated unique identifier for each note record.
- PARTY_ID: A mandatory foreign key linking to HZ_PARTIES, identifying the person for whom the note is recorded.
- SUBACCOUNT_ID: A foreign key to IGS_FI_SUBACCTS_ALL, intended to link the note to a specific financial subaccount. The metadata explicitly marks this column as OBSOLETE.
- EFFECTIVE_DATE: The date from which the note is applicable, enabling time-based tracking.
- REFERENCE_NUMBER: A foreign key linking to IGS_GE_NOTE, which is the standard table for storing the actual note text (CLOB data).
- Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): For tracking the creation and modification history of each record.
Common Use Cases and Queries
This table is central to reporting and inquiry forms that display historical notes on a party's financial profile. A common use case is retrieving all notes for a specific person (PARTY_ID), ordered by effective date to show the history. Another scenario involves joining to the IGS_GE_NOTE table to fetch the actual note text for display or reporting. A typical query pattern would be:
SELECT psn.PARTY_SA_NOTES_ID,
psn.PARTY_ID,
psn.EFFECTIVE_DATE,
gn.note_text
FROM IGS.IGS_FI_P_SA_NOTES psn,
IGS.IGS_GE_NOTE gn
WHERE psn.REFERENCE_NUMBER = gn.REFERENCE_NUMBER
AND psn.PARTY_ID = :p_party_id
ORDER BY psn.EFFECTIVE_DATE DESC;
This supports operational reporting, audit reviews, and customer service inquiries where understanding the historical context of financial interactions with a party is required.
Related Objects
IGS_FI_P_SA_NOTES is part of a defined relational model within IGS Financials. Its key dependencies, as documented in the relationship data, are:
- Primary Key: IGS_FI_P_SA_NOTES_PK on column PARTY_SA_NOTES_ID.
- Foreign Key References (Outbound):
- HZ_PARTIES (TABLE): Via the PARTY_ID column. This links the note to the core Trading Community Architecture (TCA) person record.
- IGS_GE_NOTE (TABLE): Via the REFERENCE_NUMBER column. This is the critical join to retrieve the stored note text.
- IGS_FI_SUBACCTS_ALL (TABLE): Via the SUBACCOUNT_ID column, though this relationship is noted as obsolete.
- Referenced By (Inbound): The documentation states the table is referenced by the APPS schema, indicating it is accessed by application code and potentially other database objects for data integrity and reporting.
-
TABLE: IGS.IGS_FI_P_SA_NOTES
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGS_FI_P_SA_NOTES, object_name:IGS_FI_P_SA_NOTES, status:VALID,
-
VIEW: APPS.IGS_FI_P_SA_NOTES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_FI_P_SA_NOTES_V, object_name:IGS_FI_P_SA_NOTES_V, status:VALID,
-
APPS.IGS_FI_P_SA_NOTES_PKG dependencies on IGS_FI_P_SA_NOTES
12.1.1
-
Table: IGS_FI_P_SA_NOTES
12.2.2
product: IGS - Student System (Obsolete) , description: Contains any textual notes for a sub account and a person context. This tracks the notes with an effective date. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_FI_P_SA_NOTES
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGS_FI_P_SA_NOTES, object_name:IGS_FI_P_SA_NOTES, status:VALID, product: IGS - Student System , description: Contains any textual notes for a sub account and a person context. This tracks the notes with an effective date. , implementation_dba_data: IGS.IGS_FI_P_SA_NOTES ,
-
View: IGS_FI_P_SA_NOTES_V
12.2.2
product: IGS - Student System (Obsolete) , description: This view is created by joining the table IGS_FI_P_SA_NOTES and IGS_GE_NOTE table. The Note Text is captured in IGS_GE_NOTE table and this tables are linked together by REFERENCE_NUMBER field. , implementation_dba_data: Not implemented in this database ,
-
View: IGS_FI_P_SA_NOTES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_FI_P_SA_NOTES_V, object_name:IGS_FI_P_SA_NOTES_V, status:VALID, product: IGS - Student System , description: This view is created by joining the table IGS_FI_P_SA_NOTES and IGS_GE_NOTE table. The Note Text is captured in IGS_GE_NOTE table and this tables are linked together by REFERENCE_NUMBER field. , implementation_dba_data: APPS.IGS_FI_P_SA_NOTES_V ,
-
APPS.IGS_FI_P_SA_NOTES_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_FI_P_SA_NOTES_PKG
12.1.1
-
eTRM - IGS Tables and Views
12.1.1
description: Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'. ,
-
eTRM - IGS Tables and Views
12.1.1
description: Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'. ,