Results for “as_event_facilities”

36 results




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

Overview

AS_EVENT_FACILITIES is a multi-org secured view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AS (Sales Foundation) product family, which provides the shared trading-partner and event infrastructure used by Oracle Advanced Pricing, Order Management, and related modules. The view exposes event facility records — physical or logical venues associated with trade events, seminars, and promotions — together with their addresses, contact details, and descriptive attributes.

The view is registered in the ETRM as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its primary role is to present facility data to application forms, concurrent programs, and reporting tools while transparently enforcing operating unit (ORG) security. Because the multi-org predicate is embedded in the view definition rather than applied by the consuming report, any query or integration that selects from AS_EVENT_FACILITIES automatically receives only the facility rows accessible to the session's current organization context.

Underlying Base Objects

The view is defined over a single documented base object: the synonym AS_EVENT_FACILITIES_ALL. The _ALL suffix indicates that the underlying table stores facility records across all operating units, with organization ownership recorded in the ORG_ID column. AS_EVENT_FACILITIES is therefore a filtered projection of that table, not a join or aggregation.

The filtering logic inspects the server-side CLIENT_INFO value through USERENV, extracts the first ten characters, converts them to a number, and compares the result against ORG_ID. Rows with a NULL ORG_ID — typically global or shared facilities — are matched using an NVL fallback of -99, ensuring that organization-independent records remain visible from every operating unit. Queries issued outside a properly initialized multi-org session may therefore return only the shared rows.

Key Columns

  • EVENT_FACILITY_ID — Surrogate primary key uniquely identifying each facility.
  • CODE and NAME — User-defined short code and descriptive name of the facility.
  • ENABLED_FLAG — Indicates whether the facility is active and available for selection.
  • RANK_CODE and TYPE_CODE — Classification values used to order or categorize facilities within event and pricing setups.
  • COMMENTS and DIRECTIONS — Free-text notes and travel or access directions for the venue.
  • ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, COUNTRY_CODE — Structured postal address of the facility.
  • AREA_CODE, PHONE_NUMBER, EXTENSION — Telephone contact information.
  • ORG_ID — Operating unit that owns the facility; the driving column of the multi-org security predicate.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns for customer-specific extensions.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard who-column tracking.

Common Use Cases and Queries

The most frequent use case is validating and reporting on the facilities available to a given operating unit for event or promotion planning. The following query lists all enabled facilities visible in the current multi-org context, ordered by rank:

  • SELECT event_facility_id, code, name, city, country_code FROM as_event_facilities WHERE enabled_flag = 'Y' ORDER BY rank_code, name;

A point lookup by code is common in integration and validation routines:

  • SELECT event_facility_id, name, type_code, org_id FROM as_event_facilities WHERE code = :facility_code;

Because organization security is embedded in the view, integration accounts that connect directly at the database tier must ensure CLIENT_INFO is initialized before selecting, or they will see only shared (NULL ORG_ID) rows. Reports that must span all operating units should query AS_EVENT_FACILITIES_ALL instead, applying their own organization filters explicitly. Where descriptive flexfield data is required, join to the appropriate FND_DFF tables using ATTRIBUTE_CATEGORY in the same manner as other Sales Foundation entities.