Page 1 of 2612345678910...2025...Last »

Mahmoud Al Saadi – Dynamics GP MVP!!

 

I am proud to inform you that my colleague “Mahmoud M. Al Saadi” is now Dynamics GP MVP!

Well deserved and well expected!


Regards,


Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
http://www.di.jo

View post:
Mahmoud Al Saadi – Dynamics GP MVP!!

April 1, 2015 ·  · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 27

Setup information for Electronic Reconcile Format Configurator

Hi everyone,
Found a very important article on Format Configurator in Electronic Bank Reconciliation
Cheers..
This article contains information about setting up the Electronic Reconcile Configurator.

MORE INFORMATION
General Setup for Electronic Reconcile Format Configurator

The process of setting up the Format Configurator in Electronic Reconcile is very lengthy and the following detailed steps will help to make this setup easier. Before setting up the Format Configurator, you must have a printed copy of the download file format specifications from your bank. Because bank formats vary greatly, you must contact your bank and request these specifications for the file format. The format specifications will contain details about each field being downloaded and values of all relevant codes for the bank. This information is necessary to be able to setup the Format Configurator as each bank is different and there is no standard format to enter.

Electronic Reconcile Format Configurator (Routines | Financial | Electronic Reconcile | Configurator):

Section 1 – Enter Format Information

Bank Format - The Bank Format field is an identifier for your format. Enter a unique name for this format, but typically this is the name of your Bank.

Description - This is a required field. Enter an additional description for the Bank Format.

File Format - Follow the steps below for the version you are using:

 -Microsoft Dynamics GP 2010 and prior versions – The File Format field can be selected from the drop-down list as Fixed Field, Comma Delimited, or Tab Delimited. The bank determines which option from the list that you will select. Therefore, you must contact them if the format specifications do not state the format to use.

-Microsoft Dynamics GP 2013 - The File Format field has a choice of BAI or User Defined. If you are using the Bank Administration Institute format, select BAI. For all other formats/banks, select User Defined. In the File Type field, you can choose Fixed Field, Comma Delimited or Tab Delimited as specified by your bank.

Uses Status Codes option is marked only if your bank uses Status Codes to additionally define Transaction Codes. This information is also determined by each bank. Therefore, if the format specifications do not state if your bank uses Status Codes, you must contact the bank. (This is not used very often.)

Record Type Identifier – The Record Type Identifier will contain Start Position and End Position fields if you are using the Fixed Field format and a Field Number field if you are using Comma Delimited or Tab Delimited file formats. This will be where the system should look in the line to determine what type of line (header, footer or detail) it is. If the bank doesn’t use a record type code, then you can improvise by selecting a fixed value in the file.

-Fixed Field – Enter the starting and ending position of the field that will contain the value for the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

-Comma Delimited or Tab Delimited – Enter the number of the field that contains the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

Save the Format after Section 1 has been completed before moving on to Section 2 of the Electronic Reconcile Format Configurator window.

Section 2 – Enter Record Types
Note You will only have to define the Record Types that are relevant to Electronic Reconcile. If a section is labeled as optional on the bank specifications, you do not have to set it up in the Format Configurator. The Detail Record Type is always a required section in a bank’s specifications.

Bank ID - The Bank ID will default in with the Bank Format from section 1 as soon as you tab into the Record Type field in the second column. This field cannot be changed or edited.

Record Type - The Record Type field can be selected from the drop-down list as Header, Detail, or Footer. All bank formats will require a Detail Record Type, but the header and footer Record Types may be optional. You may only setup each of the Record Types one time as multiple headers or footers are not available.

Record Type Code from Bank – The Record Type Code from Bank field is defined in your bank’s specifications. This field must be a unique and constant identifier for the format to match the information in the Detail Record Type. This is the most important field in setting up the Format Configurator to correctly match the download file with the reconciliation.  (So the Record Type Identifier will tell the system which column to look in to see what type of row it is, and then to look at the value in Record Type Code from Bank field to read if it is a header, detail or footer line.)
# of fields – The number of fields indicates how many fields are to be defined in Section 3. Enter the number of fields contained on the line for the Record Type being defined. This information must be entered for each Record Type that is required in the bank’s specifications.

Section 3 – Enter Field Information

