{"id":27934,"date":"2023-12-28T10:31:15","date_gmt":"2023-12-28T10:31:15","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=27934"},"modified":"2023-12-28T10:54:24","modified_gmt":"2023-12-28T10:54:24","slug":"use-of-transcribe-import-export-template-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2023\/12\/28\/use-of-transcribe-import-export-template-in-sage-x3\/","title":{"rendered":"Use of Transcribe Import\/Export template in Sage X3"},"content":{"rendered":"\n

In Sage X3<\/a>, we make sure of import\/export templates quite often for importing huge data with ease. However sometimes the importing data templates are acquired through any external client application which might have different external data parameters which in Sage X3 are stored in different internal codes. Sage X3 provides us a Setup module that helps setting these in an efficient way.<\/p>\n\n\n\n

For example: MATERIALS<\/strong> are external codes for category while in Sage X3 product category is RM<\/strong>.<\/p>\n\n\n\n

To know more about this, we\u2019ll show a small example of how we are transcoding the Internal code with an external code that works both for Importing & exporting cases.<\/p>\n\n\n\n

For this we\u2019re referencing following paths and screenshots below:<\/p>\n\n\n\n

Imports\/Exports template: <\/strong>All > Setup > Usage > Imports\/Exports > Import\/Export template (GESAOE)<\/strong>
Transcribe Import\/Export:<\/strong> All > Setup > Usage > Imports\/Exports > Transcribe import\/export (GESAOR)<\/strong>
Exports: <\/strong>All > Usage > Imports\/Exports > Exports (GEXPOBJ)<\/strong>
Imports:<\/strong> All > Usage > Imports\/Exports > Imports (GIMPOBJ)<\/strong>
Products:<\/strong> All > Common Data > Products > Product (GESITM)<\/strong><\/p>\n\n\n\n

New Stuff: <\/strong>How to determine where the data type is used in Sage X3<\/a><\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 1 – ZITM template<\/center><\/font>\n\n\n\n

<\/p>\n\n\n\n

-As shown in Fig. 1<\/strong> we have our custom product template on which we\u2019ll showcase the part for Category field.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 2 – Normal exported data<\/center><\/font>\n\n\n\n

<\/p>\n\n\n\n

-When we try to export the data from the above template we get the data as shown in Fig. 2<\/strong> where we can see the Category as BRR<\/strong>.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 3 – Setting up custom Transcribe table<\/center><\/font>\n\n\n\n
\"Fig.<\/a><\/center>\n
Fig. 4 – Linking the transcribe table no. in Category field of template setup<\/center><\/font>\n\n\n\n

<\/p>\n\n\n\n

-Now to transform the category data we\u2019ll set up a new Transcribe import\/export table as shown in Fig. 3.<\/strong> In that we\u2019re adding the local code as BRR & external code as TESTCATEGORY<\/strong>. Once the table is created we\u2019re linking the table number<\/strong> to the Category field\u2019s Table number<\/strong> column as shown in Fig. 4<\/strong>.<\/p>\n\n\n\n

Note:-<\/strong> By sage standards it is recommended<\/strong> to use table numbers within the range 600-999<\/strong> as below can be overwritten by application updates<\/strong>.
-For the transcription process the following principles apply:<\/p>\n\n\n\n

Exports:<\/strong> A search for the field\u2019s original value is performed on the values in Local code and then transcribed to the value in External code.
Imports:<\/strong> The External code column is searched, and the value is transcribed to the Local code value.<\/p>\n\n\n\n

-Other important parts involve while setting up the table data:
– Spaces are not allowed<\/strong> in the Local code and External code values.
– To provide a default in the column being searched, use an \u201c * \u201d as the value.
– If the column being searched includes the same value more than once, the first transcription will be used<\/strong>.
– To prevent a specific value from being transcribed, set the transcribed value to \u201c * \u201d<\/strong>.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 5 – Export data having External code<\/center><\/font>\n\n\n\n

<\/p>\n\n\n\n

-Now once we export the same product data we can see the category BRR<\/strong> is transformed with TESTCATEGORY<\/strong> as shown in Fig. 5.<\/p>\n\n\n\n

-We can test the same scenario by Importing a template with an external code<\/strong> and in sage x3 the creation is handled with the internal code<\/strong> as shown in Fig. 6 & Fig. 7<\/strong> below.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 6 – Import data with external code<\/center><\/font>\n\n\n\n
\"Fig.<\/a><\/center>\n
Fig. 7 – Successful creation of custom product<\/center><\/font>\n\n\n\n

<\/p>\n\n\n\n

-As we can see in Fig. 8.<\/strong> Below The product masters of the created product have BRR<\/strong> as the category.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 8 – Internal code referenced during creation by Sage X3<\/center><\/font>\n\n\n\n

This way we can implement advanced restrictions on transactions using 4GL in Sage X3.<\/p>\n\n\n\n

About Us<\/strong><\/h2>\n\n\n\n

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

Greytrix has some unique integration solutions developed for Sage CRM<\/a> with Sage ERPs namely Sage X3<\/a>, Sage Intacct<\/a>, Sage 100<\/a>, Sage 500<\/a>, and Sage 300<\/a>. We also offer best-in-class Sage ERP and Sage CRM customization and development services to Business Partners, End Users, and Sage PSG worldwide. Greytrix helps in the migration of Sage CRM from Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes addons like  Greytrix Business Manager, Sage CRM Project Manager, Sage CRM Resource Planner, Sage CRM Contract Manager, Sage CRM Event Manager, Sage CRM Budget Planner, Gmail Integration, Sage CRM Mobile Service Signature, Sage CRM CTI Framework.<\/p>\n\n\n\n

Greytrix is a recognized Sage Champion Partner for GUMU™ Sage X3 \u2013 Sage CRM integration listed on Sage Marketplace<\/a> and Sage CRM \u2013 Sage Intacct integration listed on Sage Intacct Marketplace<\/a>. The GUMU™ Cloud framework<\/a> 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

For more information on our integration solutions, please contact us at sage@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

In Sage X3, we make sure of import\/export templates quite often for importing huge data with ease. However sometimes the importing data templates are acquired through any external client application which might have different external data parameters which in Sage X3 are stored in different internal codes. Sage X3 provides us a Setup module that\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":[765,771,1035,3928,2225,2254,3929,3927],"class_list":["post-27934","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-export","tag-external","tag-import","tag-internal","tag-table","tag-template","tag-transcribe","tag-transform"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27934","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=27934"}],"version-history":[{"count":17,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27934\/revisions"}],"predecessor-version":[{"id":27956,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27934\/revisions\/27956"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=27934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=27934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=27934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}