Results for “supervisor_name”

2 results




Overview
Explore in AI Chat

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

Overview

AST_EMPLOYMENT_HISTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AST (TeleSales) product family. The view exposes employment history records maintained for parties (persons and organizations) within the Oracle Trading Community Architecture data model. Its principal function is to present a denormalized, read-friendly projection of employment data so that TeleSales functionality, concurrent programs, and custom reports can retrieve a party's prior and current employment details without joining directly against the underlying base table.

The view is defined as a simple projection over HZ_EMPLOYMENT_HISTORY, selecting an explicit column list together with the ROWID pseudocolumn. Because it carries standard EBS Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrency columns (OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), the view is suitable for both ad hoc reporting and integration extracts where audit lineage and multi-org-safe identifiers are required. In the 12.1.1 and 12.2.2 releases the object is documented as VALID, indicating it is compiled and available for querying in a standard installation.

Underlying Base Objects

The view is defined over a single referenced base object, HZ_EMPLOYMENT_HISTORY, accessed through a synonym owned by APPS. The definition is a straightforward SELECT that lists ROWID and the full set of employment history attributes from that table; no joins, unions, or aggregations are present. Consequently, the cardinality of the view matches the base table one-to-one, and all filtering, ordering, and DML restrictions applicable to the base table apply equally here.

Because HZ_EMPLOYMENT_HISTORY is the TCA repository for a party's employment records, each row of AST_EMPLOYMENT_HISTORY_V corresponds to a single employment history entry for a party identified by PARTY_ID. The view does not itself store data; it inherits all data integrity, partitioning, and access controls configured on the underlying table. Security is therefore governed by the grants on the synonym and the base table, and by any Oracle row-level security or TCA access policies applied in the deployment.

Key Columns

  • EMPLOYMENT_HISTORY_ID — Primary identifier of the employment history record.
  • PARTY_ID — Foreign key to the party (person or organization) whose employment is recorded.
  • BEGIN_DATE / END_DATE — Validity window for the employment entry.
  • EMPLOYED_AS_TITLE — Job title held by the party.
  • EMPLOYED_BY_NAME_COMPANY / EMPLOYED_BY_DIVISION_NAME — Employer name and division.
  • SUPERVISOR_NAME — Name of the supervisor associated with the employment record; this is the column most often targeted when users search for a supervisor's name against a party's employment history.
  • BRANCH, STATION, MILITARY_RANK, SERVED — Additional employment attributes, including branch and duty station information and indicators of military service.
  • Who and concurrency columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, APPLICATION_ID, CREATED_BY_MODULE.
  • ROW_ID — The ROWID pseudocolumn, useful for direct row addressing in diagnostics.

Common Use Cases and Queries

Typical usage includes TeleSales agent screens, party profile reports, and integration extracts that must surface a party's employment background, including the supervisor name. A common query retrieves employment entries for a given party:

  • SELECT employment_history_id, party_id, employed_as_title, employed_by_name_company, supervisor_name, begin_date, end_date FROM apps.ast_employment_history_v WHERE party_id = :p_party_id ORDER BY begin_date DESC;

To locate records by supervisor, the view can be filtered directly on the SUPERVISOR_NAME column:

  • SELECT party_id, employed_by_name_company, employed_as_title, supervisor_name, begin_date, end_date FROM apps.ast_employment_history_v WHERE UPPER(supervisor_name) LIKE UPPER('%' || :p_supervisor || '%') ORDER BY party_id, begin_date DESC;

Because the view is a one-to-one projection, queries may be extended with joins to HZ_PARTIES on PARTY_ID to obtain party names and types. Reporting against the view should observe standard EBS best practices: bind variables rather than literals, restriction to the required columns, and awareness that the view inherits the base table's data volume, so selective predicates on PARTY_ID or date ranges are advisable for performance.