Search Results populate_record_cust

Overview

RLM_SETUP_TERMS_SV is a server-side PL/SQL package owned by APPS within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the Oracle Return Material Authorization / Logistics Management (RLM) product family and is classified as a Service (SV) layer component, indicating its role as reusable programmatic logic rather than a user-facing API. Its principal business function is to resolve and populate RLM "setup terms" — the configurable return and repair agreement attributes negotiated between a customer and a supplier — at three distinct hierarchical levels: customer, customer ship-to address, and customer item.

The package exposes a global PL/SQL record type, setup_terms_rec_typ, whose fields mirror columns in RLM_CUST_SHIPTO_TERMS (for example CUM_CONTROL_CODE, CUM_ORG_LEVEL_CODE, CUM_SHIPMENT_RULE_CODE, CUM_YESTERD_TIME_CUTOFF, CUST_ASSIGN_SUPPLIER_CD, CUSTOMER_RCV_CALENDAR_CD, SUPPLIER_SHP_CALENDAR_CD, UNSHIP_FIRM_CUTOFF_DAYS, SCHEDULE_HIERARCHY_CODE and CRITICAL_ATTRIBUTE_KEY). Other programs invoke this shared type to obtain a normalized snapshot of the applicable terms governing cumulative shipment, unshipped order disposition, and scheduling hierarchy behavior.

Key Procedures and Functions

• get_setup_terms() — The primary entry point. It orchestrates resolution of the applicable setup terms for a given customer, address, and item context, returning the populated structure to the caller. This is the routine most frequently referenced by external code searching for "get_setup_terms".
• populate_record_cust() — Populates the setup terms record from the customer-level definition, establishing the baseline terms when no more specific override exists.
• populate_record_add() — Populates the record from the address (ship-to) level, applying address-specific overrides to the customer-level baseline.
• populate_record_item() — Populates the record from the customer item level, applying the most granular overrides for a specific customer-item combination.

The metadata documents six procedures/functions in total, consistent with the four named routines above plus supporting internal helpers. Parameter lists are deliberately not reproduced here; callers should reference the package specification in the database.

Tables Accessed

The package reads from the following APPS synonyms:

• RLM_CUST_SHIPTO_TERMS — The primary source of customer and ship-to level term definitions.
• RLM_CUST_ITEM_TERMS — Customer item level term definitions used by populate_record_item().
• ECE_TP_GROUP and ECE_TP_HEADERS — Trading partner group and header data used to resolve partner identity and associated agreements.
• HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES — Oracle Trading Community Architecture tables supplying customer account and account site validation and lookup.

Usage Notes

RLM_SETUP_TERMS_SV is a private service package, not a public API, and is referenced by nine other packages within the RLM module. It is typically invoked indirectly: RLM forms and concurrent programs that need to display or act upon return terms, cumulative management rules, or shipment scheduling cutoffs call get_setup_terms() to retrieve the correctly layered terms for the active customer, ship-to, and item context. Custom extensions should call the same entry point rather than querying the underlying tables directly, so that the customer/address/item precedence logic remains centralized. Because the record type is declared globally in the package specification, dependent code can declare a variable of setup_terms_rec_typ and pass it to get_setup_terms(), then reference individual fields without additional lookups.