Demystifying GP Tables and Transaction Flows

    

Table Names and Transaction Flow

WORK to OPEN to HISTORY

Update of http://dynamicsconfessions.blogspot.com/2009/11/moving-from-work-to-open-to-history.html

This article started (as so many do) from a question posted on the newsgroup about how data flows through the system and how you can figure out what the tables contain. I did a little research and concluded there wasn’t any summary of data flow and table conventions available. This post is a result of that research.

Tables – what’s in a name?

First, a short explanation of table names is in order. Each table has three names. Sometimes they are the same, but most of the time they are different. The Dexterity programmer determines the names for the tables. The three different table names are:

1. Technical Name
2. Display Name
3. Physical Name

Technical Name

The Technical Name is the name used by the Dexterity programmers in Dexterity code. You will often see the Technical Name in error messages such as:

A Get/Change Operation on table 'UPR_Year_End_WORK_HDR'failed accessing SQL data.

In the above error message, 'UPR_Year_End_WORK_HDR' is the Technical Name for the Payroll Year End Header table.

Display Name

The Display Name is also known as the ‘friendly name’. Display Names use whole words with spaces between them. Display Names protect the user from needing to translate Technical Names or Physical Names into real words. You see Display Names when you are working with a tool that is normally used by the end user. Tools such as SmartList Builder, Excel Report Builder and Report Writer use Display Names.

The screenshot below shows a list of Display Names on the Add Table window of SmartList Builder:

 

Physical Name

The Physical Name is the name seen by the database. Any type of error at the SQL level, for instance, will use the Physical Name. The error message below uses the Physical Name:

 

Also, if you launch the Microsoft SQL Server Management Studio application you will see the Physical Names of the tables. The screen shot below shows you how the table names appear in the Microsoft SQL Server Management Studio.
 

Most of your independent reporting tools, like Crystal Reports, use Physical Names.

 

Tables –naming convention for physical tables

A client recently told me that they were very confused by the table names of the Dynamics GP tables. I’m so used to those legacy table names that I don’t appreciate what a wonder it must be for a new user trying to write reports or follow the data flow.

In fact, any class I train that involves pulling data from tables (Extender, SmartList Builder, Excel ReportBuilder, ListBuilder, Report Writer, SSRS, Crystal Reports, etc.) sooner or later results in the question “How do we know which table to use?”. This query spawned the on-line class I developed for GPUG (Great Plains User Group) entitled “Finding the Dynamics GP Data you Need”

So, what do the table names mean? The old table names were limited to eight characters; remember it was the late 1980’s when this was being developed. The field names were also limited to eight characters.
 

In order to bring some sanity to that eight-character limitation, a pretty straightforward naming convention was created. This convention was followed religiously for the modules actually written by Great Plains vs. those that were acquired from other developers.
 

I actually think it’s a very good naming convention for the Dynamics GP data tables. This is only a convention, however. It is followed by the Great Plains programmers pretty diligently, but not so much by 3rd party developers.
 

Here are the basics, the first 2 or 3 characters will indicate the module name, and the numbers indicate the type of table.
 

Some of the more popular module abbreviations are in the table below.

Prefix	Module
GL	General Ledger
AF	Advanced Financial Analysis
PM	Payables Management
RM	Receivables Management
SOP	Sales Order Processing
POP	Purchase Order Processing
IV	Inventory
IVC	Invoicing (NOT SOP)
UPR	US Payroll
CM	Cash Management (Bank Rec)
LK	Linked Transactions
ME	EFT
PA	Project Accounting
FA	Fixed Assets
AA	Analytical Accounting
DTA	Multi-dimensional Analysis *
SY	System or Company
AHR	Advanced HR
HR	Human Resources
BM	Bill of Materials
DD	Direct Deposit
EXT	Extender
MC	Multicurrency
SVC	Field Service
ASI	SmartList Favorites
ERB	Excel Report Builder
EXT	Extender
SLB	SmartList Builder
CPY	Canadian Payroll **
PDK	Personal Data Keeper **
*	Thanks to Victoria Yudin
**	Thanks to Beat Bucher

 

After the module abbreviation is a five character (normally 5 characters) number that indicates the table type.
 

Knowing what these numbers stand for will help you zero in on the correct table. The table below sets out the numbering convention for the table types.

Table Number	Table Type
00000	Master Tables
10000	Work Tables
20000	Open Tables
30000	History Tables
40000	Setup Tables
50000	Temp Tables
60000	Relation Tables
70000	Report Options Tables
80000	Posting Journal Reprint Tables
90000	Mixed bag – no standard type

 

Master Tables (00000) are mostly what you find under the ‘Cards’ area. These are your Customers, Vendors, Inventory Items, GL Accounts and the like. For instance, the information you see on the Customer Maintenance window is stored in the RM Customer MSTR or RM00101 table.

 

Work, Open and History (10000, 20000 and 30000) These tables are explained in the next section of this document.

 

Setup Tables (40000) include choices you have made to initiate a module. For instance, the information entered on the Payables Management Setup window is stored in the PM Setup File or PM40100 table.
 

Temp Tables (50000) are tables that are used temporarily by the system and the records in those tables can normally be deleted without issue. For instance, the Net Profit Temporary table or AF50000 is used by the Advanced Financial Analysis module to hold the Net Profit amount that will be used on one of the statements. Once the statement has been printed, the number is irrelevant.
 

Relation or Cross Reference Tables (60000) are tables that are used to store information that spans more than one module. For instance, the SOP/POP Link table (SOP60100) holds the information about POP documents linked to SOP documents.
 

Another example is the Sales Customer Item Cross Reference (SOP60300). This table reflects the information as to how customer item numbers relate to regular item numbers. There are not that many tables in the 60000 range.
 

Report Options Tables (70000) contain all of the information you enter in any of the report options windows. The image below comes from the Payables Trial Balance Report Options window (PM70500).

 

Posting Journal Reprint Tables (80000) contain all of the information you need to reprint your posting journals. So don’t feel like you MUST print all of those reports. They are here waiting for you should you ever need to reprint them.
 

Miscellaneous Tables (90000) this group is a mixed bag of information. The table below contains the Display Names of several 90000 tables.

 

Physical Name	Display Name
CM90000	CM Transmission Log
CM90001	Checkbook EFT Log
CN90000	Collections - User Preferences
ERB90100	Data Connection Products
ERB90200	Data Connection Series
ERB90300	Data Connections
ERB90400	Data Connection Restrictions
ERB90450	Data Connection Restriction Values
ERB90500	Data Connection Security
EXT90101	Product List
EXT90101	Resource Cache - Product List
EXT90102	Product Series List
EXT90102	Resource Cache - Product Series List
EXT90103	Form List
EXT90103	Resource Cache - Form List
EXT90104	Window List
EXT90105	Report List
EXT90106	Resource Cache - Table List
EXT90106	Table List
PA91301	PA Contract Segment Override Header
PA91304	PA Contract Segment Override Detail
PA92301	PA Contract Template Seg Override Header
PA92304	PA Contract Template Seg Override Detail
PDK90003	PDK File Error Log
PDK90100	PDK Security
PP900000	Deferral Opened Periods
PTO90000	PTO Pending Master Conversion
SE90001	Account Rollups Account List Accelerator
SE988977	Account Rollups Options Columns
SLB90000	Third Party GoTo Types
SY90000	SY_User_Object_Store (Dynamics User Object Store)
SY90100	Default Chart of Accounts

 

There are, of course exceptions even within the Dynamics.dic dictionary. Additionally, the DYNAMICS database has its own naming scheme. So now you know; if you were looking for the customer master table, you would start with the RM00*** table and go from there.

