3. #OHUG2016
Session description
• The session will provide a functional overview of the business challenges
and technical solutions in CGG’s 2015 SSHR Workflow un-customization
project.
• CGG implemented Team Leader Self Service responsibilities (aka
Manager Self Service without salary access) in the US and Canada
Business Groups and replaced the existing US/CA custom workflow with
a simplified version that directs transactions to authorized approvers
based on a “manager approval authority” field.
• CGG needed this development to satisfy several main objectives: an
accurate supervisor hierarchy in HRMS incorporating team leaders and
managers, Team Leader Self Service responsibilities that would not
display salary data, workflow incorporating a “skip rule” to identify/skip
team leader approvers in the supervisor hierarchy, and a simpler process
for support, testing and maintenance.
4. #OHUG2016
Session content
• About CGG and our HRMS structure
• The business requirement
• Team Leader – a subset of Manager Self Service
• Workflow redesign
• Simplified code to identify authorized approvers
• AME layout
• Surprise! What we didn’t anticipate, and the fix
• Terminology decoded
• Transaction monitoring
5. #OHUG2016
About CGG
• Leader in Geoscience: CGG is a fully integrated Geoscience company
providing leading geological, geophysical and reservoir capabilities to its
broad base of customers.
• Passionate People in 50 Locations: CGG employs over 7,000 people
around the world, all with a Passion for Geoscience and working together
to deliver the best solutions to its customers.
6. #OHUG2016
CGG HRMS Structure
• Product version: Oracle EBS 12.1.3 HRMS RUP8
• 6 Business Groups (AP, CA, FR, UK, US, WD) containing 50+ payroll
populations. US and CA utilize Oracle Payroll and Advanced Benefits.
• Self Service responsibilities:
– Employee Self Service: 9
– Manager Self Service: 9
– Team Leader Self Service: 9
– HR Self Service: 1
• Employee Service Center (ESCAPPROVE): 7
• Supervisor hierarchies of 10+ levels may cross BG multiple times
7. #OHUG2016
The business requirement
• Create a ‘lite’ version of the Manager Self Service responsibility called
Team Leader Self Service with menu items personalized to hide salary
information.
• Modify the process that assigns/end dates users MSS/TLSS
responsibilities based on a “manager approval authority” field.
• Replace the existing US/CA custom workflow with a simplified version
that directs transactions to authorized approvers based on the “manager
approval authority” field.
• Update employee assignments to incorporate Team Leaders to produce
accurate supervisor hierarchy in HRMS. Populate the “manager approval
authority” field on all records.
• Deliver ability for HR to monitor the status of their workflow transactions.
• Simplify process and resources needed for workflow support, testing and
maintenance.
8. #OHUG2016
Team Leader Self Service
• A subset of Manager Self Service, Team Leaders are in the supervisor
hierarchy but with restricted salary data access.
• Team Leaders should not receive workflow transactions potentially
containing salary data (i.e. new hire, assignment update, change pay),
but can receive/action other workflow transactions (i.e. absences, OTL
timecards). Team Leaders should not access Compensation Workbench.
• The Manager Approval Authority field is a Person EIT labelled “Manager
Flag”, populated for every HRMS record to differentiate between Team
Leader and Manager.
• To assign the responsibility, we have a lookup table containing unique
combinations of EIT Flag, Responsibility, Security Profile & BG.
• Nightly Concurrent Process scheduled to assign/end date Team Lead
responsibility based on employee data and the lookup table.
9. #OHUG2016
Workflow redesign
BEFORE AFTER
Multi-level approvers
N+1, N+2, HR Approver, Alternate
Approver, ESC Approver
Two approvers
Authorized N+1, ESC Approver
7 levels of timeouts
16 approval/rejection paths
No timeouts
4 approval/rejection paths
Custom workflow functions Seeded workflow functions
Custom notifications
Action history to groups outside of
workflow: PayApprove, TermNotify
Seeded notifications
Seeded Transaction Monitor
Weekly status reports via
BI Publisher
Separate workflow for Termination
Termination workflow included in
design
11. #OHUG2016
Simplified code
• Developed code to identify the First Manager (N+1) who has authority to
approve the transaction. Code loops through supervisor hierarchy for
MAA Flag = Y (stored in Person EIT). Resulting in a “skip rule” for Team
Leaders not authorized to view/approve certain transactions.
• Developed code to identify the ESCAPPROVER for a transaction based
on the Employee’s Payroll. Exception for the New Hire transaction
handled inside the code.
12. #OHUG2016
AME layout
• Defined a condition to apply to the desired seeded
functions.
WORKFLOW_PROCESS_NAME in
(HR_ASSIGNMENT_JSP_PRC,
HR_EIT_JSP_PRC,
HR_EMP_STATUS_CHG_JSP_PRC,
HR_MANAGER_JSP_PRC,
HR_NEWHIRE_JSP_PRC,
HR_P_RATE_JSP_PRC,
HR_SIT_JSP_PRC,
HR_TERMINATION_JSP_PRC)
• Approvers for Manager Level One (N+1) &
ESCAPPROVER by Payroll.
– Action type: approval-group chain of authority
– Require approval from CGG MGR LEVEL ONE
– Require approval from CGG ESC APPROVER by Payroll
13. #OHUG2016
What we didn’t anticipate
Some Seeded Functions used in other BGs with different approval setup
were impacted.
Our approach to analyze/identify the conflicts:
• Prepare a complete mapping of all Global functions from Responsibilities
of each BG.
• Identify approvals/workflow design used by each function.
We concluded that the best way forward was to apply the new simplified
design only to the US BG and CA BG population.
Our solution:
• Code was upgraded to identify the BG of transaction.
• AME was updated to add a condition that validates BG of each
transaction (based on subject of transaction).
15. #OHUG2016
Terminology decoded
• Process: The workflow process is built/defined in the back-end (we used
the Workflow Builder tool) to perform a certain action.
• Function: This is a building block in the front-end application that is
configured to call a particular functionality.
• A function calls the workflow process to perform an action. More than one
function can be defined that call/point to the same workflow process.
Keep in mind that multiple functions initiating the same workflow process
can be defined in different BG.
16. #OHUG2016
Transaction monitor
• Seeded functionality to query/track status of workflow processes. The
filter for “function name” points to workflow process name.
• Useful for auditors.
17. #OHUG2016
BI Publisher
• Weekly bursting of active workflows with “notified” status to the
appropriate ESCAPPROVE.
• Ability to run ad hoc extracts based on other parameters.
18. #OHUG2016
Workflow testing
• Tedious workflow testing of multiple transactions, custom notifications,
multi-level approvers, timeouts and exception paths (one example below)
replaced with a simpler process for support, testing and maintenance.
19. #OHUG2016
Thank you for attending
• Please complete the session evaluation!
• Feel free to contact me:
– Email: tilly.manning@cgg.com
– Twitter: https://twitter.com/tillymanning
– LinkedIn: https://www.linkedin.com/in/tilly-manning-phr-gphr-hrip-
shrm-scp-6152889
