Search Results xnp_debug_u1




Overview
Explore in AI Chat

Overview

XNP.XNP_DEBUG is a general-purpose diagnostic logging table owned by the XNP schema within Oracle E-Business Suite. Its documented purpose is to store general debug information generated by the NP system, making it a low-volume, high-value instrument for troubleshooting, tracing, and auditing runtime behavior across NP-related processing. In EBS 12.1.1 and 12.2.2, the object is registered in FND Design Data as XNP.XNP_DEBUG, resides in the APPS_TS_TX_DATA tablespace, and carries a VALID status.

From a heuristic Data Vault modeling perspective, XNP_DEBUG is classified as standalone. It depends on no parent business entity through foreign keys and is referenced by no child objects, so it behaves less like a hub or link and more like an autonomous event or diagnostic satellite. The SECURITY_GROUP_ID column carries a reference to FND_SECURITY_GROUPS, but this is a multi-tenancy constraint rather than a true business relationship, reinforcing the standalone classification as a modeling suggestion.

Key Information Stored

The table contains ten documented columns. The surrogate primary key is DEBUG_ID, a NUMBER column that uniquely identifies each row; it is also enforced by the unique index XNP_DEBUG_U1 (NORMAL, UNIQUE, APPS_TS_TX_IDX). Because the table has no natural business key, DEBUG_ID serves effectively as the only unique business-key candidate.

  • DEBUG_ID – Surrogate unique identifier for the debug record; primary key (XNP_DEBUG_PK) and sole column of XNP_DEBUG_U1.
  • DEBUG_LEVEL – Numeric debug level controlling verbosity or severity of the captured message.
  • CONTEXT – VARCHAR2(80) context data identifying the module, component, or processing scope being traced.
  • DESCRIPTION – VARCHAR2(1996) descriptive text of the debug event; the primary human-readable payload.
  • CREATED_BY, CREATION_DATE – Standard who columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard who columns capturing the last modifying user, timestamp, and login.
  • SECURITY_GROUP_ID – Numeric discriminator used in hosted (multi-tenant) environments; documented as referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is diagnosing NP system behavior during implementation, patching, or production incidents. Developers and DBAs query this table by DEBUG_LEVEL or CONTEXT to isolate a failing component, and by CREATION_DATE to correlate debug output with a specific execution window.

  • Retrieve the most recent high-severity messages: SELECT * FROM XNP.XNP_DEBUG WHERE DEBUG_LEVEL >= 5 ORDER BY CREATION_DATE DESC;
  • Trace a specific context: SELECT DEBUG_ID, DEBUG_LEVEL, DESCRIPTION FROM XNP.XNP_DEBUG WHERE CONTEXT = :ctx;
  • Time-window analysis: filter on CREATION_DATE between two bind values for incident forensics.
  • Multi-tenant scoping: constrain on SECURITY_GROUP_ID in hosted deployments.
  • Reporting: join to FND_USER on CREATED_BY for user attribution, though volume is typically small and purge routines should be applied.

Related Objects

The documented dependency graph for XNP.XNP_DEBUG is intentionally narrow. The table references no database object except the SECURITY_GROUP_ID dependency on FND_SECURITY_GROUPS (join on SECURITY_GROUP_ID). It is referenced externally by the APPS schema alias XNP_DEBUG, which is the standard synonym-based access path in EBS. Reporting and diagnostic queries commonly join FND_USER on CREATED_BY / LAST_UPDATED_BY for user context. Because the object is standalone with no child foreign keys, there are no dependent transaction tables; maintenance and purging should be performed directly against XNP.XNP_DEBUG by DEBUG_ID.