JD Edwards EnterpriseOne Date Utility

Transcription

1 JD Edwards EnterpriseOne Date Utility June 2010

2 JD Edwards EnterpriseOne Date Utility Releases Xe thru 9.0 Copyright Notice Copyright 2010, Oracle and/or its affiliates. All rights reserved. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. License Restrictions Warranty/Consequential Damages Disclaimer 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. Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010; 5,960,204; 5,987,497; 5,995,972; 5,987,497; and 6,223,345. Other patents pending. Warranty Disclaimer 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. Restricted Rights Notice 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 , Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA Hazardous Applications Notice 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. Third Party Content, Products, and Services Disclaimer 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. Contains GNU libgmp library; Copyright 1991 Free Software Foundation, Inc. This library is free software which can be modified and redistributed under the terms of the GNU Library General Public License.

3 Includes Adobe PDF Library, Copyright Adobe Systems, Inc. and DL Interface, Copyright Datalogics Inc. All rights reserved. Adobe is a trademark of Adobe Systems Incorporated. Portions of this program contain information proprietary to Microsoft Corporation. Copyright Microsoft Corporation. Portions of this program contain information proprietary to Tenberry Software, Inc. Copyright Tenberry Software, Inc. Portions of this program contain information proprietary to Premia Corporation. Copyright 1993 Premia Corporation. This product includes code licensed from RSA Data Security. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). All rights reserved. This product includes the Sentry Spelling-Checker Engine, Copyright 1993 Wintertree Software Inc. All rights reserved. Open Source Disclosure Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracle's JD Edwards EnterpriseOne products and the following disclaimers are provided. This product includes software developed by the Apache Software Foundation ( Copyright (c) The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

4 JD Edwards EnterpriseOne Date Utility Business Problem JD Edwards EnterpriseOne stores calendar dates in Julian date format. The system allows two-digit dates to be entered to facilitate data entry. The system uses data dictionary item CENTCHG (CenturyChangeYear) to determine the century to use for populating data tables. The system also uses this data dictionary item to automatically populate the default effective through and expiration dates in some data tables. In releases Xe and ERP8.0, the default value for CENTCHG is set to 10. Thus dates populated using the CENTCHG default are created as 12/31/2010. In release 8.9, the default value is set to 15, creating a date of 12/31/2015. In releases 8.10 through 9.0, the default value is set to 40, creating a date of 12/31/2040. As we approach the end of the year 2010 it is necessary to update the default value of CENTCHG to ensure accurate dates are assigned to new data within JD Edwards EnterpriseOne. After changing the default value, new data that is created will use the appropriate expiration date. However, the system cannot update existing dates in the tables. Some expiration dates may be valid. Therefore, users must evaluate the dates to determine which dates should be revised. Customer Impact The CENTCHG default value impacts: Customers currently running JD Edwards EnterpriseOne Xe thru 8.9 releases. Customers who upgraded to a newer release from Xe, ERP 8.0, or 8.9. Purpose The Date Utility identifies the tables and fields within JD Edwards EnterpriseOne that contain a specific date value and enables you to change that date value. You can run the Date Utility in three modes: Scan mode. The Scan mode enables you to search across a user-specified group of JD Edwards EnterpriseOne tables for a specific date value and provides data output for analysis. Update Proof mode. The Update Proof mode enables you to identify the specific field within a specific table that the system updates when you run the Date Utility in Update Final mode using the same set of input parameters. Update Final mode. The Update Final mode enables you to replace an existing date value in a specified field within a specified table. Copyright 2010, Oracle and/or its affiliates. All rights reserved. 1

