Results for “irc_documents”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IRC_DOCUMENTS is a Human Resources (PER) module table in the Oracle E-Business Suite, owned by the HR schema. It stores documents that a registered user wishes to persist directly on the database, with resumes and cover letters cited as canonical examples. In practice the table functions as the iRecruitment document repository, holding both raw binary content and character-based text produced by document parsing, together with the descriptive attributes that allow the application to classify, retrieve, and display each file. The object is documented as VALID in both EBS 12.1.1 and 12.2.2, with the 12.2.2 physical schema comprising 19 columns under the HR owner.

The provided relationship metadata classifies IRC_DOCUMENTS heuristically as standalone within a Data Vault modeling scheme. No foreign-key dependencies are documented, so it is best treated as an independent structure rather than a hub, link, or satellite, though its PARTY_ID, PERSON_ID, and ASSIGNMENT_ID columns imply logical associations to person and assignment entities that are not declared as database constraints.

Key Information Stored

The surrogate primary key is DOCUMENT_ID, enforced by the IRC_DOCUMENTS_PK constraint and the IRC_DOCUMENT_PK unique index. The remaining documented unique indexes correspond to Oracle LOB storage segments (SYS_IL0000202559C00004$$, SYS_IL0000202559C00005$$, and SYS_IL0000202559C00011$$), which index the large object columns rather than representing business keys. Notable columns include:

• DOCUMENT_ID — surrogate primary key uniquely identifying each stored document.
• BINARY_DOC — LOB holding the original binary file content.
• CHARACTER_DOC — LOB holding character-based content, typically extracted or converted from the binary document.
• PARSED_XML — LOB containing structured XML produced by parsing the document, enabling text search and automated processing.
• FILE_NAME, FILE_FORMAT, MIME_TYPE — descriptive attributes identifying the file, its format, and its MIME classification.
• TYPE and DESCRIPTION — user-facing categorization and free-text description of the document.
• PARTY_ID, PERSON_ID, ASSIGNMENT_ID — logical references linking a document to a party, person, or assignment record.
• END_DATE — effective-dating column supporting logical expiration of the document.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard EBS audit and optimistic locking support.

Common Use Cases and Queries

Typical scenarios include retrieving a candidate's resume for a recruiter, auditing which documents are attached to a person, and reporting on document formats or volumes. Queries should avoid selecting the large LOB columns unless the content is required, because BINARY_DOC, CHARACTER_DOC, and PARSED_XML are heavyweight. A lightweight metadata query follows:

• SELECT document_id, file_name, file_format, mime_type, type, creation_date FROM hr.irc_documents WHERE person_id = :person_id ORDER BY creation_date DESC;
• SELECT document_id, file_name FROM hr.irc_documents WHERE party_id = :party_id AND (end_date IS NULL OR end_date > SYSDATE);
• SELECT file_format, COUNT(*) FROM hr.irc_documents GROUP BY file_format;

Reporting use cases commonly join DOCUMENT_ID to downstream attachments or activity tables, track document aging through CREATION_DATE and END_DATE, and measure format distribution to validate upload policies.

Related Objects

Because the metadata describes IRC_DOCUMENTS as standalone, the following relationships are logical rather than declared foreign keys; join columns are named explicitly.

• PER_ALL_PEOPLE_F — joined via PERSON_ID to resolve the person owning the document.
• PER_ALL_ASSIGNMENTS_F — joined via ASSIGNMENT_ID to relate documents to specific assignments.
• HZ_PARTIES — joined via PARTY_ID to resolve the registered party.
• IRC_CANDIDATES / iRecruitment candidate entities — logically associated through PERSON_ID for applicant resumes.
• FND_LOBS — referenced indirectly when documents are stored through the generic file storage framework.
• IRC_DOCUMENTS_PK / IRC_DOCUMENT_PK — the primary key constraint and unique index enforcing DOCUMENT_ID uniqueness.

Consultants integrating with this table should confirm whether the application writes documents through IRC_DOCUMENTS directly or through the iRecruitment APIs, and should respect LOB handling and audit column maintenance in any custom code.