{"id":23817,"date":"2021-10-28T07:26:43","date_gmt":"2021-10-28T07:26:43","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=23817"},"modified":"2021-10-28T07:26:45","modified_gmt":"2021-10-28T07:26:45","slug":"restriction-on-sales-order-if-date-exceeds-the-defined-due-date","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2021\/10\/28\/restriction-on-sales-order-if-date-exceeds-the-defined-due-date\/","title":{"rendered":"Restriction on Sales Order if date exceeds the defined due date"},"content":{"rendered":"\n

Due date is defined in every Sales\/Purchase transaction in Sage X3 <\/a>on the basis of Payment terms and Payment terms is a mandatory field in every transaction. One of our client requested to restrict Sales Order transaction on the basis of due date. Number of days beyond which if payment of posted Sales Invoice is due for a customer, then order process will be restricted for that customer. In simple words, a Validation is required where if the defined date is exceeded beyond the defined due date in the Sales Invoice transaction and payment is not done against that invoice then the user should not be allowed to create Sales Order for the same customer.<\/p>\n\n\n\n

In Payment Terms master, user will define the no. of days of Credit Payment which will be linked with the Customer Master. But the user can change payment terms value in Sales Invoice screen and only payment terms selected in the Sales Invoice will be considered.<\/p>\n\n\n\n

For this purpose, we will save the required setup in the Customer master.<\/p>\n\n\n\n

New Stuff:<\/strong> How to create dashboard using statistical parameters in Sage X3 V12<\/a><\/p>\n\n\n\n

\"[Authorized<\/a><\/center>\n
[Authorized Credit in Customer Master]<\/center><\/font>\n\n\n\n

As shown in the above screenshot, \u201cCheck\u201d option should be selected in Credit Control section and Authorized Credit Amount should be saved in the customer master, then only the functionality of Due date will work. We have saved these settings for the customer \u2013 CD0163.<\/p>\n\n\n\n

After that we have created and posted one Sales Invoice entry for the same customer \u2013 CD0163 on 10\/11\/21 i.e. on 11th October. And \u201cNP01\u201d is selected in Payment terms field in the Sales Invoice screen in which 21 days are saved. That means due date of the invoice will be considered after 21 days of the creation date.<\/p>\n\n\n\n

\"[Due<\/a><\/center>\n
[Due Date of Invoice]<\/center><\/font>\n\n\n\n

As sown in the screenshot, due date is 11\/01\/21 i.e. 1st November which is calculated as 11th October (Creation Date) + 21 Days.<\/p>\n\n\n\n

We have not created any payment entry against that Sales Invoice till 1st November. Payment Amount for that customer is \u20180\u2019.<\/p>\n\n\n\n

Now, we will try to create Sales Order entry for the same customer \u2013 CD0163 on 2nd November.<\/p>\n\n\n\n

\"[Pop-up<\/a><\/center>\n
[Pop-up Message on Sales Order Screen]<\/center><\/font>\n\n\n\n

If you have observed in the above screenshot, it is giving pop-up \u201cThe Transaction Date for this customer should not be greater than it\u2019s Due Date 01\/11\/2021\u201d. It will not allow user to create any Sales Order for the same customer until Payment is done against the Sales Invoice.<\/p>\n\n\n\n

Hence with the help of this customization, Sales Order transactions will be restricted if date exceeds the defined Due Date.<\/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":"

Due date is defined in every Sales\/Purchase transaction in Sage X3 on the basis of Payment terms and Payment terms is a mandatory field in every transaction. One of our client requested to restrict Sales Order transaction on the basis of due date. Number of days beyond which if payment of posted Sales Invoice is\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":[13,8],"tags":[3172,477,3456,2906,3099,1977],"class_list":["post-23817","post","type-post","status-publish","format-standard","hentry","category-integration","category-sage-erp-x3","tag-amount","tag-customer","tag-due-date","tag-payment-term","tag-restriction","tag-sales"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/23817","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=23817"}],"version-history":[{"count":6,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/23817\/revisions"}],"predecessor-version":[{"id":23823,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/23817\/revisions\/23823"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=23817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=23817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=23817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}