Please note that all Tiers of support require the following:
- ATP designation that the system is not to be replaced by Workday (a “Keep” or “Partially Replace” designation).
- Ancillary system direction on which Workday elements to provide in place of UDDS, particulary for systems sorting people (Supervisor Org, Cost Center) UDDS guidance is available here: https://secure.atp.wisconsin.edu/udds-guidance-ancillary-systems/
For last-mile ETL/flat file integrations, IICS offers 4 levels of support.
Tier 1: Providing templates and documenation for system support teams.
This often comes in the form of proof-of-concept (PoC) IICS mappings for common integration needs, including sfiles to accomodate formatting for standard EIBs for integrations. This level is good for systems with technical staff and common ATP pattern recomendations.
Tier 2: Working side-by-side with the system support team to begin the integraton.
This next tier of support is useful when ancillary systems cannot be retrofit to include required Workday elements. ERP-IICS developers will work to create PoC integrations including connections to crosswalk tables to translate data sources in tandem with ancillary system developers.
Tier 3: Developing the integration with the expectation that the long term support will be handled by the system support team.
ERP-IICS developers will create the integration, but system support will need to maintain support in the future state. Integrations of this nature often involve more complext integrations pulling from the ancillary system directly and automatically feeding Workday via a core connection
Tier 4: Developing the integration & providing long term support will be handled by the ERP-Integration IICS developers. This tier is available for systems without technical support staff to support maintaining their integrations.
IICS Capabilites and ‘Good Fit’ Patterns
- Use cases where Ancillary System raw data is consumed via file export, validations performed, and data is formatted in to an EIB template (Submit Customer Invoice, Submit Supplier Invoice, Submit Cash Sale Inbound, Accounting Journal Inbound or others published in the EIB Library) for deliver to Stakeholders to manually upload into Workday
- For use with Ancillary Systems which are not able to consume data directly from APIs or make use of Workday Reports, IICS processing can be used to call Person/HR/Finance API’s to produce extractions for loading or provisioning, such as delivering a nightly list of all active employees needed for provisiong into an Ancillary system.
ERP-IICS Request Forms
For ATP BAs, Campus BAs & PMs, Technical Coaches and others with ATP Jira access, please use the Jira request process below.
For Ancillary systems owners, technical contacts, developers and others without ATP Jira access, please use the IICS Request form below.
Jira IICS Request Process for Ancillary Systems
For users with ATP Jira access, please follow the existing process by adding a “child issue” with your request to the “Ancillary Systems – IICS Requests” JIRA Work Package. [WIP-59078] Ancillary Systems – IICS Requests – Jira (atlassian.net)
Detailed directions and notes on the Jira process are available here.
IICS Request form for Ancillary Systems
For Ancillary System Stakeholders without ATP Jira access, please use the link to the form below to request support – if ATP support is required a Jira will be created on your behalf.