Duty segregation scenarios were developed to help campuses assign users to responsibilities within the Oracle application. The scenarios were categorized into the following three tracks:
Click on the category to view the guidelines that campus and central office management should use.
The guidelines are based on ideal segregation of duty capabilities. Realistically, some campus locations may not be able to follow them because of size and processing requirements. Please review the guidelines and adhere to them where possible.
Note: Segregation of duty controls should be adhered to cross-track and cross-module, where not specified. For example, a single user should not be granted high level access to Accounts Payable (AP) and Grants Management.
Was this document clear and easy to follow? Please send your feedback to firstname.lastname@example.org.
Copyright © 2011 The Research Foundation of State University of New York