Results for “autocash_hierarchy_id”

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

Overview

AR.AR_AUTOCASH_RULES is a Receivables (AR) module table that stores the application method associated with each rule belonging to an AutoCash Rule Set. In Oracle EBS, AutoCash Rule Sets define the ordered strategy by which the AutoCash process applies a customer receipt against open transactions. Each individual rule within a set — Automatic, Oldest First, Overdue First, Discount First, Partial Match, or a specified custom method — is materialized as a row in AR_AUTOCASH_RULES, and the sequence in which these rules are evaluated is persisted in this table. The object carries a VALID status in the AR schema and is documented as a child of AR_AUTOCASH_HIERARCHIES, which holds the rule-set header.

The metadata notes a PRIMARY KEY constraint AR_AUTOCASH_RULES_PK on AUTOCASH_RULE_ID, and a unique key AR_AUTOCASH_RULES_UK1 on the combination of AUTOCASH_HIERARCHY_ID and RULE_SEQUENCE. A single foreign key is documented, linking AUTOCASH_HIERARCHY_ID back to AR_AUTOCASH_HIERARCHIES. Based on the mined foreign-key structure, the heuristic Data Vault classification is satellite-leaning: the table primarily describes attributes of a rule-set parent and could be modeled as a satellite of the hierarchy hub, though it also behaves as a dependent child in the classical relational sense.

Key Information Stored

The table contains 25 documented columns. The most operationally significant are the following:

• AUTOCASH_RULE_ID — the surrogate primary key (AR_AUTOCASH_RULES_PK and unique index AR_AUTOCASH_RULES_U1) that uniquely identifies each rule row.
• AUTOCASH_HIERARCHY_ID — the foreign key to AR_AUTOCASH_HIERARCHIES, identifying the AutoCash Rule Set to which this rule belongs.
• RULE_SEQUENCE — the ordinal position of the rule within the set; combined with AUTOCASH_HIERARCHY_ID, it forms unique index AR_AUTOCASH_RULES_U2, guaranteeing at most one rule per sequence position per hierarchy.
• AUTOCASH_RULE — the rule code itself (for example Automatic, Oldest First, Overdue First, Discount First, Partial Match). Combined with AUTOCASH_HIERARCHY_ID, it forms unique index AR_AUTOCASH_RULES_U3, preventing the same rule from appearing twice in one set.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns capturing audit and concurrency information for the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle Applications descriptive flexfield (DFF) columns, available for customer-specific extensibility on the rule definition.

Care should be taken to distinguish the surrogate key AUTOCASH_RULE_ID from the business-key candidates exposed by the two composite unique indexes (hierarchy plus sequence, and hierarchy plus rule). The natural identity of a rule is the combination of the rule set and the rule value or the rule set and the sequence, not the numeric identifier.

Common Use Cases and Queries

Typical uses fall into configuration reporting, migration support, and troubleshooting of AutoCash behavior. A common query lists every rule for a given rule set in evaluation order:

• Join AR_AUTOCASH_RULES to AR_AUTOCASH_HIERARCHIES on AUTOCASH_HIERARCHY_ID to report the rule name together with its parent set name, ordered by RULE_SEQUENCE.
• Reverse-lookup queries locate which AutoCash Rule Sets contain a particular rule, using AUTOCASH_RULE in the predicate — useful when updating application logic globally.
• Data-migration and setup-validation scripts reconcile rule sequences between environments by comparing AUTOCASH_HIERARCHY_ID, RULE_SEQUENCE, and AUTOCASH_RULE across instances.
• Audit reports exploit LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recently modified AutoCash configurations.

Related Objects

• AR.AR_AUTOCASH_HIERARCHIES — the parent table; joined on AUTOCASH_RULES.AUTOCASH_HIERARCHY_ID = AR_AUTOCASH_HIERARCHIES.AUTOCASH_HIERARCHY_ID. This is the only documented foreign key and the definitive parent relationship.
• AR.AR_CASH_RECEIPTS and the AutoCash execution process — the rule set defined here is consumed when the AutoCash workflow resolves matching strategies for open transactions.
• AR.AR_CASH_RECEIPT_HISTORY — records the AutoCash results applied, allowing reverse validation of the rule that was effective at posting time.
• AR.AR_PAYMENT_SCHEDULES — the open transactions against which rules are applied; useful when recreating what AutoCash would have selected.
• AR.AR_RECEIVABLE_APPLICATIONS — the applied receipts produced after AutoCash matching, directly traceable to the rule that triggered application.
• AutoCash Rule Sets setup form — the UI that reads and writes AR_AUTOCASH_RULES rows and enforces sequence uniqueness.

Because the table is narrow and tightly scoped to rule-set configuration, reporting on it is straightforward, and most analytical joins begin from AR_AUTOCASH_HIERARCHIES and descend into AR_AUTOCASH_RULES by hierarchy identifier.