Camps Help TitlePrint this document linkBack to Help Home Link
Inventory Status Codes

The “Trans Status” column on the inventory is used to determine the current status of each CAMPS transaction.

*  PENDING TRANSACTIONS: A second transaction cannot be entered for an employee if there are other pending transactions for that same employee, and if the job number is the same.  (If the second transaction is for a different job number, it will be permitted.)

      For example, if an action displays on the inventory with any status other than “Approved” or “Rejected,” a new transaction cannot be initiated until the pending transaction is approved or deleted.  If this is attempted, the message “Cannot Add a New Transaction Since Another Pending Transaction Exists for this User” will display.

      If this occurs, the user must check the inventory and resolve any pending transactions for the employee in question.

APPROVED

After a transaction has been reviewed by a CSC staff member and found to be in compliance with Administrative Code 4A, the transaction will be approved and its status will change to “Approved” in the inventory.

Some transactions, such as leaves of absence, salary adjustments, and certain separations, do not require formal CSC approval.  When these transactions are Submitted by an authorized appointing authority user, they are “auto-approved,” and the status will immediately show as “Approved” in the inventory.

All Approved transactions will remain on the inventory for seven calendar days, although they will also display in the employee’s history record at the time of approval.

FUTURE

Transactions with a future effective date will be displayed in the inventory with a “Future” status.  However, no effective date may be entered that is more than five years beyond the current date.  When the effective date is equal to the current date plus one day, the status will automatically change to “New” and normal processing can continue.  If the transaction is one that is auto-approved, the status will automatically change to “Approved” once the effective date has been reached.

Appointing authorities and CSC analysts may delete “Future” transactions by selecting the action, then clicking the Delete button at the bottom of the screen.

INCOMPLETE

Transactions that cannot be finalized for any reason (such as incomplete information) may be stored as “Incomplete” in the inventory, provided their effective date is greater than or equal to the most recent history record.  To save as Incomplete, click on the SAVE, rather than the SUBMIT, button at the bottom of the screen.  Saving a transaction as “Incomplete” will ignore all system edits, and will allow the user to access and finalize the transaction at a later time.

INCOMPLETE CSC

This status is available only to CSC users.  It is used to identify those transactions that cannot be finalized by the Civil Service Commission because additional information or review is required.  This status may only be used on transactions that are displaying in the inventory as “Incomplete;” therefore, it will not be available on any transactions that are auto-approved.

To use this status, access the “Incomplete” transaction from the inventory, and select “Incomplete CSC” from the Transaction Status drop-down box.  Both the SAVE and SUBMIT functions will save the transaction as “Incomplete CSC.”  However, SAVE will not perform any edits on the data entered (and is the preferred selection), while SUBMIT will edit the data before allowing you to continue.

Inventory transactions with an “Incomplete CSC” status may only be acted on by a CSC staff member.

NEW

The “New” status indicates that a transaction has been completed by the appointing authority, and is ready to be reviewed by the Civil Service Commission.  To display as a “New” transaction, the effective date must be greater than or equal to the most recent job history record.

A transaction can still be deleted by the appointing authority while in “New” status.

* NOTE:  Some actions, based on transaction code, are automatically approved once they pass all validations.

For CSC users, all “New” transactions will display in red.


PENDING AA APP 1

When an appointing authority user with security level “0” (basic Data Entry access) submits a transaction, the Transaction Status will be set to “Pending AA App 1.”  A user with Security Level 1 or 2 will then be required to review and submit the transaction.

PENDING AA APP 2

When an appointing authority user with security level “1” (Data Entry and First Level Approval) submits a transaction, the Transaction Status will be set to “Pending AA App 2.”  A user with Security Level 2 will then be required to review and submit the transaction.

PENDING CORRECTION

If a transaction is found to contain one or more errors, such as a wrong title code, a wrong appointment type, etc., the CSC reviewer will set the transaction status to “Pending Correction,” and may include comments about what corrections are needed.  It is the appointing authority’s responsibility to open the record from the inventory and make the necessary corrections.

After the corrections are made, the appointing authority should SUBMIT the transaction again.

REJECTED

If a transaction is found to not be in compliance with Administrative Code 4A, or if the wrong type of transaction is submitted (for example, an Advancement rather than a Promotion), the transaction will be “Rejected.”  Once rejected, no further action may be taken on the transaction.  The rejected action will remain on the inventory for seven calendar days.  After that time, the transaction will be removed from the inventory.  A basic record of the transaction may then be viewed only through the Rejected Transaction report.

RETROACTIVE

When a retroactive transaction is submitted by an appointing authority, the action will be reviewed by a CSC analyst, at which time one of four statuses will be assigned:  Returned, Pending Correction, Rejected, or Approved.  (If any status other than Approved is assigned by CSC, normal processing procedures apply.)

When approved by CSC, the transaction’s status will change from “Under Retro Review” to RETROACTIVE.  The appointing authority is then responsible for completing the retroactive “package” and resubmitting the action for final approval.


RETRO INCOMPLETE

If a transaction has an effective date that is earlier than the effective date of the most recent job history record, and has been “Saved” (as opposed to “Submitted”) by the appointing authority, it will display with a status of “Retro Incomplete.”

RETRO REVIEW 2

The appointing authority must approve all transactions with a “Retroactive” status, by reviewing the retroactive package of records and clicking SUBMIT.  After submission, the transaction status will change to RETRO REVIEW 2.

Transactions at the RETRO REVIEW 2 level must be APPROVED or REJECTED by CSC staff.

RETURNED

If a transaction is missing needed information, the CSC reviewer will set the transaction status to “Returned,” and may include comments about what information is missing.  It is the appointing authority’s responsibility to open the record from the inventory and make the necessary corrections.

After the required information has been obtained, the appointing authority should SUBMIT the transaction again.

UNDER REVIEW

When a CSC staff member opens a typical transaction (i.e. one whose effective date is greater than or equal to the most recent job history record), its status will automatically change to “Under Review.”  After review by the Civil Service Commission, one of four statuses can be assigned:  Returned, Pending Correction, Rejected, or Approved.

Once an action is Under Review, the AA may no longer make any changes to the transaction.

* NOTE:  Some actions, based on transaction code, are automatically approved once they pass all validations.

UNDER RETRO REVIEW

From the time a retroactive transaction is submitted by an appointing authority to its initial approval, the status will display as “UNDER RETRO REVIEW.”

NOTE: Some actions, based on transaction code, are automatically approved once they pass all validations.