All topics
8 / 60
EBSintermediate

Application Object Library (AOL) and FND Tables

Understand the foundational metadata layer (AOL/FND) that powers menus, responsibilities, and security in EBS

The Application Object Library (AOL), often referred to by its schema prefix FND, is the technology foundation underlying every EBS module. It manages users, responsibilities, menus, functions, concurrent programs, flexfields, profile options, and messages — essentially all the metadata that defines how the application behaves and who can access what.

AOL/FND is like the building management system of an office tower — it defines who has a badge (FND_USER), which floors and rooms that badge opens (responsibilities/menus), and keeps a common directory and notice board (message dictionary) that every tenant company (module) in the building uses.

Key Concepts

1
Key FND tables every technical consultant should know include FND_USER (application users), FND_RESPONSIBILITY (responsibilities), FND_MENU_ENTRIES (menu structure), FND_FORM_FUNCTIONS (registered functions/forms), and FND_CONCURRENT_PROGRAMS (batch program definitions). A responsibility ties together a menu, a request group (which concurrent programs are runnable), and a data group (which schema instance to use), forming the access control boundary for a user.
responsibility
2
AOL also provides common technical services: the Message Dictionary (FND_NEW_MESSAGES) for translatable error messages, Value Sets for flexfield/parameter validation, and the AOL API framework for standard utilities like FND_GLOBAL (session context) and FND_FILE (logging to concurrent request logs).
Message DictionaryValue SetsAOL API framework
3
Interview questions in this space often test whether a candidate can trace 'why can't this user see this menu item' by walking through Responsibility to Menu to Function, or explain how FND_GLOBAL.USER_ID / RESP_ID are used pervasively across custom code for auditing and security context.
Use cases:aolfndsecurityresponsibilitiesfoundation