$TXT Created by BECKWITH,RALPH at MNTVBB.FO-WASH.MED.VA.GOV (KIDS) on Friday, 06/05/09 at 12:19 ============================================================================= Run Date: APR 22, 2010 Designation: PRC*5.1*135 Package : PRC - IFCAP Priority: Mandatory Version : 5.1 SEQ #116 Status: Released Compliance Date: MAY 23, 2010 ============================================================================= Associated patches: (v)PRC*5.1*13 <<= must be installed BEFORE `PRC*5.1*135' Subject: CEILING TRANSACTIONS NOT SHOWING UP ON RUNNING BALANCE Category: - Routine Description: ============ This patch will address the following issue: Ceiling transactions are not showing up on the Running Balance Report. ASSOCIATED NSR(s): ================== N/A Remedy: ======= HD0000000055279 Ceiling transactions not showing up on Running Balance Report. Duplicates: HD0000000055290 FGH-0502-30435 2337 TRANSACTION NOT ON RUNNING BALANCE HD0000000055294 NYH-0502-12960 UNABLE TO CARRYFORWARD CP BALANCE HD0000000055298 TAM-0602-32925 PURCHASE CARD FORM HD0000000055309 AUG-0802-31737 Questions Regarding FCP Line Item Review HD0000000055372 SBY-0303-31878 Running Balance questionable HD0000000055413 JAC-0803-71592 Control point has reset to 0000 HD0000000130056 FGH - WHY DUPLICATE "RB" XREF IN FILE 410? HD0000000132659 Incorrect account balance HD0000000145313 Prosthetics FCP -- Transaction #'s Maxed Out & Running Balance Issues HD0000000254875 Transaction dropped leading 0 on the PC order HD0000000311921 Transaction attached to order dropped leading zero on FCP HD0000000317083 Cannot sign and close out an amended record HD0000000384650 Obligation in two FCP - 117 and 5117 Test Sites: =========== VA Boston HCS St Cloud VA Medical Center Portland VA Medical Center Remedy Overview: ================ HD0000000055279 Ceiling transactions not showing up on Running Balance (RB) Report. Problem: -------- Processed a ceiling transaction which did not post on the Control Point's Running Balance Report, however it does show up when the Ceiling Report is printed. This happens when using option [Change Existing Transaction Number]. In addition, when editing a New Purchase Order, Detailed Purchase Card Order or Delivery Order a new order date/FCP causes the following problems: -- Duplicate cross-reference "RB" nodes will occur -- Inventory item within order will cause skipping of creation of correct requisition number, modifying existing req# and canceling old req# entry -- Changing order date that will fall into new fiscal quarter does not modify the req# or 'RB' entry to correct FY and FQ. -- 4 digit Fund Control Point (ex. 0498) will appear as 498 in requisition number and 'RB' cross reference entry in File 410 [CONTROL POINT ACTIVITY]. Resolution: ----------- Modify routines PRCSUT3 and PRCHNPOA to insure that the editing of the Order Date and/or the Fund Control Point will create the correct requisition number and 'RB' cross reference entry in the File 410 [CONTROL POINT ACTIVITY]. Routines: PRCSUT2, PRCHNPOA, PRCH135P (deleted after install) >>> POST INSTALL RUN TO FIX CROSS REFERENCE 'RB' IN FILE #410 <<< [CONTROL POINT ACTIVITY]. *** There will be a post install run that will delete duplicate 'RB' *** cross reference entries associated with a record internal number *** with a different Fund Control Point. Also, it will delete any 'RB' *** cross references that are linked to a null master record. ================INSTALLATION INSTRUCTIONS ================= You may install this patch at any time without interruption to users. It should take less than 2 minutes to install this patch. ************************************************************************* PLEASE NOTE: Pre-Init routine PRCH135P will be deleted once the install is complete. If you wish to check the checksum of this routine please use the 'Verify Checksums in Transport Global' under the installation Menu. ************************************************************************** 1. Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. From the Kernel Installation & Distribution System menu, select the Installation menu. 3. From this menu, you may select to use the following options: (when prompted for INSTALL NAME, enter PRC*5.1*135) a. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. b. Print Transport Global - This option will allow you to view the components of the KIDS build. c. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all components of this patch (routines, DD's, templates, etc.). d. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. 4. Use the Install Package(s) option and select the package PRC*5.1*135. 5. When Prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. 6. When prompted 'Want to DISABLE Schedule Options, Menu Options and Protocols? NO//', respond YES. When prompted to select the options you would like to place out of order, enter the following: Edit Detailed Purchase Card Order [PRCH EDIT DETAILED ORDER] Change Existing Transaction Number [PRCSANTN] Routine Information: ==================== The second line of each of these routines now looks like: ;;5.1;IFCAP;**[Patch List]**;02/09/09;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PRCH135P Before: n/a After: B2630246 **135** Routine Name: PRCHNPOA Before: B24881754 After: B25980907 **135** Routine Name: PRCSUT2 Before: B46852842 After: B49296654 **13,135** Routine list of preceding patches: 13 ============================================================================= User Information: Entered By : BECKWITH,RALPH Date Entered : MAR 03, 2009 Completed By: HEFFERNAN,COREY Date Completed: APR 21, 2010 Released By : NELSON,VICKI M Date Released : APR 22, 2010 ============================================================================= Packman Mail Message: ===================== $END TXT