Search Results validate_accessprofiles

Overview

AS_ACCESS_PUB_W is the public wrapper package that front-ends the Oracle E-Business Suite Sales Foundation access-profile engine and the sales-team administration APIs. It belongs to the AS (Sales) product family and is owned by the APPS schema. In Oracle EBS 12.1.1 and 12.2.2 the package serves two closely related business purposes: it exposes the runtime security predicates that determine whether a given resource (customer, lead, opportunity, person, or organization) is visible or modifiable to the current user, and it provides the maintenance entry points for sales-team assignments that drive those visibility rules. The "_W" suffix denotes the generated Rosetta wrapper layer, meaning the package presents the canonical public signature while the substantive logic resides in the underlying as_access_pub body. Access profiles are the central mechanism by which EBS restricts sales users to subsets of customers and to specific sales teams, so this package is effectively the runtime gatekeeper for Sales, Telesales, and related application modules.

The docum

Key Procedures and Functions

The documented interface contains eighteen subprograms. Two are Rosetta plumbing routines: ROSETTA_TABLE_COPY_IN_P2 and ROSETTA_TABLE_COPY_OUT_P2 marshal bulk PL/SQL collection data into and out of the internal sales_team_tbl_type record structure, allowing set-based processing of sales-team rows across the Java/BC4J boundary. Three procedures manage sales-team membership: CREATE_SALESTEAM, UPDATE_SALESTEAM, and DELETE_SALESTEAM, which insert, amend, and remove sales-team assignments and are the write-side counterparts to the access checks.

The validation routine VALIDATE_ACCESSPROFILES is the subprogram most commonly sought by developers, since it is the documented entry point for confirming that a supplied access-profile configuration is internally consistent and permissible before it is committed or applied. The remaining twelve functions are boolean-style access predicate helpers. HAS_VIEWCUSTOMERACCESS and HAS_UPDATECUSTOMERACCESS test customer visibility and modification rights. HAS_VIEWLEADACCESS, HAS_UPDATELEADACCESS, HAS_VIEWOPPORTUNITYACCESS, and HAS_UPDATEOPPORTUNITYACCESS perform the equivalent tests for leads and opportunities. HAS_VIEWPERSONACCESS and HAS_UPDATEPERSONACCESS cover person records, while the generic predicates HAS_ORGANIZATIONACCESS, HAS_PERSONACCESS, HAS_LEADACCESS, and HAS_OPPORTUNITYACCESS evaluate access against a specific organization, person, lead, or opportunity identifier. Together these functions let calling code ask a single, authoritative question—may this user act on this record?—instead of reimplementing sales-team and access-profile joins.

Tables Accessed

The package accesses the PLITBLM table (reached through an APPS synonym), the standard EBS PL/SQL index-by-table scratch structure used during bulk DML and bulk collection processing. Sales-team and access-profile data proper is held in the Sales Foundation tables that as_access_pub reads and writes internally, including the sales-team and access-profile assignment entities; the wrapper layer itself only touches PLITBLM directly for its bulk operations.

Usage Notes

AS_ACCESS_PUB_W is invoked primarily by Oracle Forms and OA Framework pages within the Sales and Telesales modules when rendering customer, lead, and opportunity lists, and by concurrent programs and custom extensions that must apply the same access rules programmatically. It is referenced by one other package in the documented metadata. Custom code should call the HAS_* predicates rather than querying sales-team tables directly, because those functions encapsulate the access-profile hierarchy and the assignment's active date range. VALIDATE_ACCESSPROFILES should be called before persisting an access-profile setup through CREATE_SALESTEAM or UPDATE_SALESTEAM so that invalid configurations are rejected at source. Because this is a Rosetta-generated specification, the signature and types are stable across 12.1.1 and 12.2.2, and any direct modification of the package body is unsupported.