Results for “check_mandatory_str_col”

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

Overview

HZ_COMMON_PUB is a public PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite Trading Community Architecture (TCA) module. It functions as a shared utility and validation layer that other TCA packages and Oracle Receivables components invoke to perform common, reusable operations against the party, customer, and site data model. The package is classified as a PUBLIC API, meaning it is intended to be callable from external code, forms, concurrent programs, and custom extensions. Its documented status is VALID in both EBS 12.1.1 and 12.2.2.

The package does not itself embody a single business transaction. Rather, it centralizes transactional control (commit and rollback), installation detection for TCA, lookup validation, sequencing helpers for account and party-site numbers, address and name resolution, and reusable time-window and mandatory-column validation routines. Dependencies include FND_API, FND_MSG_PUB, FND_MESSAGE, FND_LOOKUP_VALUES, FND_TERRITORIES_VL, FND_ACCESS_CONTROL_UTIL, AR_LOOKUPS, ARP_UTIL, and core HZ tables, confirming its role as a cross-cutting utility in the TCA and Receivables stack.

Key Procedures and Functions

The documented API surface comprises 29 procedures and functions. The principal groups are:

• Transactional control: COMMIT_TRANSACTION and ROLLBACK_TRANSACTION standardize commit/rollback behavior across callers using the FND_API messaging conventions.
• Installation checks: IS_TCA_INSTALLED determines whether Trading Community Architecture components are present, allowing callers to branch behavior in mixed installations.
• Lookup validation: VALIDATE_LOOKUP and VALIDATE_FND_LOOKUP validate values against TCA lookups and FND_LOOKUP_VALUES respectively.
• Number generation: GET_ACCOUNT_NUMBER and GET_PARTY_SITE_NUMBER retrieve next sequence values using HZ_ACCOUNT_NUM_S and HZ_PARTY_SITE_NUMBER_S.
• Security context: CONTENT_SOURCE_TYPE_SECURITY, ENABLE_CONT_SOURCE_SECURITY, and DISABLE_CONT_SOURCE_SECURITY manage content-source access control, typically via DBMS_SESSION.
• Attribute resolution: GET_CUST_ADDRESS, GET_CUST_NAME, GET_CUST_CONTACT_NAME, and GET_PARTY_NAME return denormalized descriptive attributes for a given account, party, or contact.
• Column validations: CHECK_MANDATORY_STR_COL, CHECK_MANDATORY_DATE_COL, and CHECK_MANDATORY_NUM_COL enforce required value presence for string, date, and numeric columns.
• Time utilities: TIME_COMPARE, IS_TIME_BETWEEN, and IS_TIME_OVERLAP support temporal comparisons and interval overlap checks.

Tables Accessed

The package reads and, in limited cases, writes the following tables through APPS synonyms:

• HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES — party and account name, contact, and role resolution.
• HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, HZ_PARTY_SITE_NUMBER_S — address and site number resolution and sequencing.
• HZ_LOCATIONS — address attribute lookups.
• HZ_RELATIONSHIPS — party relationship traversal for contact and role queries.
• HZ_ACCOUNT_NUM_S, HZ_PARTY_SITE_NUMBER_S — sequence access for account and site numbers.
• FND_LOOKUP_VALUES — lookup validation.
• DBMS_SESSION, DUAL — session context management and singleton queries.

Usage Notes

HZ_COMMON_PUB is invoked indirectly by 30 other database objects and is referenced by numerous TCA and Receivables APIs. Typical invocation channels include Oracle Forms for customer and party maintenance, concurrent programs performing bulk TCA operations, and custom PL/SQL extending standard TCA flows. Because it is a public API with documented commit/rollback helpers, callers should treat COMMIT_TRANSACTION and ROLLBACK_TRANSACTION as the standard mechanism for transactional closure. The security-context procedures should be invoked around operations requiring content-source restriction. Developers should not rely on undocumented signatures; only the 29 documented procedures and functions are supported. No database object depends on HZ_COMMON_PUB itself, confirming its pure utility role.