Use the Vendor Labor subtask after highlighting a row in the voucher detail and storing information relating to one line in the voucher detail, such as vendor ID, GLC (General Labor Category), PLC (Project Labor Category), hours, and amount.
This screen is useful if you want to capture the total hours and currency units incurred against the project for vendors and their employees. Capturing total hours and currency units against labor categories is essential for level-of-effort projects; projects where your bill is based on hours incurred against labor categories or percent of labor hours incurred; your fee is applied on total hours; or you track all hours charged against the project for project management.
This field is non-editable. The system uses it to track the number of lines in the table, and updates it automatically as you insert or delete lines.
Enter, or use Lookup to select, a valid vendor employee identification number for this vendor.
Enter, or use Lookup to select, a GLC for this vendor. If there is a relationship between the GLC to the PLC against the project, the system displays the PLC for this vendor and project.
Enter, or use Lookup to select, a PLC for this vendor. The PLC you enter must be valid for the project charged on the main screen.
Hours *
Enter the hours for this vendor and labor category. You can enter no hours (zero).
Enter the amount for this vendor and labor category. You can enter no currency amount (zero) on a Sub Line, but the total of all the Sub Lines must equal the currency amount on the selected line of the Table Window of the header.
This column displays the VAT recovery amount, if any.
Enter the effective billing date in this column. You can attach effective billing dates to each labor line. As a result, corrections can be given the proper date and each line can have a separate Effective Billing Date.
Validations:
GLC - The system checks the General Labor Categories screen to make sure the GLC entered on this line is present.
PLC - The system reads the Basic Info screen in to see whether the Project Work Force Required checkbox is selected and performs the following validations:
If the work force is required, the application checks the Vendors screen to determine whether this vendor exists. Next, the system checks the PLC in the Assign PLC to Vendor Work Force screen to ensure that this PLC is valid for this vendor. If the work force is not required, the system proceeds to the next level of validation.
If a project work force does not exist or is not required, the system checks the Assign PLCs screen to determine whether the PLC entered has been assigned to a project. If the project is found in the screen but the PLC is not assigned to it, the entry is rejected. If neither the project nor the PLC is found in the Assign PLCs screen, the application proceeds to the next level of validation.
The total amount of the voucher line (total invoice before discount minus discount) and total vendor labor must match, or you cannot save the Vendor Labor subtask or return to the main screen.
The final level of validation for the PLC takes place in the Project Labor Categories screen. If the system does not find the PLCin this screen and has not located any previous validations, it rejects the PLC.
This field displays the Vendor Employee Name associated with the Vendor Employeefrom the Vendor Employees screen.
This field displays the description of the PLC.
* A red asterisk denotes a required field.
The following is a list of possible defaults that can occur when you enter a new line in the table window or leave a field/column in this subtask. (The vendor labor defaults work in conjunction with defaults for projects charged.)
If the project from the Enter A/P Vouchers screen requires a work force, the default is from the Default column in the Assign PLC to Vendor Work Force screen that indicates which PLC should be used as a default for a specific vendor.
If the vendor is not located in this screen, Costpoint obtains the vendor from the Default PLC column in the Vendor Employees screen in Vendor User Flow. If the vendor is not located in this screen, Costpoint displays an error message. If the PLC is defaulted successfully, Costpoint also defaults the PLC Description from the Assign PLCs screen in the Projects domain.
Level 2: Project Timesheet Defaults
If the first attempt to default the PLC does not succeed, the application tries to default the PLC from the Project Timesheet Defaults screen. Again, if the PLC defaults successfully, the application also defaults the PLC Description from the Assign PLC to Projects screen or the Project Labor Categories (PLC) screen.
The application also attempts to default the GLC. If the GLC is found but the PLC is not, the application tries to retrieve the PLC from the General Labor Categories screen in Costpoint Labor. If the PLC is found, the PLC Description is located first in the Assign PLCs screen and second in the Project Labor Categories (PLCs) screen.
If the Project Labor Category Map table is set up for the project and GLC, the related PLC defaults into this subtask. This level of defaults are used only if prior levels are not used.
Once you leave the Vendor Employee field after entering a valid vendor employee ID, the application defaults the GLC from the Vendor Employees screen. If the GLC defaults successfully but the PLC is not entered, the application attempts to locate it from the General Labor Categories screen. If the PLC is found, the PLC Description is located first in the Assign PLCs screen and second in the Project Labor Categories (PLCs) screen.
Changes to this screen update the VCHR_LAB_VEND table.