Application Object Library: A Complete Guide to Oracle E-Business Suite AOL

Application Object Library, commonly known as AOL, is an important part of Oracle E-Business Suite. It provides a collection of shared application components, tools, libraries, programs, and services that help Oracle E-Business Suite applications work together in a consistent and organized way.

For beginners, the term Application Object Library may sound complicated. In simple words, AOL provides common building blocks that Oracle applications can use for tasks such as user management, security, menus, forms, reports, concurrent processing, profiles, flexfields, and application customization.

Instead of every Oracle application creating its own version of these features, Application Object Library provides a common framework. This makes Oracle E-Business Suite easier to administer, customize, maintain, and use.

This guide explains Application Object Library in simple language. It covers its meaning, major components, security model, concurrent processing, Oracle Forms, customization, development, administration, common problems, and frequently asked questions.

What Is Application Object Library?

Application Object Library is a shared technology layer within Oracle E-Business Suite.

It provides common functionality that can be used by different Oracle applications. These applications may include financial, supply chain, procurement, human resources, manufacturing, and other enterprise applications.

For example, many Oracle E-Business Suite applications need to perform the same basic tasks:

Authenticate users
Control access
Display menus
Open forms
Run reports
Process background jobs
Validate information
Store configuration settings
Support flexfields
Display standard messages
Manage application profiles
Register custom application objects

Application Object Library provides many of these shared capabilities.

A useful way to think about AOL is as the common foundation underneath Oracle E-Business Suite applications.

Application Object Library Meaning in Simple Words

The easiest way to understand Application Object Library is to imagine a large company with many departments.

The finance department may use one set of business applications. The purchasing department may use another. The inventory department may use another.

Although their business activities are different, they still need common services such as:

Employee access
Security
Navigation
Reports
Background processing
Configuration
Data validation

Application Object Library provides many of these common services.

Therefore, AOL does not represent one individual business module. Instead, it supports multiple Oracle E-Business Suite applications.

Why Is Application Object Library Important?

Application Object Library is important because Oracle E-Business Suite is a large and interconnected enterprise platform.

Different applications need to follow common technical and administrative rules.

Without a shared framework, every Oracle application would potentially need its own system for:

User access
Security
Menus
Functions
Reports
Background processing
Configuration
Data validation
Application registration

AOL helps standardize these areas.

This creates several benefits.

Consistent Administration

Administrators can use common Oracle E-Business Suite concepts across multiple applications.

Centralized Security

User access can be organized through users, responsibilities, menus, functions, and other security structures.

Reusable Development Components

Developers can use existing Oracle libraries and services rather than building every feature from scratch.

Standardized Background Processing

Concurrent processing provides a common way to run lengthy programs and reports.

Easier Customization

Companies can create custom forms, reports, programs, menus, and other components that fit into the Oracle E-Business Suite framework.

Main Components of Application Object Library

Application Object Library includes many different components.

Also Read: RLP Letter: What It Means, Why You Received One, and What to Do Next

Some of the most important ones are:

Users
Responsibilities
Menus
Functions
Concurrent programs
Concurrent requests
Concurrent managers
Request groups
Profile options
Flexfields
Value sets
Messages
Application libraries
Application registration
Application directory structures
Security and auditing features

Each component performs a different job, but they work together.

Application Users in AOL

An application user is an account that allows someone to access Oracle E-Business Suite.

A user normally signs in with a username and authentication credentials.

However, creating a user does not automatically provide unlimited access.

The user’s assigned responsibilities determine what areas of Oracle E-Business Suite the person can access.

For example, an employee working in purchasing may receive a purchasing-related responsibility, while an accounting employee may receive a financial responsibility.

This separation is important for both security and organization.

What Is an Oracle Responsibility?

A responsibility is one of the most important concepts in Application Object Library.

In simple terms, a responsibility defines the environment and access available to a user.

A responsibility can control access to:

Menus
Functions
Concurrent programs
Reports
Request groups
Profile settings
Application data contexts

A single user can have multiple responsibilities.

For example, an employee might have access to:

Accounts Payable
General Ledger
Purchasing
Reporting

Each responsibility can provide a different working environment.

Why Are Responsibilities Important?

Responsibilities help organizations apply the principle of least privilege.

A user should generally receive the access needed to perform their job rather than unrestricted access to every feature.

This can help reduce:

