Search Results create_access

Overview

APPS.AMS_ACCESS_PVT is a private PL/SQL package within the Oracle E-Business Suite Marketing (AMS) module that manages access control records for marketing entities. It governs which users or roles may view, update, approve, own, or administer specific marketing objects such as campaigns, event headers, event offers, offers, and funds. The package is declared with AUTHID CURRENT_USER and sources its logic from amsvaccs.pls (version 115.25). Its API classification is PVT, meaning it is intended primarily as an internal implementation layer invoked by other public APIs and forms rather than as a standalone entry point. In EBS 12.1.1 and 12.2.2 the package remains the backbone of marketing security, resolving user-or-role grants, date-bounded active ranges, and administrative overrides for the AMS access model. The primary record structure, access_rec_type, encapsulates all attributes of an access row, including activity access ID, object reference, user or role identity, active-from and active-to dates, and the ADMIN, APPROVER, OWNER, DELETE, and ACTIVE flag columns.

Key Procedures and Functions

The package exposes a one of the most frequently searched procedures, CREATE_ACCESS, along with fifteen other documented procedures and functions. CREATE_ACCESS inserts a new access record passed through p_access_rec and returns the generated x_access_id; it enforces a default object version number of 1, checks uniqueness when an access ID is supplied, generates a key from a sequence when omitted, and validates flag columns as 'Y' or 'N'. UPDATE_ACCESS modifies existing access rows, and DELETE_ACCESS removes them. LOCK_ACCESS provides concurrency control by locking an access record. Validation routines include VALIDATE_ACCESS, CHECK_ACCESS_RECORD, CHECK_ACCESS_ITEMS, and INIT_ACCESS_REC and COMPLETE_ACCESS_REC, which initialize and complete the record structure before persistence. Security-oriented routines include CHECK_FUNCTION_SECURITY, CHECK_OWNER, CHECK_UPDATE_ACCESS, CHECK_VIEW_ACCESS, CHECK_ADMIN_ACCESS, and UPDATE_OBJECT_OWNER. GET_SOURCE_CODE retrieves source code values. Each is designed to be called within the AMS API stack and follows Oracle's standard API parameter conventions.

Tables Accessed

The package reads and writes through APPS synonyms to AMS_ACT_ACCESS, the base access table, and its support objects AMS_ACT_ACCESS_S (sequence) and AMS_ACT_ACCESS_DENORM (denormalized access). Object ownership and marketing context are validated against AMS_CAMPAIGNS_ALL_B, AMS_EVENT_HEADERS_ALL_B, AMS_EVENT_OFFERS_ALL_B, OZF_OFFERS, and OZF_FUNDS_ALL_B. Role and group resolution uses JTF_RS_GROUPS_DENORM and JTF_RS_GROUP_MEMBERS. Source code validation relies on AMS_SOURCE_CODES, with DUAL and PLITBLM supporting PL/SQL-level operations.

Usage Notes

AMS_ACCESS_PVT is referenced by roughly thirty other packages, indicating its central role in the marketing security stack. It is typically invoked by AMS public APIs, by the Oracle Marketing forms when a user creates or edits campaign, event, or offer access, and by concurrent programs that seed or reconcile access records. Custom code should call it only after validating the surrounding AMS business context, honoring the rule against passing FND_API message tokens, and supplying either a valid access ID for uniqueness checking or leaving it null for sequence generation.