Skip to Content
author's profile photo Former Member
Former Member

OB28 Documentation

Hello,

Can anyone tell me were to find information to learn how to use OB28 transation ?

Reagards,

PA

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2007 at 04:41 PM

    Settting up the FI Validations

    You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.

    For e.g. to allow postings from company code 0001 to business area AA only.

    GGB0 - To maintain the validations

    Validation - Enter a validation name e.g. VBUS

    Applicaion Area - SAP module e.g. FI

    Calling Point - Dependent upon the application area that is selected.

    0001 - Document Header - validate enteries at document header, e.g BKPF table

    0002 - Line Items - check line item entris within a document, e.g. BSEG table

    0003 - Complete Document - check settings for the whole documents.

    e.g. Validation step 001

    Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.

    If checks failed, the error message number 14 is displayed to stop the transaction.

    Prerequisite

    <BSEG> $BUKRS = '0001' AND

    <BKPF> $GLVOR = 'FI00'

    Check

    <BSEG> $GSBER = 'AA'

    Message

    Type E No. 14 - Business Area not allowed for company 0001

    Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS

    3 - 4

    OB28 - Define Validations for Posting

    CC CallPnt Validation Description Activtn Level

    0001 2 VBUS Business Area Validation 1

    Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input

    GGB4 - Manage the activation of all validations in the SAP system.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Dear PA,

      You can try to create your own dictionary structure with one fields (SE11). Lets say ZSTR. And then add this structure and field to table GB01. Thanks to that it should be visible in GGB0 as avaiable field for message variables.

      After that you can declare structure ZSTR in TABLES in your exit program and fill structure field according to your needs.

      e.g. U100 in EXIT-Formpool:

      select * from zcost

      where kstar = bseg-hkont

      and kostl = bseg-kostl .

      if sy-subrc <> 0.

      B_RESULT = B_FALSE.

      endif.

      you can create sets (gs01) and include both your cost centre and gls in the two seperate sets and then use your sets in FI validation (ob28) to create validation and messages.

      Create your two sets (gl & costcentre) based on the table SKB1 and field SAKNR and table CSKS and field KOSTL respectively and input your valid gls and ccs in the sets. Then go to FI validation (ob28), your validation should be against your CoCode and then call point '2' for line item. If there is already a validation you just need to add a step to it if there is none you need to create one. I am assuming there is none then in validation assign CoCode and call point 2 and press enter (don't enter the name of your validation yet). Double click on the line and then press create valiation on the Line Item. Now create a step (step001) enter your pre-requisite from Structure BKPF this will check if the step need to be applied. I guess your prerequisite could be docType (ie 'SA' , 'KR', etc.) or if you want for all docTypes you should have only your company code as prerequiste. Then assign your 'Check' criteria, you should select from Structure BSEG and something like this (G/L IN "Name of the gl set that you created" AND Cost Centre IN "Name of cc set that you created"). Then go to message section and pick an appropiate message from message class or create a new message. Ah..don't forget to activate your validation if there was none active validation at the beginning. Let me know if this works out for u

      http://www.sap-basis-abap.com/sapfi004.htm

      You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.

      For e.g. to allow postings from company code 0001 to business area AA only.

      GGB0 - To maintain the validations

      Validation - Enter a validation name e.g. VBUS

      Applicaion Area - SAP module e.g. FI

      Calling Point - Dependent upon the application area that is selected.

      0001 - Document Header - validate enteries at document header, e.g BKPF table

      0002 - Line Items - check line item entris within a document, e.g. BSEG table

      0003 - Complete Document - check settings for the whole documents.

      e.g. Validation step 001

      Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.

      If checks failed, the error message number 14 is displayed to stop the transaction.

      Prerequisite

      <BSEG> $BUKRS = '0001' AND

      <BKPF> $GLVOR = 'FI00'

      Check

      <BSEG> $GSBER = 'AA'

      Message

      Type E No. 14 - Business Area not allowed for company 0001

      Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS

      3 - 4

      OB28 - Define Validations for Posting

      CC CallPnt Validation Description Activtn Level

      0001 2 VBUS Business Area Validation 1

      Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input

      GGB4 - Manage the activation of all validations in the SAP system.

      Regards,

      Naveen.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.