Oracle For Peoplesoft Enterprise Financials: Financial Operations Control 2.3 - Release Notes
Oracle For Peoplesoft Enterprise Financials: Financial Operations Control 2.3 - Release Notes
Oracle For Peoplesoft Enterprise Financials: Financial Operations Control 2.3 - Release Notes
3 - Release Notes
Release 2.3
Part No. E14386-01
January 2009
Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financials: Financial Operations Control 2.3 Release Notes Part No. E14386-01 Copyright 2009, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
Contents
Contents....................................................................................................................................... 1 About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3 Preface .............................................................. 2 Oracle Release Information Publications ................................................................................. 2 Additional Resources ............................................................................................................... 3 About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3............................................................................ 4 Canonical Data Model .............................................................................................................. 4 Integrated Inventory Valuation Management ........................................................................... 4 Integrated Sales Revenue Recognition.................................................................................... 5 Integrated Procure to Pay ........................................................................................................ 5 Product Enhancements for Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications 2.3........................................................................................... 5 Life Cycle Data Management ................................................................................................... 6 Enhanced Inventory Valuation ............................................................................................... 13 Timely Revenue Recognition ................................................................................................. 17 Streamlined Merchandising Procure to Pay........................................................................... 20 Drill Back and Drill Forward.................................................................................................... 23 Key Features .......................................................................................................................... 24 Participating Application Enhancements ................................................................................... 25 Oracle Retail Merchandising System 13.0.2 .......................................................................... 26 PeopleSoft Enterprise Financial Applications 9.0 .................................................................. 26 Foundation Pack Enhancements 2.3......................................................................................... 27 EBO Enhancements............................................................................................................... 27 ODI 10.1.4.8 ........................................................................................................................... 27
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3 Preface
This preface discusses: Oracle release information publications Additional resources
Statement of Direction
The statement of direction is published 6 to 9 months before a release. It provides a high-level overview of the major focus of product development efforts, enabling high-level business decision makers to begin preliminary upgrade planning.
What out-of-the-box functionality will change? What customizations may be affected? How will an upgrade or new implementation affect other systems?
Copyright 2009 Oracle. All rights reserved.
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
After the project team has reviewed and analyzed the release content document, business decision makers should be in the position to determine whether to allocate budget and initiate implementation plans. The Release Content Document is published approximately 1 month before a release.
About Document
The About Document contains release notes and is published at release. It validates the final scope of the release, and outlines the features and enhancements that are available with the release of each product, describing the finalized functional and technical details that will enable project teams to confirm budgets and complete implementation plans.
Additional Resources
There are many additional resources that will help your organization determine the affects of upgrading to this release. Visit the Oracle Metalink website frequently to keep apprised of ongoing changes. This table lists the types of resources that are available on Oracle Metalink: Resource User guides Navigation Top Tech Docs > Online Documentation > Applications Knowledge Home > Oracle Applications > Integrations > Applications Integration Architecture Data models Installation guides Upgrade guides Top Tech Docs > Applications Electronic Technical Reference Manuals (eTRM) Knowledge Home > Oracle Applications > Integrations > Applications Integration Architecture Knowledge Home > Oracle Applications > Integrations > Applications Integration Architecture
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
The new features and enhancements that are included in this release are grouped by release themes, then by product area. Our goal is to help organizations leverage technology to its fullest and increase the efficiency and effectiveness of operations. Please note that the final release may not have every feature that is discussed in this document, and a specific feature may become part of a different application or have a product name that is different from those cited in this document. Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3 is focused on the following key areas: Canonical data model Integrated inventory valuation management Integrated sales revenue recognition Integrated procure to pay
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
Oracle Retail Merchandising System (RMS), through its Stock Ledger component, provides PeopleSoft Financial applications with the value of ending inventory at cost using the method the retailer indicates (cost method or retail method of accounting).
Product Enhancements for Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications 2.3
This section discusses new enhancements for the Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control and its key features. These enhancements fall into five areas: Life cycle data management Enhanced inventory valuation Timely revenue recognition Streamlined merchandising procure to pay Drill back and drill forward
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
The life cycle data management includes: Currency exchange rate integration Payment term integration Suppliers information integration Chart of accounts combination validation integration
This integration is not a point-to-point integration between PeopleSoft GL and RMS. An AIA layer serves as a transformation and mediation layer between PeopleSoft GL and RMS. As a part of the currency exchange rates integration, PeopleSoft GL sends the currency exchange rates to the AIA layer and the AIA layer delivers the information to RMS. The AIA layer performs message filtering, message transformation, and message routing. Additionally, it separates the participating applications from one another so that separate upgrade cycles may be utilized.
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
PeopleSoft Payables is the source of valid payment terms. RMS uses payment terms to apply the correct payment terms to a supplier or purchase order and ensures correct timing of payment and application of payment term discounts. The payment terms integration synchronizes payment terms information from PeopleSoft Payables to RMS through these integration flows: Load initial payment term from PeopleSoft Payables to RMS: Enables the loading of all payment terms from PeopleSoft Payables to RMS for a new instance (logical or physical) of RMS. Incremental creation and updates of payment term from PeopleSoft Payables to RMS: Enables the synchronization of incremental creation and updates of the payment terms from PeopleSoft Payables to RMS.
This integration is not a point-to-point integration between PeopleSoft Payables and RMS. An AIA layer serves as a transformation and mediation layer between PeopleSoft Payables and RMS. As a part of the payment term integration, PeopleSoft Payables sends the payment term to the AIA layer and the AIA layer delivers the information to RMS. The AIA layer performs message filtering, message transformation, and message routing. Additionally, it separates the participating applications from one another so that separate upgrade cycles may be utilized. This diagram illustrates the payment term integration flow:
Supplier Integration
In the integrated environment, PeopleSoft Payables acts as a payables and accounting engine, and RMS handles supplier payments, merchandise write-offs, and prepaid adjustments. Merchandise suppliers are suppliers of goods and services that the retailer sells to customers. PeopleSoft Payables and RMS require sharing of suppliers information between them. RMS requires the supplier information for several key functions including creation and management of items and purchase orders. PeopleSoft Payables requires suppliers information for supplier payment. For end-to-end business integration, same supplier usage and related information must be shared between these two systems. Between the two participating applications, PeopleSoft Payables is the source of valid suppliers (vendors in PeopleSoft Payables) and their Remit to Location and Order from Addresses, and the relationships between this supplier data and the financial business unit structure.
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
The supplier integration synchronizes suppliers information from PeopleSoft Payables to RMS through these integration flows: Load initial suppliers from PeopleSoft Payables to RMS: Enables the loading of all active merchandise suppliers, supplier locations and their remit and order to addresses, and the relationship between the supplier data and the financial business unit structure from PeopleSoft Payables to RMS for a new instance (logical or physical) of RMS. It is a preimplementation stage. PeopleSoft suppliers must be classified as supplier and have the open for ordering attribute for the initial load. Incremental creation and updates of suppliers from PeopleSoft Payables to RMS: Enables the synchronization of incremental creation and updates of the suppliers from PeopleSoft Payables to RMS.
This integration is not a point-to-point integration between PeopleSoft Payables and RMS. An AIA layer serves as a transformation and mediation layer between PeopleSoft Payables and RMS. As a part of the supplier integration, PeopleSoft Payables sends the suppliers information to the AIA layer and the AIA layer delivers the information to RMS. The AIA layer performs message filtering, message transformation, and message routing. Because this integration is not a point-topoint integration, the vendor number (ID) in PeopleSoft is not similar to the supplier number (ID) in Oracle Retail. Even though the vendor numbers may be different in the two systems, predefined user inquiries enable rapid access to the vendor number ensuring ease of lookup. Additionally, it separates the participating applications from one another so that separate upgrade cycles may be utilized. This diagram illustrates the supplier integration flow:
10
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
PeopleSoft GL is the system of record for chart of accounts segment combinations. Chart of accounts ChartFields (segments) combinations are set up manually in Oracle Retail Merchandising System (RMS), Retail Invoice Matching (ReIM), and Retail Sales Audit (ReSA). This manual setup enables assignment of transaction data in sales audit, stock ledger, and invoice match to specific account codes. ReIM can also create segment combinations dynamically during the invoice match transaction processing. While creating the valid segment combinations, Oracle Retail validates each created combination individually with PeopleSoft GL. Any valid segment combination in Oracle Retail must exist as a valid combination in PeopleSoft GL. Oracle Retail publishes the segment combination to PeopleSoft GL for validation. PeopleSoft GL verifies the combination and returns the status to Oracle Retail. If the combination is valid, the combination is stored in the Oracle retail database tables. Oracle Retail sends these data for validation to PeopleSoft GL: Requesting system (RMS, ReIM, or ReSA) Set of books (GL business unit) Segment or ChartField combination values
PeopleSoft GL sends the validation status whether the combination is valid. The AIA layer copies all the other information from the original request and sends these response data to Oracle Retail: Requesting system (RMS, ReIM, or ReSA) Set of books (GL business unit) Valid segment or ChartField combination values Validation status valid or invalid
11
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
This diagram shows the chart of accounts combination validation integration flow:
12
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
13
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
Inventory valuation
14
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
The stock ledger transactions to be loaded into PeopleSoft GL are placed on the financial staging table through the use of table triggers or batch, by means of the appropriate General Ledger account combinations (maintained in the RMS cross-reference table in Oracle Retail) and the currency exchange rates. The PeopleSoft Journal Generator loads the accounting entries from Oracle Retail and creates PeopleSoft GL journal entries. The accounting tables are referenced on the accounting entry definition defined for each type of accounting entry transaction. The Journal Generator uses new accounting entry definitions to create PeopleSoft journal entries. When the journal entries have been created by the Journal Generator, they are edited and posted similarly to the PeopleSoft subsystem journals.
15
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
16
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
Revenue recognition
Copyright 2009 Oracle. All rights reserved. 17
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
18
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
19
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
20
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
These diagrams show the Retail Merchandise Procure to Pay business process flow:
21
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
22
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
In this integration, the AIA layer maintains the cross-references to associate the object identifications among the RMS, ReSA, and ReIM systems and the PeopleSoft GL and Payables systems. The cross-reference is built during the processes for submission of invoices, credit notes, debit memos, and rebates in ReIM to PeopleSoft Payables. The AIA services use the cross-references to link the invoices to payments. This diagram illustrates the overall drill back and drill forward flows:
23
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
Key Features
Here are the key features of this PIP: This integration is not a point-to-point integration between the PeopleSoft Enterprise Financials system and Oracle Retail applications. This PIP implementation is independent of version of integrated applications. An AIA layer serves as a thin, intermediate layer of application between PeopleSoft Enterprise Financials system and Oracle Retail. Importantly, this integration remains synchronized with the new releases of the participating applications. Audited transaction data is exported to the PeopleSoft Financial applications days before the traditional audit process permits. The Financials applications can use this timely data in a proactive manner, which results in increased productivity and operational efficiencies. A pre-packaged integration enables rapid deployment of the customer process and thus reduces the cost and risk associated with the integration. Total cost of ownership for Oracle and its customers is also reduced. Provides consistent supplier data. Without this synchronization, an organization cannot be served effectively. Automated processes result in increased operational efficiencies. Seamless drill back and drill forward actions between the PeopleSoft Enterprise Financials system and Oracle Retail applications. Drill back and forward capabilities enable traceability between the Oracle Retail transactions and ledger journal entries. The Oracle Retail as well as PeopleSoft users do not require any training on inquiring the specific data in either application. Use of Oracle Data Integrator to handle large volumes of transactions. Leverages the current processes and integration in Oracle Retail and PeopleSoft Enterprise Financials system.
24
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
This diagram illustrates the overall process flow of the Oracle Retail to PeopleSoft Financials PIP:
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
26
About Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financial Applications: Financial Operations Control 2.3
For more information, about the enhancements to the foundation pack, see the release notes for Oracle AIA Foundation Pack 2.3.
EBO Enhancements
EBO enhancements include: Payment Terms EBO: Date effectivity is added in the AIA layer. This enables you to future date the appropriate payment term. Supplier Party EBO: Contact information for supplier location is added in the AIA layer. This enables you to define your supply chain in a better way.
ODI 10.1.4.8
ODI 10.1.4.8 enhancements include the following changes: All bulk data movement is removed from BPEL flows and moved to ODI to enable far greater performance and scalability. Cross-reference data is generated between the supplier, payment terms, and invoice and voucher objects. This provides you traceability and scalability of the cross-referenced data.
27