{"id":17891,"date":"2026-01-28T09:42:57","date_gmt":"2026-01-28T09:42:57","guid":{"rendered":"https:\/\/tenthplanet.in\/idempiere\/?p=17891"},"modified":"2026-01-28T09:42:59","modified_gmt":"2026-01-28T09:42:59","slug":"how-closure-and-finalization-of-rfq-works-in-idempiere","status":"publish","type":"post","link":"https:\/\/tenthplanet.in\/idempiere\/how-closure-and-finalization-of-rfq-works-in-idempiere\/","title":{"rendered":"How Closure and Finalization of RFQ Works in iDempiere"},"content":{"rendered":"\n

The Close RFQ<\/strong> action formally ends the RFQ lifecycle in iDempiere. It locks the RFQ, finalizes all responses, and marks sourcing as complete, separating vendor evaluation from execution while preventing late changes or inconsistent downstream processing.<\/p>\n\n\n\n

RFQ Ready for Closure<\/strong><\/h2>\n\n\n\n

Before closing an RFQ, the system expects that the sourcing decision is already complete. Typically, this means RFQ responses are collected, reviewed, and\u2014if required\u2014ranked and marked with a selected winner<\/strong>. At this stage, purchase orders or sales orders may already be created, but the RFQ itself remains open until explicitly closed.<\/p>\n\n\n\n

This design allows procurement teams to finish execution documents first and then formally seal the RFQ.<\/p>\n\n\n\n

Key readiness indicators:<\/strong><\/p>\n\n\n\n

    \n
  • RFQ responses are created and evaluated<\/li>\n\n\n\n
  • Winning response is identified (manually or via Rank Responses)<\/li>\n\n\n\n
  • No further vendor input is expected<\/li>\n<\/ul>\n\n\n\n

    Close RFQ Process Execution<\/strong><\/h2>\n\n\n\n

    The Close RFQ process is triggered from the gear (Process) menu<\/strong> on the RFQ header. When selected, the system opens the c<\/strong>lose<\/strong> RFQ and <\/strong>r<\/strong>esponses<\/strong> dialog. This dialog controls how the closure is executed and how stakeholders are informed.<\/p>\n\n\n\n

    The process can be run immediately or scheduled as a background job. When r<\/strong>un<\/strong> as <\/strong>j<\/strong>ob<\/strong> is enabled, the system executes closure asynchronously and sends a notification to the process owner once completed.<\/p>\n\n\n\n

    Dialog controls include:<\/strong><\/p>\n\n\n\n

      \n
    • Run as Job<\/strong> \u2013 Executes closure in background<\/li>\n\n\n\n
    • Notification Type<\/strong> \u2013 Defines how closure status is communicated (e.g., Email)<\/li>\n<\/ul>\n\n\n\n
      \"\"<\/figure>\n\n\n\n

      System Actions During RFQ Closure<\/strong><\/h2>\n\n\n\n

      Once the close RFQ process runs successfully, iDempiere performs a coordinated set of system updates. These updates ensure data integrity across RFQ, RFQ responses, and downstream documents.<\/p>\n\n\n\n

      The RFQ is marked as p<\/strong>rocessed<\/strong>, which immediately blocks:<\/p>\n\n\n\n

        \n
      • New RFQ responses<\/li>\n\n\n\n
      • Changes to RFQ header<\/li>\n\n\n\n
      • Changes to RFQ lines and quantities<\/li>\n<\/ul>\n\n\n\n

        At the same time, all linked RFQ responses are finalized. No response\u2014winner or non-winner\u2014can be edited further. This guarantees that procurement decisions remain auditable and stable.<\/p>\n\n\n\n

        System effects applied automatically:<\/strong><\/p>\n\n\n\n

          \n
        • RFQ p<\/strong>rocessed<\/strong> checkbox is set<\/li>\n\n\n\n
        • RFQ becomes read-only<\/li>\n\n\n\n
        • All RFQ responses are locked<\/li>\n\n\n\n
        • Process completion message is logged and notified<\/li>\n<\/ul>\n\n\n\n

          RFQ State After Closure<\/strong><\/h2>\n\n\n\n

          After closure, the RFQ remains visible for reporting, traceability, and audit purposes, but it is no longer part of active operations. Users can still open the RFQ to review details, responses, rankings, and linked documents such as purchase orders or sales orders.<\/p>\n\n\n\n

          The p<\/strong>rocessed<\/strong> indicator clearly signals that the RFQ lifecycle has ended. This distinction is essential in environments with recurring or cooperative RFQs, where historical RFQs must not be reused unintentionally.<\/p>\n\n\n\n

          \"\"<\/figure>\n\n\n\n

          Purpose of Closing RFQ<\/strong><\/h2>\n\n\n\n

          Closing an RFQ enforces commercial discipline. It ensures that once sourcing decisions are finalized, the organization moves forward with execution instead of revisiting negotiations or allowing late changes.<\/p>\n\n\n\n

          From a governance perspective, this step creates a clean boundary between:<\/p>\n\n\n\n

            \n
          • Sourcing phase<\/strong> (RFQ, responses, evaluation)<\/li>\n\n\n\n
          • Execution phase<\/strong> (purchase orders, sales orders, logistics, invoicing)<\/li>\n<\/ul>\n\n\n\n

            It also supports audit and compliance requirements by preserving a frozen snapshot of the RFQ decision.<\/p>\n\n\n\n

            Use Cases<\/strong><\/h2>\n\n\n\n
              \n
            • Preventing vendors from submitting late quotations<\/li>\n\n\n\n
            • Locking RFQ data after winner selection<\/li>\n\n\n\n
            • Finalizing sourcing cycles for audit or compliance<\/li>\n\n\n\n
            • Ensuring RFQs are not reused in future cycles<\/li>\n\n\n\n
            • Supporting clean reporting for answered vs. closed RFQs<\/li>\n<\/ul>\n\n\n\n

              Outcome and System Integrity<\/strong><\/h2>\n\n\n\n

              After an RFQ is closed:<\/p>\n\n\n\n

                \n
              • Procurement decisions are finalized<\/li>\n\n\n\n
              • Downstream documents remain valid and traceable<\/li>\n\n\n\n
              • Reporting reflects accurate RFQ status<\/li>\n\n\n\n
              • Data integrity is preserved across purchasing and sales<\/li>\n<\/ul>\n\n\n\n

                The close RFQ action ensures that iDempiere treats the RFQ as a completed sourcing artifact<\/strong>, not an active transaction. This keeps procurement workflows predictable, auditable, and operationally safe.<\/p>\n\n\n\n

                In the RFQ lifecycle, c<\/strong>lose<\/strong> RFQ is the final control gate<\/strong> that confirms the sourcing process is finished and the organization has fully moved into execution and fulfillment.<\/p>\n","protected":false},"excerpt":{"rendered":"

                The Close RFQ action formally ends the RFQ lifecycle in iDempiere. It locks the RFQ, finalizes all responses, and marks […]<\/p>\n","protected":false},"author":19,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[],"class_list":["post-17891","post","type-post","status-publish","format-standard","hentry","category-purchase"],"acf":[],"_links":{"self":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/17891","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/comments?post=17891"}],"version-history":[{"count":0,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/posts\/17891\/revisions"}],"wp:attachment":[{"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/media?parent=17891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/categories?post=17891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tenthplanet.in\/idempiere\/wp-json\/wp\/v2\/tags?post=17891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}