Hi, Does anyone know if PDFCreator or PDFArchitect 5 will work with GP2015 R2?
↧
RE: GP 2015 and Adobe Acrobat Standard DC?
↧
GP 2015 and Adobe Acrobat Standard DC?
We have Adobe Acrobat Standard 9 installed. We upgraded to GP 2015 last summer and have not had any issues despite the requirements calling for Adobe Acrobat X.:
We are looking at purchasing Acrobat Standard DC, since Acrobat X is now two versions behind, but wanted to be sure it is compatible with GP 2015. Has anybody upgraded to both Acrobat DC and GP 2015 yet? If so, have you had any issues with the Send To options on reports?
↧
↧
RE: Straight Line Depreciation not calculating correctly
I am having a similar issue. I have an asset that has a place in service date of 4/30/2017 however the Depr. Begin Date is coming up as 3/31/2017. The cost of the asset is $41603.75 for 5 years. SL Depn should be a monthly rate of 693.40. The yearly rate should be $8320.75 however the system is calculating $6240.56
We imported FA and this is the first month we are trying to do it. Can you explain the calculations?
↧
RE: Straight Line Depreciation not calculating correctly
Bari -
Just a quick note. If the Begin Depreciation Date is 3/31/2017, then the math works. $693.39583333 repeating times 9 months (April to December inclusive) = 6240.5625.
↧
Straight Line Depreciation not calculating correctly
Ok so I'm currently entering in assets into the fixed asset module and I can't seem to figure out how GP is calculating the depreciation. Here is the relevant information
Cost Basis: 80,809.50
Place in service date: 12/29/14
Dep to date: 12/28/14
0 LTD and YTD
Life: 5 years 0 days
Dep method: Straight line Orig
No Averaging Convention
No Switchover
So based on all of this I am expecting the period depreciation to be $1,346.83 (80,809.50 / 5 / 12 ) since there isn't any depreciation taken on it yet. That would roughly $44.89 per day. However, it is calculating out periodic depreciation to be $1,571.30 and daily depreciation to be $50.82.
For the most part changing the averaging convention does very little but I set it to none because I want the assets to depreciate exactly based on their placed in service date. However, when I change the depreciation method to SL remaining life, it calculates periodic depreciation to be $1,368.22. This is better but still off from what I would expect.
Does anyone have an idea?
↧
↧
RE: Straight Line Depreciation not calculating correctly
Can you explain the calculations for the Current Depn? How does the system start depn on 3/31 when the in service date is 4/30/17?
The current depn is showing as $2080.18
I can't upload the picture of the screen
↧
RE: SmartList Error: Wrong number of parameters sent to script 'Explorer_Get_SQL_Join_Info'.
No responses to this? Anyone from Microsoft on here who might have a clue?
↧
SmartList Error: Wrong number of parameters sent to script 'Explorer_Get_SQL_Join_Info'.
Hi, all
I'm getting a weird error on the Inventory->Items->default SmartList (*):
Unhandled script exception:
Wrong number of parameters sent to script 'Explorer_Get_SQL_Join_Info'.
This is on GP2016. We have Extender in use, with some SmartList integration.
Other (non-default) Item SmartLists are fine - so I figure this is something to do with the default SmartList settings. I looked in Adminsitration->System->SmartList Options, but everything looks OK.
We have several GP companies, and it's the same in all of them - again, pointing to something in DYNAMICS that's not right.
This *may* relate to an upgrade we did a few months back, from GP10 (yes, GP10) to GP2016. The transition for Extender was less-than-smooth, and there may be some garbage hanging about in a table somewhere. I'm suspecting that this may be Extender-related, but I don't really have any evidence that this is the case.
Any clues as to where I should be looking?
↧
RE: Not able to select Serial number - Manufacturing Component Transaction Entry
I deleted the record on the MOP1210 table by way of SQL.
Once I deleted it, I ran a reconcile and a checklink. The issue was resolved at this point.
↧
↧
Not able to select Serial number - Manufacturing Component Transaction Entry
I am trying to ISSUE to a Manufacturing order.
If I try to Post, it says there are no items on the "Pick Document"
I select the item and I then receive the screen to select serial number.
There are no serial numbers to select. Why would this be happening?
↧
Manufacturing Order - Costing Accounts
I am using Scribe to integrate orders from Dynamics 365(CRM) to GP 2010.
99% of the orders have the costing accounts assigned appropriately but there are a few whereby it does not.
I have been examining this for some time, but cannot find the issue. Does anyone have any suggestions on what I should look for?
Thank you,
Will
↧
RE: Straight Line Depreciation not calculating correctly
Bari -
That comes up to 3 months worth of depreciation. If the depreciation includes April, this should mean you've depreciated May and June as well. Please share the following values from your Asset Book card, since you cannot put in a screen capture (or switch to Use Rich Format below your reply to enable inserting images): Depreciation Method, Averaging Convention, Switchover, Place in Service Date, Depreciated To Date, Original Lif in Years, Days and Remaining Years, Days, and Cost Basis/Begin Year Cost
↧
RE: Straight Line Depreciation not calculating correctly
Depreciation Method: Straight-Line Orig Life
Averaging Convention: Full Month
Switchover: No Switch
Place in Service Date: 4/30/17 (Depr. Begin Date 3/31/2017 Date added: 11/14/2017)
Depreciated to Date: 11/30/2017
Original Life in Year, Days: 5 years, 000 days
Remaining year, Days: 4 years, 121 days
Cost Basis: $41603.75
Begin Year Cost: 41603.75
↧
↧
Payables Transaction Appearing Only on the Historical Aged Trial Balance (HATB)
Hello:
A payables credit transaction is appearing only on the Detailed Historical Aged Trial Balance (HATB) and not anywhere else in GP or in the company database.
I have checked the "usual suspects" in the database, as follows: PM20000, PM30200, PM30300, and PM30600.
But, again, the transaction appears only on the report.
How do we fix this?
Thank you!
John
↧
UOM on Requisition not carrying through to the PO
Hi Folks
I'm on GP2016 R2 and my question is as follows.
I have a UOM of Each with an equivalent of 1 dozen being equal to 12 of each. When I place a Requisition, I order a qty of 2 x dozen. When I generate a PO off the Requisition, it converts the UOM to Each and states the quantity of 24 x Each. I don't want that on my PO. It needs to remain as a qty of 2 x dozen.
If I place a PO without going via a Requisition, it behaves as expected and keeps my quantity as 2 x dozen.
I expect the PO to have the exact same Qty, UOM and Unit Cost as it had on the originating Requisition.
Does anyone have any suggestions for me please?
Thank you
↧
Display Project PO Number on RM Statements
Hi,
I'm trying to display the Project PO Number from PA Billing Detail Open table(PA23200) on the RM Statement on Blank Paper report. I'm using the function rw_TableLineString per the below Article. The table has 2 string and 1 integer field as Primary Key, but couldn't pass all 3 to the function parameters due to limitations on the datatype, hence decided to use another Unique key to just pass the Document number. But it didnt do anything it seems. Also tried hardcoding the primary key values and see if it returns something, but none. Do you have any other suggestions? your help would be highly appreciated.
set 'PA Document No.' of table PA_Billing_DTL_OPEN to sNumber;
get first table PA_Billing_DTL_OPEN by PA_Billing_DTL_OPEN_Key10;
Thanks,
Jothikrishnan
↧
RE: Payables Transaction Appearing Only on the Historical Aged Trial Balance (HATB)
What is the value of your date fields in the PM20000, PM30200 & PM30300? There are 27 date fields in those tables, but for me the answer would reside in one of those fields.
Kind regards,
Leslie
On my blog, I have a description of 26 of those fields dynamicsconfessions.blogspot.com/search
Leslie
↧
↧
RE: Payables Transaction Appearing Only on the Historical Aged Trial Balance (HATB)
Hi Leslie:
Thank you, as always, for your response!
The transaction, actually, does not appear in any of the tables. What would be the best approach?
Thanks, again!
John
↧
RE: Payroll need to refund 401k deduction overpaid
Hi Valerie,
I understand that this is a challenging process. Generally, you would use a Business Expense pay type pay code that is "Subject to" the same taxes that the 401k is "Sheltered from". Then, you would create a manual check to move these monies to the correct code after posting the pay run.
If this is a common issue for you, you may want to look at our "Negative Deductions" product that automates this process and makes refunding overpayments much easier.
http://www.integrity-data.com/software/negative-deductions-enhancement/
Let me know if you would like to discuss this in more detail. Have a great day!
↧
Payroll need to refund 401k deduction overpaid
We are on Dynamics GP 2016 R2.
Here is an issue - there were not maximums set up on our 401K deduction codes. So, on the last pay run, we exceeded the maximum amount for one employee. We now need to refund this amount to the employee, taking out taxes and reduce their 401k amount.
What is the proper way to do this? I've seen a variety of suggestions, but most say the end result will be that the employee's W2 will show an inflated value. Is there a way to avoid this?
I understand that I will need to do the following:
- Set up a non-wage Pay Code for the Refund subject to Federal Taxes
- Do a pay run in the amount over paid to 401k
I am trying to figure it out in TEST, but, I am not having much success. I've tried a manual check, but it doesn't remove any taxes. When I do a regular payroll transaction, it does not pick it up to build. Also, it won't let me do a negative amount to the 401k deduction, which I was hoping would allow me to adjust the employee's 401k YTD balance.
In advance, I do understand that there is a solution available from Integrity Data to make this easier, but we do not have it at this time. Given that we intend to fix the Max Deduction amount, I am not sure we will have any issues going forward.
Thanks.
↧