Search Results markup_percent_override




Overview
Explore in AI Chat

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

Overview

PA_PROJECT_ASGMTS_AR is the Projects (PA) module table that stores assignment records for a project. In Oracle EBS terminology an "assignment" links a resource — a person or an organization — to a project or to a project role for a bounded period of time, and the _AR suffix confirms that the physical object carries assignment/resource staffing data. The ETRM documentation describes it as storing "details of all Assignments for a project," and the object is owned by the PA schema and is VALID in both release 12.1.1 and 12.2.2.

The documented physical schema contains 93 columns. The breadth of the column list — role identifiers, staffing weights, availability search attributes, bill and transfer-price overrides, expense limits, and approval flags — indicates that this table is used primarily by the resource management and staffing workflows, not only by simple project-team maintenance. Columns such as STAFFING_PRIORITY_CODE, PENDING_APPROVAL_FLAG, NO_OF_ACTIVE_CANDIDATES, and LAST_AUTO_SEARCH_DATE are consistent with a candidate search and approval lifecycle for assignment requests.

From a data-vault modeling perspective, the mined foreign-key structure suggests a link classification. The table's role is largely to associate a project party with roles, resources, locations, and expenditure organizations, i.e., it resolves many-to-many relationships rather than describing a single independent entity. Modelers should therefore treat PA_PROJECT_ASGMTS_AR as a link-type object when designing integration or warehouse layers, while retaining its changing descriptive attributes (dates, status, rates) as satellite content.

Key Information Stored

The surrogate identifier is ASSIGNMENT_ID. Business-key candidates center on ASSIGNMENT_NUMBER and ASSIGNMENT_NAME, with PROJECT_ID supplying the owning project context. Important columns include:

Common Use Cases and Queries

The most frequent use is reporting current and historical project team composition, usually joined to PA_PROJECTS and PA_PROJECT_PARTIES. Assignments with END_DATE greater than SYSDATE and STATUS_CODE indicating an active state represent the current staffing picture. Staffing analysts query pending assignments by filtering on PENDING_APPROVAL_FLAG and APPRVL_STATUS_CODE, while resource managers use SEARCH_MIN_CANDIDATE_SCORE, NO_OF_ACTIVE_CANDIDATES, and LAST_AUTO_SEARCH_DATE to monitor automated candidate searches.

A representative query pattern is:

SELECT a.assignment_number, a.assignment_name, a.project_id, a.start_date, a.end_date, a.status_code FROM pa.pa_project_asgmts_ar a WHERE a.project_id = :project_id AND NVL(a.end_date, SYSDATE+1) >= SYSDATE;

Billing and revenue teams analyze rate overrides by combining BILL_RATE_OVERRIDE, REVENUE_BILL_RATE, and MARKUP_PERCENT with project contract data. Data-migration and integration projects extract assignments by the purge columns to support archival routines.

Related Objects

Documented foreign keys and the role of this table place it at the center of several predictable joins:

  • PA_PROJECT_PARTIES — joined on PROJECT_PARTY_ID; identifies the assigned party.
  • PA_PROJECT_ROLE_TYPES — joined on PROJECT_ROLE_ID; defines the role type.
  • HR_ALL_ORGANIZATION_UNITS — joined on EXPENDITURE_ORGANIZATION_ID; the expenditure organization.
  • PA_LOCATIONS — joined on LOCATION_ID; the work location.
  • PA_PURGE_BATCHES_ALL — joined on PURGE_BATCH_ID; purge/archival control.
  • PA_PROJECTS — the parent project referenced through PROJECT_ID.
  • PA_EXPENDITURES_ALL / PA_COST_DISTRIBUTION_LINES_ALL — downstream consumers of assignment-based expenditure defaults.

Together these relationships confirm that PA_PROJECT_ASGMTS_AR functions as the staffing and role-assignment hub within the Projects module, supporting resource management, approval workflows, and rate determination across Oracle EBS 12.1.1 and 12.2.2.