Unauthorized activity
Accidental changes
Security risks
Operational errors
Unnecessary access

Responsibilities are therefore an important part of Oracle E-Business Suite administration.

Application Object Library Menus

Menus determine which functions users can access within a responsibility.

A menu can contain:

Functions
Submenus
Forms
Navigation options

Menus are usually organized hierarchically.

For example, a responsibility might display a main menu containing several submenus. Each submenu may contain additional functions.

A simplified relationship is:

User → Responsibility → Menu → Function

Understanding this relationship is useful when troubleshooting Oracle E-Business Suite access problems.

If a user cannot see a particular form or function, the problem may involve the responsibility or its assigned menu.

What Is an AOL Function?

A function represents a piece of functionality within Oracle E-Business Suite.

It can provide access to a form or another application feature.

Function security allows administrators to control which functions can be accessed through particular responsibilities.

For example, a company might want employees to view customer information but prevent them from performing certain administrative actions.

Functions and menus can be configured to create the appropriate access structure.

Application Object Library and Security

Security is one of the most important areas supported by Application Object Library.

A typical security structure may involve:

User
Responsibility
Menu
Function
Request group
Profile option
Data access

These components work together to establish what users can see and do.

A simplified example is:

A user signs in.

The user selects a responsibility.

The responsibility provides a menu.

The menu contains approved functions.

The user accesses the functions permitted by that responsibility.

This layered approach makes Oracle E-Business Suite security more manageable.

What Is Concurrent Processing?

Concurrent Processing is another major Application Object Library concept.

It allows Oracle E-Business Suite to run long or resource-intensive tasks in the background.

For example, a user may need to run a report containing a large amount of information.

Instead of keeping the user’s session busy until the report finishes, the report can be submitted as a concurrent request.

The system can process it in the background.

This allows the user to continue working.

Concurrent processing can be used for:

Reports
Data imports
Batch processing
Financial programs
Data updates
Scheduled jobs
Background calculations
Other long-running programs

How Concurrent Processing Works

The basic process is straightforward.

First, a user submits a concurrent request.

The request enters the processing queue.

A suitable concurrent manager identifies the request.

The concurrent manager starts the program.

The program performs its task.

The request eventually reaches a completion status.

The user can then review the result, log, or output.

This approach is particularly useful in large enterprise environments where many users may be running programs simultaneously.

What Is a Concurrent Request?

A concurrent request is an individual request to run a registered concurrent program.

For example, suppose a company has a program called “Monthly Sales Report.”

When a user submits that program for August, the resulting execution is a concurrent request.

The request may move through statuses such as:

Pending
Running
Completed
Inactive
Error
Warning

The exact status depends on the program and its execution result.

System administrators often monitor concurrent requests when troubleshooting Oracle E-Business Suite.

What Is a Concurrent Manager?

A concurrent manager is a background processing component that runs concurrent requests.

Think of it as a worker that receives eligible jobs and executes them.

An Oracle E-Business Suite environment may have different concurrent managers configured for different processing requirements.

Administrators can use configuration rules to control which requests particular managers process.

This can become important in environments with high workloads.

What Is FNDLIBR?

FNDLIBR is a specific program library associated with Oracle Application Object Library.

It is commonly associated with immediate concurrent programs and the standard concurrent processing environment.

FNDLIBR should not be confused with Application Object Library as a whole.

The distinction is simple:

FNDLIBR is a specific AOL program library.

AOL is the broader collection of shared Oracle E-Business Suite functionality.

Technical professionals may encounter FNDLIBR when examining concurrent manager configuration, executable definitions, or troubleshooting background processing.

Application Object Library and Concurrent Programs

A concurrent program is a registered program that can be executed through Oracle E-Business Suite’s concurrent processing framework.

Depending on the environment, concurrent programs may use technologies such as:

PL/SQL
SQL*Plus
Oracle Reports
SQL*Loader
C
Pro*C
Shell or host scripts

A concurrent program generally has an executable definition and registration information.

It can also have parameters that allow users to provide information when submitting the program.

For example, a report might ask the user to select:

Start date
End date
Organization
Business unit
Customer
Account
Product

Value sets can be used to validate many types of parameter input.

Standard Request Submission

Standard Request Submission, often called SRS, provides a common interface for submitting Oracle E-Business Suite concurrent programs.

Instead of every report requiring a completely different submission screen, Oracle E-Business Suite can provide a standard request submission process.

