This screen is used to review client monthly liability information for the Client Pay-In System

Error #

Error Message

Data Items

LB001

ADD ACTION: PLEASE ETNER LIABILITY DATES AND AMOUNT
Operator has entered an “A” in either Trans or in one of the Act fields, and screen liability dates and amount fields are open for operator entry.

ACT TRANS

LB002

CHANGE ACTION: UPDATE LIAB BEG AND/ OR LIABILITY END DATES
Operator has entered a “C” in one of the Act fields,and screen liability dates are open for update on the line selected.

ACT TRANS

LB003

LIAB BEG YEAR DOES NOT EXIST ON YEARLY ACCT FOR PRIME ID There is a Yearly Account record for the Prime ID entered, but the Yearly account year is not the same as the year entered in the Liab Beg date. Set up another Yearly account for the next year.

PRIME ID

LB004

LIAB BEG DATE MUST BE AFTER LAST MONTHLY BILLING DATE
A bill for the liability has been sent to the client on or after the Liab Beg date. Enter a date which falls after the monthly billing date.

LIAB BEG

LB005

LIAB END DATE CANNOT BE BEFORE LAST MONTHLY BILLING DATE
A bill for the liability has been sent to the client after the Liab End date. Enter a date which is the same as or is after the monthly billing date.

LIAB END

LB006

LIAB BEG DATE INVALID. ENTER VALID MM/O1/CCYY DATE
Date must be in MM/01/YYYY format with month, day and year numeric, and day as FIRST day of month.

LIAB BEG

LB007

LIAB END DATE INVALID. ENTER VALID MM/O1/CCYY DATE
Date must be in MM/##/YYYY format with month, day and year numeric, and day as LAST day of month.

LIAB END

LB008

LIAB AMT INVALID. ENTER A NUMERIC AMOUNT GREATER THAN ZERO
The liability amount must be numeric and greater than zero.

LIAB AMT

LB009

LIAB BEG DATE CHANGED TO FIRST DAY OF MONTH
A warning message to notify the data entry person of an automatic change made to the Liab Beg date. The Liab Beg date must always be the first day of the month.

LIAB BEG

LB010

LIAB BEG DATE MUST BE BEFORE ITS RELATED LIAB END DATE The Liab Beg and Liab End dates for the same liability overlap. Change the Liab Beg date to an earlier date and/or change the Liab End date to a later date.

LIAB BEG

LIAB END

LB011

LIAB BEG DATE MUST BE AFTER THE NEXT LIAB END DATE
The Liab Beg and Liab End dates for different liability segments overlap. The dates specified will be highlighted on the screen. Change the Liab Beg date to a later date.

LIAB BEG

LB012

LIAB END DATE CHANGED TO THE END OF MONTH
A warning message to notify the data entry person of an automatic change made to the Liab End date. The Liab End date must always be the last day of the month.

LIAB END

LB014

UPDT CANCELED. CLIENT HAS BEEN BILLED FOR LIABILITY
The Liab End date is earlier than the monthly billing date. The client has been billed for the liability and no changes or deletions are allowed for this liability.

LIAB END

LB015

DO YOU WANT TO ADD THIS LIABILITY? ANS Y OR N
The record is ready for updating to the liability file. Verify the information in the Liab Beg, Liab End and Amt Liab fields. Enter “Y” to complete the add action or “N” to reopen add fields for entry.

ANS

LB016

DO YOU WANT TO CHANGE THIS LIABILITY?
The record is ready for updating to the liability file. Verify the information in the Liab Beg, Liab End and Amt Liab fields. Enter “Y” to complete the change action or “N” to reopen change fields for entry.

ANS

LB017

DO YOU WANT TO DELTE THIS LIABILITY? ANS Y OR N.
The record is ready for deleting from the liability file. Verify the record selected for deletion. Enter “Y” to complete the delete action or “N” to cancel the deletion.

ANS

LB018

LIABILITY RECORD HAS BEEN SUCCESSFULLY UPDATED
The liability record has been added to, changed, or deleted from the liability file.

LB019

UPDT CANCELED TO REFRESH SCREEN WITH CURRENT LIAB DATA
The liability record has been changed after the update action began and before the update action was completed. The update has been canceled to allow the data entry person to review the most current liability information before updating the liability record. Start update action again.

LB020

ENTER LIAB BEG AND END DATES IN MM/DD/CCYY DATE FORMAT
The prompt displays at start of update action or when an error is detected in the date. Review and re-enter date.

LIAB BEG

LIAB END

