{"id":27612,"date":"2023-10-27T05:27:01","date_gmt":"2023-10-27T05:27:01","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=27612"},"modified":"2023-10-27T05:27:05","modified_gmt":"2023-10-27T05:27:05","slug":"how-to-set-up-reports-in-payment-entry-transactions-to-be-available-to-print-based-on-legislation","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2023\/10\/27\/how-to-set-up-reports-in-payment-entry-transactions-to-be-available-to-print-based-on-legislation\/","title":{"rendered":"How to set up reports in Payment entry transactions to be available to print based on legislation"},"content":{"rendered":"\n

Have you ever pondered whether you could make the report printable based on the Legislation in Payment Entry Transaction screen? In Sage X3<\/a>, we have figured out how to make this achievable.<\/p>\n\n\n\n

Before we proceed, kindly note this setup is only possible when you have multiple legislation in your Sage X3 application.<\/strong><\/p>\n\n\n\n

When you have multiple legislation set up in your Sage X3 you’ll have this option enabled.<\/p>\n\n\n\n

New Stuff:<\/strong> Menu item title translation in Sage X3<\/a><\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 1: Payment Entry Setup<\/center><\/font>\n\n\n\n

In the Payment Entry setup-> Steps, you\u2019ll find a field Report.<\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 2: Payment Entry Setup, Steps<\/center><\/font>\n\n\n\n

Jump into reports and create a new report code as below.<\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 3: Reports<\/center><\/font>\n\n\n\n

Note: the legislation and Process ID should be the same.<\/strong><\/p>\n\n\n\n

Once the Report is set up, on the selection of the report you\u2019ll find the below 2 options namely, NOTIF and ZIND. NOTIF is a default Report type that is Standard and is available for all legislation types and ZIND is the new report code that we set up. This ZIND report code will only be available when the Legislation type is IND.<\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 4: Reports Selection<\/center><\/font>\n\n\n\n

Now that the report code is attached to the Payment entry type, Validate the entry type and let\u2019s go to the final step, Print code.<\/p>\n\n\n\n

Now in the print code, you\u2019ll have to add the report code as follows. The first 3 characters, PAY, is the object code followed by the IND which is the Process name in the report code ZIND we created (refer Fig 3: Reports).<\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 5: Print Code<\/center><\/font>\n\n\n\n

If suppose you need to further bifurcate your report with the currency as well then you can add it as PAYINDEUR where EUR is the currency code. Refer the below Fig for your reference.<\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 6: Print code with further bifurcation of currency<\/center><\/font>\n\n\n\n

Now that the Print code is setup, you can check your payment entry transaction type where the legislation is IND and with the report code as ZIND you\u2019ll only find these 2 report codes available for print and for the rest of the transaction where legislation is not IND and Report code is not ZIND these reports will not be available for print.<\/p>\n\n\n\n

\"Fig<\/a><\/center>\n
Fig 7: Report selection in Payment entry screen<\/center><\/font>\n\n\n\n

Hence following the above steps you can add Reports to be available as per the legislation in the Payment Entry Screen.<\/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":"

Have you ever pondered whether you could make the report printable based on the Legislation in Payment Entry Transaction screen? In Sage X3, we have figured out how to make this achievable. Before we proceed, kindly note this setup is only possible when you have multiple legislation in your Sage X3 application. When you have\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":[860,1270,3873,3872,1822],"class_list":["post-27612","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-function","tag-menu-item","tag-menu-submodule","tag-report-as-module","tag-sage-x3"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27612","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=27612"}],"version-history":[{"count":12,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27612\/revisions"}],"predecessor-version":[{"id":27626,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27612\/revisions\/27626"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=27612"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=27612"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=27612"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}