This article provides guidance for production campuses on the steps to follow when requesting a non-production CHRS database connection to their own masked Campus Solutions environment.
Overview
CHRS production campuses do not have access to create database (DB) links or set up integrations within CHRS. However, they can create DB links and configure integrations within their own masked Campus Solutions (CS) environment. In most cases, a DB link is sufficient for development and testing directly in CS. However, certain scenarios, such as Tools Testing and MP Validation, etc. require full integration between CS and CHRS. When a campus needs to connect a CHRS non-production environment to their own masked CS environment, a ServiceNow ticket must be submitted.
Submit Request
Step 1: Submit a ServiceNow ticket:
- Type: Request
- Category: CMS-CHRS
- Subcategory: Integration
-
Ticket Short Description:
- In the ticket short description, indicate that your campus needs to have CHRS connected to your own masked CS environment (example: Request for HACHRPSA to Connect to CAFULTST-Fullerton)
-
Description:
- In the description provide the following:
- CS Database Name
- CHRS Database Name
- Reason for Request
- In the description provide the following:
Step 2: CMS will complete the necessary steps to configure integration in the requested non-production CHRS environment, and update ServiceNow ticket that campus can proceed to connect their own masked CS environment.
Configure Campus Masked CS Environment
NOTE: The following steps must be completed by the campus in their own CS environment!
Step 1: Navigate to the Service Operations page
- Nav Bar Menu > PeopleTools > Integration Broker > Integration Setup > Service Operations > General page
Step 2: Confirm the following Service Operations are active and have the correct CHRS database noted in the link
- CSU_SEC_USERID
- CSU_PROVISION_INT
- CSU_CHRS_CS_INTEGRATION_POST
Step 3: Confirm the following Service Operations are inactive as they are related to PDM functionality in CS
- CSU_MDH_POST
- CSU_MDH_Local
Step 4: Navigate to the Domain Status
- Nav Bar Menu > PeopleTools > Integration Broker > Service Operations Monitor > Administration > Domain Status
Step 5: Confirm the Domain Status is active
Step 7: Recreate the Crosswalk table using SQL:
DELETE FROM PS_CSU_CHRS_XREF;
INSERT INTO PS_CSU_CHRS_XREF(CSU_CHRS_ID, CSU_CS_ID)
SELECT CSU_CHRS_ID, CSU_CS_ID
FROM PS_CSU_EMPL_MAP_VW@CSU_CS_HR_LINK A
, PS_INSTALLATION B
WHERE B. COMPANY = 'XX' AND A.BUSINESS_UNIT = 'XXCMP';
COMMIT;
The Crosswalk table must always be rebuilt in CS. When recreating the Crosswalk table, B. Company is from the Campus Solutions PS_Installation Table and A. Business_Unit from CHRS.
The campus codes can be located in the CHRS Library.
Step 8: Complete Campus Performed Integration Checklist to confirm integration is setup correctly between CS and CHRS.
End of Article
0 Comments
Add your comment