Search Results delete_salesteams

Overview

The APPS.AS_OPPORTUNITY_PUB_W4 package is a public PL/SQL API within the Oracle E-Business Suite Sales (AS) module, classified under the ETRM as an OTHER-type API and owned by the APPS schema. It is one of a series of wrapper packages (denoted by the "_W4" suffix) that consolidate bulk operations against Opportunities and their associated contact and sales team assignments. The package is declared AUTHID CURRENT_USER, meaning that privileges are evaluated against the invoking schema rather than the defining APPS schema, which is consistent with Oracle's public API design convention for controlled access to base tables.

The header identifies the source file as asxwop4s.pls (version 120.2, dated 2005/08/04), indicating that the package has been stable since the 11i/early R12 code line and remains available in 12.1.1 and 12.2.2. It exposes a matrix of JTF collection-typed parameters (JTF_NUMBER_TABLE, JTF_DATE_TABLE, JTF_VARCHAR2_TABLE_100/200/300) that allow callers to pass array-based payloads, enabling high-volume create and update operations in a single call rather than row-by-row processing.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• CREATE_CONTACTS — Bulk creation of opportunity contacts, accepting version, initialization, commit, and validation flags plus JTF typed arrays representing contact attributes and role assignments.
• UPDATE_CONTACTS — Bulk modification of existing opportunity contact records, using the same array-based pattern to update multiple contacts in one invocation.
• DELETE_CONTACTS — Removal of opportunity contact associations. This is the procedure most commonly located via the search term "delete_contacts" and is the primary entry point for de-associating contacts from an opportunity.
• DELETE_SALESTEAMS — Removal of sales team member assignments from an opportunity, following the same bulk deletion pattern.
• COPY_OPPORTUNITY — Duplication of an opportunity, including dependent contact and sales team lines, supporting the "copy" business flow.
• GET_ACCESS_PROFILES — Retrieval of access/security profiles applicable to a given opportunity context, used to drive record-level access decisions.
• GET_PROFILE — Retrieval of profile option values relevant to opportunity processing.

Standard API parameters recur across the create/update/delete routines: p_api_version_number, p_init_msg_list, p_commit, and p_validation_level, together with identity, check-access, admin, and partner contact party identifiers.

Tables Accessed

ETRM does not enumerate base tables for this package because all access is resolved through APPS synonyms on the underlying AS and JTF tables (for example, the opportunity header, opportunity contact, and sales team tables). The delete procedures write to the opportunity contact and sales team intersection tables, while the get procedures read access and profile configuration data. Because access is channeled via APPS synonyms, the package does not require explicit grants on base tables when invoked by application code.

Usage Notes

This package is not referenced by any other documented package per ETRM metadata, and it is not typically called directly by concurrent programs or Oracle Forms. In practice it is invoked from custom PL/SQL integration code, business event subscriptions, or Oracle's internal opportunity processing logic that requires array-based DML. When calling DELETE_CONTACTS, the caller should set p_init_msg_list to FND_API.G_TRUE to clear the message stack, manage transaction control explicitly via p_commit, and always interrogate the returned message stack for validation failures before committing. Direct DML against the underlying opportunity contact tables is strongly discouraged in favour of this API.