{"id":21377,"date":"2020-12-28T08:32:17","date_gmt":"2020-12-28T08:32:17","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=21377"},"modified":"2020-12-28T09:50:41","modified_gmt":"2020-12-28T09:50:41","slug":"restriction-on-purchase-invoice-creation","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2020\/12\/28\/restriction-on-purchase-invoice-creation\/","title":{"rendered":"Restriction on Purchase Invoice creation"},"content":{"rendered":"\n

As per the standard functionality of Sage X3<\/a>, if the user is entering same Supplier Document No in new Purchase Invoice entry which is already entered or used in the existing invoice entry then user gets a warning message popup that \u201cReference entered on Invoice(Invoice No)\u201d as shown in the below screenshot. But after clicking on \u201cOk or Cancel\u201d it allows user to create Invoice with the same document number. That means it is just a warning message and it depends on the user if he wants to continue with the same document no or different document no.<\/p>\n\n\n\n

New Stuff:<\/strong> How to Align Lot numbers with Purchase receipts numbers<\/a><\/p>\n\n\n\n

\"[Warning<\/a><\/center>\n
[Warning Message]<\/center><\/font>\n\n\n\n

Recently one of our client came up with the requirement in which he wanted to restrict purchase invoice creation if the combination of Supplier Document No, Suppler Invoice Date and Amount i.e. (Invoice-tax) is repeated for the same Supplier. For this purpose, we did a customization in such a way that it will not allow you to create new Purchase Invoice entry if combination of the mentioned three fields is already used for some other invoice for the same supplier.<\/p>\n\n\n\n

For Example \u2013 In the below screenshot you can see in Invoice No – 1012011INVBS0047, for Supplier \u2013 V00010, Supplier Document No is SD001, Date is 11\/26\/20 and Amount is 1100.<\/p>\n\n\n\n

\"[Purchase<\/a><\/center>\n
[Purchase Invoice Entry: 1012011INVBS0047]<\/center><\/font>\n\n\n\n

Now, when you try to create new invoice for the same supplier \u201cV00010\u201d with the same Supplier Document No \u2013 \u201cSD001\u201d, Date \u2013 \u201c11\/26\/20\u201d and Amount 1100 then it will give you an error that \u201cSupplier Document Number, Supplier Inv Date and Amount already exist for Invoice No: 1012011INVBS0047\u201d as shown in the below screenshot.<\/p>\n\n\n\n

\"[Error<\/a><\/center>\n
[Error on Purchase Invoice Screen]<\/center><\/font>\n\n\n\n

It will not allow you to create invoice with the same combination. At least one of those three fields should be different. This customization will work only for the same supplier. If supplier is different and this combination is repeated then Invoice will be created without any error.<\/p>\n\n\n\n

Hence with the help of this customization, Purchase Invoice creation will be restricted if the combination of Supplier Document No, Supplier Invoice Date and Amount (Invoice-tax) is repeated for the same Supplier.<\/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":"

As per the standard functionality of Sage X3, if the user is entering same Supplier Document No in new Purchase Invoice entry which is already entered or used in the existing invoice entry then user gets a warning message popup that \u201cReference entered on Invoice(Invoice No)\u201d as shown in the below screenshot. But after clicking\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,504,1564,3099,3173],"class_list":["post-21377","post","type-post","status-publish","format-standard","hentry","category-integration","category-sage-erp-x3","tag-amount","tag-date","tag-purchase-invoice","tag-restriction","tag-supplier-document-no"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/21377","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=21377"}],"version-history":[{"count":7,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/21377\/revisions"}],"predecessor-version":[{"id":21417,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/21377\/revisions\/21417"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=21377"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=21377"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=21377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}