Functional Area Substitution – GGB1

In order to populate your postings with functional areas, you must setup a substitution. Substitutions are similar to validations. Unlike validations that create on-screen messages to the user, substitutions actually replace and fill in field values behind the scenes without the user’s knowledge. Similar to validations, substitutions can be setup for a number of different application areas and callup points. Substitutions are activated on the company code level, so it is important to ensure that you have followed all steps for each company code.

Financial Accounting >> Special Purpose Ledger >> Tools >> Maintain Validation/Substitution/Rules >> Maintain Substitution

Transaction code: GGB1

The fields in Create Substitution screen are:

Application Area: Enter the appropriate area is the module or submodule that you wish to create the substitution for. The available options are:

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

Callup Point: Callup points determine when the substitution is run. For FI application area, the following callup points are available

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

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

0003 Complete Document: This callup point substitutes settings for the document as a whole. This activity is also known as matrix substitution.

0005 Cost of Sales Accounting: This callup point is used for functional area substitutions

On the next screen add a description. To add a step to substitution, click on insert entry button. Specify of you are using a user-exit or select the field you wish to substitute. For field substitution, you need enter the following

Perquisite: The perquisite uses Boolean logic to determine if a condition is true. If the condition is true, the substitution is carried out. If the condition is not true, no further processing occurs. 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. 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: This is the section 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.

Validations and substitutions are case sensitive – make sure you type in all your logic in CAPS – Check syntax does not find errors in small case.

Run the check syntax function to see if the Boolean logic has errors. Saving creates the ABAP code run your substitution.

One thought on “Functional Area Substitution – GGB1

Leave a Reply

Your email address will not be published.