Search Results get_application_short_name

Overview

QP_DEFAULT_SSC is a PL/SQL package body owned by APPS in the Oracle E-Business Suite. It forms part of the Oracle Advanced Pricing (QP) module and is classified in the ETRM metadata under API classification OTHER. The package provides defaulting behavior for the Supplemental Selling Context (SSC) record structure defined in QP_ATTR_MAP_PUB, specifically the Ssc_Rec_Type. Its role is to supply default values and normalization logic for SSC attributes used in pricing and attribute mapping operations. The package declares a global constant G_PKG_NAME used to identify the package in error and log messages, and a private global variable g_SSC_rec of type QP_Attr_Map_PUB.Ssc_Rec_Type that holds the working SSC record manipulated by the package's logic.

The metadata indicates that the package exposes a small set of getter-style functions along with one record-population procedure. Several functions are deliberately implemented as stubs returning NULL, indicating that in the current release the package relies either on external defaulting sources or on future extension points rather than providing business defaults itself.

Key Procedures and Functions

The ETRM metadata documents a single procedural entry, ATTRIBUTES, along with a set of related functions that together constitute the package's documented surface. The functions identified in the source excerpt include:

• Get_Application_Short_Name — returns a VARCHAR2 value representing the application short name associated with the SSC defaulting context. In the shipped source this function returns NULL, indicating no application-level default is applied.
• Get_Enabled — returns a VARCHAR2 flag indicating whether the SSC defaulting feature is enabled. The shipped implementation returns NULL.
• Get_Pte — returns a VARCHAR2 value associated with the Pricing Transaction Entity (PTE) default. The shipped implementation returns NULL.
• Get_Pte_Source_System — returns a NUMBER. Unlike the other getters, this function is implemented and obtains the next value from the QP_PTE_SOURCE_SYSTEM_S sequence, storing it in a local variable and returning it. This provides a generated source system identifier for PTE processing.
• Get_Flex_Ssc — a procedure that normalizes the descriptive flexfield (DFF) attributes on g_SSC_rec. It iterates over the attribute1 through attribute15 columns and converts any value equal to FND_API.G_MISS_CHAR into NULL, ensuring that the sentinel "missing" value is not persisted or propagated downstream. Comments in the source note that flex APIs for defaults may be called in the future, marking this procedure as an extension point.

Tables Accessed

The documented metadata lists two referenced objects, both accessed through APPS synonyms:

• QP_PTE_SOURCE_SYSTEM_S — the sequence used by Get_Pte_Source_System to generate a new source system identifier via SELECT ... FROM DUAL. The sequence forms part of the pricing transaction entity infrastructure.
• DUAL — used as the single-row source for the sequence nextval selection.

No other tables are documented as directly referenced by this package. The flex attribute normalization performed in Get_Flex_Ssc operates on the in-memory g_SSC_rec structure rather than on a database table.

Usage Notes

QP_DEFAULT_SSC is invoked within Oracle Advanced Pricing when a Supplemental Selling Context record must be defaulted or normalized before being passed to the attribute mapping APIs in QP_ATTR_MAP_PUB. Typical callers include pricing setup forms and internal pricing APIs that build SSC records and require defaults for application short name, enabled status, PTE, and flex attributes. The package is also referenced by one other package, indicating a dependency within the pricing attribute mapping layer.

Because the package is an internal implementation object and not a public API, custom code should avoid calling it directly. Developers extending Advanced Pricing should instead use the documented public APIs in QP_ATTR_MAP_PUB and related packages. The NULL-returning getters indicate that the current release does not impose business defaults for those values, and Get_Flex_Ssc exists primarily to cleanse G_MISS_CHAR sentinels before the SSC record is consumed by downstream attribute mapping logic. The package is compatible with EBS 12.1.1 and 12.2.2, with the source header indicating it was last modified in the 2005 timeframe (version 120.2).