| # Print Cross Validation Rule Violations (tfgld0451m000) Use this session to print violations against the General Ledger. A violation occurs when a ledger account and dimension combination is not allowed according to the selected validation rules. You can run this session for a range of validation rules (status Active or Draft), and for a range of ledger accounts. Related topics Cross validation rules – examples Selection Range Validation Rule A user-defined rule that allows you to indicate which combinations of GL accounts and dimension values are valid. A cross validation rule requires at least one rule element. Cross validation rules are applied to all transactions registered in the General Ledger. In case of multiple financial companies, validation rules can be either company-specific or applicable across all companies. Version The validation rule version. LN generates the version numbers. Options Include Draft Rules If this check box is selected, cross validation rules with status Draft are also taken into account. Note If a higher draft version of an active rule exists, the draft version will be checked whereas the active version will be ignored. Date for Check The date and time for which the check must be performed. General Ledger Selection Range Financial Company A company that is used for posting financial data in Financials. You can link one or more enterprise units from multiple logistic companies to one financial company. Note This selection range is only available if the range of validation rules applies to multiple companies. Ledger Account A register used to record financial transactions and to accumulate the values of the transactions for reporting and analysis. The ledger accounts classify the transactions into categories such as revenues, expenses, assets, and liabilities. Fiscal Year / Period A separate period, or year for financial purposes. Three financial period types exist: Fiscal, in which all transactions are recorded (for example, 12 months). Reporting, for management requirements (for example, 52 weeks). Tax, for tax regulations (for example, 4 quarters). Transaction Category A way to categorize transaction types, for example journal vouchers, recurring/reverse journals, purchase invoices, and sales invoices. The category defines how to process a transaction linked to the selected transaction type. Document The identification of a transaction. The document code is a combination of: Transaction-type code Series number Sequence number |