Search Results rlm_manage_demand_sv




Overview
Explore in AI Chat

Overview

RLM_MANAGE_DEMAND_SV is an Oracle EBS PL/SQL package owned by the APPS schema, classified as a service (SV) layer component within the Oracle Enterprise Territory Management / Channel Revenue Management (RLM) module family. In Oracle EBS 12.1.1 and 12.2.2, the RLM schema objects support demand management, territory assignment, and channel revenue processes. This package encapsulates the business logic for creating, validating, reallocating, and maintaining demand records that flow through the RLM interface structures. Its status is VALID as of the ETRM 12.2.2 metadata documentation.

The package acts as a central orchestrator: it consumes data from the RLM interface tables, applies sourcing and customer-item rules, and exposes demand quantities—including in-transit quantities—to other RLM service packages and concurrent programs such as RLM_RLMNETCH_XMLP_PKG. It is both a consumer and a provider within a dense dependency graph, referencing foundational packages like RLM_CORE_SV and RLM_DP_SV, and being referenced by RLM_CUM_SV, RLM_EXTINTERFACE_SV, RLM_RD_SV, RLM_TPA_SV, RLM_VALIDATEDEMAND_SV, and RLM_WF_SV.

Key Procedures and Functions

The documented package exposes 40 procedures and functions. Among those explicitly named in the ETRM metadata are:

  • NAME — a procedure or function whose purpose relates to returning or resolving the name attribute of a demand entity.
  • GETALLINTRANSITQTY — a function that calculates the aggregate in-transit quantity for demand records, drawing on sourcing and item data to determine quantities not yet received.
  • GETINTRANSITACROSSORGS — a function that aggregates in-transit quantities across multiple inventory organizations, supporting cross-organizational demand visibility.

The remaining procedures and functions follow the RLM service-layer convention of validating interface headers and lines, generating demand records, and propagating demand changes to dependent service packages. Because the documented metadata does not enumerate every signature, parameter lists should be verified against the package specification in the target instance.

Tables Accessed

The package reads and writes the following documented tables (referenced via APPS synonyms):

Usage Notes

RLM_MANAGE_DEMAND_SV is typically invoked by other RLM service packages (such as RLM_VALIDATEDEMAND_SV and RLM_TPA_SV), by the RLM Net Change concurrent report via RLM_RLMNETCH_XMLP_PKG, and by custom extensions integrating RLM demand data. It is not an end-user API; callers should use it through the RLM service layer and standard concurrent program wrappers rather than direct invocation, and must honor commit handling controlled by the calling process.