LB021

LIAB END DATE MUST BE AFTER ITS RELATED LIAB BEG DATE
The Liab Beg and Liab End dates for the same liability overlap. Change the Liab End date to a later date.

LIAB END

LB022

DEL ACTION INVALID. MUST DELETE MOST CURRENT LIABILITY FIRST
The first record on the file for the prime entered may be deleted. The message will display if the second or later records are selected for deletion. Select the first record for the prime on the file for deletion.

ACT

LB023

LIAB END DATE MUST BE BEFORE PREVIOUS LIAB BEG DATE
The Liab Beg and Liab End dates for different liability segments overlap. The dates specified will be highlighted on the screen. Change the Liab End date to an earlier date.

LIAB END

JF002

CASE NMBR NOT FOUND ON CMS FILE
A CMS case record does not exist for the prime number entered.

PRIM ID

JF003

INVALID SCREEN IDENTIFIER IN FAST PATH
The Fast Path entered in the Fast Path field was not found on the Fast Path file. Re-enter correct screen ID in Fast Path or enter screen ID from a clear screen.

FAST PATH

JF007

AFS CMS FILE CLOSED
The AFS CMS file is NOT available at this time. Try again later.

JF014

KEY PRESSED INACTIVE FOR THIS SCREEN
The function key pressed is not used on this screen.

JF015

FAST PATH FILE NOT OPEN
The Fast Path file is NOT available at this time. Try again later.

FAST PATH

JF016

UNKNOWN ERROR ON FAST PATH FILE
The Fast Path file has an error. Call the HelpDesk.

FAST PATH

JF017

NO COMMAND ENTERED. ENTER A COMMAND
No command was entered to view records or to go to another screen. Please enter valid command.

JF023

INVALID ANS – MUST BE Y OR N
The character entered in the Answer field is invalid. Re-enter a “Y” or an “N” in the answer field.

ANS

JF024

END OF RECORDS
Either F7 was pressed and there are no previous records to view on the screen or F8 was pressed and there are no more records to view on the screen.

JF025

SYS ID INVALID FOR THE FAST PATH ENTERED
The two-characters following the Fast Path entry field contains the system ID of the screen. Enter the correct system ID for the screen to uniquely identify the screen.

FAST PATH

JF027

INVALID TRANS TYPE – MUST BE I OR A
The Trans Type must be I for Inquiry or A for add.

TRANS TYPE

JF028

LIABILITY FILE CLOSED
The liability file is NOT available at this time. Try again later.

JF029

PRIM ID NOT FOUND ON LIABILITY FILE
There is no liability record for the prime ID entered. Type an “A” in Trans Type to add a liability.

JF030

ACT INVALID – MUST BE A (ADD) OR C (CHG) OR D (DEL)
A letter entered in the Act column is invalid. Re-enter an “A” to add a record, “C” to change a record or a “D” to delete a record.

ACT

JF031

PRIM ID NOT FOUND ON YEARLY ACCOUNT FILE
The prime entered is not on the Yearly Accounting file. Re-enter the correct prime or add the new prime to the yearly accounting file.

PRIM ID

JF032

YEARLY ACCOUNT EXISTS BUT IS NOT OPEN FOR THIS PRIM ID The prime entered is on the Yearly Accounting file, but the yearly account shows a status other than open. This is a warning message to let the data entry person know that no billings will be sent unless the Yearly Account is open for this prime ID.

PRIM ID

JF033

UNKNOWN RACF ERROR. CONTACT SDS SYSTEMS
An error occurred with RACF. Contact your RACF administrator or contact SPD Information Systems.

JF034

PAY-IN CONTROL FILE CLOSED
The Pay-In System Control File is closed. Try again later.

JF035

PAY-IN CONTROL FILE ERROR. UPDATE CANCELED.
The Pay-In System Control File is having problems. You may continue to inquire, but no update is possible. Contact SPD Information Systems to notify them that a file error occurs when LIAB reads the Pay-In Control File.

JF040

USER NOT AUTHORIZED FOR UPDATE ACTION REQUESTED
The RACF security has determined that no update authorization exists for your RACF ID. Contact your RACF administrator for update authorization.

JF041

USER NOT IN SAME DISTRICT AS CLIENT. UPDT NOT AUTHORIZED
The RACF security has determined that no update authorization exists because the user is not in the same district as the branch belonging to the client.

JF043

UNKNOWN RACF USERS
The RACF security did not find your RACF ID. Sign on to the RACF security system using CESN USER ID and password.