5 JD Edwards EnterpriseOne Date Utility Chapter 1 The Date Utility is intended to update current dates in the system, not historical dates. It is not necessary to run the Date Utility across historical tables such as the Account Ledger (F0911), Item Ledger (F4111) Sales Order Header History File (F42019), Sales Order History File (F42119), PO Detail Ledger (F43199) and so on. The Date Utility is intended to update dates used for current and future transactions. This document explains how to install and run the Date Utility in all modes. Installing the Date Utility To install the Date Utility: 1. Access the Update Center on My Oracle Support. 2. Filter on JDE EnterpriseOne Products and search for DATEUTIL.. 3. Select the appropriate executable file. a. For release Xe, select DATEUTILXE. b. For releases later than Xe, select DATEUTIL. 4. Copy the DateScan.exe file to OW_DIR_BASE\system\bin32 directory. Note. OW_DIR_BASE is the base directory of the current JD Edwards EnterpriseOne installation. In this document, b9 represents the base directory in all examples and data strings. Using the Date Utility To use the Date Utility: 1. Create UDC table entry 98/UU. You use the UDC table to store an imported list of table names that you maywanttoexclude when you run the Date Utility. 2. Import the list of table names that you want to exclude. Oracle provides an Excel file, Date Utility - Table Scan Exclusion List.xls,that lists recommended table names to exclude. Note. You can edit the list according to your business needs. 3. Sign in to the correct JD Edwards EnterpriseOne environment. 4. Run the Date Utility in Scan mode. 5. Analyze the Scan mode results. 6. Backup the database. 7. Run the Date Utility in Update Proof mode. 8. Review the Update Proof mode results. 9. Run the Date Utility in Update Final mode. 10. Review the Update Final mode results. 11. Validate the accuracy of the updates. 2 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

6 Chapter 1 JD Edwards EnterpriseOne Date Utility Setting Up UDC Table 98/UU In order to minimize the amount of time necessary to run the Date Utility, you should create UDC table 98/UU and import a list of tables that you want to exclude while running the Date Utility. Oracle provides a list of tables to exclude. Steps to Create UDC Table 98/UU To create UDC table 98/UU: 1. Login to the correct JD Edwards EnterpriseOne environment. 2. Enter UDC in the Fast Path field and press Enter. 3. On the Work with User Defined Codes form, enter 98 in the Product Code field. 4. Click in the User Defined Codes field and click the Visual Assist button. 5. On the Work With User Defined Code Types form, click Add. 6. On the User Defined Code Types form, click the Go to End button. 7. Enter the following information into the grid: Code Types Description Code Length 2nd Line (Y/N) Numeric (Y/N) UU Date Utility Table Exclusion 10 N N 8. Click OK. 9. Return to the Work With User Defined Codes form. Steps to Import Data into UDC Table 98/UU To import data into UDC table 98/UU: 1. On the Work With User Defined Codes form, enter 98 into the Product Code field. 2. Enter UU into the User Defined Codes field. 3. Click Find. Thegridshouldbeempty. 4. Click Add. 5. On the User Defined Codes form, select Import Grid Data from the Tools menu. The system displays the Import Assistant form. 6. In the Step 1 Define Import File section: a. Select the Import From Excel radio button. b. Click the Browse button and navigate to where you have stored the Date Utility - Table Scan Exclusion List.xls c. Enter 98UU Entries in the Worksheet name field. 7. IntheStep2 DefineCellRangesection,entertherangeofcellsthatyouwanttoimportfromtheDate Utility - Table Scan Exclusion List.xls document. Copyright 2010, Oracle and/or its affiliates. All rights reserved. 3

7 JD Edwards EnterpriseOne Date Utility Chapter 1 8. In the Step 3 Define Import Location in Grid section, select the Insert (Import... grid) button. 9. Click the Apply button. The system imports the data into the grid on the form. See example of a completed Import Assistant form below. 10. Click Continue to import the data into the 98/UU table. Note. The system may be set to import a maximum number of rows of data in a single instance. If you have more data to import, repeat the process and adjust the cell range accordingly. 11. Click OK to save the imported data. 12. Click Find to confirm that the system successfully imported the data. This is an example a completed Import Assistant form. 4 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

8 Chapter 1 JD Edwards EnterpriseOne Date Utility Example of a completed Import Assistant form Copyright 2010, Oracle and/or its affiliates. All rights reserved. 5

