Results for “igs_inq_application”
11 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The IGS.IGS_AD_RECRT_PI_HDR_ALL table is a public, active IGS product table that stores batch description records required to execute the Probability Values Import process. It functions as the logical parent header table for the probability value import interface within the Oracle E-Business Suite IGS (iProcurement / Advanced Procurement) module. The table resides in the APPS_TS_INTERFACE tablespace, is owned by the IGS schema, and is designated under the FND Design Data identifier IGS.IGS_AD_RECRT_PI_HDR_ALL.
In Oracle EBS 12.1.1 and 12.2.2, this object acts as an interface staging table that groups probability value records into discrete processing batches. Each batch is uniquely identified by a sequence-generated number provided by OSS, linking header-level batch descriptions to detailed interface lines in the child table.
From a Data Vault modeling perspective, the heuristic classification of this object is standalone, meaning it does not reference any other database object by foreign key. The primary key is IGS_AD_RECRT_PI_HDR_PK on PRBLTY_VAL_BATCH_ID, with a unique index IGS_AD_RECRT_PI_HDR_ALL_U1 on the same column acting as the business-key candidate. As a modeling suggestion, this table aligns most closely with a hub, since it holds a unique business key (PRBLTY_VAL_BATCH_ID) without dependent descriptive attributes that would characterize a satellite.
Key Information Stored
- PRBLTY_VAL_BATCH_ID (NUMBER) — Mandatory unique sequence-generated number identifying a batch processed by the user; this is the surrogate primary key and the business-key candidate carrying the unique index.
- DESCRIPTION (VARCHAR2, 240) — Free-text description of the batch.
- ORG_ID (VARCHAR2, 20) — Organization identifier, supporting multi-org partitioning of batch records.
- CREATED_BY (NUMBER, 15) — Standard WHO column recording the creating user.
- CREATION_DATE (DATE) — Standard WHO column for record creation timestamp.
- LAST_UPDATED_BY (NUMBER, 15) — Standard WHO column for the last updating user.
- LAST_UPDATE_DATE (DATE) — Standard WHO column for the last update timestamp.
- LAST_UPDATE_LOGIN (NUMBER, 15) — Standard WHO column capturing the login context of the last update.
The eight documented columns in ETRM 12.1.1 comprise the full structure; no additional attributes are defined.
Common Use Cases and Queries
The principal use case is monitoring and auditing the Probability Values Import process. Batch headers are created before records are loaded into IGS_AD_RECRT_PI_INT_ALL, allowing batch-level traceability and status reporting.
- Listing all batches, optionally filtered by organization:
SELECT PRBLTY_VAL_BATCH_ID, DESCRIPTION FROM IGS.IGS_AD_RECRT_PI_HDR_ALL WHERE ORG_ID = :org_id; - Counting interface lines per batch by joining to the child table on PRBLTY_VAL_BATCH_ID.
- Audit reporting using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.
- Locating a batch via keyword search on DESCRIPTION.
Related Objects
- IGS.IGS_AD_RECRT_PI_INT_ALL — The child interface table; its PRBLTY_VAL_BATCH_ID column references IGS.IGS_AD_RECRT_PI_HDR_ALL, providing the parent-to-child link.
- APPS.IGS_AD_RECRT_PI_HDR_ALL — The APPS-synonym view exposing the same table to the applications layer.
- IGS_AD_RECRT_PI_HDR_ALL_U1 — Unique index on PRBLTY_VAL_BATCH_ID, enforcing batch uniqueness.
- IGS_AD_RECRT_PI_HDR_PK — Primary key constraint on PRBLTY_VAL_BATCH_ID.
Because the table is classified as standalone, it does not reference other objects, but it is referenced by the child interface table through the batch identifier.
-
TABLE: IGS.IGR_I_PKG_INT 12.1.1
-
TABLE: IGS.IGR_I_LINES_INT 12.1.1
-
TABLE: IGS.IGR_I_CHAR_INT 12.1.1
-
TABLE: IGS.IGR_I_INFO_INT 12.1.1
-
TABLE: IGS.IGR_I_APPL_INT 12.1.1
-
Lookup Type: BUSINESS_ENTITY 12.1.1
-
Lookup Type: BUSINESS_ENTITY 12.2.2
-
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'.