Search Results g_download

Overview

AK_FLOW3_PVT is a private PL/SQL package owned by the APPS schema within the Oracle E-Business Suite, belonging to the Oracle Application Framework object metadata layer administered by the Applications Core (AK) product team. Its designation as a private (PVT) package indicates that it is not intended for direct invocation by external modules, customers, or extension developers; rather, it acts as an internal validation engine consumed only by other AK-owned APIs. In Oracle EBS 12.1.1 and 12.2.2, the AK modules provide the infrastructure for declaratively defined application objects — flows, pages, regions, region items, and their relationships — that drive the HTML-based user interface rendering and navigation model.

The package header carries a version identifier reflecting its origin in the 11i-era codebase (header revision dated 2005), and the source remains functionally stable across both 12.1.1 and 12.2.2 releases. Its principal business function is record-level validation of flow and page-region metadata before such metadata is committed to the repository tables. The package does not define business data; it guards the structural integrity of the metadata that defines how other EBS screens are composed and navigated.

Key Procedures and Functions

Five documented program units constitute the package interface, all oriented toward validation:

• VALIDATE_FLOW — Validates a flow record. The function accepts flow column values and a caller indicator, and returns the standard FND_API return status (unexpected error, error, or success), together with a boolean indicating whether all validation tests passed. The p_caller argument must correspond to one of the constants defined in AK_ON_OBJECTS_PVT, namely G_CREATE, G_DOWNLOAD, or G_UPDATE, so that validation behaviour can differ by entry point.
• VALIDATE_PAGE — Performs the equivalent record-level validation for a page definition belonging to a flow.
• VALIDATE_PAGE_REGION — Validates the association between a page and a region, ensuring that region placement metadata is internally consistent.
• VALIDATE_PAGE_REGION_ITEM — Validates a page region item, the finest-grained addressable element within the AK metadata hierarchy.
• VALIDATE_REGION_RELATION — Validates relationships defined between regions, including foreign-key and unique-key style constraints expressed as AK metadata.

All units follow the FND_API conventions: an API version number, a validation level defaulting to full validation, and an OUT NOCOPY return status parameter. Default values of FND_API.G_MISS_NUM and FND_API.G_MISS_CHAR distinguish unspecified columns from explicitly supplied null values.

Tables Accessed

The package reads and writes the AK metadata repository through APPS synonyms. AK_ATTRIBUTES, AK_UNIQUE_KEYS, and AK_FOREIGN_KEYS supply the constraint and attribute definitions used during validation. AK_FLOW_PAGES and AK_FLOW_PAGE_REGIONS hold the flow-to-page and page-to-region associations being checked. AK_FLOW_REGION_RELATIONS stores region relationship definitions, while AK_REGIONS holds the master region definitions referenced by the page region and region relation records.

Usage Notes

AK_FLOW3_PVT is invoked indirectly. The Create, Update, and Download APIs of the AK object layer call VALIDATE_FLOW and its companion routines before persisting metadata, passing G_CREATE, G_UPDATE, or G_DOWNLOAD respectively. Two other packages in the EBS codebase reference it. It is never called from Oracle Forms or concurrent programs directly, and Oracle does not support customer invocation of private AK packages; customizations requiring metadata validation should use the supported public AK APIs instead. Because the package name and parameters are unrelated to any infusion pump or medical device product, the search phrase that surfaced this object is a lexical mismatch rather than an indication of its function.