![\"SAP\"](\"http:\/\/oprsteny.cz\/wp-content\/uploads\/SAP.jpg\")
I believe you once had to solve a requirement (if not, you’ll definitely receive one in future) where you had to design a SELECTION-SCREEN parameters which value has to be dynamically updated according to results of the program – eg. last processed IDOC number, Purchase\/Sales Order number or just the last date when the report was executed. <\/p>\n
One solution is to create a Z-table which will contain just one entry with value you need.<\/p>\n
Another, more clean, clear and easy to maintain solution is to use dynamic variables in your variant SELECTION-SCREEN PARAMETERS or SELECT-OPTIONS.<\/p>\n
All existing program variants are all stored in table VARI.
\nVariant texts (descriptions) are stored in table VARIT.
\nVariant directory structure info is stored in table VARID.
\nAssignments of variants to selection screens are stored in table VARIS.<\/p>\n
The problem is that the select-options and parameters values are stored in a cluster thus they are not easilly accessible – you can’t write\/read them easily. It is of course possible using function modules starting on RS_VARIANT*, eg.<\/p>\n
But back to our problem. Let’s assume you would like to have a selection screen with three fields:<\/p>\n
You can achieve this using the RS_VARIANT* function modules: you read all variant parameters and select-options values, modify them in program and update the variant with new values back to cluster using another RS_VARIANT* function module.<\/p>\n
More elegant solution<\/strong> would be a variable stored in table TVARVC, which serves as a “repository” for all dynamic variables that you can use in your variants:<\/p>\n …with available values<\/p>\n …with available values<\/p>\n Now we have our program variant ready so let’s try to execute our report with our variant.<\/p>\n If we now modify the values either in program or manually via TCode SM30 in view TVARV and execute the report again with our variant ‘USE_VARS’, the parameters in selection screen will take the new\/updated values from TVARVC automatically.<\/p>\n I believe you once had to solve a requirement (if not, you’ll definitely receive one in future) where you had to design a SELECTION-SCREEN parameters which value has to be dynamically updated according to results of the program – eg. … Continue reading \n
\nCreation of an entry in TVARVC can also be done directly by the program, but note you can assign only the existing entries in TVARVC to program variants
\n![\"New](\"http:\/\/oprsteny.cz\/wp-content\/uploads\/PROGRAM_VARIABLES_05.png\")
<\/a><\/li>\nPARAMETERS:\r\n p_idoc type edidc-docnum OBLIGATORY,\r\n p_date type sy-datum OBLIGATORY,\r\n p_time type sy-uzeit OBLIGATORY.<\/pre>\n<\/li>\n
\n<\/a>
\n<\/a><\/li>\n\n
\n
\n
<\/a><\/li>\n\n
\n
<\/a><\/li>\n<\/ol>\n<\/a><\/p>\n<\/a><\/p>\nDATA:\r\n ls_tvarvc TYPE tvarvc.\r\n\r\nSELECT SINGLE *\r\n INTO ls_tvarvc\r\n FROM tvarvc\r\n WHERE name = 'Z_MY_PROGRAM_LAST_IDOC'.\r\n\r\nCHECK sy-subrc = 0.\r\n\r\nls_tvarvc-low = ls_tvarvc-low + 5.\r\nMODIFY tvarvc FROM ls_tvarvc.\r\n\r\nSELECT SINGLE *\r\n INTO ls_tvarvc\r\n FROM tvarvc\r\n WHERE name = 'Z_MY_PROGRAM_LAST_DATE'.\r\n\r\nCHECK sy-subrc = 0.\r\n\r\nls_tvarvc-low = sy-datum.\r\nMODIFY tvarvc FROM ls_tvarvc.\r\n\r\nSELECT SINGLE *\r\n INTO ls_tvarvc\r\n FROM tvarvc\r\n WHERE name = 'Z_MY_PROGRAM_LAST_TIME'.\r\n\r\nCHECK sy-subrc = 0.\r\n\r\nls_tvarvc-low = sy-uzeit.\r\nMODIFY tvarvc FROM ls_tvarvc.<\/pre>\n
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"