Search Results update_policy

Overview

The APPS.JTF_PREFAB_POLICY_PUB package body implements the public API layer for managing "preference fabricator" policies within Oracle E-Business Suite. Preference fabricator policies define the rules by which user interface preferences, portlet configurations, and personalization settings are automatically fabricated, filtered, and applied for users, responsibilities, or applications. This package provides the programmatic interface through which administrators and dependent application modules create, maintain, and remove those policy definitions in a controlled, API-compliant manner.

The package is classified as a Public (PUB) API and is owned by the APPS schema. Its header comment (jtfprefabpob.pls 120.3) indicates it has been a stable component of the EBS technology stack since the mid-2000s and remains present in both 12.1.1 and 12.2.2. All procedures follow the Oracle Application Object Library API standard: they accept p_api_version, p_init_msg_list, and p_commit control parameters, and return x_return_status, x_msg_count, and x_msg_data for error handling and message propagation.

Key Procedures and Functions

The package exposes thirteen documented procedures, organized around three policy domains:

• Core policy management: INSERT_POLICY, UPDATE_POLICY, and DELETE_POLICY maintain the master preference fabricator policy records. INSERT_POLICY is the entry point most frequently referenced in searches; it accepts a policy name, priority, description, enabled flag, application scope flags, depth, responsibility/user scope flags, refresh interval and interval unit, start and end times, and a run-always flag, returning the generated policy identifier and object version number.
• User and responsibility scope: INSERT_UR_POLICY and DELETE_UR_POLICY manage the association between a policy and specific users or responsibilities.
• System policy configuration: CONFIGURE_SYS_POLICY establishes system-level policy defaults.
• Shipping and warehouse policies: INSERT_WSH_POLICY, UPDATE_WSH_POLICY, and DELETE_WSH_POLICY manage policy records tied to shipping execution, while INSERT_WSHP_POLICY and DELETE_WSHP_POLICY handle the associated policy-entry detail rows.

Each procedure follows the same control-flow pattern: it opens an API savepoint, validates the incoming arguments, performs the DML, optionally commits, and populates the standard return-status and message-buffer outputs.

Tables Accessed

The package interacts with the following base tables through APPS synonyms:

• JTF_PREFAB_POLICIES_B and JTF_PREFAB_POLICIES_TL — the base and translation tables for core policy definitions.
• JTF_PREFAB_SYS_POLICIES — system-level policy defaults.
• JTF_PREFAB_UR_POLICIES — user and responsibility policy associations.
• JTF_PREFAB_WSH_POES_B, JTF_PREFAB_WSH_POES_TL, and JTF_PREFAB_WSHP_POLICIES — shipping policy headers, translations, and policy-entry rows.
• The corresponding _S sequences (JTF_PREFAB_POLICIES_B_S, JTF_PREFAB_SYS_POLICIES_S, JTF_PREFAB_UR_POLICIES_S, JTF_PREFAB_WSHP_POLICIES_S, JTF_PREFAB_WSH_POES_B_S) supply primary keys, and DUAL is queried to fetch the next sequence value.

Usage Notes

This package is typically invoked from the Preference Fabricator configuration forms, from concurrent programs that seed or refresh default policies, and from custom extension code that needs to create policies programmatically. Callers must pass a valid p_api_version, initialize the message list when required, and inspect x_return_status for FND_API.G_RET_STS_SUCCESS before proceeding. Because the API sets a savepoint on entry, callers may safely roll back on failure. No other packages in the documented metadata reference this API, so it functions as a top-level entry point rather than a shared internal dependency.