Search Results as_sales_member_pub




Overview
Explore in AI Chat

Overview

The APPS.AS_SALES_MEMBER_PUB package body is a public-API component of the Oracle EBS Sales Foundation module, delivered under the Applications (APPS) schema and validated as VALID in both release 12.1.1 and 12.2.2. Its classification as a PUB package identifies it as a supported, externally callable interface rather than a private implementation unit. The package fulfills a specialized role within the Sales Force and sales-team model: it translates identifiers and encoded values exchanged with external sales-automation systems — most notably Salesforce — into the internal representations used by Oracle's sales-member and sales-partner data structures, and vice versa. This translation layer is essential when EBS acts as the system of record for territory and sales-team assignments while an external CRM maintains its own identifier scheme.

The package body is documented as referencing AS_SALESFORCE_V, a view associated with Salesforce integration, confirming its purpose as a bridge between the Salesforce identifier model and native EBS sales-member data.

Key Procedures and Functions

The documented public interface consists of two program units:

  • CONVERT_SFID_TO_VALUES — Converts a Salesforce identifier (SFID) into the corresponding Oracle EBS values. This routine accepts an external system key and resolves it to the internal sales-member or partner attributes needed by downstream EBS processes.
  • CONVERT_PARTNER_TO_ID — Performs the inverse mapping, deriving an identifier from a sales partner or member record. This supports outbound synchronization, where EBS data must be expressed in the external system's key format.

Together these routines provide bidirectional key translation, allowing integrations to reconcile records originating in either system. Parameter lists are not exposed in the available metadata and should be confirmed against the package specification in the target instance.

Tables Accessed

The documented dependency list identifies AS_SALESFORCE_V as the principal data source, read to obtain Salesforce-side identifiers and associated values during conversion. The package also depends on PER_PEOPLE_F, the dated HR people view, reflecting the fact that sales-team members are held as employees or contacts in the HR model; person records are therefore resolved as part of the conversion. Standard EBS infrastructure objects are referenced as well, including AS_UTILITY_PVT, FND_API, FND_MSG_PUB, and the STANDARD package. Use of FND_MSG_PUB and FND_API indicates that the routines populate the standard message stack and honor the EBS API error-handling convention of returning a status code with accompanying messages. No base tables are documented as being modified; the package is presented as a read-and-resolve utility.

Usage Notes

Because AS_SALES_MEMBER_PUB is not referenced by any database object, it is not an internal dependency of other server-side code but is instead called from the outside — typically from custom integration code, concurrent programs, or web-service wrappers that synchronize Salesforce sales-team data with EBS. The documented reverse relationship is significant: the package body is referenced by 42 other packages, making it a widely consumed public interface whose signature should be treated as stable. Callers should invoke it within the standard EBS API pattern, checking the returned status and inspecting the FND_MSG_PUB message stack for errors. Because it mediates identifier translation, it is normally executed in batch or interface contexts rather than interactively, and any customization should avoid modifying the package body directly in favor of wrapper code that calls the documented public routines.