Results for “as_list_rules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AS_LIST_RULES table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores user-defined rules used by Oracle Sales and Oracle TeleSales to identify duplicate records within a list of customers, contacts, or prospects. Duplicate identification is a core data-quality function in list management: before a marketing or telesales list can be worked, the application must determine which list members represent the same real-world entity. AS_LIST_RULES provides the configurable criteria — for example, matching on name, address, or phone number — that drive this deduplication logic.

The documented ETRM relationship data classifies this object as standalone under a heuristic Data Vault analysis mined from the foreign key structure. As a modeling suggestion, this implies the table behaves as an independent reference or configuration hub rather than a transactional link or a dependent satellite. It does not carry foreign keys to other documented tables, and its principal business identifier, LIST_RULE_ID, is exposed through a unique index, reinforcing its role as a self-contained definition table.

Key Information Stored

The table comprises twelve documented columns. The most significant are as follows:

• LIST_RULE_ID — The surrogate primary key, enforced by AS_LIST_RULES_PK and additionally through the unique index AS_LIST_RULES_U1. It uniquely identifies each duplicate-identification rule and serves as the join key to any dependent processing logic.
• RULE_NAME — The user-facing name assigned to the rule, used to present and select rules during list deduplication setup.
• TYPE — A classification column distinguishing the category or behavior of the rule, allowing the application to apply different matching semantics to different rule types.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — The standard concurrent program context columns, capturing which batch process created or last modified the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The WHO-column audit trail, recording user identity and timestamps for creation and modification.

No business-key candidate other than LIST_RULE_ID is documented; RULE_NAME functions as a descriptive attribute rather than a guaranteed unique identifier.

Common Use Cases and Queries

Typical usage centers on reviewing, reporting, and auditing the rules configured for list deduplication. Administrators query the table to confirm rule definitions before executing a list cleanup, and reporting extracts identify which rules were applied and by whom.

To list all defined rules with their types:

SELECT list_rule_id, rule_name, type,
       creation_date, last_update_date
FROM   osm.as_list_rules
ORDER BY rule_name;

To retrieve a specific rule by identifier:

SELECT list_rule_id, rule_name, type
FROM   osm.as_list_rules
WHERE  list_rule_id = :p_rule_id;

To identify rules modified within a date range for audit purposes:

SELECT list_rule_id, rule_name, last_updated_by, last_update_date
FROM   osm.as_list_rules
WHERE  last_update_date BETWEEN :from_date AND :to_date;

Because the table is low-volume configuration data, queries are inexpensive; there is little need for additional indexing beyond the documented unique indexes.

Related Objects

AS_LIST_RULES is classified as standalone, so no foreign keys to other tables are documented in the ETRM metadata. Related objects therefore depend on logical, rather than enforced, relationships:

• AS_LIST_HEADERS / AS_LIST_LINES — List definition tables whose deduplication processing consumes the rules defined here.
• AS_LIST_RULES_TL (if present in the installation) — Translation table potentially holding language-specific rule names.
• AS_DEDUPE_* processing entities — Application logic that evaluates the TYPE and rule criteria against list members.
• FND_CONCURRENT_REQUESTS — Joined via REQUEST_ID to trace the concurrent program that created or updated a rule.
• FND_USER — Joined via CREATED_BY and LAST_UPDATED_BY for audit reporting.

As with any OSM-schema object, direct DML should be avoided; rule maintenance is expected to proceed through the supported Oracle Sales Foundation setup UI, with queries limited to read-only reporting and diagnostics.