Victoria Yudin has some fantastic information on the popular tables from each module. If you are creating reports, or crafting SQL queries, it is information you can use http://victoriayudin.com/gp-tables/.

Victoria also has some very helpful SQL queries available for you to download.

Let’s move on to our WORK/OPEN/HISTORY discussion

 

Data Flow (WORK, OPEN and HISTORY progression)

I put together this document attempting to address the progression of transaction data for the following modules:

·         GL (Financial – general ledger journal entries)

·         CM  (Bank Transactions)

·         RM (Receivables Management – A/R transactions)

·         PM (Payables Management – A/P transactions)

·         SOP  (Sales Order Processing)

·         POP (Purchase Order Processing)

·         Invoicing (Basic invoicing, nothing to do with SOP)

·         Inventory
 

Dynamics GP transactions typically have three states:

1. Unposted
2. Posted
3. Historical
   These different states determine, to a large degree, whether the data is in the WORK, OPEN, or HISTORY table.
    

What causes the information to move through these tables varies. The progression is not consistent across modules and it’s easy to get bewildered trying to figure it out.
 

Below you will find a short summary of how the data moves through these tables. Also included under each section is a list of the more common tables for that module’s WORK, OPEN and HISTORY tables. The lists are not comprehensive, but they’ve captured the major tables.

GL (financial– general ledger)

WORK–

Unposted GL Transactions

 

Table Number	Description
GL10000	Transaction WORK
GL10001	Transaction Amounts WORK
GL10002	Transaction Clearing Amounts WORK
GL10100	Quick Journal WORK
GL10101	Quick Journal Amounts WORK
GL10300	General Ledger Tax WORK
GL12000	Budget Transaction WORK
GL12001	Budget Transaction Amounts WORK

A transaction lives in the Transaction WORK table before it has been committed to the ledger. You can still edit or delete a transaction when it is in the WORK tables.

 

OPEN–

Posted GL Transactions

Table Number	Description
GL20000	Year-to-Date Transaction OPEN

Once a transaction is posted, it is committed to the ledger. The header information is added to each line such that each leg of the journal entry is a complete record. The posted transaction moves to the transaction OPEN table. For GL, each record in the OPEN table represents a single leg of the journal entry.

 

HISTORY–

Transactions from a closed year

Table Number	Description
GL30000	Account Transaction HISTORY
GL32000	Budget Transaction HISTORY

Until the year closes all of the GL transactions are in the Year-to-Date Transaction OPEN table (GL20000).  I don’t mean when the year ends, but rather after the year-end closing routine is done. After the closing routine, the posted transactions move to the transaction HISTORY table (GL30000). You cannot move them back to the OPEN table after the year end closes. In addition, you cannot ‘unpost’ a transaction and move it back into the WORK table.
 

As with all rules, there are exceptions. Here's one. Using the Fiscal Periods Modifier tool in the Professional Services Tools Library you can indeed open a previously closed year. However, the data does not move from the Account Transaction HISTORY table (GL30000) over to the Year-to-Date Transaction OPEN table (GL20000).

CM (Bank Transactions)

WORK–

Unposted Deposit Transactions

Table Number	Description
CM10100	Deposit header information
CM10101	Each item to be deposited
ECM10003	ECM_Committed_Detail
ECM10002	ECM_CPO_Inquiry
ECM10001	ECM_Inquiry
ECM10110	ECM_Line_Ctrl
ECM10005	ECM_ReqItemList

 OPEN–

Posted Bank Transactions

Posted Deposit Transactions

Reconciliations

Table Number	Description
CM20203	Checkbook EFT Transaction Batch
CM20202	Checkbook Transaction Electronic Funds Transfer
CM20400	CM Distribution
CM20100	CM Journal
CM20300	CM Receipt
CM20501	CM Reconcile Adjustments
CM20500	CM Reconcile Header
CM20200	CM Transaction
CM20201	CM Transaction Totals
CM20600	CM Transfer

 

HISTORY–

There is no HISTORY table

PM (Payables Management – A/P transactions)

WORK–

Unposted PM Transactions

Table Number	Description
PM10100	PM Distribution WORK OPEN
PM10200	PM Apply To WORK OPEN File
PM10100	PM Distribution WORK OPEN
PM10400	PM Manual Payment WORK File
PM10201	PM Payment Apply To WORK File
PM10300	PM Payment WORK
PM10500	PM Tax WORK File
PM10000	PM Transaction WORK File

OPEN–

Posted PM Transactions

Posted Purchasing Invoices

 

Table Number	Description
PM10100	PM Distribution WORK OPEN
PM10200	PM Apply To WORK OPEN File
PM10100	PM Distribution WORK OPEN
PM20401	PM Scheduled Payment LINE
PM20400	PM Scheduled Payments Header
PM20000	PM Transaction OPEN File

Posted transactions stay in the OPEN table until they have been fully applied. OPEN means there is still an amount outstanding. If you write a check that partially pays an invoice, that invoice would remain in the OPEN table. The check, however, if its entire balance was applied, would move to the HISTORY table.

                

HISTORY–

Posted, Fully Applied, or Voided PM Transactions

Table Number	Description
PM30300	PM Apply To HISTORY File
PM30600	PM Distribution HISTORY File
PM30200	PM Paid Transaction HISTORY File
PM30401	PM Scheduled Payments Header HISTORY
PM30700	PM Tax HISTORY File
PM30800	PM Tax Invoices

Transactions automatically move to HISTORY when the document becomes fully applied (a transaction is a check, credit memo, invoice, etc.) For a check or credit memo, fully applied means the entire balance of the check or credit memo has been matched to an invoice. For an invoice, it is when the balance is fully paid off (or written off), or a credit memo takes the balance to zero. Voiding a document in the OPEN table will automatically move the voided document to HISTORY.

Documents in HISTORY can also be voided thereby moving them back to the OPEN table. Documents cannot be 'unposted' and moved back to the WORK table. Likewise, documents cannot be “unvoided” and moved back to the OPEN table.

RM (Receivables Management - A/R Transactions)

WORK–

Unposted RM Transactions

Table Number	Description
RM10201	RM Cash Receipts WORK File
RM10501	RM Commission WORK File
RM10101	RM Distribution WORK File
RM10301	RM Sales WORK File
RM10601	RM Tax WORK File

 

OPEN–

Posted RM Transactions

Posted SOP Invoices

Posted SOP Cash Receipts

Voided RM Transactions

Table Number	Description
RM10101	RM Distribution WORK File
RM20201	RM Apply OPEN File
RM20101	RM OPEN File
RM20400	RM Scheduled Payment Header
RM20401	RM Scheduled Payment Line

 

HISTORY–

Posted and Fully Applied Receivables Transactions

Table Number	Description
RM30501	Commission HISTORY
RM30301	Receivables GL Distribution HISTORY
RM30201	RM Apply HISTORY File
RM30502	RM Batch HISTORY
RM30101	RM HISTORY File
RM30401	RM Scheduled Payment Header HISTORY
RM30601	RM Tax HISTORY File

Unlike PM transactions, RM transactions do NOT automatically move to HISTORY. You need to run the 'Paid Transaction Removal' routine in order to move the fully applied transactions to HISTORY. Nothing automatically moves to HISTORY, not voids, not write-offs, not payoffs, nothing. Only 'fully applied' documents will be moved via the 'Paid Transaction Removal' routine.

Therefore, if you still have a balance on an invoice, it stays in the OPEN table. If a credit memo or receipt has not been matched up to an invoice, it will stay in the OPEN table. To get it out of the OPEN table and move it to HISTORY, run the 'Paid Transaction Removal' routine. The fact that the customer's net balance is zero does not impact whether or not the document moves to HISTORY.

