Request access to COA Validator/Segment Service/COA Integration Hub (includes Roles)

Access to and use of the web service will require approval and access (via a service account). When making your access request you will be asked to identify if you need access to COA Validator or COA Integration Hub. COA Integration Hub access also grants access to Segment Service. Access to COA Validator does not automatically grant access to the Segment service or COA Integration Hub.

COA Validator: The main purpose of the COA Validator web service is to provide Yale systems and application owners a tool to validate COA.

COA Integration Hub: COA Integration Hub is a SQL Server database that contains information about COA segments, hierarchies and other general COA data. COA data is downloaded from Workday into the COA Hub on a routine interval and is available to use for Yale systems and application owners.

COA Segment: The main purpose of the COA Segment web service is to provide Yale systems and application owners data about COA segments, hierarchies and other general COA data. This data  is sourced from the COA Integration Hub.

GetRoles: This will give Roles by individual user, cost center, and role.

 

Who can consume the Web Services?

COA services can be consumed by:

  • Yale Internal Clients (System and Applications).
  • External vendors and B2B trading partners.

Basic authentication will be utilized as the security mechanism that will help enforce access control to the web service/resources.   Consumers will need to pass and be authenticated by a username and password. In addition, external vendors/users to Yale will need to provide their invoking server/machine IP address so that firewall access can be granted before consuming the web service.

 

Following are the steps that will need to be taken, in order to obtain access to data:

  1. Fill out access request form: Finance Integration Hub Access Request
  2. An e-mail to be submitted to fss@yale.edu requesting access along with the completed form. The Finance Support Services team will review the request and approve (or deny with follow-up questions).
  3. Once approved a Service now ticket will be created by Finance Support Services team to the 'Financial Systems' ITS group for access.

          3b.  For any new applications / systems, a service account (following standardized naming conventions) will need to be created as part of this request and will reside in Active Directory.  

                A service Now subtask will be initiated to ITS Helpdesk for the account to be created by Client Accounts. A 2-3 day turnaround time is expected.

 

  Note: Web service access will not be granted to Individual user Net IDs

 

Related articles

 

The main purpose of the COA Segment web service is to provide Yale systems and application owners data about COA segments, hierarchies and other general COA data. Access to use the web service will require approval and access is given via a service account.  

fss@yale.edu