The integration works by pulling data from SORD view (export.vw_Person_Attendance) into CiteOps.
- When will the Integration Run? How to run it manually.
- How to check what fields are read-only for users.
- How to troubleshoot Integration logs errors: Fields such as Occupation, Crews, etc were not by either exact or close match.
- User is duplicated in CiteOps- missing Employee No.
- Checking User in SORD view (This step is checked by CiteOps Support)
When will the Integration Run? How to run it manually.
The SQL integration runs daily at 7:30 am.
To run it manually you can go to the Manage screen > Integrations > People from SAP > Run
How to check what fields are read-only for users.
- Go to the Manage screen.
- Click on Integrations.
- Double-click on 'People from SAP' integration.
- Open the 'Mappings' tab.
In the 'Read Only' column, the checkmark suggests that these fields on the user profiles' are read-only or greyed out.
How to troubleshoot Integration logs errors: Fields such as Occupation, Crews, etc. were not by either exact or close match.
Once the integration runs in CiteOps, we usually encounter errors on the Logs tab. The Logs tab can be found in the Manage screen > Integrations > People from SAP > 'Logs' tab
E.g. Planning Coordinator occupation for Mark Payne (939391) was not found by either or close match.
This means that CiteOps cannot find the 'Planning Coordinator' on the Occupation, therefore it doesn't know where to map it to.
We troubleshoot this by going to the 'Lookups' tab and mapping the 'Planning Coordinator' to an existing Occupation in CiteOps, and hitting 'Save'.
User is duplicated in CiteOps- missing Employee No.
There are 2 scenarios:
1. When a user in CiteOps does not have an 'Employee No.' on their profile, then after the integration runs, it creates a new user with all the details. This will lead to duplication since now there will be two accounts created for the same person; one with an employee number(new user account created by the integration) and one without an employee number(already existing account in CiteOps).
2. When a previously imported user or an existing user has 'Employee No. on their profile, then the 'People from SAP' will update the fields on the existing user.
Checking User in SORD view (The below steps are checked by Commit Works Support team)
A. User is shown CiteOps- Person is available in the SORD view
In this example, we check the information for Mark Payne, we modified the query to include his first name and last name. Then hit Execute - (3).
Findings:
a) As seen from the above screenshot, once the query runs, there are details that are returned.
If the person is available, it will show in the SORD view or on the 'Results' tab.
b) Now after we run the 'People from SAP' integration, the user details are added/updated into CiteOps.
B. User is NOT shown in CiteOps- Person is NOT available/no details available in the SORD view
In this example, we check the information for Bert Webb, we modified the query to include his first name and last name. Then hit Execute - (3).
Findings:
a) As seen from the above screenshot, once the query runs, there are no details returned as the bottom half is empty. This confirms that the user was not in the view and hence became inactive once the integration ran.
b) If the person is not available in the SORD view or empty in the 'Results' tab, then the user is not available in CiteOps.
c) If it is a new user and the user does not come in the SORD view then that user cannot be added to CiteOps.
Comments
0 comments
Please sign in to leave a comment.