Oracle Retail Integration Bus Release Notes Release 12.0.1 October 2006
Oracle Retail Integration Bus Release Notes, Release 12.0.1 Copyright 2006, Oracle. All rights reserved. Primary Author: Randy Kapelke The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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 agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065 The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, thirdparty Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
Preface A Release Notes document can include some or all of the following sections, depending upon the release: Overview of the release Functional, technical, integration, and/or performance enhancements Assumptions Fixed and/or known issues/defects Because of their brevity, Release Notes do not include chapters, appendices, or a table of contents. Audience Release Notes are a critical communication link between Oracle Retail and its retailer clients. There are four audiences in general for whom a Release Notes document is written: Retail clients who wish to understand the contents of this release. Integrators and implementation staff who have the overall responsibility for implementing Oracle Retail Integration Bus (RIB) into their enterprise. Business analysts who are looking for high-level functional information about this release. System analysts and system operation personnel who are looking for high-level functional and technical content related to this release. Related Documents Customer Support For more information, see the following documents in the Oracle Retail Integration Bus Release 12.0.1 documentation set: Oracle Retail Integration Bus Installation Guide Oracle Retail Integration Bus Operations Guide Oracle Retail Integration Bus Integration Guide https://metalink.oracle.com When contacting Customer Support, please provide: Product version and program/module name. Functional and technical description of the problem (include business impact). Detailed step-by-step instructions to recreate. Exact error message received. Screen shots of each step you take. iii
Conventions Navigate: This is a navigate statement. It tells you how to get to the start of the procedure and ends with a screen shot of the starting point and the statement the Window Name window opens. Note: This is a note. It is used to call out information that is important, but not necessarily part of the procedure. This is a code sample It is used to display examples of code A hyperlink appears like this.
Release Notes Overview This document contains information on the changes that have been made to RIB since the previous release. RIB Infrastructure Package Summary Note: Oracle Retail strongly recommends that before any installation or development work is performed, the RIB 12.0.1 Installation Guide, provided with the release, is read and followed cover to cover. In addition, the RIB 12.0.1 Known Issues section below must be read and understood. Finally, users should take care to complete all certifications and regression/volume testing with RIB 12.0.1 before deployment begins to production environments. RIB infrastructure package name ribcommon1201_eng_ga.tar ribobjects1201_eng_ga.tar riha1201_eng_ga.tar rdmt1201_eng_ga.tar Description/contents Common infrastructure code for all RIB applications. Contains the message payloads and definitions (RIB Objects) for the RIB. Contains the Oracle Retail Integration Hospital Administrator (RIHA). Contains the RIB Diagnostics and Monitoring Toolkit. Release Notes 1
RIB Application Package Summary RIB Application Package Summary RIB application PAKs adhere to the following naming convention: Common name: RIBPak<RIB Highest Version>for<Application name><application Minimum version supported,> For example, RIBPak1201forRMS1201 is the RIB 12.0.1 PAK for RMS 12.0.1. The format for application Minimum version would be X.XX.XXX, where the X denotes MAJOR version, XX denotes MINOR version, and XXX would indicate PATCH/MINOR MINOR version. Packaging filename: ribpak<rib Highest version>for<application name><application Minimum version supported>_<language>_ga.tar For example, ribpak1201forrms1201_eng_ga.tar is the RIB 12.0.1 PAK for RMS 12.0.1 Note: Application PAKs may be released independently of the RIB infrastructure releases. Please see the section, Certification Matrices, below for more information as to when certain application PAKs may be available on a generally available (GA) basis for a specific application. In the event that a GA Application PAK is not released as part of a GA RIB release and is not listed in the Certification Matrices below as part of a planned Application PAK release in the future, contact Oracle Customer Support in order to obtain this PAK. RIB Application PAK name RIB PAK file name Description/contents RIBPak1201forRMS1201 ribpak1201forrms1201_eng_ga.tar The publishers, subscribers, and TAFRs to enable connectivity of RIB 12.0.1 to RMS 12.0.1. RIBPak1201forRWMS1201 ribpak1201forrwms1201_eng_ga.tar The publishers, subscribers, and TAFRs to enable connectivity of RIB 12.0.1 to RWMS 12.0.1. RIBPak1201forRPM1201 ribpak1201forrpm1201_eng_ga.tar The Enterprise Archive Resource (EAR) and associated files to enable connectivity of RIB 12.0.1 to RPM 12.0.1. RIBPak1201forISO1111 ribpak1201forsim1111_eng_ga.tar The publishers, subscribers, and TAFRs to enable connectivity of RIB12.0.1 to SIM 11.1.1 2 Oracle Retail Integration Bus
Certification Matrices Certification Matrices Oracle Retail Applications Certification Matrix The following is a list of Oracle Retail products certified with the RIB 12.0.1 release. Oracle Retail application Oracle Retail application version RIB last tested date RIB last tested version Comments + tested/supported combinations Oracle Retail Merchandising System (RMS) Oracle Retail Warehouse Management Systems (RWMS) Oracle Retail Price Management (RPM) 12.0.1 5/05/2006 RIB 12.0.1 Tested/Supported with the following combination: RMS 12.0.1, RPM 12.0.1, RWMS 12.0.1 using RIB 12.0.1 12.0.1 5/05/2006 RIB 12.0.1 Tested/Supported with the following combination: RMS 12.0.1, RPM 12.0.1, RWMS 12.0.1 using RIB 12.0.1 12.0.1 5/05/2006 RIB 12.0.1 Tested/Supported with the following combination: RMS 12.0.1, RPM 12.0.1, RWMS 12.0.1 using RIB 12.0.1 Note: Read each application s release documentation in its entirety before beginning any application s installation. Release Notes 3
Certification Matrices Third-party Products Certification Matrix The following is a list of third-party products, platforms, or components certified with recent RIB 12.0.1 release: Third-party product, platform, or component Third-party product, platform, or component version RIB last tested date RIB last tested version Comments SeeBeyond egate 5.0.5 5/05/2006 RIB 12.0.1 For the RIB 12.0.1 release, an upgrade to SeeBeyond egate 5.0.5 is required. Please see the SeeBeyond egate 5.0.5 release documentation for details. SeeBeyond has released required ESRs supplementing the SeeBeyond egate 5.0.5 release. The details of each ESR are fully expressed in the ESR Read Me files. # 95734 This ESR provides an installation for UNIX and Windows to update the Java Runtime Environment (JRE) from 1.3.1 to 1.4. The ESR includes the JRE for each platform. Oracle 10g Release 2 5/05/2006 RIB 12.0.1 Solaris 9 5/05/2006 RIB 12.0.1 HP-UX 11.11 5/05/2006 RIB 12.0.1 AIX 5.3 5/05/2006 RIB 12.0.1 MS Windows Java Runtime Environment (JRE) Jakarta Tomcat Internet Explorer 2000/XP N/A N/A This release is required for the SeeBeyond GUI components. 1.4.2_07 5/05/2006 RIB 12.0.1 The minimum required version for the RIB 12.0.1 infrastructure and Oracle Retail Integration Hospital Administrator is the JRE 1.4.2_07. N/A N/A N/A RIB DTDs should be made networkaccessible for the Oracle Retail Integration Hospital Administrator (RIHA). 6.0 N/A N/A The RIB 12.0.1 release is recommended for use with Windows 2000/XP and Internet Explorer 6.0 or higher releases. The installation of the SeeBeyond e*gate product requires the Microsoft platform. Complete platform details can be found in the SeeBeyond e*gate Integrator Installation Guide. 4 Oracle Retail Integration Bus
RIB 12.0.1 Known Issues RIB 12.0.1 Known Issues Infrastructure Known Issues Internal Bug Number SeeBeyond JDBC Driver installation post-installation steps MQC#1435 MQC#1474 MQC#1476 MQC#1478 MQC#1486 MQC#1490 Description SeeBeyond comes with JDBC 9.2.0.1, but must use 10.2.0.1. This upgrade must be done manually during the installation process. rib-tafr install directory and configuration files ewalloctostockorderfromrib map two extra fields ewtransferstostockorderfromri B map expidite_flag from TsfDtl to SODtl j2ee ribinstall.sh fails some of the time in shutting down the oc4j instance. In CogsDesc change fields header_media & line_media to number (5) Allocations stuck on the RWMS side RIB table due to an SQL Exception. Mitigation/workaround See the RIB Installation Guide for detailed instructions. This issue is being actively addressed in development. This issue is being actively addressed in development. This issue is being actively addressed in development. This issue is being actively addressed in development. This issue is being actively addressed in development. This issue is being actively addressed in development. Release Notes 5
Changes Since RIB 12.0 Documentation Known Issue Issue title Description Mitigation/workaround Integration Guide and SIM mapping reports The RIB 12.0.1 Integration Guide does not contain the Oracle Retail Store Inventory Management (SIM) mapping reports. The document does contain the functional overviews related to SIM. This issue is being actively addressed in development. Changes Since RIB 12.0 Functional/Infrastructure Changes Internal Bug Number MQC#1450 MQC#1451 MQC#1454 MQC#1473 MQC#1478 Description ALL PAKS RWMS/RMS New version of OracleConnectionUtil.java, to be applied to RIB versions 11.0.1 and 11.1 Ressurect deleted DiffTypes as deleted in MQC #1353 Add superclass to castor jarfiles Add two fields to AllocDtl j2ee ribinstall.sh fails some of the time in shutting down the oc4j instance. Notes The ASN In (856) Interface no longer supports the conversion from EDI file to RIB Payload (XML) format. Retailers are required, using their EDI translation software, to translate incoming ASN In (856) EDI transactions to the ASNin Message Type (ASNInCre, ASNinMod, ASNInDel). Functionality has not yet been added to RWMS to fully support the multi-level distribution (MLD) functionality previously added to Oracle Retail Allocation. Thus, RIBForRWMS does not support this functionality as well. Once implemented, an Oracle Retail Allocation user is able to allocate a distribution center (DC) to DC shipment prior to receipt in the second DC. This functionality causes the merchandise to move as a cross-dock shipment directly to the store from within that second DC. This capability to be integrated with the RWMS receiving modules is actively being addressed by development. This change does not require any change in the RIB, and thus does not require a RIB upgrade. Uses OracleConnectionUtil. 6 Oracle Retail Integration Bus
Changes Since RIB 12.0 Application PAK Changes Internal Bug Number Description Notes MQC#1409 MQC#1410 MQC#1465 MQC#1466 MQC#1467 MQC#1481 MQC#1483 MQC#1485 MQC#1487 'WHEquipClsDesc, WHEquipDesc, WHEquipClsRef, WHEquipRef - correct field order 'LocPODlsRspDesc - xmlschema correction RIBCONTAINER.XML INCORRECTLY SETS JVM HEAP SIZE Change APPROVAL_ID to varchar2(30) in TsfDesc.xsd and SODesc.xsd Fix error in attempt to log a error message. RIB tafr coltranserstostockorderfrom RIB does not transform the comments field to topic etstockorderiso. StockOrderISO TAFR drops NOT AFTER DATE on transfers going from RMS to SIM (ENTERPRISEBUG#114) Change message from varchar2300 to 22000 in SODesc. Add allocdel to RIB_TYPE_SETTINGS in all_rib_table_values.sql. LocPODlsRspDesc xml-schema is invalid. Corrected case of type variables. In the RIBforSIM 12.0.1 release ribpak1201forsim1111_eng_082306.tar, the RIB1201/RIBforISO/iso/files/prod/tuning/RIB Container.xml file sets the JVM heap size using equals characters instead of minus characters. When RIB tafr coltranserstostockorderfromrib transform message from top ettransfersfromrms to etstockorderiso, the comment which is stored on message attribute is not transferred to the new topic etstockorderiso. When this message gets to SIM, the comment are not included, and SIM has a requirement to see comments. The RIB must modify tafr coltranserstostockorderfromrib to include the message (comments) from the original message. This issue arises when, in RMS, a user uses the Mass Return Transfer to create a transfer from store to warehouse with the NOT AFTER DATE field populated, approves this transfer and sends to SIM. The transfer goes through TransferFromRMS and TransfersToStockOrderFromRIB then to StockOrderISO. When the message reaches SIM, the NOT AFTER DATE field is missing in SIM. The XML message as the message goes through reveals that from the StockOrderFromRIB topic to StockOrderISO topic, the NOT AFTER DATE field is dropped. Change message from varchar2300 to 22000 in SODesc. Add allocdel to RIB_TYPE_SETTINGS in all_rib_table_values.sql. Release Notes 7
Changes Since RIB 12.0 Internal Bug Number Description Notes MQC#1489 MQC#1491 Problems with ewtransferstostockorderfrom RIB TAFR in 12.0.1. RIB tafr coltranserstostockorderfrom RIB does not transform the comments field to topic etstockorderiso. The TAFR ewtransferstostockorderfromrib throws the following exception. Messages are stuckon JMS as a result of this exception: 16:53:43.965 COL I 9 (java_extensions.cxx:1442): *************** Exception occurred **************^M 16:53:43.966 COL I 9 (java_extensions.cxx:1442): tostring: java.lang.nosuchmethoderror: com.retek.rib.etd.sodesc.getdeliver ydate()lcom/retek/rib/etd/deliverydate;^m 16:53:43.967 COL I 9 (java_extensions.cxx:1442): ^M 16:53:43.968 COL I 9 (java_extensions.cxx:1442): getmessage: com.retek.rib.etd.sodesc.getdeliverydate()lcom /retek/rib/etd/d eliverydate;^m 16:53:43.969 COL I 9 (java_extensions.cxx:1442): ^M 16:53:43.971 COL I 9 (java_extensions.cxx:1442): StackTrace: java.lang.nosuchmethoderror: com.retek.rib.etd.sodesc.getdeliverydate()lcom /retek/rib/etd/deliverydate; at crtransferstostockorderfromrib.transformmess age(crtransferstostockorderfromrib.java:338) at com.retek.rib.sbyn.collab.tafrhelper.convertmess ages(tafrhelper.java:96) at crtransferstostockorderfromrib.executebusine ssrules(crtransferstostockorderfromrib.java:13 2) at com.stc.jcsre.jcollaboration.translate(jcollaborati on.java:148) at com.stc.common.collabservice.jccollabcontrolle rimpl.translate(jccollabcontrollerimpl.java:568) 8 Oracle Retail Integration Bus
Changes Since RIB 12.0 Internal Bug Number Description Notes MQC#1492 MQC#1494 MQC#1495 ewtransfertostockorder sends message to hospital with RIBIntegrationException. TransfersToStockOrderFromRI B TAFR drops the NOT AFTER DATE field. Remove ASN EDI e*ways from rib4sim PAK (12.0.1) The attached transfer message was sent from RMS to the topic ettransferfromrms. On switching on the tafr ewtransferstostockorderfromrib, the message was sent to the RIB hospital with the following exception: com.retek.rib.binding.exception.ribintegrationex ception: Thread instance of ClientContext already exists (did another method forget to call clearthreadinstance()?): Thread instance of ClientContext already exists (did another method forget to call clearthreadinstance()?) - Nested exception: - java.lang.illegalstateexception: Thread instance of ClientContext already exists (did another method forget to call clearthreadinstance()?) No similar exception was logged on the SeeBeyond logs or the Riblogs. The ASN In (856) Interface no longer supports the conversion from EDI file to RIB Payload (XML) format. Retailers are required, using their EDI translation software, to translate incoming ASN In (856) EDI transactions to the ASNin Message Type (ASNInCre, ASNinMod, ASNInDel). Release Notes 9