Users can:

Select a program.
Enter parameters.
Submit the request.
Monitor its status.
Review the output.

This provides a consistent experience across many Oracle applications.

Application Object Library and Profile Options

Profile options allow administrators to configure application behavior.

They can control settings used at different levels.

Common levels can include:

Site
Application
Responsibility
User

This allows administrators to apply different configurations depending on the organization’s requirements.

For example, a setting could apply to the entire system, while another could apply only to a particular responsibility.

Profile options are therefore useful for controlling application behavior without necessarily changing application source code.

What Are Flexfields?

Flexfields are one of the best-known Oracle E-Business Suite concepts.

They provide a flexible way to capture business information.

Organizations often have business requirements that do not fit perfectly into a standard application structure.

Flexfields provide additional configuration options.

Two major types are:

Key flexfields
Descriptive flexfields

Key flexfields are commonly used for structured business identifiers.

Descriptive flexfields can provide additional descriptive information associated with application records.

Flexfields are powerful because organizations can configure them according to their specific business requirements.

What Are Value Sets?

A value set defines rules for validating values entered into Oracle E-Business Suite.

For example, an organization may want a field to accept only:

Numbers
Specific text
Values from a list
Values from a database query
Certain formats

Value sets can help prevent invalid information from being entered.

They are also frequently used with concurrent program parameters.

For example, instead of allowing a user to type any organization name, a value set can provide an approved list.

This improves consistency and data quality.

Application Object Library and Oracle Forms

Oracle Forms has historically played an important role in Oracle E-Business Suite.

Application Object Library provides shared libraries and standards that can be used by Oracle Forms applications.

These libraries contain reusable functionality.

Using shared libraries can help applications maintain consistent behavior.

They can support areas such as:

Navigation
Validation
Messages
Application standards
Flexfields
Profiles
Common user interface behavior

Important Oracle E-Business Suite libraries can include components such as APPCORE and FNDSQF.

Developers who work with Oracle Forms and E-Business Suite customization often need to understand these libraries.

What Is the CUSTOM Library?

The CUSTOM library is associated with Oracle E-Business Suite customization.

It provides a place where organizations can implement certain custom logic without unnecessarily changing Oracle’s standard application code.

This distinction is important.

Directly modifying standard Oracle application files can make maintenance and future upgrades more difficult.

A better approach is generally to use supported extension and customization mechanisms whenever possible.

Application Object Library and Custom Applications

Organizations can create custom applications that integrate with Oracle E-Business Suite.

A custom application can contain components such as:

Forms
Reports
Concurrent programs
Menus
Functions
Libraries
Database objects
Responsibilities

For example, a company might have a specialized internal process that is not included in the standard Oracle E-Business Suite functionality.

The organization could develop a custom application to support that process.

Also Read: Keibann: Meaning, Uses, Workflow, Online Presence, and What You Need to Know

Application Object Library provides important infrastructure for registering and integrating these custom components.

What Is Application Registration?

Application registration identifies an application to Oracle E-Business Suite.

Registration allows Oracle E-Business Suite to associate different application objects with the appropriate application.

This can include:

Forms
Responsibilities
Menus
Programs
Reports
Libraries

Application registration becomes particularly important when organizations create custom applications.

Proper registration helps maintain an organized application environment.

What Is an Application Short Name?

An application short name is a shortened identifier used to identify an Oracle E-Business Suite application.

Technical teams may see application short names in:

Directory structures
File names
Configuration
Scripts
Application code
Database objects

For developers and administrators, understanding application short names can make technical troubleshooting easier.

APPL_TOP and Application Object Library

APPL_TOP is another important term in Oracle E-Business Suite.

It represents an application-level directory structure.

It contains application files and directories associated with Oracle E-Business Suite.

Technical administrators and developers commonly work with APPL_TOP when managing:

Forms
Reports
Concurrent programs
Application files
Custom files
Configuration

In Oracle E-Business Suite environments, understanding the file system is important for technical maintenance.

Application Object Library Architecture

Application Object Library works as part of the larger Oracle E-Business Suite architecture.

A simplified model looks like this:

User interface

↓

Oracle E-Business Suite application

↓

Application Object Library services

↓

Database and processing infrastructure

This is only a conceptual model, but it makes the relationship easier to understand.

Business applications handle specific business processes.

