Search Results dump_hz_org_rec

Overview

APPS.CSD_GEN_UTILITY_PVT is a private utility package within the Oracle E-Business Suite Depot Repair / Service (CSD) product family. Its primary business function is to provide centralized diagnostic, debugging, and record-dumping services for the CSD application programming interfaces and their supporting private packages. The package exposes a small set of debug-control primitives — SET_DEBUG_ON, SET_DEBUG_OFF, and IS_DEBUG_ON — together with a message-accumulation procedure (ADD) and a comprehensive family of record-dump routines that serialize the contents of PL/SQL records to a flat file for developer and support analysis.

Because it is classified as a PVT (private) API, the package is not intended as a public integration surface. It is an internal instrumentation facility used by other CSD packages to trace execution, capture API input/output structures, and record error stacks when service requests, repair estimates, repair orders, and related transaction data are processed. In EBS 12.1.1 and 12.2.2 environments, the package behavior is effectively unchanged at the source level; the header indicates the last substantive revision predates both releases, and operation is governed by profile options rather than version-specific runtime behavior.

Key Procedures and Functions

The debug-control procedures form the entry point for the facility. SET_DEBUG_ON enables debug output, SET_DEBUG_OFF disables it, and the function IS_DEBUG_ON — the object referenced in the user's search — returns a boolean indicating whether debugging is currently active. Callers use IS_DEBUG_ON to guard expensive diagnostic code so that record-dumping only occurs when explicitly enabled.

• ADD — appends a caller-supplied debug message to the accumulated output buffer.
• DUMP_API_INFO — writes identifying information for a given package and API name, supporting trace correlation.
• DUMP_ERROR_STACK — exists as both a procedure and an overloaded function returning a string, capturing the current error stack for logging or display.
• DUMP_PROD_TXN_REC — dumps a product transaction record from CSD_PROCESS_PVT.
• DUMP_SR_REC — dumps a service request record from CSD_PROCESS_PVT.
• DUMP_ESTIMATE_REC and DUMP_ESTIMATE_LINE_REC — dump repair estimate header and line records from CSD_REPAIR_ESTIMATE_PVT.
• DUMP_REPAIR_ORDER_GROUP_REC — dumps repair order group records from CSD_REPAIR_GROUPS_PVT.
• DUMP_ADDRESS_REC — dumps address records from CSD_PROCESS_PVT.
• TCA record dumpers — DUMP_HZ_PERSON_REC, DUMP_HZ_ORG_REC, DUMP_HZ_ACCT_REC, DUMP_HZ_CUST_PROFILE_REC, DUMP_HZ_PHONE_REC, DUMP_HZ_EMAIL_REC, DUMP_HZ_WEB_REC, and DUMP_HZ_PARTY_SITE_REC serialize the corresponding Trading Community Architecture (TCA) public API record types from HZ_PARTY_V2PUB, HZ_CUST_ACCOUNT_V2PUB, HZ_CUSTOMER_PROFILE_V2PUB, and HZ_CONTACT_POINT_V2PUB.

Tables Accessed

The package does not manipulate application business tables. Its documented references are infrastructure objects:

• UTL_FILE — the Oracle supplied file I/O package used to write debug output to a flat file whose directory is derived from the CSD_LOGFILE_PATH profile option, defaulting to /tmp.
• DUAL — used for trivial scalar evaluation within PL/SQL expressions.
• PLITBLM — the PL/SQL internal table memory structure, referenced when diagnosing collection-based memory utilization.
• V$SESSION — consulted to capture session-level context (such as SID) for the log header.

Usage Notes

CSD_GEN_UTILITY_PVT is invoked internally rather than by end users. It is referenced by 49 other packages across the CSD module, making it a high-fan-in utility in the dependency graph. Typical invocation patterns include:

• Package-level tracing — CSD public and private APIs wrap their logic with IS_DEBUG_ON checks and call ADD or the DUMP_* routines to log parameters and record structures when debugging has been enabled.
• Error diagnostics — DUMP_ERROR_STACK is called from exception handlers to record the PL/SQL error stack before control returns to the calling layer.
• Enablement via profile options — debug behavior is controlled through the CSD_DEBUG_LEVEL profile option read at package initialization, and output routing through CSD_LOGFILE_PATH. Support personnel enable these profiles during troubleshooting rather than modifying code.

Because the package is private and its output is written to operating system files, customizations should not call it as a supported API; instead, developers should treat IS_DEBUG_ON and the dump routines as diagnostic aids valid only while the corresponding profile options are set. In 12.2.2, the package remains a PL/SQL capability and is unaffected by the editioning and online patching model. Knowledge of this package is essential when interpreting CSD debug logs during incident analysis or when validating data passed into CSD APIs.