---
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


---

# Purchasing tasks and procurement cases

# Purchasing tasks and procurement cases {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 24, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

All automated purchasing tasks and procurement cases are created using flow designer
from the Service Delivery Common (SDC) application. Flow designer uses the underlying task and
case generation decision tables, and purchasing tasks and procurement cases are created based on
the conditions defined in the decision tables.

## Conditions and triggers for task and case creation {#purchasing-tasks__section_jq5_k3t_flb}

While the Sourcing decision dependent on case and Order dependent on case fields in the Finance Case table determine the need for a [procurement case](https://servicenow-prod.fluidtopics.net/709U7dJVJUX4kdlDiSsPWQ#gloss-procurement-case-spo "A record used to track and manage procurement-related queries or issues.") to be created, the Sourcing decision dependent on task and Order dependent on task fields in the Finance Task table determine
the need for a [procurement task](https://servicenow-prod.fluidtopics.net/709U7dJVJUX4kdlDiSsPWQ#gloss-procurement-task-spo "A specific action or step that contributes to the completion of a procurement case.") to be created.  
Tasks and cases are generated when the following rules are triggered, with the decision tables supporting this generation via decision inputs.

* Purchase Requisition Task and Case Generation Rule
* Sourcing Request Task and Case Generation Rule
* Negotiation Task and Case Generation Rule
* Negotiation Event Task and Case Generation Rule
{#purchasing-tasks__ul_cf3_g4l_htb}

## Procurement case types {#purchasing-tasks__section_fzx_5sm_dvb}

Here's a list of the types and subtypes of procurement cases:

* Edit a purchase
* Edit a receipt
* GL Coding Review
* Budget Review
* Contract Review
* Send NDA for Signature
* Return a purchase
* Replace a purchase
* Request a Corporate Card
* Inquiry
* Delivery Address Review
* Request a copy of contract
* Due Diligence
{#purchasing-tasks__ul_prw_3qj_htb}

For procurement cases, you can also create child cases or associate child cases to parent
cases. However, remember that you must close all child cases and associated child cases
before you can close any parent case. Similarly, you can reopen a child case or associated
child case only when the parent case is still open.

## Procurement case states {#purchasing-tasks__section_ob2_k21_ccc}

The states that are available for a procurement case are listed.

* Draft
* Processing Case
* In Review
* On Hold
* Work in Progress
* Closed Canceled
* Closed Rejected
* Closed Completed
{#purchasing-tasks__ul_ddj_k21_ccc}

## Purchasing task types {#purchasing-tasks__section_chx_xsm_dvb}

A list of the types and subtypes of purchasing tasks are listed.

* Purchasing task
  * Select a Supplier: Ask the shopper to compare pricing from multiple suppliers and select a supplier.
  * Sourcing task
  * Ask a question: Ask the shopper for more information about the purchase.
  {#purchasing-tasks__ul_ud4_mg5_flb}
* Procurement/Supplier task: Create a procurement task for a supplier.
{#purchasing-tasks__ul_evr_g5t_dlb}

You can also create child tasks or associate child tasks to parent tasks. However, remember
that you must close all child tasks and associated child tasks before you can close any
parent task. Similarly, you can reopen a child task or associated child task only when the
parent task is still open.  
The following are the key fields of a purchasing task:{#purchasing-tasks__table_v3k_j25_flb__entry__2}

| Field | Description |
|-|-|
| Number | System-generated unique identifier of the purchasing task. |
| Assignment group | Group to which this purchasing task belongs. |
| Assigned to | User to which this purchasing task is assigned. |
| Primary contact | Person within the procurement team working on the purchase who can be contacted with questions. This field is populated or updated with the same user in the Assigned to field of the parent task record, as follows: * For a sourcing task, from the referenced sourcing request * For a purchasing task, from the purchasing task itself * For a contract task, from the contract task itself * For a supplier task, from the supplier task itself * For a finance task, from the finance task itself {#purchasing-tasks__ul_sml_glp_3nb} |
| State | Status of the purchasing task. |
| Substate | Progress of obtaining the shopper's responses to the procurement specialist's questions. |
| Due date | Expected date of completing the task. |
| Short description | Short description of the task. |
| Description | Detailed description of the task. |
| Detailed description | Detailed description of the Custom Task for Employee task subtype. You can enter your instructions in html or rich text format, and even add hyperlinks or images as required. |
| Summary Details ||
| Supplier | Supplier reference for this task. |
| Sourcing request | Sourcing request associated with this task. |
| Purchase requisition | Purchase requisition associated with this task. |
| Purchase order | Purchase order for which the revision request task is raised. |
| Sourcing decision dependent on task | Specifies whether this task must be completed before a sourcing request can be created. Note: This field is displayed only if a related sourcing request is entered. |
| Qualification dependent on task | Specifies whether this task must be completed before a qualification request can be created. Note: This field is displayed only if a related sourcing request is entered. |
| Order dependent on task | Determines if completion of this task is required prior to a purchase order being created. Note: This field is displayed only if a related purchase requisition is entered. |
| Expected start | Expected date of starting work on the task. |
| Actual start | Actual date of starting work on the task. |
| Actual end | Actual date of completing the task. |
| Duration | Actual time taken to complete the task. |
| Question \& Answer ||
| This section contains the information of the questions posed to the shopper and the responses that the shopper provides. ||
[Table 1. Purchasing task fields]

{#purchasing-tasks__table_v3k_j25_flb}
* **[Purchasing task and procurement case creation](https://servicenow-prod.fluidtopics.net/C~CxbFSRcplOD7B8KGwZEQ)**   
  Create purchasing tasks and procurement cases in sourcing requests and purchase requisitions.