EBSbeginner

System Administrator Responsibility and Setup Hierarchy

Understand the standard setup sequence a System Administrator follows when configuring a new EBS instance

The System Administrator responsibility is the master control panel for configuring EBS: creating users, responsibilities, menus, profile options, printers, and concurrent program definitions. Nearly every functional implementation begins with a system administrator establishing the technical foundation before functional consultants configure module-specific setups.

Setting up System Administrator hierarchy is like designing an org chart with keycards: you first design which doors exist (menus/functions), then create keycard profiles bundling specific doors (responsibilities), and finally issue keycards to individual employees (users) matching their job needs.

Key Concepts

1
A typical setup sequence starts with defining the Application and Data Group, then building Menus that expose specific functions, followed by creating Responsibilities that tie menus to request groups and data groups. Only after this foundation exists can Users be created and assigned responsibilities appropriate to their job role.
ApplicationData GroupMenusResponsibilitiesUsers
2
System Administrators are also responsible for maintaining Concurrent Program definitions, Request Sets (grouping multiple concurrent programs to run together in sequence or parallel), Printers, and Value Sets used across flexfields. They also manage Alerts — periodic or event-driven notifications configured through Oracle Alert.
Concurrent Program definitionsRequest SetsPrintersValue SetsAlerts
3
A well-organized responsibility and menu hierarchy is critical for security segregation of duties (SoD); interviewers often probe whether a candidate understands how improper menu/function exclusion rules can create SoD violations, such as a single responsibility allowing both PO creation and PO approval.