When you run the Paid Trx Removal you specify a cutoff date that applies to:

     ·         NSF checks

     ·         Voided documents

     ·         Waived (finance charges)

     ·         Paid Transactions

You specify a separate date for:

     ·         Checks

Once RM transactions are moved to HISTORY - they cannot be voided thereby moving them back to OPEN. This is why the checks have a separate date - what if they bounce!
 

Documents can be 'unapplied' only while they are in the OPEN table, not after they have been moved to HISTORY. For instance, if you applied a cash receipt to the wrong invoice, you can change it to the correct invoice only if it has not been moved to HISTORY. Documents can be voided only while they are in the OPEN table. Voided documents stay in the OPEN table until they are moved to history via the 'Paid Transaction Removal' routine. You cannot void a document in the HISTORY table.
 

But here’s one HUGE exception.  Using the Professional Services Tools Library (PSTL) you can indeed “unapply” an amount from a document in HISTORY.  If, for example, an invoice had been completely paid off and moved to history and then you realize the cash was applied to the wrong invoice. Using the (PSTL) tool you can ‘unapply’ the cash thereby moving both the cash receipt and the invoice back into the OPEN table.
 

Once you have the documents back in the OPEN table you can apply the check to the correct invoice, void the document, write off the document or do anything else you can ordinarily do with an OPEN document.

SOP (Sales Order Processing)

WORK–

Unposted SOP documents

Table Number	Description
SOP10100	Sales Transaction WORK (SOP Header)
SOP10200	Sales Transaction Amounts WORK (SOP Line Items)
SOP10102	Sales Distribution WORK and HISTORY (Debits and Credits)
SOP10202	Sales Line Comment WORK and HISTORY (Comments on Line Items)
SOP10101	Sales Commissions WORK and HISTORY
SOP10203	Sales Order Bin Quantities WORK and HISTORY
SOP10103	Sales Payment WORK and HISTORY
SOP10201	Sales Serial/Lot WORK and HISTORY
SOP10105	Sales Taxes WORK and HISTORY
SOP10106	Sales User-Defined WORK HISTORY

An unposted document includes not only Invoices and Returns, but also Quotes, Orders and Backorders.
 

OPEN–

There is no OPEN file

When a SOP document is posted, the transaction moves to the RM OPEN table and the SOP document moves to the SOP HISTORY table. Only Invoices and Returns can be posted. The posted SOP document becomes an open receivable (or credit) in the RM OPEN table.
 

HISTORY–

Posted SOP Invoices or SOP Returns

Voided SOP Documents

Orders whose items have been fully transferred to other documents

Quotes that have had any item transferred to another document

Backorders that have been fully transferred to other documents

Table Number	Description
SOP30200	Sales Transaction HISTORY (Header information)
SOP30300	Sales Transaction Amounts HISTORY (Line item information)
SOP30201	Sales Deposit HISTORY
SOP10102	Sales Distribution WORK and HISTORY (Debits and Credits)
SOP10202	Sales Line Comment WORK and HISTORY (Comments on Line Items)
SOP10101	Sales Commissions WORK and HISTORY
SOP10203	Sales Order Bin Quantities WORK and HISTORY
SOP10103	Sales Payment WORK and HISTORY
SOP10201	Sales Serial/Lot WORK and HISTORY
SOP10105	Sales Taxes WORK and HISTORY
SOP10106	Sales User-Defined WORK HISTORY

SOP invoices and returns automatically move to HISTORY as soon as they are posted. For documents that do not automatically transfer to HISTORY, run the 'Reconcile-Remove Sales Documents' utility to move them.
 

The following documents cannot be posted:

·         Quotes

·         Orders

·        Backorders

POP (Purchase Order Processing)

WORK–

Any Purchase Order document that has not been moved to history

Table Number	Description
POP10100	Purchase Order WORK
POP10110	Purchase Order Line
POP10300	Purchasing Receipt WORK
POP10310	Purchasing Receipt Line
POP10150	Purchase Order Comment
POP10160	Purchase Order Tax
POP10340	Purchasing Bin Quantities WORK
POP10550	Purchasing Comment
POP10390	Purchasing Distribution WORK
POP10700	Purchasing Landed Cost
POP10140	Purchasing Manufacturer Numbers
POP10500	Purchasing Receipt Line Quantities
POP10306	Purchasing Receipt User-Defined
POP10330	Purchasing Serial Lot WORK
POP10600	Purchasing Shipment Invoice Apply
POP10360	Purchasing Tax

OPEN–

There is no open file
 

HISTORY–

Posted Receipts automatically move to history

Posted Purchasing Invoices automatically move to history

Voided Purchasing Documents automatically move to history

Closed Purchase Orders

Cancelled Purchase Orders

Table Number	Description
POP30100	Purchase Order HISTORY (PO Header)
POP30110	Purchase Order Line HISTORY (PO Line Items)
POP30300	Purchasing Receipt HISTORY (Receipt Header)
POP30310	Purchasing Receipt Line HISTORY (Receipt Line Items)
POP30160	Purchase Order Tax HISTORY
POP30000	Purchasing Batch HISTORY
POP30340	Purchasing Bin Quantities HISTORY
POP30390	Purchasing Distribution HISTORY
POP30700	Purchasing Landed Cost HISTORY
POP30330	Purchasing Serial Lot HISTORY
POP30360	Purchasing Tax HISTORY

Posted Receipts, Posted Purchasing Invoices and Voided Purchasing Documents automatically move to history. You must run the Purchasing Routine 'Remove Completed Purchase Orders' to move all of the closed or canceled POs to HISTORY. If a PO is not closed or canceled it will not be moved, so there is no danger of moving a PO that doesn't qualify. You can set restrictions on which POP documents are examined for removal. It is not an ‘all or nothing’ kind of routine.

IVC (Basic Invoicing – not SOP)

WORK

Unposted Documents

Table Number	Description
IVC10400	Invoicing Commissions
IVC10300	Invoicing Distributions
IVC10103	Invoicing Line Comments
IVC10200	Invoicing Payments WORK
IVC10102	Invoicing Serial and Lot Number WORK
IVC10500	Invoicing Taxes
IVC10101	Invoicing Transaction Amounts WORK
IVC10100	Invoicing Transaction WORK

 

OPEN

There is no open file (posted transactions update receivables, like SOP)
 

HISTORY

Posted Invoices

Posted Returns

Table Number	Description
IVC30102	Invoicing Transaction Amounts HISTORY
IVC30101	Invoicing Transaction HISTORY
IVC10400	Invoicing Commissions
IVC10300	Invoicing Distributions
IVC10500	Invoicing Taxes
IVC10103	Invoicing Line Comments
IVC10102	Invoicing Serial and Lot Number WORK

Invoices and Returns automatically move to the HISTORY table when posted. Like SOP, when and invoice or return is posted, the customer transaction record moves into the RM OPEN table. The transaction, therefore becomes an open receivable or credit.

IV (Inventory)

WORK

Unposted Adjustments

Unposted Variances

Unposted Stock Counts

Unposted Transfers

 

Table Number	Description
IV10004	Inventory Bin Quantity Transfer
IV10201	Inventory Purchase Receipts Detail
IV10200	Inventory Purchase Receipts WORK
IV10002	Inventory Serial and Lot Number WORK
IV10001	Inventory Transaction Amounts WORK
IV10003	Inventory Transaction Bin Quantities WORK
IV10000	Inventory Transaction WORK

OPEN

There is no open file
 

HISTORY

Posted Transactions

 

