Results for “document_status”

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

Overview

APPS.PER_CONTRACTS_V2 is a VALID database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema and assigned to the PER (Human Resources) product family. Its documented purpose is to support the Manage Contracts form in Oracle HRMS, presenting contract and contract-document information for persons within a business group in a form suitable for both the form layer and downstream reporting or integration use. The view consolidates data from person, person-type, period-of-service, and contract sources into a single denormalized row per contract, which makes it convenient for EBS reporting, concurrent programs, and inbound/outbound interfaces that require contract status and document status information without joining the underlying HR tables manually. ETRM metadata records its status as VALID and its owner as APPS.

Underlying Base Objects

The documented base objects referenced by PER_CONTRACTS_V2 include both tables and PL/SQL packages:

• HR_PERSON_NAME and HR_SECURITY (packages) — used for name formatting and row-level security.
• PER_PEOPLE_F and PER_ASSIGNMENTS_F (views) — effective-dated person and assignment data.
• PER_CONTRACTS_F, PER_PERIODS_OF_SERVICE, and PER_PERSON_TYPES (synonyms) — contract, service period, and person-type sources.
• HR_GENERAL (package) — provides the DECODE_LOOKUP function used to translate lookup codes into meanings.
• HR_PERSON_TYPE_USAGE_INFO and PER_MANAGE_CONTRACTS_PKG (packages) — supply user person type and contract association values.
• FND_SESSIONS (synonym) and DUAL (synonym) — session/effective-date context and singleton queries.

Because the view text aliases these objects as PER, CON, PPT, PPS, and SES, the view behaves as a joined projection rather than a stored table; it inherits the effective-dated and security semantics of the HRMS person model.

Key Columns

The view exposes a wide set of columns. The most significant include:

• BUSINESS_GROUP_ID, PERSON_ID, FULL_NAME, EMPLOYEE_NUMBER, APPLICANT_NUMBER — identity and business-group context.
• NATIONAL_IDENTIFIER, DATE_OF_BIRTH — personal attributes.
• CONTRACT_ID, REFERENCE, TYPE — contract identity and type; TYPE is decoded via the CONTRACT_TYPE lookup.
• STATUS, STATUS_REASON — decoded through CONTRACT_STATUS and CONTRACT_STATUS_REASON lookups.
• DOC_STATUS, DOC_STATUS_CHANGE_DATE — the document status code and its change date; DOC_STATUS is decoded through the DOCUMENT_STATUS lookup, which is directly relevant to searches on "document_status".
• DURATION, DURATION_UNITS, CONTRACTUAL_JOB_TITLE, PARTIES, DESCRIPTION — contract terms.
• START_REASON, END_REASON, NUMBER_OF_EXTENSIONS, EXTENSION_REASON, EXTENSION_PERIOD — lifecycle attributes.
• CTR_INFORMATION1..20, ATTRIBUTE_CATEGORY — descriptive flexfield content for contract information.

Common Use Cases and Queries

Typical uses include generating contract and document-status listings, feeding interfaces that must reconcile contract documentation state, and validating the Manage Contracts form data.

List contracts by document status for a business group:

• SELECT person_id, employee_number, full_name, contract_id, reference, status, doc_status, doc_status_change_date FROM apps.per_contracts_v2 WHERE business_group_id = :p_bg_id AND doc_status = :p_doc_status ORDER BY full_name;

Obtain decoded document status meanings:

• SELECT contract_id, reference, HR_GENERAL.DECODE_LOOKUP('DOCUMENT_STATUS', doc_status) document_status_meaning FROM apps.per_contracts_v2 WHERE person_id = :p_person_id;

Join to person or assignment data for downstream reporting:

• SELECT v.full_name, v.contract_id, v.status, v.doc_status, a.assignment_number FROM apps.per_contracts_v2 v, apps.per_assignments_f a WHERE v.person_id = a.person_id AND TRUNC(SYSDATE) BETWEEN a.effective_start_date AND a.effective_end_date;

Because the view relies on HR security and session context, queries should respect business-group filtering and, where applicable, secure the results using the standard HR security APIs.