tag:blogger.com,1999:blog-2902800390575811159.comments2023-12-25T03:01:26.251-06:00Dynamics Confessions BlogspotDynamics Confessorhttp://www.blogger.com/profile/06555435567985477366noreply@blogger.comBlogger441125tag:blogger.com,1999:blog-2902800390575811159.post-6364465323963303542018-07-19T10:30:01.782-05:002018-07-19T10:30:01.782-05:00Loving this thread, thanks! MR does a fine job if ...Loving this thread, thanks! MR does a fine job if you haven't spent days/weeks writing complex financials in FRx. Happy to say I have supported many staying on it with MR as the backup for when we cannot find these work arounds. Appreciate the effort.Whitey63https://www.blogger.com/profile/15113260511509249772noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-46118437615593258062018-05-17T19:59:22.502-05:002018-05-17T19:59:22.502-05:00I'm running
Windows 10 Pro
Version 1803
OS Bui...I'm running<br />Windows 10 Pro<br />Version 1803<br />OS Build 17134.48<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-8388923888487945732018-05-17T19:38:15.242-05:002018-05-17T19:38:15.242-05:00Michael,
I think I have the answer for you. You ne...Michael,<br />I think I have the answer for you. You need to go to Programs and Features and turn on .net 2.0, which will also turn on .net 3.0. After that, download the files from Microsoft Update. The system will need to restart. When you install FRx, install the Prerequisite named Microsoft Data Access Components. Restart the machine and you should be able to get through the FRx installation without the error. Be sure to change the GPConn.dll to the 143Kb version and you should be good to go.<br />Live the Dream!<br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-16817436624825973322018-05-17T14:55:15.110-05:002018-05-17T14:55:15.110-05:00Hi,
What module did you void things in?
LeslieHi,<br />What module did you void things in?<br />LeslieDynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-86082249803690996042018-05-17T13:58:03.186-05:002018-05-17T13:58:03.186-05:00Thank you for your kind words,
I'm so happy th...Thank you for your kind words,<br />I'm so happy this was of value for you. If you have any other Macro questions, please send them my way!<br />Live the Dream!<br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-66735024677155117982018-05-04T09:17:46.075-05:002018-05-04T09:17:46.075-05:00Again, Leslie saves the day!Again, Leslie saves the day!Heatherhttps://www.blogger.com/profile/03523209527107500614noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-52294841633596800112018-05-04T01:41:18.848-05:002018-05-04T01:41:18.848-05:00Michael,
I'll keep my ears open. Just for the ...Michael,<br />I'll keep my ears open. Just for the heck of it I reinstalled it on this machine (after having uninstalled it) and it ran once you got the right connector file and changed the ODBC to a lower level of SQL client (really no SQL client 'number')<br /><br />The end is coming, but on my end anyway, I've still got 2018 running with FRX. That's tough error message, I remember having received it in my travels, but do not recall how we got by it.<br /><br />If you find the solution, please add a comment to help us other poor souls too.<br /><br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-33201525283026856062018-05-03T16:48:03.835-05:002018-05-03T16:48:03.835-05:00Hi Leslie,
Wasn't able to find another...Hi Leslie,<br /> Wasn't able to find another Windows 10 station that was Build 371 or earlier. We did roll back two different windows 10 stations back to Build 371 but continue to have the same install error, no matter which installation version we use or compatibility/run as administrator combination we use.<br /><br />Can you think of any other prerequisites you might have installed on your Windows 10 machine (e.g. Older Version of .NET) that might be allowing you to install FRX. Could be wrong, but thinking maybe the 402 update (End of April Update) injected something onto our systems that breaks the FRX Installation, even though we've rolled the update back.<br /><br />Anything you can think of would be greatly appreciated.<br /><br />Thank you again!<br /><br />Michael.<br /><br /> Michaelnoreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-42142497987341853952018-05-03T10:00:04.641-05:002018-05-03T10:00:04.641-05:00Believe I have both the pre-SP9 version with a FRx...Believe I have both the pre-SP9 version with a FRxSetup.exe date of 09/04/2002 and what I believe to be the SP9 version (FRx674GP10FullInstall) with a FRxSetup.exe date of 05/01/2007.<br /><br />Have attempted to install using various Compatibility settings (e.g. XP SP2, XP SP3, etc.) but no luck.<br /><br />I see that my Windows Build is 16299.402 which is slightly higher than yours. Will look to see if I can track down another station with a build closer to .371 for starters.<br /><br />Was able to get the SQL Server Native Client 10 & 11 in preparation to run a connection and am well aware of the GPCONN.DLL, so good there.<br /><br />Guessing, aside from possibly running the install using a Compatibility setting and possibly temporarily disabling any Antivirus software at the time, you didn't need to do anything special.<br /><br />Will let you know what comes of things and will also check back here in case you have any other additional insight.<br /><br />Thank you very much for your assistance here and on all your other various posts that have been extremely helpful and informative!<br /><br />Michael.Michaelnoreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-3664752241089796132018-05-02T20:36:21.577-05:002018-05-02T20:36:21.577-05:00Hi Michael,
I started the install with FRx 6.7 wit...Hi Michael,<br />I started the install with FRx 6.7 with SP 9.<br />I did a clean install on Windows 10 Pro Version 1709, Build 16299.371<br />I've installed it on two machines with the above configuration. Which one were you using?<br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-28625970332325246782018-05-02T15:31:20.744-05:002018-05-02T15:31:20.744-05:00Hi Leslie,
See you note that you are able ...Hi Leslie,<br /> See you note that you are able to get FRX installed onto a Windows 10 machine. Where you able to do a clean install of FRX on a Windows 10 machine running the latest Version 1709, Build 16299.402? I'm not able to get past the initial install (keep getting "The current version of the application could not be determined. The setup will now terminate.").<br /><br />Found other posts that say this became an issue with the Fall Creator Update. Also found you mentioned on another blog (https://www.gpug.com/communities/community-home/digestviewer/viewthread?GroupId=247&MessageKey=2814d329-64f5-4b78-ac91-3ecf734a8a82&CommunityKey=4754a624-39c5-4458-8105-02b65a7e929e&tab=digestviewer) that you were successful install FRX.<br /><br />Do you happen to know what version of FRX you are starting with?<br /><br />Any help would be greatly appreciated.<br /><br />Sincerely,<br /><br />Michael J. Nola<br />Michael J. Nolanoreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-30454870753163799512018-04-18T21:38:23.304-05:002018-04-18T21:38:23.304-05:00Hello Leslie,
I'm new to great plains dynami...Hello Leslie, <br /><br />I'm new to great plains dynamics and I posted voids with April dates that were invoiced in February. What is the simplest solution to fix these incorrect voids? <br /><br />Thank you for your time!Anonymoushttps://www.blogger.com/profile/12516280092282384597noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-14810172835336951432018-03-29T19:12:43.936-05:002018-03-29T19:12:43.936-05:00Mark,
Congrats to you for being able to change the...Mark,<br />Congrats to you for being able to change the workflow. It's just so easy to void the invoice in RM, I think it was a good fix if you've got non-inventory items but still want to get your reports from SOP.<br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-8756536105852191382018-03-29T08:36:23.884-05:002018-03-29T08:36:23.884-05:00Ideally, the client should not void an invoice or ...Ideally, the client should not void an invoice or return that came from SOP. Better to use a debit memo or credit memo in RM, or offset with another SOP transaction that would adjust the impact on inventory. I agree that in an inventory system, it can create confusion to update the VOIDSTTS to 1. <br /><br />But if we are using this script on a regular basis, the thought is we do not need to worry about RM30101 as the issue would be captured before the document moves to history.<br /><br />In my case, the client uses non-inventory items, and they were "fixing" the issue by bad business practices, of voiding the transaction in RM and re-issuing the invoice. This had the affect of doubling the sales reports, so we used the scripts above to handle the already poor situation, and keep the sales reports accurate. Eventually, we were able to correct the user's poor workflow.<br />MarkW101https://www.blogger.com/profile/15269794593320755445noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-28043643906368611882018-03-29T00:37:39.622-05:002018-03-29T00:37:39.622-05:00If you wanted to change the SOP30200 Void status u...If you wanted to change the SOP30200 Void status using sql, I'd most likely do it in a single statement to deal with the work and history RM tables. I game up with this:<br /><br />UPDATE SOP30200<br />SET VOIDSTTS = 1<br />FROM SOP30200<br />INNER JOIN ReceivablesTransactions ON SOP30200.SOPNUMBE = ReceivablesTransactions.[Document Number]<br /> AND SOP30200.CUSTNMBR = ReceivablesTransactions.[Customer Number]<br />WHERE (ReceivablesTransactions.[Void Status] = 'Voided')<br /> AND ReceivablesTransactions.[Document Type] IN ('Sales / Invoices', 'Returns')<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-19850116451897626352018-03-28T19:20:29.702-05:002018-03-28T19:20:29.702-05:00Hi,
Thank you for your comment and for sharing the...Hi,<br />Thank you for your comment and for sharing these scripts. If you wanted to run an update like this, you would also want to include the RM transaction history table -RM30101.<br /><br />The fact that SOP is not updated when an invoice or return is voided in RM is not a bug. It's working as designed. The void status in SOP is used when you actually void the transaction in SOP. I wouldn't suggest voiding a SOP transaction in RM because your inventory balances will not be properly updated. If you are not using 'Sales Inventory' or 'Discontinued' items, it shouldn't be a problem, but be careful of where your sales reports are coming from.<br /><br />LeslieDynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-56108274948623799922018-03-28T11:03:55.245-05:002018-03-28T11:03:55.245-05:00FYI - If you void an invoice or return in RM that ...FYI - If you void an invoice or return in RM that started out in SOP, the void status (VOIDSTTS) in SOP30200 does not get updated. I wrote a SQL job to synch with RM. <br /><br />update SOP<br /> set VOIDSTTS = 1<br />from ( select * <br /> from RM20101<br /> where RMDTYPAL = 1<br /> and VOIDSTTS = 1) RM<br />join ( select * <br /> from SOP30200<br /> where SOPTYPE = 3<br /> and VOIDSTTS = 0) SOP<br /> on RM.DOCNUMBR = SOPNUMBE<br /><br />update SOP<br /> set VOIDSTTS = 1<br />from ( select * <br /> from RM20101<br /> where RMDTYPAL = 8<br /> and VOIDSTTS = 1) RM<br />join ( select * <br /> from SOP30200<br /> where SOPTYPE = 4<br /> and VOIDSTTS = 0) SOP<br /> on RM.DOCNUMBR = SOPNUMBE<br />MarkW101https://www.blogger.com/profile/15269794593320755445noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-31656341494805955252018-03-27T18:08:07.769-05:002018-03-27T18:08:07.769-05:00No, I do not think it skips Discontinued inventory...No, I do not think it skips Discontinued inventory.Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-16435916202892982092018-03-26T19:13:34.144-05:002018-03-26T19:13:34.144-05:00Hi Sue,
First, I want to admit to you know that I ...Hi Sue,<br />First, I want to admit to you know that I have never worked with Tableau. In fact, I had to look it up to figure out what it was :)<br /><br />1. Correct, do not change any amounts anywhere in GP via SQL. Certainly not the SOP tables. SQL will let you do it, but you will not like what happens to the software and the accounting department will be really mad.<br /><br />2. Correct, the SOP History tables hold posted sales & returns and the other items you noted in the previous comments. Be sure to exclude 'voided' transactions and consider any write-offs if you have them. Don't pull things from the SOP10XXX tables because they are unposted, correct again.<br /><br />Another note, I don't know if anyone posts sales or adjustments directly in the receivables transaction entry window, but consider the RM Open and History tables if they do. SOP is not updated by anything posted through Receivables Management. Write offs, for example, are recorded in Receivables.<br /><br />Live the dream!<br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-62159106221393099392018-03-26T13:32:36.603-05:002018-03-26T13:32:36.603-05:00Hi Leslie,
Thanks so much for the quick reply. I...Hi Leslie, <br /><br />Thanks so much for the quick reply. I'm currently working on the project with Tableau. I connected SQL server directly to Tableau. My understanding is :<br /><br />1. We cannot change the Return Documents amount in SQL database to negative <br />2. If I need to know the sales performance I should pull the data from SOP HISTORY table (ie. SOP30200 & SOP30300) since these are POSTED and CORRECT actual records. I should NOT pull data from SOP WORK table (SOP10100 & SOP10200) as these are unposted transactions.<br /><br />Does that make sense? Please correct me if I am wrong. <br /><br />Thanks so much for your help. <br /><br />SueAnonymoushttps://www.blogger.com/profile/12500207496289684486noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-36280036542851291152018-03-26T13:14:31.288-05:002018-03-26T13:14:31.288-05:00Hi Sue,
You are seeing exactly the correct things ...Hi Sue,<br />You are seeing exactly the correct things in the History table. While only the Invoice and Return can be posted, they are not the only transactions in the history table. The other documents automatically move to history as you've described.<br /> 1.Orders move to history when all of their items have been fully transferred to other docs.<br /> 2.Quotes move to history when any item is transferred to another document<br /> 3.Backorders move to history when all items have been fully transferred to other docs.<br />Return documents should show a positive amount, the system differentiates between what is positive and what is negative according to the document type. This is consistent with most of the modules in GP. You'll see the same thing in RM and PM.<br />Kindly,<br />Leslie<br />Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-84331554085392467502018-03-23T14:10:47.977-05:002018-03-23T14:10:47.977-05:00Hi Leslie,
Thanks so much for your posting as I...Hi Leslie,<br />Thanks so much for your posting as I'm very new to GP this is super helpful.<br />I have a quick question. As you mentioned in SOP unposted document (Invoice, Return, Quote, Order, and Backorder) are in the WORK (SOP10100 & SOP10200) once they are posted will automatically move to HISTORY. However, only Invoice and Return can be posted. <br />Why in the HISTORY table there will be <br /><br />Orders whose items have been fully transferred to other documents<br />Quotes that have had any item transferred to another document<br />Backorders that have been fully transferred to other documents<br /><br />What is the status mean? Should I not see Order, Backorder in HISTORY since they cannot be posted?<br /><br />Another question is how come the Return in SOP30300 show as positive amount? Shall they show as negative amount?<br /><br />Really appreciated your help.<br /><br />Sue<br /><br />Anonymoushttps://www.blogger.com/profile/12500207496289684486noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-22983507512272216942018-03-23T14:10:27.729-05:002018-03-23T14:10:27.729-05:00Hi Leslie,
Thanks so much for your posting as I...Hi Leslie,<br />Thanks so much for your posting as I'm very new to GP this is super helpful.<br />I have a quick question. As you mentioned in SOP unposted document (Invoice, Return, Quote, Order, and Backorder) are in the WORK (SOP10100 & SOP10200) once they are posted will automatically move to HISTORY. However, only Invoice and Return can be posted. <br />Why in the HISTORY table there will be <br /><br />Orders whose items have been fully transferred to other documents<br />Quotes that have had any item transferred to another document<br />Backorders that have been fully transferred to other documents<br /><br />What is the status mean? Should I not see Order, Backorder in HISTORY since they cannot be posted?<br /><br />Another question is how come the Return in SOP30300 show as positive amount? Shall they show as negative amount?<br /><br />Really appreciated your help.<br /><br />Sue<br /><br />Anonymoushttps://www.blogger.com/profile/12500207496289684486noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-52639161674105875432018-03-14T17:22:50.798-05:002018-03-14T17:22:50.798-05:00Interesting,
It doesn't work for March, May or...Interesting,<br />It doesn't work for March, May or December. Their function test results do not even work for those three months. I looked at it briefly and thought it was because we used 'MON DD' and that wasn't listed, but that isn't so. If you enter it exactly as they have it, it doesn't work for those either. I'll have to research this a bit. I know it's not as cool as their function, but the following will yield the date with the full year:<br /><br />SELECT UPPER(right(convert(VARCHAR, getdate(), 106), 8)) <br /><br /><br />--Microsoft SQL Server date format function test<br />--MSSQL formatting dates<br />SELECT dbo.fnFormatDate (getdate(), 'MM/DD/YYYY') --01/03/2012<br />SELECT dbo.fnFormatDate (getdate(), 'DD/MM/YYYY') --03/01/2012<br />SELECT dbo.fnFormatDate (getdate(), 'M/DD/YYYY') --1/03/2012<br />SELECT dbo.fnFormatDate (getdate(), 'M/D/YYYY') --1/3/2012<br />SELECT dbo.fnFormatDate (getdate(), 'M/D/YY') --1/3/12<br />SELECT dbo.fnFormatDate (getdate(), 'MM/DD/YY') --01/03/12<br />SELECT dbo.fnFormatDate (getdate(), 'MON DD, YYYY') --JAN 03, 2012<br />SELECT dbo.fnFormatDate (getdate(), 'Mon DD, YYYY') --Jan 03, 2012<br />SELECT dbo.fnFormatDate (getdate(), 'Month DD, YYYY') --January 03, 2012<br />SELECT dbo.fnFormatDate (getdate(), 'YYYY/MM/DD') --2012/01/03<br />SELECT dbo.fnFormatDate (getdate(), 'YYYYMMDD') --20120103<br />SELECT dbo.fnFormatDate (getdate(), 'YYYY-MM-DD') --2012-01-03<br />SELECT dbo.fnFormatDate (getdate(), 'MON DD, YYYY') --2012-01-03<br /><br />--CURRENT_TIMESTAMP returns current system date and time in standard internal format<br />SELECT dbo.fnFormatDate (CURRENT_TIMESTAMP,'YY.MM.DD') --12.01.03<br />GO Dynamics Confessorhttps://www.blogger.com/profile/06555435567985477366noreply@blogger.comtag:blogger.com,1999:blog-2902800390575811159.post-14508884343316122672018-02-26T08:31:24.541-06:002018-02-26T08:31:24.541-06:00Why the query returns to me this ?
SELECT DISTINCT...Why the query returns to me this ?<br />SELECT DISTINCT dbo.fnFormatDate (getdate()+(304), 'MON YY')<br />->27EC 18Anonymousnoreply@blogger.com