Beruflich Dokumente
Kultur Dokumente
Overview
Distribution
Oracle Assets
Job Title*
Ownership
The Job Title [list@YourCompany.com?Subject=EDUxxxxx] is responsible for ensuring that
this document is necessary and that it reflects actual practice.
Calendar Region
Implementation considerations for the Calendar Region:
Allow Purge
• You must check the Allow Purge checkbox in order to purge information from this asset
book. It is recommended that you leave the checkbox unchecked until you are ready to
purge data from the book. You can then enable the Allow Purge option, purge your data,
then again disable the checkbox. This helps to ensure against unwanted purges of data
from this book.
GL Ledger
• Enter the ledger for which you want to create journal entries.
Allow GL Posting
• Enable if you want to create journal entries for this book. You cannot allow general
ledger posting for your budget books.
Prorate Calendar
• Use the prorate calendar with the smallest period size or resolution you need for
determining your depreciation rate. For example, you may want to use a monthly prorate
Energy Assets
Oracle Energy Assets addresses the financial and reporting requirements of the oil and gas
industry. The oil and gas industry accounts and reports asset information based on a two-level
parent (field) and child (wells) structure.
Asset information is:
• Captured at the lower level.
• Summarized to a higher level at which operations, queries and reporting are done.
Operations include:
• Depreciation calculation
• Overriding Oracle Assets-calculated depreciation
• Calculating gain and loss on retirement
• Transfer of costs and reserve
• Impairment
Depreciation Methods
Oil and gas companies use unit-of-production and life-based methods based on a depreciation
basis defined as Net Book Value (NBV) over the net remaining reserves for the Energy Units
Copyright © Oracle, 2007. All rights reserved.
Security by Book
Prior to Security by Book, unless your Oracle Assets installation was Multi-Org enabled, there
was no way to restrict user access to query and update information pertaining only to those
users' asset books. Users could access any asset book on the system. Thus, the power and
flexibility of having each department in a large organization have its own asset books was
mitigated because each departments' staff could still query and update possibly sensitive data
in other departments.
Oracle Assets's Security by Book feature makes use of a Security Profile that is attached to a
responsibility to determine which records are available to holders of that responsibility. The
Security Profile acts as the 'glue' between an organization and a responsibility. To set up a
security profile that permits access to asset books of certain organizations only, you make use
of organizational hierarchies.