Results for “updated_by”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_RESOURCE_UTL is a VALID PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as an OTHER API within the ETRM metadata model rather than a formal public interface. The package serves the Resource Manager foundation of the CRM/TeleSales (JTF) product family, providing centralized validation, hook dispatch, and environment-context utilities for resource, group, team, and role records. Rather than exposing a business transaction, it supplies the low-level validation layer that other resource-related packages and forms depend upon. The metadata records that JTF_RESOURCE_UTL is referenced by 33 other database objects while referencing a broad set of FND, HZ, JTF, IEM, IEO, OE, PER, and RA entities. This reference asymmetry confirms its role as a shared infrastructure package: it is a callee, not a caller of higher-level resource APIs.

Key Procedures and Functions

The package exposes 36 documented procedures and functions. Several are administrative context helpers: CREATED_BY, UPDATED_BY, and LOGIN_ID resolve the current user or login identity from FND_GLOBAL for audit column population. CALL_INTERNAL_HOOK dispatches through the JTF hook framework, reading JTF_HOOKS_DATA and JTF_USER_HOOKS. The remainder form a family of validation routines, each enforcing referential and business rules before a resource record is written:

• VALIDATE_RESOURCE_GROUP, VALIDATE_RESOURCE_TEAM, VALIDATE_RESOURCE_NUMBER, and VALIDATE_RESOURCE_CATEGORY verify group, team, numbering, and category attributes of the resource entity.
• VALIDATE_USAGE, VALIDATE_SOURCE_ID, and VALIDATE_SUPPORT_SITE_ID check object-usage and source/support associations.
• VALIDATE_EMPLOYEE_RESOURCE confirms that a resource maps to a valid employee.
• VALIDATE_USER_ID and VALIDATE_SALESREP_ID confirm user and salesrep linkages.
• VALIDATE_INPUT_DATES enforces date-range integrity, while VALIDATE_TIME_ZONE, VALIDATE_NLS_LANGUAGE, and VALIDATE_CURRENCY_CODE validate reference and localization values.
• VALIDATE_HOLD_REASON_CODE and VALIDATE_SERVER_GROUP validate hold and middle-tier server-group values.

No parameter lists are published in the ETRM documentation; callers should treat signatures as internal and reference them only from code already coupled to this package.

Tables Accessed

The package reads and, in validation routines, participates in maintaining several base and view objects through APPS synonyms. Resource and role structures are drawn from JTF_RS_RESOURCE_VALUES, JTF_RS_ROLES_B, JTF_RS_GROUPS_B, JTF_RS_GROUP_USAGES, and JTF_RS_RESOURCE_EXTNS, with JTF_OBJECTS_B and JTF_OBJECT_USAGES providing the object registry. Party data resolves through HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, and HZ_TIMEZONES. User and localization context comes from FND_USER, FND_LANGUAGES, FND_LOOKUPS, FND_CURRENCIES_ACTIVE_MONET_V, and FND_TIMEZONES_VL. Email and server context is supplied by IEM_EMAIL_ACCOUNTS and IEO_SVR_GROUPS, while hook dispatch reads JTF_HOOKS_DATA. Employee and territory checks draw on PER_ALL_PEOPLE_F, PER_PEOPLE_F, and RA_TERRITORIES.

Usage Notes

JTF_RESOURCE_UTL is typically invoked indirectly. Oracle Resource Manager forms, concurrent programs, and the JTF_RS_* package family call its validation routines before committing resource, group, team, and role records, which is consistent with the 33 objects that reference it. Because the ETRM metadata classifies it as OTHER rather than a public API, customizations should not call it directly unless the calling code already depends on the same JTF resource foundation. When extending resource validation, Oracle's supported path is to register a hook via the JTF hook framework, which CALL_INTERNAL_HOOK resolves, rather than modifying this package. Direct edits are overwritten by patching; any custom logic must be carried in a separate package or hook implementation.