Search Results xml_schema_name_present




Overview
Explore in AI Chat

Overview

SYS.XML_SCHEMA_NAME_PRESENT is a low-level Oracle database package that forms part of the XML DB infrastructure shipped with the Oracle database kernel, and by extension is present in every Oracle E-Business Suite 12.1.1 and 12.2.2 environment. Within the EBS context, this package is not an Applications-owned object; it belongs to the SYS schema and is classified in the ETRM (E-Business Suite Technical Reference Manual) metadata under the API classification "OTHER." Its business function is narrow but fundamental: it provides a programmatic test that determines whether a named XML schema is registered and visible to a given database user. Because EBS makes extensive use of XML-based technologies — including the XML Publisher (BI Publisher) engine, Oracle XML Gateway, and various e-commerce integrations — the ability to verify the presence of an XML schema at runtime underpins a range of dependent processing.

Key Procedures and Functions

The ETRM documentation records a single exposed subprogram for this package:

  • IS_SCHEMA_PRESENT — A function that returns a numeric result indicating whether a specified XML schema is present for a specified user. The caller supplies the schema object name and the user number, and the function reports presence or absence. The documented source shows a numeric return type rather than a BOOLEAN, consistent with the convention used throughout Oracle-supplied PL/SQL APIs that must be callable from SQL as well as PL/SQL. No additional procedures or functions are documented for this package, and the package body is not exposed in the ETRM content.

Because the signature is minimal, consumers should treat the function strictly as a predicate: a non-zero result conventionally signals that the schema exists, while zero signals that it does not. Exact return semantics should always be confirmed against the specific database release in use.

Tables Accessed

The ETRM metadata lists no tables referenced through APPS synonyms for this package. This is expected, since the package is a SYS-owned object and interfaces directly with the Oracle XML DB data dictionary views and internal metadata tables rather than with any EBS application tables. Its checks are executed against the database's own registry of registered XML schemas, which is maintained by the XML DB component. Consequently, no EBS transactional or setup tables are read or written by this package, and it holds no application data.

Usage Notes

The ETRM metadata records that XML_SCHEMA_NAME_PRESENT is referenced by 32 other packages, which confirms that it is a shared utility invoked internally by higher-level Oracle-supplied code rather than an API intended for direct customer invocation. Typical invocation scenarios include:

  • Validating schema availability before an XML document is parsed or transformed, particularly in flows that depend on schema-based validation.
  • Supporting XML Publisher and XML Gateway processing, where the presence of registered schemas determines whether a template or message can be resolved.
  • Serving as a guard condition inside other SYS or XML DB packages that lazily register or reference schemas.

Because the package is undocumented for customer use and owned by SYS, it should not be called from custom EBS code or modified in any way; doing so risks invalidating the database dictionary or breaking dependent Oracle-supplied packages. Its relevance to EBS administrators is primarily diagnostic — confirming that the XML DB schema registry is intact when XML-dependent features fail.