Over at High Dynamic Range, Aaron Berquist is (freakishly?) infatuated with FieldService, Or: Product 949, You Sure Are Fine. Checkout his post to find out why.
You, Me and Dynamics GP
The premier information site for Microsoft Dynamics GP
Showing posts with label Contracts. Show all posts
Showing posts with label Contracts. Show all posts
04 January 2011
06 December 2010
02 December 2010
Tool for Improving "Mark All" Speed in Contract Administration
Aaron Berquist drops a new blog on the community with a couple of great posts including a Tool for Improving "Mark All" Speed in Contract Administration . This is a great start Aaron. I’ve subscribed to get updates.
11 August 2008
Weekly Dynamic: Contracts, One Time Billing, Multiyear Revenue
In the Microsoft Dynamics GP Contracts module, a part of the Field Service series, it's easy to see how to create monthly, quarterly or annual billed contracts with a different revenue recognition schedule. What's not as obvious is how to deal with something like a three year agreement that is paid up front. There is no billing type beyond annual.
The Contracts module can certainly handle this. Using the example above, simply set the revenue recognition dates to the appropriate 3 year period. Then set the billing type to Annual and the billing dates to only cover the first year. The system will create one bill at the beginning of the billing period for the entire 3 year coverage time.
I have seen cases where this causes the monthly billing amount in the lines to be off but that has no effect on these type contracts. It's annoying, but it won't hurt anything.
So there you go, multi year, single payment contracts in just a couple of short steps.
The Contracts module can certainly handle this. Using the example above, simply set the revenue recognition dates to the appropriate 3 year period. Then set the billing type to Annual and the billing dates to only cover the first year. The system will create one bill at the beginning of the billing period for the entire 3 year coverage time.
I have seen cases where this causes the monthly billing amount in the lines to be off but that has no effect on these type contracts. It's annoying, but it won't hurt anything.
So there you go, multi year, single payment contracts in just a couple of short steps.
28 July 2008
Weekly Dynamic: Contract Secrets
Full Disclosure and warnings first. My employer, I.B.I.S., Inc. wrote the Field Service modules (Including the Contracts module mentioned here) and later sold them to Microsoft. I.B.I.S. continues to provide development work on this module but I don't have any inside knowledge related to the modules. Anything in here I developed on my own. Also, this is tip has the potential to make a huge mess, use it at your own risk.
I've spent a lot of time with the Contracts module lately and thought I would share a little tip. There is a trigger on the Contract Lines table (SVC00601) that creates the lines in the Billing(SVC00603) and Revenue Recognition (SVC00604) tables.
What this means is that if you change the dates in the SVC00601 table via SQL, it automatically sets the right amount of revenue recognition lines. This is really useful in an initial setup scenario where you might have thousands of contracts coming to GP from another system. If you find an error, you can make mass adjustments via SQL. This could also be useful if you need to modify the Revenue Recognition schedule to match a schedule from an old system.
Be careful when you use this though. It's best used in a setup scenario where no billing or revenue recognition have occurred yet. Also, some choices in the Contract Header table (SVC00600) such as Revenue Smoothing or Billing Smoothing affect the behavior of the trigger.
It is nice to know that it's a SQL trigger and not something in the code that modifies billing and revenue schedules. It makes wholesale adjustments much easier.
Update: I just wanted to add that if any billing has been done, this trigger won't fire. This only works for initial setup.
I've spent a lot of time with the Contracts module lately and thought I would share a little tip. There is a trigger on the Contract Lines table (SVC00601) that creates the lines in the Billing(SVC00603) and Revenue Recognition (SVC00604) tables.
What this means is that if you change the dates in the SVC00601 table via SQL, it automatically sets the right amount of revenue recognition lines. This is really useful in an initial setup scenario where you might have thousands of contracts coming to GP from another system. If you find an error, you can make mass adjustments via SQL. This could also be useful if you need to modify the Revenue Recognition schedule to match a schedule from an old system.
Be careful when you use this though. It's best used in a setup scenario where no billing or revenue recognition have occurred yet. Also, some choices in the Contract Header table (SVC00600) such as Revenue Smoothing or Billing Smoothing affect the behavior of the trigger.
It is nice to know that it's a SQL trigger and not something in the code that modifies billing and revenue schedules. It makes wholesale adjustments much easier.
Update: I just wanted to add that if any billing has been done, this trigger won't fire. This only works for initial setup.
Subscribe to:
Posts (Atom)