Define Validation

In validation , the SAP System checks whether particular input values fulfill one or more of your user-defined conditions.

These checks take place during the entry of values into the system. If the conditions are fulfilled, the input value is transferred into the system. If the conditions are not fulfilled, the SAP System displays a user-defined message.

Preconditions

Before you edit your CO-relevant objects (such as cost centers, cost elements, and orders), you should maintain the conditions under which the SAP System is to check the eligibility of these objects.

You define these conditions as either controlling area related or related to a callup point predetermined by SAP.

The callup point flags a particular point in the flow of a transaction.

Standard settings

The following callup points are defined in the SAP System for controlling:

• 0001: Document row

This callup point is used for all CO-relevant postings in external accounting, as well as for all CO-internal postings. The R/3 System stores the data in the structures COBK (CO-object: document header ) and COBL (account assignment block).

• 0002: CO-internal posting: Sender-Receiver-Validation

Used only for CO-internal postings and only for the validation of sender-receiver relationships. The data exists in the following structures:

• COBL_GENERAL (Sender/Receiver Header Information from COBL)

• COBL_RECEIVER (Receiver Object Information)

• COBL_SENDER (Sender Object Information)
  

Note that you can only use these three structures for validation at callup point 0002. It is also not possible to switch sender structure (COBL_SENDER) and receiver structure (COBL_REVCEIVER)

The structures of callup point 0002 contain additional fields that are not available in the structures of callup point 0001. For example, COBL_RECEIVER and COBL_SENDER contain the sender- or receiver company code, while COBL does not contain the partner company code.

You can specify in the sender and receiver structures for which account assignment type (true or statistical) the validation is to be executed on the objects. In the sender structure (COBL_SENDER) you can use the substructure "Account assignment types of CO account assignments for partner objects" (COBLP_COKZ). In the receiver structure (COBL_RECEIVER) you can use substructure "Account assignment types of CO account assignments" (COBL_COKZ).

To provide a better overview, the system offers you only the organizational units of the true account assignment objects in the structures COBL_SENDER and COBL_RECEIVER. It is therefore not possible to carry out a validation of organizational units for statistical objects.

For system performance reasons, the R/3 System does not fill the structures COBL_SENDER and COBL_RECEIVER with statistically assigned objects during periodic allocations. Validation is therefore only possible for true account assignment objects for periodic allocations.

• 0100: Document header

This callup point is used for manual postings in CO, for example, during the reposting of costs or during activity allocation. The data is available in the structure COBK (CO object: document header).

Caution

If you are allocating costs to profitability segments using assessment, the system does not always fill the "PAOBJNR" field (profitability segment). If account-based Profitability Analysis is active, the field is filled. If it is not active, the "PAOBJNR" may not always be filled (this is due to technical restrictions).

The "CO_KAERG" field (account assignment type: Profitability segment) is always filled by the system.

Examples Example: Validation at callup point 0001

Example: Validation reposting to another company code, callup point 0002

Example: Validation of non-statistical account assignments at callup point 0002

Activities

1. Determine which callup points you wish to run eligibility checks on, and in which controlling areas.

2. Choose "New entries".

3. Enter the controlling area where you wish to execute validation.

4. Enter a callup point.

5. Save your entries.

6. Choose Environment -> Validation followed by Validation -> Create.

7. Enter a name and callup point.

8. If you use an existing validation as a reference, enter the validation you require as a reference. Next, either change or retain the data in the reference according to your requirements, then save it.

9. If you do not use a reference, proceed as follows:

a) Confirm your entries by choosing "Continue".

b) Enter a description of the validation.

c) To define the validation steps, choose "Insert entry".

d) Enter a description for each validation step.

e) Maintain messages, conditions, and checks. Use the function "Fields for bedding" to do so.

You can maintain rules and messages by choosing the corresponding function.

f) Save your validation steps.

g) Return to the "New Entries: Overview of added entries"

10. Enter the validation name for your controlling area.

11. Enter an activation level. Activation level "1" guarantees that the validation is active in the corresponding controlling area.

a) Save your validation.

Note on transport

There is a special function available in the IMG called "General Controlling". This is for validation transport

Further information

For more information see the R/3 Library under "AC - Financials -> FI - Financial Accounting -> Special Purpose Ledger -> Validations and Substitutions".