How to find what Receipt Layer was affected by the Cost Adjustment in Microsoft Dynamics GP

View products that this article applies to.

SYMPTOM

How to find what receipt layer was affected by the cost adjustment in Microsoft Dynamics GP

Hopefully, you find this article useful for determining the receipt layers that were affected by a cost adjustment and how to update the exact layer that was affected if you didn’t mean to or did it wrong.

The below information taken from this BLOG. (Refer to the blog article for screenprints.)

↑ Back to the top

RESOLUTION

I would like to go over how to find what receipt layer was affected by your system generated Cost Adjustment. Some customers have wanted to know how to find this information, so they can go back and adjust the layer back to the original cost due to a mistake that was made. So, with this article I’ll explains how to find the receipt layer that was affected as well as how to adjust the receipt layer back if you choose to do so.

Typically, a journal entry is created with a 'GLTRX' prefixed batch and when you drill down on the Source Document you will receive the following message “Transaction history does not exist for this transaction.” This can make hard to determine what exact receipt layer this cost adjustment affected. In the Reference field you will find what document caused the cost adjustment but not the receiving layer affected. The following article goes through why these Cost Adjustments are created.

https://support.microsoft.com/en-US/help/2448193

Note: You would have to have the Historical Inventory Trial Balance Installed, running and recording information in the SEE30303 table before you can use this method to identify the receipt layer that was affected by the cost adjustment.

See the following article on how to do this. It also goes over why to use this report as well:https://community.dynamics.com/gp/b/dynamicsgp/archive/2017/04/04/why-to-use-the-historical-inventory-trial-balance-report

Additionally, you will need access to SQL Server Management Studios with the ability to run select statements. (Read permissions)

Next, you will want to note the Transaction Source (TRXSORCE) or Journal Entry (JRNENTRY) of the cost adjustment, so you can enter it in one of the following scripts which will pull the Item Number and what Receipt Number it was on. Also, if this layer has been depleted the document that consumed it will be in the DOCNUMBR column. You can choose what option you want to use. For example, the TRXSORCE is going to start with GLTRX ending in a number and you will want to enter in place of the xxx on the first script.

SELECT DOCNUMBR, RCPTNMBR1, * FROM SEE30303 WHERE TRXSORCE = 'xxx'

SELECT DOCNUMBR, RCPTNMBR1, * FROM SEE30303 WHERE JRNENTRY = 'xxx'

You can get the Journal Entry Number or Transaction Source from Financial >> Inquiry >> Financial >> Journal Entry Inquiry.

When you run the script, look at the RCPTNMBR1 column for the receipt that brought the Inventory in.

Next, go to the Purchase Receipts Inquiry (Inventory >> Inquiry >> Receipts) to drill down in the Cost Adjustment using the Receipt Number and the Site ID (LOCNCODE field) found in the SEE30303.

Now, that you found the receipt layer and determined it was Invoiced incorrectly you can go to the Inventory Adjust Costs tool (Inventory >> Utilities >> Adjust Costs) and adjust it to your desired cost. Note, adjusting the layer will affect any layer related such as transfers and Sales.

In this situation I received 1 quantity at $1.00 and sold it at that cost (screenprint in blog article). Then I invoiced receipt layer for $1.50 accidentally (should have been $1.00) which created the cost adjustment. I now then switch the $1.50 to $1.00 and then process it. GP then will output a posting journal like this below to show you the new cost for the Subledger and a new Journal Entry will be created for the GL as well

If you want to drill down on the Document Number that depleted the layer go to Item Transaction Inquiry. Or you can go to an Inquiry respective to what type of outflow it is such a Sales Inquiries.

(The above information taken from this BLOG and includes screenprints.)

↑ Back to the top