This workflow details the campus steps to complete the Labor Cost Distribution (LCD) process.
Run CSU Load SCO Pay Tape
This step loads your campus' own pay tape data to begin processing LCD.
Systemwide Human Resources (SWHR) loads the centralized SCO Pay Tape for ALL campuses (even non-CHRS campuses) as early as possible for each pay period. Once SWHR has loaded the current pay tape, a listserv of campus users will receive an email with their campus count.
Note: Campuses are responsible for submitting who on their campus want to be notified of the centralized pay tape load.
Optional: Run CSU Pre Check Audit Report
The purpose of the CSU Pre Check Audit Report is to view potential errors caused by bad or missing data and allow the user to correct these errors prior to running the CSU Create Paycheck Data job. Some of the errors produced in the report are fatal and must be addressed, while others are minor and can be ignored.
This is an optional step; however, it is highly recommended.
Were there any errors reported by the CSU Pre-Check Audit Report?
You must correct any errors before proceeding.
For additional information or assistance with CSU Pre-Check Audit report errors and/or warnings, please refer to the [LCD Troubleshooting Guide].
Does your campus use Time & Labor Earnings Distribution?
Optional Step: Run TL Earnings Distribution
If your campus uses Time & Labor (TL) Earnings Distribution, this step must be run prior to creating CSU Paycheck Data.
This is uncommon.
Run CSU Create Paycheck Data Job
This step (CSULCDCR PSJob) creates the paycheck data in CSU custom tables, but does not yet finalize them.
You will have an opportunity to correct any errors on the CSU Check Errors Correction page or CSU Distribution Override page after running the job.
Note: This process can be backed out.
Run CSU Check Errors Correction
This step is very important as it reflects the errors captured by the previous CSU Create Paycheck Data process on the CSU_CHECK_ERROR table.
It is the campus’ responsibility to clean up ALL errors before moving to the next step.
Are there any paycheck errors that need correction?
Correct the paycheck errors before proceeding.
At a minimum, the Earnings Code and Department must always be supplied.
Additionally, if the error message is "090003 Future Dated Transaction", the Combo Code must also be supplied.
For additional assistance, please refer to the [LCD Troubleshooting Guide].
Run CSU Paycheck Data Finalize Job
Launch the Paycheck Data Finalize Job (CSULCDFN PSJob) to kick off the final CSU Create Paychecks process and the CSU Update YTD Balances process.
Note: This process can be backed out.
Run CSU Distribute Paychecks
This step distributes paycheck data to the appropriate accounts.
Note: This process can be backed out.
Review CSU Distribution Errors
Valid Combo Codes must be supplied before the final journal can be created.
If the Distribution Process was unable to lookup a Combo Code, errors will be collected here.
It is the campus’ responsibility to clean up ALL errors before moving to the next step.
Are there any Paycheck Distribution errors?
Correct any distribution errors before proceeding.
For additional assistance, please refer to the [LCD Troubleshooting Guide].
Optional Step: CSU Distribution Override
A campus may wish to retrieve distribution records and override the Combination Code information before creating the accounting lines — before the final journal is created on HR_ACCTG_LINE, and once the CSU Paycheck Distribution process has completed successfully and all of the CSU Paycheck Distribution Errors have been cleared from the previous step, a final opportunity is provided to manually override LCD default distribution(s).
For the CSU Labor Cost Distribution (LCD) process the, CSU Distribution Override step is optional. Only in certain cases would a campus need to complete this process.
Optional Step: Run CSU Combo Edit Validation
This report can be run at any time — this process compares the Chartfield combinations from the PS Valid Combo Table's most current row of data =< SYSDATE (i.e., ‘today’) against the General Ledger combo edit table rules.
It produces a report that will advise of any Combo Codes that are found invalid by the GL Combo Edit rules.
This step is not required but highly recommended to ensure your combo codes are correct.
Run CSU Actuals General Ledger (GL) Interface
The CSU Actuals General Ledger (GL) Interface process creates the accounting lines that will be published to CFS.
This process requires a live database link to CFS.
Note: This process can be backed out.
Optional Step: Expenditure Adjustments
Run the CSU Export Accounting Lines process
CSU Export Accounting Lines uses Integration Broker to publish HR Accounting Lines from the HCM database to the financials application (CFS).
This process should be run each time a journal is created, either through loading a pay tape and processing LCD, or through processing expenditure adjustments.
The run control launches a PSJOB that runs an SQR and initiates an application engine program. Once this process has been launched, the process instance number of the SQR will be recorded in the PS_HR_ACCTG_LINE.PROCESS_INSTANCE field.
Important Note: This is the point of no return. Once the CSU Export Accounting Lines job has run and the process instance has been populated on HR_ACCTG_LINE, you will no longer be able to back out GL Interface as the HR_ACCTG_LINE entries now exist in both CHRS and CFS.
Please refer to the [LCD Troubleshooting Guide] for instructions on opening ServiceNow tickets with the CHRS and CFS teams to assist with data correction if you need to back out GL interface after having already exported the accounting lines to CFS.
Run the CSU Labor Cost Table Refresh process
This process refreshes the CSU_LABOR_DIST table which powers the Financial Data Warehouse (FDW) Labor Cost Distribution reports.
AFTER the Export Accounting Lines process runs but BEFORE the Labor Cost Table Refresh process runs, the Journal Generation process should be completed in CFS.
Campuses should validate that journal data was populated in the HR_ACCTG_LINE record in CHRS. Only AFTER validating that the journal data was populated, should campuses continue with this step.
Note: This process can be backed out.
Run the CSU Publish LCD Data to FIN process
This step publishes the CSU_LABOR_DIST data to CFS.
The Financial Data Warehouse (FDW) uses this table, along with HR_ACCTG_LINE for all FDW reports regarding LCD.
All Financial Data Warehouse LCD data is pulled from CFS production.
Run CSU ESP Interface
This should be the same value that has been established by the campus as the default for FIRMS financial reporting; this value will be used during FIRMS program derivation by Rule #1.
Data that has been collected, calculated, derived, and stored in the history tables will be extracted and written into flat files in a file format that emulates the legacy data structures.
End of Article