Home » Listing Details
Top Websites
  1. Mark Polino's DynamicAccounting.net
    Over 3700 resources listed.
  2. Developing for Dynamics GP - By David Musgrave and the MS GP Dev Support Team
    Over 700 resources listed.
  3. Mariano Gomez at The Dynamics GP Blogster
    Over 600 resources listed.
  4. Mohammad Daoud's Dynamics GP Blog
    Over 400 resources listed.
  5. Microsoft Dynamics Partner Community Blog
    Over 400 resources listed.
  6. Dynamics GP Help
    Over 400 resources listed.
  7. Vaidy Mohan at Dynamics GP - Learn & Discuss
    Over 400 resources listed.
  8. Christina Phillips, Steve Endow & Lorren Zemke at Dynamics GP Land
    Over 300 resources listed.
  9. Frank Hamelly at GP2theMax
    Over 200 resources listed.
  10. About Dynamics, Development and Life
    Over 200 resources listed.
  11. eOne Business Solutions Blog
    Over 200 resources listed.
  12. Inside Microsoft Dynamics GP Official Blog
    Over 200 resources listed.
  13. VS Tools Forum
    Over 100 resources listed.
    Your Resource for Visual Studio Tools for Dynamics GP
  14. Inside Microsoft Dynamics GP Official Blog
    Over 100 resources listed.
  15. Janakiram M.P. at DynamicsBlogger
    Over 100 resources listed.
  16. Victoria Yudin's Dynamics GP Website
    Over 100 resources listed.
    Victoria Yudin
  17. Catherine Eibner MBS Developer Evangelist
    Over 100 resources listed.
  18. Dynamics CPM
    Over 100 resources listed.
  19. Sivakumar Venkataraman at Interesting Findings & Knowledge Sharing
    Over 100 resources listed.
  20. Dynamics Small Business
    Over 100 resources listed.
  21. Belinda, The GP CSI
    Over 100 resources listed.
  22. Rose Business Solutions Blog New
    Over 100 resources listed.
  23. Microsoft Dynamics GP UK Blog
    Over 100 resources listed.
  24. Leslie Vail at Dynamics Confessor Blogspot
    99 resources listed.
  25. Michael Johnson at MBS Guru
    96 resources listed.

ID:11090
Title:What do those strage reference codes in GL mean?
URL:http://dynamicsgpblogster.blogspot.com/2009/09/what-do-those-strage-reference-codes-in.html
Description: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/
Category:TIPS AND TRICKS BY MODULES: GL (General Ledger)
Link Owner:
Date Added:June 17, 2010 06:12:47 PM
Number Hits:2
RatingsAverage rating: (0 votes)
Reviews

No Reviews Yet.

 
GPWindow.com

Developed and presented by
Smith & Allen Consulting, Inc.,
GP specialists since 1991.