| Oracle® Retail Invoice Matching Release Notes Release 13.2.9 E73282-02 |
|
 Previous |
Release Notes
Release 13.2.9
E73282-02
March 2016
Oracle Retail Invoice Matching (ReIM) Release 13.2.9 is a patch release for ReIM 13.2. ReIM 13.2.9 includes selected defect fixes and enhancements for ReIM 13.2 code.
Oracle Customer Support investigates submitted issues assuming that all released updates have been applied. It is the customer's decision when to apply a new release; however, delays in applying updates can complicate the support process.
Oracle Retail patch releases are periodic releases that can include new defect fixes and product enhancements.
Documentation for patch releases includes the following:
New and updated guides (for example, operations and user guides) that apply to the patch release level. See "Related Documentation" for a list of the documents published for ReIM 13.2.9.
Defect reports for new fixes and enhancements for the patch release.
See the Oracle Retail Invoice Matching Installation Guide, Release 13.2.9 for information about the following:
Hardware and software requirements
Oracle Retail application software compatibility
Before applying the ReIM 13.2.9 patch release, be sure that:
ReIM 13.2 has been installed
Patch release ReIM 13.2.8 has been applied
Before applying the patch release over your files:
Note whether any modules have been customized. If so, the customizations must be reapplied to the new version of the module, or the fix may need to be applied to the custom version of the code.
Copy the original files to a different directory before you copy over them, in case you need to refer to them at a later date.
Back up data before running any script, because the scripts provided do not preserve data. See defect reports for details.
Check with your database administrator to determine whether your database should be analyzed after a script is run. In many cases, analysis of the database is necessary to take advantage of new or modified indexes intended to improve performance of the application.
This section addresses the technical enhancements included in Oracle Retail Invoice Matching Release 13.2.9.
|
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. |
Oracle Retail Invoice Matching Release 13.2.9 is supported for use with the following database server:
Oracle Database Enterprise Edition 12cR1 (12.1.0.2)
A defect fix is a modification to the base Oracle Retail code (for example, a bug fix, a performance enhancement, or a functional enhancement). Each defect fix that is included in this release has a corresponding defect report titled <defect-number>.PDF (for example, 12345678.PDF).
In the same folder, the file named DEFECT MODULE XREF ReIM 13.2.9.XLS lists every defect number and the modules and scripts that are included in this release. Review each defect report carefully before implementing the defect fixes. Note that scripts do not preserve data. Make sure that all data is backed up before you run any script.
The following defect fixes and enhancements are included in ReIM 13.2.9. This is not a complete list; see the cross-reference spreadsheet and defect reports for a complete list and full details.
Table 1 Noteworthy Defect Fixes
| Defect Number | Summary |
|---|---|
|
21550621 |
An Invoice for which a tax discrepancy is already resolved. If the invoice details are opened in edit/view mode without changing any tax details, it is observed that the invoices are moving to the TAXDIS status again. |
|
21240950 |
After providing the reason codes for credit memo items an error message is displayed on saving. The message displays that the resolution could not be saved, but the underlying table is updated. |
|
21195255 |
Invoice is not getting matches for Receipts from different Locations and Cost discrepancy. |
|
20652230 |
When the data is saved into the database the application throws the following error when creating Credit Note Request. |
|
20181418 |
In the ReIM application, the find calculation of the PRIM_TRANS_AMOUNT column in IM_FINANCIALS_STAGE is incorrect. |
|
18613170 |
In the ReIM application, when you upload an EDI file with Croatian special characters an error is displayed. |
|
21468875 |
Invoice with 30 Cyrillic characters displayed an error during posting. Patch from 3-10653070881 was deployed in the testing environment. |
|
21237903 |
The font size is changing in Summary Match window in the ReIM application. |
|
20739281 |
After a matching and posting is done for prepaid invoices, the DOC_DATE in IM_FINANACIAL_STAGE table is the DOC_DATE from the IM_DOC_HEAD, which is incorrect, and it should be MATCH_DATE from IM_DOC_HEAD (for VDATE the date matching is performed). |
|
20643751 |
The REIMPOSTING batch file has a poor performance and it is consuming up to 6-7 hours to process 300-400 Invoices, which is not expected. |
|
21193324 |
COMPLEXDEALUPLOAD batch fails with a deadlock error. |
|
20981385 |
Search for a PO that is in closed status, with its receipt in U (Unmatched) or I (Input) status. Attempt to resolve a cost or quantity discrepancy for that PO. The error Invalid ID is displayed on the Cost Review Find and Quantity Review Find pages. |
|
20806217 |
For closed orders, the Order lookup is returning invalid id in Cost Review search. |
|
20770727 |
All documents, which are manually created, should be editable. However, the Non Merchandise Invoices which are manually created are missing in the list. |
|
21555755 |
The Invoices are not posted due to partially matched receipts which are causing an issue when matched with RCA (Receiver Cost Adjustment). |
|
20815339 |
In the ReIM application, the Debit Memo in the posted statuses can be deleted. |
|
20741033 |
When the AUTOMATCH batch attempts to detail a match to an invoice receipt which has the same item shipped in multiple cartons, the QUANTITY_MATCHED in SHIPSKU table is not updated correctly. |
|
20675054 |
The Bug 20454469 works only for suppliers. It does not work for other vendor types like Partners etc. |
|
20631871 |
SHIPSKU QTY_MATCHED is updated to a negative value on deleting an invoice from the ReIM window. |
|
21552767 |
When CRDMEQ is created as a resolution action of CRDNT and CRDNRQ QTY there is a discrepancy in the ADJUSTED_UNIT_COST. |
|
21220774 |
When RUA is performed from the ReIM application for a mass class item, the ReIM application rounds up the adjustment value to 0 decimal. |
|
21696632 |
In the ReIM application there is a performance issue with the 'Default from Receipts' option. |
|
21459556 |
RCA is not functioning as expected from the RMS application to the ReIM application. The Summary Match List is displaying the Unmatched Quantity incorrectly. |
|
21215680 |
In the ReIM application, the ORDER NUMBER field in the Group entry is disabled for credit notes. |
|
20963215 |
The Invoice ID (ext_doc_id) is changed when the invoice is posted. |
|
20948682 |
In the ReIM application, the Available Quantity is displaying the complete Quantity as the Available Quantity. Also the Variance calculation in the Auto Summary Match invoice frame is not correctly displayed. |
|
20574432 |
An incorrect PO detail is displayed in the Invoice Maintenance Detail window. |
|
20349994 |
Incorrect Debit Memo amount is sent to AP from the ReIM application. |
|
22279056 |
The receipt is not visible in the Receipts Unmatched section, only the invoice is visible in Invoice Unmatched section. |
|
22134838 |
While editing a non-merchandise invoice for Partner Tax, the Tax Breakdown window is displayed as blank. |
|
22134088 |
The CANCEL button and the TERMS field are disabled after modifying the non-merchandise invoice. |
|
22101939 |
The VWT posting to financials is 1020 and debit memo is generated for 2500. The debit memo is picking the Order Cost in place of Invoice Cost. |
|
22390188 |
There is an incorrect Vendor Type for non-merchandise fixed deal for partner. |
|
22522022 |
After clicking on the Pay Invoice it should allow you to perform Prepay Processing without any error. |
|
22390056 |
The Posting batch displays an error and the data is not populating in the posting tables. |
|
22390004 |
The REIMRECEIPTWRITEOFF posting data is not populating in the IM_FINANCIALS_STAGE table. |
|
22273918 |
The CNRC in Match Status is getting deleted. |
For more information, see the following documents:
Oracle Retail Invoice Matching Installation Guide
Oracle Retail Invoice Matching Operations Guide
Oracle Retail Invoice Matching Data Model
Oracle Retail Merchandising Batch Schedule
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 13.2.9
E73282-02
Copyright © 2016,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.
