Granting Permissions to Lawson System Foundation Tables in Landmark

The buildschemaviewperms utility generates a SQL script granting permissions to another user or role for all tables in a database space marked IsView=Yes in the data area deployment file. After generating the script, you run the script using a SQL utility to grant the desired permissions.

Run this script any time a structural change resulting from a blddbdict or database reorganization occurs to Infor Lawson System Foundation tables that are marked as IsView in the Infor Landmark Technology data area deployment file.

Before running this utility, all Infor Lawson System Foundation tables used by Infor Landmark Technology must be set to IsView=Yes in the appropriate section of the database deployment file (%LACFGDIR%\dict\dataarea.xml). This deployment file is modified using the changeda utility. Changing Database Space Attributes Using changeda

Note: Before the April 2021 Landmark update, the dataarea.xml file was located in %LASRCDIR%\dict. The April 2021 update and later updates will attempt to move the dataarea.xml file to %LACFGDIR%\dict. If the file cannot be moved, the system will continue to use the dataarea.xml file in %LASRCDIR%\dict.

To Grant Permissions to Infor Lawson System Foundation Tables in Landmark

At a Landmark command prompt, type

buildschemaviewperms -u application_user|role [-s] productline|dataarea [file|module] > permsscriptname.sql

where


Parameter	Description
`application_user`	The user specified for the Infor Lawson System Foundation tables in the `%LARUNDIR%\dataarea\db.cfg` file.
`role`	A security role defined for your application.
`productline\|dataarea`	The product line or data area that contains the application.
`file\|module`	The name of a file or module that you want to build permissions for.
`permsscriptname.sql`	The name of the script that will grant permissions to the Infor Lawson System Foundation tables.

Login to the Oracle database as the user specified for the Infor Lawson System Foundation tables in the %LARUNDIR%\dataarea\db.cfg file.
Manually edit the permsscriptname.sql script to adjust permissions as needed for your site.
Because the buildschemaviewperms utility converts schema names (the table name prefix) to uppercase (which is incorrect for Oracle), you must change all schema names (table prefixes) in the file to the same case as that entered in the dataarea.xml file.
Run the generated permsscriptname.sql script from a SQL prompt, using the application_user and password for the user specified for the Infor Lawson System Foundation tables in the %LARUNDIR%\dataarea\db.cfg file.