{"id":22688,"date":"2021-06-30T05:35:00","date_gmt":"2021-06-30T05:35:00","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=22688"},"modified":"2021-06-30T05:42:23","modified_gmt":"2021-06-30T05:42:23","slug":"validation-on-purchase-invoice-screen","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2021\/06\/30\/validation-on-purchase-invoice-screen\/","title":{"rendered":"Validation on Purchase Invoice screen"},"content":{"rendered":"\n

As we know in Purchase Invoice screen, Supplier Document No and Supplier Invoice Date fields are mandatory. In Sage X3<\/a>, while creating Purchase Invoice transaction, user can enter same No and Date for different invoice numbers. But one of our client requested to add a validation for the Purchase Invoice where, if the Supplier, Supplier Invoice date and Gross amount (Invoice-tax) are same but supplier doc number is different then an alert notification should be displayed on the screen.<\/p>\n\n\n\n

For Example: – A purchase Invoice is created against the vendor: V03941 with supplier invoice no(Doc number): CHNCNT208-2021 and invoice Date: 09\/08\/20, and having gross amount: 168000<\/p>\n\n\n\n

Consider below screenshot for reference:<\/p>\n\n\n\n

New Stuff:<\/strong> How to enable \u201cAccounting Cancellation\u201d option on Purchase Invoice Screen<\/a><\/p>\n\n\n\n

\"[PI<\/a><\/center>\n
[PI 1 – Supplier Doc No and Date]<\/center><\/font>\n\n\n\n
\"[PI<\/a><\/center>\n
[PI 1 – (Invoice-tax)]<\/center><\/font>\n\n\n\n

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

If the user is trying to create new purchase invoice with the same supplier invoice date: 09\/08\/20, gross amount: 168000 but different invoice number: CHICNT390-2021 then the system should show a pop-up\/warning regarding the same.<\/p>\n\n\n\n

Consider below screenshot for reference:<\/p>\n\n\n\n

\"[PI<\/a><\/center>\n
[PI 2 – Supplier Doc No and Date]<\/center><\/font>\n\n\n\n
\"[PI<\/a><\/center>\n
[PI 2 – (Invoice-tax)]<\/center><\/font>\n\n\n\n

For this purpose, we did a customization on Purchase Invoice screen. Refer below code:<\/p>\n\n\n\n

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

If !clalev([ZPIH]) : Local File PINVOICE[ZPIH] : Endif
FOR [F:ZPIH] WHERE [F:ZPIH]NUM<>[M:PIH0]NUM and [F:ZPIH]BPRVCR<>”” and [F:ZPIH]BPRVCR=[M:PIH1]BPRVCR and [F:ZPIH]BPRDAT=[M:PIH1]BPRDAT AND [F:ZPIH]AMTNOT=[M:PIH4]TOTLINAMT <\/p>\n\n\n\n

if [M:PIH1]BPRVCR = [F:ZPIH]BPRVCR AND [M:PIH0]BPR = [F:ZPIH]BPR and [F:ZPIH]BPRDAT=[M:PIH1]BPRDAT AND [F:ZPIH]AMTNOT=[M:PIH4]TOTLINAMT <\/p>\n\n\n\n

INFBOX “Supplier Document Number, Supplier Inv Date and Amount already exist for Invoice No : ” + [F:ZPIH]NUM
OK = 0
GOK = 0
GPE = 1
mkstat=2
break <\/p>\n\n\n\n

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

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

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

Add the above code in VERIF_MOD and VERIF_CRE events on SPEPIH script.<\/p>\n\n\n\n

After adding the above code if user try to create new purchase invoice with the same supplier invoice date, gross amount but different supplier doc number then the system will show a pop-up\/warning regarding the same and It will restrict user to create purchase invoice.<\/p>\n\n\n\n

\"Warning<\/a><\/center>\n
Warning message]<\/center><\/font>\n\n\n\n

Hence with the help of this customization, we can restrict a Purchase Invoice creation on the basis of Supplier Document No, Supplier Invoice Date and Gross Amount.<\/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 we know in Purchase Invoice screen, Supplier Document No and Supplier Invoice Date fields are mandatory. In Sage X3, while creating Purchase Invoice transaction, user can enter same No and Date for different invoice numbers. But one of our client requested to add a validation for the Purchase Invoice where, if the Supplier, Supplier Invoice\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":[1564,3327,3328,2357,2394],"class_list":["post-22688","post","type-post","status-publish","format-standard","hentry","category-integration","category-sage-erp-x3","tag-purchase-invoice","tag-supplier-doc-no","tag-supplier-inv-date","tag-validation","tag-warning"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/22688","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=22688"}],"version-history":[{"count":16,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/22688\/revisions"}],"predecessor-version":[{"id":22712,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/22688\/revisions\/22712"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=22688"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=22688"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=22688"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}