9 JD Edwards EnterpriseOne Date Utility Chapter 1 Running the Date Utility in Scan Mode The Scan mode enables you to search across JD Edwards EnterpriseOne tables for a specific date value. Use the Scan mode to identify the tables and fields that you need to revise prior to running the Date Utility in either of the Update modes. Scan Mode Input Parameters The input parameters determine how the system searches for the specified date. You must limit the search using either table or system code ranges. The Scan mode input parameters are: Date Table Range System Code Range Enter the date that the system searches for in the JD Edwards EnterpriseOne tables. This parameter is mandatory. Enter the start and end table names to limit the tables that the system searches across for the specified date. If you use this parameter, you cannot use the System Code Range parameter. Enter the start and end system codes to limit the tables that the system searches across for the specified date. This is the system code attached to the table within Object Management Workbench (OMW). If you use this parameter, you cannot use the Table Range parameter. Note. The System Code Range field is alphanumeric. Note. The input parameters are case sensitive. Scan Mode Output The Scan mode produces a CSV file with the following information: The scanned date value. Table name and description. Field name and description. System code. Numberofrecords found. This table summarizes the CSV file output based the input parameter combinations: 6 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

10 Chapter 1 JD Edwards EnterpriseOne Date Utility Example Purpose Data String Input Output 1 List all JD Edwards EnterpriseOne tables and fields within the table range of F0001 to F0010 that contain the date December 31, List all JD Edwards EnterpriseOne tables and fields within the system coderangeof01to09that contain the date December 31, b9\system\bin32\datescan.exe TBLE F0001 F0010 b9\system\bin32\datescan.exe SYSCODE The system produces a CSV document that lists the tables ranging from F0001 to F0010, fields within the tables, system codes associated to the tables, and the number of occurrences that contain the date December 31, The system produces a CSV document that lists the tables within system codes ranging from 01 to 09, fields within the tables, system codes associated to the tables, and the number of occurrences that contain the date December 31, Note. The system also writes the log in the file DateScanLog.txt and appends to the log each time you run the Date Utility. The system creates the CSV files and log in the directory where the jdedebug log is created per the JDE.INI file. For example, if the entry in the JDE.INI file, DEBUG section is [DEBUG] DebugFile=c:\datescan\jdedebug.log, the system stores the CSV files and log in the C:\datescan directory. This is an example of data string input for the Date Utility in Scan mode: Data string input for Scan mode This diagram is an example of the data output from the Date Utility run in Scan mode: Copyright 2010, Oracle and/or its affiliates. All rights reserved. 7

11 JD Edwards EnterpriseOne Date Utility Chapter 1 Data output from the Date Utility run in Scan mode Steps to Run the Date Utility in Scan Mode To run the Date Utility in Scan mode: 1. Sign in to the correct JD Edwards EnterpriseOne environment. 2. From the Windows Toolbar, click Start. 3. Click Run. 4. Type cmd in the Run window. 5. Click OK to display the Command Prompt line. 8 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

12 Chapter 1 JD Edwards EnterpriseOne Date Utility Example 1: Command prompt initial display 6. Type cd.. at the cursor location. 7. Press Enter. 8. Repeat steps 6 and 7 until you see the C:\> prompt. Example 2: Command prompt ready for data string input You are now ready to input data parameters and run the Date Utility. 9. Enter the data string for the date you want to search for in the JD Edwards EnterpriseOne database. You can include table ranges or system codes as discussed earlier. For example, enter b9\system\bin32\datescan.exe TBLE F0001 F Copyright 2010, Oracle and/or its affiliates. All rights reserved. 9

13 JD Edwards EnterpriseOne Date Utility Chapter 1 Example 3: Command prompt with data string input 10. Press Enter to run the Date Utility. You will see the message Initializing Environment for Date Scan Utility. This indicates that the Date Utility is running. Note. If you are not logged into your environment, the system displays a prompt to login. Login to continue. Example 4: Initializing Date Utility Note. The length of time that the Date Utility runs depends upon the input parameters that you specify. The system runs just-in-time installs (JITIs) for each table based upon the input parameters. 11. After the system processes all the tables, press any key to continue. 10 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

14 Chapter 1 JD Edwards EnterpriseOne Date Utility Example 5: Exiting Date Utility 12. Wait until you see the C:\> prompt before running the Date Utility again. Example 6: Date Utility ready to run again When the Date Utility is finished running the first time, the system creates a log and a CSV file document with adateand time stamp. Each subsequent time you run the Date Utility, the system appends new log information to the exiting log file and creates a new CSV file document with a date and time stamp. The title of the log is DateScanLog.txt. The naming convention of the CSV document is in the format of DateScanOutput_MM_DD_HH_Mm_SS.csv. For example a CSV file document with the name DateScanOutput_05_26_11_40_37.csv indicates that the system completed the Date Utility on May 26 at 11:40:37 AM. Copyright 2010, Oracle and/or its affiliates. All rights reserved. 11

