Scribd Logo
Upload

Welcome to Scribd!

  • 175 views

    Validation Rules in FI

    Uploaded by

    saeed.ca6924
    Validation rules in SAP R/3 ensure that only valid data is entered into the system. These rules are stored in the Rule Manager and check values as they are entered. If data does not pass the validation checks, only valid information will be posted to FI modules. Custom validations can be created using the validations program to define Boolean statements to check entries beyond standard validations. A validation can contain up to 999 steps to validate data against multiple criteria before posting.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    Validation Rules in FI

    Uploaded by

    saeed.ca6924
    175 views6 pages
    Validation rules in SAP R/3 ensure that only valid data is entered into the system. These rules are stored in the Rule Manager and check values as they are entered. If data does not pass the validation checks, only valid information will be posted to FI modules. Custom validations can be created using the validations program to define Boolean statements to check entries beyond standard validations. A validation can contain up to 999 steps to validate data against multiple criteria before posting.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Validation rules in SAP R/3 ensure that only valid data is entered into the system. These rules are stored in the Rule Manager and check values as they are entered. If data does not pass the validation checks, only valid information will be posted to FI modules. Custom validations can be created using the validations program to define Boolean statements to check entries beyond standard validations. A validation can contain up to 999 steps to validate data against multiple criteria before posting.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    175 views6 pages

    Validation Rules in FI

    Uploaded by

    saeed.ca6924
    Validation rules in SAP R/3 ensure that only valid data is entered into the system. These rules are stored in the Rule Manager and check values as they are entered. If data does not pass the validation checks, only valid information will be posted to FI modules. Custom validations can be created using the validations program to define Boolean statements to check entries beyond standard validations. A validation can contain up to 999 steps to validate data against multiple criteria before posting.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 6

    Validation rules in FI

    By Shiva Kumar Tirumalasetty, Deloitte Consulting India Pvt Ltd

    In the SAP R/3 System, nearly all input values are validated by a program or against tables or master
    files. Since some types of validations cannot be standardized, you can use the validations program to
    create validations for your specific requirements.

    The validation function enables you to check values and ranges of values as they are being entered in the
    SAP R/3 System. Validation rules are stored in the Rule Manager. As data is entered into the system, the
    Integration Manager validates the data against the validation rules. Because data is validated before it is
    actually posted, only valid information is posted to the FI-SL application component.

    The system validates account numbers against a master file or checks that a ledger is assigned to
    a local company code.

    You use validations when you want to create a user-defined Boolean statement to validate an
    entry in a way that is not defined for the standard system.

    A validation can consist of up to 999 steps. You can therefore validate data against any number of
    Boolean statements before the data is posted.

    Creating a Validation:

    1.       Go to transaction GGB0 and select the application area-Financial accounting from the tree menu.
    Select the node: Line item.

    Click on the “Validation” button available on the application toolbar to create the validation and enter
    the following details:

    Validation name: VB15_V2

    Description: Validation for the tax code

    Message ID: ZFGL

    Call up Point: 2

    Application area: FI

    Click on ‘Save’.
    Note: Validations can be created for all the application areas of FI available on the screen of GGB0 as
    shown above.
    2.       Now click on “Step” button on the application toolbar to create the validation step with the below
    details:

    In the “prerequisites” sub node enter the below condition: (This validation rule should trigger only
    for transaction FB01,FB60,FB65,FB02,MIRO,FV60,FV65,FVB0,FBM2,FBV0,FBV2,F-01,F-44,and
    only for vendor line items(KOART= ‘K’)

    (BKPF-TCODE = 'FB01' OR BKPF-TCODE = 'FB60' OR

    BKPF-TCODE = 'FB65' OR BKPF-TCODE = ‘MIRO’ OR

    BKPF-TCODE = 'FB02' OR BKPF-TCODE = 'FBM2' OR

    BKPF-TCODE = 'FBV0' OR BKPF-TCODE = 'FBV2' OR

    BKPF-TCODE = 'FV60' OR BKPF-TCODE = 'FV65' OR

    BKPF-TCODE = 'F-01' OR BKPF-TCODE = 'F-44’) AND

    (BSEG-KOART = ‘K’)
    n the “message” sub node, enter the details of the error message that needs to be displayed.

    4.       Go to transaction OB28 to activate the Validation, Click on new entries and enter the following
    details and save:

    CoCd (Company code) = VB15.


    CallPnt = 0002 (Line Item).

    Validation = VB15_V2

    Activtn level = 1(Active).

    Now Test if the validation created will trigger. Go to Transaction FB01 and try to create a vendor
    credit memo(With One vendor Line item: Posting Key : 21)

    5.                   Since we have created a validation rule to trigger for company code: VB15 and only for
    the vendor Line item (KOART = K), the error message is displayed as below.

    You might also like