Wednesday, September 16, 2009

What do those strage reference codes in GL mean?

The following applies to inventory items with a valuation method of Average Perpetual, LIFO Perpetual, or FIFO Perpetual items.

As of the release of Dynamics GP 9.0 the system will automatically generate General Ledger adjustment entries for situations where an item was sold or consumed from inventory, but its cost was later changed.

In earlier versions of GP, adjustments to Inventory and COGS needed to be entered manually to correct the accounts used by the transactions that sold or consumed the items. As of Dynamics GP 9.0, those adjustments will now be automatically generated. You will see different codes in GL (MCTERCT for example) depending on the type of transactions entered and timing of the transactions.

Unfortunately at this time there isn't a document describing the codes for Manufacturing. However, here are some codes based on various sources of info:

1. MCTERCT - If the items were issued in the Component Transaction Entry window and then the invoice is completed the adjustment will have a prefix of MCTERCT

2. MRCTRCV - If the items were issued in Mo Receipt Entry (they are backflushed) and then the invoice is complete the adjustment will have a prefix of MRCTRCV.

3. MCLSRCV - If the items were issued in the MO Close process (the MO was partially received and more backflushed items were issued during the close) and then the invoice is completed the adjustment will have a prefix of MCLSRCV.

As you can see the naming conventions follow a certain pattern. MCTE transactions come from the Component Transaction Entry window. MCLS transactions come from the MO Close process. MRCT transactions come from the MO Receipt entry window.Here is a complete list of the origins which may be used on Journal Entries that result from a change in average cost that affects sold receipt layers.

The following values will be used at the beginning of the Reference field for the specified originating document types:

1. BOM – Assembly Transaction
2. INV – invoice from the Invoicing module
3. IVT – inventory transfer
4. IVA – inventory adjustment
5. IVV – inventory variance
6. SALES – sales invoice from Sales Order Processing
7. PRTN – purchase return
8. MCTE – for a transaction that originated in Manufacturing Component Transaction Entry
9. MRCT – manufacturing receipt
10. MCLS – manufacturing close, including regular close and Quick MO
11. STCK – stock count variance
12. FSSC – field service Service Call
13. FSRMA – field service RMA
14. FSRTV – field service RTV
15. FSWO – field service Work Order
16. PA – project accounting
17. POP – close a PO line in Edit PO Status
18. RECON – created by Inventory Reconcile
19. CONV - created by an upgrade conversion
20. MCTERCT - If the items were issued in the Component Transaction Entry window and then the invoice is completed the adjustment will have a prefix of MCTERCT

21. MRCTRCV - If the items were issued in Mo Receipt Entry (they are "backflushed") and then the invoice is complete the adjustment will have a prefix of MRCTRCV.

22. MCLSRCV - If the items were issued in the MO Close process (the MO was partially received and more “backflushed” items were issued during the close) and then the invoice is completed the adjustment will have a prefix of MCLSRCV.

There is a report you can install to better help determine where the accounts are pulling from. It won’t help for those entries already created in the system, but should provide you with the information related to the GL entries going forward. If you are on SP3 for Microsoft Dynamics GP 10.0 then you can add the following line under the [General] header of the Dex.ini file of your GP code folders:

RevalJEInDetail=TRUE

When you post a transaction, be sure you are printing the Cost Variance journals. Doing so will cause the PRUD (Purchase Receipt Update Detail) reports to print. This report will give a break down of any/all transactions that make up a particular variance transaction. If you do this then any of the cost adjustment transactions that will be written to the GL will also include the following information in these fields (GL20000):

ORCTRNUM (Originating Control Number) - this will now hold the original document number of the decrease item transaction affected by the cost variance adjustment.

ORMSTRID (Originating Master ID) - this will hold the item number that was revalued on the decrease item transaction.

ORDOCNUM (Originating Document Number) - this will now hold the original receipt number from the Inventory Purchase Receipt (IV10200) table that had a revaluation and forced the cost adjustment.

ORMSTRNM (Originating Master Number) - this will now hold the text value of "IV Ripple Transaction" to make it easier for users to identify the cost adjustments flowing into the GL.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

4 comments:

Anonymous said...

Is there anything for users on SP2? I cannot find the origin for an entry MCTEADJ and am responsible for posting the entry. I'd like to see it's origin.

Mariano Gomez said...

Since MCTE is used for a transaction that originated in Manufacturing Component Transaction Entry, I have to imagine that MCTEADJ refers to adjustments to a Manufacturing Component Transaction Entry transaction.

MG.-
Mariano Gomez, MVP

_H_ said...

Can this be disabled in any way. We run numerous kitchens and our daily usage is adjusted out. As a result we have hundreds of IVA entries in the GL that we can't account for.

Is there somewhere that explains this further?

We are on v10 SP2, and no plans to upgrade, so is there anything we can implement to catch/view this in future?

Anonymous said...

Wow! This RevalJEInDetail=TRUE should be enabled by default. Love it - thanks Mario.