{"id":9641,"date":"2016-12-29T11:17:31","date_gmt":"2016-12-29T11:17:31","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=9641"},"modified":"2016-12-29T11:17:31","modified_gmt":"2016-12-29T11:17:31","slug":"how-to-determine-the-characters-of-the-user-entry-types-in-sage-erp-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2016\/12\/29\/how-to-determine-the-characters-of-the-user-entry-types-in-sage-erp-x3\/","title":{"rendered":"How to determine the characters of the user entry types in sage ERP X3?"},"content":{"rendered":"

Adxtuc<\/strong> determines the characters of the user entry types. You may define types of entry that will be added to – or even substituted by – \u00a0standard types within an Adonix application. These extra types are described by one letter: their “code.”<\/p>\n

Syntax:<\/u><\/p>\n

[S]adxtuc (33) (32) Char<\/p>\n

Example:<\/u><\/p>\n

\"characters<\/p>\n

Output:<\/u><\/p>\n

\"determine<\/a><\/p>\n

Description :
\n<\/a><\/u><\/p>\n

You may parameterize 32 extra types accordingly, but the application is limited to 9 extra types. You may enter them in the TUL1 through TUL9 parameters of the ADX chapter, or module. The first nine workstations of adxtul<\/strong> are loaded by the supervisor by these TUL1 to TUL9 parameters.<\/p>\n

The characters composing each type are defined by a maximum of 17 sub-types and up to 33 additional characters.<\/p>\n

The additional characters must be editable and therefore have an ASCII code included in the ranges from 32 to 127 and from 149 to 255.<\/p>\n

The value of adxtuc<\/strong> is a character string, the result of the concatenation of these additional characters, and without a separator. If this string is empty, you will only be able to enter the characters of the sub-type(s).<\/p>\n

adxtuc<\/strong> is a table system variable of Char of 33 characters, each one parameterizing these additional characters. Assigning it allows you to modify this parameter.<\/p>\n

About Us:<\/strong><\/p>\n

Greytrix is one stop solution provider for Sage ERP and Sage CRM needs. We provide complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third party add-on development and implementation expertise.<\/p>\n

Greytrix<\/a>\u00a0have some unique solutions of\u00a0Sage X3\u2019s integration with Sage CRM<\/a>,\u00a0Salesforce.com<\/a>\u00a0and\u00a0Magento eCommerce<\/a>. It also offers best-in-class\u00a0Sage X3 customization and development services<\/a>\u00a0to Sage business partners, end users, and Sage PSG worldwide.<\/p>\n

For more information on Sage X3 Integration and Services, please contact us at\u00a0x3@greytrix.com<\/a>\u00a0.We will be glad to assist you.<\/p>\n

\u00a0Also Read:<\/u><\/strong><\/p>\n

–\u00a0How to restrict the user to enter limited characters in Sage ERP X3<\/a><\/p>\n

–\u00a0Getting number of fields in table<\/a><\/p>\n

–\u00a0How to extract a substring from the leftmost end in Sage X3?<\/a><\/p>\n

–\u00a0How to replace the character in the string?<\/a><\/p>\n

–\u00a0How to get the number of records which is deleted by Delete Command<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Adxtuc determines the characters of the user entry types. You may define types of entry that will be added to – or even substituted by – \u00a0standard types within an Adonix application. These extra types are described by one letter: their “code.” Syntax: [S]adxtuc (33) (32) Char Example: Output: Description : You may parameterize 32\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[584,1780,1941,1942,1943,1947],"class_list":["post-9641","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","tag-determine-the-characters-of-the-user-entry-types","tag-sage-erp-x3","tag-sage-x3-technical","tag-sage-x3-technical-assistance","tag-sage-x3-technical-blog","tag-sage-x3-technical-issues"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/9641","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=9641"}],"version-history":[{"count":0,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/9641\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=9641"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=9641"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=9641"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}