Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-RCM (Application Component) Records and Case Management⤷
RMPS_PRO_AUTH (Package) Authorization Checks - PRO
Basic Data
| Data Element | RMPS_AUTH_TYPE |
| Short Description | Type of Authorization Check |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RMPS_AUTH_TYPE | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Auth.Check |
| Medium | 15 | Type Auth Check |
| Long | 20 | Type of Auth. Check |
| Heading | 28 | Type of Authorization Check |
Documentation
Definition
The type of the authorization check defines which authorization objects are checked and which additional checks are run on objects such as folders and documents.
Use
The authorization objects RMPS: Access Record, Case, Document Org. Assignment of User and RMPS: Access Record, Case Document Special Org. Units are always checked.
For "TNA#" type authorization checks, RMPS TNA: Status-Dependent Attribute Check is also checked.
The access lists are also checked. The access lists are defined as a list of users in the field Access: Users and as a list of groups in the field "Access: Group". The user must be entered in one of the access lists (if the access lists are defined for the object). The setting "#Assignment to All Access Lists" requires that the user is assigned to all groups specified in the field Access: Group and not just to one (AND across the groups, not OR). This setting is only used rarely.
In the "TNA: ..." scenarios, documents assigned a status profile (using a connection parameter) are subject to an authorization check that hides the private objects of other users. The setting "...with Access to Private Objects" displays the private objects.
The access lists provide an enhancement to the authorization objects for organizational assignments, since an entry in an access list has the same affect as the assignment to the organizational unit of the document.
In the standard scenario (non-TNA), you can use the setting "Standard (No Access to Private Documents)" to activate an appropriate check, and private documents are hidden if assigned an appropriate status profile.
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 640 |
