NAV.dk = Dynamics NAV = Navision

Microsoft Dynamics NAV Inventory Costing Data Integrity Diagnostic

Baseret på erfaringer fra kostprisproblemer i Microsoft Dynamics NAV har Microsoft lavet et diagnoseværktøj der gennemløber de vigtigste NAV varetabeller for at identificere potentielle data problemer. Denne diagnose har i alt 31 dataintegritets kontroller:

Validation #1: The following records have zero quantity entries in the ILE Table.
Validation #2: Quantity * Remaining Quantity is less than zero in the ILE Table.
Validation #3: Absolute value of (Remaining Quantity) is greater than absolute value of (Quantity).
Validation #4: Quantity must be positive if "Positive" is true (1) and vice versa.
Validation #5: ILE Table Error: Remaining Quantity and Open are not in sync.
Validation #7: ILE Table Error: No Value Entry for the following ILE Entry.
Validation #8: ILE Table Error: Sign on Quantity and "Remaining Quantity" must be the same.
Validation #9: Value Entry Table Error: For every VE there must exist at least one associated ILE or Capacity entry.
Validation #10: A linked "Value Entry" should not have the valuation date 12/31/9999 for a positive entry with "entry type" consumption.(Valid for versions older than 4.0?).
Validation #11: Value Entry Table Error: Valuation Date for Entry types of "Direct Cost", "Indirect Cost", and "Variance" don't match.
Validation #12: ILE - IAE Table Error: Item Ledger Entry and Item Application Entry have differing quantities. For positive ILE entries the ILE.Quantity should equal the sum of IAE entries (grouped by ILE.EntryNo). For negative ILE entries, the absolute value of the ILE.Quantity must be greater than or equal to the absolute value of the sum of IAE entries.
Validation #13: IAE Table Error: The combination of [Item Ledger Entry No], [Inbound Item Entry No], and [Outbound Item Entry No] ocurr more than once.
Validation #14: IAE Table Error: For a positive quantity in IAE, both the [Item ledger Entry No.] and the [Inbound Item Entry No.] should be the same.
Validation #15: IAE Table Error: For a negative quantity in IAE, the [Item ledger Entry No.] and the [Inbound Item Entry No.] should be different.
Validation #16: IAE Table Error: For a negative quantity in IAE, the [Item ledger Entry No.] and the [Outbound Item Entry No.] should be the same.
Validation #17: IAE Table Error: For a positive quantity in IAE, the [Item ledger Entry No.] and the [Outbound Item Entry No.] should be the different.
Validation #18: ILE - IAE Table Error: Remaining quantity on an inbound (positive) ILE entry should equal the sum of quantity fields in the IAE for an item.
Validation #19: IAE Table Error: [Outbound Item Entry No.] and [inbound Item Entry No.] should never be the same.
Validation #20: IAE, ILE, VE Table Error: For a positive ILE entry that has [Valued By Average Cost] set to true in VE , the [Outbound Item Entry No.] field for the AIE should not be blank(0).
Validation #21: IAE, ILE Table Error: The quantity of a transfer inbound must be the same as the quantity of its corresponding transfer outbound (Transfer Level).
Validation #22: VE-ILE Table Error: The [Valuation Date] and Document Type of an inbound must be the same as the [Valuation Date] and Document Type of its corresponding outbound entry for a given document number.
Validation #24: Outbound Issue: For outbound entries with [Valued by Average Cost] set to true, IAE [Cost Application] should be false.
Validation #25: Transfer Issue: For inbound entries IAE.[Cost Application] should be true regardless of [Valued by Average Cost].
Validation #26: The VE.[Valued By Average Cost] field should be the same for all VE entries associated with the same ILE.[Entry No].
Validation #27: The VE.[Valued By Average Cost] field should false for all value entries where the item does NOT use the Average Costing Method.
Validation #28: ILE Check for cannibalization of manufactured items ([Item No_] = [Source No_] and [Entry Type] <> “Output”. (entry type of 6).
Validation #29: Check Expected Cost on completely invoiced entry. (Checks if the amount of Cost Amount (Expected), Cost Amount (Expected) (ACY), or Expected Cost Posted to G/L and Exp. Cost Posted to G/L (ACY) equals zero, if not it isreported as inconsistent data.).
Validation #30: Value Entries that have Adjustment = true, must have zero invoiced quantity.
Validation #31: Output Completely Invoiced Date Check (Three checks; (1) if IAE.Qty > 0 then IAE.[Output Completely Invoiced Date] = ILE.[Posting Date], (2) if IAE.Qty < 0 and ILE.Qty = ILE.[Invoiced Quantity] then IAE.[Outputcompletely Invoiced Date = ILE.[Last Invoiced Date], (3) if IAE.Qty < 0 and ILE.Qty <> ILE.[Invoiced Quantity] then IAE.[Output Completely Invoiced Date should be a blank date.
Validation #32: Item Ledger Entry [Invoiced Quantity] should equal the sum of the associated Value Entry [Invoiced Quantity].
Validation #33: Absolute value of the ILE Quantity should always be greater or equal to the absolute value of the ILE [Invoiced Quantity].

Se mere om diagnoseværktøjet i vedlagte PDF og kontakt din normale Navision leverandør eller Skanderby A/S (Michael Skanderby på ms@skanderby.dk eller 87 42 17 00) for flere oplysninger.