The purpose of this document is to provide campus users with assistance in troubleshooting integration errors that occur in CS, CHRS, and/or PDM. Depending on the database the error occurs, different resources will be responsible for troubleshooting and resolving.
In both CHRS and CS, campuses cannot rely on the “Done” status directly located on the page and must review the details to see if an “error” has occurred.
Integration errors can occur due to:
- Campus Data
- Duplicates
- DB Link(s) down
- CS system down unexpectedly
- CHRS system down unexpectedly
CHRS Database
CHRS Production Support Databases
The CHRS Production Support databases do not automatically have integration setup. CMS connects the Sunday CHRS Production Support databases (H*CHRSPA & H*CHRPSB) to an internal CS database.
Campuses have the option to submit a ServiceNow ticket if they want a CHRS Production Support database to be connected to their CS database.
If a campus is having one or more of the below issues in a CHRS Production Support database, it is due to integration not being setup:
- Create/Update POI
- Create/Update Employee
- Create New Job Records
- Use Employee Self-Service
- Use Self-Service Course Assignment Tab for TAE
- Use Student Mod (Hire/Rehire)
- Use CSU Hire Dates
- Use CHRS Recruiting Staging Table
- Use CSU Notification Summary Report
- Use Work Study Balance Page
- Use Auto Enrollment processes.
- Enroll new Time reporters.
- Updates of CS EmplID and Bus email for the PSOPRDEFN table
- Process GL Interface
- Process Export Accounting Lines
- Process LCD Table Refresh
- Process LCD Publish to FIN
- Complete Combo Code Edit
- Complete Combo Code Validation
CHRS Production (HCHRPRD)
CHRS is a shared environment with level 1 data included within the integration messages.
- Therefore, in CHRS, campuses do NOT have direct access to review integration setup, asynchronous or synchronous message details.
- Campuses DO have access to the CSU IB Monitor page which provides an overview of integration setup, asynchronous or synchronous message details.
When a campus is experiencing an issue in CHRS production, it generally will be discovered when a New User is unable to login to CHRS due to not having a User Profile. When that occurs, it is generally due to a duplicate being created in CHRS. However, in some cases, the cause could be something else.
Before submitting a ServiceNow ticket, the following questions should be answered:
- Has a duplicate been created? If yes, refer to the Duplicates Guide (Pending).
- Has my campus reviewed integration setup and Synchronous/Asynchronous messages in CS to see if any errors have occurred?
A ServiceNow ticket will need to be submitted for the Integration team to assist.
The ServiceNow ticket should have CMS-CHRS as the Category and Integration as the Subcategory.
Don't forget to include:
- Database(s) affected.
- Details about the transaction causing the concern (EmplID, employee, POI, new or updated person, etc.)
- Date and time issue occurred or was discovered.
- Any additional information you think will be helpful.
Campus Solutions
CS Clone
Most of the campus CS clones will not have integration with CHRS Production Support databases. If a campus needs their campus CS clone connected to a CHRS Production Support Database they will need to submit a ServiceNow Ticket.
Before submitting a ServiceNow ticket the following questions should be answered:
- Is the DB Link setup correctly?
- Has the CHRS Crosswalk Table been refreshed?
- Is what my campus trying to do require full integration and have we submitted a ServiceNow ticket?
CS Production
When a campus is experiencing an issue with integration in CS production, it is generally related to Integration Setup. However, on the rare occasion the issue could be related to something else.
Complete Step 2 and Step 3 below before opening a ServiceNow ticket.
Begin by reviewing that the integration configuration has not been modified. We recommend doing a triple check on this and clearing your browser cache, as this is related to the majority of issues. If something is not set up correctly, then it should be fixed, and the transaction should be reinitiated. If everything is set up correctly, then the campus should move forward in their investigation.
- Domain Status
- Confirm the status is Active
- Navigation: Menu > PeopleTools > Integration Broker > Service Operations Monitor > Administration > Domain Status
- Service Operations
- Confirm the status for each Service Definition is active and they have the correct database noted in the URL
- CSU_CHRS_CS_INTEGRATION_POST
- CSU_SEC_USERID
- CSU_PROVISION_INT
- Navigation: Menu >People Tools> Integration Broker > Integration Setup> Service Operation
- Confirm the status for each Service Definition is active and they have the correct database noted in the URL
Between CS and CHRS, Synchronous Messages are sent between the system. If the integration issue is related to CHRS, review the Synchronous Messages in your CS database during the timeframe your campus believes an error has occurred.
CS Navigation: Menu > PeopleTools > Integration Broker > Service Operations Monitor > Monitor Synchronous Services
Based on the status action, different actions may be required.
| Status | Action(s) to Take |
|---|---|
| NEW |
|
| ERROR |
|
| DONE |
|
If no transaction appears, then an error has potentially occurred in CHRS and a ServiceNow ticket is required.
A ServiceNow ticket will need to be submitted for the Integration team to assist.
The ServiceNow ticket should have CMS-CHRS as the Category and Integration as the Subcategory.
Don't forget to include:
- Database(s) affected.
- Details about the transaction causing the concern (EmplID, employee, POI, new or updated person, etc.)
- Date and time issue occurred or was discovered.
- Any additional information you think will be helpful.
End of Article
0 Comments
Add your comment