Output Data Produced by TCD Systems

The TCD system produces the following output data to be passed to Time and Labor:

#	Table	Notes
1.	Punched Time Interface	Contains punched time transactions.
2.	Punched Task Interface	Contains punched task transactions related to punched time transactions (child of Punched Time).
3.	Elapsed Time Interface	Contains elapsed time transactions (such as Sick, Vacation, Holiday, and so on).
4.	Elapsed Task Interface	Contains elapsed task transactions related to elapsed time transactions (child of Elapsed Time).

Time and Labor receives this data through PeopleSoft Integration Broker.

The first step is to validate the information sent by the TCD. This includes standard format edits. This data may also come into Time and Labor through a flat file.

The next step is to translate Badge IDs to EmplIDs and create Reported Time entries.

The last step is to initiate the Validation process, which takes the data to the next step.

Because a time reporter can report time at more than one TCD, Time and Labor must be able to accept data for a time reporter from multiple sources at the same time.

Punched Time Interface

The Punched Time data structure contains punched time transactions. The majority of time transactions are written to this data structure.

#	Data Element	Type	Length	Required	Notes
1	Badge ID	Char	20	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
2	Empl ID	Char	11	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
3	Empl RCD#	Num	3	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
4	Punch Date Time	DateTime	See Interface Specifications in Using Time Collection Devices	N	Identifier. This field is required if the Add/Delete indicator is A.
5	Delete Date	Date	10	N	Indicates the Date for an Add/Delete indication of D. This field is required if the Add/Delete indicator is D.
6	Punch Type	Char	1	N	1 = In, 2 = Out, 3 = Meal, 4 = Break, 5 = Transfer. This field is required if the Add/Delete indicator is A.
7	TCD ID	Char	10	Y	Indicates which TCD time transaction came from.
8	Time Zone	Char	9	N	EST, PST, MST, and so on
9	Supervisor ID	Char	20	N	Can be blank − Supervisor ID who did the override.
10	User ID	Char	8	N	Can be blank − User ID who did the override.
11	Override Reason Code	Char	5	N	Can be blank − Reason code for the override.
12	Add/Delete Indicator	Char	1	N	Can be blank − A = Add, D = Delete
13	Action Date/Time	DateTime	See Interface Specifications in Using Time Collection Devices	N	Can be blank − Date and Time when override occurred.
14	Task Profile ID	Char	10	N	Can be blank − override or positively reported.
15	Task Template ID	Char	10	N	Can be blank − Task Template used when positively reported.
16	Country	Char	3	N	Override Country
17	State	Char	6	N	Override State
18	Locality	Char	10	N	Override Locality
19	Comments	Char	254	N

The TCD system can send either Badge IDs or Empl ID/Empl Rcd#. Time and Labor translates Badge IDs to EmplIDs.

Note: If the correctEmpl Rcd # is not set up for a clock badge type on the Badge page in Workforce Administration for an employee, the Time and Labor TCD Integration assigns all time to Empl Rcd = 0 when it processes messages converting Badge to Emplid/Empl Rcd.

See Badge Page.

Time and Labor obtains the time zone from the TCD definition if the time zone does not come in on this record.

Time and Labor compares the Task Template ID on the Punched Time record to the Task Template ID on the Time Reporter's Taskgroup. If the Task Template IDs do not match, then Time and Labor assumes Taskgroup borrowing has occurred and finds a Taskgroup that contains the Task Template ID.

Time and Labor compares the Task Profile ID on the Punched Time record to the Task Profile IDs attached to the Time Reporter's Taskgroup. If the Task Profile IDs do not match, then the system assumes Taskgroup borrowing has occurred and finds a Taskgroup that contains the Task Profile ID.

Time and Labor creates an Audit record if the Supervisor ID on the record is not blank. The audit record will have a generic "Override at TCD" reason.

For Country, State and Locality, Time and Labor uses the values on the interface if present. If not present, the system checks the TCD definition to see if these values are specified at the TCD. If they are, Time and Labor uses the TCD definition values. In either case, the system compares these values to the Time Reporter's values in HR. Time and Labor uses these values as overrides on Reported Time if there is a difference.

In general, PeopleSoft recommends that the deletion and replacement of punches be done online in Time and Labor. However, the Add/Delete Indicator in the Punch Interface provides delete/replace functionality on the day level for an employee. Individual punches cannot be deleted through the interface, and a replacement is a delete of a day and then an add of what the day should be. For this to occur, the TCD must maintain an image of that day, so corrected punches could be sent with the whole day. When a delete is processed in the PeopleSoft system, punch date times are evaluated in the time zone in which they were reported. Here is an example of deleting a punch.