When you click on a Record Type in Section 2, the corresponding number of fields will display in Section 3.

Record Type – The Record Type field in the left-most column of Section 3 will default in when you select a Record Type in Section 2.

# – The number field will default in with the number of fields that you entered in Section 2.

Field Type – The Field Type field is used to define each of the relevant fields for each of the Record Types. Select the Field Type from the drop-down list that includes options for Accounts, Dates, and amounts. If the exact name of your field from your bank’s specifications does not appear in the list, you may have to either select an option that is similar or use the Filler/Ignore option. Again, you only need to define the relevant fields, most importantly: Account Numbers, Check Numbers, Check Dates, Check amounts, Transaction Codes, Record Type Codes, etc.

Note Just as with Record Types, you will only have to define the fields that are relevant to Electronic Reconcile. If there is a field on the bank’s specifications that cannot be defined with an existing Record Type or does not have to be defined, use the Filler/Ignore option.

Format - The Format field defines the type of output format for certain fields. Formats only have to be set for Field Types that contain dates or a currency amount, as these are the only options for Formats. There are no options for text or string. Therefore, if the field is not a date or a currency amount, just leave the Format field blank. The From and To fields are used to enter the character positions of the field. Enter the starting and ending character position for each field in each Record Type. The From and To fields must be entered if using the Fixed Field File Format, so if you are using Tab Delimited or Comma Delimited File Formats you can leave these fields as zero.

Transaction Codes (Codes Entry – Transaction Codes Entry)

While still in the Electronic Reconcile Format Configurator window, go in the Transaction Codes Entry window through the path listed above in the top Menu Bar. If you have not defined the Transaction codes, you will get the message “Record Type match not found” on the error report.

Transaction Codes identify the type of transaction that each Detail line represents. Electronic Reconcile requires a Transaction Code in a configured Bank Format to work correctly. You must have Transaction Codes or Record Type Codes defined to use Electronic Reconcile. These codes must come from the bank and must be listed on the bank’s specifications.

Transaction Type – The Transaction Type field is used to define each of the different types of transactions that appear on your bank’s specifications. Select a Transaction Type from the list to match or to closely match your bank’s specifications. Note that the options in the list are the only currently supported types. At this time, the two options that will match using Electronic Reconcile are Check Paid and Deposit Cleared.

Note: In Microsoft Dynamics GP 2013, options for Transfer Credit and Transfer Debit have also been added and will electronically match in Electronic Reconcile. However, you must enter the Bank Transaction Type Codes in as defined by your bank. Additional functionality in Microsoft Dynamics GP 2013 is also that you can have multiple Transaction Type Codes for each Transaction Type.

Transaction Type Code – The Transaction Type Code field is used to enter the value for each Transaction Type and this value is given to you as part of the file specifications from your bank. Enter the Transaction Type Code value that corresponds to the selected Transaction Type. This information must come from the bank and cannot be improvised if it is not available on the bank’s specifications.

G/L Account - The G/L Account field is available only for the following Transaction Types: Interest Income, Other Income, Other Expense, and Service Charge. Enter the G/L Account Number of a General Ledger Posting Account for the adjustment that will be generated. Electronic Reconcile will automatically create adjustments for these transaction types if they appear in the downloaded file from your bank.

Note The Interest Income, Other Income, Other Expense, and Service Charge transaction types do not electronically match, and instead will create Adjustment entries on the reconciliation. (Click the Adjustments button on the Select Bank Transactions window).

Account Description – The Account Description field will default in with the description of the account from General Ledger and is not editable.

Distribution Reference – The Distribution Reference field can be used to enter an additional reference for the adjustment that will be made. You can enter a Distribution Reference if you want, but it is not a required field.

Document Type - The Document Type field will default in with the Transaction Type that you selected at the top of the Transaction Code Entry window: Interest Income, Other Income, Other Expense, or Service Charge. This field cannot be changed unless you go back and change the Transaction Type field.

Define Status Codes - The Define Status Codes button only becomes available if you have marked the Uses Status Codes option in the Electronic Reconcile Format Configurator window. Define Status Codes is only available for certain Transaction Types: Check Paid and Deposit Cleared. After selecting one of these 2 Transaction Types, you would select the Define Status Codes button to go into the Status Codes Entry window. Here you would select: Paid Check, Check Reversal, Stop Pay, or Stop Pay Reversal for the Status Type and enter the corresponding Status Code from your bank’s specifications. Again this information has to come from your bank and cannot be improvised or Electronic Reconcile will not work correctly.

