Oracle® Retail Merchandising System
Release Notes
Release 13.2.9
E62000-01
March 2016
Oracle Retail Merchandising System (RMS) Release 13.2.9 is a patch release for RMS 13.2. RMS 13.2.9 includes selected defect fixes and enhancements for RMS 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.
This document contains the following topics:
n Overview
n About Patch Releases
n Hardware and Software Requirements
n Applying the Patch Release
n Functional Enhancements
n Integration Enhancements
n Technical Enhancements
n Running Scripts
n RMS Defect Fixes and Documentation
n RMS Noteworthy Defect Fixes
n RMS Known Issue
n RMS Related Documentation
n Brazil Localization and Oracle Retail Fiscal Management
n Documentation Accessibility
Overview
Oracle Retail Merchandising System (RMS) is used to execute core merchandising activities, including merchandise management, inventory replenishment, purchasing, vendor management, and financial tracking.
Oracle Retail Sales Audit (ReSA) provides the tools to evaluate point-of-sale data to ensure the accuracy and completeness of information exported to downstream systems used in optimization processes, financial reporting, and analysis.
RMS Localized for Brazil
The Oracle Retail Fiscal Management (ORFM) module is an optional module for RMS 13.2 to support Brazil localization and the particular tax requirements of Brazil. For more information, see Brazil Localization and Oracle Retail Fiscal Management later in this document.
About Patch Releases
Oracle Retail patch releases are periodic releases that can include the following:
n New defect fixes
n Product enhancements
n Technical upgrades
Documentation for patch releases includes the following:
n New and updated guides (for example, operations and user guides) that apply to the patch release level. See RMS Related Documentation for a list of the documents published for RMS 13.2.9.
n Defect reports for new fixes and enhancements for the patch release.
|
Note Customers must apply the entire patch release to update their installation to the currently supported level. |
See the Oracle Retail Merchandising System Installation Guide for Release 13.2.9 for instructions about how to apply the defect fixes and enhancements that you have not already applied.
Hardware and Software Requirements
See the Oracle Retail Merchandising Installation Guide for additional information about the following:
n Hardware and software requirements
n Oracle Retail application software compatibility
Applying the Patch Release
Before applying the RMS 13.2.9 patch release, be sure that:
n RMS 13.2 has been installed.
n Patch releases RMS 13.2.1 through 13.2.8 have been applied.
Before applying the new files over your code:
n 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.
n 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.
Functional Enhancements
The following functional enhancements are included in Oracle Retail Merchandising System Release 13.2.9:
|
Defect |
Description |
|
19453394 |
During item creation, a duplicate check is performed against the numeric form of the item. This enhancement introduces a new API, which can call out custom functions stored on a table dynamically based on the function key passed by the base RMS functions. Necessary infrastructure is built to pass the standard input to the custom functions and place holders for error messages so that the custom function can return exceptions to the base RMS code. As part of this enhancement, custom API calls are placed where item approvals take place (UI and XITEM). This means that you can now introduce customized item approval check functions and register them on the table. When the functions are registered, the custom API that we have introduced is called dynamically and additional validations are performed. The API handles the exceptions generated by the custom code and reports/logs them in an appropriate manner. |
|
14770250 |
Tax at header level in ReSA is not recognized by the transaction detail form (SATRDETL). This enhancement primarily deals with the reintroduction of transaction level tax. Currently, the RTLOG that originates from an external system like POS with the transaction level tax not supported by RESA. With this enhancement, the TTAX (Transaction Level Tax) is consumed and processed by RESA along with the existing Item Level Tax (IGTAX). The store that sends the RTLOG can either support TTAX or IGTAX but not both. Updates to the existing files that are generated by the PRO*C batch and tax level for the store are added. The TTAX record is consumed by RESA. The transaction detail form (SATRDETL) is enabled with the TAX tab that describes the transaction level tax details. This TAX tab is enabled or disabled based on the store setup to handle either the TTAX or IGTAX respectively. |
Integration Enhancements
The following integration enhancements are included in Oracle Retail Merchandising System Release 13.2.9:
|
Defect |
Description |
|
16781629 |
Update the WEIGHT FOR CATCH and WEIGHT SIMPLE PACK ITEM. The receiving process of catch weight items is updated to allow the default weight on such receipts from ASN, when they are not captured during the receiving process and to allow the weight only adjustments on the catch weight receipts. |
|
18339776 |
Add fields in the item integration used by RWMS. As part of the basic integration of item information between RMS and RWMS, the RMS sends the UOM conversion factor to the catch weight indicator, case pack size, case dimensions and other key attributes of the item. For catch weight items, an issue exists in both systems interpreting this data differently when the standard UOM for the item is not EACH which relates specifically to types 1 and 2 catch weight items. This is primarily because the pack size (or pack quantity for simple packs) of the item sent by RMS represents a weight for these items, not a unit quantity. To address this issue, new fields (CASE_PACK_SIZE_UNITS, INNER_PACK_SIZE_UNITS, PALLET_PACK_SIZE_UNITS and UNIT_WEIGHT at supplier country level and PACK_ITEM_QTY_UNITS at BOM level) are added and are sent to RWMS for accurate UOM conversion. |
Technical Enhancements
This section addresses the technical enhancements included in Oracle Retail Merchandising System Release 13.2.9.
|
Defect |
Description |
|
20551246 |
LIKESTORE issues when using a LIKESTORE with a large number of items. When you create a new store in RMS, you can specify a LIKE store. A LIKESTORE serves as a template from which the new store is created. The LIKESTORE batch is part of a sequence of batch programs that are executed to ensure that a new store is successfully created in RMS when using the LIKESTORE option. When the STOREADD batch is executed, it sets the STORE OPENDATE and closes the date of all the LIKE stores far in the future, so that those records are considered during a LIKESTORE batch run. The LIKESTORE batch then creates ITEM-LOCATION relationships for all the items in the existing store with new store (row by row). The LIKESTORE batch processes like stores, sets the store open, and closes dates back to original date in the post process. You can specify whether to copy the replenishment information, delivery schedules, and activity schedules from the existing store, and which is copied in the LIKESTORE post process. It is necessary to run the STOREADD, LIKESTORE, and LIKESTORE POST in the same order, to successfully add all the stores to RMS. The LIKESTORE batch executes for a long time because it processes the new ITEM LOC CREATION row by row. The batch is threaded by DEPT, since it calls the new ITEM LOC function row by row. |
|
20666051 |
PLSQL logger implementation. A new Oracle utility PLSQL Logger (http://tylermuth.wordpress.com/2009/11/03/logger-a-plsql-logging-and-debugging-utility) is installed in all RMS13.2 development environments. It is simple to use, provides a good stack trace, and can turn on/off logging based on different logging levels. |
|
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. |
Database Server Support
Oracle Retail Merchandising System Release 13.2.9 is now certified for use with the following database server:
n Oracle Database Release 12.1.0.2
Browser Support
Oracle Retail Merchandising System Release 13.2.9 is now certified for use with the following browser:
n Mozilla Firefox ESR 31+
Oracle Access Manager (OAM) Security Stack
Oracle Retail Merchandising System Release 13.2.9 is now certified for use with Oracle Access Manager (OAM) 11.1.2.3.
Oracle WebGate Security Stack
Oracle Retail Merchandising System Release 13.2.9 is now certified for use with Oracle WebGate 11.1.2.3.
Oracle HTTP Server Security Stack
Oracle Retail Merchandising System Release 13.2.9 is now certified for use with Oracle HTTP Server 11.1.1.9.
Oracle Internet Directory (OID) Security Stack
Oracle Retail Merchandising System Release 13.2.9 is now certified for use with Oracle Internet Directory (OID) 11.1.1.9.
Java Support
The client of Oracle Retail Merchandising System Release 13.2.9 is certified for use with the following Java versions:
n Oracle Java 7 update 80
n Oracle Java 8 update 65
Running Scripts
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, an analysis of the database is necessary to take advantage of new or modified indexes intended to improve performance of the application.
RMS Defect Fixes and Documentation
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 patch has a corresponding defect report titled <defect-number>.PDF (for example, 1234567.PDF) that is posted to My Oracle Support at the following location: Oracle Retail Defect Document Listings (MOS ID:2021275.1).
In the same folder, the file named DEFECT MODULE XREF RMS 13.2.9.XLS lists every defect number and the modules and scripts that are included in the patch. 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.
RMS Noteworthy Defect Fixes
The following RMS noteworthy defects are fixed in this release:
|
Defect |
Description |
|
18014230 |
STAGE_COMPLEX_DEAL_DETAIL.ACTUAL_TURNOVER_UNITS returns a null value after executing VENDINVC. |
|
18342085 |
The Transfer Order is created from the replenishment even if the receiving store is closed. |
|
19361958 |
There is a different logic for AVAILABLE QTY calculation in TSF & RTV when the NON_SELLABLE_QTY is a negative value. |
|
19261502 |
When creating a new store using LIKESTORE and CHANGING COST for an item, the unit cost in the ITEM_SUPP_COUNTRY_LOC is different from the ORIGINAL STORE COST. |
|
19703270 |
There is a calculation issue for the Off-invoice deal buy/get (recursive). |
|
19206181 |
When having an item parent (status worksheet) with several item children (from ITEMCHILDREN) all have the same cost price by default inherited from the parent item (from ITEMSUPPCTRY). |
|
19940923 |
Incorrect cost prices for negative stock adjustments. |
|
19171429 |
The received Order Quantity is not distributed correctly based on the approved allocations. |
|
20100004 |
The reclassified item is not populated by the deal on MERCH_LEVEL = 6. |
RMS Known Issue
The following known issue exists in this release:
n If you are using Internet Explorer 11, Oracle Retail recommends that you install the 32 bit version of JRE 1.8 on the client system. RMS may not work if the 64 bit version of JRE 1.8 is installed on the client system.
RMS Related Documentation
For more information, see the following documents in the Oracle Retail Merchandising System release 13.2.9 documentation set:
n Oracle Retail Merchandising System Installation Guide
n Oracle Retail Merchandising System Operations Guide
n Oracle Retail Merchandising System Data Model
n Oracle Retail Merchandising System Batch Schedule
Brazil Localization and Oracle Retail Fiscal Management
|
Note This section of the Release Notes applies only if you have localized RMS for Brazil operations by installing the Oracle Retail Fiscal Management (ORFM) module. |
Release History
Oracle Retail Fiscal Management is an optional module of the RMS application. Not all RMS patches include ORFM updates.
n The last available release of ORFM is Release 13.2.8.
ORFM Noteworthy Defect Fixes
The following ORFM noteworthy defects are fixed in this release:
|
Defect |
Description |
|
18900354 |
When you import the NF using the EDI NF tables, the FMEDINF batch matches the classification of the item in NF with classification registered in RMS. The batch should make all checks for all items at the same time and report all errors, not one by one. |
|
19224975 |
The RMS Receiving functionality consumes RIB messages slowly. |
|
19246636 |
The POS_MODS_TAX_INFO table has duplicated information of PACK PER TAX and the NCM_CODE is null. |
|
19261144 |
The PERC_MVA and VLR_BASE_REDU_ICMSST fields are blank when you choose the Nota Fiscal in the discrepancy resolution. |
|
19277882 |
The ORFM_FISCAL_HEADER BLOCK: B_FM_FFNF_TAX_DETAIL_EXT is not navigable. |
|
19337637 |
When you receive the transfer in the ORFM application, the ENTRY_OR_EXIT_DATE field does not update to the date when the product was received. |
|
19597667 |
The ORFM application incorrectly updates the values for the PIS tax when receiving a Purchase Order. |
|
19636777 |
Remove the SUFRAMA validation code from L10N_BR_S_FND_SQL.CHK_SUPS_ENT. |
|
19637694 |
The NFE ACESS KEY field is mandatory for NF Complementary when the ModeType is equal to Entrada, the Document Type is equal to 55, and the Utilization issue is different from Emissao. |
|
19788600 |
When you issue one NF from one location that has a substitute state inscription in the destinations state, the substitute state inscriptions does not appear in the Nota Fiscal. |
|
19796399 |
The EX_IPI flag is not sent to the 'TAXWEB' to validate as it does not exist in RTIL log. |
|
19796937 |
When the language taken from the USER_ATTRIBUTE table is different from the primary language taken from the SYSTEM_OPTIONS table, it displays an RTK_KEY = MISSING_CODE error. |
|
19805962 |
The NF total does not match the sum of detail and ST. |
|
19847622 |
RFM-NF generation does not follow a sequential order. |
|
19925498 |
An error occurs when the SPED process batch file is executed. |
|
19987610 |
While entering the NF Complementary for Cost Tax Correction, the CST DETAIL field is not available to input any data. |
|
20090008 |
The NF should not be updated after it moves to the FP status. |
|
20121041 |
Review code dependencies for svcprov_cotsfb.pls file. |
|
20262612 |
An error occurs when you validate an item with ST in TSF creation. |
|
20370245 |
Unable to execute FM_NFE_PUB_SQL.GET_NFE_INFO for RTV. |
|
20370719 |
Field INDIEDEST is not fulfilled when trying to issue a regular TSF outbound. |
|
20461160 |
Issues with existing database scripts. |
|
20610832 |
When the RMA NF is in the error status, the scheduled status goes to CN. |
|
20720545 |
When a supplier is created using the Web service, you encounter an SUPPLIERSERVICE.WSDL error message. |
|
20738860 |
RIB_RECEIPTDTL_REC has an invalid length. |
|
20898363 |
Incorrect breakout of NF_MAX_ITEM. |
|
20963317 |
Appropriate RFM postings do not happen for Inventory Adjustment NF. |
|
20965790 |
RMA NF displays a "This document already exists" error message. |
|
21033608 |
When running the batch import_SPED.ksh, the C_GET_SPED_REC cursor is not closed and the function FM_SPED_HEADER fails in the package FM_SPED_SQL. |
|
21443588 |
The C_GET_CUSTNF_INFO cursor encounters errors. |
|
21553533 |
When a fiscal document (NF) is generated for stock adjustment, the value posted for TOTAL_COST is incorrect against TRAN CODE 22. |
|
21621932 |
ICMS postponing by configuring RTIL and testing the integration with TaxWeb. |
|
20102827 |
Update .dat files to include several objects. |
|
21621932 |
ICMS postponing for RTIL and TaxWeb. |
|
20949165 |
The GTAX_ITEM_ROLLUP table has zero values when you add all stores to the item. |
|
21972447 |
The STMAIN batch fails with a generic stored procedure error. |
|
18503078 |
Creating items from existing items does not copy the POS taxes correctly. |
|
19191903 |
When you create a triangulation PO and run an RTV stub with this triangulation PO as a reference, it fails with an error. |
|
19390626 |
The unit cost of an item is only updated in item_supp_country and not in the item_supp_country_loc. |
|
19544543 |
The ORDTXBRK form does not bring up the item/tax information when the item is cancelled. |
|
20949438 |
The initial markup is not calculated correctly on item creation. |
ORFM Related Documentation
For more information, see the following documents in the Oracle Retail Fiscal Management Release 13.2.9 documentation set:
n Oracle Retail Fiscal Management and Brazil Localization Installation Guide
Documentation Accessibility
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 Merchandising System, Release 13.2.9
E62000-01
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
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.
Licensing Note: This media pack includes a Restricted Use license for Oracle Retail Predictive Application Server (RPAS) - Enterprise Engine to support Oracle® Retail Analytic Parameter Calculator for Regular Price Optimization only.
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.