Results for “qualification_status”

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

Overview

BIL_DIMV_QUALIFICATIONS is a reporting view historically shipped with the Oracle E-Business Suite BIL – Sales Intelligence product, a business-intelligence layer that provided dimensional and analytical structures over sales-related transactional and reference data. The view exposes sales representative qualifications, including certifications, licenses, training achievements, and academic records, attributed to persons who appear in the sales force dimension. Its documented purpose is to present qualification data alongside salesperson identity so that sales organizations can analyze and report on the credentials held by their representatives.

BIL – Sales Intelligence is flagged as obsolete in Oracle EBS 12.1.1 and 12.2.2. The ETRM documentation explicitly records the status "Not implemented in this database," indicating that the object is not created in the certified current installations covered by that documentation. It should therefore be treated as a legacy artifact: useful for understanding historical data models and for migration or archival analysis, but unlikely to exist in a freshly installed or fully patched 12.1.1 or 12.2.2 environment.

The user search term qualification_id corresponds directly to the final projected column in the view text, which carries the identifier of the underlying qualification record.

Underlying Base Objects

The view is defined as a UNION ALL of two branches. The first branch joins HRFV_QUALIFICATIONS (aliased HQ) to BIL_DIMV_SALESFORCE (aliased BDS) on the condition HQ.PERSON_ID = BDS.EMPLOYEE_PERSON_FK. HRFV_QUALIFICATIONS is the HR foundation view over qualification data, exposing person-level qualification records. BIL_DIMV_SALESFORCE is the sales force dimension view that identifies which persons are recognized as sales representatives. The join therefore restricts qualifications to persons who are members of the sales force, and applies an effective-date filter using NVL(QUALIFICATION_START_DATE, SYSDATE) <= SYSDATE and NVL(QUALIFICATION_END_DATE, SYSDATE) >= SYSDATE so that only currently valid qualifications are returned.

The second branch of the union selects from a table aliased FL, which by column naming conventions (LOOKUP_CODE, MEANING, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE) is an FND_LOOKUPS-style lookup source, projecting lookup values into the same column shape as the HR branch. The ETRM metadata records no separately documented base objects beyond these references, so the union structure above is the authoritative description of the view's definition.

Key Columns

The view projects a consistent set of columns from both branches:

• PERSON_ID – identifier of the sales representative; the join key to the sales force dimension.
• BUSINESS_GROUP_ID / BUSINESS_GROUP_NAME – the HR business group owning the person record.
• PERSON_NAME – name of the qualified individual.
• QUALIFICATION_ID – surrogate identifier of the qualification record, and the column most often used to link back to source qualification data.
• QUALIFICATION_TITLE, GRADE_ATTAINED, QUALIFICATION_STATUS – descriptive attributes of the credential and its current standing.
• QUALIFICATION_START_DATE / QUALIFICATION_END_DATE – validity window used by the view's effective-date predicate.
• AWARDED_DATE, PROJECTED_COMPLETION_DATE – key milestone dates.
• LICENSE_NUMBER, LICENSE_EXPIRY_DATE, LICENSE_RESTRICTIONS – licensing details where the qualification is a professional license.
• FEE, FEE_CURRENCY, TOTAL_TRAINING_AMOUNT, TRAINING_COMPLETED_AMOUNT, TRAINING_COMPLETED_UNITS, REIMBURSEMENT_ARRANGEMENTS, METHOD_OF_REIMBURSEMENT – financial and training measures.
• AWARDING_BODY, SCHOOL_OR_COLLEGE_NAME, SCHOOL_OR_COLLEGE_ID – issuing institution information.
• QUALIFICATION_CATEGORY, QUALIFICATION_TYPE_NAME, GROUP_RANKING, COMMENTS – classification and free-text attributes.

Common Use Cases and Queries

Typical use cases include identifying which sales representatives hold current licenses, monitoring expiring licenses, analyzing training investment by representative, and reporting qualifications by category or awarding body. A basic query retrieving qualifications for a specific representative would take the form:

• SELECT qualification_id, person_name, qualification_title, qualification_status, awarded_date, license_expiry_date FROM bil_dimv_qualifications WHERE person_id = :person_id;
• SELECT person_name, qualification_title, license_expiry_date FROM bil_dimv_qualifications WHERE license_expiry_date BETWEEN SYSDATE AND SYSDATE + 90 ORDER BY license_expiry_date;
• SELECT qualification_category, COUNT(*) FROM bil_dimv_qualifications GROUP BY qualification_category;

Because the view is documented as obsolete and not implemented in the reference database, these queries are principally of value for legacy reporting reconciliation, data migration planning, or where a customized or historical instance retains the object. Implementers should verify object existence in the target instance before relying on it in production SQL.