Special notes to remember when setting up Electronic Reconcile:

  • You must have a printout of the file format specifications from your bank before setting up the Electronic Reconcile Format Configurator.
  • Every bank is different. Therefore, you cannot follow one standard format for all banks.
  • If you open the .TXT or .CSV file with Notepad, the system will typically not read any information after position 245. So make sure all the required fields to be mapped are in the first part of the line if your lines are more than 245 characters. The information after 245 will be read as a new line and appear on the Unprocessed Data Record error report as “Record Type match not found: Record Type = ” because there isn’t one. This would be acceptable if no fields after position 245 are not needed. If there are fields that are needed, you will need to contact your bank to see if they are able to reconfigure the file to be smaller and not exceed 245 characters.
  • The Electronic Reconcile Format Configurator only needs to be setup once when first starting to use Electronic Reconcile, and then you just keep downloading .TXT or .CSV files from the bank to match this Format Configurator.
  • The following fields must be present in your bank format: Transaction Code, Account Number, Check/Serial Number, Transaction Amount, Record Type Code, and the Bank Cleared Date. If your format uses Status Codes, then the Transaction Status Code must also be present in the configuration.
  • If you have gone through all of the Electronic Reconcile process and no transactions are marked off as cleared in your Bank Reconciliation module, most likely something is not set up correctly in the Electronic Reconcile Format Configurator. The most common error message that will be received is a “Record Type Match Not Found” error on the Unprocessed Records report that prints after trying to download.
  • If you try to re-download after you have already downloaded the .txt file from the bank, you will receive “Duplicate” error messages because the system sees the transactions as duplicates instead of just downloading new transactions.
  • If you try to delete a Reconcile and re-enter the information after you have already downloaded the .txt file from the bank, you will receive “Duplicate” error messages because the system sees the transactions as duplicates.
  • Make sure the Bank Account Number is unique for the checkbook that is set up with Electronic Reconcile. If the Bank Account Number is set up with a different checkbook, Electronic Reconcile will not be able to match the downloaded transactions and you will receive a message stating that the Bank Account Number is not set up.
  • In the Codes Entry window of the configurator, the types that will automatically match are: Check Paid, Deposit Cleared, Transfer Debit and Transfer Credit.
  • If you enter an increase adjustment or a decrease adjustment in the Reconcile Bank Adjustments window, the following adjustment types create an adjustment transaction in the Reconciliation Bank Adjustments window: (For example, ‘interest’ or a ‘misc fee’ on your bank statement would not be in GP (so nothing to match to), so you need the system to book the adjustment/journal entry in GP for these types.)
    • Interest Income
    • Other Income
    • Other Expense
    • Service Charge
  • If you enter an increase adjustment, a decrease adjustment, or a withdrawal in the Bank Transaction Entry window, you are prompted to manually mark the adjustment. When you receive this message, you must manually mark the records in the configurator file.
  • Checks will be matched by the Check Amount and Check Number. Deposits will be matched by the Deposit Amount and Deposit Date (within a default 8 day range, but you can override that when prompted to be a different day range.) 
  • The Bank Cleared Date can affect the matching process. GP will only clear checks in which the Bank Cleared date is AFTER the Check Issue Date in GP. GP would not clear a check on a date prior to the date it was actually issued in GP.  
  • GP will ignore any leading zeroes on a check in the matching process and in fact, will strip them off the check number when importing. Leading zeroes will not affect the matching process for the check number. GP is able to match the check number, regardless of any leading zeroes.

This article was TechKnowledge Document ID: 19396



Applies to
  • Microsoft Dynamics GP 2010
  • Electronic Reconciliation Management, when used with:
    • Microsoft Dynamics GP 10.0
    • Microsoft Dynamics GP 9.0
    • Microsoft Business Solutions–Great Plains 8.0
    • Microsoft Business Solutions–Great Plains 7.5
    • Microsoft Great Plains Dynamics 7.0
    • Microsoft Great Plains eEnterprise 7.0
    • Great Plains Dynamics 6.0
    • Great Plains eEnterprise 6.0

