Search Results asg_rowid

Overview

APPS.HR_ADP_EMP_REF_V is a public Oracle E-Business Suite view registered under the FND Design Data object PER.HR_ADP_EMP_REF_V. Its documented status is VALID, and it is classified as a public view that may be used for custom reporting or other data requirements. The view returns a list of employees together with their Government Reporting Entities (GREs) and exposes a derived column named COMPANY_CODE_EQUIVALENT, which is intended to be mapped to the ADP Company Code when using ADP Connection. In the version delivered with Oracle HR, COMPANY_CODE_EQUIVALENT is populated with GRE_ID. If the ADP Company Code is not implemented as a GRE in the customer environment, the view is expected to be customized to return the appropriate value in that column.

Because this view is referenced by other ADP interface extract views, any change to the derivation of COMPANY_CODE_EQUIVALENT is propagated to the COMPANY_CODE_EQUIVALENT values returned by those dependent views. This makes HR_ADP_EMP_REF_V a central reference point for ADP-related extract logic in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The documented view metadata for 12.2.2 identifies the following referenced base objects: HR_ADP (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), HR_SOFT_CODING_KEYFLEX (SYNONYM), PAY_PAYROLLS_F (VIEW), PER_ALL_ASSIGNMENTS_F (SYNONYM), PER_ALL_PEOPLE_F (SYNONYM), and PER_PERIODS_OF_SERVICE (SYNONYM). These objects supply the employee, assignment, period-of-service, payroll, and security information that the view consolidates. HR_SECURITY is significant because it enforces row-level access, ensuring the view returns only records the querying user is authorized to see. HR_GENERAL and HR_ADP provide supporting business logic, while HR_SOFT_CODING_KEYFLEX may be referenced for key flexfield-derived values such as the GRE when the ADP Company Code is modeled through a flexfield.

Key Columns

• COMPANY_CODE_EQUIVALENT (VARCHAR2, 60) — The ADP company code. Delivered as GRE_ID; the derivation is customizable.
• GRE_ID (VARCHAR2, 60) — The Government Reporting Entity identifier.
• EMPLOYEE_NUMBER (VARCHAR2, 30) and PERSON_ID (NUMBER, 10) — Employee identifiers.
• BUSINESS_GROUP_ID (NUMBER, 15) — Business group context.
• ASSIGNMENT_ID (NUMBER, 10), ASSIGNMENT_SEQUENCE, and PRIMARY_FLAG (Y/N) — Assignment identification and primary assignment indicator.
• SOCIAL_SECURITY_NUMBER (VARCHAR2, 30) — Employee SSN.
• FIRST_NAME (150), LAST_NAME (150), MIDDLE_NAMES (60), SUFFIX (30) — Name components.
• ASG_ROWID and PER_ROWID — Internal-use row identifiers.
• PERIOD_TYPE — Payroll periodicity (for example, Calendar Month).
• DATE_START, FINAL_PROCESS_DATE, LAST_UPDATE_DATE — Period-of-service dates.

Common Use Cases and Queries

The view is typically used to build ADP extract files, reconcile employee-to-company-code mappings, and validate that GREs align with the ADP Company Code. A representative query follows:

SELECT company_code_equivalent, employee_number, person_id,
       first_name, last_name, primary_flag, period_type
  FROM apps.hr_adp_emp_ref_v
 WHERE business_group_id = :p_business_group_id
   AND primary_flag = 'Y';

Because the view is security-aware, results are automatically restricted to the caller's authorized business groups. When the ADP Company Code is not modeled as a GRE, the view should be customized, and downstream ADP views will reflect the modified COMPANY_CODE_EQUIVALENT value.