Results for “fax_area_code”

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

Overview

The ICX_AS_EVENT_FAC_STAFF_V view is an Oracle E-Business Suite 12.1.1 / 12.2.2 database object owned by the APPS schema and registered under the ICX product family, which corresponds to Oracle iProcurement. It is described in the ETRM metadata as the "Event Facility Staff View" and holds VALID status in the data dictionary. The view exposes personnel assigned to event facilities, including their contact details such as telephone and fax numbers, and is intended to support reporting and integration requirements around event planning and facility staffing in the iProcurement application.

This view is a thin, single-table projection over the base table AS_EVENT_FAC_STAFF. No joins, filters, or computed expressions are applied; the view simply renames the underlying columns and presents them as an APPS-owned object. Because the column FAX_AREA_CODE is exposed directly, users searching on "fax_area_code" reach this view as the documented access point for fax area code information associated with event facility staff records.

Underlying Base Objects

The view is defined exclusively over AS_EVENT_FAC_STAFF, which is referenced in the ETRM documentation as a synonym. No other tables or views participate in the definition. The relationship is therefore one-to-one at the row level: each row returned by the view corresponds directly to a single row in the base table, with identical cardinality. Because the view contains no filter predicates, referential integrity checks or business-rule guards, callers obtain the unfiltered contents of the base table as visible through the APPS schema. All columns are enumerated explicitly in the view text rather than using a wildcard, which stabilizes the public column set for dependent code.

Key Columns

• EVENT_FAC_STAFF_ID — Primary identifier for the event facility staff assignment.
• EVENT_FACILITY_ID — Foreign-key reference to the event facility to which the staff member belongs.
• PRIMARY_FLAG — Indicates whether the staff member is the primary contact for the facility.
• STATUS_CODE — Lifecycle or status indicator for the staff record.
• LAST_NAME, FIRST_NAME, JOB_TITLE — Identity and role of the contact.
• AREA_CODE, PHONE_NUMBER, EXTENSION — Telephone contact details.
• FAX_AREA_CODE, FAX_PHONE_NUMBER — Fax contact details; the fax area code is a separate, explicit column, enabling direct filtering and extraction.
• COMMENTS — Free-text notes maintained against the staff record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield storage for extensible, customer-defined data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard auditing columns.

Common Use Cases and Queries

Typical scenarios include facility contact directories, event coordination reports, and interfaces that require fax or telephone details for event facility staff. A basic listing of staff for a facility is shown below.

• SELECT event_fac_staff_id, last_name, first_name, primary_flag, status_code FROM apps.icx_as_event_fac_staff_v WHERE event_facility_id = :facility_id;
• SELECT last_name, first_name, fax_area_code, fax_phone_number FROM apps.icx_as_event_fac_staff_v WHERE fax_area_code IS NOT NULL;
• SELECT event_fac_staff_id, job_title, area_code, phone_number, extension FROM apps.icx_as_event_fac_staff_v WHERE primary_flag = 'Y';

Because no filtering logic is embedded in the view, applications should supply their own STATUS_CODE and PRIMARY_FLAG predicates to avoid returning inactive or non-primary records. The view is stable across the referenced releases and can be queried safely from custom concurrent programs, reports, and integrations.