Read more here:
Setup information for Electronic Reconcile Format Configurator

March 25, 2015 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 26

Dynamics GP Analysis Cubes Error: The column "INTERID" cannot be processed because more than one code page (1252 and 1256) are specified for…

 

I am sure if were in the non-English countries, you might need to use code pages other than CP1252 to support your characters, and 1256 would your right choice for example if you been in Arab speaking countries, but this makes a problem when it comes to Analysis Cubes installation.

Once you install the Analysis Cubes and finish all wizard issues you feel like things are becoming easy and will proceed to start your job getting your cubes inititalized and then you will be start getting below errors:

Results to CompanyMaster Task OLE DB Destination [22]    
Description: The column “INTERID” cannot be processed because more than one code page (1252 and 1256) are specified for it. 
End Error 

Error: 2015-03-23 10:18:58.26    
Code: 0xC02020F4    
Source: Copy Data from Results to CompanyMaster Task OLE DB Destination [22]    
Description: The column “CMPNYNAM” cannot be processed because more than one code page (1252 and 1256) are specified for it. 
End Error 

Warning: 2015-03-23 10:18:58.26    
Code: 0x800470C8    
Source: Copy Data from Results to CompanyMaster Task OLE DB Destination [22]    
Description: The external columns for component “OLE DB Destination” (22) are out of synchronization with the data source columns. The external column “CompanyID” needs to be updated.  The external column “CompanyName” needs to be updated. 
End Warning 

Error: 2015-03-23 10:18:58.26    
Code: 0xC004706B    
Source: Copy Data from Results to CompanyMaster Task SSIS.Pipeline    
Description: “component “OLE DB Destination” (22)” failed validation and returned validation status “VS_ISBROKEN”. 
End Error 

Progress: 2015-03-23 10:18:58.26    
Source: Copy Data from Results to CompanyMaster Task     
Validating: 50% complete 
End Progress 

Error: 2015-03-23 10:18:58.26    
Code: 0xC004700C    
Source: Copy Data from Results to CompanyMaster Task SSIS.Pipeline    
Description: One or more component failed validation. 
End Error 

Error: 2015-03-23 10:18:58.26    
Code: 0xC0024107    
Source: Copy Data from Results to CompanyMaster Task     
Description: There were errors during task validation. 
End Error 

Error: 2015-03-23 10:18:58.26    
Code: 0xC00220E4    
Source: Run Company     
Description: Error 0xC0012050 while preparing to load the package. Package failed validation from the ExecutePackage task. The package cannot run.  . 
End Error 

Warning: 2015-03-23 10:18:58.26    
Code: 0x80019002    
Source: DynamicsGP_TWO_to_DynamicsGPWarehouse_Package_Master     
Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. 
The Execution method succeeded, but the number of errors raised (6) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.  End Warning  DTExec: The package execution returned DTSER_FAILURE (1). 
Started:  10:18:57 AM 
Finished: 10:18:58 AM 
Elapsed:  0.842 seconds. 
The package execution failed. 
The step failed.

Obviously it is all about the first error, different code pages are exist and therefore your data cannot be copied from the production database to the data warehouse, going further with investigations I been able to get around this error by unifying the code page in my packages, and this is by simply allowing a flag in cubes SSIS packages to use the default code page “AlwaysUseDefaultCodePage” to be “True” and your issues will no longer be shown:

image

Now the challenge here you need to extract the packages from the MSDB store, to your Visual Studio and perform this change, save your package and re-import this back to your MSDB, this will need to be done to the following packages:

