Sage 100

4.30, importing A/P Invoices. Would like a way to prevent the importing of Invoices that already exist in MAS 90 history for that Vendor. Appears that some Perform Logic can be used but I wasn't able to locate it in the Community Forums. Anyone?

Just a thought, but what about if you hard-coded a N to the Adjustment field? I'm assuming that already existing invoices are coming in as adjustments?

I believe Assigning the Adjustment field as N (which is typically the case) just tells the system that the imported invoice is not an Adjustment - and therefore imports it as a regular 'ol invoice. I want to prevent the invoice from being imported if it already exists in history for that Vendor.

Instead of Perform Logic, haven't tried it but presumably you could have a User Defined Script for AP_Invoice_Bus on the PreValidate() of InvoiceNo that would check AP_InvoiceHistoryHeader_svc to see if that APDivisionNo, VendorNo, InvoiceNo combination already exists. If it does then disallow the entered InvoiceNo from being used. In Invoice Data Entry this PreValidate would end up running before the normal MAS logic of popping the Adjust Invoice on File dialog. **In theory** since V/I is using the same AP_Invoice_Bus object it should also run the script (and suppress any UI from the script) and ergo prevent existing invoices from being imported for that Div / Vendor.

It's not a theory - I use events scripts for V/I because I don't know pvx script as well as I know VBSCript. But they are only available in 4.40 and Brett says he needs it for 4.3

Good to get personal validation on that Dan thx 4 sharing that! About Brett needing it for 4.30 the Homer line of doh! is in order. Brett do u still need Perform Logic sample maybe I can whip 1 up assuming I can use it to fail a record. The Perform events in a BF import are a PITA to deal with cuz you're never sure how far VI has really gotten thru the import when it hits your perform program.

This PERFORM should work but test it please: In the Configuration tab, click on Perform In Perform Maintenance add this: Perform Type = Before Assign File Type = Header Table Name = AP_InvoiceHeader Column Name = InvoiceNo Sequence = 001 (assuming you don't have others) Command = ..\AP\AP_VISkipExistingInvoices.m4p;ENTRY_POINT Click Accept Then before running import, place attached .M4P file into \mas90\AP folder (it's a text file you can view). The V/I log on both Test and Accept will show a Fail for existing invoices.

Wow, awesome @AlnoorCassim. I'll post back the results once I have a chance to try it.

I love how some of the providex files try to open in my iTunes.

ROTFLMAO! I have a good one about M4P too. Last year I couldn't get 4.30 SU 18 to install on client's 2003 server. Traced it down to M4P files the SU was installing. Tried manually copying them in via Windows Explorer but ""Error 5 access denied"". I could copy them into C: drive but not D: where MAS was installed. On D: I could rename a file from M4P to BAK but couldn't rename BAK back to M4P. Rebooted server in Safe Mode that did work. Finally found their IT had installed this Microsoft utility called File Server Resource Manager. It had a setting enabled to prevent storing any new audio or video files and on D: only. It included <drumroll> ""M4P Apple Quick Time"". What a riot! Since then I've been waiting for that tech support call from the angry office mgr stating MAS broke every since implementing the company-wide policy to uninstall iTunes from all PCs and delete all audio/video files on the servers in the effort to make the workers productive.

Thats a good one to keep in our bags of tricks.

Just added M4P to the exclusion list in MS Security Essentials today and sho nuff... flagged it as an audio file.

@JimWoodhead I think this is the post you are looking for.

Crazy that this post was almost exactly a year ago. Thank you!!!

@AlnoorCassim , Can I cut and paste your post to the Oasis side?

Yes

FYI, I never got the opportunity to try @alnoorcassim suggestion. @jimwoodhead, please let us know how you make out.

The perform logic works great. But you need a different perform logic for v4.3 vs v4.4+ . The syntax is a bit different . Here is the V4.40 version. It is surprising that this logic isn't more common. Thanks @AlnoorCassim #performlogic #vi #apinvoice