substitution & validation

[Former Member]

What is Validation and substitution, where it will be usefull can anyone plz help me out.

[former_member1006152]

I hope the following material shall be useful to you.

Validations ,Substitutions and Sets

FI Validations

Validations are used to check settings and return a message if the prerequisite check condition is met. You can use validations to supplement existing SAP logic to fit your business needs. A validation is a valuable tool that can be used in many of the financial and controlling modules.

Define validations (GGB0)

Functional areas

Functional areas within the FI enterprise structure are used to organize your business for cost of sales accounting. Functional areas allow you to segregate and classify different types of costs within one expense account. This makes it possible, for example, to use a single labor account to determine what amount of labor is spent directly on production as opposed to sales or administration. It is possible to report on functional areas from both FI and profit center accounting.

Define functional areas (OKBD)

Define substitutions (GGB1)

Create sets (GS01)

Activate functional area substitution (OBBZ)

Advanced validations and substitution configuration.

Define functional areas (OKBD):

Functional area: Enter the four-character alphanumeric identifier for your functional area.

Name: Enter a descriptive name for your functional area. This entry is alphanumeric and can be up to 25 characters long.

Define substitutions (GGB1):

Substitution; Enter seven-character alphanumeric identifier for your substitution. The identifier can be anything you want it to be.

Application area: enter the appropriate area. The application area is the module or sub module that you wish to create the substitution for. The available options are as follows;

AM: asset management

CO: controlling

FI: financial accounting

GL: special ledger

JV: joint venture accounting

KC: enterprise controlling—SAP EIS

PC: profit center accounting

PS: project systems

Call up point: enter the appropriate call up point. Calls up points determine when the substitution is run. The available calls up points are dependent upon the application area that is selected. For FI application area, the following calls up points are available.

0001 Document Header: Use this call up point to substitute entries at the document header level. The entries that are usually available for substitution at this point are stored in the BKPF table.

0002Line Item: Use this call up point to substitute line item entries within a document. The entries that are usually available for substitution at this point are stored in the BSEG table.

0003Complete Document: this call up point substitutes settings for the documents a whole. This activity is also known as a matrix substitution.

0005 Cost of Sales Accounting: this call up points used for functional area substitutions.

Prerequisite: the prerequisite uses Boolean logic to determine if a condition is true.

If the condition is true, the substitution is carried out. If it the condition is not true, no further processing occurs. Click the Flds in Bool. statement button to display and select the available fields to use in your logic. The valid Boolean logic operators are =,>, < and <>. The entry immediately following the Boolean statement must be put in single quotation marks (‘ ‘) unless a set is being used. Sets group together of a number of entries. When you use sets, the system needs to match only one of the entries in the set for the prerequisite to be true. Sets are defined using report writer. The creation of sets will be covered later in this section. To link multiple logic steps together, either an AND or an OR is required at the end of each statement line.

Substitutions: the Substitutions section is where you tell the system what values to replace. You have the option of either using constant values or using a user-exit to specify values or carry out other logic statements.

Warning---within validations and substitutions, some of the logic is case sensitive. Be sure to type in your logic using ALL CAPS. The syntax check will not tell you that you have an error if it’s in lowercase.

Create sets (GS01):

Set ID: enter 12 –character alphanumeric identifier of your set in the Set ID box. This is the set name that you will refer to when using the set.

Table: enter the name of the table that contains the field you want to create the set for in the table box. This field and others like it appear in many different tables. It is important to know which table is used at the time you are using the set.

Activate functional area substitution (OBBZ):

1. Enter the four-character identifier for the company code (CC) for which you want to activate the substitution. As with validations, you can only have one substitution active per company code per call up point.

2. Enter the call up point (Call Pnt) at which you want your substitution to be executed.

3. Enter the identifier of the substitution that you wish to activate.

4. The description field fills in automatically based on the substitution that you choose.

5. Enter the activation level (Activtn Level) for which you would like to activate the

Validation. There are three codes to simplify your entry.

0: Not Activate (validation will not execute)

1: Activated at all levels throughout the system.

2: Activated at all levels throughout the system except for batch input.

Advanced validations and substitution configuration.

Link programs to substitutions (GCX2)

Bool Class: The Boolean class specifies where the field is being used or is excluded. Boolean classes map roughly to the combination of application area and call up point. Here is partial listing of Boolean classes:

1: Coding Block –used for CO line items.

8: Document Header—used for FI items.

9: Document Header and line Item—used for F I items.

16: Cost of Sales Accounting—used for functional areas.

Class Type-A class type refers to whether a field is used in Boolean statement substitution fields, or both. Here’s a listing of them:

B—used for fields that are to be used in Boolean statements

S—used for fields that are to be used for substitution

A—used for fields that can be used in both Boolean statement and for substitution

Table—The name of the table in which the field you wish to use or exclude resides

Field—The name of the field you wish to use or exclude.

Exclude—if this field is checked, the field is excluded for use for the class type specified in the record. If this indicator is set, you can not change it, and you can not add the field in the configuration table that adds or excludes fields.

[Former Member]

Hello

Validations, you can check values and combinations of values as they are being entered in the SAP system. Because validation occurs before data is posted, only valid information enters the FI-SL application component.

Examples of validation rules:

· If the cost center is 10, then the account must be 400000.

· If the currency is INR and the document type is SA, then the plant must be 02.

Substitution rules are stored in the Rule Manager that, as data is being entered, substitutes this data. Substitution occurs before the data is summarized in a summary database.You can use a substitution simultaneously at different callup points and you can create different dependencies for substituting data

Reg

*assign points if useful

[Former Member]

plz visit the following link