Dynamics GP

Deployment Methodology for Dynamics GP Dictionary Files

2008-08-21T14:30:00Z

Deployment Methodology for Dynamics GP Dictionary Files

When installing Dynamics GP files, a decision is made as to where the files will be stored. This white paper will discuss the different options and the benefits of each.

The different methods we will discuss are:

Leaving the files in their default location (C:\Program Files\Microsoft Dynamics\GP)
Moving the report and forms dictionary (forms.dic and reports.dic) to a network share
Having the files reside in a source directory and pulling them to the workstation daily

Leaving the files in their default location

Pros:

Easy to do, since this is the default behavior.

Cons:

Difficult to update if there are modifications. In order to deploy a report modification, you would have to manually visit each work station and either import a new package through the interface or copy the new report.dic file to the local drive. Often this results in workstations with various modifications that a specific user might need - there is no consistent deployment throughout the enterprise. One user might have a report dictionary modified for a SOP document, another might have a modification for a POP document.
Custom modifications are not backed up. If the modification exists on one workstation only, there is no corporate memory of it.
Creates an atmosphere that might encourage individual users to make ad hoc modifications that only exist on one workstation.

Summary:

Best for 1-4 workstations, locations that have very few modifications

Moving the report and forms dictionaries to a network share

This option is best for most deployments. Create a share on the network and point the reports and forms dictionaries to that share. The dynamics.dic file is always local - it never changes and this helps to reduce network load and increase the speed of the application.

Pros:

Modifications are consistently deployed, since all users share the same reports.dic and forms.dic files.
Since all user share common .dic files, the inconsistent deployment created by the first option is avoided
Provides a network location where the dictionary files can be backed up
Ad hoc modifications are not possible

Cons:

Slightly increased network load
Adds an extra step to workstation installs
Modifications to the .dic files can only be done if all users are out of Dynamics.

Summary:

Best for 5-15 workstations, and moderate modification needs.

Having the files reside in a source directory and pulling them to the workstation daily

Create a folder (usually on the SQL Server) that is the main repository for .dic files.
Create a logon.bat file in Active Directory that directs all workstations to download the .dic files to the workstation at logon (only the files modified since the last logon are downloaded).

Pros:

Deployment of modifications is simple - copy the new .dic file to the deployment share and direct the users to log off and on again.
Good balance for network loading - files are always run locally, and downloaded only when changed.
Since all user share common .dic files, the inconsistent deployment created by the first option is avoided
Provides a network location where the dictionary files can be backed up
Ad hoc modifications are not possible

Cons:

Requires some networking skills to create and maintain the logon.bat file. Should only be done at locations that have a dependable networking resource.
Requires slightly more time to maintain going forward, adds one extra layer of complexity to the installation.

Summary:

Best for installations with more than 15 users or that expect heavy or ongoing modification needs. Requires a networking resource. Best if a developer is involved.

CM20200 Fields Definitions

2008-08-07T14:56:00Z

Element name	Data type	Length	Required	Default	Description
Option	i4	2	Y	Not applicable	Transaction option:
					1=Enter transaction;
					2=Enter receipt
CMTrxType	i4	2	N	3	Transaction type (only used when Option=1):
					3=Check;
					4=Withdrawal;
					5=Increase adjustment; 6=Decrease adjustment
RcpType	i4	2	N	1	Receipt type (only used when Option=2):
					1=Check;
					2=Cash;
					3=Credit card
TRXDATE	datetime	16	N		Transaction date; default is system date
CHEKBKID	string	15	Y	Not applicable	Checkbook ID
CURNCYID	string	15	N		Currency ID; default is currency assigned to the checkbook
CMTrxNum	string	20	Y	Not applicable	Transaction number
CARDNAME	string	15	N		Credit card name; required when RcpType=3
paidtorcvdfrom	string	30	N		Paid to: when Option=1
					or
					Rcvd from: when Option=2
DSCRIPTN	string	30	N		Description
TRXAMNT	number	21	Y	Not applicable	Transaction amount
USERID	string	15	N		User ID; default is eBusiness
GLPOSTDT	datetime	16	N		GL posting date; default is TRXDATE
DistRef	string	30	N		Distribution reference; only used for required default distribution
BACHNUMB	string	15	N		GL batch number
					For additional information, see Bank Reconciliationi
XCHGRATE	number	21	N	0	Exchange rate
RATETPID	string	15	N		Rate type ID
EXPNDATE	datetime	16	N		Expiration date
EXCHDATE	datetime	16	N		Exchange date
EXGTBDSC	string	30	N		Exchange ID description
EXTBLSRC	string	50	N		Exchange rate source
RATEEXPR	i4	2	N	Default is from setup	Rate expiration:
					0=None
					1=Daily;
					2=Weekly;
					3=Biweekly;
					4=Semimonthly;
					5=Monthly;
					6=Quarterly;
					7=Annually;
					8=Miscellaneous;
					9=None;
DYSTINCR	i4	2	N	Default is from setup	Days to increment; only used when RATEEXPR=8
RATEVARC	number	21	N	0	Rate variance
TRXDTDEF	i4	2	N	Default is from setup	Transaction date default: 0=Exact date;
					1=Next date;
					2=Previous date
RTCLCMTD	i4	2	N	Default is from setup	Rate calculation method: 0=Multiply;
					1=Divide
PRVDSLMT	i4	2	N	0	Previous days limit
DATELMTS	i4	2	N	0	Date limits:
					0=Unlimited;
					1=Limited
TIME1	datetime	16	N		Time 1; if not passed in, field used for finding XCHGRATE

Dynamics GP POP workflow

2008-07-10T13:26:00Z

This post describes the POP workflow. It's an 'in process' kind of thing - I'll add as I come across it. If anyone has anything to add please send it...

POs are entered via PURCHASING > PURCHASE ORDER ENTRY, into POP10100 and POP10110

RECEIPTS:
There are two types of receipts, SHIPMENT and SHIPMENT/INVOICE

Shipments (when posted) create a line in POP10500 and lines in POP30300 and POP30310

Shipment/Invoices (when posted)...