Search Results asg_custom_pub

Overview

ASG_CUSTOM_PUB is a public PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The package forms part of the Oracle Advanced Supply Chain Planning (ASCP) and Global Order Promising infrastructure, where the ASG_ prefix denotes components belonging to the Advanced Supply Chain Planning / Advanced Planning Foundation layer. Its documented status is VALID, and its API classification is PUB, indicating that it exposes a supported public interface intended for invocation by external callers rather than serving strictly as a private implementation detail.

The business purpose of ASG_CUSTOM_PUB is to provide a controlled entry point for customizing planning data items and for flagging data as dirty so that downstream planning engines recognize and reprocess the affected records. In the ASCP model, the customization layer allows implementers to extend or override standard planning behavior without modifying seeded Oracle code. ASG_CUSTOM_PUB acts as the wrapper that marshals such customizations into the internal ASG_CUSTOM_PVT layer.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within ASG_CUSTOM_PUB. The principal documented entry points are:

• CUSTOMIZE_PUB_ITEM — Applies customization logic to a specified planning item, allowing customer-specific attributes or overrides to be introduced into the planning data model through the supported public API surface.
• MARK_DIRTY — Marks one or more planning records as dirty, signalling to the planning engine that the associated data must be re-evaluated and reprocessed during the next planning run.

The metadata records six procedures/functions in total, with CUSTOMIZE_PUB_ITEM and MARK_DIRTY being the named public entry points. The remaining routines support the public interface internally and are not enumerated individually in the documentation excerpt. Parameter lists are deliberately not reproduced here, as they are not part of the documented metadata; consumers should refer to the packaged specification for exact signatures.

Tables Accessed

The ETRM dependency record for ASG_CUSTOM_PUB does not enumerate directly referenced base tables. The documented dependencies are code objects rather than data tables, specifically: ASG_CUSTOM_PVT (the private implementation package), ASG_DOWNLOAD, FND_API (the standard Oracle Applications API framework), FND_MSG_PUB (the message dictionary API), and STANDARD (the PL/SQL standard package). Because the public package delegates its data manipulation to ASG_CUSTOM_PVT and ASG_DOWNLOAD, table access is performed indirectly through those dependent units, which typically operate against ASCP planning and staging tables such as those in the MSC and ASG schemas. Implementers should trace dependencies through ASG_CUSTOM_PVT to identify the precise tables affected in their environment.

Usage Notes

ASG_CUSTOM_PUB is intended to be invoked programmatically rather than interactively. Typical invocation scenarios include custom concurrent programs, user hooks, and extensions written against the supported public API. Because the package depends on FND_API and FND_MSG_PUB, callers should follow the standard Oracle Applications API conventions: initialize the message stack, invoke the routine, inspect the returned status, and retrieve any error messages via FND_MSG_PUB before committing work.

The ETRM documentation records that ASG_CUSTOM_PUB is not referenced by any other database object, confirming that it is a top-level entry point consumed by external (custom) code rather than an internal dependency of seeded Oracle packages. The MARK_DIRTY routine is most commonly called after custom logic alters planning inputs, ensuring the planning engine does not rely on stale data. Because the package is classified PUB and is schema-resident in APPS, custom code should reference it via the APPS synonym to remain upgrade-safe across 12.1.1 and 12.2.2.