Table Number	Description
IV30500	Inventory Distribution HISTORY
IV30300	Inventory Transaction Amounts HISTORY
IV30100	Inventory Transaction Batch HISTORY
IV30302	Inventory Transaction Bin Quantities HISTORY
IV30301	Inventory Transaction Detail HISTORY
IV30200	Inventory Transaction HISTORY
IV30600	Item Lot Attribute HISTORY
IV30400	Item Serial and Lot Number HISTORY

 

Inventory transactions are automatically moved to history when posted.

That's it! Please let me know of any adjustments you think I need to make to this.
 

Until next post!
 

Leslie

Change the name of the SQL Server

 

Sometimes it comes up that we need to change the name of the SQL Server. Below is a quick and dirty checklist on how to accomplish this task. I feel certain there are several iterations of this all over the Internet – now there is one more .

 

1. Open SQL Server Management Studio and click New Query.

2. Type Select @@ServerName to find out the current server name. In our example, we’ll be changing the server name from RKF to REH.

3. Next, type sp_dropserver ‘RKF’

4. You are now ready to add the correct name by typing sp_addserver ‘REH’.

5. Stop sql server and the sql server agent by opening a command prompt and typing net stop mssqlserver.

6. Restart SQL server by typing net start msssqlserver.

7. Restart SQL server agent by typing net start sqlserveragent.

8. Click New Query in SQL Server Management Studio and type select @@servername to verify everything is correct and you have successfully changed the sql server name.

Until next post!

Leslie

Refunding Over withheld FICA

I’m getting more and more questions trickle in regarding how to ‘fix’ payroll when you’ve over withheld on FICA.

This problem came about mostly because the first release of the 2012 tax tables put employee FICA back to 6.2%. As you all know, recent legislation kept the employee rate at 4.2%.

Well, for you early adopters out there, you may have a problem.

This blog article includes a proposed series of steps you can take to resolve the issue of having over withheld FICA the extra 2% that was part of the first release of Release 1 of the 2012 tax tables.

You have two problems when you Over withhold FICA (or any tax).

First problem: You need to give the employee back the money and correct his payroll summary to reflect the correct FICA. This fix assumes the percentage was wrong; it does not include the added complication of FICA wages being wrong. Meaning that you included an amount in FICA wages that you shouldn’t have

Second problem: Fixing the employee’s tax record in GP so it properly reflects the amount of FICA tax withheld.

Problem 1: Fixing the Employee

1) Set up a new pay code (or use an existing) with the pay type of ‘Business Expense’. Uncheck all of the ‘Subject to Taxes’ boxes and make sure the ‘Report as Wages’ box is not checked


2) Assign this Pay Code to the employee needing the refund, accept the company defaults. Be sure the Workers’ Comp Code is blank.


3) Enter a payroll transaction for the employee needing a refund and use the Business Expense pay code you set up in step (1). Make sure no taxes are calculating.


4) Close the batch and build the check(s). Make sure:
a) No automatic pay types are checked
b) You have included the pay period that you put on the employee pay code
c) No deductions are included (check it, don’t presume)
d) No benefits are included (check this too)
e) Don’t forget to select the batch you just created


5) Select ‘Build’ when you are happy with the settings.
6) Check your Build report for errors – you shouldn’t have any.
7) Calculate checks from payroll transactions menu


8) Print the checks and post the batch.
9) Make sure NO other entries are on the report except for the amount paid the employee. There should be NO TAX, NO BENEFITS, NO DEDUCTIONS.

The employee should be fixed at this point as far as getting their money back, now to deal with the FICA tax record.

Problem 2: Fixing the Employee FICA withheld amount.

1) You will use the Payroll Manual Check window to adjust the tax.
2) DO NOT enter a batch ID for this transaction.
3) Select the Transaction Type as FICA Soc Sec Tax, the Code FICASS should appear on the window.
4) Enter the amount that you refunded the employee AS A NEGATIVE NUMBER in the amount box.
5) We aren’t doing anything to Taxable Wages, so leave that field blank.


6) Save the transaction and make sure the Net Amount is the amount that was over withheld.


7) Post the entry – remember no batches!
8) Watch your Distribution accounts and checkbook register because those may have to be adjusted, depending on your settings

Good luck with it.

There are probably other ways to do this and I invite your comments. This is the way we have been doing it.

Kind regards,

Leslie

Management Reporter 2012–more info 1

First, the blog that tells all on what is currently public on Management Reporter 2012.

http://blogs.msdn.com/b/dynamicscpm/

Remember that I said there was more! My good friend and fellow MVP Mariano Gomez is trying to get the fine folks at Microsoft to let us wow you by letting us talk about ALL of the planned features instead of trickling them out one at a time.

This new release is big. It’s time to start making plans to convert to Management Reporter and say goodbye to our good friend FRx.

Leslie

Management Reporter 2012 Rocks!

 

It’s time to put FRx out to pasture and welcome Management Reporter with open arms!

Heretofore I have not been carrying the flag for Management Reporter, but I just saw some stuff today that blows the doors off of what it can do. Management Reporter has come of age!

I’ll be sharing more details as soon as I find out which ones I can share, but there are more features coming that have not been advertised. Stay tuned, Management Reporter 2012 is a must.

It’s so good that it would be worth it to go to Convergence just to learn about Management Reporter 2012. Since its targeted release date is date Q1 2012 – that puts it in prime time for Convergence.

More to come, but just know that so many things you wanted it to do it WILL!

Until next post!

Leslie

2012 Tax tables re-released!

Round 1 of the 2012 tax tables have been re-released to reflect the changes made by congress to extend the 2% tax holiday.  Make sure you have the new tables or you will be buying yourself a lot of heartache.

Get the new tax tables from PartnerSource: 2012 Tax Tables from PartnerSource

Until next post!

Leslie

Federal W-2 electronic file couldn’t be created

If you have ever been lucky enough to receive this error, it can be difficult to track down a solution. Fortunately, one solution is easy – an ‘additional information’ button would have been nice though.



In my world this error message is presented because the path indicated in the File Name field does not exist, or you do not have ‘write’ permission to it.



Some of the newer operating systems, like Windows 7, will not let you create files in what they deem to be ‘protected folders’. So what worked last year might not work this year.

Good luck with year-end!

Until next post!

Leslie

Beware the 2012 Tax Tables!

The first batch of 2012 tax tables issued by GP are WRONG.

DO NOT USE THEM!

The FICA withholding is set to 6.2% instead of 4.2%. I know how much fun we had last year with this problem, let's not do it again. GP will be issuing new tables this week - those should be correct.

If you have imported the 2012 tables, you can simply change the FICAS tax table to reflect the correct 4.2% rate.

Here's how to change the percentage:


Microsoft Dynamics GP > Setup > System > Payroll Tax

1. Tax Code = FICAS

2. Select the 'Filing Status' button

Payroll Tax Setup window

On next window:

3. Filing Status = NA

4. Select the 'Tables' button

Payroll Tax Setup window

Type in the new Tax Rate where indicated. You can also update the limit. In the window below, the FICA limit is 106,800. The limit goes up for the 2012 tax year to $110,100.

Payroll Tax Tables window

We are all rushing to the finish line this time of year - don't forget to have fun!  I hope this will help someone.

Until next post!

Leslie

Internal Error 2738

Have you ever started to install a product, think it’s about to install, and then been greeted with:

This happened to me recently (today) while installing the GP2010 version of AvaTax. Specifically AvaTax 11.0.0.0.1.05.

Well, I’ve seen this error many times and have solved it by registering the vbscript.dll. To register the DLL, do the following:
For a 32-bit machine

