{"id":31110,"date":"2025-08-29T07:06:36","date_gmt":"2025-08-29T07:06:36","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=31110"},"modified":"2025-08-29T07:06:36","modified_gmt":"2025-08-29T07:06:36","slug":"disabling-work-order-options-until-sales-order-approval-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2025\/08\/29\/disabling-work-order-options-until-sales-order-approval-in-sage-x3\/","title":{"rendered":"Disabling Work Order Options Until Sales Order Approval in Sage X3"},"content":{"rendered":"\n

A client recently had a requirement related to restricting Work Order creation in Sales Orders under certain conditions. Specifically:<\/p>\n\n\n\n

When the Product Source type is Work Order on a Sales Order line, the Work Order generation options should not be available until the Sales Order is fully approved.<\/p>\n\n\n\n

This blog explains how we achieved this by customizing the Sales Order screen (OSOH) and controlling the visibility and access to Work Order creation options in Sage X3<\/a>.<\/p>\n\n\n\n

Work Order Generation in Sales Order Screen<\/strong>:<\/p>\n\n\n\n

There are two ways to generate a Work Order from the Sales Order screen:<\/p>\n\n\n\n

    \n
  1. At the line level via the 3-dot menu \u2014 Multilevel Planning<\/strong><\/li>\n<\/ol>\n\n\n\n

    New Stuff:<\/strong> HSBC Integration with Sage X3<\/a><\/p>\n\n\n\n

    \"fig1<\/a><\/center>\n
    fig1 multilevel planning<\/center><\/font>\n\n\n\n

    On the right panel of the Sales Order screen via the 3-dot menu \u2014 Work Order<\/p>\n\n\n\n

    \"fig2<\/a><\/center>\n
    fig2 work order menu<\/center><\/font>\n\n\n\n

    Implementation Steps<\/strong><\/p>\n\n\n\n

      \n
    1. Hide ‘Multilevel Planning’ Option at Line Level
      To achieve this, we used the Init Button action on the NBLIG field within the SOH4 screen of the Sales Order window.<\/li>\n<\/ol>\n\n\n\n

      Steps:<\/strong><\/p>\n\n\n\n

        \n
      1. Go to: Development \u2192 Script Dictionary \u2192 Windows \u2192 OSOH<\/li>\n\n\n\n
      2. Open the SOH4 screen.<\/li>\n\n\n\n
      3. Click on the field NBLIG.<\/li>\n\n\n\n
      4. Add the Init Button action.<\/li>\n\n\n\n
      5. Save and validate the screen.<\/li>\n\n\n\n
      6. Globally validate the OSOH window and the Sales Order transactions from setup module.<\/li>\n<\/ol>\n\n\n\n
        \"fig3<\/a><\/center>\n
        fig3 SOH4 screen<\/center><\/font>\n\n\n\n

        Code:<\/strong>
        Add the code below script to hide the Multilevel Planning option when the condition is met:
        If Product source = 5 AND (Signed flag <> 3 OR Signed flag <> 5)
        Raz GBOUT15
        ##Here the GBOUT15 is the button code for multi-level planning option
        else
        ENDIF<\/p>\n\n\n\n

        This hides the Multilevel Planning option from the line-level 3-dot menu if the product source is Work Order and the Sales Order is not fully approved.<\/p>\n\n\n\n

          \n
        1. Disable ‘Work Order’ Option at Header Level<\/strong><\/li>\n<\/ol>\n\n\n\n

          To control the Work Order menu on the right-hand panel, we added following script<\/p>\n\n\n\n

          Code:<\/strong>
          If Product source = 5 AND (Signed flag <> 3 OR Signed flag <> 5)
          ##Stop the standard process then use the below code
          Call VIREBOUT(CHMEN,”DM”) From GOBJET
          else
          ENDIF<\/p>\n\n\n\n

          This disables the Work Order option if the condition is met for any line in the Sales Order.<\/p>\n\n\n\n

          Final Result<\/strong>
          With these changes:<\/p>\n\n\n\n

          \u2022 The Multilevel Planning option is hidden at the line level until the Sales Order is approved.
          \u2022 The Work Order option on the header is disabled until the Sales Order is approved.<\/p>\n\n\n\n

          \"fig4<\/a><\/center>\n
          fig4 Output<\/center><\/font>\n\n\n\n

          These conditions ensure that Work Orders are only generated post-approval, maintaining process control and data integrity.<\/p>\n\n\n\n

          Summary Table<\/strong><\/p>\n\n\n\n

          Feature<\/strong><\/td>Location<\/strong><\/td>Action Used<\/strong><\/td>Script \/ Field<\/strong><\/td>Condition Applied<\/strong><\/td><\/tr>
          Multilevel Planning Button<\/td>Line level (3-dot)<\/td>Init Button<\/td>SPESOH script\/NBLIG in SOH4 screen<\/td>Product Source = 5 AND SO not approved<\/td><\/tr>
          Work Order Menu<\/td>Header (3-dot)<\/td>SETBOUT <\/td>SPESOH script<\/td>Product Source = 5 AND SO not approved<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n[about_us_blog_common]\n","protected":false},"excerpt":{"rendered":"

          A client recently had a requirement related to restricting Work Order creation in Sales Orders under certain conditions. Specifically: When the Product Source type is Work Order on a Sales Order line, the Work Order generation options should not be available until the Sales Order is fully approved. This blog explains how we achieved this\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,13],"tags":[603,4407,4402,1822,2428],"class_list":["post-31110","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-disable-button","tag-disable-menu","tag-field-options","tag-sage-x3","tag-work-order"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/31110","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=31110"}],"version-history":[{"count":8,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/31110\/revisions"}],"predecessor-version":[{"id":31118,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/31110\/revisions\/31118"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=31110"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=31110"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=31110"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}