What does the third-party import do?

You run an import from a legacy system or third-party product to populate master or transaction data in the format that e-timecard requires. The import file must be a comma-delimited ASCII file that you create from your product. Each line in the ASCII file represents a single record, with each record delimited by a <CR>. Columns left blank must still have a comma to delimit them. You can find detailed file specifications in the online JAMIS e-timecard table definitions.

Warning: No one can be logged into e-timecard when you run the interface from a third-party product.

The following table shows the e-timecard master files that the full import process updates as well as what happens on subsequent imports.

e-timecard master files
File name	Description	Subsequent imports
LDEDCD	Earning code master	Synchronized
LDEMPT	Employee type table	Loaded on initial import only
LDEDEM	Employee earning codes	Synchronized
LDEMPL	Employee master	Synchronized
JCORG9	Organizational unit	Reloaded each import
JCJOBM	Job master	Reloaded each import
JCCTLC	Contract labor categories	Reloaded each import
JCCLAS	Cost classes	Reloaded each import
JCCELM	Cost elements	Reloaded each import
JCCLCE	Contract labor category mapping	Reloaded each import
JCTML1	Time and materials level 1	Reloaded each import
JCTML2	Time and materials level 2	Reloaded each import
JCTML3	Time and materials level 3	Reloaded each import
JCTML4	Time and materials level 4	Reloaded each import
GLACCT	General ledger accounts	Creates a hard coded suspense account
CMWBSN	Contract management work breakdown structure number	Synchronized

Hint: Before you run an import from a third-party product, make sure that the permission granted on the input directory is sufficient to allow access to the import program.