Child pages
  • USPIMPORT - Import File Specifications
Skip to end of metadata
Go to start of metadata

USPIMPORT - Import File Specifications

 

Overview

The USPIMPORT/ ATTEND option allows data obtained from third party software to be imported into USPS. The information is imported into ATDSCN and may be used to automatically load information into UPDCAL_CUR or UPDCAL_FUT.

 Please refer to the USPIMPORT chapter of the USPS Reference Manual to familiarize yourself with the purpose and use of this program.

 The import file used with the ATTEND option will be supplied by a third party software vendor. It must be a comma delimited or comma separated values (CSV) file.

 The record layout for this file is described in the next section of this chapter.

 Any records in the CSV file which are unable to be posted to ATDSCN will be written to a "rejected" CSV file. If desired, the ITC may edit the file to correct the errors then reload the corrected "rejected" file using USPIMPORT.

Attendance/Absence Import Specification

General Record Format

The input records are standard comma separated values (CSV). The records must conform to the following rules:

  • Each field is separated by a comma (,).
  • Text fields that contain spaces or lowercase characters should be surrounded by double quotes (").
  • Numeric fields must contain numeric digits, an explicit decimal point (.), and a leading or trailing sign (+/-). If a sign character is not included in the field, it is assumed positive. The decimal point is optional if the number is a whole number.
  • Numeric values must be in the range specified in the record layout.
  • Each field is identified by its ordinal position within the record.
  • For fields that are optional, if the field is at the end of the record, you may omit the field and all fields after it. For fields in the middle of the record, you must specify a null (string) field consisting of two double quotes ("").

Each record should be terminated by a LF/CR sequence (or just LF or just CR as is appropriate for the source operating system). An LF/CR sequence is preferred.

Example of Absence Transactions

 

AA,123456789,01,'''',19980921,AB,SI,1,D,,1


This is an absence transaction record for ID 123456789 on 09-21-1998 for one day of sick leave. Notice that no data was supplied after the appointment type. These fields are all optional.

 

 AA,123456789,'''',001123,19980921,AB,SI,5.75,H 


This is an absence record for ID 123456789 on 09-21-1998 for 5.75 hours of sick leave. In this transaction, the location code is used to determine the job rather than the job number.


Example of Attendance Transactions

 

AA,123456789,'''',001123,19980928,AT,SB,.5,D,50.55,1,'''','''','''',N


This is an attendance record for ID 123456789. The attendance was for half a day and it is not to be posted to UPDCAL. The job to post to will be determined by the location code and the unit amount (if necessary).

 

AA,123456789,'''',111222,19981031,AT,AT,5,H,'''','''','''','''',123456 


This is an attendance record for ID 123456789 on 10-31-1998. The attendance was for 5 hours and may be posted to UPDCAL using the XREF code for charging the pay account.

 

 AA,123456789,'''',111222,19981031,AT,AT,5,H,'''','''','''','''',1231234123123412345612312123 


This transaction will have the same affect as the previous transaction except it will be using the budget account supplied for pay account charging.

 

AA,123456789,'''',111222,19981101,AT,SB,1,D,50.00,'''',987654321


This transaction will post an attendance record for one day. The sub for ID was supplied, so the user will have the option of charging this attendance off to the absentee's regular pay account. At run-time, the user will be asked if they wish to charge the default pay accounts or the regular employee's pay accounts.


Example of Attendance/UPDCAL Transactions

 

AA,123456789,1,,20120514,AT,AT,5,H,,,,,0011100112000000000000000000,Y,,MIS,2,Y,SUB,,Y


This transaction will post an attendance record for ID 123456789 on 05/14/2012. The attendance is for 5 hours. The pay information will be posted to UPDCAL with the pay type of MIS if the "Post to UPDCAL Current, Future, None:" flag is set to Y. The sub for ID was not supplied therefore, the listed pay account on the csv file will be charged. The board projection flag is set to Y therefore the benefits will be charged to the correct benefit account accordingly.

 

AA,987654321,01,,20120121,AB,DO,4.0,H,,,,,,,4.0,DCK


This transaction will post an absence dock ATDSCN record of 4 hours for ID 987654321 on 01/21/2012. The information will be posted in UPDCAL as a DCK pay type if the user selected Y in the Post to UPDCAL option in the USPIMPORT setup screen.





  • No labels