B2W Import Errors

- Row XXX. FLXXX. Total Time is missing for Travel Phase. Hrs must be entered for travel.

          - Usually someone has put something in the Travel Phase column, but has failed to enter in actual hours under Travel Column (if it is a Field Log) or in the Travel Line (if it is a Work Log)

   Solution: Go to the FL/WL in B2W and delete what is in the Travel Phase (unless there should be actual travel hours in this line, in which case put in the Travel Hours)

- Combined Warning & Error: Row XXX. FLXXX. ##WARNING: Hrs entered under Travel is missing Travel Phase. Travel Phase '1' will be used.
  Row XXX. FLXXX. Employee XXX. Job XX-XXXX-XX. Phase 1 (Travel) does not exist - if internal job, check employee division code and matching phase.
           - Usually someone has put something in the Travel hours, but has failed to fill out the Travel Phase Column (program has tried to fill it with '1', but that is not valid for multiphase jobs)

   Solution: Go to the FL/WL in B2W and FILL OUT THE TRAVEL PHASE COLUMN in B2W with the appropriate Phase.

- Row XXX. FLXXX. ##ERROR: Employee XXX is paid weekly/bi-weekly. Transaction date XX/XX/20XX is out of range XX/XX/20XX - XX/XX/20XX.

          - Usually someone is importing a date in the future according to the payroll cut-off date.

          
   Solution: Ensure you are importing a date range that makes sense for the pay period.

- Row XXX. FLXXX. ##ERROR: Contact Payroll: Earning Code XXTIME does not exist or is inactive for Employee XXX on date XX/XX/20XX.

           - Usually payroll has made the employee’s start date or raise be AFTER the date you are importing.

          
   Solution: Call Payroll and ask them to adjust the start date/raise date in Sage’s payroll to include your date worked.

- Row XXX. FLXXX. ##ERROR: Employee XXX is not setup or is not active in Project and Job Costing..

           - Usually the new Employee has been entered in Sage (HR Runs Payroll Link for this), but Payroll Dept has not brought the Employee into Sage PJC Module.

          
   Solution: Call Payroll and ask them to bring Employee into Sage’s PJC Module.

B2W Import Warnings (warnings will not stop you from importing, but read them to MAKE SURE THEY MAKE SENSE!)

- Row XXX. FLXXX. ##WARNING: Employee XXX is paid weekly/bi-weekly. Transaction date XX/XX/20XX is in an earlier pay period. The transaction will be posted to 20XX-XX.

- Row XXX. FLXXX. ##WARNING: Equipment usage transaction date XX/XX/20XX is in a locked fiscal period. The transaction will be posted to 20XX-XX.

         
   Solution: If you mean to import hours from a closed period, then proceed (it will be posted in the specified open period). If you did not intend to import hours from a previous period, ensure that you are importing a date range that makes sense for the pay period.

- Row XXX. FLXXX. ##WARNING: Hrs entered under Travel is missing Travel Phase. Travel Phase '1' will be used.

   Solution: If you are ok with the program using 1 as the Phase for this Travel Time, then proceed. This should be fine for all single phase jobs. If the FL/WL involves a multiphase job, you will see a follow-up error that Phase 1 (Travel) doesn't exist, as in the second error listed within this article.