| Table Data Authorizations (ttams3145m000) |  |
| use.session.to maintain table data authorizations. This means that you can specify restrictions for normal users that are linked to the role to do database actions on records of a table for a given condition. Table data authorizations are specified for a range of data in a table by defining a condition. The authorization that is defined in this session can be an exception or addition to the authorizations that are defined in: The Table Authorizations by Company (ttams3144m000) session The Table Authorizations by Package (ttams3140m000) session The Table Authorizations by Module (ttams3141m000) session The Table Authorizations by Table (ttams3142m000) session You can use table data authorizations to block specific data in the database for normal users that are linked to the role. You can define authorizations depending on the data of a table. For example, a user can only be allowed to insert sales orders with the order number is between 100.000 and 200.000. You can specify an authorization level, for each condition, for example, the data authorization. This can be another authorization level as the table authorization level, which is defined in the database table authorization sessions. If you have not specified table authorizations, the table authorization status is delete, insert, modify, or read. An overlap can occur between two conditions for the same table with different authorization levels. The most restrictive authorization level is taken in this case. For the meaning of the condition within the expression, see the list of expressions below:
Cond. | Seq. | Field | Operator | Value 1 | And/Or/End
--- | --- | --- | --- | --- | ---
1 | 1 | X | equal | 1 | And
1 | 2 | Y | equal | 3 | Or
2 | 1 | Z | equal | 4 | End
Cond. | Seq. | Field | Operator | Value 1 | And/Or/End
--- | --- | --- | --- | --- | ---
1 | 1 | X | equal | 1 | And
2 | 1 | Y | equal | 3 | Or
2 | 2 | Z | equal | 4 | End
When specifying the two expressions, they will turn out to be different. Expression 1: (X=1 and Y=3) or (Z=4) Expression 2: (X=1) and (Y=3 or Z=4) You can define the table data authorizations for all companies or for a specific company. The authorizations for the specific company have the highest authority in this case. The table data authorizations are an exception to the database table authorizations at company level, at package level, at module level, and at table level. You can use the specific menu to: Delete the table data authorizations for a range of tables. Convert the changes of the database table authorizations to the run-time data dictionary. The database authorization data of the role is stored in the $BSE/lib/db/<first character of role>/<role>. Copy the database table authorization to the related child fields when a field refers to the related table and the field is part of the primary key of the table for which the database table authorizations is defined. Related topics To use an overview session To maintain records in an overview session
Fields | Description
Role | Specifies the code of the role.
Role | The description of the role.
All Companies | If this check box is selected, the authorizations are defined for all companies. If authorizations are defined for a specific company as well as for all companies, they can overlap. The authorizations for a specific company have the highest priority.
Company | Specifies the code of the company for which the database table authorizations at table data-level are defined.
Company | The description of the company.
Table | Specifies the code of the table for which the database table authorizations at table-data level are defined.
Table | The description of the table.
Authorization | Specifies the database table authorizations type, which is defined for the tables. This information is used by the server to determine whether a user is authorized to carry out a database action on the tables in the package, depending on the specified expression.
Cond. | If the expression consists of multiple conditions, the condition sequence-number is specified. The use of a condition sequence number in relation to the serial number can be explained with the following examples:
Cond. | Sern | Field | Operand | Value 1 | And/Or/End
--- | --- | --- | --- | --- | ---
1 | 1 | X | equal | 1 | And
1 | 2 | Y | equal | 3 | Or
2 | 1 | Z | equal | 4 | End
Cond. | Sern | Field | Operand | Value 1 | And/Or/End
--- | --- | --- | --- | --- | ---
1 | 1 | X | equal | 1 | And
2 | 1 | Y | equal | 3 | Or
2 | 2 | Z | equal | 4 | End
Expression 1: (X=1 and Y=3) or (Z=4) Expression 2: (X=1) and (Y=3 or Z=4)
Sern | Specifies the number of the subexpression in the condition. An expression can contain more than one subexpression.
Field | Specifies the code of the table field to which the condition applies.
Operator | Specifies the operator that you can use in the expression.
Value 1 | The value of the field in the condition.
Value 2 | Only if the operator is between or not between, the second value applicable.
And/Or/End | The operator who links two conditions, which can be and or which can be or. The expression is closed by using end of expression. If you have entered a condition that is closed by end of expression, all conditions after that will be ignored.