...

...

Introduction

When importing data from classic USPS into USPS-R there are three levels of messages that can be written to the log file.

...

• This error indicates there were orphaned records with invalid ASCII values in the pay counter field discovered in the classic USPFUTPAY.IDX file. It is unclear what caused classic to leave these orphaned records in the file, but this seems to be a common occurrence. They did not show up in the UPDCAL_FUT UI and were ignored by the classic system. The records can be reviewed in the extract file or using datatrieve, however since they were "invisible" for all intents and purposes in classic we assume they can be excluded from the import without negative repercussions.

PayrollItemConfigImportImpl:payrollitem: Line XX: MED/FICA type not found for deduction code 69X

• This error may happen if there is a DEDNAM record in Classic for a MEDFICA type deduction code that has no employee records attached to determine whether it is a Medicare or FICA type. If there are no employees currently attached to the deduction then the Payroll Item Configuration record may not be necessary.

Warnings

PayrollItemConfigImportImpl: payrollitem: The vendor number () for the PayrollItemConfiguration being imported (code: XXX, type: ) does not match the Payee PayrollItemConfigurationType ([]) or the 'Pay To' information.  Creating a new Payee for the PayrollItemConfiguration.

• This is actually a warning/informational message and does not result in any data being excluded from import. Basically, this is a side effect of the fact that we created the concept of a payee in USPS-R where as all the payee information (vendor number, address etc.) was stored directly on DEDNAM. . 

PositionImportImpl: position: Pay Per Period () entered does not equal Pay Per Period calculated based upon contract values () for employee:

• This is also just a warning message. The district can review these if they choose to. It is telling you that when we calculated what we think the pay per period should be based on the contract values at import does not match what the district has in the pay per period field for the contract. We use whatever the district has entered, so the imported data will match classic. 

...