Search Results as_accesses




Overview
Explore in AI Chat

Overview

AS_ACCESSES is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AS – Sales Foundation product family. The view exposes employee access records for accounts and opportunities and is described in the Oracle ETRM documentation as multi-org enabled. In 12.1.1 and 12.2.2 it presents a filtered projection of the underlying access data, and its object status is documented as VALID. It is not a table in its own right; it is a read-only query layer intended to simplify access by application code, reports, and interfaces.

Its most significant structural characteristic is the built-in filter on DELETE_FLAG. Because soft-deleted access records are excluded, the view presents only currently active access assignments. This makes it the recommended entry point for any reporting requirement that must reflect live team membership rather than the full historical access population.

Underlying Base Objects

The view is defined over a single referenced base object, the synonym AS_ACCESSES_ALL_ALL, which resolves to the underlying multi-org access table in the AS schema. The projection selects all significant business and audit columns from that object and applies the predicate DELETE_FLAG IS NULL. Consequently, any row visible in AS_ACCESSES exists in AS_ACCESSES_ALL_ALL and is not logically deleted.

Because the base object carries the multi-org discriminator ORG_ID, the view is also multi-org aware. Querying it does not automatically enforce operating unit security; callers must filter on ORG_ID, or rely on row-level security applied at the base object level, to restrict results to the appropriate operating unit. Audit columns such as LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN are passed through unchanged, as are the concurrent program context columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on active account and opportunity team membership, validating salesforce role assignments, reconciling access after reassignment, and extracting access data for downstream integration or data warehousing. The following query returns current team leader assignments for a given account within a single operating unit:

SELECT access_id, customer_id, person_id, salesforce_role_code, team_leader_flag
FROM apps.as_accesses
WHERE customer_id = :customer_id
AND org_id = :org_id
AND team_leader_flag = 'Y';

A second, frequently used pattern retrieves all active opportunity access for a resource:

SELECT a.access_id, a.lead_id, a.access_type, a.creation_date
FROM apps.as_accesses a
WHERE a.person_id = :person_id
AND a.org_id = :org_id;

Because the DELETE_FLAG predicate is already applied, no additional deletion filter is required. However, callers requiring soft-deleted or historical records must query AS_ACCESSES_ALL_ALL directly. The view is Oracle proprietary and confidential, and all published access should respect the documented implementation notes for the 12.1.1 and 12.2.2 releases.