Automatic Payments
Dunning Program
Correspondence
Special General Ledger Transactions
Parking Documents
Validations and Substitutions
Data Archiving in FI

Using Additional Techniques for Substitutions and Validations

Objective

After completing this lesson, you will be able to work with rules and sets in validation and substitution

Rules

Visual representation of conditional logic for account group management, highlighting prerequisites, checks, and rules to ensure data integrity and workflow compliance.

A rule is a logical statement that you can use in a prerequisite statement, check, or another rule.

A rule permits complex logic to be summarized and can be reused. Technically, a rule is nothing more than a prerequisite or the check of a validation.

If a boolean statement is used often, or if it contains complex logic, you can create a rule for it. For example, a validation that contains an extensive prerequisite that is also used in a substitution, as in the rule RULE1 AND BKPF-BLART <> ‘G/L Account Posting’.

Here, the name of the rule is RULE1. When the system processes this statement, it first processes RULE1, and then checks whether the document type is not ‘G/L Account Posting’. The name of a rule can be a maximum of 11 characters long.

Rule in a Matrix Validation

A financial validation rule example demonstrates conditional logic for account checks, requiring specific criteria to ensure data accuracy and compliance.

You can also use rules within a statement that uses mathematical processing.

For example: RULE1 AND BKPF-BLART <> ’SB’.

In this example, the rule is named RULE1. When the system processes this statement, it first processes RULE1 and then checks whether the document type is not SB. The rule name can be a maximum of 11 characters long.

How to Create and Use Rules

DemoStart Demo

ovSets

Illustration of a user-access control system linking user groups to account management fields, emphasizing prerequisites and checks for data validation within specified tables.

A set is a flexible data structure for mapping ordered amounts and hierarchies. Sets are maintained and administrated centrally. They are used in almost every component of the FI-Special Purpose Ledger system.

The sets are used in the following examples:

  • In boolean logical formulas in validation
  • In substitution and ledger selection
  • During allocation (assessment or distribution)
  • In planning
  • In roll-ups
  • In currency conversion

To improve system performance, use basic or single-dimension sets rather than long lists of boolean statements or user exits.

The syntax rule is table name - field name IN set name.

As illustrated in the preceding figure, if the user is contained in set USER-GROUP, the system checks whether this user uses a corresponding account (included in the set ACCOUNT-MANAGEMENT).

Set Usage

Illustrates a structured logic for data validation and classification, linking account management and cost management sets with predefined prerequisites and checks for alignment.

You can use multisets, which are a combination of sets for various fields (dimensions), to execute cross-validation with values of different characteristics.

If the user enters one of the expense accounts 61003000, 61004000, 61005000 or 61006000, the user must use a corresponding cost center (TA##1100, TA##1200, TA##1300 or TA##1400).

Use Rules and Sets to Create a Substitution

ExerciseStart Exercise

Summary

  • Rules summarize complex logic for reuse in validations and substitutions.
  • Sets map ordered amounts and hierarchies for efficient processing.
  • Use multisets for cross-validation with different characteristics.
  • Additional techniques enhance validation and substitution capabilities.
Learning

SAP FacebookSAP YoutubeSAP LinkedIn