Search Results check_valid_org_server




Overview

MO_GLOBAL_SERVER is a wrapper package body in the Oracle E-Business Suite Applications (APPS) schema that exposes the core Multi-Org initialization and context-management APIs of the MO_GLOBAL package to server-side callers. Multi-Org architecture is the mechanism by which a single EBS installation hosts data for multiple operating units while restricting each user session's visibility to an authorized organization. The MO_GLOBAL package performs that initialization and context switching; MO_GLOBAL_SERVER provides a thin, companion interface whose procedures and functions mirror the underlying MO_GLOBAL entry points, delegating each call directly without altering the parameter semantics.

The package body header ($Header: AFMOGBWB.pls 120.2 2006/10/21) shows a stable artifact that has persisted largely unchanged across the 12.1.1 and 12.2.2 releases, reflecting the maturity of the Multi-Org foundation layer. Its classification in the ETRM repository is OTHER, indicating it is an internal technical package rather than a business-facing public API.

Key Procedures and Functions

The package exposes approximately 23 documented procedures and functions. The most directly relevant to context management are:

Each routine is a single-statement delegation to its mo_global counterpart, so behavior, exceptions, and return values are identical to the base package.

Tables Accessed

The ETRM metadata records no direct table references for this package. This is consistent with its design: MO_GLOBAL_SERVER performs no SQL of its own and relies entirely on MO_GLOBAL, which reads and maintains the Multi-Org security context — typically through the org hierarchy and security profile structures underlying the MO schema. Any table activity observed at runtime therefore originates from the delegated MO_GLOBAL calls rather than this wrapper.

Usage Notes

MO_GLOBAL_SERVER is invoked by server-side PL/SQL that requires Multi-Org context but executes outside the standard Forms-based session path — for example, concurrent programs, database triggers, and custom interfaces that must establish an operating unit context before querying or updating organization-sensitive data. The ETRM repository records that this package is referenced by one other package, confirming its role as a dependency rather than a top-level entry point. Typical usage begins with INIT_SERVER or SET_POLICY_CONTEXT_SERVER, followed by IS_MO_INIT_DONE_SERVER or GET_CURRENT_ORG_ID_SERVER to confirm session state.

Because the package is classified OTHER and is not a public API, customizations should call MO_GLOBAL directly rather than depending on this wrapper, which exists primarily for internal delegation and interface stability.