SLA Integration

Asset accounting is tightly integrated with SLA, users can use the seeded accounting definitions or can define custom definitions leveraging the flexibility of SLA.

Mass Additions Enhancements

New columns provided to Mass Additions interface tables to import certain values like asset life, depreciation method etc from legacy systems without deriving from asset category setups

New extensible pubic APIs provided to automatically prepare mass additions without user interface for all required attributes such as expense account, asset category, location etc.

XML Reports

XML publisher support major asset transaction reports in variable formats by creating your own templates using familiar tools such as Acrobat, Word and Excel.

Automatic Depreciation Rollback

Function to Roll Back Depreciation is removed as it is handled by the Assets automatically.

If users need to make adjustments to one or few assets after running depreciation without closing period, they can proceed to do so, oracle assets rollback depreciation for the assets adjusted automatically

Assets for which depreciation was rolled back is automatically picked up during the next depreciation run or at the time that the depreciation period is finally closed.

Other Enhancements

Enhanced logging for Asset Transactions and Programs

Enhanced functionality for Energy industries a) Asset Impairment b) Energy units of Production Method (UOP) c) Energy straight line method.
 

Use the API FND_GLOBAL.APPS_INITIALIZE to set the applications context in standalone sessions that were not initialized through normal means. Typically, you would use this API in external custom programs that are establishing their own connections.

procedure APPS_INITIALIZE(user_id IN number,resp_id IN number,resp_appl_id IN number security_group_id IN number);
USER_ID           - The User ID number.
RESP_ID           - The ID number of the responsibility.
RESP_APPL_ID  - The ID number of the application TO which the responsibility belongs.
SECURITY_GROUP_ID - The ID number of the security GROUP. This argument IS automatically defaulted BY the API. The caller should NOT pass a value FOR it.

Usage: fnd_global.APPS_INITIALIZE (1010,20417,201)

This procedure sets up global variables and profile values in a database session. Call this procedure to initialize the global security context for a database session. You can use it for routines such as PL/SQL or other programs that are not integrated with either the Oracle Applications concurrent processing facility or Oracle Forms (both of which already do a similar initialization for a database session). The typical use for this routine would be as part of the logic for launching a separate non–Forms session from an established Oracle Applications form session. You can also use this procedure to set up a database session for manually testing application code using SQL*Plus. This routine should only be used when the session must be established outside of a normal form or concurrent program connection. You can obtain valid values to use with this procedure by using profile option routines to retrieve these values in an existing Oracle Applications form session.

begin
fnd_global.APPS_INITIALIZE(200131258,20004,51710);
end;

Using FNDLOAD can download data from an application entity into an editable text file, which can be uploaded to another database.The Conversion between database format and text file format is specified by a configuration file.

 

It can be done for the following list

 · Concurrent Programs, Executables
· Request Groups, Request Sets
· Profile Options
· Key and Descriptive Flexfields
· Menus and Responsibilities
· Forms and Form Functions
· Attachments
· Messages
· Value Sets and Values
· Lookup Types
· User Responsibilities
· Printer Definitions
· FND Dictionary
· Help Configuration
· Document Sequences
· Concurrent Manager Schedules

Advantages when using FNDLOAD 

 1. Because downloaded data is stored in a text file, version administration is possible
2. No learning curve. this is relief for developer/dbas
3. Fully supported and recommended by Oracle
4. Capture the migrations in a file and use it during installations(log file).
5. Pin-point when something happened and where (database) easily
6. AOL data migration process is now simplified!

Disadvantages 

1. Applications patching mechanisms use FNDLOAD heavily possibility of negative impact is not zero
2. No validation against migrating database/instance sensitive data