![\"SAP\"](\"http:\/\/oprsteny.cz\/wp-content\/uploads\/SAP.jpg\")
I needed to create a database table\u00a0where there will be no key fields (all fields to be editable during table maintenance) but at the same time I needed some easy way how to identify each table row with unique key. And I found a solution using automatically generated GUID during row addition handled by maintenance view events.<\/p>\n
We will start from scratch so we’ll design and create our database table called in our case ZCA_MNTEVT.<\/p>\n
We will disallow it’s display and maintenance because these actions will be performed by it’s maintenance view only.<\/p>\n Now we add the necessary fields<\/p>\n … set technical settings<\/p>\n … and set enhancement category (in top menu – Extras<\/em> – Enhancement category<\/em>)<\/p>\n We will name the view similarly to the database table, ie ZCA_VMNTEVT.<\/p>\n … and create it as maintenance view<\/p>\n In tab Table\/Join<\/em> conditions we enter the name of our database table.<\/p>\n Now click on the View Flds<\/em> tab, click on Table fields<\/em> button and select the necessary fields (fileds you want to have in the maintenance view available to be edited) The final look of available fields will be as on the following picture<\/p>\n Now switch to tab Maint.Status\u00a0<\/em>where we’ll set the required access level.<\/p>\n At this moment we’re done with the view and we can save&activate it.<\/p>\n Stay in the maintenance view screen and go to top menu – Utilities<\/em> – Table Maintenance Generator<\/em> where we will create One step<\/em>\u00a0maintenance type in new function group named with the same as the view: ZCA_VMNTEVT.<\/em><\/p>\n Press F6 (create) to generate code of function group ZCA_VMNTEVT<\/em> for the maintenance view.<\/p>\n When the generation is completed go to top menu –\u00a0Environment<\/em>\u00a0–\u00a0Modification<\/em>\u00a0–\u00a0Events,\u00a0<\/em>create new entry for event of row creation\/addition (event #05) and assign a form name where our code will be placed. Click on the SAVE button and then on the button in the\u00a0Editor<\/em>\u00a0column.<\/p>\n You will be asked for a new include name where the code will be placed. Enter your desired name or just confirm the suggested one.<\/p>\n When the code editor is displayed enter the following piece of code.<\/p>\n Save and activate all your changes<\/p>\n Now if you run transaction SM30 and maintain ZCA_VMNTEVT you will see the GUID column is visible and editable. This is not what we’ve originally wanted. So we have to edit the maintenance view accordingly:<\/p>\n Run transaction SE80 and open function group ZCA_VMNTEVT, expand the Screens <\/em>folder, open screen 0100 <\/em>and add the highlighted line into the code<\/p>\n Double click on the module and you’ll be prompted for another include name. Enter desired name or just confirm.<\/p>\n When code editor is displayed enter the following piece of code.<\/p>\n Now save and activate all the changes, go to transaction SM30<\/em> and maintain ZCA_VMNTEVT. The above (hiding a column) was just to show you how you can manipulate data and look&feel of the screen programatically. The same (hiding a column of a view) can be achieved much simpler way – setting it’s visibility directly in the Maintenance view:<\/p>\n If you now regenerate the view using Maintenance view generator, you’ll achieve the same result as previously with typing the code manually.<\/p>\n In this specific case the second approach (setting the field attribute in the view directly) is definitely better because all manual code you put in the auto-genereated code will be removed when maintenance generator is executed again.<\/p>\n Now try to enter some values and save the changes.<\/p>\n Go to transaction SE16, open table ZCA_MNTEVT and verify the GUID has been generated for all new rows.<\/p>\n I needed to create a database table\u00a0where there will be no key fields (all fields to be editable during table maintenance) but at the same time I needed some easy way how to identify each table row with unique key. … Continue reading ![\"Table](\"http:\/\/oprsteny.cz\/wp-content\/uploads\/ZCA_MNTEVT01.png\")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nCreate table view on top of our table<\/h1>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nNote: We don’t want the MANDT and GUID to be displayed because they will be automatically assigned\/generated but we need to have them in the view so we can manipulate with data in the fields in the code.<\/em><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nCreate maintenance view for table view<\/h1>\n
<\/a><\/p>\nAdd events<\/h1>\n
\nNote:\u00a0On\u00a0this picture<\/a>\u00a0you can see all available events you can use in case you need them.<\/em><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nModify the maintenance view<\/h1>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\n<\/em>Now you can see the GUID column is not visible.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"