Results for “assistance_type_cd”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_AD_MILITARY_INT_ALL is a transactional interface table in the Oracle E-Business Suite IGS (Student System) product module. It holds information about military service details submitted by external systems or feeder processes for validation and subsequent loading into the institution's student records. The table resides in the IGS schema and is owned by the Student System, which manages admissions, registration, academic history, and related student lifecycle data across Oracle EBS 12.1.1 and 12.2.2.
The _INT_ALL suffix follows the standard Oracle interface naming convention, indicating that the table is an open interface staging structure rather than an operational transaction table. Records arrive, are validated, and are either promoted to permanent military service records or rejected with an error code. Consistent with this staging role, and as reflected in the heuristic Data Vault classification supplied in the metadata, the table is best modeled as a standalone structure — it occupies neither a hub, link, nor satellite position within a Data Vault model, since it acts as a transient inbound buffer rather than a durable keyed entity. Its 44 documented columns include a full WHO/WHEN audit block and a 20-segment descriptive flexfield range.
Key Information Stored
The surrogate primary key is INTERFACE_MILITARY_ID, enforced by the constraint IGS_AD_MILITARY_INT_PK. The most significant columns include:
ORG_ID— operating unit and multi-org partitioning key.INTERFACE_ID— external identifier for the inbound record.START_DATE/END_DATE— beginning and end of the reported military service period.MILITARY_TYPE_CD— classification of service (for example, active duty versus reserve).SEPARATION_TYPE_CD— category under which the individual separated from service.ASSISTANCE_TYPE_CD/ASSISTANCE_STATUS_CD— the type and status of the benefit or assistance being claimed.MATCH_IND— flag indicating whether the row was matched to an existing person or record.STATUS/ERROR_CODE— processing outcome and validation failure diagnostics.DUP_MILIT_SERVICE_ID— reference to a suspected duplicate military service record.INTERFACE_RUN_IDandREQUEST_ID— pointers to the concurrent program run that processed the batch.- WHO columns —
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN.
The DFF block (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20) provides site-specific extensibility. No unique business indexes are documented beyond the primary key.
Common Use Cases and Queries
Typical scenarios involve monitoring inbound military service loads, diagnosing validation failures, and reconciling duplicates before promotion. Reporting patterns include:
- Listing unprocessed or errored rows for a batch:
SELECT INTERFACE_MILITARY_ID, INTERFACE_ID, STATUS, ERROR_CODE FROM IGS_AD_MILITARY_INT_ALL WHERE INTERFACE_RUN_ID = :run_id AND STATUS = 'E'; - Identifying duplicate candidates via
DUP_MILIT_SERVICE_IDto resolve before promotion. - Auditing load throughput by
REQUEST_IDandCREATION_DATEto trace performance of the concurrent program. - Extracting service periods by operating unit using
START_DATE,END_DATE, andMILITARY_TYPE_CD.
Because rows are transient, queries should generally filter by INTERFACE_RUN_ID or STATUS rather than scanning the full table.
Related Objects
As the metadata records the object as standalone, there are no documented foreign key dependencies; relationships are effectively logical rather than enforced. The most significant related objects are:
- IGS_AD_MILITARY_INT_PK — the primary key constraint on
INTERFACE_MILITARY_ID. - The military service base table to which validated rows are promoted, joined on the matched person and
DUP_MILIT_SERVICE_ID. - The IGS admissions/student person structures, joined indirectly through
INTERFACE_IDandORG_ID. - FND concurrent request tables (FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS), joined on
REQUEST_ID,PROGRAM_ID, andPROGRAM_APPLICATION_IDfor run traceability. - The IGS interface API or concurrent program responsible for populating and processing this table, driven by
INTERFACE_RUN_ID.
-
Holds information about military service details
-
View: IGS_PE_MIL_SERVICES 12.1.1
APPS.IGS_PE_MIL_SERVICES·↳ IGS_PE_MIL_SERVICES_ALL·Explore IGS module →
-
View: IGS_AD_MILITARY_INT 12.1.1
APPS.IGS_AD_MILITARY_INT·↳ IGS_AD_MILITARY_INT_ALL·Explore IGS module →
-
This entity describes the Military services of a person
-
View: IGS_PE_MIL_SERVICE_V 12.1.1
APPS.IGS_PE_MIL_SERVICE_V·↳ IGS_LOOKUP_VALUES·↳ IGS_PE_MIL_SERVICES·Explore IGS module →
-
View: IGS_AD_MILITARY_INT 12.2.2
Not implemented in this database·Explore IGS module →
-
View: IGS_PE_MIL_SERVICES 12.2.2
Not implemented in this database·Explore IGS module →
-
View: IGS_PE_MIL_SERVICE_V 12.2.2
Not implemented in this database·Explore IGS module →
-
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'.