Configure conditions for merging purchase requisitions

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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.

    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

    Procedure

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

      Purchase requisition merge conditions.

    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.
      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.
      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.
    5. Select Update.