November 21, 2012

Default Item Class

I'm studying to take the GP10 Manufacturing certification exam and it's amazing how much I don't know (or have forgotten) about GP.  Here's an item that jumped out at me last night as I was reading through Item Setup processes:


HINT:
Set up the first class with the most common entries and select this class

as the default class. By selecting the Default option, the information defined for
this class automatically appears as the default for each subsequent class
created. This makes data entry faster if similar entries are required in many
classes. Only one default item class can be saved.

Good to know!

Happy Thanksgiving everyone.

 

 

November 7, 2012

Transaction Prefixes in Cost Adjustment Batch

Wonder what the prefixes mean in Cost Adjustment batches?  Well, wonder no more!  The following is a list of the prefixes you would see in the Reference field of a transaction in a cost adjustment (GLTRX) batch and a description of why that prefix would be used. The Reference field can be found in the Transaction Entry, Detail Inquiry, and Journal Entry Inquiry windows.

a. BOM – This comes from a Bill of Materials transaction. For example if a BOM Assembly transaction consumed an item from inventory and the cost was later changed due to a POP purchase price variance (PPV) or an average cost ripple, you would see this reference.

b. INV – This comes from an Invoice transaction created from the Invoicing module. For example if an Invoice transaction (in Invoicing) consumed an item from inventory and the cost was later changed due to a Purchase Order Processing PPV or an average cost ripple you would see this reference.

c. IVT – This comes from an Inventory Transfer Transaction. For example if an item was consumed via the Item Transfer and the costs were later changed due to a PPV or an average cost ripple you would see this reference.

d. IVA – This comes from an Inventory Adjustment transaction. For example if a decrease Inventory Adjustment transaction consumed an item from inventory and the cost was later changed due to a PPV on an invoice match or an average cost ripple you would see this reference.

e. IVV – This comes from an Inventory Variance transaction. For example if a decrease Inventory Variance transaction consumed an item from inventory and the cost was later changed due to a PPV on an invoice match or an average cost ripple you would see this reference.

f. SALES – This comes from a Sales Order Processing Invoice transaction. For example if a Sales Invoice consumed an item from inventory and the cost was later changed due to a PPV on an invoice match or an average cost ripple you would see this reference.

g. PRTN – This comes from a Purchase Order Processing return transaction where doing the return changes the cost of the item.

h. MCTE – This comes from a Manufacturing Component Transaction. For example if an item was issued (consumed) in the Component Transaction Entry window and the cost was later changed due to a PPV or an average cost ripple you would see this reference.

i. MRCT – This comes from a Manufacturing Receipt Transaction. For example if an item was backflushed and consumed in the Manufacturing Receipt Entry window and the cost was later changed due to a PPV or an average cost ripple you would see this reference.

j. MCLS –This comes from Closing a Manufacturing order via the Close process or during a Quick MO (quick MOs are automatically closed). For example if a user closes an MO and there are items that are set to backflush (consumed) and the cost was later changed due to a PPV or an average cost ripple you would see this reference.

k. STCK – This comes from Item Stock Count Variance transaction. For example if a Stock count adjustment consumed an item from inventory and the cost was later changed due to a PPV or an average cost ripple, you would see this reference.

l. FSSC – This comes from selling a Part on a Service Call. For example, an Item was Received into Inventory at one cost and the cost was later changed due to an Invoice Match you would see this reference.

m. FSRMA – This comes from an RMA. For example, you have a quantity of an item at one cost. You create a Credit RMA and receive the item in. You then Scrap the item ( which removes the one already in your inventory ) and later the cost of that item changed due to an Invoice Match you would see this reference.

n. FSRTV – This comes from an RTV. For example, you create a Credit RTV. You Ship an item at one cost and the cost was later changed due to an Invoice Match you would see this reference.

o. FSWO – This comes from using a Part on a Depot Work Order. For example, you create a WO and Use an item from the Parts Information window at one cost and the cost was later changed due to an Invoice Match you would see this reference.

p. PA – This comes from a Project Accounting transaction. For example if a PA Inventory Transfer consumed an item from inventory and the cost was later changed due to a PPV on an invoice match or an average cost ripple, you would see this reference.

q. POP –- This comes from a Purchase Order Processing shipment receipt. For example if an item was consumed through an override in any module and later the shipment was brought in at a different cost than it was when it was consumed (overrode), you would see this reference

r. RECON – You would see this reference if the outflow being revalued was created by the Inventory Reconcile Utility. One reason IV Reconcile would need to create an outflow record is if there are not enough quantities in the IV10201 to support the quantity sold in the IV10200.

s. CONV – You would see this reference if the outflow being revalued was created by the upgrade. The upgrade from an older version of Microsoft Dynamics GP to 9, 10 or GP2010 may need to create an outflow if a receipt record was partially sold at the time of the conversion.

t. PRCT- You would see this reference if the item was overridden on an In-Transit Transfer transaction and then later brought in at a different cost.