{"id":4838,"date":"2025-08-21T15:41:19","date_gmt":"2025-08-21T14:41:19","guid":{"rendered":"https:\/\/compera.vanvlerken.nl\/demand-aggregation-in-ariba-buying\/"},"modified":"2025-08-21T16:44:18","modified_gmt":"2025-08-21T15:44:18","slug":"demand-aggregation-in-ariba-buying","status":"publish","type":"post","link":"https:\/\/compera.vanvlerken.nl\/en\/demand-aggregation-in-ariba-buying\/","title":{"rendered":"Demand Aggregation in Ariba Buying"},"content":{"rendered":"\n[et_pb_section fb_built=”1″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” custom_margin=”|auto|-265px|auto||” custom_padding=”1px||186px|||” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” custom_margin=”-24px||16px|||” global_colors_info=”{}”]

Does your procurement department<\/span> also face the problem of multiple orders being placed <\/span>with the same supplier, each incurring separate delivery charges? These delivery costs can quickly escalate<\/span> if no arrangements can be made with the supplier to reduce them<\/span>. Often, such individual orders could have been consolidated into a single purchase orders.<\/span><\/p>\n

To address this inefficiency and reduce unnecessary costs, Ariba offers a powerful solution: Demand Aggregation.<\/span><\/p>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” min_height=”9px” custom_padding=”||0px|||” global_colors_info=”{}”]

How does demand aggregation work?<\/span><\/strong><\/h4>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” min_height=”416px” custom_margin=”-24px||5px|||” global_colors_info=”{}”]

Rather than immediately converting approved requests into purchase orders, Ariba Buying allows requests to be held for aggregation. These approved requests are temporarily blocked from being processed and are instead grouped based on pre-defined criteria.<\/p>\n

Standard variables include:<\/p>\n

    \n
  • Purchasing Unit<\/span><\/li>\n
  • Commodity Code<\/li>\n
  • Amount<\/li>\n
  • Contract (Yes\/No)<\/li>\n
  • Line Type<\/li>\n
  • Currency<\/li>\n
  • Supplier<\/li>\n<\/ul>\n

    Organisations may also configure up to 10 additional custom fields to tailor the aggregation logic to their specific needs.<\/p>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” min_height=”49px” custom_padding=”7px||15px|||” global_colors_info=”{}”]

    Assignment to buyers<\/strong><\/h4>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” min_height=”379px” custom_margin=”-31px||-22px|||” custom_padding=”||0px|||” global_colors_info=”{}”]

    Once a request is held for aggregation, it is assigned to a designated buyer. This assignment is similarly based on configurable variables:<\/span><\/p>\n

      \n
    • Purchasing Unit<\/span><\/li>\n
    • Commodity Code<\/span><\/li>\n
    • Contract (Yes\/No)<\/span><\/li>\n
    • Line Type<\/span><\/li>\n
    • Supplier<\/span><\/li>\n<\/ul>\n

      Again, up to 10 custom fields can be defined to direct assignments to appropriate buyers.<\/p>\n

      Requests held for aggregation become visible in the Procurement Workbench, where buyers can manually review and consolidate them per supplier before submission. This is visible in the next screenshot.<\/p>\n

      <\/p>[\/et_pb_text][et_pb_image src=”https:\/\/compera.vanvlerken.nl\/wp-content\/uploads\/2025\/08\/Plaatje_1_Engels-scaled.png” title_text=”Plaatje_1_Engels” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]

      The following screenshot shows the multiple individual requests are consolidated into a single aggregated request.<\/span><\/p>[\/et_pb_text][et_pb_image src=”https:\/\/compera.vanvlerken.nl\/wp-content\/uploads\/2025\/08\/Plaatje_2_Engels-scaled.png” title_text=”Plaatje_2_Engels” _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]

      Additional requests may later be added to an existing aggregated request. This is showed in the screenshot below.<\/span><\/p>[\/et_pb_text][et_pb_image src=”https:\/\/compera.vanvlerken.nl\/wp-content\/uploads\/2025\/08\/Plaatje_3_Engels-scaled.png” title_text=”Plaatje_3_Engels” _builder_version=”4.27.4″ _module_preset=”default” custom_margin=”-13px|||||” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]

      Automatic aggregation<\/strong><\/h4>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” custom_margin=”-21px|||||” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]

      Prefer a fully automated process? Ariba also supports automated demand aggregation using the following standard variables:<\/span><\/p>\n

        \n
      • Delivery Address<\/span><\/li>\n
      • Deliver-To (Recipient)<\/span><\/li>\n
      • Supplier<\/span><\/li>\n
      • Supplier Location<\/span><\/li>\n<\/ul>\n

        As with manual aggregation, you may define up to 10 additional custom fields to refine the logic.<\/span><\/p>\n

        Aggregation can be scheduled based on:<\/p>\n

          \n
        • A fixed day of the week<\/span><\/li>\n
        • A specific day of the month<\/span><\/li>\n
        • The last day of the month<\/span><\/li>\n<\/ul>\n

          Each schedule can be configured with an exact time of execution. Multiple aggregation windows per week or month are supported.<\/span><\/p>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]

          Key considerations<\/span><\/strong><\/h4>[\/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” min_height=”582px” custom_margin=”-17px|||||” custom_padding=”||1px|||” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]
            \n
          • Requests removed from the Procurement-Workbench are marked as cancelled and cannot be modified. A new request must be created.<\/li>\n
          • Aggregated requests follow a separate (optional) workflow.<\/li>\n
          • Only requests that meet the defined criteria are eligible for aggregation. Others are processed immediately after approval.<\/li>\n
          • Fields such as company code and ship to address in the aggregated request are inherited from the user who creates the aggregated request.<\/li>\n
          • This user who creates the aggregated request is also the formal requester, original requesters are not displayed.<\/li>\n
          • If the aggregated request consists solely of requests from one requester, it is possible to configure that person as the requester. Regardless of who submits the final aggregated request.<\/li>\n
          • The user who submits the aggregated request is responsible for the goods receipt or submitting the service entry sheet.<\/li>\n
          • No goods receipt or service entry sheet is required for the original requests.<\/li>\n<\/ul>\n

            Interested?<\/strong><\/p>\n

            If you would like to explore how Ariba\u2019s demand aggregation functionality can streamline your procurement process and reduce operational costs, please contact Compera<\/strong>, we would be pleased to assist you.<\/span><\/p>\n

             <\/p>[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]\n","protected":false},"excerpt":{"rendered":"

            Does your procurement department also face the problem of multiple orders being placed with the same supplier, each incurring separate delivery charges? These delivery costs can quickly escalate if no arrangements can be made with the supplier to reduce them. Often, such individual orders could…<\/p>\n","protected":false},"author":8,"featured_media":4836,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[102],"tags":[103,277,276,115,100,275],"class_list":["post-4838","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ariba-en","tag-ariba-en","tag-delivery-cost-en","tag-demand-aggregation-en","tag-guided-buying-en","tag-sap-en","tag-sap-ariba-en"],"_links":{"self":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/4838","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/comments?post=4838"}],"version-history":[{"count":4,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/4838\/revisions"}],"predecessor-version":[{"id":4847,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/posts\/4838\/revisions\/4847"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/media\/4836"}],"wp:attachment":[{"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/media?parent=4838"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/categories?post=4838"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/compera.vanvlerken.nl\/en\/wp-json\/wp\/v2\/tags?post=4838"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}