Solicitation Attachment 9 - Solicitation PWS Reference 007-IPPS-A PMO Data Dictionary-26 OCT 2023.xlsx

IPPS-A Data Dictionary Cover

Updated Draft REF Data tab with updated content from PLT

Updated IPPS-A Page Details Updated Mapping Repository with IDD content Updated Draft REF Data tab with updated content from PLT Updated Schema 3.x tab

Updated DIV-2 to DIV-3 Updated Mapping Repository with IDD content Updated Draft REF Data tab with updated content from PLT

Updated Mapping Repository with IDD content Updated Draft REF Data tab with updated content from PLT

Updated Mapping Repository with IDD content Updated Draft REF Data tab with updated content from PLT Updated IPPS-A Page Details Updated Legacy Systems Updated DIV-2 to DIV-3 Updated ALL Inbound Lineage Updated IRS to Outbound Topic Mapping Updated Schema 3.x

Updated Draft REF Data tab with updated content from PLT Updated Schema 3.x

Updated Draft REF Data tab with updated content from PLT Updated Schema 3.x with additional definitions

Updated Draft REF Data tab with updated content from PLT Updated Schema 3.x with additional definitions

Updated Draft REF Data tab with updated content from PLT Updated Schema 3.x with additional definitions

Table Definitions

Release 9 Job Profile Managment (JPM): Table became a view to JPM data. Ownership of table transferred from Human Resources to JPM.

20220401 HCM ACCOMP_TBL View Accomplishment Table PS_ACCOMP_TBL As of HCM 9.0 This table has become a view to Job Profile Managment Items where accomplishments are now stored.

The ACCOMP_TBL contains all your organizations accomplishments. Accomplishments are:

1) languages

2) degrees

3) licenses or certificates

4) honors or awards

5) professional memberships or

6) tests 7)NVQs (UK only) that your employees, applicants or contractors may achieve.

The ACCOMPLISHMENT field must be unique across all these accomplishment types. The field ACCOMP_CATEGORY identifies the accomplishment as one of the above listed cateories.

20220401 HCM ACCOM_OPTION Table EE Accommodation Options PS_ACCOM_OPTION U.S. only.

ACCOM_OPTION is part of a set of records used to record data for compliance with the Americans with Disabilities Act (ADA). A disabled employee or applicant can request that an employer make an accommodation for their disability so they can perform their job tasks adequately.

Use ACCOM_OPTION to record the various options available for accommodating this person's disability. ACCOM_OPTION is subordinate to ACCOM_REQUEST.

You can create multiple ACCOM_OPTION records for a person.

20220401 HCM ACCOM_REQUEST Table EE Accommodation Requests PS_ACCOM_REQUEST U.S. only.

ACCOM_REQUEST is part of a set of records used to record data for compliance with the Americans with Disabilities Act (ADA). A disabled employee or applicant can request that an employer make an accommodation for their disability so they can perform their job tasks adequately.

Use ACCOM_REQUEST to record summary information about this person's request for an accommodation.

You can create multiple ACCOM_REQUEST records for a person.

20220401 HCM ACCOM_TYPE_TBL Table Accommodation Type Codes PS_ACCOM_TYPE_TBL U.S. only.

ACCOM_TYPE_TBL is part of a set of records used to record data for compliance with the Americans with Disabilities Act (ADA). A disabled employee or applicant can request that an employer make an accommodation for their disability so they can perform their job tasks adequately.

ACCOM_TYPE_TBL is an edit table. Use it to record accommodation type codes and descriptions. For example, an accommodation for a person in a wheelchair might be to build a wheelchair ramp.

If the row is defined as SYSTEM_DATA then the user can only change the EFF_STATUS and the DESCR, DESCRSHORT.

Customers can add their own Actions.

20220401 HCM ACTION_TBL Table ACTION Setup Table PS_ACTION_TBL Contains all the ACTIONS that are possible to be applied to a JOB row.

If the row is defined as SYSTEM_DATA then the user can only change the EFF_STATUS and the DESCR, DESCRSHORT.

Customers can add their own Actions.

20220401 HCM ACTN_REASON_TBL Table Action/Reason Combinations PS_ACTN_REASON_TBL ACTN_REASON_TBL is an edit table. Use it to record combinations of action codes and the reason codes that are valid for an action.

For example, two valid reasons for a termination action might be attendance and misconduct.

20220401 HCM ACTN_REASON_VW View Current Action/Reasons PS_ACTN_REASON_VW ACTN_REASON_TBL is an edit table. Use it to record combinations of action codes and the reason codes that are valid for an action.

For example, two valid reasons for a termination action might be attendance and misconduct.

For example, two valid reasons for a termination action might be attendance and misconduct.

