{"id":32095,"date":"2026-04-29T06:16:50","date_gmt":"2026-04-29T06:16:50","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=32095"},"modified":"2026-04-29T06:16:50","modified_gmt":"2026-04-29T06:16:50","slug":"how-to-resolve-index-incorrect-fld80-error-in-stock-transaction-inquiry-screen-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2026\/04\/29\/how-to-resolve-index-incorrect-fld80-error-in-stock-transaction-inquiry-screen-in-sage-x3\/","title":{"rendered":"How to Resolve \u201cIndex Incorrect FLD(80)\u201d Error in Stock Transaction Inquiry Screen in Sage X3"},"content":{"rendered":"\n

The Stock Transaction Inquiry screen in Sage X3<\/a> is a powerful tool used to track and analyze stock movements across the system. It allows users to view detailed transaction history, helping in inventory monitoring, audit tracking, and decision-making.<\/p>\n\n\n\n

Recently, a client required the addition of a custom field in the Stock Transaction Inquiry screen. While adding the custom field in the inquiry code, the field was successfully reflected in the inquiry window. However, it was not visible on the inquiry screen.<\/p>\n\n\n\n

To display the field on the screen, it is necessary to assign the correct position in the inquiry code. During this process, when navigating (jumping) from the inquiry code, the following error <\/strong>was encountered:<\/p>\n\n\n\n

“@X3.TRT\/SUBGTC$adx (302) Error 8 : Index Incorrect FLD(80)”<\/strong><\/p>\n\n\n\n

This error typically occurs due to incorrect field positioning or index mismatch in the inquiry configuration.<\/p>\n\n\n\n

In this blog, we will walk through the step-by-step solution to resolve this issue and successfully display the custom field on the inquiry screen.<\/p>\n\n\n\n

First, we added the custom fields in FCNSSMV (Window) \u2192 CONSSMV2 (Screen)<\/strong>. After that, we navigated to the Inquiry Code SMV (Inquiry Screen) and attempted to jump to the default screen code STD. At this point, the system generated an error, as shown in Figure 1 & 2 below.<\/p>\n\n\n\n

New Stuff:<\/strong> How to Enable Log (Trace) for Work Order Creation in Sage X3 Enterprise Planning<\/a><\/p>\n\n\n\n

\"SMV<\/a><\/center> \n
SMV inquiry screen<\/center><\/font>\n\n\n\n
\"Error\"<\/a><\/center> \n
Error<\/center><\/font>\n\n\n\n

Step 1: Increase Field Limit in Inquiry Screen.<\/strong><\/p>\n\n\n\n

Go to OGTC (Windows) \u2192 GTC1 (Inquiry Screens).<\/p>\n\n\n\n

Increase the number of lines from 80 to 99 (or as per your requirement). After updating the line count, navigate to the FLD (Field) section and simply press the Tab key. The system will automatically adjust and set the field dimension (DIM) to 99, as shown in Figure 3 & 4 below.<\/p>\n\n\n\n

\"OGTC<\/a><\/center> \n
OGTC Windows<\/center><\/font>\n\n\n\n
\"Increase<\/a><\/center> \n
Increase line 80 to 99<\/center><\/font> \n\n\n\n

Step 2: Update Table Field Dimensions<\/strong><\/p>\n\n\n\n

Navigate to Tables \u2192 GTABACC.<\/p>\n\n\n\n

Increase the dimension (DIM) of the required four fields to 99, as shown in Figure 5. After making the changes, make sure to validate the table to apply the updates.<\/p>\n\n\n\n

\"Update<\/a><\/center> \n
Update Table Field Dimensions<\/center><\/font> \n\n\n\n

The error “@X3.TRT\/SUBGTC$adx (302) Error 8 : Index Incorrect FLD(80)” occurs due to limitations in the field dimension and improper indexing while adding custom fields in the inquiry screen.<\/p>\n\n\n\n

By increasing the field limit in OGTC (Inquiry Screens) and updating the field dimensions in the GTABACC table, the system is able to accommodate additional fields without any index conflict.<\/p>\n\n\n\n

After applying these changes and validating the setup, the error is resolved successfully, and the custom fields are displayed correctly on the Stock Transaction Inquiry screen.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

The Stock Transaction Inquiry screen in Sage X3 is a powerful tool used to track and analyze stock movements across the system. It allows users to view detailed transaction history, helping in inventory monitoring, audit tracking, and decision-making. Recently, a client required the addition of a custom field in the Stock Transaction Inquiry screen. While\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,13],"tags":[4553,3011,4555,4554],"class_list":["post-32095","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-index-incorrect-fld80","tag-inquiry-screen","tag-ogtc-window","tag-stock-transaction-inquiry-screen"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32095","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=32095"}],"version-history":[{"count":9,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32095\/revisions"}],"predecessor-version":[{"id":32104,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/32095\/revisions\/32104"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=32095"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=32095"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=32095"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}