APPLICATION: PTM Vision/Invoices and Pluss Commerce

 

PROBLEM SUMMARY:  Unable to process ROA payments into Vision (error occurs) from Pluss Comm until an Invoice is processed

 

<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>

***Testing required only if using Pluss Commerce; Otherwise, no testing is required***

<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>

1. Access the PlussCommerce webpage

2. Login to a Customer account

3. Select the Invoices menu

4. Select the Make Payment button

5. Enter an amount and select Pay

6. Enter CC account info

7. Select Process button

8. Select Continue Shopping button to return to PC site

9. Access PTM Vision

10. Select the Invoices button

11. Select the F6. Process button

    1. Verify the Payment is processed correctly and no error occurs

 

<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>

• Pluss Commerce E-Commerce Web Page: Please Contact Pluss Software Sales Department for more information

 

<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>

http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=22_0_pluss_commerce

 

APPLICATION: PTM Vision and the Managed Mobile Inventory Application

 

PROBLEM SUMMARY:  When the Branch ID code feature is blank and the Mobile Inven scripts are generated, we are incorrectly creating the scripts

 

<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>

***Testing required only if using the Managed Mobile Inventory Application and PTM Vision; Otherwise, no testing is required***

<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>

1. Access PTM Vision

2. Select Mobile/Utilities/Generate Mobile Scripts

   1. Verify any incoming Transactions can be properly processed into PTM Vision

 

<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>

• 5,75: Enable Android Mobile Inventory Application

• 7,21: Branch Id Code

 

<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>

http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=23_1_1

 

APPLICATION: PTM Vision 

 

SUMMARY:  PlussPay - Add Utility to Inventory for importing Commodity Codes into Inventory Items

 

<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>

N/A

<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>

 

To help users assign Commodity Codes to their Inventory items, a Commodity Code import utility can be accessed via the Inventory Options menu.

 

Note: This is not to be confused with the import utility for getting the Commodity Codes into the system. This one is specifically for assigning Commodity Codes to the Inventory Items.

 

The utility is used to import a CSV (either comma or tab delimited) populated with LineParts and Commodity Codes. The utility will try to match each LinePart up with an existing Inventory item and update the Commodity Code if a match was found. If no match is found, the utility will move onto the next pair in the file.

 

When the utility updates the Inventory item with the new Commodity Code, it checks if the Commodity Code exists in the Commodity table. If it does not exist, it will create a new entry in the Commodity table with a description stating that it was added via the import utility and for what LinePart.

 

To reduce the chances that the utility does not find a Commodity Code, it is recommended to import all of the Commodity Codes via the Commodity Code Setup option before running this utility.

Recommended Workflow

1. Obtain a list of LineParts in the Inventory in a CSV format.

2. To ensure best formatting of numbers beginning with zeros, and to prevent part numbers being converted to dates, format the columns to Text rather than General.  

   1. In Excel, select and highlight columns A and B, right click the mouse, select Format Cells and select Text in the menu.  

   2. In Google Sheets, select and highlight columns A and B, select Format from the menu, select Number and check Plain Text.

3. This can either be manually created or by using the Export Inventory Key Fields utility found at U,K,K,T,T (requires Admin password)

   1. 1. If using the U,K,K,T,T export, see the Using the U,K,K,T,T Export to Generate Import List section below

4. Assign all of the LineParts the appropriate Commodity Codes in the second column of the CSV

   1. It is recommended to open the CSV file from Step 1 in Excel, Google Sheets, or equivalent

   2. Make note of any Commodity Codes that are missing from Vision

5. Either manually or via the Commodity Code Setup import, update the Commodity Codes in Vision with the ones that were missing from Step 2

6. Use the Commodity Code Inventory import utility to load the generated CSV file

   1. See Running the Import Utility below

7. Clean up any Commodity Codes that were not found during the import

Using the U,K,K,T,T Export to Generate Import List

Navigate to the following Utility

1. U - Utilities

2. K - File Utilities

3. K - Data File Utilities

   1. Enter Admin and File Access Passwords

4. T - Inventory (Maintenance)

5. T - Export Inventory Key Fields Part-Desc-Qty-Application

 

For ease of use, make the following changes in the Options dialog

 

1. Set the Delimited Structure value to Y

2. Change the File extension from TXT to CSV in the Save To File field

3. Set the Include Description value to N

4. Click Ok and the export file will be created in the root Vision directory.

 

The export file will have additional fields that are not needed for the Commodity Code Inventory import. The easiest way to get rid of those fields is to open the file in Excel, Google Sheets, or equivalent and delete columns B and C. This leaves just column A containing all of the LineParts from the Inventory.

 

The file is then ready to have the Commodity Codes assigned in the second column.

Running the Import Utility

1. Open the Inventory window and press F6 - Options. Hover over the Import Options entry then select the Import Commodity Codes option.

2.  

3. Using the Open File dialog box that is displayed, select the file to import. If the user cancels out of the Open File dialog or the selected file does not exist for some reason the user will be prompted if they would like to select another file. If they choose No the import process will be aborted.

4. If the system is set up for Multi-Inventory, a dialog will be displayed prompting which Inventory to import into. If the value is left blank the file will be imported into the Main Inventory, otherwise it attempts to import it into the desired Inventory. If the entered Inventory does not exist in the system (i.e. there is no INVENZ) a message will be displayed stating that it doesn’t exist and the user will need to enter a valid Inventory letter.

5. Once a valid Inventory is selected, a prompt will be displayed asking if the CSV file is Tab Delimited. The user should select Yes/No based upon the contents of the file.

6. During the import, if any Commodity Codes do not exist in the system they will be automatically added to the Commodity table with a description stating that it was added via the Import and for which Part it was added for. If any Commodity Codes were not found a dialog is displayed describing what actions the import took and what to do next. The dialog also allows the user to export/save the list of missing Commodity Codes to a file for review.

7.  

8. If the user clicks Yes a Save File dialog is displayed and the utility will save the list to the selected file.

9.  

10. The user should review the list and manually correct all of the Commodity Code descriptions/details or fix the Commodity Code if it was a mis-type.

11.  

12. If none of the Commodity Codes were missing or the user responds to the Missing Commodity Codes prompt, a dialog is displayed stating the import is complete.

 

<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>

N/A

 

<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>