Results for “org_info_c”

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

Overview

APPS.PA_R_PROJECT_RESOURCES_V is a Projects (PA) module reporting view that presents the pool of project resources — primarily employees — available for assignment to project work. It consolidates human-resources attributes (person, assignment, job, and organization data) with project-resource transaction indicators drawn from Oracle Projects. The view is a core data source for resource-management and staffing reports, and for integrations that must resolve a person to a valid resource, a default operating unit, and an assignment calendar.

The view is owned by APPS and is documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2. Because it joins a large number of HR and Projects base objects, it is typically consumed read-only as a reporting or lookup surface rather than as a maintenance interface.

Underlying Base Objects

The view is defined over the following documented base objects:

• PER_ALL_ASSIGNMENTS_F — the assignment records that anchor each resource row via PERSON_ID and ORGANIZATION_ID.
• PER_ALL_PEOPLE_F — person name, employee number, e-mail, phone, and business group.
• HR_ORGANIZATION_INFORMATION — referenced twice, as ORG_INFO and ORG_INFO_C, to derive the default operating unit and calendar.
• PER_ASSIGNMENT_STATUS_TYPES — restricts the view to ACTIVE_ASSIGN and ACTIVE_CWK system statuses.
• PER_PERSON_TYPES and PER_PERSON_TYPE_USAGES_F — system and user person types.
• PER_PERIODS_OF_SERVICE and PER_PERIODS_OF_PLACEMENT — unioned to supply termination dates.
• PER_JOBS and PER_JOB_EXTRA_INFO — job name and job group.
• PA_ALL_ORGANIZATIONS, PA_RESOURCE_TXN_ATTRIBUTES, and the PA_EXPENDITURES_UTILS package — Projects-specific organization and transaction context.

Key Columns

• PERSON_ID — identifier of the resource.
• NAME — person full name, truncated to 60 characters.
• ORGANIZATION_ID — the HR organization to which the assignment belongs.
• ASSIGNMENT_START_DATE / ASSIGNMENT_END_DATE — the assignment's effective date range.
• TERMINATION_DATE — taken from the person's period of service or placement.
• OR_INFO_C-derived CALENDAR_ID — n/a
• DEFAULT_OU — default operating unit derived from org_info.org_information1.
• CALENDAR_ID — calendar derived from org_info_c.org_information1, the column surfaced by the searcher's term "org_info_c".
• P_TYPE / USER_TYPE — system and user person types.
• RES_EXISTS — flag indicating whether a project resource transaction attribute exists.
• PER_EMP_NUMBER, PER_EMAIL, PER_WORK_PHONE — employee contact details.
• JOB_NAME, JOB_GROUP_ID, SUPERVISOR_ID, LOCATION_ID — job, grouping, and reporting relationships.
• RESOURCE_TYPE — literal value 'EMPLOYEE'.
• ORG_NAME — business-group name returned by PA_EXPENDITURES_UTILS.GETORGTLNAME.

Common Use Cases and Queries

Typical uses include resource-availability reporting, staffing lookups by job or organization, and integrations that need to resolve an employee to a default operating unit and calendar.

• Listing active project resources by organization:
• SELECT person_id, name, job_name, default_ou FROM apps.pa_r_project_resources_v WHERE organization_id = :org_id;
• Retrieving the assignment calendar and default OU for a person, which is the scenario tied to the search term "org_info_c":
• SELECT person_id, name, calendar_id, default_ou FROM apps.pa_r_project_resources_v WHERE person_id = :person_id;
• Filtering resources by job group or status:
• SELECT person_id, name, job_group_id FROM apps.pa_r_project_resources_v WHERE job_group_id = :job_group_id;
• Identifying resources with existing project transaction attributes:
• SELECT person_id, name FROM apps.pa_r_project_resources_v WHERE res_exists = 'EXISTS';

Because the view already restricts to ACTIVE_ASSIGN and ACTIVE_CWK assignments, queries generally do not need additional status filtering.