Standard service - a fixed amount of work that is performed at a fixed price.  Post Service

  

Monday, 25 February 2019 13:00

FI Accounting Validation using T-code GGB0

Written by 
Rate this item
(0 votes)

Requirement:

Restrict specific user and specific transaction codes to use particular GL Account with GL Account indicator “T”.

  1. Special GL account can be N number.
  2. T-Code can be N
  • number.
    1. We can find BADI or Exits for every t code and can put validation for each one of them but it would be a cumbersome process. And we might miss something or the other.
    2. Find a common BADI or Exit for validation on same but there might not be one common BADI or Exit to do so.
    3. Functional can do configuration (in SPRO) but it is also not possible because the requirement is to restrict user for specific T-Codes and not a generalized one.

    After some serious brain storming and long discussions with the functional and business teams, I found a way to accomplish this by using GGB0 (Validation Maintenance).

    What is GGB0?

    GGB0 is the transaction code to Create and Maintain Validations.

    Some other t-codes and components which helps and supports us in GGB0 Validations are:

    1. GS01: This t-code is to Create Set.
    2. SET: Set is like a Range. We can also use particular value.
    3. OB28: This t-code is for validation of Accounting Document to Activate and deactivate GGB0 Validations.

    Also Check – How to auto activate VOFM in non Development SAP Systems?

    Let’s start.

    1. Document Header is to Put Validation on Header Level.
    2. Line Item is to validate at line Item level.
    3. Complete Document is about the Rule and Help Document for validation.

    We have created YARD as our validation name and all other details related to it is in the below image.

    Validation – To create new validation.

    Step – Is used to provide the details of validations. N number of steps are possible for one Validation Name.

    Rule – To define theValidation Rules.

    Also Read : How to update custom field of PRPS table

    Prerequisite – Here we can program and write code (validation Conditions) using Table field and Status.

    Check – Condition checks.

    Message – Here we can write our custom Messages. Advisable best practice is to create message class.

    Also, define the prerequisited for ‘T’ Type indicator, like to Select BSEG-UMSKZ = ‘T’. UMSKZ field holds – Special G/L Indicator.

    Here USER ID is SET (Range) – User list

    SET is created using T-code GS01 (Explained in subsequent Steps)

    Here I am creating Company Code SET i.e. for these particular company code(s) our validation will work.


    Also Check – GPS like tool in SAP using Google Map API

    There are 3 options in Activation Level. 1 is for Active

    Let’s check if our validation works or not.

    We have maintained the necessary t-codes in SET (GS01) and the validation works only and only for the SET maintained.

    We tried to post a document using t-code FB01. Since FB01 is there in the SET, therefore the validation gets triggered.

    It’s giving the error message as expected. It’s successful.

    As a technical developer and support personnel, you need know how to debug the Validations?

    Then it will take you to the Source Code. Let’s say if you are using Step 001 then put Break Point at Step 001

    And execute your T-code and debug the issue.

    Free Video Training on SAP DebuggingSAP Debugging for Non-Technical Consultants

    Go to t-code GGB0. Select your validation (put a cursor on it).

    Then go to Menu -> Validation -> Transport.

    Some of the useful Transaction Codes for Validation:

    • GGB0 – Validation Maintenance
    • GGB1 – Substitution Maintenance
    • GCVZ – Rule Maintenance
    • GGB4 – Action selection for validation/substitution, for example, activation of application areas, use of all messages or substituted fields
    • GCX2 – Definition of the Includes for user exits
    • OB28 – Activation of FI validations
    • OBBH – Activation of FI substitutions
    • OBBZ – Activation of cost of sales accounting substitution (in the FI area)
    • OKC7 – Activation of CO validations
    • OKC9 – Activation of CO substitutions
    • GCT9 – Transport: Validations
    • GCT0 – Transport: Substitutions

    We have a very active Telegram (App) SAP Technical Group with more than 3900+ SAP Technical Practitioners from 6 Continents of the SAP World. Please join it using below link.
    Telegram SAP Technical Discuss Group. You need to install the Telegram App first on your mobile device. Once you have it on your mobile, you can join the group and also access it from the Web on your computer and laptop.

    Some Useful Enhancements in SAP

    Read 163 times

    Leave a comment

    Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.

    Support

    Follow us on