Cross-Validation Rules (CVRs) are specifically designed to control the combinations of key flexfield segment values that can be used during data entry. For the Accounting Flexfield, a CVR on the Balancing Segment can enforce that certain balancing segment values (like intercompany accounts) are always used in valid combinations with other segments, ensuring automatic balancing during journal creation. This is a core GL setup task for complex enterprise structures.

In Subledger Accounting (SLA), accounting events are stored in intermediate tables before being transferred to GL. If the ‘Create Accounting’ program is run infrequently (e.g., only at month-end), these events tables can become extremely large, causing the creation process to slow down. The standard performance recommendation is to run the ‘Transfer to GL’ program more frequently (e.g., daily) to keep the events tables manageable, which directly improves the performance of the ‘Create Accounting’ process.

A ledger is built on a Chart of Accounts, an Accounting Calendar, a Currency, and an Accounting Method. For the setup to be valid, the period type (such as Monthly) defined in the Calendar must be compatible with the Chart of Accounts’ requirement for period-end processing. This is a fundamental dependency during ledger creation in the Accounting Setup Manager (ASM).

Reversal Criteria Sets in General Ledger provide granular control over which journals are automatically reversed. You can define a criteria set based on specific attributes like Journal Source, Category, or Account. By assigning this criteria set to manual journals at entry (or setting it as a default for a user), you ensure only those journals meeting the criteria are targeted for automatic reversal, effectively excluding subledger-generated journals.

Reporting Currencies are a feature used to report on the primary ledger’s data in one or more additional currencies. You can assign multiple reporting currencies (like USD) to different primary ledgers (in EUR, JPY). This allows you to run reports in the common reporting currency (USD) across all ledgers, effectively creating a currency-based consolidation for management reporting, without the need for the intercompany eliminations required in a legal consolidation tool like GCS.

In R12, security is primarily governed by Data Access Sets. Even with a powerful responsibility, if the user’s assigned Data Access Set does not grant read and/or write access to the specific ledger and balancing segment value (or all segment values) associated with the journal batch, they will not be able to query or see it. This is a fundamental and common security configuration issue.

Before the system can automatically create intercompany balancing entries, it must know the legal relationships between balancing segment values (BSVs). This is defined in the Intercompany Relations screen (Setup > Financials > Flexfields > Key > Segments > Intercompany), where you specify which BSVs are valid partners. Without this setup, the system has no rule to follow for generating the offsetting entry in the partner company.

The Account Hierarchy Manager (AHM) is the designated tool for creating alternative, management-focused account hierarchies without changing the core chart of accounts structure. You can define a custom hierarchy that groups accounts in the required non-standard way. This hierarchy can then be directly referenced in a Financial Statement Generator (FSG) report definition, providing a flexible and maintainable solution for custom management reporting.

The Accounting Events Manager (Navigator: Subledger Accounting > Accounting Events > Accounting Events Manager) is the central diagnostic tool for SLA. By querying for a specific event (like an invoice) and clicking ‘View Accounting’, you can see a complete breakdown. This includes the applied accounting method, transaction objects, source values, derivation rules used, and the final accounted amounts and accounts for each line. It is essential for troubleshooting accounting issues.

Cross-Validation Rules (CVRs) are specifically designed to control the combinations of key flexfield segment values that can be used during data entry. For the Accounting Flexfield, a CVR on the Balancing Segment can enforce that certain balancing segment values (like intercompany accounts) are always used in valid combinations with other segments, ensuring automatic balancing during journal creation. This is a core GL setup task for complex enterprise structures.0