Oracle Assets Module
This section has all the changes in Oracle Assets Module in the 12 Release.
Overview
Subledger Accounting Architecture
Invoice Distributions from Oracle Payables
Global Descriptive Flexfield Migration for Greece
Tuesday, September 23, 2008
Global Descriptive Flexfield Migration for Greece
Oracle Assets : Global Descriptive Flexfield Migration for Greece :-
----------------------------------------------------------------------------
Commitment and Investment Law will be migrated from Global Descriptive Flexfields
specific to Greece localizations into named fields that will appear in the Asset
Workbench and be available to all users. The global_attribute1 and global_attribute2
columns in Assets will be copied into the Commitment and Investment Law fields,
respectively.
----------------------------------------------------------------------------
Commitment and Investment Law will be migrated from Global Descriptive Flexfields
specific to Greece localizations into named fields that will appear in the Asset
Workbench and be available to all users. The global_attribute1 and global_attribute2
columns in Assets will be copied into the Commitment and Investment Law fields,
respectively.
Invoice Distributions from Oracle Payables
Oracle Assets : Invoice Distributions from Oracle Payables:-
---------------------------------------------------------------------
Invoice distributions from Oracle Payables that have been interfaced to Assets will be
upgraded to display the Invoice Line Number. This new field will appear in the Asset
Workbench, Financial Inquiry, and Mass Additions Prepare forms.
---------------------------------------------------------------------
Invoice distributions from Oracle Payables that have been interfaced to Assets will be
upgraded to display the Invoice Line Number. This new field will appear in the Asset
Workbench, Financial Inquiry, and Mass Additions Prepare forms.
Subledger Accounting Architecture
Oracle Assets : Subledger Accounting Architecture:-
------------------------------------------------------------
In Release 12, Oracle Assets adds Subledger Accounting (SLA) functionality. By default,
transactions in the current fiscal year in Asset books will have their accounting lines
migrated to the Subledger Accounting model. Accounting for current period
depreciation will be upgraded only if depreciation has already run for the period, and
the period remains open. After the upgrade, customers can run the SLA postupgrade
process to update accounting for the past transaction data as needed.
The upgrade for Subledger Accounting performs a number of tasks:
• Transactions that have occurred in the current open period will be upgraded.
Previously, accounting records were not created until after depreciation had run.
The upgrade will create these lines immediately. For example, if a user added an
asset and went to the Transaction History form, he would not see any Addition
accounting lines if depreciation had not been run. Postupgrade, however, these
records would appear in the Transaction History form for the Addition event.
The following transactions are affected:
• Additions
• Backdated Additions
• Backdated Transfers
• Retirements
• Accounting lines for transaction, depreciation, and deferred depreciation events
will be copied from the core Assets data model into the Subledger Accounting data
model. These accounting lines that are upgraded would be viewable in the new
Subledger Accounting pages and reports. Accounting lines that were not upgraded
would only appear in the old historical forms and reports.
• For transaction events, only the data for the current fiscal year are upgraded by
default. When there are less than six periods in the current fiscal year, additional
data from the previous fiscal year are upgraded to ensure that there are at least six
periods worth of data. The customer, however, can change this default setting in the
preupgrade. For depreciation and deferred depreciation events, only the current
open period is upgraded, and this is not changeable during the preupgrade. The
customer can upgrade any of the transactions, depreciation, and deferred
depreciation events that are not upgraded during the down time with the SLA
postupgrade process.
The Subledger Accounting upgrade is generic, and there are very few assumptions that
have been made:
• All of the accounting lines data that are upgraded are copied as is, and no
calculations or functional checks are done. Therefore, the data after the upgrade will
be the same as it was before the upgrade.
• Transactions that have no accounting impact will not be upgraded. That is, if there
are no accounting lines corresponding to a transaction event, that record will not be
upgraded. Tax book events that have accounting lines that correspond to their
corporate book transaction event, but not a tax book one, however, will still be
upgraded.
• Books or reporting books that are disabled will not be upgraded.
After the Subledger Accounting upgrade, a number of changes have been made to the
business flows for the Journal Entry processing as the following:
• Profile option FA: Use Workflow Account Generation is set to Yes during the
upgrade. Customers should analyze current customizations in the workflow setup.
If the requirement is to use the rules in workflow for generating code combinations
for asset transactions, there are two options:
Re-implement the custom rules in Subledger Accounting. Use the workflow rules as they are, which is the default value upon upgrade.
• Journal Source and Journal Category setups have been removed from the Book
Controls setup form. This setup has moved to Subledger Accounting.
• Depreciation Expense Account and the Bonus Expense Account for all category and
book combinations in the Asset Category setup form have been upgraded from a
single segment account value to entire account combinations.
• The intercompany account setup in Book Controls form has been replaced by
Intercompany/Intracompany setup in Accounting Setups.
Note: In Release 12, the Intercompany setups will be maintained at
the ledger level. The upgrade will update the existing
Intercompany setup at book level to ledger level.
• Users will need to run Create Accounting instead of Create Journal Entries.
• Users will need to run Calculate Deferred Depreciation and then Create Accounting
instead of Create Deferred Depreciation Journal Entries.
The following lists those features that are obsolete in Release 12 or replaced by another
feature:
• The Create Journal Entries and Rollback Journal Entries programs are now obsolete.
Create Journal Entries has been replaced by Create Accounting.
• The Create Deferred Depreciation Journal Entries program is now obsolete. Users
now need to run Calculate Deferred Depreciation followed by Create Accounting.
• The Account Drill Down report has been replaced by a new Subledger Accounting
report called the Account Analysis report.
• Profile option "FA: Include Nonrecoverable Tax in Mass Addition" is obsolete. This
is replaced by Post Accounting Programs under SLA. The setup for all eligible lines
from Payables to Assets for Mass Additions Create program is done in Post
Accounting Programs.
------------------------------------------------------------
In Release 12, Oracle Assets adds Subledger Accounting (SLA) functionality. By default,
transactions in the current fiscal year in Asset books will have their accounting lines
migrated to the Subledger Accounting model. Accounting for current period
depreciation will be upgraded only if depreciation has already run for the period, and
the period remains open. After the upgrade, customers can run the SLA postupgrade
process to update accounting for the past transaction data as needed.
The upgrade for Subledger Accounting performs a number of tasks:
• Transactions that have occurred in the current open period will be upgraded.
Previously, accounting records were not created until after depreciation had run.
The upgrade will create these lines immediately. For example, if a user added an
asset and went to the Transaction History form, he would not see any Addition
accounting lines if depreciation had not been run. Postupgrade, however, these
records would appear in the Transaction History form for the Addition event.
The following transactions are affected:
• Additions
• Backdated Additions
• Backdated Transfers
• Retirements
• Accounting lines for transaction, depreciation, and deferred depreciation events
will be copied from the core Assets data model into the Subledger Accounting data
model. These accounting lines that are upgraded would be viewable in the new
Subledger Accounting pages and reports. Accounting lines that were not upgraded
would only appear in the old historical forms and reports.
• For transaction events, only the data for the current fiscal year are upgraded by
default. When there are less than six periods in the current fiscal year, additional
data from the previous fiscal year are upgraded to ensure that there are at least six
periods worth of data. The customer, however, can change this default setting in the
preupgrade. For depreciation and deferred depreciation events, only the current
open period is upgraded, and this is not changeable during the preupgrade. The
customer can upgrade any of the transactions, depreciation, and deferred
depreciation events that are not upgraded during the down time with the SLA
postupgrade process.
The Subledger Accounting upgrade is generic, and there are very few assumptions that
have been made:
• All of the accounting lines data that are upgraded are copied as is, and no
calculations or functional checks are done. Therefore, the data after the upgrade will
be the same as it was before the upgrade.
• Transactions that have no accounting impact will not be upgraded. That is, if there
are no accounting lines corresponding to a transaction event, that record will not be
upgraded. Tax book events that have accounting lines that correspond to their
corporate book transaction event, but not a tax book one, however, will still be
upgraded.
• Books or reporting books that are disabled will not be upgraded.
After the Subledger Accounting upgrade, a number of changes have been made to the
business flows for the Journal Entry processing as the following:
• Profile option FA: Use Workflow Account Generation is set to Yes during the
upgrade. Customers should analyze current customizations in the workflow setup.
If the requirement is to use the rules in workflow for generating code combinations
for asset transactions, there are two options:
Re-implement the custom rules in Subledger Accounting. Use the workflow rules as they are, which is the default value upon upgrade.
• Journal Source and Journal Category setups have been removed from the Book
Controls setup form. This setup has moved to Subledger Accounting.
• Depreciation Expense Account and the Bonus Expense Account for all category and
book combinations in the Asset Category setup form have been upgraded from a
single segment account value to entire account combinations.
• The intercompany account setup in Book Controls form has been replaced by
Intercompany/Intracompany setup in Accounting Setups.
Note: In Release 12, the Intercompany setups will be maintained at
the ledger level. The upgrade will update the existing
Intercompany setup at book level to ledger level.
• Users will need to run Create Accounting instead of Create Journal Entries.
• Users will need to run Calculate Deferred Depreciation and then Create Accounting
instead of Create Deferred Depreciation Journal Entries.
The following lists those features that are obsolete in Release 12 or replaced by another
feature:
• The Create Journal Entries and Rollback Journal Entries programs are now obsolete.
Create Journal Entries has been replaced by Create Accounting.
• The Create Deferred Depreciation Journal Entries program is now obsolete. Users
now need to run Calculate Deferred Depreciation followed by Create Accounting.
• The Account Drill Down report has been replaced by a new Subledger Accounting
report called the Account Analysis report.
• Profile option "FA: Include Nonrecoverable Tax in Mass Addition" is obsolete. This
is replaced by Post Accounting Programs under SLA. The setup for all eligible lines
from Payables to Assets for Mass Additions Create program is done in Post
Accounting Programs.
Overview
Oracle Assets : Overview :-
-----------------------------
In Release 12, Oracle Assets introduces a number of new features. Some of these
features require a data upgrade and involve terminology, prompt, and flow changes.
Some of the existing functionality is now obsolete.
-----------------------------
In Release 12, Oracle Assets introduces a number of new features. Some of these
features require a data upgrade and involve terminology, prompt, and flow changes.
Some of the existing functionality is now obsolete.
Oracle iProcurement Module
Oracle iProcurement
This section have covered all the changes in the Oracle iProcurement module in 12 Release.
Overview
Catalog Agreement Management
Content Security
This section have covered all the changes in the Oracle iProcurement module in 12 Release.
Overview
Catalog Agreement Management
Content Security
Content Security
Oracle iProcurement : Content Security :-
-----------------------------------------------
The upgrade process will upgrade existing realms, stores, and catalogs to Release 12
stores and content zones in the following way:
• Migrate local catalogs to become Local content zones. Local catalogs may contain
supplier restrictions. These restrictions are carried forward as supplier restrictions
in Release 12 content zones.
• Migrate punch out, transparent punch out, and informational punch out catalogs to
their corresponding types of Release 12 content zones.
• Migrate catalog and non-catalog stores to become Release 12 stores. Release 12
stores can contain both catalog and non-catalog content. Previous stores may
contain operating unit restrictions. These restrictions will not be carried forward
into Release 12 stores. Instead, these restrictions are applied to every content zone
within each store having operating unit restrictions.
• Migrate category realms at the responsibility level. In Release 12, category
restrictions are applied to each individual content zone.
• Migrate item source realms for Responsibilities.
• Migrate Default Smart Forms such that they have the lowest available sequence
number within Release 12 stores. This way, smart forms that appeared by default
previously will continue to appear by default in Release 12.
• POR: Approved Pricing Only profile is no longer used. The upgrade will apply the
correct settings in each content zone to achieve the same functionality in Release 12.
• Migrate descriptor configuration. Previously, it is possible to provide invalid values
for Descriptor settings such as Search Result Visibility, Item Detail Visibility, and Searchability— Invalid configuration settings were simply ignored by the system.
Release 12 validates Descriptor configurations at the time when they are updated in
the user interface, and will not allow any invalid value to be provided.
• The upgrade will re-default all the properties for the seeded descriptors from
previous releases. For example, visibility, sequence setting and alternate names may
change. After the upgrade, administrators should review the seeded descriptors
properties and make any necessary changes.
The following notes refer to changes in behavior in Release 12 as a result of Content
Security enhancements:
• Shopping Lists are migrated but content security is applied differently on Release
12 Public and Favorite lists. In Release 12, items on Shopping Lists are available to a
user if that user's responsibility and Operating Unit context are such that he would
have access to that same item through a Store. If the user does not have access
rights to an item through the normal Store search and browse function, he will not
have access rights to that item on a Shopping List.
• User-level realm will no longer be supported.
-----------------------------------------------
The upgrade process will upgrade existing realms, stores, and catalogs to Release 12
stores and content zones in the following way:
• Migrate local catalogs to become Local content zones. Local catalogs may contain
supplier restrictions. These restrictions are carried forward as supplier restrictions
in Release 12 content zones.
• Migrate punch out, transparent punch out, and informational punch out catalogs to
their corresponding types of Release 12 content zones.
• Migrate catalog and non-catalog stores to become Release 12 stores. Release 12
stores can contain both catalog and non-catalog content. Previous stores may
contain operating unit restrictions. These restrictions will not be carried forward
into Release 12 stores. Instead, these restrictions are applied to every content zone
within each store having operating unit restrictions.
• Migrate category realms at the responsibility level. In Release 12, category
restrictions are applied to each individual content zone.
• Migrate item source realms for Responsibilities.
• Migrate Default Smart Forms such that they have the lowest available sequence
number within Release 12 stores. This way, smart forms that appeared by default
previously will continue to appear by default in Release 12.
• POR: Approved Pricing Only profile is no longer used. The upgrade will apply the
correct settings in each content zone to achieve the same functionality in Release 12.
• Migrate descriptor configuration. Previously, it is possible to provide invalid values
for Descriptor settings such as Search Result Visibility, Item Detail Visibility, and Searchability— Invalid configuration settings were simply ignored by the system.
Release 12 validates Descriptor configurations at the time when they are updated in
the user interface, and will not allow any invalid value to be provided.
• The upgrade will re-default all the properties for the seeded descriptors from
previous releases. For example, visibility, sequence setting and alternate names may
change. After the upgrade, administrators should review the seeded descriptors
properties and make any necessary changes.
The following notes refer to changes in behavior in Release 12 as a result of Content
Security enhancements:
• Shopping Lists are migrated but content security is applied differently on Release
12 Public and Favorite lists. In Release 12, items on Shopping Lists are available to a
user if that user's responsibility and Operating Unit context are such that he would
have access to that same item through a Store. If the user does not have access
rights to an item through the normal Store search and browse function, he will not
have access rights to that item on a Shopping List.
• User-level realm will no longer be supported.
Catalog Agreement Management
Oracle iProcurement : Catalog Agreement Management :-
------------------------------------------------------------------
Bulk-loaded items in iProcurement will be migrated to newly created Global Blanket
Procurement Agreements (GBPA) based on their Supplier, Supplier Site, Currency,
Operating Unit, and Contract Reference. From the iProcurement Catalog
Administration responsibility, there will be a summary of all newly created GBPAs for
bulk-loaded items. There will also be a data-exceptions report that lists all the
exceptions that prevent migration of bulk-loaded content to new GBPAs. For more
details on how to correct these exceptions, refer to the iProcurement Preupgrade steps
in the Oracle Applications Upgrade Guide: Release 11i to Release 12.
The following is a list of changes in Release 12 as a result of the catalog upgrade:
• The upgrade will migrate bulk-loaded items into GBPAs. Release 12 , users will
load content into a GBPA and they will no longer need to provide Supplier,
Supplier Site, Operating Unit, and CPA/GCPA reference in the file. The bulk-load
option will also be available for BPAs and quotes.
• In Release 12, users will not be able to load catalog content for all Operating Units.
Please refer to the Oracle Purchasing Implementation guide for more details on
assigning GBPAs to Operating Units.
• Approved Supplier's Lists (ASLs) will not be shown in iProcurement search results.
In Release 12, the Oracle Purchasing Sourcing Rule will be used to determine the
best Supplier and Supplier Site combination during the requisition creation process.
• The bulk-load file format in Release 12 has been changed. A Converter has been
provided for users to convert old files to Release 12 format.
• In Release 12, users will not need to run the extractor to update the catalog content.
It will be updated in real-time.
------------------------------------------------------------------
Bulk-loaded items in iProcurement will be migrated to newly created Global Blanket
Procurement Agreements (GBPA) based on their Supplier, Supplier Site, Currency,
Operating Unit, and Contract Reference. From the iProcurement Catalog
Administration responsibility, there will be a summary of all newly created GBPAs for
bulk-loaded items. There will also be a data-exceptions report that lists all the
exceptions that prevent migration of bulk-loaded content to new GBPAs. For more
details on how to correct these exceptions, refer to the iProcurement Preupgrade steps
in the Oracle Applications Upgrade Guide: Release 11i to Release 12.
The following is a list of changes in Release 12 as a result of the catalog upgrade:
• The upgrade will migrate bulk-loaded items into GBPAs. Release 12 , users will
load content into a GBPA and they will no longer need to provide Supplier,
Supplier Site, Operating Unit, and CPA/GCPA reference in the file. The bulk-load
option will also be available for BPAs and quotes.
• In Release 12, users will not be able to load catalog content for all Operating Units.
Please refer to the Oracle Purchasing Implementation guide for more details on
assigning GBPAs to Operating Units.
• Approved Supplier's Lists (ASLs) will not be shown in iProcurement search results.
In Release 12, the Oracle Purchasing Sourcing Rule will be used to determine the
best Supplier and Supplier Site combination during the requisition creation process.
• The bulk-load file format in Release 12 has been changed. A Converter has been
provided for users to convert old files to Release 12 format.
• In Release 12, users will not need to run the extractor to update the catalog content.
It will be updated in real-time.
Overview
Oracle iProcurement : Overview:-
--------------------------------------
Oracle iProcurement Release 12 gives catalog administrators the ability to make small
and quick updates to catalog content online. The online authoring feature complements
the existing batch upload process, which is optimized for large data upload. This release
also gives more comprehensive and flexible rules for securing catalog content. Below is
a description of the upgrade impact on the catalog management.
--------------------------------------
Oracle iProcurement Release 12 gives catalog administrators the ability to make small
and quick updates to catalog content online. The online authoring feature complements
the existing batch upload process, which is optimized for large data upload. This release
also gives more comprehensive and flexible rules for securing catalog content. Below is
a description of the upgrade impact on the catalog management.
Saturday, September 6, 2008
Invoices Associated with the Given Purchase Order Number
PO: Invoices Associated with the Given Purchase Order Number:-
------------------------------------------------------------------------------------------------------------------
SELECT aip.invoice_id invoice_id,
b.po_number po_number
FROM ap_invoices_all aip,
(SELECT invoice_id,po_number FROM ( SELECT ai.invoice_id,
AP_INVOICES_PKG.GET_PO_NUMBER( ai.invoice_id) po_number
FROM AP_INVOICES_ALL AI) A
WHERE a.po_number <>'UNMATCHED') b
where b.invoice_id=aip.invoice_id
and b.po_number= ‘Purchase Order Number’;
------------------------------------------------------------------------------------------------------------------
SELECT aip.invoice_id invoice_id,
b.po_number po_number
FROM ap_invoices_all aip,
(SELECT invoice_id,po_number FROM ( SELECT ai.invoice_id,
AP_INVOICES_PKG.GET_PO_NUMBER( ai.invoice_id) po_number
FROM AP_INVOICES_ALL AI) A
WHERE a.po_number <>'UNMATCHED') b
where b.invoice_id=aip.invoice_id
and b.po_number= ‘Purchase Order Number’;
Subscribe to:
Posts (Atom)
