{"id":28478,"date":"2024-02-20T09:10:56","date_gmt":"2024-02-20T09:10:56","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=28478"},"modified":"2024-02-21T04:33:34","modified_gmt":"2024-02-21T04:33:34","slug":"identifying-local-menu-data-from-message-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2024\/02\/20\/identifying-local-menu-data-from-message-in-sage-x3\/","title":{"rendered":"Identifying local menu data from message in Sage X3"},"content":{"rendered":"\n<p>In <a href=\"https:\/\/www.greytrix.com\/sage-x3\/sage-x3-development\/\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.greytrix.com\/sage-x3\/sage-x3-development\/\" rel=\"noreferrer noopener\">Sage X3<\/a>, we often come across some standard messages for which we want to track back its local menu chapter for either reusing purposes or data fetching. In Sage X3 this can be done very efficiently using the <strong>Message search utility<\/strong>.<\/p>\n\n\n\n<p>To know more about this, we\u2019ll show a small example of how we are identifying the pop-up message within the purchase request module and its local menu chapter.<\/p>\n\n\n\n<p>For this we\u2019re referencing following paths and screenshots below:<\/p>\n\n\n\n<p><strong>Message Search:<\/strong> All &gt; Development &gt; Searches &gt; Message <strong>(RECHMESS)<\/strong><br><strong>Local Menu:<\/strong> All &gt; Development &gt; Data and parameters &gt; Tables &gt; Local menus &#8211; messages <strong>(TXT)<\/strong><br><strong>Purchase Request:<\/strong> All &gt; Purchasing &gt; Purchase requests &gt; Purchase requests <strong>(GESPSH)<\/strong><\/p>\n\n\n\n<p><strong>New Stuff: <\/strong><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2024\/02\/15\/adding-additional-invoices-to-closed-pos-in-sage-x3\/\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2024\/02\/15\/adding-additional-invoices-to-closed-pos-in-sage-x3\/\" rel=\"noreferrer noopener\">Adding Additional Invoices to Closed POs in Sage X3<\/a><\/p>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-1-Text-message-on-Order-button-1024x330.png\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-1-Text-message-on-Order-button-1024x330.png\" alt=\"Fig. 1 - Text message on Order button\"><\/a><\/center>\n<font size=\"2\"><center>Fig. 1 &#8211; Text message on Order button<\/center><\/font>\n\n\n\n<p>-As shown in <strong>Fig. 1<\/strong> we have our Purchase request entry transaction and we\u2019ve clicked the Order button upon which the system throws a warning box. Now we\u2019ll identify whether the message is fetched through a local menu.<\/p>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-2-Message-search-utility-1024x343.png\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-2-Message-search-utility-1024x343.png\" alt=\"Fig. 2 - Message search utility\"><\/a><\/center>\n<font size=\"2\"><center>Fig. 2 &#8211; Message search utility<\/center><\/font>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-3-Put-in-the-message.png\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-3-Put-in-the-message.png\" alt=\"Fig. 3 - Put in the messagep\"><\/a><\/center>\n<font size=\"2\"><center>Fig. 3 &#8211; Put in the message<\/center><\/font>\n\n\n\n<p>-First we\u2019ll navigate over to the Message search utility from the above path as shown in <strong>Fig. 2<\/strong> and then enter the popped message in the text field as shown in<strong> Fig. 3<\/strong> and hit OK.<\/p>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-4-The-local-menu-chapter-and-number.png\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-4-The-local-menu-chapter-and-number.png\" alt=\"Fig. 4 - The local menu chapter and number\"><\/a><\/center>\n<font size=\"2\"><center>Fig. 4 &#8211; The local menu chapter and number<\/center><\/font>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-5-Checking-the-local-menu-data-1024x529.png\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2024\/02\/Fig.-5-Checking-the-local-menu-data-1024x529.png\" alt=\"Fig. 5 - Checking the local menu data\"><\/a><\/center>\n<font size=\"2\"><center>Fig. 5 &#8211; Checking the local menu data<\/center><\/font>\n\n\n\n<p>-After the search is complete a log displays all the traced local menus data formatted in the below format:<br><strong>mess(message line, chapter no, message translation no. in integer)<\/strong><\/p>\n\n\n\n<p>For our example, we received mess(0086, 00194, 1) which means our local menu chapter is 194 and message line is 86 with ENG translation as shown in Fig. 5.<\/p>\n\n\n\n<p>This way we can identify whether a message has a linked local menu chapter in Sage X3 which makes helpful to track and reuse the message.<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-text-color has-link-color wp-elements-c5e1638fe0db781fd132d689b469078c\" style=\"color:#c71d22\"><strong>About Us<\/strong><\/h2>\n\n\n\n<p>Greytrix \u2013 a globally recognized and one of the oldest Sage Development Partners is a one-stop solution provider for Sage ERP and Sage CRM organizational needs. Being acknowledged and rewarded for multi-man years of experience and expertise, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development, and implementation competence.<\/p>\n\n\n\n<p id=\"block-28013e99-0882-44c6-b705-7b16c85053b2\">Greytrix&nbsp;has some unique integration solutions developed for&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-crm\/\">Sage CRM<\/a>&nbsp;with Sage ERPs&nbsp;namely&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-x3-erp\/\">Sage X3<\/a>,&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-intacct\/\">Sage Intacct<\/a>,&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-100-erp\/\">Sage 100<\/a>,&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-500-erp\/\">Sage 500<\/a>,&nbsp;and&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-300-erp\/\">Sage 300<\/a>. We also offer best-in-class&nbsp;Sage ERP&nbsp;and&nbsp;Sage CRM&nbsp;customization and development services&nbsp;to&nbsp;Business&nbsp;Partners,&nbsp;End&nbsp;Users, and Sage PSG worldwide. Greytrix&nbsp;helps in&nbsp;the migration of Sage CRM from&nbsp;Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes&nbsp;addons like&nbsp;&nbsp;Greytrix Business Manager,&nbsp;Sage CRM Project Manager,&nbsp;Sage CRM Resource Planner,&nbsp;Sage CRM Contract Manager,&nbsp;Sage CRM Event Manager,&nbsp;Sage CRM Budget Planner,&nbsp;Gmail Integration,&nbsp;Sage CRM Mobile Service Signature,&nbsp;Sage CRM CTI Framework.<\/p>\n\n\n\n<p id=\"block-4bc42a09-fb13-4598-8137-ce5f7b91ce28\">Greytrix is a recognized&nbsp;Sage Champion Partner&nbsp;for GUMU&#x2122; Sage X3 \u2013 Sage CRM integration listed on&nbsp;<a href=\"https:\/\/www.sage.com\/marketplace\/asb_ListingDetail?listingId=a1h24000007PC3aAAG\" target=\"_blank\" rel=\"noreferrer noopener\">Sage Marketplace<\/a>&nbsp;and Sage CRM \u2013 Sage Intacct integration listed on&nbsp;<a href=\"https:\/\/marketplace.intacct.com\/MPListing?lid=a2D0H000007kiHyUAI\" target=\"_blank\" rel=\"noreferrer noopener\">Sage Intacct Marketplace<\/a>. The&nbsp;<a href=\"https:\/\/www.greytrix.com\/gumu\/\" target=\"_blank\" rel=\"noreferrer noopener\">GUMU&#x2122; Cloud framework<\/a>&nbsp;by Greytrix forms the backbone of cloud integrations that are managed in real-time for the processing and execution of application programs at the click of a button.<\/p>\n\n\n\n<p id=\"block-76376301-1c3e-4250-8a09-727595a606f0\">For more information on our integration solutions, please contact us at&nbsp;<a href=\"mailto:sage@greytrix.com\">sage@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In Sage X3, we often come across some standard messages for which we want to track back its local menu chapter for either reusing purposes or data fetching. In Sage X3 this can be done very efficiently using the Message search utility. To know more about this, we\u2019ll show a small example of how we\u2026 <span class=\"read-more\"><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2024\/02\/20\/identifying-local-menu-data-from-message-in-sage-x3\/\">Read More &raquo;<\/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":[4031,1176,1269,1276,1822,3927,2343],"class_list":["post-28478","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-chapter","tag-local","tag-menu","tag-message","tag-sage-x3","tag-transform","tag-utility"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28478","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=28478"}],"version-history":[{"count":8,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28478\/revisions"}],"predecessor-version":[{"id":28486,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28478\/revisions\/28486"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=28478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=28478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=28478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}