Sage 100

Sage 100 Advanced, version 4.5. Trying to update a client's AR History to fix a bunch of bad salesperson data. I keep getting an Error 65 in AR_CREDITCARDCOMMONENTRY.PVC at Line 190 when I import the data through VI. I've never run into this before (probably because I don't do a much historical data updating). Client uses Sage Payment Solutions for processing credit cards. I've done this in a non-SPS company, and I get the same error. I've also tried doing a zero dollar credit memo to see if I can update the salesperson that way, but it doesn't change the salesperson. There are 10k records, so DFDM is out of the question. Any bright ideas? Thanks in advance!

I found this, not exactly the same but the same file - I wonder if it's something to do with PC Charge, they used to use PC Charge, right? Subject: Error 45 AR_CreditCardCommonEntry.PVC 1182 occurs after clicking on Authorize Now button in Sales Order Entry. Possible Resolution: Select Modules / Library Master / Main / Company Maintenance Click on the Servers tab. In the Path field, enter the path to the PCCharge Payment server Active Charge directory. Click on Accept to save the change.

Try temporarily disabling credit card processing.

I tried disabling - no joy.

If I take out the ""CorporateTaxOverride"" the job runs, but about 1/3 of the records fail. What is the CorporateTaxOverride? Can I disable validation somehow?

@BethBowers, you are correct. There is also a UDF, but those are the only fields.

What fields are you importing? If you're just changing the salesperson, then are you only using the Invoice, Header Seq, and Salesman fields?

Thinking out loud (virtually).... An error 65 occurs when the program cannot reference a non-existent window or GUI object. The VI job may be file verifying the payment type info in history. Is the payment type info valid? You may try copying the data to a generic non SPS system and trying the import.

Does it do it on the test run or only on the Accept run?

@DougHiggs: Good thoughts. I may try that. @BethBowers: It happens any time. I can test or accept. Either way, I get the error.

Otherwise you may get one of the PVX gurus to write a PVX script to go through and update the salesperson.

Aaron, check to see if the error message references a particular field. It may be that the field no longer exists in the data dictionary since the changes made to the credit card processing in Sage 100

@AnneParsons, there weren't any particular fields referenced, but I like your train of thought. We'll keep trying.

You know they started to buckle down on importing historical data. Since then I find that it is best to add the Y/N value fields in the import as Assign (N). And since the error is on the CC Pymt Balance amount - I would include this field as well - hopefully that too can be assigned a zero value. Hope that works.

Got back to the client yesterday, and tried everything suggested here. No dice. Called Sage support, and they had me flip the CorporateTaxOverride and DepositCorporateTaxOverride to ""Y"" and it worked just fine. Apparently the support rep looked in the Sage private KB, and found the answer. #Solved #Solution <rant>Why can't they just share everything and put a disclaimer about ""untested, use at your own risk?""</rant>

When working at Sage it was the process that once a KB was written, one additional call tag would release it for publication. In other words, if another case call came in after the KB was written and that case linked to the article, then the article was made available on the website. I don't know whether that process is still in place or not but I know that there were a handful of new analysts starting when I left so it wouldn't hurt to wrap up the call by asking for the article number being linked to the case. They can see it once the article is linked or from the KB address bar. We can help drive this practice. I share this so that we can do our part as well to help ensure timely publication of those KB articles, reduce frustation in the field and bottom line-provide the quality service our customer's pay for and expect.