To build the vendor scorecard file:Before you run the Vendor Scorecard File Report or view summary vendor scorecard information, build the scorecard file for the specific parameters you are interested in viewing. The scorecard file contains data for all the vendors in your system. You can schedule the scorecard to build on a regular basis using the Phantom Scheduler.
Note: We recommend that you schedule the scorecard file to build during off hours. If the build does not complete prior to the phantom stop time, the system system stops building the file, and resumes again during off hours.
The vendor scorecard file includes only purchase orders and direct sales orders that are completely received in the system. The scorecard excludes purchase orders that contain one or more credit items, as well as purchase orders that are flagged as exceptional.
To build the file, the system reviews all purchase orders, direct orders, and procurements in the system from the date you enter in the Start Date field until today. Depending on the volume of purchase orders and direct orders in your system, the amount of data that the system analyzes to build the report can be quite large. For this reason, we recommend that you build the scorecard file once a month, or at least quarterly. We also recommend that you schedule the process to run during non-work hours.
|
Important: If you want to save data from a previous file, save the reports you have run on previous files to your computer prior to building a new vendor scorecard file. |
To build the vendor scorecard file:
From the Reprts > End of Month Reports > Vendor Scorecard menu, select Vendor Scorecard File Build to display the Vendor Scorecard File Build screen.
Complete the following fields:
|
Field |
Description |
|
Continue from Last Build |
The first time you build the vendor scorecard file, or the first time you build after purging vendor scorecard data, this field defaults to N. After you have successfully built a scorecard file, this field defaults to Y and the date in the Start Date field is the date of the last successful scorecard file build. Continuing from the last build allows you to schedule the build to run weekly, or more frequently, and is the optimal way to build your data. The system adds only the new data since the last build to the file. If you choose to not continue from the last build, you need to purge your scorecard file prior to building a new file. |
|
Start Date |
Enter the first date to include in the file. The system builds the data from that date to the current date. If the Continue from Last Build field is set to Y, the system adds the data to the existing file. If you have successfully built a vendor scorecard file, the Start Date defaults to the date the last file was built. You cannot change this date. |
|
Cost Basis |
Select the cost basis, such as cost of goods sold (COGS) for which you want to gather metrics. The system uses the basis you select here to calculate the inventory metrics, such as average inventory value and overstock inventory value, available in the scorecard. The default is COGS-COST. If you want to view inventory metrics for a basis different than what you used to build the file, you need to purge the scorecard file and rebuild it using the different basis. |
|
Overstock Days |
Enter the number of days that a product needs to be in stock before you consider it to be overstock. The system uses this number of days to calculate the value of your overstock inventory from a vendor. The default value is 90 days. If you want to evaluate overstock based on a different time period, you need to purge the scorecard file and rebuild it using a different number of days. |
|
Stagnant Period |
Enter the number of months that a product needs to be in stock without being sold before you consider it to be stagnant or dead stock. The system uses this number of days to calculate the value of your stagnant inventory from a vendor. The default value is 12 months. If you want to evaluate stagnant stock based on a different time period, you need to purge the scorecard file and rebuild it using a different number of days. |
See Also: