Sage 100

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI Jane

  The problem is that the file I am getting is nothing like what Data Collector is looking for.   I will have to set up a routine to change the file data/format.    It is coming from their Payroll Timeclock.

Bob Osborn , MCSE Sr. Consultant, Sage 100 e: BobO@dsdinc.com p: 800-627-9032 x 180 w: www.dsdinc.com

    

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

I decided to set up a report that will convert the CSV file that is given to me into a Tab Delimited file for Data Collector.  I am doing this a a Labor import (not in/out) as I don't have that info.).  I get it to import ok but in the edit screen it tells me I have an invalid end time.    I don't have an end time at all as when labor is entered without punch in & out you don't put in start or end times.  I can add them but it doesn't "like" anything I import.   

Any suggestions?   I can't find anything in the JO portal about this. 

HI Jane

  The problem is that the file I am getting is nothing like what Data Collector is looking for.   I will have to set up a routine to change the file data/format.    It is coming from their Payroll Timeclock.

Bob Osborn , MCSE Sr. Consultant, Sage 100 e: BobO@dsdinc.com p: 800-627-9032 x 180 w: www.dsdinc.com

    

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

What is the Capture Start/Stop times setting?

I decided to set up a report that will convert the CSV file that is given to me into a Tab Delimited file for Data Collector.  I am doing this a a Labor import (not in/out) as I don't have that info.).  I get it to import ok but in the edit screen it tells me I have an invalid end time.    I don't have an end time at all as when labor is entered without punch in & out you don't put in start or end times.  I can add them but it doesn't "like" anything I import.   

Any suggestions?   I can't find anything in the JO portal about this. 

HI Jane

  The problem is that the file I am getting is nothing like what Data Collector is looking for.   I will have to set up a routine to change the file data/format.    It is coming from their Payroll Timeclock.

Bob Osborn , MCSE Sr. Consultant, Sage 100 e: BobO@dsdinc.com p: 800-627-9032 x 180 w: www.dsdinc.com

    

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

What is the Capture Start/Stop times setting?

I decided to set up a report that will convert the CSV file that is given to me into a Tab Delimited file for Data Collector.  I am doing this a a Labor import (not in/out) as I don't have that info.).  I get it to import ok but in the edit screen it tells me I have an invalid end time.    I don't have an end time at all as when labor is entered without punch in & out you don't put in start or end times.  I can add them but it doesn't "like" anything I import.   

Any suggestions?   I can't find anything in the JO portal about this. 

HI Jane

  The problem is that the file I am getting is nothing like what Data Collector is looking for.   I will have to set up a routine to change the file data/format.    It is coming from their Payroll Timeclock.

Bob Osborn , MCSE Sr. Consultant, Sage 100 e: BobO@dsdinc.com p: 800-627-9032 x 180 w: www.dsdinc.com

    

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Shouldn't the End Time simply be the time in hours:minutes? 

What is the Capture Start/Stop times setting?

I decided to set up a report that will convert the CSV file that is given to me into a Tab Delimited file for Data Collector.  I am doing this a a Labor import (not in/out) as I don't have that info.).  I get it to import ok but in the edit screen it tells me I have an invalid end time.    I don't have an end time at all as when labor is entered without punch in & out you don't put in start or end times.  I can add them but it doesn't "like" anything I import.   

Any suggestions?   I can't find anything in the JO portal about this. 

HI Jane

  The problem is that the file I am getting is nothing like what Data Collector is looking for.   I will have to set up a routine to change the file data/format.    It is coming from their Payroll Timeclock.

Bob Osborn , MCSE Sr. Consultant, Sage 100 e: BobO@dsdinc.com p: 800-627-9032 x 180 w: www.dsdinc.com

    

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Hi All  I opened a case with Scanco on this.  They were able to duplicate the issue and have sent it to development.  

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

Hi All, turns out with Data Collect for Labor type entries (non In/Out entries) that you can not have more than 8 hours for an entry.    In Direct Time entry you can enter 40 hours with no problem.   Suggested that they add the "rules" to the manual. Sure they will get right on that...   

Hi All  I opened a case with Scanco on this.  They were able to duplicate the issue and have sent it to development.  

Bob - Data Collector import doesn't require that all the fields are imported.  There are a few required fields, and some are dependent on your customer's Time Tracker parameters (for example Start and End times).  

A VI import can be problematic as it dynamically transacts to the work tickets.  What I mean by that is if the batch of imported data is bad (all/most records), you need to one by one delete the records from Time Tracker Entry - because reinitializing the JT_DailyTimeEntry file does not remove the labor transactions from the work tickets.  Data Collector does not dynamically transact to the work tickets when the source file is imported; after the source file is imported you can review/modify/delete the imported time before committing (updating) updating them to JT_DailyTimeEntry.    

I only use Data Collector as my tool to import labor originating from an external system. 

HI Jane, thanks much?!   The issue I have here is that I can't get all this info in the import as it is coming from their Payroll Timeclock.  But I was able to get the VI version working.   

Attached is the import file format field requirements.  Use of the Data Collector is documented in the user manual posted in the JobOps portal.

Hi @Jane Scanlan, I thought about it but I can't find any info on how to configure the import file for it. Do you have anything that shows this?

Bob - Data Collector is the import function that you should use for importing time.  It is a far simpler tool than VI.  

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

HI All, I was able to resolve the issues.  Found one field that I was not importing.  I also found that the end time is not required.  The file comes from their payroll timeclock. The Temp001 is the Earning  code which is R, O, D or V (regular, overtime, double overtime or Vacation which is skipped).  Temp002 is not used. 

------------------------------
Bob Osborn
Senior Consultant
DSD
7142645278
------------------------------