1. First, be sure to close the Windows installer.
2. Click Start > All Programs > Accessories
3. Right-click on Command Prompt and select Run as Administrator.
4. Type cd C:\Windows\System32 and then press Enter.
5. Type regsvr32 C:\Windows\System32\vbscript.dll and then press Enter.
6. You will hopefully receive the following dialog:
   Click OK
7. Close the command prompt window.
8. Restart your computer.

For a 64-bit machine

1. First, be sure to close the Windows installer.
2. Click Start > All Programs > Accessories
3. Right-click on Command Prompt and select Run as Administrator.
4. Type cd C:\Windows\SysWOW64 and then press Enter.
5. Type regsvr32 C:\Windows\SysWOW64\vbscript.dll and then press Enter.
6. You will hopefully receive the following dialog:
   Click OK
7. Close the command prompt window.
8. Restart your computer.

Normally, that’s all you need to do. But what if things go wrong???

If Things Go Wrong:
If this doesn’t work, you’ll need to take more aggressive action. After searching the MSDN site and blogs, I found the solution. If you want to read the original article, go to: article on 2738 errors.  As it turns out, script-based custom action failures are behind many 2738 (and 2739) errors. If you are a programmer (are you listening Avalara?) it would be best not to use script-based custom actions in an MSI. If you do, you are opening up your users to problems.
The problem is that re-registering the DLL from a regular command prompt writes the registration to  HKEY_CURRENT_USER instead of HKEY_CURRENT_MACHINE. Starting with Vista, the Windows Installer will not load and use scripting engines if the registration is written to HKEY_CURRENT_USER. Consequently, re-registering the DLL from a normal user cmd prompt, will not help fix this type of error.
To see if you have this problem – MAKE A BACKUP OF YOUR REGISTRY-  and then check for the existence of the key below, and unregister it if it exists in HKEY_CURRENT_USER.

• For a 32-bit machine: HKCU\SOFTWARE\Classes\CLSID\{ B54F3741-5B07-11CF-A4B0-00AA004A55E8}
• For a 64-bit machine: HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

To unregister the vbscript.dll from HKEY_CURRENT_USER:

1. First, be sure to close the Windows installer, and then MAKE A BACKUP OF YOUR REGISTRY. After the backup is complete, continue the listed steps.
2. Click Start > All Programs > Accessories
3. Right-click on Command Prompt and select Run as Administrator.
4. For a 32-bit machine type in the following command:
   reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
5. For a 64-bit machine type in the following command:
   reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

After removing the HKCU key, my software – Avalara’s AvaTax – installed perfectly.
I hope this helps someone with this delightful dialog:

Until next post!
Leslie

Demystify Monthly Maintenance Routines Transcript

Today was GP day at the Decisions Fall 2011 virtual Conference! My session was ‘Demystify Monthly Maintenance Routines’. After the presentation we all had some time in the chat room to exchange questions.We had some great questions in the session, but it was hard to match the question with the answer due to my below average typing skills.

I took a copy of the transcript and matched up the questions with the answers the best I could.
If you weren’t able to attend the session ‘live’, I hope you can listen to the recorded session that will be available next week.

It’s a great conference with some very fun and informative sessions!

Enjoy!

Sheila Jefferson-Ross (12/06/2011 12:43:33 PM):Why should you wait to move transactions to History in Receivables? Is there a benefit?
Leslie Vail (12/06/2011 1:13:08 PM):Sheila: why wait to move transaction to history. For AR, you cannot get them back to open if you need to void or modify, or bounce a check. added info: When you move trx to history, you will also clean up the Apply window. The Apply window lists transactions in the Open table only. If you don't archive, this list can become quite unwieldy.

Stephanie Cole (12/06/2011 12:45:03 PM):What can you do if you have moved an accounts receivable transaction to history and need to change the application?
Leslie Vail (12/06/2011 1:13:44 PM):Stephanie: There is a tool called Unapply RM that you can buy. it's part of the PSTL tools

Barb Schroth (12/06/2011 1:04:21 PM):Will these slides be available anywhere?
Leslie Vail (12/06/2011 1:14:01 PM):Barb: yes, the slides are available

Hal Steinkopf (12/06/2011 1:06:48 PM):A "print only" option to preview what will happen seems so logical for all routines/utilities. Is there some operational reason that it is not available for all of them?
Leslie Vail (12/06/2011 1:14:31 PM):Hal: I agree 1000%. Different programmers are about all that I can come up with.

Sheila Jefferson-Ross (12/06/2011 1:08:33 PM):Can any user access PSTL once installed or do they have to login as 'sa'?
Leslie Vail (12/06/2011 1:15:02 PM):Sheila: you have to log in as ‘sa’ to run any PSTL tool. Of course, normal security also applies

Laura O'Loughlin (12/06/2011 1:09:23 PM):did you say the gl year end utility deletes active, but unused accounts orjust inactive
Leslie Vail (12/06/2011 1:15:24 PM):Laura: it deletes inactive accounts that have never been used

Beat Bucher (12/06/2011 1:12:27 PM):My current users have kept 3 years worth of POP transactions in the work tables...
Leslie Vail (12/06/2011 1:15:48 PM):Beat: Boy, their lookups and reports must be slow. Why?

Hal Steinkopf (12/06/2011 1:13:00 PM):Leslie, are you chatting with us or are we chatting among ourselves?
Leslie Vail (12/06/2011 1:16:10 PM):Hal: I'm here, just moving through the quesitons

Ladd Sustar (12/06/2011 1:13:03 PM):Good job. thank you for the information.
Sheila Jefferson-Ross (12/06/2011 1:13:08 PM):Moving PO's to history can be done more often than 3 years. They are only moved to history and can viewed at any time.
Mariano Arias (12/06/2011 1:13:13 PM):Thank you Leslie ... Regards from Mexico!!!
Brenda Haynes (12/06/2011 1:13:32 PM):Hi Leslie: Is it only on Receivables that checklinks should be run over and over until it clears?
Leslie Vail (12/06/2011 1:16:45 PM):Brenda: no, all of them should run until clear

Ladd Sustar (12/06/2011 1:14:09 PM):i have done this on other modules as well - rerun of checklinks
Hal Steinkopf (12/06/2011 1:15:46 PM):Different programmers is a mighty poor excuse for inconsistencies in a product. I will put heat on microsoft to clean that up and encourage others to do same.
Leslie Vail (12/06/2011 1:17:03 PM):Hal: Here here!

Tom Johnson (12/06/2011 1:16:12 PM):Similar to Beat's question, is there a recommended interval for running Paid Trx Removal on RM? Is there any issue with never moving open trx to history?
Leslie Vail (12/06/2011 1:17:32 PM):Tom: never moving to history is a problem if you print statements.

Beat Bucher (12/06/2011 1:16:22 PM):I really have no idea... I told them to keep at max the current year worth of POP documents..
Sheila Jefferson-Ross (12/06/2011 1:16:58 PM):If you don't move your paid transactions to history in AR you will have incredibly slow reports - trial balance, statements etc...
Sonny Pawchuk (12/06/2011 1:17:01 PM):Do you have any hints with Analytical Accounting, Running the Check links on that module always provides interesting errors/results and running a year end with the module still intimidates me (because there always seems to be a possibility of loosing AA data). Trying to run any AA process in a test company never seems to work.
Beat Bucher (12/06/2011 1:17:09 PM):I think the move to history should be part of the month end activities, but purchasing doens't really have one..
Leslie Vail (12/06/2011 1:18:43 PM):All: I don't know what the reluctance is to moving to history. Back many years ago you couldn't reprint a PO in history. But today that is not a problem

