Search Results as_accesses_all_all

Overview

The AS_ACCESSES_ALL_ALL table is a core data object within the Oracle E-Business Suite Sales Foundation (AS) module, specifically in the OSM schema. It functions as the central repository for managing and storing access control records. Its primary role is to define and maintain the relationships between internal resources—such as employees and sales teams—and external business entities, including customers, sales leads, and opportunities. This table is fundamental to enforcing data security and visibility rules within the sales application, ensuring that users can only access the accounts, leads, and opportunities they are authorized to view or manage. The presence of "ALL" in the table name typically indicates it is a multi-organization enabled table, storing data across all operating units.

Key Information Stored

The table's structure is centered around linking a person or resource to a specific business object. The primary key is the ACCESS_ID, a unique system-generated identifier for each access record. The table's design captures several critical relationships through foreign key columns. The PERSON_ID column identifies the individual resource, often linked to the HR or resource management modules. The object being accessed is defined by a combination of columns such as CUSTOMER_ID, ADDRESS_ID, LEAD_ID, and SALES_LEAD_ID, which link to customer, address, and lead master data. Furthermore, the table supports partner and team-based access through columns like PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, and SALES_GROUP_ID, linking to partner entities and sales teams (JTF_RS_GROUPS_B). The SALESFORCE_ID column links directly to the sales resource definition (JTF_RS_RESOURCE_EXTNS).

Common Use Cases and Queries

A primary use case is generating reports on sales team coverage and account assignments. For instance, administrators may query which resources have access to a specific high-value customer. Another critical scenario involves data security validation, where custom reports verify that access rules align with organizational territory design. A common query pattern involves joining to customer and resource tables to list all accessible records for a given salesperson. For example, to find all customers a specific resource can access, one might use a SQL pattern such as: SELECT DISTINCT hz.party_name FROM as_accesses_all_all acc, hz_parties hz WHERE acc.person_id = :p_resource_id AND acc.customer_id = hz.party_id AND acc.customer_id IS NOT NULL;. This table is also pivotal during data migration and upgrades, as evidenced by its relationship with the PV_ACCESS_MIGRATION_LOG table.

Related Objects

The AS_ACCESSES_ALL_ALL table is a central hub with extensive foreign key relationships to major master data and transactional tables across EBS. Key documented relationships include:

• Customer Data: Links to HZ_PARTIES and RA_CUSTOMERS via CUSTOMER_ID, and to HZ_PARTY_SITES and RA_ADDRESSES_ALL via ADDRESS_ID.
• Lead Data: Links to AS_LEADS_ALL via LEAD_ID and to AS_SALES_LEADS via SALES_LEAD_ID.
• Resource and Team Data: Links to JTF_RS_RESOURCE_EXTNS via SALESFORCE_ID and to JTF_RS_GROUPS_B via SALES_GROUP_ID.
• Partner Data: Links to HZ_PARTIES and HZ_PARTY_SITES via PARTNER_CUSTOMER_ID and PARTNER_ADDRESS_ID.
• Dependent Objects: It is referenced as a parent table by AS_TERRITORY_ACCESSES (via ACCESS_ID) and PV_ACCESS_MIGRATION_LOG (via ACCESS_ID).

These relationships underscore its integral role in connecting sales force automation with customer, partner, and territory management systems.