--- sourceDocument: Yokohama Finance and Supply Chain sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/source-to-pay-operations Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Finance and Supply Chain ft:clusterId : - stpop bundleId : - stpop workflow : - Employee --- # Universal Request # Universal Request {#ariaid-title1} * Release version: Yokohama * * Updated December 4, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Universal Request The Universal Request feature allows supplier contacts to raise issues that do not fit predefined case types or require multiple departments' involvement. It streamlines the workflow for routing and resolving queries, enhancing efficiency in supplier communication. Show full answer Show less Access to the Universal Request feature requires checking your entitlements and is available starting from the Yokohama December 2025 release. To enable this feature, the Universal Request for Source-to-Pay Operations plugin \[snfscurcommon\] must be installed. ## Key Features * **Stakeholders:** Involves supplier contacts who submit requests and routing agents who manage these requests. * **Routing agents:** Tier-1 agents with roles to view, update, transfer, and close Universal requests and create supplier cases from them. * **Submission Process:** Supplier contacts submit requests via the Supplier Collaboration portal, with the option to mark requests as sensitive for automatic routing to the appropriate group. * **Primary Ticket Creation:** Sensitive requests automatically create a supplier case, while non-sensitive requests require routing agents to create a case manually. * **Resolution Process:** Routing agents accept or reject resolutions from primary tickets, with options to transfer tickets across departments or create associated tickets for collaborative resolutions. ## Key Outcomes By utilizing the Universal Request feature, ServiceNow customers can expect streamlined issue resolution, improved cross-departmental collaboration, and enhanced management of supplier queries. This leads to faster response times and better overall supplier relationships. The Universal Request feature enables supplier contacts to raise issues that do not fit into predefined case types or involve multiple departments. It provides a structured workflow for routing and resolution of queries. Important: Check your entitlements to determine whether you have access to the Universal Request feature. This feature is available from the Yokohama December 2025 release onwards. You must install the Universal Request for Source-to-Pay Operations plugin \[sn_fsc_ur_common\] to enable the Universal Request feature in SLO. For more information on installing the plugin, see [Install Universal Request for SLO](https://servicenow-prod.fluidtopics.net/Mj04pBWb2g3EIxkBPCpwcw "Install the Universal Request for Source-to-Pay Operations [sn_fsc_ur_common] plugin to use the Universal Request feature in SLO."). ## Key Stakeholders {#universal-request__section_l24_4g4_nhc} The Universal Request workflow involves the following stakeholders: * Supplier contacts: Supplier contacts submit their queries by raising Universal requests. * Routing agents: Routing agents are tier-1 agents who manage both Universal requests and supplier cases. These agents have both the Universal Request role and the \[sn_slm.agent\] role. Routing agents can perform the following operations: * View, update, transfer, and close Universal requests * Create supplier cases from Universal requests {#universal-request__ul_mnh_xr5_nhc} {#universal-request__ul_ig2_jsn_nhc} Note: You can create Routing agents by adding users to the Source Operations Universal Request Group. This group is a default assignment group that contains Universal request roles and supplier agent roles. For more information on assigning roles, see [Assign roles to UR users](https://www.servicenow.com/docs/access?context=ur-assign-roles&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US). For more information on roles in Universal requests, see [Universal Request roles and groups](https://www.servicenow.com/docs/access?context=ur-roles&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US). ## Universal Request workflow {#universal-request__section_v5q_y22_lhc} 1. Submission of a Universal requestThe supplier contact submits a Universal request from the Supplier Collaboration portal. For more information on raising a Universal request, see [Create a Universal Request from the Supplier Collaboration Portal](https://servicenow-prod.fluidtopics.net/9xROcpdCzJDROLXHWqVe6A "Create a Universal Request to raise issues that do not fit into predefined case types or involve multiple departments."). 2. Assignment of the Universal request * For requests that are marked as sensitive, suppliers select the department at the time of request submission. The request is assigned automatically to the corresponding assignment group. Note: Suppliers can mark a Universal request as sensitive by selecting the Issue contains sensitive or confidential information check box while submitting the request form. For more information, see [Create a Universal Request from the Supplier Collaboration Portal](https://servicenow-prod.fluidtopics.net/9xROcpdCzJDROLXHWqVe6A "Create a Universal Request to raise issues that do not fit into predefined case types or involve multiple departments."). * For requests that aren't marked as sensitive, routing agents review the request and route them to an appropriate assignment group based on the information provided in the description and short description by the supplier. {#universal-request__ul_qd5_v52_lhc} 3. Primary ticket creation * For requests that are marked as sensitive, a primary ticket of the type supplier case is created automatically. * For requests that aren't marked as sensitive, routing agents must create a supplier case for resolution. For more information, see [Create a supplier case](https://servicenow-prod.fluidtopics.net/RV4gYrB~rnnLo1XwtfcHfQ "As a procurement specialist, with an additional supplier role of sn_slm.manager, create a supplier case from the list view of Source-to-Pay Workspace to address your supplier-related business needs."). Note: Routing agents can also create an invoice case instead of a supplier case from a Universal request if they have the required permissions. {#universal-request__ul_k43_jv2_lhc} 4. Resolution of the Universal request * If the routing agent accepts the resolution provided in the primary ticket, the Universal request is marked as complete and closed. * If the resolution is rejected, the supplier case is dissociated from the Universal request. The routing agent then creates a new primary ticket from the Universal request for resolution. {#universal-request__ul_sfb_dm2_nhc} {#universal-request__ol_nrv_2f2_lhc} Primary tickets can also be transferred to other departments when resolving a Universal request requires cross-departmental support or must be reassigned to a different department. For more information on transferring primary tickets, see [Transfer a primary ticket](https://www.servicenow.com/docs/access?context=route-primarytask-to-ur&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US). When a Universal request needs support from multiple departments, you can create Associated tickets in addition to the primary ticket. Associated tickets enable multiple departments to work on the resolution of the Universal request simultaneously. For more information see, [Create associated ticket for primary ticket of UR](https://www.servicenow.com/docs/access?context=create-associated-ticket&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US).