Search Results igp_us_artifacts_u1
Overview
The IGP_US_ARTIFACTS table, owned by the IGS (iGrants) schema, serves as a central repository for storing binary file artifacts within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary role is to support the storage and management of user-uploaded files, such as documents and images, which are associated with specific functional processes. The table is designed to store the file content, its metadata, and audit information, enabling applications to persistently manage and retrieve these digital assets. Its existence within the IGS schema indicates its primary integration with the iGrants or related grant management modules.
Key Information Stored
The table's columns are logically grouped into identifiers, file metadata, content, and standard audit columns. The ARTIFACT_ID is a sequence-generated primary key uniquely identifying each stored file. Core file metadata includes ARTIFACT_NAME (up to 256 characters), ARTIFACT_TYPE (a MIME type like 'application/msword' or 'image/pjpeg'), and FILE_SIZE. The ACCOUNT_ID column links the artifact to an author or owner within the system. The most critical column is ARTIFACT_CONTENT, defined as a BLOB, which stores the actual binary data of the uploaded file. Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and an OBJECT_VERSION_NUMBER for data concurrency control complete the structure.
Common Use Cases and Queries
This table is fundamental for scenarios requiring document attachment functionality. Common use cases include uploading supporting documents for a grant application, storing user profile pictures, or archiving signed agreement PDFs. A typical query to retrieve artifact metadata for a specific account would be: SELECT ARTIFACT_ID, ARTIFACT_NAME, ARTIFACT_TYPE, FILE_SIZE, CREATION_DATE FROM IGS.IGP_US_ARTIFACTS WHERE ACCOUNT_ID = :p_account_id;. To extract the binary content for download or processing, applications would query the ARTIFACT_CONTENT BLOB column. Reporting use cases often involve listing artifacts by type or tracking storage usage by aggregating the FILE_SIZE column, though note it is stored as a VARCHAR2(10).
Related Objects
Based on the provided dependency information, the IGP_US_ARTIFACTS table has a defined relationship with the APPS synonym named IGP_US_ARTIFACTS. This public synonym, owned by the APPS schema, points to the IGS.IGP_US_ARTIFACTS base table, providing a standard access point for all EBS application code. The table's integrity is enforced by two unique indexes: IGP_US_ARTIFACTS_PK (on ARTIFACT_ID) and IGP_US_ARTIFACTS_U1 (on ACCOUNT_ID and ARTIFACT_NAME), the latter preventing duplicate artifact names for a given account. Non-unique indexes on CREATED_BY and LAST_UPDATED_BY facilitate audit trail queries. The LOB index (SYS_IL0000402814C00006$$) manages efficient access to the BLOB data in the ARTIFACT_CONTENT column.
-
INDEX: IGS.IGP_US_ARTIFACTS_U1
12.1.1
owner:IGS, object_type:INDEX, object_name:IGP_US_ARTIFACTS_U1, status:VALID,
-
TABLE: IGS.IGP_US_ARTIFACTS
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGP_US_ARTIFACTS, object_name:IGP_US_ARTIFACTS, status:VALID,
-
12.1.1 DBA Data
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'. ,