W3EB_DEPBEN_VW

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	EMPLID	Character(11)	VARCHAR2(11) NOT NULL	Employee ID Prompt Table: PERSON
2	DEPENDENT_BENEF	Character(2)	VARCHAR2(2) NOT NULL	Dependent Benefit 01=default Default Value: 01
3	NAME	Character(50)	VARCHAR2(50) NOT NULL	Name
4	NAME_AC	Character(50)	VARCHAR2(50) NOT NULL	Alternate Character Name
5	SAME_ADDRESS_EMPL	Character(1)	VARCHAR2(1) NOT NULL	Same Address as Employee Y/N Table Edit Default Value: N
6	RELATIONSHIP	Character(2)	VARCHAR2(2) NOT NULL	Relationship to Employee Default Value: O
7	DEP_BENEF_TYPE	Character(1)	VARCHAR2(1) NOT NULL	Dependent Beneficiary Type B=Beneficiary C=COBRA Dependent Only D=Dependent E=QDRO Estate N=None O=Both Q=QDRO Representative - Employee R=QDRO Representative -Recipient
8	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: S
9	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. */
10	SEX	Character(1)	VARCHAR2(1) NOT NULL	Gender F=Female M=Male U=Unknown X=Indeterminate/Intersex/Unspec Default Value: M
11	BIRTHDATE	Date(10)	DATE	Date of Birth