COLUMN SECURITY

Secures users from viewing a particular field or changing a value for a particular field in an
application or application version. This item can be a database or non-database field that is defined
in the data dictionary, such as the work/calculated fields.

For example, if you secure a user from viewing the Salary field on the Employee Master application,
the Salary field does not appear on the form when the user accesses that application.

7.7.1 Understanding Column Security

This section explains how to add and revise column security. You can secure users from viewing a particular
field or changing the value for a particular field. This item can be a database field, or a field that is defined in
the data dictionary but is not in the database.

Note:
You can find the tables, applications, forms, business views, and so on, that use a data item by
launching the Cross Reference application (P980011) after you build the cross-reference tables
(F980011and F980021).

You can set up column security on a table, an application, an application version, or a form. Even if an
application uses a business view that does not contain the data item that you want to secure, you can still
secure it, as long as the item appears on a form in the application.

7.7.1.1 Column Security Options

When you use Column Security you can set View, Add, and Change options to secure a field. For the field to
appear on a table, application, application version, or form, the View option must be set to Y. When the View
option is set to N for a field, that field does not appear on the object. Add and Change options depend on the
View option being set to Y for the field. The Add and Change options are independent of each other.

You can set the View and Add options to Y and the Change option to N. With security defined in this manner,
the field appears on the object and is enabled when the user enters the object in add mode. If the user enters the
object in update mode, the field appears but is disabled.

You can set the View and Change options to Y and the Add option to N. With security defined in this manner,
the field appears on the object and is enabled when the user enters the object in update mode. If the user enters
the object in add mode, the field appears but is disabled.

You can set all three options to Y. With security defined in this manner, the field appears on the object and is
enabled in both add and update mode.

7.7.1.2 Column Security on a Table

Before you set up column security on a table, do these:

 Verify that the object that you want to secure is in the table.
 Verify that the object that you want to secure is part of an application that uses a business view over a
table containing the object.
 COLUMN SECURITY

 Verify that the object that you want to secure uses a business view that includes the column containing
the object.

For example, if you want to apply column security to data item RLS (Release Number) in the F00941 table,
RLS must be an item in that table, and it must also be part of an application using a business view over that
table. Finally, the business view over the F00941 table must include a column containing the data item RLS.

If all of these conditions are met, you can successfully apply column security to the data item. Setting column
security on a table also means that you set security on the data item for any other applications that use the
F00941 table.

7.7.1.3 Column Security on an Application

Before you set up column security on an application, do these:

 Verify that the object that you want to secure is in the application.
 Verify that you are securing the correct data item in an application (data item descriptions can be
similar, if not identical).

For example, if you want to apply column security to data item UGRP (UserRole) in the Object Configuration
Manager application (P986110), you first verify that the item is in the application. Because it is in the
application, you can apply security to the data item. However, note that data items UGRP, MUSE, USER, and
USR0 all contain the identical data description of User ID. Verify the item by its alias, not by its data
description.

7.7.1.4 Column Security on an Application Version

You can secure users from using columns (or fields) in a version of an application. When you secure a column
in a version, the system secures the column in all forms associated with that application version.

Before you set up column security on an application version, do these:

 Verify that the object that you want to secure is in the version of the application.
 Verify that you secure the correct data item in an application (data item descriptions can be very
similar, if not identical). Verify the item by its alias, not by its data description.

7.7.1.5 Column Security on a Form

Security Workbench enables you to secure the column in one particular form, either in an application or in a
version of an application.

Before you set up column security on a form, do these:

 Verify that the object that you want to secure is in the form.
 Verify that you secure the correct data item in the form (data item descriptions can be very similar for
different data items).

7.7.2 Adding Column Security

 COLUMN SECURITY

Enter P00950 in Fast Path.

1. On the Work With User/Role Security form, select the Form menu, Set Up Security, Column.
2. On the Column Security form, complete the User / Role field, and then click Find to display current
column security for the user or role.
3. To add new security, go to the last row of the detail area and enter information into any of these fields:
 Table
 Application
 Version

If you want to add column security to a particular version, enter a version of the application that you
entered in the Application field.

 Form Name

You can enter *ALL in any of these fields; however, after *ALL is entered for a table, application,
or form for a specific data item, you cannot enter *ALL again for that data item.

4. Complete these fields:

 Data Item
 View

If the value for View is N, the data item will not appear on any of the objects identified in Step 3,
making Add and Change functions obsolete.

 Add
 Change
5. To change security, change the row values in the detail area.
6. Click OK to save the security information.

7.7.3 Removing Column Security

Enter P00950 in the Fast Path.

1. On the Work With User/Role Security form, select the Form menu, Set Up Security, Column.
2. On the Column Security form, complete the User / Role field, and then click Find.

Note:
If you accessed the Column Security form from the Work With User/Role Security for a specific
record, the user or role associated with the security record appears in the User/Role field by default.

3. Highlight the security record or records in the detail area and click Delete,and then click OK on
Confirm Delete.
4. Click OK when you finish deleting column security.

If you do not click OK after you delete the security records, the system does not save the deletion.