This error kept coming up at a client whom was using the Sales Document Consolidation product from Binary Stream.
As it turned out, the problem was because the DUEDATE field in the SOP10100 table was showing a value of 1900-01-01 00:00:00.000, that is not a valid date in the Dynamics GP SOP posting world. This situation came about because (as near as we could tell), the customer did not have a default payment term assigned to them.
If you get this error on your SOP Edit List, go take a look at that field.
Kind regards,
Leslie
Gotcha’s on using the withholding feature in Dynamics GP
Lately, I’ve been fielding several questions from clients regarding the ability to track Backup Withholding using Dynamics GP. The short answer is that you can do it, you’ve just got to be careful.
Here are a few tips:
Bear in mind, this withholding feature was not designed for the United States. If you are using it for US Backup Withholding, be sure to test it after each service pack release.
Live the Dream!
Leslie
Please vote for this suggestion if you agree.
Vote here: https://connect.microsoft.com/dynamicssuggestions/Feedback
Read about it here: https://connect.microsoft.com/dynamicssuggestions/feedback/details/921385/do-not-automatically-unapply-other-documents-if-one-is-voided
This refers to the new feature in GP2013 that will automatically unapply all documents (except payments) from a vendor invoice if even one of those documents is voided. For instance, if you pay an invoice using checks, credit memos, returns and write offs – ALL of those documents (other than checks) become unapplied when one of the checks is voided.
I just posted the suggestion on Connect, here’s why the new feature is a bad idea:
This new feature is a DISASTER and should be an option, NOT an automatic unapply of all non-payment documents. Here's what happens.
| You have a payable to a vendor | $1,000 |
| You pay by check ($400) | ($400) |
| You pay by check ($415) | ($415) |
| You apply a credit memo of ($10) | ($10) |
| You apply a credit memo of ($75) | ($75) |
| You apply a return ($50) | ($50) |
| You write off ($50) | ($50) |
| Remaining Balance | $0 |
At this point the invoice is fully applied and in history, as are the other apply documents.
Now, you void the $400 payment. Magically the following documents become unapplied:
Now the balance of the invoice shows to be $585 instead of the ‘real’ balance of $400
WHAT! This is insanity!
So now you have to go back and figure out what those four documents should be applied to and apply them. This is causing a real problem and it should not behave this way. At least present a dialog asking the user if they want to unapply the other documents, don't just do it. And why the inconsistency with the payments, why aren't they unapplied too, the returns are.
This new 'automatic' feature is a nightmare and should instead be an option, not a mandate.
Kind regards,
Leslie
Please vote for this suggestion if you agree.
Vote here: https://connect.microsoft.com/dynamicssuggestions/Feedback
Read about it here: https://connect.microsoft.com/dynamicssuggestions/feedback/details/921350/allow-changes-to-the-amount-paid-field-on-the-edit-payables-check-batch-window
I just posted the suggestion on Connect as appears below:
Currently, if you check a voucher on the right side of the Edit Payables Check Batch window, the Amount Paid defaults to 100% of the Open amount. What if I don't want that? What if I want to pay less than the total amount.
Well, then we have to open that particular payment in the Edit Checks window and change the amount. OR, we have to enter the check anew in the Edit Checks window. Either way, it adds a lot of steps to the payables function.
I think we ought to be able to just change the amount on the Edit Payables Check Batch window and go on with processing the check run.
Live the Dream!
Leslie
Please vote for this suggestion if you agree.
Vote here: https://connect.microsoft.com/dynamicssuggestions/Feedback
Read about it here: https://connect.microsoft.com/dynamicssuggestions/feedback/details/921350/allow-changes-to-the-amount-paid-field-on-the-edit-payables-check-batch-window
I just posted the suggestion on Connect as appears below:
The Edit Payables Check Batch window is a widely accepted, much sought after window and I was thrilled to see its addition to the program. However, I find it difficult to use if you have a long list of vouchers for a vendor and you need to uncheck most of them.
As soon as you select a vendor on the left-hand side, all of the vouchers are marked on the right-hand side. If you want to Unmark them, you have to do it one at a time. I expected the little check box above all of the other checkboxes would provide the Mark All, Unmark All functionality but it does not. If it's supposed to, it's broken.
This would reduce the amount of time it took for the payables clerk to pay vouchers if only a few vouchers were paid. Clients do not necessarily want to pay ALL of the vouchers outstanding, so there's always a second step to 'Unselect' the ones you do not want to pay.
It's easy to miss some vouchers, and end up paying too many. Cash out the door.
It would be much better if the default were 'unchecked', since changing the default doesn't make sense at this point, I think we need an "Check/Uncheck All" button, or an option in the Payables Setup window that controls the default behavior
Kind regards,
Leslie
I find that there is a relatively unused feature of the Edit Payables Check Batch window. You have the option to change which columns appear on each side of the window. One change I nearly always make is to display the document number instead of the voucher number. Voucher number, really, what’s up with that?
Not only can you turn on or off the columns, you can also rearrange them.
In the screenshot below, notice I changed the left-hand section to include the Payment Priority. On the right-hand side, I changed Voucher Number to Document Number and added a field for the Original Amount.
To make these changes, you just need to push the ‘Column’ button in the header of the side you want to change. The button is circled in red above.
Upon pushing the button on the left, you get the following window with some additional choices that you can turn on or off. You are limited; you can only choose to display three columns. It will bark at you if you select too many.
Pushing the button on the right, will reward you with the following window with some additional choices that you can turn on or off. You are limited to seven columns for the right side. This side will bark at you too if you select too many.
Choices for the left and right are listed in the table below:
| Left Side | Right Side |
| Vendor ID | Voucher Number |
| Vendor Name | Document Number |
| Total Amount Paid | Due Date |
| Class ID | Amount Remaining |
| Payment Priority | Amount Paid |
| Original Amount | |
| Discount Date | |
| Terms Available | |
| Terms Taken | |
| Type | |
| Transaction Description | |
| Currency ID |
Utilizing this feature can make this popular window even more inviting.
Now, if we only had a way to ‘Unmark All’. The suggestion is on Connect. Vote for 921336 if you agree.
Kind regards,
Leslie
Hi all,
I’ve been asked about where you could send a contribution in celebration of Richard’s life, and I now have that information. His family has established a memorial fund where you can send contributions that will be forwarded to the American Heart Association (AHA) in your name.
Richard was taken from us by congestive heart failure. The AHA is working to find a cure so that we do not lose any more colleagues that suffer the same problem as did our friend Richard. Here is the information you need to make contributions:
Richard’s memorial fund
Bank of America
555 S. Hunt Club Blvd
Apopka, FL 32703
Routing number: 063100277
Account number: 898065822095
Richard’s memorial services
Richard’s daughter, Betsy, gave this information to Heidi Pukas, which was conveyed to me . There will be two memorial services for Richard, the details are below:
First Baptist Church of Forest City
Saturday July 12th @ 11am
721 W Lake Brantley Road
Altamonte Springs, FL 32714
(407) 869-1278
Bethany United Methodist Church
Friday July 18th @ 10am
118 W. 3rd Street South
Summerville, SC 29483
(843) 873-1230
I hope some of you can be there.
Kind regards,
Leslie
Farewell to the Professor. It saddens me to tell you that we lost Richard Whaley this morning 07/01/2014. He was home with his family by his side. As you may know, Richard’s health had been very bad these last couple of years, he slipped away in his sleep.
Richard was a very close friend of mine and he will be sorely missed. I was very lucky to spend a few days with him the week before last, and I will treasure that trip for a lifetime.
Richard was one of the GPUG Superstars, on the ‘top’ 100 list from forever, and a former Microsoft GP MVP. We remember him for his conference antics, like cruising around on a Segway and dressing up like a professor.
Richard brought us nearly two dozen books on Dynamics GP, most of which he penned himself, as well as books on AX, CRM, NAV, SL and SQL Reporting Services:
As well as being an expert on the Manufacturing module, he was versed in nearly every other module. He knew so much about Dynamics GP and was never too busy to help others. Richard answered hundreds of questions for us on the Community Forum, he gave countless hours of his time to GPUG and taught classes at most of the conferences.
He will be a hard act to follow.
Please send me any pictures you may have of Richard and I will add them to this post.
Kind regards,
Leslie
Our friend Richard Whaley is in poor health. In fact, he is in hospice care right now. Richard didn’t want anyone to know how poor his health was, because he didn’t want any of us to worry. Well, it’s time to worry – and to pray.
Beyond that, it’s time to let Richard know just how much he’s helped you, and meant to you, if he has. Whether with his books, or webinars, or forum responses, or just stopping by during one of the conferences for a chat. I don’t think he realizes just how much of a difference he’s made to this community.
So, let’s fill his mailbox at rwhaley@accoladepublications.com or Richard.Whaley@IntegratedBusinessGroup.com. Trend on twitter with #ProfessorWhaley, or however you can get the message to Richard that he has been a giant amongst us Dynamics GP folks. We forgive him for ever supporting Macola – we all make mistakes 
I’ll be flying to Orlando tomorrow from Dallas to see Richard. I hope by the time I see him his mailbox will be full!
Bless you all who care.
Leslie
P.S. I’m kind of mad at him myself, I was just starting to like him.
Not only is there a Dex.ini switch to disable the new ribbons (EnableWCRibbons=FALSE), but you can set a User Preference as to how you would like them to display.
I thank Heather Roggeveen for pointing out this new User Preference. When you launch the User Preferences window, there’s a new option. Check out the screen shot below:
You have three choices: Action Pane, Action Pane Strip, or Menu Bar. Each are described below:
Window Command Display
Select how to display commands in a window. Refer to the following table to view how commands can be displayed in a window.
Window Command Display selections
Action Pane
Action Pane Strip
Menu Bar
In addition, you can use a Dex.ini switch to turn off the Action Pane for all users at the workstation level. To turn off the Action Pane for the workstation, put the following in your Dex.ini file: EnableWCRibbons=FALSE
Enjoy!
Leslie
Boy what a day, another new dex.ini switch to add to my collection. I’m guessing R2 of GP2014 has many more that I have not discovered yet. Please let me know if you find new ones.
Here’s what this one does. If you set it to FALSE the new ribbon bars go away and the windows look like they did prior to the R2 release. If you set it to TRUE, you get the fancy new ribbon bars. Here’s an example:
EnableWCRibbons=TRUE
EnableWCRibbons=FALSE
If you don’t like the ribbon bars, you can hide them. I’m guessing you should learn to love them because I bet at some point this switch won’t work anymore.
Enjoy!
Leslie
Here’s one more for the collection.
I ran into an issue today after I loaded the patch to update my GP 2013 to build 1745. After the patch was loaded, I no longer had access to Modifier. I’m a pretty heavy Modifier user, so this was a big problem for me. I searched around the Internet a bit and didn’t find anything. I looked on the forum, even posted a question, but didn’t get an answer.
Next, I looked at the Dex.ini file for the new build and compared it to the old build. A Ha! There was a new Dex.ini switch that appeared in my build 1745 install. The switch read: VBADisable=TRUE. That sounded to me like it might be the problem. I changed the TRUE to FALSE and tried again.
Sure enough, the Modifier tool was once again available. This is probably documented somewhere, but I couldn’t find it. If you should run into this, here’s your answer.
Enjoy!
Leslie
I developed my own cheat sheet / checklist for setting up the Multicurrency module. I wanted something that I could fit on a single page just to remind me of what I needed to do next.
Recently, I’ve had a few colleagues ask me whether I had some kind of easy to follow checklist and I’ve been sending them this one. It seems more and more companies are implementing multicurrency these days, so I thought I’d share it with the community. It’s not fancy, nor does it provide any explanations – but it does provide the navigation to the various widows.
I welcome your comments on ways to improve it or if you think things should be re-ordered.
| 1. Create Currency (use the ISO code for the ID, don’t use the ‘Z’ entries) |
| 2. Create Exchange Table |
| 3. Establish Rates |
| 4. Grant Company access to currency and rate table (all must exit Dynamics) |
| 5. Set Rate Types |
| 6. Set Posting Account Defaults. The system will search for an account in the order listed below. As soon as it finds one, it stops looking. If all should share the same account, enter it at the Company level. Rate Type Accounts Currency ID Company-level Posting Accounts |
| 7. Assign Currency Access to your GL Accounts. Identify which accounts should accept transactions in a foreign currency. |
| 8. Assign Currency ID and Rate Type ID to Checkbook ID |
| 9. Assign default Currency ID and Rate Type ID to appropriate Customers (or roll down from Customer Classes) and set revaluation options |
| 10. Assign default Currency ID and Rate Type ID to appropriate Vendors (or roll down from Vendor Classes) and set revaluation options |
Enjoy!
Leslie
Physical Name
| Display Name |
Date Fields
|
PM20000
| PM Transaction OPEN File |
10
|
PM30200
| PM Paid Transaction History File |
11
|
PM30300
| PM Apply To History File |
6
|
PM20000PM Transaction Open File - 10 dates |
VCHRNMBR
| Voucher Number |
VENDORID
| Vendor ID |
DOCTYPE
| Document type of transaction. (Invoice, Return, Payment, etc.) |
DOCDATE
| Document date on the invoice or payment. This date is used by the subsidiary module (Payables Management) to 'age' the document and to calculate it's due date. |
DISCDATE
| Date by which the invoice must be paid to earn the terms discount |
DUEDATE
| Date the invoice is due. After this date it is delinquent |
POSTEDDT
| System date when user pushed the [Post] button when the doc was originally posted. |
MODIFDT
| User date when transaction was last modified |
DINVPDOF
| The apply date from the final document applied to the invoice. This is the date the invoice or pmt became fully applied. Voided is fully applied, written-off can be fully applied. A document in the Open table should not have a value in this field, because no documents in the open table should be ‘paid off’. |
PSTGDATE
| Posting date for the invoice or payment; set by the user on batch window or doc date expansion window. This is the date of the transaction on the General Ledger - the date attached to the Journal Entry created by the transaction. |
Tax_Date
| Date that should be used to calculate and/or report sales tax, defaults to Document date; set by user on window |
PRCHDATE
| Physical date of transfer of goods/services |
DEX_ROW_TS
| Dex Row Timestamp – system date & time when last modified |
PM30200PM Paid Transaction History File - 11 dates |
VCHRNMBR
| Voucher Number |
VENDORID
| Vendor ID |
DOCTYPE
| Document type of transaction. (Invoice, Return, Payment, etc.) |
DOCDATE
| Document date on the invoice or payment. This date is used by the subsidiary module (Payables Management) to 'age' the document and to calculate it's due date. |
DISCDATE
| Date by which the invoice must be paid to earn the terms discount |
DUEDATE
| Date the invoice is due. After this date it is delinquent |
POSTEDDT
| System date when user pushed the [Post] button when the doc was originally posted. |
MODIFDT
| user date when trx last modified an ‘apply’ is a modification, a void is not. |
DINVPDOF
| Apply date of the document that caused the invoice or pmt to be fully applied. Voided is fully applied, written-off can be fully applied. The DATE1 field for the final apply record in the PM30300 table becomes the DINVPDOF. |
PSTGDATE
| Posting date for the invoice or payment; set by the user on batch window or doc date expansion window. This is the date of the transaction on the General Ledger - the date attached to the Journal Entry created by the transaction. |
VOIDPDATE
| The Posting Date (GL date) for the Void -The sub ledger void date becomes the DINVPDOF |
Tax_Date
| Date that should be used to calculate and/or report sales tax, defaults to Document date; set by user on window |
PRCHDATE
| Physical date of transfer of goods/services |
DEX_ROW_TS
| Dex Row Timestamp – system date & time when last modified, includes voids. |
PM30300PM Apply to History File - 6 dates |
VENDORID
| Vendor ID |
VCHRNMBR
| Voucher number of the payment document. The ‘apply from’ voucher number. |
APFRDCNM
| Document number of the payment ( check number). The ‘apply from’ Document number |
DOCTYPE
| Document type of the payment. The ‘apply from’ document type. |
APTVCHNM
| Voucher number of the invoice being paid. The ‘apply to’ voucher number. |
APTODCNM
| Document number of the invoice being paid. The ‘apply to’ invoice number |
APTODCTY
| The type of document the pmt is being applied to; invoice, debit memo, etc. The ‘apply to’ document type. |
DOCDATE
| Document date of the payment being applied; check date. The ‘apply from’ document date. |
DATE1
| The date the sub ledger uses for the ‘apply date’. This is set by the user on the apply window and used by the system in the HITB and to determine when the 1099 amount is reportable. |
GLPOSTDT
| Posting date to the general ledger, if an entry is necessary, like in a write-off. Set by user on the apply window |
APTODCDT
| Document date of the invoice being paid. The ‘apply to’ document date |
ApplyToGLPostDate
| Original GL posting date of the invoice being paid. The ‘apply to’ GL posting date. |
ApplyFromGLPostDate
| Original GL posting date of the payment document. The ‘apply from’ GL posting date. |