15 JD Edwards EnterpriseOne Date Utility Chapter Repeat steps 9 thru 12 using another data string input based on your business requirements. 14. Analyze the output documents to determine which tables and fields you want to update. Based upon the data output, you may determine that you can update some tables using the corresponding application. Running the Date Utility in Update Mode The Update mode enables you to replace a specific date value within a specific table and field. You can only replace the values in one field of a given table during a single run of the Date Utility. For example, if you need to replace four date fields within a single table, you have to run the Date Utility four times. You can run the Date Utility in Update Proof and Update Final modes. Run the Date Utility in Update Proof mode first to confirm that the number of records that the system identified when you ran the Date Utility in Scan mode is the same number. The system does not replace any data when you run it in Update Proof mode. After confirming the Update Proof mode results with the date scan results, you can run the Date Utility in Update Final mode. The system replaces the data based upon your input parameters. When you run the Date Utility in Update Final mode, the system updates all records that match the input criteria. You cannot direct the Date Utility to update less than all of the records in a given column. For example, if the Date Utility identified ten records in table F0008 with the 12/31/2010 in the D12J field, and your input parameters are UPDATE FINAL F0008 D12J; the system updates all ten records in the F0008 table with the new date of Warning! Before you run the Date Utility in Update mode, BACKUP YOUR DATABASE. The Date Utility does not perform any validation against the tables. Oracle recommends that you run the Date Utility against a test environment before you run it against a production environment. If you only need to revise a small number of records in any table, you should use available interactive programs to update the records. Update Mode Input Parameters The input parameters determine the table and field for which the system replaces the date. You must input the following information for the update mode to run successfully: Mode Enter the mode for which you want to run the Date Utility. Values are: UPDATE PROOF: Run the Date Utility in Update Proof mode to confirm that the system is about to replace the number or records within the specified table and field that you identified when you ran the Date Utility in Scan mode. UPDATE FINAL: Run the Date Utility in Update Final mode to update all values in the specified table and field. Note. You should run the Date Utility in Update Proof mode before you run it in Update Final mode. Table Name Enter the table name for which you want the system to replace a date. 12 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

16 Chapter 1 JD Edwards EnterpriseOne Date Utility Field Name Date to Replace Replacement Date Enter the field name within the table for which you want the system to replace a date. Many tables contain more than one date field. If you need to update multiple fields within a table, you must run the Date Utility in Update mode multiple times. Enter the existing date that you want the system to replace. This should be the same date that you used when running the Date Utility in Scan mode. Enter the new date that you want the system to populate in the field. This should be a valid future date. The system does not validate this date against the CENTCHG field value. Note. The input parameters are case sensitive. Update Mode Output The Update mode produces a CSV file with the following information: Date to Replace. Replacement Date. Table name and description. Field name and description. Number of records the system updated. When you run the Date Utility in Update Final mode, the system updates the field specified in the input parameters and the following audit fields: Field Name (Data Dictionary Item) Field Description Field Value PID Program ID SCANUTIL UPMJ Date Updated Current Date TDAY Time of Day Current Time JOBN Workstation ID Machine Name USER User ID EnterpriseOne User ID The input parameters for Update mode are limited to one set of criteria for both Proof and Final mode. This example summarizes the CSV file output: Copyright 2010, Oracle and/or its affiliates. All rights reserved. 13

