Standard Operating Procedure
Internal business procedure, not a Training Document
FSPD Number(s) & Title:
GL.04 – CA Nightly Batch Processing
GL.05 – CA Post-Confirm Batch Processing
Procedure Owner (Central Office, Division Head): Business and Financial Services(BFS), AVC/Controller
Issue Date: 10/17/2017
Date of Last Revision: 10/17/2017
Purpose:
To outline the procedure to resolve issues resulting from Batch processes.
Procedure Definition/Scope (from FSPD):
GL.04 - The Commitment Accounting Nightly Batch Processing process depicts what will be included in the nightly batch process, the sequence of processing, and how errors or issues related to batch processing will be resolved. At the University of California, ITS will handle the management of batch processes and will work with the UCPath Center for issue resolution.
GL.05 - The Commitment Accounting Post-Confirm Batch Processing process begins when Payroll is confirmed and ends before ODS batch processes run.
I-370 Web Service FAU validation
Procedure Definition/Scope (UCR Revised Definition):
Same as above except for the interfaces listed below that will be consumed differently.
I-170 Combination codes interface (Pre go-live only)
I-370 Web Service FAU validation (Post go-live)
Frequency (ad hoc, daily, weekly, monthly, annually, etc.):
Daily
Trigger:
UCR receives notifications on Batch Process status
Primary Variations: N/A
This procedure has X primary variants:
Roles and Responsibilities
Campus Point of Contact for UCPC: Computing and Communications
Entity
|
Roles and Responsibilities
|
UCOP
| |
HR Business Partner/Org Unit
|
CNC – Resolve technical related issues
|
UCR Business and Financial Services
| |
UCR Office of Resource Planning and Budget
| |
UCR Office of Human Resources
| |
UCR SSC
| |
UCPath Center
|
Provide Batch process status
|
Required Parameters/Controls
Required Notifications
Notification To
|
Generated By
|
Mechanism
|
|
|
|
Overall Activity Sequence
Capture at a ‘One Person, One Task, One Tool’ level
Step #
|
Step Description (Verb/Noun)
May have sub-steps
|
Party
|
1
|
Receive status
|
Business and Financial Services
|
2
|
Identify issues (If any)
|
Business and Financial Services
|
3
|
Resolve Technical issues (if any)
|
CNC (Computing and Communications)
|
4
|
Communicate Technical issues to CNC
|
Business and Financial Services
|
5
|
Resolve Non-Technical Issues
|
Business and Financial Services
|
6
|
Notify BFS of technical resolution
|
CNC (Computing and Communications)
|
7
|
Manage the process
|
Business and Financial Services
|
9
|
Notify UCPath on issue resolution
|
Business and Financial Services
|
Decision Tree or Flow Diagram (Optional) - N/A
Complex/Exception Cases – N/A
N/A
Tools/Templates Used (Existing w/revisions, New, Decommissioned, etc.)
Email
Process Touchpoints – N/A
None
References
Definitions
Term: Definition
Related Documentation and Resources
Website URL: Link
Questions
Question 1
Question 2
Use this table to summarize changes made to this document
Date
|
Editor
|
Summary of Changes
|
11/17/2016
|
Alfred Karam
Gabe Nwandu
Molly Parlett
|
Final Draft
|
|
|
|
|
|
|
Share with your friends: |