Results for “as_event_names”
22 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AS_EVENT_NAMES is a multi-org secured view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the AS — Sales Foundation product family and exposes event name definitions, the reference data used by Oracle Sales and its related components to categorize business events such as opportunities, forecasts, and pipeline activities. In the standard EBS architecture the view is not itself a storing object; it presents a filtered, organization-scoped projection of an underlying _ALL table.
The view's principal role in reporting and integration is to provide a runtime security checkpoint. Because Sales Foundation data is partitioned by operating unit, the view masks records that fall outside the session's current organization context, returning only rows whose ORG_ID matches the organization derived from the user's CLIENT_INFO session value. This makes it the sanctioned access point for custom reports, Discoverer workbooks, OBIEE extracts, and inbound/outbound interfaces that must respect multi-org isolation without re-implementing security logic.
Underlying Base Objects
The view is defined over the single synonym AS_EVENT_NAMES_ALL, which resolves to the actual multi-org base table holding all organization-partitioned rows. The view text selects every functional and descriptive attribute column from that base object and applies a WHERE predicate of the form:
- NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)
The DECODE/SUBSTRB combination parses the first ten characters of the CLIENT_INFO environment string to obtain the current operating unit identifier. Rows whose ORG_ID is null are treated as seed or global data (mapped to -99) and are visible across organizations. The metadata records AS_EVENT_NAMES as VALID in the ETRM catalog, and the object is documented as multi-org enabled.
Key Columns
- EVENT_NAME_ID — Primary identifier for the event name record; the value users search on when resolving an ID to a name or joining to Sales Foundation transaction tables.
- NAME — The display name of the event.
- DESCRIPTION — Free-text explanation of the event's purpose.
- ORG_ID — Operating unit that owns the record; drives the multi-org filter.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns supporting audit and change tracking.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments available for customer-specific extensions.
Common Use Cases and Queries
A frequent requirement is to resolve the numeric event_name_id returned by a Sales Foundation query into its user-readable name. Because the view enforces organization security, the query should be run from a responsibility whose operating unit matches the record's ORG_ID.
- Lookup a single event:
SELECT event_name_id, name, description FROM as_event_names WHERE event_name_id = :p_id; - List all visible events:
SELECT event_name_id, name FROM as_event_names ORDER BY name; - Join to a transaction table:
SELECT e.name, t.* FROM as_event_names e, <sales_table> t WHERE t.event_name_id = e.event_name_id; - Validate multi-org visibility:
SELECT org_id, COUNT(*) FROM as_event_names GROUP BY org_id;
Integration developers should note that INSERT, UPDATE, and DELETE statements cannot be issued against this view; DML must target AS_EVENT_NAMES_ALL through the appropriate API or base-table access. When org context is not initialized, CLIENT_INFO parsing returns NULL and only global (ORG_ID null) rows are returned. This behavior is the documented multi-org pattern for the object and should be preserved in any custom code.
-
View: AS_EVENT_NAMES 12.1.1
Event names (multi-org)
APPS.AS_EVENT_NAMES·↳ AS_EVENT_NAMES_ALL·Explore AS module →
-
View: AS_EVENT_NAMES 12.2.2
Event names (multi-org)
APPS.AS_EVENT_NAMES·↳ AS_EVENT_NAMES_ALL·Explore AS module →
-
VIEW: APPS.AS_EVENT_NAMES 12.2.2
-
VIEW: APPS.AS_EVENT_NAMES 12.1.1
-
12.1.1 DBA Data 12.1.1
-
View: AS_EVENT_MERGE_V 12.1.1
Event merge view
Not implemented in this database·Explore AS module →
-
View: AS_EVENT_MERGE_V 12.2.2
Event merge view
Not implemented in this database·Explore AS module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
View: ICX_AS_EVENTS_V 12.1.1
Events View
Not implemented in this database·Explore ICX module →
-
View: ICX_AS_EVENTS_V 12.2.2
Events View
Not implemented in this database·Explore ICX module →
-
View: AS_EVENTS_V 12.1.1
Events view
Not implemented in this database·Explore AS module →
-
View: AS_EVENTS_V 12.2.2
Events view
Not implemented in this database·Explore AS module →
-
12.2.2 FND Design Data 12.2.2
-
eTRM - AS Tables and Views 12.2.2
- Retrofitted
-
eTRM - AS Tables and Views 12.1.1
- Retrofitted
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - AS Tables and Views 12.2.2
- Retrofitted
-
eTRM - AS Tables and Views 12.1.1
- Retrofitted