Results for “hr_adp_address_v”

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

Overview

HR_ADP_ADDRESS_V is a read-only database view owned by the APPS schema within the PER (Human Resources) product module of Oracle E-Business Suite. It is an ADP payroll interface view, purpose-built to supply address and organizational data in a layout compatible with ADP payroll processing. The view joins employee assignment, person, address, payroll, organization, and payroll time period information into a single, denormalized result set that can be handed off directly to an ADP extract routine. It is validated in the EBS 12.1.1 and 12.2.2 releases.

The view plays a supporting role in the broader ADP integration delivered through the HR_ADP package. Where HR_ADP exposes the extraction logic, HR_ADP_ADDRESS_V provides the address-oriented projection of that data, including company codes, GRE (Government Reporting Entity) names and identifiers, employee numbers, and formatted US-style addresses. Because it is a view rather than a table, it applies no storage of its own and always reflects the current transactional state of the underlying HR tables. The user search term "gre_name" corresponds directly to the GRE_NAME column exposed by this view, which is sourced from the organization name on HR_ALL_ORGANIZATION_UNITS and joined through the soft coding keyflex structure.

Underlying Base Objects

The documented base objects underlying HR_ADP_ADDRESS_V are HR_ADP (package), HR_ADP_EMP_REF_V (view), HR_ALL_ORGANIZATION_UNITS (synonym), HR_GENERAL (package), HR_SECURITY (package), HR_SOFT_CODING_KEYFLEX (synonym), PAY_PAYROLLS_X (view), PER_ADDRESSES (synonym), PER_ALL_ASSIGNMENTS_F (synonym), PER_ALL_PEOPLE_F (synonym), and PER_TIME_PERIOD_TYPES (synonym).

• PER_ALL_ASSIGNMENTS_F supplies the primary assignment, payroll, effective-dated assignment type, and soft coding keyflex references; the view restricts to primary, employee-type assignments with the latest effective start date.
• PER_ALL_PEOPLE_F supplies the person identifier and employee number.
• PER_ADDRESSES supplies the address lines, city, state, country, and postal code, filtered by address style US or US_GLB.
• HR_SOFT_CODING_KEYFLEX provides SEGMENT1 as GRE_ID and links to the organization unit that supplies GRE_NAME.
• PAY_PAYROLLS_X and PER_TIME_PERIOD_TYPES derive the payroll pay frequency (W, S, B, M).
• HR_ADP, HR_GENERAL, and HR_SECURITY provide the extraction date and security context used in the WHERE clause.

Key Columns

• GRE_NAME — the Government Reporting Entity name, from HOU.NAME, the column referenced by the "gre_name" search.
• GRE_ID — segment1 of the soft coding keyflex representing the GRE identifier.
• COMPANY_CODE_EQUIVALENT — company code from the HR_ADP_EMP_REF_V reference view.
• ORGANIZATION_ID, BUSINESS_GROUP_ID, PERSON_ID, EMPLOYEE_NUMBER — core HR identifiers for the individual and their organizational context.
• PAY_FREQUENCY — decoded from periods per fiscal year to W, S, B, or M.
• ADDRESS_ID, ADDRESS_PRIMARY_FLAG, ADDRESS_TYPE, DATE_FROM, DATE_TO — address identity and validity data.
• ADDRESS_LINE1..3, CITY, STATE, ZIP_CODE, COUNTRY — the formatted US-style address fields projected for ADP.

Common Use Cases and Queries

The view is typically consumed by ADP extract processes and by diagnostic reports verifying that employee address and GRE data are complete before a payroll interface run. A representative query retrieving the GRE name and address for an employee follows.

SELECT gre_name, gre_id, employee_number, address_line1, city, state, zip_code, country FROM apps.hr_adp_address_v WHERE employee_number = :p_employee_number;

To list all employees mapped to a given GRE:

SELECT gre_name, employee_number, pay_frequency, address_line1 FROM apps.hr_adp_address_v WHERE gre_name = :p_gre_name ORDER BY employee_number;

To audit current primary addresses for the extract:

SELECT employee_number, address_primary_flag, city, state, zip_code FROM apps.hr_adp_address_v WHERE address_primary_flag = 'Y';

Because the view enforces filters for primary employee assignments, US address styles, and the current ADP extract date, queries against it return only records eligible for ADP processing, making it suitable for reconciliation and pre-interface validation.