Results for “per_periods_of_placement_v”

20 results




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

Overview

PER_PERIODS_OF_PLACEMENT_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered as VALID in release 12.2.2 (and available in 12.1.1). It belongs to the PER — Human Resources product/module and is documented as providing "periods of placement for contingent workers." In EBS terminology, a period of placement represents a discrete engagement interval for a contingent worker (for example, a contractor, temporary worker, or agency-supplied resource), bounded by a start date and a projected or actual termination date.

The view's practical role is to expose placement-period data in a flattened, reporting-friendly form. It layers a lookup-decoded termination reason on top of the base table, which means consumers of the view do not have to join to FND_LOOKUPS or invoke HR_GENERAL.DECODE_LOOKUP themselves to obtain a human-readable termination reason. Because it is a simple, non-key-preserving view over the placement table, it behaves like a view for read/reporting and integration extraction use. The identifying key exposed is PERIOD_OF_PLACEMENT_ID, which is the column most frequently searched for and used as the join predicate when retrieving a specific placement period.

Underlying Base Objects

The ETRM metadata documents two referenced objects:

  • PER_PERIODS_OF_PLACEMENT (SYNONYM) — the primary base object. The view is defined as a direct SELECT ... FROM PER_PERIODS_OF_PLACEMENT PDP, projecting essentially every column of the base table. The synonym resolves to the underlying PER_PERIODS_OF_PLACEMENT table (owned by the PER schema).
  • HR_GENERAL (PACKAGE) — referenced only within the view's select list, specifically the call HR_GENERAL.DECODE_LOOKUP('HR_CWK_TERMINATION_REASONS', PDP.TERMINATION_REASON). This resolves the stored termination reason code into its display meaning using the seeded lookup type HR_CWK_TERMINATION_REASONS.

Because the view is a thin projection over the base table with one decode, it is not an aggregation or multi-table join view. Row cardinality therefore matches the base table, and a query against the view can be expected to return one row per placement period. Writers should note that the view is intended for querying; inserts and updates for contingent worker placements are not performed through it.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting on active and historical contingent worker placements, extracting placements for integration with time-and-labor or procurement systems, and identifying placements due to expire.

Retrieve a single placement period by its ID:

  • SELECT period_of_placement_id, person_id, date_start, projected_termination_date, actual_termination_date, d_termination_reason FROM per_periods_of_placement_v WHERE period_of_placement_id = :id;

List all placements for a person:

  • SELECT period_of_placement_id, date_start, projected_termination_date, actual_termination_date FROM per_periods_of_placement_v WHERE person_id = :person_id ORDER BY date_start;

Find placements nearing their projected termination date within a business group:

  • SELECT period_of_placement_id, person_id, projected_termination_date FROM per_periods_of_placement_v WHERE business_group_id = :bg_id AND actual_termination_date IS NULL AND projected_termination_date BETWEEN SYSDATE AND SYSDATE + 30 ORDER BY projected_termination_date;

In each case the decoded D_TERMINATION_REASON can be selected directly, avoiding an explicit join to the lookup table.