Search Results resource_address

Overview

CS_IB_EMPLOYEES_V is an Oracle E-Business Suite service module view owned by the APPS schema and classified as VALID. It is part of the CS (Service) product family and functions as a resource-oriented interface view within the Install Base / Service infrastructure. The view presents a unified, denormalized list of employee resources, exposing a resource name, resource number, resource identifier, a resource type literal, and a concatenated resource address. It is designed to feed service applications—such as field service dispatch, task assignment, and resource selection—with a lightweight, pre-joined source of employee resource records rather than requiring callers to join HR and address tables directly.

The view is significant for the search term "resource_address", because the concatenated RESOURCE_ADDRESS column is precisely what makes this view convenient for consumers that need a display-ready address string for each employee resource.

Underlying Base Objects

The documented view text is defined over two primary sources:

• HR_EMPLOYEES — the employee master entity, aliased E, supplying FULL_NAME, EMPLOYEE_NUM, and EMPLOYEE_ID.
• PER_ADDRESSES — the person address entity, aliased A, supplying the address components. The documented metadata lists PER_ADDRESSES as a synonym in APPS.

The join is expressed as an outer join on E.EMPLOYEE_ID = A.PERSON_ID (+), meaning employees without a matching address record are still returned, with address components evaluating to NULL. The view text also references supporting HR packages through the documented ETRM metadata: FND_PROFILE (PACKAGE), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), and HR_SECURITY (PACKAGE). These packages govern name formatting, profile option access, and row-level security, which affects which employee rows a given user may see.

Key Columns

• RESOURCE_NAME — the employee's full name (E.FULL_NAME).
• RESOURCE_NUMBER — the employee number (E.EMPLOYEE_NUM).
• RESOURCE_ID — the employee identifier (E.EMPLOYEE_ID).
• RESOURCE_TYPE — a literal 'EMPLOYEE', distinguishing this row from other resource types.
• RESOURCE_ADDRESS — the concatenation of ADDRESS_LINE1 through ADDRESS_LINE3, TOWN_OR_CITY, REGION_2, POSTAL_CODE, and COUNTRY. This is the column most relevant to the "resource_address" search.
• ORIGINAL_RESOURCE_ID — the originating employee identifier, duplicated from EMPLOYEE_ID.
• CONTACT_CATEGORY — a literal 'EMPLOYEE'.
• SORT_ORDER — a literal 'BBBB', used to order resources in a combined list.

Common Use Cases and Queries

Typical use is lookup and reporting of employee resources together with an address. A representative query retrieving employee resources by number is:

SELECT resource_id, resource_name, resource_number, resource_address FROM apps.cs_ib_employees_v WHERE resource_number = :p_emp_num;

To search for employees by address text (the "resource_address" scenario):

SELECT resource_name, resource_number, resource_address FROM apps.cs_ib_employees_v WHERE UPPER(resource_address) LIKE '%' || UPPER(:p_address) || '%';

Because RESOURCE_TYPE and CONTACT_CATEGORY are constants, the view is often unioned with similar resource views in service resource pickers, with the SORT_ORDER literal controlling presentation order. Row visibility respects HR security, so results reflect the calling user's authorized employee set.