Sheila Jefferson-Ross (12/06/2011 1:19:21 PM):Leslie - can you copy a PO that has been moved to history?
Leslie Vail (12/06/2011 1:24:26 PM):Sheila: you can copy open or history POs

Beat Bucher (12/06/2011 1:19:28 PM):I think it's a remaining of 'old' business processes that were never challenged... :-)
Hal Steinkopf (12/06/2011 1:19:53 PM):...and records in history will really speed up processing of SmartLists, NavigationLists, inquiries, etc when done on "Current"/open records
Tom Johnson (12/06/2011 1:20:00 PM):I personally don't have a problem with moving data to history....it's all the other people. Isn't that always the case?
Leslie Vail (12/06/2011 1:20:21 PM):Tom: darned all of those other people :)

Hal Steinkopf (12/06/2011 1:22:01 PM):Thank you Leslie - a very informative session! ...and with just enough detail (and not too much) to keep my interest.
Leslie Vail (12/06/2011 1:22:28 PM):Hal: thank you very much.

Sheila Jefferson-Ross (12/06/2011 1:22:26 PM):On the topic of Mass Deleting of Vendors - I just ran a SQL script that changed the vendor status to Temporary if they had not had any checks cut since 2006 and their current balance was zero. This saved a huge amount of time in changing all those vendor cards manually and now they can review their list of Temp vendors before using the Mass Delete.
Beat Bucher (12/06/2011 1:22:40 PM):Hey Leslie, thanks anyway for the presentation... didn't got everything because I was distracted by some urgent user calls :-(.. will recope with the recorded sessions.
Leslie Vail (12/06/2011 1:23:04 PM):Nice to see you again Beat!

Beat Bucher (12/06/2011 1:23:17 PM):Sheila, would you mind to share the quick script ?
Gabriel Vegas (12/06/2011 1:23:27 PM):Gracias por la sesion , bastante interesante
Beat Bucher (12/06/2011 1:23:48 PM):Me too :-p
Sheila Jefferson-Ross (12/06/2011 1:23:53 PM):How about I send it to Leslie and she can post it on her blog for all to see. Would that be something you would like Leslie?
Laura Vance (12/06/2011 1:24:03 PM):Yes, it was very helpful. Thanks for the info
Beat Bucher (12/06/2011 1:24:04 PM):YES !!
Brenda Haynes (12/06/2011 1:24:33 PM):That script would be great. Thanks.
Leslie Vail (12/06/2011 1:24:42 PM):Sheila: sure, bring it on

Sheila Jefferson-Ross (12/06/2011 1:25:17 PM):I'll put it together for you. Has everyone seen Leslie's blog? Can you share your blog address Leslie?
Beat Bucher (12/06/2011 1:25:20 PM):See you in Houston :-) and have a great time in the mean.
Leslie Vail (12/06/2011 1:25:50 PM):if you search for the Dynamics Confessor (corny I know) it will come up

Hal Steinkopf (12/06/2011 1:25:52 PM):and you can then convert the concept in that script to a view in your company database and then create a smartlist (with possible reminder) of all those vendors who qualify (obviously without the update effect).
Beat Bucher (12/06/2011 1:26:11 PM):http://dynamicsconfessions.blogspot.com/
Leslie Vail (12/06/2011 1:26:22 PM):Thanks Beat!

Beat Bucher (12/06/2011 1:26:27 PM):no Pb
Sheila Jefferson-Ross (12/06/2011 1:27:00 PM):You're the best Leslie. Talk soon!
Leslie Vail (12/06/2011 1:27:18 PM):Thank you thank you!!!!

Maryana Estrada (12/06/2011 1:27:38 PM):Thanks a lot Leslie! :D
Leslie Vail (12/06/2011 1:29:32 PM):You are all very welcome. I am so glad you came!

Reconciling Inventory, what really happens?

I’ve seen this question come up a couple of times lately, even here at the GPUG 2011 Summit. I have some good information about the details of the inventory reconciliation process so I thought it might help to pass it along to everyone.

The Inventory files involved in the reconcile are:

• Purchase Receipts (IV10200)
• Purchase Receipts Detail (IV10201)
• Item Master (IV00101)
• Item Serial Number Master (IV00200)
• Item Quantity Master (IV00102)
• Item Lot Number Master (IV00300)
• Item Vendor Master (IV00103)
• Inventory Transaction Amounts Work (IV10001)
• Inventory Serial and Lot Numbers Work (IV10002)
• Item Site Bin Master (IV00112)
• Inventory Transaction Bin Quantities Work (IV10003)
• Inventory Transaction Bin Quantities History (IV30302)

Additional files outside of Inventory are involved in the reconcile if modules Purchase Order Processing, Sales Order Processing, or Invoicing are loaded.

The files outside of inventory that may be involved are as follows:

• Purchase Order Line (POP10110)
• Purchasing Receipt Line Quantities (POP10500)
• Sales Transaction Amounts Work (SOP10200)
• Sales Serial/Lot Work and History (SOP10201)
• Invoicing Transaction Amounts Work (IVC10101)
• Invoicing Serial and Lot Number Work (IVC10102)

The Reconcile process goes like this:  

1. The quantities are reconciled first between the Purchase Receipts and the Item Serial Number Master file.
2. Then the Purchase Receipts and Item Lot Number Master files are reconciled.
3. At this point, the quantities are reconciled between the Purchase Receipts file and Item Quantity Master file
4. Reallocating of Inventory Transaction Amounts Work, Inventory Serial and Lot Numbers Work, Sales Transaction Amounts Work, Sales Serial/Lot Work and History, Invoicing Transaction Amounts Work and Invoicing Serial and Lot Number Work tables is done next.
5. The On Order quantities are determined for the Item Quantity Master and Item Vendor Master tables by comparing them to the Purchase Order Line and Purchasing Receipt Line Quantities tables.
6. The last step in the reconcile is to reconcile the quantities on each of the items’ individual quantity location records to the total quantity record for that same item.

This information is available in Article ID: 874220.
I created a picture for my slides:

I hope this is helpful!

Live the Dream!

Leslie Vail

Recording a Rebate from a Vendor

This has come up a few times in recent days, so I thought I’d post this quick tip about how to record a refund check or rebate received from a vendor.

You get a check in the mail!

Let’s say you buy enough office supplies to get a $100.00 cash reward from Advanced Office Systems.  They send you a $100.00 check. You could create a deposit in the Bank Rec module, but then you wouldn’t have a record of your good fortune with the vendor.

To record this $100.00 check and keep it linked to the vendor, use the Document Type Return in Payables Transaction Entry.

Put the amount of the refund in the Returns field and in the Check field. When you post the transaction, you will have evidence of it in the vendor record and the check will be waiting for you to deposit in the check register.



The $100.00 check is waiting to be deposited.


How do you apply it to a credit memo?

A kind user of the Community asked how to handle receiving the cash after they had already entered a credit document in anticipation of a credit or refund. My advice in this situation is to simply void the credit and re-enter it as a refund as described above.

Please let me know if you have more ideas!

Until next post!

Leslie Vail
leslievail@earthlink.net

---

Notable settings on the Account Maintenance Window

There are several settings on the Account Maintenance window that are underutilized. These settings have existed for over ten years, but still I see the default settings used in all but a meager number of installations. The following settings will be explored:

· Account Aliasing
· Allow Account Entry
· Account Category
· Posting Type
· Typical Balance
· Level of Posting from Series
· Include in Look up
· Effectively Inactivating an Account

Account Aliasing

Creating an account Alias allows you to speed data entry by creating a Nickname for an account. Instead of having to remember or search for a specific account number. To create an alias, simply add the nickname to the alias field just under the Description field.