20220401 HCM ADDL_PAY_DATA Table Additional Pay Detail PS_ADDL_PAY_DATA ADDL_PAY_DATA record stores the additional pay detail required to create additional payline records during paysheet processing.

Warning! The schema for this record, which is shared by Payroll and Benefits, shows that it is keyed by EMPL_RCD. For those rows managed by Benefits Administration (ADDL_REASON="BAS"), this is not logically or functionally accurate. Within the context of benefit enrollment (and by extension, benefits-generated additional pay), EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so for ADDL_PAY rows managed by Benefits the EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to such rows be against BENEFIT_RCD_NBR.

20220401 HCM ADDL_PAY_EFFDT Table Add'l Pay Effective Dates PS_ADDL_PAY_EFFDT ADDL_PAY_ERNCD record is the effective dated control record for ADDL_PAY_DATA.

Warning! The schema for this record, which is shared by Payroll and Benefits, shows that it is keyed by EMPL_RCD. For those rows managed by Benefits Administration (ADDL_REASON="BAS"), this is not logically or functionally accurate. Within the context of benefit enrollment (and by extension, benefits-generated additional pay), EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so for ADDL_PAY rows managed by Benefits the EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to such rows be against BENEFIT_RCD_NBR.

You can create multiple ASGN_HOME_HOST records for an employee.

20220401 HCM ASSGN_TYPE_TBL Table Assignment Type Codes PS_ASSGN_TYPE_TBL Use ASSGN_TYPE_TBL to record international assignment types such as foreign service transfer, domestic loan employee, or employer-requested transfer. This data is part of the International Assignment application.

You can create multiple ASSGN_TYPE_TBL records for a single assignment type, each with a unique effective date.

20220401 HCM ASSIGNMENT Table EE Assignments PS_ASSIGNMENT ASSIGNMENT is one of a group of records used to record information about an employee's job assignments away from home base. Use ASSIGNMENT to log high-level data about the assignment. Detail-level data is covered in other records. This data is part of the International Assignment functionality.

You can create multiple ASSIGNMENT records for an employee, each with a unique begin date.

Warning! For technical reasons, this record's schema shows that it is keyed by EMPL_RCD. This is not logically or functionally accurate. Throughout all of Base Benefits, when in the context of benefit enrollment, EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so here EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to this record be against BENEFIT_RCD_NBR. Thus a typical driving join for benefit participation is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_BEN_PROG_PARTIC.EMPL_RCD, and a typical join for benefit enrollment is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_HEALTH_BENEFIT.EMPL_RCD. The security and search views used in Base Benefits perform this "mapping" internally.

20220401 HCM BEN_PRG_PRTC_VW View Vw on BEN_PROG_PARTIC PS_BEN_PRG_PRTC_VW This view has been created on BEN_PROG_PARTIC to get data for payroll processing. The field COBRA_EVENT_ID would have a value of zero for payroll considerations; also the key structure needs to have EMPL_RCD# as the last key field before EFFDT.

The view therefore has been created to meet these requirements.

Warning! For technical reasons, this record's schema shows that it is keyed by EMPL_RCD. This is not logically or functionally accurate. Throughout all of Base Benefits, when in the context of benefit enrollment, EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so here EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to this record be against BENEFIT_RCD_NBR. Thus a typical driving join for benefit participation is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_BEN_PROG_PARTIC.EMPL_RCD, and a typical join for benefit enrollment is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_HEALTH_BENEFIT.EMPL_RCD. The security and search views used in Base Benefits perform this "mapping" internally.

The BN_TOGGLE field is used by Benefits Self Service to force a save. Its value has nothing to do with the other two fields.

Project: REL 3 Description: Added fields EFFDT, EFF_STATUS, LASTUPDOPRID, and LASTUPDDTTM.

Use a combination of CAREERMOVE_TBL and CAREERPATH_TBL to define sequential paths of jobcodes through which an employee can advance from their present jobcode. Use CAREERMOVE_TBL to set up each 'move' from a jobcode. For example, move #1 would be the next job after their current one, and move #2 would be the next one after that.

Use CAREERPATH_TBL to set up the lower layer of 'options' for each move on CAREERMOVE_TBL. If the desired career path is a strict hierarchy, there will be only one option for each move. If there is more than one choice for each move, then multiple options can be entered. The option sequence number can be filled in if there is a particular order to the options, in terms of first and second choice or likelihood to occur. This data is part of the Career Planning module.

CAREERMOVE_TBL must be set up before you enter data in CAREERPATH_TBL.

20220401 HCM CAREERPATH_TBL Table Career Path Table - Job Code PS_CAREERPATH_TBL IPPS-A: Matt Blunt, 11/21/2019 Project: REL 3 Description: Added fields EFFDT, EFF_STATUS, LASTUPDOPRID, and LASTUPDDTTM.

Use a combination of CAREERMOVE_TBL and CAREERPATH_TBL to define sequential paths of jobcodes through which an employee can advance from their present jobcode. Use CAREERMOVE_TBL to set up each 'move' from a jobcode. For example, move #1 would be the next job after their current one, and move #2 would be the next one after that.

Use CAREERPATH_TBL to set up the lower layer of 'options' for each move on CAREERMOVE_TBL. If the desired career path is a strict hierarchy, there will be only one option for each move. If there is more than one choice for each move, then multiple options can be entered. The option sequence number can be filled in if there is a particular order to the options, in terms of first and second choice or likelihood to occur. This data is part of the Career Planning module.

CAREERMOVE_TBL must be set up before you enter data in CAREERPATH_TBL.

20220401 HCM CITIZENSHIP Table EE/Dependent Citizenship PS_CITIZENSHIP Use CITIZENSHIP to record an employee's or dependent's country of citizenship. You can enter related passport data on CITIZEN_PSSPRT.

/* IP_HIREREHIRE_01 -- SMARWAHA - 02/28/2017 */

Changed prompt view from COUNTRY_TBL to a view IP_CNTRY_CTZ_VW

This table was created in release 8.0

CITIZEN_STS_LNG table is the related language table for CITIZEN_STS_TBL.

20220401 HCM CMP_RULE_AFT_WS Table Default Rule Fields Workscroll PS_CMP_RULE_AFT_WS Defaulting Rule Fields Workscroll, containing the record fields available for the Defaulting Rules.

The Workscroll is used in Job Data to load the Job fields and their values (in derived fields) at save time, AFTER the Job Data component is modified. That allows to determine at save time if a warning should be issued to click the Compensation Defaulting button.

20220401 HCM CMP_RULE_BEF_WS Table Default Rule Fields Workscroll PS_CMP_RULE_BEF_WS Defaulting Rule Fields Workscroll, containing the record fields available for the Defaulting Rules.

The Workscroll is used in Job Data to load the Job fields and their values (in derived fields) BEFORE the Job Data component is modified. That allows to determine at save time if a warning should be issued to click the Compensation Defaulting button.

Used as a prompt on JOB_DATA to get the Active Contracts per Emplid.

Release 9 Job Profile Managment (JPM): Table became a view to JPM data. Ownership of table transferred from Human Resources to JPM.

Effective Dated to store different types of Course Descriptions 20220401 HCM COURSE_EQUIP Table Training Course Equipmt Needs PS_COURSE_EQUIP Use COURSE_EQUIP to specify the equipment and materials needed to conduct a particular training course. This record belongs to the Training Administration application.

You can create multiple COURSE_EQUIP records for a course, each with a unique equipment code.

You can create multiple COURSE_LANGUAGE records for a course, each with a unique Language code.

20220401 HCM COURSE_LICENSE Table Training Course Goal-Licenses PS_COURSE_LICENSE Use COURSE_LICENSE to specify professional licenses or certifications that a particular training course is training students for. This record belongs to the Training Administration application.

You can create multiple COURSE_LICENSE records for a course, each with a unique license/certification code.

20220401 HCM COURSE_TBL Table Training Courses PS_COURSE_TBL Use COURSE_TBL to record data about training courses you want to track in your database. This record contains high-level information about a course; specific information about course 'sessions' is found in other records such as CRSE_SESSN_TBL, CRSE_SESSN_COST, and CRSE_SESS_INSTR. These records belong to the Training Administration application.

You can create only one COURSE_TBL record per course code.

Project: IP_AWE_01 Epic: Workflow: GVT_DESCR40 added as alt search key

05/24/99 The HRMS DEPT_TBL definition has been synchronized with the ERP definition. Any changes made to the HRMS definition must be made to ERP definition.

Use DEPT_TBL to record information about the organizational entities in your company. Data also includes description, company code, location, and budget fields. Assign a DEPTID to each department, division, region, etc. which is used in your organizational hierarchy. The Tree Editor is used to build a hierarchy of these codes, and to identify and group them into the appropriate organizational levels.

Department ID is used as the primary organizational identifier on payroll earnings records. It is also used as the basis for implementing organizational security for employee data.

You can create multiple DEPT_TBL records for a department, each with a unique effective date.

NMORRIS IPPS-A 01/14/2020: Added IP_DECEASED, MILITARY_SERVICE, & MIL_RANK fields for Dependent Beneficiary Personal Profile page as part of DD93 Development and DEERS inbound interface.

NMORRIS IPPS-A 09/06/18 Form DD93 - Commented out one line to keep Benefit Type from changing when Relationship is changed. DEERS interface/DD93 requirement.

NMORRIS IPPS-A 09/06/18 Form DD93 - Added default value of "U" for DEP_BENEF_TYPE.

