Document Sequencing of Payments:-
------------------------------------------
If you used document sequencing for payments in Release 11i, your document sequence
category has been migrated from the payment document, which is associated with a
bank account and hence, legal entity in Release 12, to the bank account uses entity. If
you require, you can also specify the document sequence category at the bank account
payment method and payment document levels. These changes are necessary to
preserve the option of having document sequence categories vary across operating Units.
Friday, August 22, 2008
Centralized Banks and Bank Account Definitions in Oracle Cash Management
Centralized Banks and Bank Account Definitions in Oracle Cash Management:-
-------------------------------------------------------------------------------------------
In Release 12, the ownership of internal banks and bank accounts will move to Oracle
Cash Management for all products in the E-Business Suite. All internal banks and bank
accounts you had defined for your operations will be migrated from the Payables
entities to the central Cash Management entities. A Legal Entity now owns the bank
accounts and their payment documents, rather than being owned by an Operating Unit,
as in prior releases.
Also in Release 12, the ownership of supplier bank accounts transitions from Oracle
Payables to Oracle Payments. The banks and bank branches will be centralized in
Oracle Cash Management entities, as above, however the bank accounts you had
defined for your suppliers will be migrated from the Payables entities to the central
Payments entities. Oracle Payments centralizes and secures all payment instrument
data, including external bank accounts, credit cards, debit cards, and so forth.
-------------------------------------------------------------------------------------------
In Release 12, the ownership of internal banks and bank accounts will move to Oracle
Cash Management for all products in the E-Business Suite. All internal banks and bank
accounts you had defined for your operations will be migrated from the Payables
entities to the central Cash Management entities. A Legal Entity now owns the bank
accounts and their payment documents, rather than being owned by an Operating Unit,
as in prior releases.
Also in Release 12, the ownership of supplier bank accounts transitions from Oracle
Payables to Oracle Payments. The banks and bank branches will be centralized in
Oracle Cash Management entities, as above, however the bank accounts you had
defined for your suppliers will be migrated from the Payables entities to the central
Payments entities. Oracle Payments centralizes and secures all payment instrument
data, including external bank accounts, credit cards, debit cards, and so forth.
Invoice Lines
Invoice Lines:-
----------------
Invoice Lines are introduced as an entity between the invoice header and invoice
distributions in order to better match the structure of real world invoice documents and
improve the flow of information in the Oracle E-Business Suite. With the new model,
the invoice header remains unchanged, and continues to store information about the
supplier who sent the invoice, the invoice attributes and remittance information.
Invoice lines represent the goods (direct or indirect materials), service(s) and/or
associated tax/freight/miscellaneous charges invoiced. Invoice distributions store the accounting, allocation and other detail information that makes up the invoice line. In
prior releases, a charge allocation table managed the allocations, but this entity is
obsolete in Release 12.
During the upgrade, Oracle Payables creates one invoice line for every distribution
available in the 11i distributions table, except in the case of reversal pairs where
Payables creates one line with a zero amount. Other Release 12 features like Subledger
Accounting and E-Business Tax integration require that Payables invoice distributions
be stored at the maximum level of detail. Oracle Payables makes this transformation of
existing invoice distributions during the upgrade. For example, instead of storing the
Exchange Rate Variance and Invoice Price Variance as attributes of an invoice
distribution, as in prior releases, Oracle Payables will create a distribution for each of
those charges.
----------------
Invoice Lines are introduced as an entity between the invoice header and invoice
distributions in order to better match the structure of real world invoice documents and
improve the flow of information in the Oracle E-Business Suite. With the new model,
the invoice header remains unchanged, and continues to store information about the
supplier who sent the invoice, the invoice attributes and remittance information.
Invoice lines represent the goods (direct or indirect materials), service(s) and/or
associated tax/freight/miscellaneous charges invoiced. Invoice distributions store the accounting, allocation and other detail information that makes up the invoice line. In
prior releases, a charge allocation table managed the allocations, but this entity is
obsolete in Release 12.
During the upgrade, Oracle Payables creates one invoice line for every distribution
available in the 11i distributions table, except in the case of reversal pairs where
Payables creates one line with a zero amount. Other Release 12 features like Subledger
Accounting and E-Business Tax integration require that Payables invoice distributions
be stored at the maximum level of detail. Oracle Payables makes this transformation of
existing invoice distributions during the upgrade. For example, instead of storing the
Exchange Rate Variance and Invoice Price Variance as attributes of an invoice
distribution, as in prior releases, Oracle Payables will create a distribution for each of
those charges.
Suppliers Added to Trading Community Architecture
Suppliers Added to Trading Community Architecture ( TCA ):-
------------------------------------------------------------------------
In Release 12, Suppliers are defined as Trading Community Architecture (TCA) parties.
During the upgrade, TCA party records are created and updated for all suppliers, they
are linked back to their records in the supplier entities and the payment and banking
details are migrated into the Oracle Payments data model. The supplier, supplier site,
and supplier contacts tables are obsolete and replaced with views that join information
from the old tables with information in TCA.
TCA Party Creation for Suppliers
During the upgrade, Oracle Payables creates new parties in TCA for all suppliers that
do not have existing party information. The parties are created with a party usage of
supplier. Country and address information is required for parties in the TCA data
model, so if there is no country or address line 1 specified for a supplier site, Oracle
Payables derives the country based on the most frequently used operating unit of the
supplier's historical transactions. E-Business Tax uses the country information when
you elect to calculate tax based on ship-from or bill-from location criteria. Please
confirm your setup of parties before you elect to use this E-Business Tax feature.
Also during the upgrade, Oracle Payables reviews the supplier sites and determines
duplicates, based on the supplier, address, city, county, province, state, country, zip and
language. Oracle Payables then creates only one Party Site for each distinct supplier site
address.
Suppliers created using Oracle Trade Management, Oracle Transportation
Management, and Oracle iSupplier Portal have existing party information. During the
upgrade, Oracle Payables updates the existing party in TCA with the Taxpayer ID from
the supplier record, if it is different from the one in TCA.
TCA Party Creation for Employees
In prior releases, employees were defined and linked to a supplier record in order for
Oracle Payables to create payments for their expense reports. Employees defined in
Oracle Human Resources and associated with an Oracle Payables supplier record have
existing party information. During the upgrade, Oracle Payables updates the existing
party information to have a party usage of supplier. Oracle Payables does not migrate
the employee address to the party site in TCA, they remain in Oracle Human Resources
for data security reasons.
Migration of Other Supplier Attributes
In Release 11i, you could record the relationship between a franchise or subsidiary and
its parent company by recording a value for the Parent Supplier field in the Suppliers
window. During the Release 12 upgrade, this information is migrated into the party
relationships model of TCA.
------------------------------------------------------------------------
In Release 12, Suppliers are defined as Trading Community Architecture (TCA) parties.
During the upgrade, TCA party records are created and updated for all suppliers, they
are linked back to their records in the supplier entities and the payment and banking
details are migrated into the Oracle Payments data model. The supplier, supplier site,
and supplier contacts tables are obsolete and replaced with views that join information
from the old tables with information in TCA.
TCA Party Creation for Suppliers
During the upgrade, Oracle Payables creates new parties in TCA for all suppliers that
do not have existing party information. The parties are created with a party usage of
supplier. Country and address information is required for parties in the TCA data
model, so if there is no country or address line 1 specified for a supplier site, Oracle
Payables derives the country based on the most frequently used operating unit of the
supplier's historical transactions. E-Business Tax uses the country information when
you elect to calculate tax based on ship-from or bill-from location criteria. Please
confirm your setup of parties before you elect to use this E-Business Tax feature.
Also during the upgrade, Oracle Payables reviews the supplier sites and determines
duplicates, based on the supplier, address, city, county, province, state, country, zip and
language. Oracle Payables then creates only one Party Site for each distinct supplier site
address.
Suppliers created using Oracle Trade Management, Oracle Transportation
Management, and Oracle iSupplier Portal have existing party information. During the
upgrade, Oracle Payables updates the existing party in TCA with the Taxpayer ID from
the supplier record, if it is different from the one in TCA.
TCA Party Creation for Employees
In prior releases, employees were defined and linked to a supplier record in order for
Oracle Payables to create payments for their expense reports. Employees defined in
Oracle Human Resources and associated with an Oracle Payables supplier record have
existing party information. During the upgrade, Oracle Payables updates the existing
party information to have a party usage of supplier. Oracle Payables does not migrate
the employee address to the party site in TCA, they remain in Oracle Human Resources
for data security reasons.
Migration of Other Supplier Attributes
In Release 11i, you could record the relationship between a franchise or subsidiary and
its parent company by recording a value for the Parent Supplier field in the Suppliers
window. During the Release 12 upgrade, this information is migrated into the party
relationships model of TCA.
Introduction
Introduction:-
----------------
In Release 12, the Oracle E-Business Suite introduces Subledger Accounting, E-Business
Tax, Ledgers, Banks and other common data model components that are used by Oracle
Payables.
The following are new in Release 12:
• Suppliers are defined as Parties within Oracle Trading Community Architecture.
• Invoice Lines are introduced as an entity between the invoice header and invoice
distributions in order to better match the structure of invoice documents and
improve the flow of information like manufacturer, model, and serial number from
Purchasing through to Assets.
• Banks, bank branches and internal bank accounts are defined centrally and managed in Oracle Cash Management.
• Document sequencing of payments has moved to the Cash Management bank
account uses setup
• Payments, and all funds disbursement activities, are handled by a new module,
Oracle Payments
• Payment features controlled by Global Descriptive Flexfields (GDF) in prior
releases have been consolidated and migrated into the data models of Oracle
Payables, Oracle Payments and Oracle Cash Management. The architecture of this
solution moves attributes from the GDFs, which are obsolete in Release 12, to
regular fields on the appropriate entity, including the invoice, payment format &
document, supplier site, and bank account. Having a single code base as opposed to
GDFs implemented per country simplifies global implementations and streamlines
transaction processing.
• Oracle Subledger Accounting, a new module in Release 12, handles accounting
definitions and all accounting setup associated with a Ledger. (In Release 12, Oracle
General Ledger has replaced Sets of Books with Ledgers.) As part of this change,
centralized accounting reports are available to all applications. Additionally, Oracle
Payables introduces a new Trial Balance report.
• Oracle E-Business Tax, a new module, manages transaction tax setup associated
with trading partners and tax authorities, as well as all transaction tax processing
and reporting across the E-Business suite of applications. Part of the architecture of
this solution moves tax attributes from Global Descriptive Flexfields (GDFs), which
are obsolete in Release 12, to regular fields on the appropriate entities.
• A Responsibility can be associated with multiple Operating Units using Multi
Organizations Access Control. Due to this change, all processing and some
reporting in Oracle Payables is available across Operating Units from a single
applications responsibility. Hence you can isolate your transaction data by
operating unit for security and local level compliance while still enabling shared
service center processing.
----------------
In Release 12, the Oracle E-Business Suite introduces Subledger Accounting, E-Business
Tax, Ledgers, Banks and other common data model components that are used by Oracle
Payables.
The following are new in Release 12:
• Suppliers are defined as Parties within Oracle Trading Community Architecture.
• Invoice Lines are introduced as an entity between the invoice header and invoice
distributions in order to better match the structure of invoice documents and
improve the flow of information like manufacturer, model, and serial number from
Purchasing through to Assets.
• Banks, bank branches and internal bank accounts are defined centrally and managed in Oracle Cash Management.
• Document sequencing of payments has moved to the Cash Management bank
account uses setup
• Payments, and all funds disbursement activities, are handled by a new module,
Oracle Payments
• Payment features controlled by Global Descriptive Flexfields (GDF) in prior
releases have been consolidated and migrated into the data models of Oracle
Payables, Oracle Payments and Oracle Cash Management. The architecture of this
solution moves attributes from the GDFs, which are obsolete in Release 12, to
regular fields on the appropriate entity, including the invoice, payment format &
document, supplier site, and bank account. Having a single code base as opposed to
GDFs implemented per country simplifies global implementations and streamlines
transaction processing.
• Oracle Subledger Accounting, a new module in Release 12, handles accounting
definitions and all accounting setup associated with a Ledger. (In Release 12, Oracle
General Ledger has replaced Sets of Books with Ledgers.) As part of this change,
centralized accounting reports are available to all applications. Additionally, Oracle
Payables introduces a new Trial Balance report.
• Oracle E-Business Tax, a new module, manages transaction tax setup associated
with trading partners and tax authorities, as well as all transaction tax processing
and reporting across the E-Business suite of applications. Part of the architecture of
this solution moves tax attributes from Global Descriptive Flexfields (GDFs), which
are obsolete in Release 12, to regular fields on the appropriate entities.
• A Responsibility can be associated with multiple Operating Units using Multi
Organizations Access Control. Due to this change, all processing and some
reporting in Oracle Payables is available across Operating Units from a single
applications responsibility. Hence you can isolate your transaction data by
operating unit for security and local level compliance while still enabling shared
service center processing.
Monday, August 18, 2008
Release 12 New Features
This section is design to the provide all the new features/changes done from 11i to Release 12.
GL Module
AP Module
Oracle Assets Module
Oracle iProcurement Module
GL Module
AP Module
Oracle Assets Module
Oracle iProcurement Module
GL Module 12 Release New Features
This section is design to give all the information about the changes in the GL Module from 11i to Release 12.
Changes in Terminology
Accounting Setup
Sets-of-Books Changes
Multiple Reporting Currency Changes
Global Accounting Engine Integration
Period Rates
Revaluation
Statistical Report-Level Currency for Financial Statement Generator Reports
Changes in Terminology
Accounting Setup
Sets-of-Books Changes
Multiple Reporting Currency Changes
Global Accounting Engine Integration
Period Rates
Revaluation
Statistical Report-Level Currency for Financial Statement Generator Reports
Subscribe to:
Posts (Atom)
