Search Results msc_owb_tree




Overview
Explore in AI Chat

Overview

OWB_TREE is a PL/SQL package owned by the APPS schema and maintained at VALID status in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its name places it within the Oracle Warehouse Builder (OWB) integration layer that EBS exposes for reporting and analysis tooling. Functionally, the package provides the hierarchical tree-handling services required to render organizational, sourcing, and classification structures to external extraction, transformation, and loading consumers. In the EBS architecture, packages prefixed OWB and MSC frequently appear together because the MSC (Advanced Supply Chain Planning) schema consumes OWB structures when building its own hierarchical views of inventory organizations, suppliers, and categories.

The ETRM classification of OWB_TREE is OTHER, indicating that it is not a public, seeded business API with a published interface contract, but an internal utility. It is documented primarily for dependency and impact analysis rather than for direct customer invocation.

Key Procedures and Functions

The ETRM record documents five callable units. Their purposes are inferred from their names and their position in the OWB/MSC tree-rendering chain:

  • GETSTRUCTURE — Returns the hierarchical structure of a tree, supplying the node relationships that downstream consumers use to reconstruct the parent-child layout.
  • GET_EXCP_COUNT — Returns an exception count associated with a tree or node set, typically used to flag nodes where sourcing, assignment, or configuration data is missing or inconsistent.
  • GET_CUST_HIER_STRING — Produces a delimited string representation of a customer hierarchy, a common requirement when hierarchies must be flattened for a report, interface table, or file extract.
  • GET_SOURCING_NODES — Returns the sourcing-related nodes of a tree, supporting supply chain and sourcing rule analysis.
  • GET_LOOKUPS — Retrieves lookup values used to label or decode tree node types and statuses.

No parameter lists are documented in the ETRM metadata; signature details must be confirmed from the deployed package specification.

Tables Accessed

The ETRM record for OWB_TREE lists no base tables referenced through APPS synonyms. Its only recorded external dependency is SYS.STANDARD, the standard PL/SQL package providing built-in datatype support. This pattern is consistent with a package that works almost entirely against data structures passed in by the caller or against tables resolved dynamically at runtime. Consumers should not assume the absence of table access; where the dependency view shows only STANDARD, the SQL may be issued against synonyms or views not captured in the documented dependency list, or the package may act purely as a transformation layer over arguments supplied by the calling program.

Usage Notes

OWB_TREE is referenced by two other packages in the APPS schema: MSC_OWB_TREE and MSC_SCH_WB. The search term msc_owb_tree reflects this close coupling — MSC_OWB_TREE is the supply chain variant that wraps or extends the generic tree services. Because OWB_TREE is the base package, changes to it carry downstream impact into both MSC_OWB_TREE and MSC_SCH_WB and should be assessed through the dependency tree before patching or customization.

Typical invocation occurs from within other PL/SQL packages rather than from Oracle Forms or concurrent programs directly. The structures it exposes, particularly sourcing nodes and flattened customer hierarchy strings, are the kind of output consumed by planning data extraction, workbook generation, and reporting feeds. Custom code should treat these procedures as internal interfaces: bind values should be validated by the caller, and any reliance on undocumented signatures carries upgrade risk across the 12.1.1 to 12.2.2 boundary.