AOL provides shared application functionality.

The database stores application data.

Concurrent processing handles background programs.

Together, these components form an integrated enterprise environment.

Application Object Library for Oracle Developers

Oracle developers who work with E-Business Suite benefit greatly from understanding AOL.

A developer may need to work with:

Oracle Forms
PL/SQL
Concurrent programs
Menus
Functions
Responsibilities
Value sets
Flexfields
Application registration
AOL libraries
APIs

Suppose a company asks a developer to create a new custom report.

The developer may need to:

Create the report logic.
Create an executable.
Register the executable.
Define a concurrent program.
Add parameters.
Create or select appropriate value sets.
Add the program to a request group.
Give an appropriate responsibility access.
Test the report.
Deploy it according to the organization’s change-management process.

This is a good example of how several AOL components work together.

Application Object Library for System Administrators

System administrators interact with AOL differently from developers.

Their daily work may include:

Creating users
Assigning responsibilities
Managing menus
Reviewing functions
Managing request groups
Configuring profiles
Monitoring concurrent requests
Managing concurrent managers
Troubleshooting access problems
Reviewing security settings

For administrators, AOL knowledge is essential because many user-access problems are actually configuration problems involving responsibilities, menus, functions, or request groups.

Application Object Library for Technical Consultants

Technical consultants often work between business users, developers, and administrators.

For example, a business user may say:

“We need a new report available to the purchasing team.”

The consultant needs to translate that business request into technical requirements.

The process may involve:

Identifying the report requirements
Determining the required data
Creating the program
Registering the program
Defining parameters
Creating value sets
Configuring request groups
Assigning responsibilities
Testing access
Confirming security

Understanding AOL makes this process easier.

Application Object Library and Database Objects

AOL works closely with the Oracle Database.

Many Oracle E-Business Suite configuration elements are stored in database objects and tables.

However, technical professionals should distinguish between reading information and directly changing Oracle application data.

A developer may be able to query a table to investigate a configuration issue.

That does not automatically mean the table should be directly updated.

Supported APIs, forms, application interfaces, and documented configuration methods should generally be preferred when making changes.

Direct modifications can create data integrity, support, and upgrade problems.

Application Object Library and Customization

Customization is common in enterprise Oracle environments.

Companies often need Oracle E-Business Suite to support business processes that are different from standard functionality.

Possible customizations include:

Custom reports
Custom forms
Custom menus
Custom responsibilities
Custom concurrent programs
Additional fields
Custom validation
Custom interfaces
Custom applications

The key is to customize carefully.

A well-designed customization should integrate with the Oracle framework while minimizing unnecessary changes to standard Oracle objects.

Application Object Library and Oracle E-Business Suite 12.2

Oracle E-Business Suite Release 12.2 introduced important architectural changes.

One major concept is online patching.

Release 12.2 environments also use a dual file system structure associated with online patching.

Because of these architectural differences, organizations should not automatically apply procedures designed for older Oracle E-Business Suite releases to a 12.2 environment.

Release-specific procedures matter.

This is especially important for:

Patching
Customization
File management
Application registration
Development
Deployment
System administration

Oracle E-Business Suite professionals should always identify the exact release before following technical instructions.

Common Application Object Library Problems

AOL-related problems can occur during administration, development, customization, or daily use.

User Cannot See a Function

Possible reasons include:

Incorrect responsibility
Incorrect menu
Function not included
Function security restriction
Configuration issue

The first step is usually to determine which responsibility the user is using.

User Cannot Run a Concurrent Program

Possible reasons include:

Program not assigned to the appropriate request group
Incorrect responsibility
Program registration problem
Inactive executable
Concurrent manager problem

Checking the user’s responsibility and request group is often a useful starting point.

Concurrent Request Remains Pending

A pending request may be caused by:

No available manager
Manager specialization
Incompatibility rules
Processing workload
Configuration problems

Administrators should review the request status and concurrent manager activity.

Form Does Not Open

Potential causes include:

Incorrect registration
Missing files
Library problems
Compilation issues
Environment configuration
Customization errors

Troubleshooting should identify whether the problem exists in the application setup, file system, database, or custom code.

Application Object Library Best Practices

Organizations can improve their Oracle E-Business Suite environments by following good AOL practices.

Follow Least-Privilege Access

Users should generally receive only the access necessary for their jobs.

Avoid giving administrative responsibilities to users who do not require them.

