Search Results rlm_comp_sched_to_demand_temp

Overview

RLM_COMP_SCH_TO_DEMAND_SV is an Oracle EBS Application Programming Interface package body owned by the APPS schema, classified under the ETRM (Enterprise Transportation and Logistics / Released Management) module. Its business purpose is to translate or convert complementary scheduling records into demand records within the Oracle shipping and order fulfillment flow. In practical terms, the package bridges scheduling structures and downstream demand consumption by populating a temporary staging table (RLM_COMP_SCHED_TO_DEMAND_TEMP) that is subsequently processed by related scheduling, matching, and delivery programs.

The package operates in the shipping and scheduling domain, where complementary scheduling is used to consolidate and reconcile customer shipment commitments against actual demand. It performs data validation and enrichment by resolving customer, party, and item identities before demand records are finalized. The "_SV" suffix indicates a server-side validation package. In Oracle EBS 12.1.1 and 12.2.2, this package retained a VALID status in the data dictionary, confirming that it was shipped as part of the standard Oracle E-Business Suite codebase and is executable at runtime.

Key Procedures and Functions

The ETRM metadata documents three procedures/functions within this package body; the summary below describes their intended roles without inventing parameter lists.

• Complementary-Schedule-to-Demand Conversion: The primary routine drives the transformation of complementary scheduling data into demand rows, writing into the temporary staging table RLM_COMP_SCHED_TO_DEMAND_TEMP for subsequent processing.
• Validation / Setup Resolution: A companion routine resolves and validates scheduling headers, lines, and setup terms, ensuring that referenced schedules and match setups exist and are consistent before demand creation proceeds.
• Reference Enrichment: A supporting routine enriches staged records with customer, party, and item attributes, supplying lookup values and messages used for error reporting.

Because the documentation excerpt does not expose procedure signatures, no parameter lists are inferred here; callers should reference the actual package specification for formal argument definitions.

Tables Accessed

The package reads from and writes to the following documented objects:

• RLM_COMP_SCHED_TO_DEMAND_TEMP — the principal staging/temporary table into which converted scheduling-to-demand rows are inserted. The user search term "rlm_comp_sched_to_demand_temp" corresponds directly to this object.
• RLM_SCHEDULE_HEADERS and RLM_SCHEDULE_LINES_ALL — source scheduling header and line data used to derive demand quantities and identifiers.
• RLM_MATCH_SETUP_TEMP and RLM_SEQ_MATCH_TEMP — temporary matching and sequencing structures associated with schedule processing.
• RLM_SHIP_DELIVERY_CODES — delivery code lookups used during validation.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — customer account and party identity resolution.
• MTL_CUSTOMER_ITEMS and MTL_SYSTEM_ITEMS_B — customer item and inventory item master data for item validation.
• FND_LOOKUP_VALUES_VL and FND_MESSAGE — lookup value retrieval and message/error text generation.
• DUAL, STANDARD, and PLITBLM — standard Oracle constructs used for control-flow and utility operations.

The package also references sibling packages including RLM_SETUP_TERMS_SV, RLM_SHIP_DELIVERY_PATTERN_SV, and RLM_TPA_SV, indicating a layered design that delegates validation and term resolution to dedicated service packages.

Usage Notes

RLM_COMP_SCH_TO_DEMAND_SV is invoked internally by Oracle scheduling and shipping processes rather than being called directly by end users. It is referenced by one other database object, consistent with its role as a supporting utility within the RLM scheduling conversion chain. Typical invocation occurs during complementary schedule processing, when the system converts complementary scheduling commitments into demand records for downstream matching and delivery. Because it writes to a temporary table, it is generally executed within a batch or concurrent-program context, with results subsequently consumed by follow-on matching programs.

In EBS 12.1.1 and 12.2.2, customizations should avoid modifying this seeded package; instead, extensions should wrap or supplement the staging table. Developers troubleshooting "rlm_comp_sched_to_demand_temp" issues should inspect the temporary table contents and the FND_MESSAGE-generated errors emitted by the validation routines.