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


---

# Configure conditions for merging purchase requisitions

# Configure conditions for merging purchase requisitions {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure the conditions under which the purchase requisitions (PR) should be merged.

## Before you begin

Role required: sn_shop.shopping_hub_admin or sn_shop.procurement_administrator

## About this task

The conditions that you set determine when to merge the purchase requisitions.  
Note:  
The existing default scenarios for merging purchase requisitions and purchase lines remain valid and function as they did previously. For more information, see [Purchase requisition merging](https://servicenow-prod.fluidtopics.net/bRBHaCbzdb25FLjqaEV3lw "Purchase requisitions can be merged if certain criteria are met. This avoids multiple purchase orders from being created unnecessarily and also helps enforce approval rule limits.").

You cannot merge the PRs that are in any of the following states:

* Closed Complete
* Closed Canceled
* Closed Rejected
* Pending Submission
* Pending Cancellation
* Pending Revision
* Pending Supplier Confirmation
{#config-pr-merge__ul_zsl_vyd_bdc}

## Procedure

1. Navigate to AllShoppingHubAdministrationShoppingHub Configuration.
2. In the Configuration type column, select Merge configuration.  
   The Configuration type field is set to Merge configuration by default.

3. The Active check box is selected by default.  
   Deselect the Active check box if you want to deactivate the merge configuration.
4. On the Merge conditions tab, fill in the fields.  
   {#config-pr-merge__table_jzv_bqw_ycc__entry__2}

   | Field | Description |
   |-|-|
   | Purchase table | Read-only field that shows the Purchase Requisition \[sn_shop_purchase_requisition\] table. |
   | Merge type | The type of merge that you want to allow. The options are: * Allow both: Enables you to configure both auto merge and manual conditions. Displays both the Auto merge conditions and Manual merge conditions sections. * Allow only auto merge: Enables you to configure only the auto-merge conditions. Displays the Auto merge conditions section. * Allow only manual merge: Enables you to configure only the manual-merge conditions. Displays the Manual merge conditions section. {#config-pr-merge__ul_g41_trw_ycc} |
   | Matching conditions | Include custom fields that you want as part of the condition builder. Move the required fields from the Available list to the Selected list. Let's consider a scenario with two PRs, PR1 and PR2. For these PRs to be merged, the values in the fields defined in the matching conditions must be identical in both PRs. For example, if the matching conditions contain the Cost center and Legal entity fields, PR1's cost center must match PR2's cost center, and the same goes for their legal entity values. |
   | Auto merge conditions | Allows you to define conditions to automatically merge PRs, based on any of the fields available for a PR. This section becomes available after you select the Allow only auto merge option in the Merge type field. |
   | Manual merge conditions | Allows you to define conditions to manually merge PRs, based on any of the fields available for a PR. This section becomes available after you select the Allow only manual merge option in the Merge type field. |
   [ ]

   {#config-pr-merge__table_jzv_bqw_ycc}
5. Select Update.
**Related concepts**   

* [Service portal configuration for ShoppingHub](https://servicenow-prod.fluidtopics.net/n5Frl4qUcW4II1iBfmAbWQ "As an admin, you can configure your service portal such that shoppers who are on the portal can quickly access ShoppingHub and even view purchasing and approval to-dos assigned to them.")
* [Advanced Work Assignment for Source-to-Pay Operations](https://servicenow-prod.fluidtopics.net/IPTtX0i1oJ_j3s66KkWleQ "Use the Advanced Work Assignment for Source-to-Pay Operations feature to automatically assign work items to agents based on availability and capacity.")  
**Related tasks**   

* [Install Sourcing and Procurement Operations](https://servicenow-prod.fluidtopics.net/lJx2dRk79hEsBi_j0ENl3Q "Install Sourcing and Procurement Operations and its dependent applications from the ServiceNow Store.")
* [Configure punchout for third-party site purchases](https://servicenow-prod.fluidtopics.net/Vs8h07HkgeicMr_K50zxoQ "Set up punchout configuration to allow shoppers or employees to make third-party site purchases​.")
* [Customize your top suppliers on Shopping Hub](https://servicenow-prod.fluidtopics.net/e~2s3WNILkxGkgm6V6yZGw "Personalize the list of suppliers to see on your Shopping Hub homepage. Update your list with the change in your preferences anytime.")
* [Install ShoppingHub Mobile](https://servicenow-prod.fluidtopics.net/twuVIEJEf_N8jT5AYHbQSg "Install the Shopping Hub Mobile application from the ServiceNow Store.")  
**Related reference**   

* [Setting up primary data for ShoppingHub](https://servicenow-prod.fluidtopics.net/pAtnjiky4qIUrg0euXuR6A "Create primary data of your suppliers and office locations that your suppliers deliver to. Define your product catalog with data of your product categories, product models, and supplier products. Define shopping controls to control the supplier product visibility to your employees.")

*[\>]: and then