Results for “igs_as_notify_be”
23 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_AS_NOTIFY_BE is a table in the IGS (Student System) product schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Per the ETRM metadata, its documented purpose is to contain information about business events that have been generated. In the Oracle Student System context, the "AS" prefix generally denotes the Academic Scheduling subsystem, and the "NOTIFY_BE" naming indicates a notification or event-registration store for business events raised against scheduling-related entities. The table therefore acts as a bookkeeping record that links a specific academic scheduling context to an internal event identifier, allowing downstream processes, workflow subscribers, or integration consumers to detect, retrieve, and act upon generated business events.
From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as satellite-leaning. The table's primary key — IGS_AS_NOTIFY_BE_PK, composed of UOO_ID and INTERNAL_NAME — behaves as a composite business key with descriptive and operational attributes, rather than a pure hub or link. It also carries one foreign key reference, from UOO_ID to IGS_PS_UNIT_OFR_OPT_ALL, which provides the parent context for the event record.
Key Information Stored
The table contains 11 documented columns. The most significant are:
- UOO_ID — Part of the composite primary key and the foreign key to IGS_PS_UNIT_OFR_OPT_ALL. It identifies the unit offering option against which the business event was raised, anchoring the event to a specific scheduling record.
- INTERNAL_NAME — The second component of the primary key. It holds the internal identifier of the generated business event, distinguishing events recorded for the same unit offering option.
- CREATED_BY, CREATION_DATE — Standard Oracle EBS who-columns capturing the user and timestamp of the initial insert.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login session responsible for it.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — The concurrent program context columns. These record which concurrent request and concurrent program created or last touched the row, which is valuable when tracing an event back to a batch scheduling or notification process.
The surrogate-style unique index IGS_AS_NOTIFY_BE_U1 mirrors the primary key on (UOO_ID, INTERNAL_NAME), confirming that this pair is the true business-key candidate. There are no other documented unique indexes.
Common Use Cases and Queries
Typical usage centers on auditing and troubleshooting generated scheduling business events. A representative query joining to the parent offering option would be:
SELECT n.UOO_ID, n.INTERNAL_NAME, n.CREATION_DATE, n.CREATED_BY FROM IGS.IGS_AS_NOTIFY_BE n WHERE n.UOO_ID = :unit_ofr_opt_id;- Identifying which events were generated by a specific concurrent program:
SELECT REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE FROM IGS.IGS_AS_NOTIFY_BE WHERE PROGRAM_ID = :program_id; - Auditing recent event activity by date range using CREATION_DATE or LAST_UPDATE_DATE.
Reporting scenarios include monitoring event volume per unit offering option, diagnosing duplicate or missing notifications for a scheduling cycle, and reconciling business events against the concurrent request log.
Related Objects
- IGS_PS_UNIT_OFR_OPT_ALL — The parent table referenced by the foreign key IGS_AS_NOTIFY_BE.UOO_ID. This is the primary join target, linking each event to its unit offering option record.
- IGS_AS_NOTIFY_BE_PK — The primary key constraint over (UOO_ID, INTERNAL_NAME).
- IGS_AS_NOTIFY_BE_U1 — The unique index over the same business-key columns.
- FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — Relate via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for concurrent process traceability.
- FND_USER — Relates via CREATED_BY and LAST_UPDATED_BY for user attribution.
-
Contains the Information of the Business event generated
-
TABLE: IGS.IGS_AS_NOTIFY_BE 12.1.1
-
Table: IGS_AS_NOTIFY_BE 12.2.2
Contains the Information of the Business event generated
Not implemented in this database·Explore IGS module →
-
This entity describes the available options for each unit offering.
Not implemented in this database·Explore IGS module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGS Tables and Views 12.1.1
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
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'.