EPIC: AWOL/Confined R3 Descr: Added DS Attribute & Sub-Attribute fields & EXEMPT_DIS

IPPS-A 09-AUG-2016 Star Straf Project: IP_DUTYSTS_02_014 Added END_DT for Duty Status tracking DUTY STATUS Task 19 Create Crosswalk Table /* End IPPS-A */

Use DISCIPLIN_ACTN to record high-level data about disciplinary actions taken against an employee. The detailed disciplinary steps are recorded in a subordinate record named DISCIPLIN_STEP.

You can create more than one DISCIPLIN_ACTN record for an employee.

20220401 HCM DISCIPLIN_LTR Table Disciplinary Action Letter PS_DISCIPLIN_LTR IPPS-A 09-AUG-2016 Raj Subbiah Project: IP_DISCIPL_ACT_05 Changed Letter code default to "DAF" /* End IPPS-A */

Disciplinary Action Letter 20220401 HCM DISCIPLIN_STEP Table EE Disciplinary Action Steps PS_DISCIPLIN_STEP IPPS-A 01-JUL-2020 MLy EPIC: AWOL/Confined R3 Descr: Added DS Attribute & Sub-Attribute fields

IPPS-A 09-AUG-2016 Star Straf Project: IP_DUTYSTS_02_014 Added END_DT for Duty Status tracking DUTY STATUS Task 19 Create Crosswalk Table /* End IPPS-A */

IPPS-A Sunder Lingareddy - R3 Changed the default on SEQNUM to 1 to keep the PAR transactions in sync.

Use DISCIPLIN_STEP to record the particular steps involved in a disciplinary action taken against an employee. The high-level information on a disciplinary action is recorded in the parent record named DISCIPLIN_ACTN.

You can create more than one DISCIPLIN_STEP record for each disciplinary action taken against an employee.

20220401 HCM DISCIP_STEP_TBL Table Disciplinary Action Step Codes PS_DISCIP_STEP_TBL Use DISCIP_STEP_TBL to identify specific steps that can be taken in disciplinary actions against employees. This is an edit table.

You can create multiple DISCIP_STEP_TBL records, each with a unique effective date.

20220401 HCM DISCIP_TYPE_TBL Table Disciplinary Action Type Codes PS_DISCIP_TYPE_TBL Use DISCIP_TYPE_TBL to identify disciplinary actions that can be taken against employees. This is an edit table.

You can create multiple DISCIP_TYPE_TBL records, each with a unique effective date.

You can create multiple DRIVERS_LIC records for an employee if they have more than one license.

You can create multiple EMERGENCY_CNTCT records for an employee.

Date: 04/08/2021 Developer: Jody Nabors

CSR#: HCM-4526

PS Project: IP_SCRTY_IP_GRD_JFM_GBL Epic: Application Security Description: Implement the Security Access Types 100/101 (mainly by adding the IP_SCRTY_WHERE_IP_GRD_JFM SQL object to incorporate IP_GRD_JFM/100 and 101).

EMPLMT_SRCH_GBL is an Employment Search record containing all of the localized alternate search keys. None of the localized search keys are maked as alternate searches. However, it's easy for a customer to mark any/all of them as alternate search keys if they choose to.

Use it to select person records for a specific EMPL_RCD (ERN) for you to use when you access a panel. This view shows you records only for persons in departments that your operator class is allowed to access.

Use this view to access records with primary keys of EMPLID and EMPL_RCD#. To access records keyed by EMPLID without EMPL_RCD#, use one of ther Personal Searches.

20220401 HCM EMPLOYEES Table Non terminated Employees PS_EMPLOYEES EMPLOYEES is a table populated by PER099 AppEngine process.

It is a snapshot of emploees' personal/demographic data, employment data, and job/salary data as of the date indicated when the program is run.

This table is primarily for reporting. Only employees with EMPL_STATUS (A,P,L,S,W) are included with all their EMPL_RCDs and the most current JOB row as of the ASOFDATE.

Use ESTAB_TBL to record company data needed to produce an EEO-1 employer information report, if required, to meet U.S. government equal employment opportunity reporting requirements.

PeopleSoft's standard report PER016 is the EEO-1 report.

You should create a separate record for each 'establishment' in your company. You must designate one establishment as the 'headquarters unit'.

A view W3PY_W4_FTX_VW based on this record has been created for the purpose of WEB-enabled W4 update. Changes made to the record FED_TAX_DATA would need to be analyzed and made to W3PY_W4_FTX_VW, if necessary.

20220401 HCM FORM Table Form PS_FORM Form Instance Entered by the end user

IPPS-A - Ken Quick - 01/31/2021 - SPR4771 Replaced custom fields with the IP_FORM_SBR subrecord.

Form Type field

1) search edit on

2) no prompt defined