Search Results populate_rule_input_rec

Overview

CSD_RULES_ENGINE_PVT is a private PL/SQL package in the APPS schema that implements the rules engine for Oracle Depot Repair, part of the Enterprise Asset Management (EAM) / Service family of modules. Its role is to evaluate user-defined Depot Repair rules against a repair order context and to return either a matched rule outcome or a defaulted attribute value. The package is registered as a private (PVT) API, meaning it is not part of the supported public interface and is intended for consumption by other Oracle packages rather than direct customer calls. In Oracle EBS 12.1.1 and 12.2.2, the file header identifies the source as csdvrulb.pls and the last documented revision date as 2008, reflecting that the underlying logic has been stable across both releases.

Key Procedures and Functions

The package exposes approximately twenty-four documented procedures and functions. The principal entry points are:

• PROCESS_RULE_MATCHING — the central driver that matches rules against an input record, accepting the standard FND_API parameters plus a CSD_RULE_MATCHING_REC_TYPE record. It is documented as being called from Depot Repair Bulletins.
• SOO_DEFAULTING and PROCESS_SOO_RULE — support the sourcing/defaulting path for service order and repair order attributes.
• GET_DEFAULT_VALUE_FROM_RULE — the procedure the user searched for. It retrieves the default value produced by a matched rule, forming the bridge between rule evaluation and attribute assignment on the repair order.
• MATCH_CONDITION and CHECK_CONDITION_MATCH — evaluate individual rule conditions against the populated input record.
• COPY_RULE_INPUT_REC_VALUES and POPULATE_RULE_INPUT_REC — copy and populate the rule input record structure used throughout matching.
• GET_DEFAULT_VALUE — a lower-level value retrieval routine.
• Validation helpers: CHECK_RO_ITEM_CATEGORY, CHECK_PROMISE_DATE, CHECK_RESOLVE_BY_DATE, CHECK_RETURN_BY_DATE, CHECK_REPEAT_REPAIR, CHECK_CHRONIC_REPAIR, and CHECK_CONTRACT_EXP_DATE.
• Lookup and SQL helpers: GET_COUNTRY_CODE, GET_RO_INSTANCE_ID, GET_RULE_SQL_FOR_RO, and GET_SQL_OPERATOR.

Parameter lists are not reproduced here; callers should reference the package specification for exact signatures.

Tables Accessed

The package references the following tables through APPS synonyms:

• CSD_RULES_B and CSD_RULE_CONDITIONS_B — the rule definitions and their conditions, read to determine which rules apply to the repair order.
• CSD_REPAIRS — the depot repair order header/detail context for matching and defaulting.
• HR_LOCATIONS_ALL, HZ_LOCATIONS, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES — location and party-site data used for geographic conditions such as country code resolution.
• MTL_ITEM_CATEGORIES — item category information used by the item category validation logic.
• OKC_K_LINES_B — contract line data used for contract expiration checks.
• WIP_ENTITIES — work-in-process entity information for the repair instance.
• DBMS_SQL and PLITBLM — dynamic SQL and PL/SQL table utilities used to build and execute rule-driven queries.

Usage Notes

CSD_RULES_ENGINE_PVT is invoked by approximately nine other packages and is not intended for direct call from forms or concurrent programs. In practice, it is reached indirectly through Depot Repair Bulletins and the Depot Repair sourcing/defaulting flow, where the repair order context is assembled into CSD_RULE_MATCHING_REC_TYPE before PROCESS_RULE_MATCHING is called. Because the package is classified PVT, its interfaces may change without notice; customizations should call the supported public API layer that wraps it. The use of DBMS_SQL indicates the matching logic generates dynamic SQL from rule metadata, so performance is sensitive to rule volume and condition complexity. In 12.2.2 the package behaves identically to 12.1.1 at the API level, and any online patching should preserve the APPS synonym ownership and grants.