Search Results update_template

Overview

ASO_SUP_TEMPLATE_DATA_PVT is a private PL/SQL package in the Oracle E-Business Suite Order Management (ASO) module. It supports the supplementary template infrastructure used by Oracle Order Management to drive configurable, template-based ordering scenarios, such as quote and sales agreement templates. The package encapsulates the internal validation and persistence logic that governs supplement template context and level definitions. Its private classification (PVT) indicates it is an internal implementation package rather than a public API; it is not intended for direct invocation by external products or customers, though it may be referenced indirectly through public ASO APIs and their dependent forms and flows. The package header carries the source file identifier asovstmb.pls, with an original revision stamp of 2005, positioning it as stable, long-lived core code carried forward across the 12.1.1 and 12.2.2 releases without significant architectural change.

Key Procedures and Functions

The documented package exposes three procedures or functions, all centered on the lifecycle of supplementary template data:

• VALIDATE_TEMPLATE — A validation function that confirms a template context and template level are legitimate, active lookup values. The documented body shows it queries ASO_LOOKUPS for the ASO_SUP_TEMPLATE_CONTEXT lookup type and FND_LOOKUP_VALUES for the template level, checking enabled flags and effective dates. It returns a status indicator and logs diagnostic messages through ASO_DEBUG_PUB when the debug flag is enabled.
• CREATE_TEMPLATE — The creation routine invoked to insert a new supplementary template definition. In the context of the user's search term "create_template," this is the entry point that custom code or internal callers reach for when programmatically establishing template records.
• UPDATE_TEMPLATE — The complementary routine that modifies an existing template definition, allowing attribute or level changes to be persisted against an already-created template.

Tables Accessed

The documented metadata lists one directly referenced table via APPS synonym: FND_LOOKUP_VALUES. This is the standard Oracle Application Object Library lookup table, used here to validate template levels against the ASO_SUP_TEMPLATE_CONTEXT lookup type, scoped by view_application_id 697 and the user's language. The package body excerpt additionally shows a reference to ASO_LOOKUPS for context validation, though this appears as an alternate or legacy validation path. Effective date columns (start_date_active, end_date_active) are checked so that only currently valid lookup codes pass validation, ensuring template logic respects configured lookup maintenance windows.

Usage Notes

Because ASO_SUP_TEMPLATE_DATA_PVT is a private package, it is normally invoked from within the ASO module's own PL/SQL stack rather than directly by external developers. Callers access the "create_template" capability indirectly through public ASO supplementary template APIs or through Order Management setup forms that manage template definitions. Concurrent programs and order capture flows that need to validate or persist template context and level values may reach this package through those public wrappers. Developers writing custom extensions that must programmatically build supplementary templates should prefer documented public ASO APIs over this private package, since private packages may change between patch levels without notice. Debug output is gated by ASO_DEBUG_PUB.G_Debug_Flag, so enabling that flag is the standard method for tracing validation behavior during troubleshooting.