This report is typically used for auditing purposes. It lets you print a list (by program) of the operators, groups or roles that have access to that program.
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Role conflicts | Choose the level of conflict detail to display on the
report.
|
| Field | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Program | Select the programs against which you want to view
operator access.
|
||||||||||
These options enable you to apply a theme to the report and to define multiple output destinations for the report once it has been compiled (SRS Output Options).
A role conflict file must exist before you can report on role conflicts. To create this file you need to select the Create Conflict.txt option from the Options menu of the Operator Audit program (->->->).
You can tailor this file to your specific requirements. The file contains a list of program pairs that, in your opinion, constitute a conflict in your organization.
For example: If you don't consider it appropriate for an operator to have access to processing manual checks as well as voiding checks in the Accounts Payable module, then you would list the programs: APSP82APSP93 in the conflict.txt file.
The conflict.txt file must have the following properties:
-
The file must be a text file that can be created using an editor such as Notepad.
-
The file name must be conflict.txt. The file name is not case-sensitive unless you are using a Unix based operating system, in which case the file name must be in capital letters.
-
The file must reside in your \Work folder and, in a client/server environment, on the server.
Each line of the text file comprises two six-character SYSPRO program names or e.net business objects, which result in a role conflict. The program name pairs are separated by a single space.
Comments can be included in the text file. They can be included at the beginning of the line (i.e. with a semi-colon in column 1) or they can be added from column 25 onwards in a line, providing a semi-colon is placed in column 25.
![[Note]](images/note.png)
|
|
|
Role conflicts are applied both in the order in which the programs appear in the conflict.txt file and in reverse. For example: If the operator is allowed access to both IMPMOG and APSP82 then the role conflict is listed against IMPMOG and against APSP82 in the report. |
|
The following is an example of a conflict.txt file with comments:
;Role conflicts for IMPMOG - Admin operator groups
IMPMOG APSP82
;AP Manual Check Payment
IMPMOG APSP93
;AP Void payment entry
;Role conflicts for IMPPMP - Admin Operators
IMPPMP APSP82
IMPPMP APSP93
The following is an example of a conflict.txt file without comments:
IMPMOG APSP82
IMPMOG APSP93
IMPPMP APSP82
IMPPMP APSP93