Employee 1 has the following punches on 1/1/99, and these punches have already been sent to Time and Labor:

EMPLID	PUNCH_DATETIME	PUNCH_TYPE	Add/Delete Indicator
1	1/1/99 8AM	IN	A
1	1/1/99 12PM	MEAL	A
1	1/1/99 1PM	IN	A
1	1/1/99 5PM	OUT	A

Someone at the TCD decides that the 12PM MEAL punch and 1PM IN punch need to be deleted because the employee didn't take lunch.

These are the rows Time and Labor should receive in the interface (the time on a deleted row is irrelevant):

EMPLID	PUNCH_DATETIME	DELETE_DATE	PUNCH_TYPE	Add/Delete Indicator
1		1/1/99		D
1	1/1/99 8AM		IN	A
1	1/1/99 5PM		OUT	A

Here is an example of replacing a punch.

Employee 2 has the following punches on 1/1/99, and these punches have already been sent to Time and Labor:

EMPLID	PUNCH_DATETIME	PUNCH_TYPE	Add/Delete Indicator
2	1/1/99 8 AM	IN	A
2	1/1/99 12 PM	MEAL	A
2	1/1/99 1 PM	IN	A
2	1/1/99 5 PM	OUT	A

Someone at the TCD decides that the 1PM IN punch should be a 2PM IN punch because Employee 2 really took a two hour lunch.

These are the new rows Time and Labor should receive in the interface:

EMPLID	PUNCH_DATETIME	DELETE_DATE	PUNCH_TYPE	Add/Delete Indicator
2		1/1/99		D
2	1/1/99 8AM		IN	A
2	1/1/99 12PM		MEAL	A
2	1/1/99 2PM		IN	A
2	1/1/99 5PM		OUT	A

Punched Task Interface

The Punched Task data structure contains punched task transactions related to a punched time transaction.

_#	Data Element	Type	Length	Required	Notes
1	Badge ID	Char	20	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
2	Empl ID	Char	11	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
3	Empl RCD#	Num	3	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
4	Punch Date Time	DateTime	See interface specifications in Using Time Collection Devices	Y	Identifier.
5	Delete Date	Date	10	N	Always is Null
6	Task Element Code	Char	3	Y	Only for positive task element reporters.
7	Task Element Value	Char	25	Y	Only for positive task element reporters.

The TCD system can send either Badge IDs or Empl ID/Empl Rcd#. Time and Labor translates Badge IDs to EmplIDs.

The TCD also passes Rule Elements on this table. Rule Elements look similar to task elements. Time and Labor distinguishes them by the element code and splits out rule elements into specific fields on the reported time record.

Mapping of task element codes may need to occur if the TCD can only process numeric values.

Only punch types of IN and Transfer should produce Punched Task records.

Elapsed Time Interface

The Elapsed Time data structure contains elapsed time transactions reported at the TCDs (such as tip, vacation, sick, holiday, and so on):

#	Data Element	Type	Length	Required	Notes
1	Badge ID	Char	20	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
2	Empl ID	Char	11	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
3	Empl RCD#	Num	3	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
4	Date Under Report	Date	10	N	Identifier (CCYY-MM-DD). This field is required if the Add/Delete indicator is A.
5	Sequence Number	Num	3	Y	Identifier to make each row unique.
6	Delete Date	Date	10	N	Indicates the Date for an Add/Delete indication of D. This field is required if the Add/Delete indicator is D.
7	Add/Delete Indicator	Char	1	Y	A/D, Default = A.
8	TCD ID	Char	10	Y	Indicates which TCD time transaction came from.
9	Time Reporting Code	Char	5	Y	TCD vendors may need to convert numeric code to character code.
10	Quantity	Num	12.6	Y	This field can represent hours (in hours and tenths), amount, or units.
11	Currency Code	Char	3	N	An optional currency code for when the quantity represents money.
12	Pay Rate Override	Num	12.6	N	Can be zero. If populated, it will be used to calculate time reporter's pay.
13	Rate Code Override	Char	6	N	Override Rate Code
14	Billable Indicator	Char	1	Y	Billable Indicator for use in pay calculations (Y/N) Default=N.
15	Supervisor ID	Char	20	N	Can be blank − Supervisor ID who did the override.
16	User ID	Char	8	N	Can be blank − User ID who did the override.
17	Override Reason Code	Char	5	N	Can be blank − Reason code for the override.
18	Action Date/Time	Date Time	See interface specifications in Using Time Collection Devices	N	Can be blank − Date and Time when override occurred.
19	Task Profile ID	Char	10	N	Can be blank − override or positively reported.
20	Task Template ID	Char	10	N	Can be blank − Task Template used when positively reported.
21	Country	Char	3	N	Override Country
22	State	Char	6	N	Override State
23	Locality	Char	10	N	Override Locality
24	Comments	Char	254	N

