Personalizing pages in the OA framework enables you to cater for site-wide and user-specific needs at several levels.

Benefits of page personalizations in the OA framework are that they survive upgrades and patches

*…Administrators can apply personalizations on any component 
*…Users can apply personalizations on queries 
*…Administrators can easily disable personalizations for debugging 
*…Personalizations can be implemented on a test system, for testing prior to deployment 
*…Personalizations can be translated

You save OA framework-based pages as page definitions, for which the database stores metadata. At runtime, a page definition is layered over the base page it personalizes, leaving the original page unchanged.

Personalization levels

Personalizations may occur at the administrator or user level, or be seeded by Oracle application developers.

Administrator-level personalizations

At the administrator level, all OA framework-based pages can be personalized by default. However, administrators can't personalize programmatically created pages or regions, or pages or regions for which the application developer has explicitly disabled administrator personalization.

Administrators may personalize pages, for example, by

*…Changing text for labels, prompts, and tip messages 
*…Hiding or showing components 
*…Reordering components 
*…Restricting query results 
*…Adding items, such as fields, buttons, links, pick lists, or images 
*…Structuring graphs and charts 
*…Seeding end-user views 
*…Specifying whether fields are required 
*…Changing the destination of hyperlinks

The extent to which an administrator can personalize page flow is limited, and depends on how the flow was implemented. In some cases, you can modify function URLs and personalize the destination URLs that display as navigational elements. Page flow changes are generally beyond the scope of systems administrators, however, because such changes may affect transaction flows, and need thorough testing.

Administrators can personalize OA framework pages at the following levels:

*…Function 
*…Location 
*…Site 
*…Organization 
*…Responsibility

As an administrator, you can define personalizations at the function level to determine which users can access specific functions, and when. For example, you can hide the salary field from a user updating an employee record, but display it when the user creates a new employee.

At the location level, you can use locales as the context for personalization – for example, to show different address field labels based on users' country settings.

Site-level – or global – personalizations apply to all users with access to a given application component, such as "setting the number of rows shown in a table."

Organization-level personalizations apply only to users in a specified organization or business unit. You can use organization-level personalizations, for example, to stipulate that notifications be sorted by age for one organization and by urgency for another.

Personalizations at the responsibility level display only to users under a specific responsibility. You may, for example, configure a trend graph to display only to users under the sales manager responsibility.

The level at which an administrator configures personalization settings determines their precedence over other settings. For example, a responsibility-level personalization takes precedence over site-level personalizations for users with the specified responsibility. Users at the site who are not using the relevant responsibility would see only the site-level changes.

User-level personalizations

Default user personalizations, or user views, can exist at three levels. They can be seeded by Oracle developers, created by a system administrator, or created by the end user.

End users can access the personalization user interface by clicking the Save View or Personalize button. They can then personalize inquiry pages using query regions to create specific data views. For example, they can

*…Create and save searches 
*…Configure table column titles 
*…Hide or show columns 
*…Reorder columns 
*…Add data filters 
*…Change sort orders

Oracle-seeded levels

Oracle 11i E-Business Suite developers can seed personalizations – or build them into – Oracle applications. Seeded function and user-level personalizations, which are like the function and user levels available to administrators and users, respectively, can only be changed or deleted by Oracle customer administrators. However, system administrators or users may duplicate functions and then alter them using personalization settings.

*…Seeded function personalizations may, for example, provide applications with customized 
*…Menus and responsibilities 
*…Cascading style sheets (CSS) 
*…FND messages and lookups 
*…Icons and images 
*…Other required business or user personalizations

OA developers can create and ship seeded personalizations at any administrator personalization level, but system administrators at the customer site can change or delete these settings.

Translating and Deploying Personalizations

You should create personalizations in a test environment before deploying them to one or more production environments, and you should always create initial personalizations in the base language of the application instance.

To export a small number of personalization translations, you use the Export or Upload Translations buttons on the Manage Personalization Levels page. To import or export personalizations in bulk, you use the Export tool to obtain XML files. Because XLIFF (.xlf) files support translations, you then use the XLIFF Extractor to extract translation information from the page XML files.

Finally, you use the XLIFF Importer to load translations into the database repository. Personalizations are stored as documents in the MDS Repository.

Summary

Administrators and end users can personalize pages in the Oracle Application (OA) framework to meet their needs and preferences. Administrators can create, translate, and deploy page personalizations at the function, location, site, organization, and responsibility levels. End users can personalize inquiry pages. Personalized page definitions are stored in the Oracle database, and don't alter the base pages to which they apply.

One of the most common business scenarios in Oracle Apps is Purchase to Pay.

That is when companies purchase goods and receive them in their inventory and raise an invoice for it and later pay the supplier. This purchase to pay cycle has many intermediate accounting steps, specially from localisation perspective.

However I am going to demonstrate here the accounting entries carried out in Base Apps when for the Purchase to pay cycle when you track goods from receipt stage to pay stage.

The transactions carried out in the system for this cycle are:

1. Receive Goods

2. Deliver Goods to inventory

3. Raise an Invoice for the supplier against the purchase order

4. Make payment to supplier

The accounting entries are:

TRANSACTION	ACCOUNT	DR	CR
RECEIVE	Accrual Liability		1
RECEIVE	In-Transit	1
DELIVERY	In-Transit		1
DELIVERY	Inventory	1
INVOICE	Accrual Liability	1
INVOICE	Voucher's Payable		1
PAYMENT	Voucher's Payable	1
PAYMENT	BANK		1

You might have different names for your accounts but these are the Debit-Credit transactions. Notice how In-Transit gets knocked off between Receive and Deliver. Next Accrual Liability get's knocked off between Receive-Deliver and Invoice. The point to note here is that to find your outstanding liability, that is, goods received but not invoiced you would want to find the total credit balance in Accrual Liability account.

Next again note that Voucher's payable is the account that get's hit when you create an invoice with payables. This again get's knocked off when you make the payment. Please remember that I am only talking about standard invoices here. Again, if you want to find total goods invoiced but not yet paid you would query the total credit balance in Voucher's payable account. (you may have a different name in your system).

So in essence the final entry is just simply, Bank Credit to Inventory Debit! Simple and sweet!