| Oracle® Retail Invoice Matching Release Notes Release 15.0 E69594-01 |
|
 Previous |
Release Notes
Release 15.0
E69594-01
December 2015
This document highlights the major changes for Release 15.0 of Oracle Retail Invoice Matching.
Oracle Retail Invoice Matching (ReIM) supports the verification of merchandise invoice costs and quantities prior to payment. ReIM receives invoice data through Electronic Data Interchange (EDI), or from invoices manually entered through a group or single invoice entry facility.
Invoice records are verified against associated receipts in an automated matching process. If invoices are matched to receipts within tolerance at a summary level, they are evaluated for best payment terms and posted to a staging table. The staging table is interfaced with the retailer's accounts payable system, where payments are processed and corresponding accounting entries are posted.
If invoices and receipts are not matched at the summary level after a specified period of time, the auto-matching process attempts to match at a line level within tolerance. If matches are not identified at the line level, the process calculates a cost or quantity discrepancy. The discrepancy is routed to defined user groups for resolution.
Discrepancies are resolved by applying reason codes based on a set of defined actions (for example, charge-back supplier) that determine disposition of the discrepancies. Discrepancies are routed out of the auto-match process. You can then begin manual identification of summary and detail level matches. The retailer can resolve line level discrepancies.
See the Oracle Retail Invoice Matching Installation Guide, Release 14.1 for information about the following:
Hardware and software requirements
Oracle Retail application software compatibility
|
Note: Mozilla Firefox is the recommended browser. Wide screen monitors are required. |
The functional enhancements described below are included in this release of ReIM.
ReIM now supports enhanced matching configurability to allow for the customization of matching solutions across suppliers. The configurable match engine includes the following:
A Match Key that allows users to create Configurable Match Pools (a collection of invoices and receipts in which matching is attempted):
Options associated with the Match Key include: Purchase Order (PO)/Location, PO, Supplier Site/Location, Supplier/Location, and Supplier Group/Location.
Match Strategies functionality defines which Auto Match processes to run for a supplier and in what order they should be run. Options include:
Summary All to All
Summary One to Many (Regular or Best)
Detail Match (Regular or Best)
|
Note: Match Strategies can be mapped to a Supplier or Supplier Group |
Auto match now supports the ability to automatically resolve cost or quantity discrepancies. This feature is supported by additional columns that have been added to the tolerance table and maintenance screen.
The Cost Pre-Matching routine has been made optional at the system level.
SKU compliance Percentage
Adds a validation to automatch summary matching logic which requires the percent of invoice items which appear on the receipt and the percent of receipt items which appear on the receipt to be above a threshold for the match to be accepted.
A system option has been added to allow line matching to be attempted before the routing date. However, if discrepancies exist, they are not sent to the Discrepancy Review List until after the routing date. Automatch has also been enhanced to continue attempts to match an invoice even after discrepancies have been generated.
Summary Match functionality has been rewritten to work within the Oracle Application Development Framework (ADF) environment. Features include the following:
The Summary Match Totals table has been expanded to include a status icon. The table also includes a variance percentage for both cost and quantity.
Suggested Match
This new feature executes 'best match' logic to suggest which receipts should be matched to a selected invoice or invoices.
Quick Match window
This window launches directly into the Summary Match screen using common attributes on the invoice such as Supplier ID, PO, or Invoice number.
The Invoices and receipts search screen popup allows documents to be added to the Summary Match screen.
A hyperlink now shows items and their details for the invoice.
A hyperlink now shows all items and their details for the receipt.
SKU compliance validation is also performed during manual summary matching. If the compliance validation fails, the user is given the option to override the validation and complete the match.
Detail Match has been completely rewritten to work under the ADF environment. Features include:
Detail Matching features a three-tiered table to drive the matching process. Tier one is the parent (or style) level, used for mass selecting the SKUs under the parent. Tier two is the SKU level and the main driver for matching functionality. It shows the invoice and receipt totals for the SKU and allows the SKU to be selected for processing. Tier three includes two types of rows, invoice rows and receipt rows, which can be individually included or excluded from consideration for matching.
The Summary Match Totals table is also shown on the Detail Match screen. It shows the status of the match at a summary level. There is also a 'Summary Match Button that becomes enabled if actions taken on the detail screen put the overall summary match within tolerance.
A new Detail Match Totals table has been added to the detail match screen to show the totals of the items selected for matching or resolution.
A Resolution Popup screen allows cost and quantity discrepancies to be resolved in one step. Additionally, it will allow for the resolution of discrepancies for multiple items at one time if they can be resolved with the same reason code.
There is now an ability to split a receipt item to match an invoice item.
There is now an ability to substitute a receipt item to match to a different invoice item.
The Discrepancy Review List replaces the Cost Review List and the Quantity Review List. It displays and allows resolution of both cost and quantity discrepancies in a single step. It will also allow for the mass resolution of discrepancies for multiple items. In addition, it links to the detail match screen to resolve complicated matching scenarios.
The Match Inquiry Screen is a new feature that shows the results of a match. The screen includes four containers: Invoice Header, Summary Match, Detail Match, and Adjustment Documents.
The Summary Match section includes hyperlinks on invoice and receipt to show additional detail of these documents. The Adjustment Documents container shows any Debit Memos, Credit Memos, or Credit Note Requests generated as a result of the matching process.
Tolerances are now independent entities that can be mapped to Supplier Sites, Suppliers, Supplier Groups, or Departments. One tolerance entity can be designated as the system default.
Additional columns have been added to the tolerance table and maintenance screen to facilitate automatic resolution of discrepancies for invoice matching during the auto match process. Note that these columns are only used for invoice auto resolution. Credit Note automatching continues with the previous approach, which used reason codes from the system options table.
The following enhancements were made to this functionality:
New tabs were added to facilitate entry viewing, and maintenance of billing details for both Fixed and Complex Deals.
New fields were added for Credit Note Match Keys. The Credit Note Auto match batch now uses these fields instead of reference fields 3 and 4 to build match pools. Fields were added for Credit Note ID, Invoice ID, Deal ID, and Deal Component.
The system now allows for the ability to perform a Discrepancy Write Off (DWO) when voiding a credit note request.
This functionality was redesigned to leverage the document maintenance screen as the basis for correcting errors in the document. In addition, the mass correction process was redesigned to take advantage of ADF features.
The process to reverse a debit memo has been redesigned. When reversing a debit memo, users have the option of reversing one or more items on the debit memo, and for each item, they can reverse the entire amount or just a portion of the item. When the reversal is executed, a Credit Memo is generated in approved status. This modified process eliminates the 'Disputed' status on a Credit Memo.
Manual Summary and Detail matching have undergone similar enhancements to those of Invoice matching, including:
Summary Match screen
'Suggested Match', and the hyperlinks on document IDs (in this case, document IDs are the Credit Note Request ID and Credit Note ID) to show items details.
Detail Match screen
Cost and quantity discrepancies can now be resolved in one step, and there is support for the mass resolution of discrepancies.
Credit Note Matching also has a Tax Validation feature to ensure that taxes are correct before matching is allowed.
Supplier options functionality has undergone the following modifications:
Supplier Options was enhanced to maintain options at the Supplier Site Level.
The 'Linked Supplier' function was replaced with a new 'Supplier Group' entity, which allows for the grouping of suppliers for matching purposes. The Supplier option now maintains options at three levels: supplier site, supplier, and supplier group.
The ability to map a match strategy to either a supplier or a supplier group was added.
System options has undergone the following modifications:
Parameters previously found in the ReIM.properties file have been moved to System Options.
The parameters by category have been organized and are maintained in collapsible containers.
Along with the re-architecture of the application to the ADF framework, ReIM now delivers a role-based dashboard and contextual business intelligence (BI). The dashboard and contextual reports were built using Oracle Business Intelligence Enterprise Edition (OBIEE), which provides the following:
The ability to build interactive dashboards and reporting.
The ability to invoke business processes from within those dashboards and reports.
The ability to support Contextual BI reports embedded within the application's transactional screens. The reports display data in context to the action being taken during the transaction.
The ReIM dashboards and contextual BI were designed specifically for the primary ReIM users, an Accounts Payable Specialist, and a Finance Manager, to help focus the work effort on the highest priority items and allow for the quick identification of areas of concern. In-context launch from the dashboard directly into ReIM screens also streamlines work efforts and increases productivity. The Operation Insights functionality is an optional component for the ReIM application.
The dashboard reports available include the following:
Upcoming Invoices
Automatch Rate
Supplier Site Performance (visible only to the Finance Manager)
Employee Workload (visible only to the Finance Manager)
Invoices
This is a report showing unmatched invoices assigned to the user. The report includes an in-context launch that calls the summary match screen to facilitate matching the invoice.
Contextual BI Reports include the following:
Supplier Site Details Report
Quantity Comparison Report
Cost Events Report
This section addresses the technical enhancements included in Oracle Retail Invoice Matching Release 15.0.
By moving to the ADF platform, ReIM provides several new features that were not previously available. These include the following:
Enhanced search capabilities, including the support for both basic and advanced search modes.
Configurable tables that support more robust filtering and sorting capabilities, as well as the ability to export to a spreadsheet.
Collapsible containers that allow users to minimize the data displayed on a screen to only the area they are interested in seeing.
The consolidation of screens that allows related screens to be displayed as tabs in a single screen rather than forcing users to open multiple windows. This functionality is also facilitated through the streamlining of the ReIM Task List, which is used to present to users the screens to which they have access.
In support of the functional requirements, the Invoice Matching batch programs were reviewed, and changes were made to streamline the overall process. The following programs have been deprecated: Financial posting workspace purge, discrepancy purge, disputed credit memo resolution rollup, and the user maintenance batch.
For more information, see the Oracle Retail Invoice Matching Operations Guide.
All batch processes were updated to utilize a new Fusion batch framework, and Java Spring dependencies were removed. Batch processes in the financial posting cycle were updated to allow configurability, allowing retailers to target a specific set of suppliers in a given run of the batch cycle.
For more information, see the Oracle Retail Invoice Matching Operations Guide.
Now that the UI architecture has been migrated to ADF, the previous 'Customization Toolkit' used for Invoice Matching has been replaced. Invoice Matching now supports the standard ADF customization process, leveraging non-invasive approaches for customization and extension.
RAAC is an application that is being introduced in 15.0 for Oracle Application Development Framework (ADF)-based applications such as ReIM. It is a replacement for the Retail Application Security Roles Manager (RASRM). RAAC allows application administrators to manage application roles, manage Application Navigator and manage notifications. Access to this application is provided for the application administrator role by default in ReIM and is accessible from the user interface's user menu.
For more information, see the Oracle Retail Application Administration Console chapter of the Oracle Retail Merchandising Implementation Guide.
The user interface now provides the ability for users to switch between applications using the Application Navigator facility.
These applications are configured using the Manage Application Navigator function within the Retail Application Administration Console (RAAC).
For more information, see the Oracle Retail Application Administration Console chapter of the Oracle Retail Merchandising Implementation Guide.
This technical enhancements described below are included in this release.
|
Note: The list below announces the addition of Oracle Retail support for the technology described. See the Installation Guide requirements section for critical information, such as whether the enhancement below replaces previous versions or is supported in addition to already existing versions. |
ReIM Release 15.0 is supported for use with the following version of Oracle Fusion Middleware:
Oracle Fusion Middleware 12c (12.1.3)
The integration enhancement described below is included in this release:
The integration option that sends all transactions to the IM_FINACIALS_STAGE has been decommissioned. The IM_FINACIALS_STAGE table continues to be used as part of the remaining integration, which sends transactions expected to be sent to G/L system to IM_FINANCIALS_STAGE and documents expected to be sent to A/P system to IM_AP_STAGE_HEAD and IM_AP_STAGE_DETAIL.
The following features have been decommissioned in this release of ReIM:
Parent Invoices
The ability to match documents above the PO/location level removes the need for Parent Invoices.
Group Entry
A Single Invoice entry's 'save and add another' feature provides the ability to quickly enter header only invoices.
Receipt Write Off History Screen
A screen showing receipts that have been written-off.
Discrepancy Purge Batch Job
Changes in the Automatch design and discrepancy resolution process remove the need for this batch job.
Disputed Credit Memo Action Rollup
The redesigned Debit Memo reversal process removes the need for this batch job.
The following functionality is currently not included in the ReIM 15.0 Release:
G/L Cross-reference User Interface
G/L Options User Interface
Dynamic Segments User Interface
Reason Codes User Interface
|
Note: The ReIM application continues to require data for G/L Cross-reference, G/L Options, Dynamic Segments, and Reason Codes to be set up in the database. See the System Configuration chapter of the Oracle Retail Invoice Matching Operations Guide for instructions related to manual data setup. |
The known issues below remain in this release.
| Known Issue/Defect | Defect Number |
|---|---|
| When users access the application through Internet Explorer, the Detail Match screen locks up if it is called from Discrepancy Review List in Detached Mode. | ReIM number: 21954330
ADF number: 21466264 |
| Hidden and visible columns may overlap in the Manage Columns and Reorder Columns pop up area, if the length of the column description is greater than 20 characters. This is an open ADF issue in the current version of ADF. | ADF number: 21156449 |
| Operational Insights – I18n and Accessibility parameters are not being passed successfully to the Operational Insights OBIEE dashboard reports embedded in the ADF applications. The resulting dashboards do not conform to any specific language or accessibility settings that the application user may have defined. This is an open issue in the current version (11.1.1.9) of OBIEE. | OBIEE Bug number: 21866582 |
For more information, see the following documents:
Oracle Retail Invoice Matching User Guide
Oracle Retail Invoice Matching Operations Guide
Oracle Retail Invoice Matching Installation Guide
Oracle Retail Invoice Matching Data Model
Oracle Retail Merchandising Security Guide
Oracle Retail Merchandising Implementation Guide
Oracle Retail Merchandising Batch Schedule
Oracle Retail Operational Insights User Guide
The following documents are available through My Oracle Support. Access My Oracle Support at the following URL:
This guide describes the approach that each Oracle Retail Merchandising Operations Management application takes for the upgrading process, as well as its upgrade assumptions and considerations. Actual procedures for the upgrade may be included in the application's Installation Guide.
The tests in this document have been created to assist in verifying (smoke testing) that the installation of the following products was successful: RMS, ReSA, RTM, Oracle Retail Allocation, ReIM, ARI, and RPM. These tests are not intended to verify all functionality in the suite of products previously listed.
The following document is available on the My Oracle Support Web site. Access MyOracle Support at the following URL:
Online training is available to Oracle supported customers at product release. These online courses provide release-specific product knowledge that enables your functional and technical teams to plan, implement and/or upgrade and support Oracle Retail applications effectively and efficiently.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle® Retail Invoice Matching Release Notes, Release 15.0
E69594-01
Copyright © 2015,C:\Program Files\Adobe\AdobeFrameMaker10\Templates\Oracle\TEMLS\xml\insets\holder_ak.xml
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 is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.
Value-Added Reseller (VAR) Language
Oracle Retail VAR Applications
The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include:
(i) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation (MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.
(ii) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of Kirkland, Washington, to Oracle and imbedded in Oracle Retail Mobile Store Inventory Management.
(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.
(iv) the software component known as Adobe Flex™ licensed by Adobe Systems Incorporated of San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization application.
You acknowledge and confirm that Oracle grants you use of only the object code of the VAR Applications. Oracle will not deliver source code to the VAR Applications to you. Notwithstanding any other term or condition of the agreement and this ordering document, you shall not cause or permit alteration of any VAR Applications. For purposes of this section, "alteration" refers to all alterations, translations, upgrades, enhancements, customizations or modifications of all or any portion of the VAR Applications including all reconfigurations, reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or confidential information of the VAR Applications for purposes of competitive discovery.
The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to replace, with functional equivalent software, any of the VAR Applications in future releases of the applicable program.