Document Customizations

Maintain records of:

Custom applications
Custom forms
Custom reports
Concurrent programs
Menus
Responsibilities
Profile settings
Value sets
Flexfields

Good documentation makes future maintenance easier.

Avoid Unnecessary Standard Code Changes

Changing standard Oracle code can make upgrades and troubleshooting more difficult.

Use supported customization mechanisms whenever possible.

Test Before Production

Every important AOL configuration or customization should be tested in an appropriate non-production environment.

Testing can identify:

Security problems
Missing dependencies
Incorrect menus
Incorrect responsibilities
Concurrent processing issues
Data problems

Review User Access Regularly

Organizations should periodically review user responsibilities.

Employees change jobs, leave organizations, or receive new duties.

Their Oracle access should change accordingly.

Monitor Concurrent Processing

Administrators should monitor:

Pending requests
Running requests
Failed requests
Request duration
Concurrent manager activity

Unexpected processing delays can affect business operations.

Application Object Library and Enterprise Security

Enterprise applications can contain valuable business information.

Depending on the Oracle E-Business Suite implementation, this can include:

Financial information
Customer information
Supplier information
Employee information
Inventory information
Business transactions
Operational data

Application Object Library’s security model helps organizations control access to application functionality.

However, security is not something that should be configured once and forgotten.

Organizations should regularly review:

User accounts
Responsibilities
Sensitive functions
Administrative access
Concurrent program access
Custom responsibilities
Data access

Regular reviews can help identify unnecessary permissions.

Application Object Library and Auditing

Auditing is another important consideration in enterprise applications.

Organizations may need to understand who accessed or changed certain information and when activity occurred.

The exact auditing requirements depend on the organization’s business, security policies, industry requirements, and Oracle configuration.

Organizations should define appropriate retention and monitoring policies rather than assuming that every activity is automatically audited.

Application Object Library Practical Example

Imagine a company wants its purchasing team to run a new supplier report.

The process could look like this:

A developer creates the report.

The report executable is registered.

A concurrent program is defined.

The report parameters are configured.

Value sets validate the parameters.

The concurrent program is added to a request group.

The request group is available to the purchasing responsibility.

The purchasing user receives that responsibility.

The user signs in.

The user submits the report.

A concurrent manager processes the request.

The completed output becomes available.

This example demonstrates how AOL components connect.

It also explains why learning only one AOL component is not enough.

Application Object Library vs Oracle Forms

Application Object Library and Oracle Forms are related but different.

Oracle Forms is a technology used to create forms-based user interfaces.

Application Object Library is a broader Oracle E-Business Suite framework that provides shared services, libraries, security structures, registration, concurrent processing, and other functionality.

A simple comparison is:

Oracle Forms = technology for building forms-based interfaces.

Application Object Library = shared Oracle E-Business Suite application infrastructure.

Oracle Forms applications can use AOL libraries and functionality.

Also Read: Messagenal: Everything You Need to Know

Application Object Library vs Oracle Database

AOL and the Oracle Database also have different roles.

The Oracle Database stores and processes data.

Application Object Library provides application-level functionality and infrastructure used by Oracle E-Business Suite.

They work closely together, but they are not the same thing.

An easy way to remember the difference is:

Database = stores and processes information.

AOL = provides shared application functionality.

Oracle E-Business Suite = combines applications, technology, database infrastructure, and supporting components into an enterprise platform.

How to Learn Application Object Library

Learning AOL can seem difficult at first because there are many related concepts.

A structured learning path can make it easier.

Step 1: Learn Oracle E-Business Suite Basics

Start with:

Oracle E-Business Suite architecture
Applications
Users
Responsibilities
Forms
Reports

Step 2: Learn AOL Security

Study:

Users
Responsibilities
Menus
Functions
Request groups
Security concepts

Step 3: Learn Concurrent Processing

Understand:

Concurrent programs
Executables
Requests
Concurrent managers
Logs
Output
Request statuses

Step 4: Learn Profiles

Understand how profile options can change application behavior.

Step 5: Learn Value Sets and Flexfields

These are important for configuration and data validation.

Step 6: Learn Oracle Forms and AOL Libraries

Developers should learn how Forms interacts with common AOL libraries.

Step 7: Learn Customization

Study custom applications, forms, reports, menus, responsibilities, and supported extension methods.