To use the Alias during account entry, select the expansion arrow next to the Account Look up Button or use CTRL Q on the keyboard to open the Account Entry window. Enter the Alias in the Account entry window, and the corresponding account will automatically come into the transaction.

Allow Account Entry Check box

Using this check box can help keep your control accounts in balance with the general ledger. The default setting is checked thereby allowing this account to be selected if it has not defaulted in to a transaction. Therefore, you could make a journal entry directly to the cash account which most likely will create a problem during bank reconciliation. For all of your control accounts – those accounts updated by a subsidiary module – the Allow Account Entry check box should be cleared.



Once the check box is cleared, an attempt to use it will result in a warning dialog and the entry will not be allowed.

Account Category

This is a required field on the window and is used exclusively by the Advanced Financial Analysis module.



The category assigned to an account determines where the account will appear on the financial statements printed from the Financial Area Page.



The accounting system would run perfectly even if every account were assigned to the Cash category. Neither FRx nor Management Reporter relies on this setting to determine classification on the financials. Account Category reports CAN be used in financial reporting, and, you can create as many categories as you would like. In addition to creating new categories you can modify the descriptions of the default categories.

Add categories or modify category descriptions on the Account Category Setup window.

Financial > Setup > Category

Posting Type

The posting type determines which accounts are rolled into Retained Earnings during the financial year end close. This setting affects nothing else. As part of your year end close checklist be sure to check each account’s posting type. If you have a beginning balance in an income or expense account after year end close, then the posting type is incorrect. KB article 864913 provides detailed instructions on how to recover from this type of problem.

Typical Balance

This setting determines whether the account appears as a positive or negative number on the financial statements. The title is a bit misleading because even though the ‘typical’ balance of the accumulated depreciation account is a credit, the correct setting for purposes of the Account Maintenance window is Debit. Since accumulated depreciation functions as a reduction to an asset account, marking debit causes it to appear negative on the balance sheet. These settings were designed for the Advanced Financial Analysis module, and also control in which column (debit or credit) the cursor defaults during transaction entry.

In short, the following are the correct selections for this section regardless of the typical balance from an accounting point of view:

Account Type	Typical Balance
Asset	Debit
Liability	Credit
Equity	Credit
Income	Credit\
Expense	Debit

Level of Posting from Series

This setting works in concert with the ‘Create a Journal Entry Per’ option in the Posting Setup window. With ‘Batch’ selected and the ‘Use Account Settings’ check box marked, the system looks to the Account Maintenance window in order to know how to create the journal entry coming up from the subsidiary module.



Using the Payables Transaction Entry window as an example, the settings illustrated above would result in a single summarized entry to the Accounts Payable (000-2100-00) account per batch. Whether entries to the other accounts are made in detail or in summary would likewise be controlled by the settings on those individual accounts.

For example, suppose only the Accounts Payable account was set to ‘Summary’ and our batch contained three vouchers. Each voucher contained a debit to the Prepaid Insurance account and a credit to Accounts Payable.

The resulting entry posted to the GL for this batch would be as follows:

Dr. Prepaid Insurance 56.98
Dr. Prepaid Insurance 27.50
Dr. Prepaid Insurance 15.00
Cr. Accounts Payable 99.48

Include in Look up

If all of your accounts are listed whenever you click on the account look up button, then you haven’t made use of this powerful setting. The default setting marks all of the items (Sales, Inventory Control, Purchasing, and Payroll) and is rarely changed. To illustrate this setting, I’ve taken away the ‘Sales’ setting from all of the accounts except for the accounts I want to appear when I first hit the account look up button. Likewise, I’ve only included ‘Sales’ in the ‘Include in Lookup’ selection for my Sales accounts.



Now that my sales related accounts are marked to be included in the sales look up, my account look up window starts with Accounts Receivable instead of Cash.



The other accounts are readily available by clicking on the View menu and selecting All Accounts.

Inactivate that Account for good!

· Inactive – dah, enough said
· Allow Account Entry – uncheck this box
· Include in Look up – unmark all items



Until next post!

• Leslie Vail

Mekorma MICR error message (GP10)

I had a client get the following error when trying to create Payroll checks with the Mekorma MICR module:

Could not load external Get GUID@mdexlib.dll. Mekorma MICR needs to be re-installed on the workstation giving the error. Be sure to install using the MICR *.exe logged in as 'Administrator'

Mekorma did indeed need to be reinstalled. Reinstallation had been required before but I never understood what happened to the mdelib.dll file. Well now we know. The client’s malware detector isolated that file as a threat.

So, if this happens to you, be sure to identify the Mekorma .dlls as ‘friendly’ files.

Until next post!

Leslie

Dexterity I class scheduled for May 16th - 20th, 2011 will be running as scheduled

There are 3 seats left and still time to sign up!

Come join us in Orlando for Dexterity Basics training.

The Dex I class is being held at the facility of Integrated Business Group (IBG). IBG is a Certified Partner for Learning Resources and have the best classrooms I have ever seen. Comfortable chairs and lots of room to spread out!

For more information and to register call Roxanna Alvarez @ 407-677-0370 or e-mail her directly ralvarez@ibgnet.com.
Date and Location:

• When: May 16th – May 20
• Where: Orlando Florida

This class is very hands-on and starts at the beginning; no previous Dexterity experience is necessary.

A synopsis of the class is below this post.

I hope to see you there!

Until Next Post!
Leslie Vail

Dexterity I – Product Fundamentals
Synopsis:
Dexterity Product Fundamentals will teach you about the development environment used to build the Microsoft Dynamics GP family of products. This course will provide you with the foundation you need to build integrated, database-independent applications. In addition, you will learn how to provide powerful application functionality for Microsoft Dynamics GP.

By actively participating in these classes, you should learn:
Basic programming techniques used by Microsoft Dynamics GP to develop their core modules.

• How to modify existing Dynamics GP forms and reports in order to make customizations for customers.
• How to develop add-on applications that will interact with the Dynamics GP products to meet specific requests by customers.
• How to package and ship your dictionary allowing Microsoft Dynamics GP to make updates to Dynamics GP without affecting the developer's dictionary.
• How to register your product with Microsoft Dynamics GP using a unique Product ID to ensure no duplication of add-on applications with the same name.
• How to develop add-on applications that will "look and feel" like Dynamics GP and provide seamless interface between the applications to ensure a professional finished product.
• How to use object triggers, which are scripts in your applications that are invoked by events in Dynamics GP, allowing several developers to deliver enhancements to the same Dynamics GP form.

Who should attend?

Customers or Partners who will be customizing or building add-on or standalone applications to integrate with the Microsoft Dynamics GP products.

General Prerequisites:
Prior to attending the course, it is highly recommended that students prepare for the course by going through the Dexterity Quick Start reference manual and working through the lessons in that manual. The Quick Start manual is located on the second CD of Dynamics GP and can be found under the Help-Online Manuals option from within Dexterity. Also, necessary is knowledge of basic programming concepts.
Price: $2,995 for 5 day course
Accepted Payment Methods: Check, Visa, MasterCard, American Express

Granting Security to Basic Information and Navigation Windows

When security is converted, the DEFAULTUSER task is not included in the Role created for an existing user. Because this task is not included, some of the windows for general navigation new to GP 10 were not available to converted users. This post explains how to add the DEFAULTUSER role to a CNV Role.

On the Navigation Pane, select the Administration Series button to launch the Administration Area Page.

On the Administration Area Page, navigate to the Setup Content Pane and then the System menu. Select Security Roles from the System menu and the Security Role Setup window will open.

Select from Icon	Select from Button