DynamicsGP_DynamicsGPWarehouse_FiscalPeriods.dtsx
DynamicsGP_DynamicsGPWarehouse_GLBudgets.dtsx
DynamicsGP_DynamicsGPWarehouse_GLMDAGroups.dtsx
DynamicsGP_DynamicsGPWarehouse_GLMDATransactions.dtsx
DynamicsGP_DynamicsGPWarehouse_GLTransactions.dtsx
DynamicsGP_DynamicsGPWarehouse_ItemCurrentQuantity.dtsx
DynamicsGP_DynamicsGPWarehouse_ItemMaster.dtsx
DynamicsGP_DynamicsGPWarehouse_PendingPurchaseOrders.dtsx
DynamicsGP_DynamicsGPWarehouse_PendingSalesOrders.dtsx
DynamicsGP_DynamicsGPWarehouse_PurchaseOrderDetail.dtsx
DynamicsGP_DynamicsGPWarehouse_SalesDetail.dtsx
DynamicsGP_DynamicsGPWarehouse_SalesPerson.dtsx
DynamicsGP_DynamicsGPWarehouse_SalesTerritory.dtsx
DynamicsGP_DynamicsGPWarehouse_TotalExpense.dtsx
DynamicsGP_DynamicsGPWarehouse_TotalRevenue.dtsx
DynamicsGP_DynamicsGPWarehouse_AgingDetails.dtsx
DynamicsGP_DynamicsGPWarehouse_AgingPeriodAmounts.dtsx
DynamicsGP_DynamicsGPWarehouse_AgingPeriods.dtsx
DynamicsGP_DynamicsGPWarehouse_CheckbookRegister.dtsx
DynamicsGP_DynamicsGPWarehouse_CompanyMaster.dtsx

Luckily, I found a script that makes this easier, it allows you to extract all your SSIS packages from MSDB to file system instead of pulling these one by one, it will save the packages to a folder on your “C:” drive, and all what you need to do then is copying these to your visual studio and start changing the flag, below the script:

;
WITH FOLDERS AS
(
    — Capture root node
    SELECT
        cast(PF.foldername AS varchar(max)) AS FolderPath
    ,   PF.folderid
    ,   PF.parentfolderid
    ,   PF.foldername
    FROM
        msdb.dbo.sysssispackagefolders PF
    WHERE
        PF.parentfolderid IS NULL

    — build recursive hierarchy
    UNION ALL
    SELECT
        cast(F.FolderPath + ” + PF.foldername AS varchar(max)) AS FolderPath
    ,   PF.folderid
    ,   PF.parentfolderid
    ,   PF.foldername
    FROM
        msdb.dbo.sysssispackagefolders PF
        INNER JOIN
            FOLDERS F
            ON F.folderid = PF.parentfolderid
)
,   PACKAGES AS
(
    — pull information about stored SSIS packages
    SELECT
        P.name AS PackageName
    ,   P.id AS PackageId
    ,   P.description as PackageDescription
    ,   P.folderid
    ,   P.packageFormat
    ,   P.packageType
    ,   P.vermajor
    ,   P.verminor
    ,   P.verbuild
    ,   suser_sname(P.ownersid) AS ownername
    FROM
        msdb.dbo.sysssispackages P
)
SELECT
    — assumes default instance and localhost
    — use serverproperty(‘servername’) and serverproperty(‘instancename’)
    — if you need to really make this generic
    ‘dtutil /sourceserver localhost /SQL “‘+ F.FolderPath + ” + P.PackageName + ‘” /copy file;”C:Packages’ + P.PackageName +’.dtsx”‘ AS cmd
FROM
    FOLDERS F
    INNER JOIN
        PACKAGES P
        ON P.folderid = F.folderid
– uncomment this if you want to filter out the
– native Data Collector packages
– WHERE
–     F.FolderPath <> ‘Data Collector’

Once you run this on your SQL Server the result will be set of commands like the below, run these commands using CMD and go to find these in your C:Packages folder:

dtutil /sourceserver SERVERNAME /SQL “DynamicsGPWarehousePackage” /copy file;”C:PackagesPackage.dtsx”

Execute these over CMD and find your files on C: drive, select all and paste the files inside your Visual Studio and start your modifications, once done import back updated packages to SQL Integration Services one by one and rerun your job.

Hope that this helps.


Regards,


Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
http://www.di.jo

Visit link:
Dynamics GP Analysis Cubes Error: The column "INTERID" cannot be processed because more than one code page (1252 and 1256) are specified for…

March 23, 2015 ·  · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 28

CBM Cash Receipt Customer GL Posting Account Error

A user reported this issue when he tried to enter a cash receipt in CBM module. Following error message prevented him from continuing further.

Screen Shot 2015-02-23 at 3.10.24 PM

This error was confirmed to be happening only for one particular customer record. For all other customers, it worked.

