Summary release notes for 2.2.173
released on 8/10/2022
Bug 24559: Bug 24599 - PTM Vision/Inventory: F8 transactions from inventory and F8 source does not work to bring up old PO's
Bug 24700: Bug 24700 - PTM Vision/Open Orders: When a Multi-inventory part with a core charge is back ordered from an order, we are prompting to add a Core charge to the core part itself
Bug 25138: Bug 25138: PTM Vision/Customer file: Tooltip on Ytd Purchases is missing
Bug 25220: PTM Vision/Shop Time Manager: If an Input form exists on a Labor operation, we are able to login to the same job multiple times when the setting is set to No
Bug 25228: Bug 25228 - PTM Vision/Open Orders: Ship-To addresses with blank phone numbers default to the Customer address instead of the address information selected
Bug 25243: Bug 25243 - PTM Vision/Customer File/Customer Aging Report: Invoice number on Customer aging report not displaying correctly
Detailed release notes for 2.2.173
_______________________________________________________________
DESCRIPTION:
Bug 24599 - PTM Vision/Inventory: F8 transactions from inventory and F8 source does not work to bring up old PO's
APPLICATION: PTM Vision/Inventory
PROBLEM SUMMARY: F8 transactions from inventory and F8 source does not work to bring up old PO's
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select I. Inventory
-
Select F8. Sls/His
-
Select T.Transactions
-
Enter a date range that would garner purchases that exist in Purchase order History
-
Select Ok
-
Select the Purchases Tab
-
Line up on a Purchase order and select F8. Source
-
Verify the correct Purchase order in PO history is shown
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
DESCRIPTION:
Bug 24700 - PTM Vision/Open Orders: When a Multi-inventory part with a core charge is back ordered from an order, we are prompting to add a Core charge to the core part itself
APPLICATION: PTM Vision/Open Orders
PROBLEM SUMMARY: When a Multi-inventory part with a core charge is back ordered from an order, we are prompting to add a Core charge to the core part itself
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select O. Open Orders
-
Select the Work or Sales order tab
-
Select F2. New
-
Enter Customer account information
-
In the Input field, enter an Inventory part that is assigned to a multi-inven and also has a Core charge
-
Back order the part
-
Select F11. PO
-
Select O to order the part
-
Select R to receive the part
-
Select F8. Process
-
Add to payables, if prompted
-
Verify no prompt is shown to change the cost of the core
-
-
Exit Purchase Orders and return to the order
-
Verify the Core cost is correct on the order
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
DESCRIPTION:
Bug 25138: PTM Vision/Customer file: Tooltip on Ytd Purchases is missing
APPLICATION: PTM Vision/Customer File
PROBLEM SUMMARY: Tooltip on Ytd Purchases is missing
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select C. Customer File
-
Hover over the Ytd Purchases field
-
Verify the tooltip is shown and states "Displays the customer's YTD purchases"
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=customer_files
DESCRIPTION:
PTM Vision/Shop Time Manager: If an Input form exists on a Labor operation, we are able to login to the same job multiple times when the setting is set to No
No Release Notes
DESCRIPTION:
Bug 25228 - PTM Vision/Open Orders: Ship-To addresses with blank phone numbers default to the Customer address instead of the address information selected
APPLICATION: PTM Vision/Open Orders
PROBLEM SUMMARY: Ship-To addresses with blank phone numbers default to the Customer address instead of the address information selected
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select C. Customer File
-
Select a Customer
-
Select F9. More
-
Select F4. Edit
-
Enter SHIP-LST in the Automatic Shipto Account field
-
Select F4. Edit
-
Select Ok
-
Select Ctrl+B. B-Ship
-
Enter a couple different Ship-To address
-
Leave the phone number on one of them blank
-
Exit the Customer file and select O. Open Orders
-
Select the Sales order tab
-
Select F2. New
-
Enter the customer
-
Once the Ship-to prompt is shown, line up on the one with no phone number and select F8. Select
-
Verify the Ship-To address is correct
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
DESCRIPTION:
Bug 25243 - PTM Vision/Customer File/Customer Aging Report: Invoice number on Customer aging report not displaying correctly
APPLICATION: PTM Vision/Customer File/Aging Report
PROBLEM SUMMARY: Invoice number on Customer aging report not displaying correctly
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select C. Customer File
-
Select F7. Print
-
Select G. Customer Aging
-
Verify the Invoice numbers are displayed correctly
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>