17 JD Edwards EnterpriseOne Date Utility Chapter 1 Proof Final Mode Purpose Data String Input Output Confirm that the system is about to replace the number of records that youidentifiedwhenyou ran the Date Utility in Scan mode. Update all values in the Expiration Date field (EXDJ) in the Item Cross Reference table (F4104), replacing December 31, 2010 with December 31, 2040 b9\system\bin32\datescan.exe UPDATE PROOF F4104 EXDJ b9\system\bin32\datescan.exe UPDATE FINAL F4104 EXDJ ThesystemproducesaCSV document with one line of information that contains the table, field, and number of records that the system will update with the replacement value. ThesystemproducesaCSV document with one line of information that contains the table, field, and number of records that the system updated with the replacement value. Note. The system also writes the log in the file DateScanLog.txt and appends to the log each time you run the Date Utility. The system creates the CSV files and log in the directory where the jdedebug log is created per the JDE.INI file. For example, if the entry in the JDE.INI file, DEBUG section is [DEBUG] DebugFile=c:\datescan\jdedebut.log, the system stores the CSV files and log in the C:\datescan directory. This diagram is an example of the data string input for Update Proof mode: Data string input for Update Proof mode This diagram is an example of the data output from the Date Utility run in Update Proof mode: 14 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

18 Chapter 1 JD Edwards EnterpriseOne Date Utility Data output from the Date Utility run in Update Proof mode This diagram is an example of the data string input for Update Final mode: Data string input for Update Final mode This diagram is an example of the data output from the Date Utility run in Update Final mode: Data output from the Date Utility run in Update Final mode Copyright 2010, Oracle and/or its affiliates. All rights reserved. 15

19 JD Edwards EnterpriseOne Date Utility Chapter 1 Steps to Run the Date Utility in Update Proof and Update Final Modes READ THE FOLLOWING WARNING MESSAGE: Warning! Before you run the Date Utility in Update mode, BACKUP YOUR DATABASE. The Date Utility does not perform any validation against the tables. Oracle recommends that you run the Date Utility against a test environment before you run it against a production environment. You should also run the Date Utility at a time when no other batch jobs or programs are in the process of modifying or adding records in the database. If you only need to revise a small number of records in any table, you should use the available interactive programs to update the records. To run the Date Utility in Update Mode 1. Sign into a JD Edwards EnterpriseOne environment. 2. From the Windows Toolbar, click Start. 3. Click Run. 4. Type cmd in the Run window. 5. Click OK to display the Command Prompt line. Example 1: Command prompt initial display 6. Type cd.. at the cursor location. 7. Press Enter. 8. Repeat steps 6 and 7 until you see the C:\> prompt. 16 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

20 Chapter 1 JD Edwards EnterpriseOne Date Utility Example 2: Command prompt ready for data string input You are now ready to input data parameters and run the Date Utility in Update mode: Running the Date Utility in Update Proof Mode To run the Date Utility in Update Proof mode: 1. Enter a data string that represents the data you want to run in Proof mode. For example, b9\system\bin32\datescan.exe UPDATE PROOF F4104 EXDJ. Data string input for Update Proof mode 2. Press Enter to run the Date Utility. The system displays a message informing you that the Date Utility ran and how many records were found. Copyright 2010, Oracle and/or its affiliates. All rights reserved. 17

21 JD Edwards EnterpriseOne Date Utility Chapter 1 Note. If you are not logged into your environment, the system displays a prompt to login. Login to continue. Date Utility run in Update Proof mode 3. After the Date Utility runs, press any key to continue. Date Utility successfully ran in Update Proof mode 4. When the Date Utility finishes running, the system appends the log and creates a new CSV file document with date time stamp. Running the Date Utility in Update Final Mode To run the Date Utility in Update Final mode: 18 Copyright 2010, Oracle and/or its affiliates. All rights reserved.

22 Chapter 1 JD Edwards EnterpriseOne Date Utility 1. Enter a data string that represents the data you want to run in Final mode. For example, b9\system\bin32\datescan.exe UPDATE FINAL F4104 EXDJ. Data string input for Update Final mode 2. Press Enter to run the Date Utility. The system displays a message informing you that the Date Utility ran and how many records were replaced. Note. If you are not logged into your environment, the system displays a prompt to login. Login to continue. Date Utility run in Update Final mode 3. After the Date Utility runs, press any key to continue. Copyright 2010, Oracle and/or its affiliates. All rights reserved. 19

23 JD Edwards EnterpriseOne Date Utility Chapter 1 Date Utility successfully ran in Update Final mode 4. When the Date Utility is finished, the system appends log information to the log file and creates a new CSV file document with a date and time stamp. 5. You can now run the Date Utility again with a different set of input parameters. 20 Copyright 2010, Oracle and/or its affiliates. All rights reserved.