Ansicht
Dokumentation

SIMG_CFMENUCX01_VA01 - Define Validations

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by SAP AG.

In this process step, you define validations for reported data, standardized financial data, and consolidated financial data. Each validation consists of one or more validation steps. Each validation step is made up of the following elements:

• Prerequisite

When defining a validation step, you can define a prerequisite that must be met to trigger a validation check. However, it is not recommended to define prerequisites for validations of reported data, standardized financial data, and consolidated financial data, because the system does not take this prerequisite into account during validation. Therefore, define validation in this process step without any prerequisites.

On the other hand, you can define prerequisites when validating postings. For more information about this, see the process step Define Validations in the Manual Postings section.

• Check

In this part of the validation step, you specify the data to be accessed during validation, and the operations to be performed with the data.

You define a mathematical formula. This contains rules for data selection and an operator.

• Message

In this part of the validation step, you specify the message to be issued by the system if the check fails.

When defining a validation step, you use the following data structures (see below for further details):

• ECCSDAT,,Structure of the data to be validated

• ECCSPAR,,Structure for prior year/period comparisons

• ECCSEQV,,Structure for equivalency checks

In the process step Assign Validations, you assign a validation to the consolidation units for checking the reported data and standardized financial data or to the consolidation groups for checking consolidated financial data.

You could define a validation in which the total value of assets matches the total value of liabilities and equity as a validation step (among others).

In the validation step, make the following settings:

• Check

SUM (Cumul. local currency ) WHERE ASSETS = SUM (Cumul. local. currency ) WHERE LIABILITIES

• Rule ASSETS

FS item = '0001000000'

• Rule LIABILITIES

FS item = '0002000000'

• Message

Total assets are not equal to total liabilities and equity

In the SAP standard delivery, a validation is predefined for each of the charts of accounts 01, 11, and 12.

These validations only contain a check for totals records in local currency. It is not necessary to define a validation for checks in both local and group currency for each chart of accounts. If you start validation from the data monitor or consolidation monitor, the system automatically runs checks in the correct currency. If you start validation from the application menu, you can specify the currency to be checked on the initial screen.

Establish which validation steps you need for the reported data, standardized financial data, and consolidated financial data.

Check how many different validations you require for the consolidation units and consolidation groups.

Define new validations as required. To do this, do the following:

1. Create a validation with a name and descriptive text.
2. When validations are defined for the first time, the system performs a configuration of the message class. For the configuration, you must specify a message class in the customer namespace (Z*). If no message class for validations exists yet, choose the 'Create' function.
   If you want to change the message class later on, on the initial screen for defining validations, choose "Environment -> Change Message Class". Enter “043” as the Boolean class. Then you can replace the old message classes with new classes.
3. Create the first validation step. To do this, choose "Process -> Add Step".
4. Leave the prerequisite for the validation step empty.
5. Define the check for the validation step. To do this, use the Formula Editor. Use the Formula Editor to enter a formula with the following syntax:

SUM ( *Table Field* ) WHERE *Rule* *Operator* SUM ( *Table Field* ) WHERE *Rule*

In this formula syntax, input variables are marked with *. When defining a check, you can assign values as follows:

1. *Table Field*

Here, you enter the field for local currency, transaction currency, group currency, or quantities.

The following fields can be transferred:

Local currency (cumulative value)

Local currency (period value)

Transaction currency (cumulative value)

Transaction currency (period value)

Group currency (cumulative value)

Group currency (period value)

Quantity (cumulative value)

Quantity (period value)

1. *Rule*

Here, enter the name of the validation rule. To define new rules, see step 6.

1. *Operator*

Here, enter one of the following comparison operators:
< > >= <= =

As an alternative to the formula listed above, you can also define formulas without the second portion SUM (*Table Field*) WHERE *Rule*. For example, you could define the following short formula:
SUM ( *Table Field* ) WHERE *Rule* >= 0

Note

The formula created by using the Editor is converted by the system into the following formula syntax:

SUM ( ECCSDAT-*Value/Quantity Field* ) WHERE *Rule* *Operator* SUM ( ECCSDAT-*Value/Quantity Field* ) WHERE *Rule*

1. Define new check rules if required.
1. Specify a name for the rule and a descriptive text, then choose the Formula Editor.
2. Specify the fields to be selected during the check (structure ECCSDAT).

Note that you must always specify the field "FS Item".

You should only use the characteristics dimension, version, year, period, consolidation chart of accounts, consolidation unit and consolidation group in the validation rule if the rule is only to be valid for a specific characteristic value of this characteristic. As a rule, you do not specify these characteristics, so that you can execute the validation step for any dimensions, versions, consolidation charts of accounts, and so on. The system determines these characteristics at the start of validation through the global parameters and the organizational units selected by the monitor (if they are specified in the rule).

You can use custom characteristics exactly like those characteristics delivered by SAP.

1. For each field, use the operator = to specify the characteristic value of the field to be used in the selection.

Example: FS item = '0007100000'

Further notes for defining rules

FS item values to be checked

• To total all FS items data, you can enter the FS item = ' ' that is, space. The system then selects all value items, that is, balance sheet items, income statement items and statistical items.

• You can use FS item sets. In these FS item sets, you can enter value items, totals items, and other sets. Note that the system interprets the totals items and selects each totaled value.
  Each FS item can only be contained once in the set, otherwise the system selects the item value multiple times. For example, a multiple selection occurs when you include a value item and a totals item in the set and the totals item contains this value item.
  Sets with item ranges are problematic when the ranges include totals items as well as the value items that belong to them. Then the system interprets and selects the values of the totals items and also the values of the value item.
  To avoid the problem of multiple selection, you can use totals items directly in the validation rule, that is, without a set.

• You can limit the FS item values to subassignments, for example, with the following rule:
  FS item = ' ' AND subassignment = '120'
  

Consolidation units to be checked

• You can restrict the check to specific consolidation units, for example, with the following rule:
  Consolidation unit = 'CUXXX'

You can also restrict the check to consolidation units with a specific attribute, for example, country/region:
Country/region / cons unit = 'USA'
Then precisely those consolidation units to which country/region 'USA' is assigned are included in the check.

The advantage is that you can define individual validation steps for specific consolidation units, but can simultaneously assign the validation of a comprehensive number of consolidation units.

Comparisons and Equivalent Units

• To compare periods or fiscal years, you can specify comparison fields (data structure ECCSPAR) for the fields "Period" and "Fiscal Year" (data structure ECCSDAT).
  Example: Year = Prior year

• For equivalency, you can specify equivalent fields (data structure ECCSEQV) for the fields (data structure ECCSDAT).
  Example: Cons unit = Equivalent cons unit

See also process step Specify Equivalencies.

• For other comparisons, you have to specify fixed characteristic values in the validation rule.
  Example: Version = '900' for version comparison
  

1. Specify the message to be issued if the check fails.

If the message does not yet exist, choose "Environment -> Maintain Messages". You can also maintain new messages directly from maintenance of validation steps.

1. Define the other validation steps.
2. Define any additional validations you require.

In the hierarchical validation log, you check the results of the validation step by step.

To transport your settings, choose "Validation -> Transport".

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 11954 Date: 20240523 Time: 165956     sap01-206 ( 159 ms )