SAP ABAP IMG Activity SIMG_CFMENUCX01_VA01 (Define Validations)

Hierarchy

☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ EC-CS (Application Component) Consolidation
     ⤷ FC00 (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)

IMG Activity

ID	SIMG_CFMENUCX01_VA01	Define Validations
Transaction Code	S_ALR_87001931	(junk)
Created on	19981222
Customizing Attributes	SIMG_CFMENUCX01_VA01	Define validations
Customizing Activity	SIMG_CFMENUCX01_VA01	Define validations

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUCX01_VA01

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

• Prerequisite

  When defining a validation step, you can define a prerequisite that must be met before a validation check is done. However, it does not make sense to define prerequisites for validations of reported, standardized and consolidated financial data, because in these particular validations the prerequisites are NOT taken into consideration. You should therefore define the validations without any prerequisites in this step.

  By contrast, however, you can define prerequisites for validations of postings. For more information on this, see the step Define validations in the section Manual Postings.

• Check

  In this portion of a validation step, you specify the data which is to be validated, and the operations to be performed with the data.

  You enter a mathematical equation (also called formula), which consists of rules for selecting the data, and an operator.

• Message

  In this portion of a validation step, you specify which message is to be displayed if the validation finds discrepancies.

You use the following data structures to define a validation step (see below for further details):

• ECCSDAT    Structure of data requiring validation
• ECCSPAR    Structure for prior year/period comparison
• ECCSEQV    Structre for equivalency checks

The step Assign validations distinguishes between validations that are assigned to consolidation units for checking reported and standardized data, and validations that are assigned to consolidation groups for checking consolidated data.

Example

You might define a validation that contains a validation step (among others) to ensure that the total value of assets matches the total value of liabilities and equity.

You would define the validation step as follows:

• 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

Standard settings

A validation is predefined in the standard system 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 that you want checked on the initial screen.

Activities

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

Establish how many separate validations you need for the consolidation units and consolidation groups.

Define any new validations that you require as follows:

1. Create a validation with a name and description.
2. The first time a validation is defined, the system configures the message class. You must specify a message class in the range reserved for R/3 customers (Z*). If a message class dedicated to validations does not yet exist, 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" for the Boolean Class. Then you can replace old message classes with new ones.
3. Create the first validation step by choosing "Edit -> Insert entry".
4. Leave the prerequisite blank.
5. Define the validation check by using the Formula Builder to enter a formula with the following syntax:

   SUM ( *table field* ) WHERE *RULE* *operator* SUM ( *table field* ) WHERE *rule*

   Here the variables (or placeholders) are denoted with asterisks (*). Substitute the variables as follows:

1. *table field*
You can substitute this variable with local currency, transaction currency and group currency fields as well as quantity fields.
You can insert any of the following fields:
Local currency (cumulative value)
Local currency (periodic value)
Group currency (cumulative value)
Group currency (periodic value)
Transaction currency (cumulative value)
Transaction currency (periodic value)
Quantity (cumulative value)
Quantity (periodic value)
2. *rule*
Substitute this variable with the name of the validation rule.
To define new rules, see activity 6.
3. *operator*
Substitute this variable with any of the following comparison operators:
< > >= <= =

In addition to using the formula as listed above, you can also define formulas without the second portion SUM ( *table field*) WHERE *rule*. For instance, you could define the following short formula:
SUM ( *table field* ) WHERE *rule* >= 0


Note

The system uses the Formula Builder to convert the formula that you created into the following formula syntax:

SUM ( ECCSDAT-*value/quantity field* ) WHERE *rule* * operator* SUM ( ECCSDAT-*value/quantity field* ) WHERE *rule*

6. Define new validation rules if needed.
1. Specify a name for the rule and a description, then choose the Formula Builder.
2. Specify the fields that are to be selected during the check (Structure ECCSDAT).
Keep in mind that you must always specify the field "FS item".
The characteristics dimension, version, year, period, consolidation chart of accounts, consolidation unit and consolidation group should only then be used in the validation rule, if the rule should only be valid for a certain characteristic value of this characteristic. As a rule you do not normally specify this characteristic, so that you can execute the validation step for any dimensions, versions, consolidation charts of accounts. The system determines these characteristics at the start of validation via the global parameters and the organizational units selected by the monitor (if they are specified).
Custom characteristics can be used exactly like the characteristics which are delivered by SAP
3. For each field, use the operator '=' (equals sign) to specify the value of the field to be selected.
Example: FS item = '0007100000'


Further notes for the defintion of rules


FS item values to be checked

• To cumulate all FS items data, you can enter the FS item = ' ' that is space. The system then selects all value items, that means 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. Keep in mind that the system interprets the totals items and selects each cumulated value.
  Each FS item can only be contained once in the set, otherwise the system selects the item value repeatedly. 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 which belong to it. Then the system interprets and selects the values of the totals items and additionally the values of the value item.
  To get round the problem of multiple selection, you can use totals items directly in the validation rule, therefore without set.
• You can limit the item values to subassignments, for example with the following rule:
  FS item = ' ' AND Subassignment = '120'
  

  Consolidation units to be checked

• You can limit the check to certain consolidation units, for example with the following rule:
  Consolidation unit = 'CUXXX'
As well as that you can limit the check to consolidation units with a certain attribute, for example the country:
Country/Cons unit = 'USA'
Then exactly those consolidation units are included in the check, to which the 'USA' is assigned.
The advantage is that you can define individual validation steps for certain 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" for the (data structure ECCSDAT).
  Example: Year = Prior year
For equivalent units, you can specify equivalent fields&#x

Business Attributes

ASAP Roadmap ID	204	Establish Functions and Processes
Mandatory / Optional	2	Optional activity
Critical / Non-Critical	1	Critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	SIMG_CFMENUCX01_VA01	0	HLA0100228	Validation

Maintenance Objects

Maintenance object type

C

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
CXV2	T - Individual transaction object	CXV2	0000000001	☐	☐	Create validation
CXV2	T - Individual transaction object	CXV3	0000000002	☐	☐	Change validation
CXV2	T - Individual transaction object	CXV4	0000000003	☐	☐	Display validation

History

Last changed by/on	SAP	20101202
SAP Release Created in