Search Results validate_methodology_code

Overview

AS_OPP_HEADER_PVT is a private PL/SQL package in the Oracle E-Business Suite APPS schema that underpins the Opportunity Header entity within Oracle Sales (AS) and the TeleSales/Leads foundation. The package encapsulates the core business logic for creating, updating, deleting, and validating opportunity header records, which represent the master record of a sales opportunity — its lead identifier, status, sales stage, channel, currency, close reason, win probability, and associated methodology. As a private (PVT) package, it is not intended for direct invocation by external callers; rather, it exists as the implementation layer behind the public opportunity API surface (AS_OPPORTUNITY_PUB) and related Sales application forms. The package is declared with AUTHID CURRENT_USER, so it executes with the privilege set of the calling user, and it defines a fetch batching constant, G_DEFAULT_NUM_REC_FETCH, defaulting to 30 records per call.

Key Procedures and Functions

The documented API entry point is CREATE_OPP_HEADER. It is a private procedure whose parameter signature fixes the standard Oracle API conventions: an API version number (required), an initialization message list flag and a commit flag (both optional, defaulting to FND_API.G_FALSE), a validation level defaulting to FND_API.G_VALID_LEVEL_FULL, access and administrative control flags, a profile table type from AS_UTILITY_PUB, partner contact and sales group identifiers, and the Header_Rec_Type record drawn from AS_OPPORTUNITY_PUB. It returns the created lead identifier, return status, message count, and message data.

Alongside CREATE_OPP_HEADER, the package supplies UPDATE_OPP_HEADER and DELETE_OPP_HEADER, which apply the same API framework to modification and removal of opportunity headers. A large family of single-attribute validation routines enforces data integrity before persistence. These include VALIDATE_LEAD_ID, VALIDATE_LEAD_NUMBER, VALIDATE_ORIGINAL_LEAD_ID, VALIDATE_STATUS, VALIDATE_DELETED_FLAG, VALIDATE_NO_OPP_ALLOWED_FLAG, and VALIDATE_DELETE_ALLOWED_FLAG, which govern the identity, lifecycle state, and deletion eligibility of the record. Descriptive attributes are validated by VALIDATE_SALES_STAGE_ID, VALIDATE_METHODOLOGY_CODE, VALIDATE_CHANNEL_CODE, VALIDATE_LEAD_SOURCE_CODE, VALIDATE_SOURCE_PROMOTION_ID, VALIDATE_CURRENCY_CODE, VALIDATE_PRICE_LIST_ID, VALIDATE_WIN_PROBABILITY, VALIDATE_CLOSE_REASON, and VALIDATE_DECN_TIMEFRAME_CODE.

Tables Accessed

The package reads and writes through APPS synonyms. The core opportunity and lead data resides in AS_LEADS_ALL, AS_LEAD_LINES_ALL, and AS_LEAD_COMP_PRODUCTS, with AS_SALES_CREDITS holding sales credit assignments. Validation lookups draw on AS_SALES_STAGES_ALL_B (sales stages), AS_SALES_METH_STAGE_MAP (methodology-to-stage mapping), AS_STATUSES_B (statuses), AMS_SOURCE_CODES (lead sources), FND_CURRENCIES and FND_LOOKUP_VALUES for standard code validation, and HZ_PARTIES and HZ_PARTY_SITES for party and site references. Resource-related validation uses JTF_RS_GROUPS_B, JTF_RS_GROUP_MEMBERS, and JTF_RS_RESOURCE_EXTNS.

Usage Notes

Because AS_OPP_HEADER_PVT is classified as a private API, it is normally invoked indirectly — through the public opportunity API layer, Oracle Sales forms, or concurrent processing that requires opportunity maintenance. The metadata records that it is referenced by one other package. The search term "g_create" points to global/constant declarations used within the package scope for internal logic rather than to a documented public procedure. Customizations should call the public wrappers and preserve the API version, initialization, and validation-level conventions shown here rather than invoking this private package directly.