We basically do not have posting accounts setup for each customer or customer class. So it is absolutely no way due to missing posting accounts. Several minutes later, decided to compare customer records between this particular customer and one other customer that’s working.

REASON: Customer Class ID for this customer record was wrong and was not part of the list of customer classes that we have setup on our company. Because this class ID was wrong, posting accounts validation stopped right there and threw a message that was totally irrelevant to actual reason.

RESOLUTION: I changed the customer class ID for this customer with an existing one. User could then enter a cash receipt in CBM.

Troubleshooting issues successfully is probably the best way to end a business day!

VAIDY

Filed under: #MSDYNGP, Cashbook, CBM, Troubleshooting

Continue reading here:
CBM Cash Receipt Customer GL Posting Account Error

February 23, 2015 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 53

Dynamics GP 2015 – Printing Arabic Text

If you are planning to upgrade to GP 2015 and currently having Arabic text in your database need to be printed using report writer, make sure NOT TO UPGRADE to GP 2015.

Normally for printing Arabic text in report writer, if your keyboard was language the text will be displayed as rubbish data as below:

In order to get this printed properly, we used to switch the keyboard language to Arabic and the text will back to normal as below:

However for GP 2015, the system will automatically switch the keyboard language to English upon the generation of the report, and unfortunately the same switch is occurred upon hitting the print button, therefore the Arabic text will never be printed in Arabic and customers will start nagging!

Hope that Microsoft could resolve this soon!


Regards,


Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
http://www.di.jo

See original article:
Dynamics GP 2015 – Printing Arabic Text

February 1, 2015 ·  · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 62

Microsoft Dynamics GP 2015 Documentation & Resources

In my opinion, Microsoft Dynamics GP team might have hurried the release of GP 2015 RTM.

Think about this. You install GP 2015 and the user manuals that comes with that are GP 2013 R2 manuals. For instance, Visual Studio Tools manual that we get after installing the tool is of version GP2013 R2, as shown below:

Screen Shot 2015-01-04 at 4.22.25 PM

Not just this manual, there are also other manuals that are basically for GP 2013 R2 but somehow got shipped with GP 2015 installation media.

Where can we get the latest manuals then? Answer is this link: Documentation and resources for Microsoft Dynamics GP 2015 and 2013.

First section on this post would be directing you to GP 2015 manuals.

QUICK UPDATE #1: I was wrong. Even this link seems to be not having *all* manuals. So probably the new ones are still under construction.

VAIDY

Filed under: #MSDYNGP, Documentation, Dynamics GP 2015, GP 2015, GP2015, Microsoft Dynamics GP, User Manuals

Read this article:
Microsoft Dynamics GP 2015 Documentation & Resources

January 4, 2015 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 135

Average Days To Pay Calculation – History & Open (SQL Script)

In my previous post, Average Days to Pay Calculation (SQL Code), I had provided a SQL stored procedure that calculates a customer’s ADTP for a given point of time (between two dates). While this was perfect, it does not include fully applied but open invoices.

Some of the readers (particularly Tim and Steve Pena) requested to amend the script to consider open invoices that are fully applied. An invoice remains open even after fully applied only when we do not run paid transaction removal (PTR). I wanted to work on this script as soon as possible, but somehow I could not.

Better late than never, isn’t it?

Please find the link below to download the SQL procedure that calculates a customer’s ADTP for a given point of time, but looks at both history (RM30101) and open (RM20101) tables, take invoices that satisfy following criteria:

  • Invoices that are fully applied.
    • If invoices are in history table, by default, current transaction amount would be zero.
    • If invoices are in open table, then take those invoices whose receivable outstanding amount is zero.
  • Invoices that are not voided.
  • Invoices that have a document amount, meaning non-zero.

I have verified this script against some sample customers for whom, invoices were either in history (RM30101) or in open (RM20101) or in both.

As always, feedbacks are welcome.

RM_AverageDaysToPay.sql

VAIDY

Filed under: #MSDYNGP, ADTP, Average Days To Pay, GP, Microsoft Dynamics GP, Receivables, RM, SQL Programming, SQL Queries, T-SQL

Read the original:
Average Days To Pay Calculation – History & Open (SQL Script)

December 11, 2014 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 80