Using Boolean Statements in FI-SL

You can enter Boolean Logic statements for:

Validations

You can enter statements that define the conditions for using and validating incoming data.

Substitutions

You can enter statements that define the conditions for substituting incoming data.

Ledger selection

You can enter statements that define the conditions for selecting a ledger for posting.

Report Writer

You can enter statements that define conditions for selecting report data.

Rollups

You can enter statements that define the conditions for transferring substitution data to rollup ledgers.

Boolean Statements in Ledger Selection

In ledger selection, you can use a Boolean statement to select a ledger for posting.

This graphic is explained in the accompanying text.

If an account is a profit and loss account, then post the transaction to the ledger.

When you determine which activities will update a ledger, you can also define specific ledger selection conditions for selecting the ledger for posting. You can enter Boolean Logic statements in the Condition field on the Change Ledger: Ledger Selection screen.

This graphic is explained in the accompanying text.

Activity grouping code: RFXX

Ledger: D4

Condition: GLT1-RCNTR = '100'

In this example, transaction data is posted to ledger D4 for all RFXX activities, when the cost center is 100.

When data is transferred into the FI-SL application component, you can post the data to a ledger according to the statement entered in the Condition field.

This graphic is explained in the accompanying text.

For improve system performance, you should enter a Boolean Logic rule rather than a statement.

Boolean Statements in Report Writer

In Report Writer, you can use a Boolean statement to select data for reports. Using Boolean statements results in slower processing, but you can define more complex selection criteria.

This graphic is explained in the accompanying text.

If the cost center is 100 and the company code isnot 2000, select the data for a report.

You enter Boolean Logic rules in the Rule name field, which appears in a dialog box when you choose Edit → Selection rule on the Create Report: General Data Selection screen.

This graphic is explained in the accompanying text.

You create a selection rule called AR-REPORT. This selection rule contains the following selection statement:

GLT1-RCNTR = '100' AND GLT1-BUKRS <> '2000'

This statement instructs the system to select all records where the cost center is 100 and the company code is not 2000.

The selection statement you use in a report definition can only refer to the table defined in the report's library.

This graphic is explained in the accompanying text.

A statement can only refer to table GLT1 if the report is in a library that uses table GLT1.

This graphic is explained in the accompanying text.

To improve system performance, you should use a set as a selection condition so that no selection statement is needed.

For more information about using statements in the Report Writer, see Defining Selection Criteria .

Boolean Statements in Rollups

In rollups, you can use Boolean statements entered in rules to transfer substituted data to receiver fields during the rollup process and to define which data should be rolled up in a rollup ledger.

This graphic is explained in the accompanying text.

If an account is greater than or equal to 200000 and less than 250000, the account should be substituted with the account 300000.

You enter Boolean Logic rules to:

Select data to be rolled up, in the Rule field on the Create Rollup <Name>: Rollup Sequence screen

Substitute data, in the Rule field on the Change View “Rollup Substitution”: Overview screen

This graphic is explained in the accompanying text.

You create a substitution rule called AR-ROLLUP. This substitution rule contains the following statement:

GLU1-RACCT >= '200000' AND GLU1-RACCT < '250000'

In the Rule field on the Change View “Rollup Substitution”: Overview screen, you enter the substitution ruleAR-ROLLUP. You also enter the value with which transaction data is substituted (for example account 300000). When the transaction account is greater than or equal to 200000 and less than 250000, then the account is substituted with account 300000.

For more information about using statements in rollups, see Creating a Rollup Sequence .

Boolean Statements in Validations

In validations, you use Boolean statements to validate incoming data. The process for validating data is a two-step process, much like an IF/THEN condition (<->):

The system first checks if the validation prerequisite is TRUE for a transaction. If the transaction is TRUE, the system checks the data against the check statement (validation rule).

The system then checks the transaction against the validation rule. If the transaction is TRUE, the data is posted.

This graphic is explained in the accompanying text.

When a transaction's plant is 10, transaction data is only valid for company 1000 when the cost center is between 110 and 180. If you try to enter transaction data when the plant is 10 and the cost center is not between 110 and 180, the system displays an appropriate system message.

Boolean Statements in Substitutions

In substitutions, you use Boolean statements to define the conditions under which a substitution is to be performed.

This graphic is explained in the accompanying text.

You create a dimension called Region in your coding block. You instruct the system to move the value 121223 to dimension Region in the FI-SL summary database when a transaction with cost center 300 enters FI-SL from another SAP application component.