SAP Function Modules
G_VALIDATE_RECORD SAP Function module - Check the Code Combinations in Summary, Line Item, or Plan LI Records
G_VALIDATE_RECORD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name G_VALIDATE_RECORD into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
GLIO
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM G_VALIDATE_RECORD - G VALIDATE RECORD
CALL FUNCTION 'G_VALIDATE_RECORD' "Check the Code Combinations in Summary, Line Item, or Plan LI Records
EXPORTING
tabname = " t800a-tab Name of table to be transferred
* popup_unvalid_rec = 'X' " flag Output invalid records on dialog box ('X': Yes)
* write_unvalid_rec = ' ' " flag Output invalid records on list ('X': Yes)
* record = ' ' " any Record of table TABNAME
TABLES
* table = " Summary, LI or Plan LI table with Object
perioden = " periods Table of dates that may need to be checked
* indextab = " index_tab Table of invalid indices from table
EXCEPTIONS
NO_PERIOD = 1 " no period tables transferred
NO_VALID_TABNAME = 2 " no object-containing SL tables transferred
NO_VALID_RECORDS = 3 " There is an invalid record
NO_REC_AND_NO_TABLE = 4 " Neither record nor table from records were transferred
. " G_VALIDATE_RECORD
ABAP code example for Function Module G_VALIDATE_RECORD
The ABAP code below is a full code listing to execute function module G_VALIDATE_RECORD including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).
| it_table | TYPE STANDARD TABLE OF STRING,"TABLES PARAM |
| wa_table | LIKE LINE OF it_table , |
| it_perioden | TYPE STANDARD TABLE OF PERIODS,"TABLES PARAM |
| wa_perioden | LIKE LINE OF it_perioden , |
| it_indextab | TYPE STANDARD TABLE OF INDEX_TAB,"TABLES PARAM |
| wa_indextab | LIKE LINE OF it_indextab . |
SELECT single TAB
FROM T800A
INTO @DATA(ld_tabname).
DATA(ld_popup_unvalid_rec) = 'Check type of data required'.
DATA(ld_write_unvalid_rec) = 'Check type of data required'.
DATA(ld_record) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_table to it_table.
"populate fields of struture and append to itab
append wa_perioden to it_perioden.
"populate fields of struture and append to itab
append wa_indextab to it_indextab. . CALL FUNCTION 'G_VALIDATE_RECORD' EXPORTING tabname = ld_tabname * popup_unvalid_rec = ld_popup_unvalid_rec * write_unvalid_rec = ld_write_unvalid_rec * record = ld_record TABLES * table = it_table perioden = it_perioden * indextab = it_indextab EXCEPTIONS NO_PERIOD = 1 NO_VALID_TABNAME = 2 NO_VALID_RECORDS = 3 NO_REC_AND_NO_TABLE = 4 . " G_VALIDATE_RECORD
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_tabname | TYPE T800A-TAB , |
| it_table | TYPE STANDARD TABLE OF STRING , |
| wa_table | LIKE LINE OF it_table, |
| ld_popup_unvalid_rec | TYPE FLAG , |
| it_perioden | TYPE STANDARD TABLE OF PERIODS , |
| wa_perioden | LIKE LINE OF it_perioden, |
| ld_write_unvalid_rec | TYPE FLAG , |
| it_indextab | TYPE STANDARD TABLE OF INDEX_TAB , |
| wa_indextab | LIKE LINE OF it_indextab, |
| ld_record | TYPE ANY . |
SELECT single TAB
FROM T800A
INTO ld_tabname.
"populate fields of struture and append to itab
append wa_table to it_table.
ld_popup_unvalid_rec = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_perioden to it_perioden.
ld_write_unvalid_rec = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_indextab to it_indextab.
ld_record = 'Check type of data required'.
SAP Documentation for FM G_VALIDATE_RECORD
The table name of an FI-SL table (object-containing), a record or a
table of records from this table as well as a table of 'Dates' must be
...See here for full SAP fm documentation
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name G_VALIDATE_RECORD or its description.