Oracle Accounting Hub Cloud (AHCS) — Mapping & Rules Cheat Sheet
Created: 2025-08-15 18:59
Author: Teonna Dorsey (original reference)
Core Concepts
• Sources: Fields coming from feeder systems (e.g., Product, Customer, Event Type).
• Mapping Sets: If <Source> equals X, then segment value = Y. Can be table-based.
• Accounting Rules: Define debit/credit accounts per event class/type.
• Journal Entry Rule Sets (JERS): Group rules for a subledger and assign to event
classes.
• Description Rules: Build journal line descriptions from source attributes.
• Supporting References: Track attributes for reconciliation and drill-down.
Typical Flow
1) Register feeder system in AHCS.
2) Define sources and import formats (file layout or integration).
3) Create mapping sets for each GL segment you will derive.
4) Define journal line rules and tie them to a JERS.
5) Create description rules and accounting attribute assignments.
6) Test import, validate, and transfer to GL.
Tips
• Keep mapping sets normalized. Avoid hard-coding multiple segments in one rule.
• Use defaulting rules for "otherwise" cases to prevent errors.
• Track changes with versions and export backups.
• Validate early with a small file; review error and warning reports.
Mini Example
• Event: Subscription invoice line
- Source attributes: ProductFamily="SaaS", Geo="US"
- Mapping: Company from Geo, Account from product, CostCenter from BU
- Accounting: DR AR Trade, CR Revenue SaaS
- Description rule: "{Customer}-{Invoice}-{Product}"