The TCD system can send either Badge IDs or Empl ID/Empl Rcd#. Time and Labor translates Badge IDs to EmplIDs.

Time and Labor assumes the currency code attached to the Time Reporting Code definition unless a currency code comes in on this record.

Time and Labor compares the Task Template ID on the Elapsed Time record to the Task Template ID on the time reporter's Taskgroup. If the Task Template IDs do not match, then the system assumes Taskgroup borrowing has occurred and finds a Taskgroup that contains the Task Template ID.

Time and Labor compares the Task Profile ID on the Elapsed Time record to the Task Profile IDs attached to the time reporters' Taskgroup. If the Task Profile IDs do not match, then the system assumes Taskgroup borrowing has occurred and finds a Taskgroup that contains the Task Profile ID.

Time and Labor creates an Audit record if the Supervisor ID on the record is not blank. The audit record has a generic "Override at TCD" reason.

For Country, State and Locality, Time and Labor uses the values on the interface if present. If not present, the system checks the TCD definition to see if these values are specified at the TCD. If they are, the system uses the TCD definition values. In either case, Time and Labor compares these values to the time reporter's values in HR. The system uses these values as overrides on Reported Time if there is a difference.

In general, PeopleSoft recommends that the deletion and replacement of elapsed time records be done online in Time and Labor. However, the Add/Delete Indicator in the Elapsed Time Interface provides delete/replace functionality on the day level for an employee. Individual elapsed time records cannot be deleted through the interface. A replacement is a delete and then an add of what the day should be. For this to occur, the TCD must maintain an image of that day, so corrected elapsed time records could be sent with the whole day.

Here is an example of deleting an elapsed time record.

Employee 1 has reported the following time on 1/1/99, and these records have already been sent to Time and Labor:

EMPLID	DUR	SEQNUM	TRC	TL Quantity	Add/Delete Indicator
1	1/1/99	1	REG	8	A
1	1/1/99	2	OT	2	A

Someone at the TCD decides that the OT record was mistakenly reported and should be deleted.

These are the rows Time and Labor should receive in the interface:

EMPLID	DUR	SEQNUM	DELETE_DATE	TRC	TL Quantity	Add/ Delete Indicator
1			1/1/99			D
1	1/1/99	1		REG	8	A

Here is an example of replacing an elapsed time record.

Employee 2 has reported the following time on 1/1/99, and these records have already been sent to Time and Labor:

EMPLID	DUR	SEQNUM	TRC	TL Quantity	Add/Delete Indicator
2	1/1/99	1	REG	8	A
2	1/1/99	2	OT	2	A

Someone at the TCD decides 3 hours of OT were worked instead of the 2 that were reported.

These are the rows Time and Labor should receive in the interface:

EMPLID	DUR	SEQNUM	DELETE_DATE	TRC	TL Quantity	Add/Delete Indicator
2			1/1/99			D
2	1/1/99	1		REG	8	A
2	1/1/99	2		OT	3	A

Elapsed Task Interface

The Elapsed Task data structure contains elapsed task transactions related to each elapsed time transaction.

_#	Data Element	Type	Length	Required	Notes
1	Badge ID	Char	20	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
2	Empl ID	Char	11	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
3	Empl RCD#	Num	3	N	The TCD must send either Badge ID or Empl ID/Empl Rcd#.
4	Date Under Report	Date	10	Y	Identifier (CCYY-MM-DD)
5	Sequence Number	Num	3	Y	Identifier to make each row unique.
6	Delete Date	Date	10	N	Always is Null
7	Task Element Code	Char	3	Y	Only for positive task element reporters.
8	Task Element Value	Char	25	Y	Only for positive task element reporters.

The TCD system can send either Badge IDs or Empl ID/Empl Rcd#. Time and Labor translates Badge IDs to EmplIDs.

The TCD also passes Rule Elements on this table. Rule Elements look similar to task elements. Time and Labor distinguishes the difference by the element code and splits out rule elements into specific fields on the Recorded Time record.

Mapping of task element codes may need to occur if the TCD can only use numbers.

Report counts of the various objects attached to the TCD includes counts of Time Reporters, TCD Restriction Profiles, Task Profiles, Task Templates, Task Elements, Task Element Values, Time Reporting Codes, Supervisors, Rule Elements, and Rule Element values. Use this report to monitor memory usage at the TCD.