HRS_EFFDT_HST

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	PSARCH_ID	Character(8)	VARCHAR2(8) NOT NULL	Archive ID (see PSARCHTEMPLATE).
2	PSARCH_BATCHNUM	Number(30,0)	DECIMAL(30) NOT NULL	Archive Batch Number
3	HRS_PERSON_ID	Number(15,0)	DECIMAL(15) NOT NULL	Person Id
4	EFFDT	Date(10)	DATE	Effective Date Default Value: %date
5	END_EFFDT	Date(10)	DATE	End Effdt
6	MAR_STATUS	Character(1)	VARCHAR2(1) NOT NULL	Marital Status C=Common-Law D=Divorced E=Separated H=Head of Household L=DissDeclLost Civil Partner M=Married P=Civil Partnership S=Single T=Surviving Civil Partner U=Unknown V=Dissolved Civil Partnership W=Widowed Default Value: U
7	MAR_STATUS_DT	Date(10)	DATE	This is the date that the employee's Marital status is/was effective. /* Marital Status date is stored redundantly on PERS_DATA_EFFDT for two reasons. 1. To allow the date to be entered prior to the first PERS_DATA_EFFDT so that the actual date for the marital status on the hire row can be entered. This is the only time that the field is enterable by the user. 2. To allow for easier reporting on the data via SQR and Crystal. This is denormalizing the PERS_DATA_EFFDT record, but the number of requests for this redundancy coupled with the need for #1, has provided the justification for denormalizing this information and taking on the added maintenance. */
8	HRS_ROW_ADD_DTTM	DateTime(26)	TIMESTAMP	Row Added DateTime
9	HRS_ROW_ADD_OPRID	Character(30)	VARCHAR2(30) NOT NULL	Row Added Operator Id
10	HRS_ROW_UPD_DTTM	DateTime(26)	TIMESTAMP	Row Updated DateTime
11	HRS_ROW_UPD_OPRID	Character(30)	VARCHAR2(30) NOT NULL	Row Updated Operator Id