Step 8: Learn Release-Specific Architecture

If you work with Oracle E-Business Suite 12.2, learn the architecture and maintenance processes specific to that release.

Career Opportunities Related to Application Object Library

AOL knowledge can be useful for several Oracle-related career paths.

These may include:

Oracle E-Business Suite Administrator
Oracle Technical Consultant
Oracle Applications Developer
Oracle Forms Developer
Oracle PL/SQL Developer
Oracle ERP Consultant
Oracle EBS Support Analyst
Oracle Database Administrator
Oracle EBS Technical Architect

The required skills vary by role.

For example, a developer may need strong PL/SQL and Forms skills, while an administrator may focus more heavily on security, concurrent processing, configuration, and system management.

Important Application Object Library Terms to Remember

If you are preparing for an Oracle E-Business Suite interview or learning AOL, remember these core terms:

AOL

Application Object Library.

FND

A group of objects and functionality strongly associated with Application Object Library.

Responsibility

Defines a user’s application access and working context.

Function

Represents application functionality that can be controlled through security.

Concurrent Program

A registered program that can run through concurrent processing.

Concurrent Request

An individual submitted execution of a concurrent program.

Concurrent Manager

Background processing component that runs concurrent requests.

Request Group

Controls which concurrent programs can be accessed through a responsibility.

Profile Option

Controls configurable application behavior.

Value Set

Provides validation rules for values.

Flexfield

Provides configurable data structures for business requirements.

FNDLIBR

An AOL program library associated with concurrent processing.

APPL_TOP

An application-level Oracle E-Business Suite directory structure.

Frequently Asked Questions About Application Object Library

1. Is Application Object Library a programming language?

No. Application Object Library is not a programming language.

It is a collection of shared application functionality, tools, libraries, programs, and infrastructure used within Oracle E-Business Suite.

Developers may use programming languages and technologies such as PL/SQL, Oracle Forms, SQL, and other supported technologies while working with AOL.

2. Is AOL used only by Oracle developers?

No.

Oracle developers, system administrators, technical consultants, support teams, and experienced functional professionals may all interact with AOL-related functionality.

Developers may use AOL for application extensions, while administrators may use it for users, responsibilities, menus, profiles, and concurrent processing.

3. Can AOL be customized for a company?

Yes, Oracle E-Business Suite supports many forms of configuration and customization.

Organizations can create custom applications, reports, forms, menus, functions, concurrent programs, and other extensions.

However, customization should be planned carefully to reduce maintenance and upgrade risks.

4. Is knowledge of SQL necessary to understand Application Object Library?

Basic SQL knowledge is very useful, especially for technical Oracle E-Business Suite professionals.

Administrators may not need advanced SQL for every task, but developers and technical consultants often use SQL to investigate configuration, understand data relationships, troubleshoot problems, and develop applications.

PL/SQL is also particularly useful for Oracle E-Business Suite development.

5. What is the difference between AOL and Oracle E-Business Suite?

Oracle E-Business Suite is the larger enterprise application platform containing multiple business applications.

Application Object Library is a shared technology layer that provides common functionality used by those applications.

In simple terms:

Oracle E-Business Suite = the larger enterprise application environment.

Application Object Library = shared infrastructure supporting that environment.

Conclusion

Application Object Library is a fundamental part of Oracle E-Business Suite. It provides shared components and services that allow different Oracle applications to operate within a common framework.

Its major areas include users, responsibilities, menus, functions, concurrent programs, concurrent managers, request groups, profile options, flexfields, value sets, Oracle Forms libraries, application registration, security, and customization.

For beginners, the most important concept is that AOL is not simply one Oracle program. It is a collection of common application services and technology that supports many parts of Oracle E-Business Suite.

Once you understand the relationship between users, responsibilities, menus, functions, concurrent programs, and concurrent managers, many Oracle E-Business Suite concepts become much easier to understand.

For developers, AOL provides important tools and standards for creating and integrating custom functionality. For administrators, it provides essential mechanisms for managing users, security, configuration, and background processing. For technical consultants, it provides the bridge between business requirements and Oracle E-Business Suite technology.

The best way to learn Application Object Library is to study its components one at a time and then understand how they work together. Start with users and responsibilities, move to menus and functions, then learn concurrent processing, profiles, flexfields, value sets, and customization.

With that foundation, Application Object Library becomes much less intimidating and much more practical to understand.