On the Security Role Setup window select each user’s Role ID, scroll down to the DEFAULTUSER Security Task ID and select it. This will grant access to a variety of navigation and lookup windows. Save this record and move on to the next applicable User Role ID. For versions prior to GP2010 there is no utility to copy security between users.



Until next post!
Leslie

GP 2010 R2 – Ready to Download!

It’s HERE!

The covers have been pulled off of the newest version of Dynamics GP. Some fabulous new features have been added that really make it worth your time to install. Links to all of the download are at the bottom of this post.

Take a look at some of the R2 updates to Foundation alone:

Business Analyzer -  this is the absolute COOLEST!

You can use Business Analyzer to help you make business decisions by viewing
Microsoft Dynamics GP reports from your desktop. The following illustration
shows Business Analyzer from your desktop.

Home Page - Viewing multiple metrics
Multiple metrics can be displayed in your home page. You also can create your own
metrics to display in your home page.

Sending reports in e-mail messages
You can send most reports in an e-mail message if you’re using a MAPI compliant email
service. All reports sent in an e-mail will be sent in HTML format, which
doesn’t require any other setup procedures. The recipient of the report must be
using Internet Explorer 7 or higher to view the e-mailed report, but no additional
setup is required.

To send a report in an e-mail, you first must set up a report option. Then, you can set
up e-mail options for each report option. Those settings, which include recipients
for the e-mail and settings for embedding or attaching the report are saved with the
report option and you’ll be able to send updated reports to the same recipients.

Sending customized messages
You can create predefined messages to send to your customers and vendors. These
messages can be assigned to the documents that you want to send in e-mail so all
customers or vendors receive the same message for selected documents. For
example, you can send a promotional message to your customers when sending
sales quotes in e-mail. You also can assign a specific message to an individual
customer or vendor. For example, you can send a holiday greeting message to a
customer. When you create a message, you can enter an e-mail address so your
customer or vendor can reply to your e-mail.

You can customize your messages by adding fields that are associated with a
document type. For example, a message can be personalized to address each
customer or vendor by name. You could add the due date for a sales invoice in a
message or the PO number for a purchase order. You also can copy the message
information from an existing message ID to a new message ID.

Viewing Reporting Services metrics
You can use Microsoft® SQL Server® Reporting Services 2008 or Reporting Services
2008 R2 to display graphical representations of Microsoft Dynamics GP data in the
metrics area of your home page. Reporting Services metrics appear in the SQL
Reporting Services Report list.

Viewing additional information
If you want to analyze data in a Reporting Services 2008 or Reporting Services R2
metric displayed in your home page, you can click a data point in the metric to open
a detailed report for additional information. If you want to view additional data in
the detailed report, you can click certain data fields to open the maintenance or
inquiry window related to that data field.

Modifying a metric – At Last!
If you are using Report Builder 3.0 or Report Builder 2.0, you can open the Microsoft
SQL Server Report Builder window from the Metrics Detail window to modify SQL
Server Reporting Services metrics and KPIs (key performance indicators). SQL
Server Reporting Services R2 also must be installed and set up to use with Microsoft
Dynamics GP.

Opening a metric in Report Viewer
If you are using Reporting Services 2008 or Reporting Services 2008 R2 to display
metrics, you can click the View icon to display a metric in Report Viewer.

Installation and deployment features
Electronic Funds Transfer (EFT) for Receivables Management is installed along with
Microsoft Dynamics GP instead of as a separately selectable Microsoft Dynamics GP
feature.

Human Resources and Payroll Suite
This is now installed as a separately selectable Microsoft Dynamics GP feature instead as an additional component.

When deploying Reporting Services reports using the Microsoft SQL Server
Reporting Services Wizard, you can deploy reports to either Native mode (SQL Server Reporting Services) or SharePoint® mode.

You can deploy Reporting Services reports and Excel reports using Microsoft
Dynamics GP Utilities. After creating the system database or company database,
you can select which reports to deploy and the location to deploy the reports to.
Instead of selecting the series that you want to deploy reports for, reports for the
components that you have installed are deployed. If you are upgrading a company,
the deployed reports are automatically upgraded. In previous releases of Microsoft
Dynamics GP, you had to use a separate wizard to deploy SRS reports and a
separate wizard to deploy Microsoft Excel reports to Microsoft SharePoint.
If you aren't ready to deploy reports using Microsoft Dynamics GP Utilities, you can
deploy reports using the Report Tools Setup window in Microsoft Dynamics GP.
You can use the Report Tools Setup window to redeploy reports or deploy reports to
a different location.

List Performance Enhancements YAY! WOO HOO!
List views provide a view of your data that you can customize in a variety of ways.
In Microsoft Dynamics GP 2010 R2, improvements were made to the speed at which
the information is displayed, enabling you to spend your time using the list rather
than waiting for it to display.

Report deployment
You can deploy SQL Services Reporting Services reports and Microsoft Excel report
using the Report Tools Setup window in Microsoft Dynamics GP. You also can use
the window to redeploy reports or deploy reports to a different location.

SmartList Builder Publish multiple Excel reports at once
You can use the new Bulk Deploy Excel Reports window and select multiple Excel
reports to publish at once, rather than publishing them individually.

SmartList Builder Set the default column order in SmartList Builder
You can define default column order using SmartList Builder so that the SmartList
is displayed with the columns in the order you want when it is first opened. A new
window, Default Column Order is added to SmartList Builder for determining the
column order.

SmartList Builder Drill Down to Extender and SmartLists
You can use the Drill Down Builder to create drill downs from Microsoft Dynamics
GP, SmartLists and Extender. A Dynamics GP Form drill down opens a Microsoft
Dynamics GP form and sets values on the form. A SmartList drill down opens a
SmartList and sets search parameters. An Extender drill down opens an Extender
Form or Detail Form and sets the values of the ID fields.

SmartList Builder Multicompany Excel Reports in a Single Excel Worksheet
You can add data from multiple companies into a single Excel Worksheet. In
addition, you can add the Company ID and/or Name to each line so that you can
see which company the data came from.

SmartList Builder Update Multiple field settings at one time
You have the ability to modify field options for multiple fields with the same field
type at once instead of one at a time. For example, you can select display options
such as currency symbols and percentage signs and mark several fields to display
the option for using the Set Field Options window.

Add Microsoft Dynamics GP forms to Extender menus
You can add Microsoft Dynamics GP forms to Extender menus using the Add
Dynamics GP Forms window allowing additional flexibility to the menus you
create.

Unified Communications and Office Communicator 2007 functionality was added. This functionality is also available using the Linked Lookup fields on Extender windows and forms, detailed forms, and extra windows.

Copy lists in Extender
You can copy list field items from one form or window to another one. The Copy
List Items window shows all the lists defined in Extender, so you can choose which
list to copy from; then, select all or individual list items to copy. In addition, you can
append the list you copy to the existing list items.

Matched Table Enhancements
In the Matched Tables window, you have new Table Description fields to help
identify the tables, and the ability to include fields that don't appear in both
matched tables.

GET YOUR COPY NOW!

PartnerSource
Product Release Downloads for Microsoft Dynamics GP 2010
Word Template Generator for Microsoft Dynamics GP 2010 R2
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Visual Studio Tools for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Web Services for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for eConnect for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Web Services for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Integration Manager for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Personal Data Keeper for Microsoft Dynamics GP 2010

CustomerSource
Product Release Downloads for Microsoft Dynamics GP 2010
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Visual Studio Tools for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Web Services for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for eConnect for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Web Services for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Integration Manager for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Personal Data Keeper for Microsoft Dynamics GP 2010

Until next post!

Leslie Vail