Role content comparisons and values
Choose between stored-text comparisons and authorization coverage, including ranges, wildcards and organizational values.
Applies to userXpress 2.0.0.0
Download PDF
- This pageRole content comparisons and values
- This sectionGlobal Role Table
- Full manualuserXpress documentation
On this page
Choose the comparison according to the question you are asking. Equals finds a value maintained exactly as entered. Covers value finds maintained authorizations that cover the requested value, including a suitable wildcard or interval.
Equals or Covers value
For a query asking about activity 03:
| Maintained value | Equals 03 |
Covers value 03 |
|---|---|---|
03 |
Match | Match |
01 through 03 |
No match | Match |
* |
No match | Match |
02 |
No match | No match |
Use Equals when reviewing how an authorization was maintained. Use Covers value when locating roles that cover a particular code.
Text comparisons treat a maintained interval as LOW..HIGH, for example 01..03. They compare text, including leading zeros and letter case. Use the SAP internal value, such as 03, rather than its description.
Coverage requests
Enter one of these forms with Covers value:
| Request | Meaning |
|---|---|
03 |
Cover this one value. |
Z_FIN* |
Cover the complete prefix beginning with Z_FIN. |
01..03 |
Cover the full interval from 01 through 03. |
* |
Cover the unrestricted value range. |
The entire request must be covered. A maintained value of Z_FIN_REPORT covers that single code but does not cover every value under Z_FIN*.
Use an asterisk only at the end of a coverage prefix. For Covers value, the prefix before the first asterisk determines the wildcard range. Use name patterns when matching object or field names.
Text comparisons
Use these comparisons to inspect maintained text or literal menu transaction codes.
| Comparison | Meaning |
|---|---|
| Equals | At least one maintained value equals the text. |
| Does not equal | No maintained value equals the text. |
| Contains / Does not contain | A maintained value contains the text, or none contains it. |
| Begins with / Ends with | A maintained value starts or ends with the text. |
| Is like / Is not like | A maintained value matches the pattern, or none matches it. Use % for any number of characters and _ for one character. |
| Is any of / Is none of | A maintained value equals one entry in the list, or none equals any listed entry. |
| Is greater than / Is greater than or equal to | A maintained value sorts after the supplied text, with equality included only in the second choice. |
| Is less than / Is less than or equal to | A maintained value sorts before the supplied text, with equality included only in the second choice. |
| Is between / Is not between | A maintained value is inside the inclusive text interval, or none is inside it. Enter both bounds. |
For example, Menu transaction → Begins with → VA finds menu codes beginning with VA. Menu transaction → Is like → VA__ finds four-character codes beginning with VA.
If a field contains both 01 and 03, Does not equal → 03 is false: the field does contain 03. The presence of another value does not make that negative condition true.
Organizational values
Add an organizational restriction as a field of its authorization object. For example, use object F_BKPF_BUK and set BUKRS → Covers value → 1000 to search for company-code coverage.
userXpress resolves organizational references using the values maintained for that role in its SAP client. For derived roles, it uses the derived role’s own organizational values.
- A maintained company-code value
1000or unrestricted coverage matches the example. - A maintained company-code value
2000does not match. - If the organizational data cannot be read or resolved, the result remains unverified. The query status explains incomplete searches.
Object and field name patterns
Use a name pattern when the objects or fields share part of a technical name.
- Click the object name or field name in the content editor.
- Choose Matches pattern in its selector.
- Enter the pattern and choose Use.
For names, * matches any number of characters and an underscore is literal. Object pattern S_USER_* searches matching object names. Field pattern ACT_* searches matching fields within that object. Choose Any field to consider any field in the object’s authorization.
The pattern remains part of the saved query. Later runs apply it to the role content available at that time.
Keep the different wildcard forms distinct:
- Object/field names use
*. - Is like value comparisons use
%and_. - Covers value uses a complete value, a trailing
*prefix or an interval.
Any maintained value, nonblank value or unrestricted coverage
These questions need different conditions:
| Question | Condition |
|---|---|
| Does the field have any maintained value, including a stored blank? | Is like → % |
| Does it have a maintained value containing at least one character? | Is like → _% |
| Does it provide unrestricted coverage? | Covers value * |
An unused empty field row in the editor is omitted from the query when applied. To ask one of the questions above, choose the explicit comparison and enter its value.
Values that remain unverified
Unsupported coverage values, malformed ranges and unavailable SAP data can prevent a definite answer. Such roles remain visible with an incomplete-results status. Open Details… for the affected clients and messages, then correct the reported cause and run the query again.