Apply Pre-Validations

GLSU gives the user the ability to pre-validate many of the values being keyed as well as other key configuration components such as blocked indicators, posting rules, and many other conditions and constraints to ensure they are correct before they are posted to SAP.

If errors exist in data during posting, time is often wasted in trying to correct these errors.

GLSU lets the user choose the fields to validate against in SAP. The SAP components of GLSU then download these values to the PC, either in an off-line or real-time method depending upon configuration of GLSU. Pre-Validation of data and SAP configuration is a large part of GLSU functionality.

Note: As of GLSU 4.1, in addition to the validations seen from ZGLSU > Validation Options, pre- validations for GGB0 (Cost Accounting and Financial Account Line item validations ) with sister transactions OKC7 and OB28 respectively are now checked. In addition, all configured coding block checks as defined in table TRWPR usually include the following: PAI exit for customer fields in coding block, asset checks, SD order checks, funds management checks, CO relevant fields, FI- relevant fields, MM-relevant fields, and joint venture checks. These pre-validations in GLSU will drill- back to the error line or row in Excel. (Technical Configuration Note: OKC7 and OB28 checks will be performed when activation level is set to either a "1" or a "2").

The fields which are validated are chosen in the ABAP program. See the section in the next chapter to learn how to choose which fields to validate against. By default, in a new GLSU installation all pre- validations are performed (and performed "LIVE") unless otherwise configured.