web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP2010 Item Stock Inquiry - Duplicate transaction

(0) ShareShare
ReportReport
Posted on by 225

Hi,

I am sure I have seen this issue before but cannot find the fix....

I have an instance where the same receipt is within the item stock inquiry window twice affecting stock.  There is only one receipt line in the TABLES and there is no physical duplicate duplicate between work and history.

In the past there has been issues with this view and I am sure that MS has released an amendment to the a view that generates the results in order to rectify the issue where it looks as if a duplicate entry is created.  However I cannot seem to find this.

This is within dynamics gp2010 sp3. 

Thanks

 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bron Profile Picture
    4 on at

    Chris -

    I've seen this problem a couple different times - unfortunately I have always had to 'fix' the data via SQL delete statements (never a good method to fix something). Usually, the IV10200, IV30300, IV30301 tables need altering - In my experience the POP tables are usually correct - however, these would need to be checked as well.

    After altering the tables in Back Office, I typically run IV reconcile to let the system re-calculate quantity on hand.

    Never attempt this process without making a backup and if you haven't altered data in the back office before, I don't recommend you try to self educate. Probably best to reach out to someone with experience.

  • Chris_L Profile Picture
    225 on at

    Hi,

    thanks I will check these tables - but I am sure I have seen this before and it hasn't been data but a bug in one of the views.  

    Thanks for the post and I will check the IV tables.

  • Bron Profile Picture
    4 on at

    Chris -

    If you're comfortable with SQL - I have an SQL script that searches the entire company database for any 'string' value. In situations like this, I run the script with whatever unique string value is appropriate (PO Receipt Number) - the script tells me all tables and what columns store that unique value - then I manually check every table. Tedious but thorough.

    Last time I saw this problem - the IV tables had records with both 16384 and 16385 for line number sequences. Unfortunately, the IV10200 table doesn't have line sequence numbers - just Dex_Row_ID which I ended up deleting the duplicate records based upon DEX_ROW_ID.

    If you need the SQL script let me know.

  • Steven Zallen Profile Picture
    30 on at

    Hi

    I began to experience similar issues with line numbers for Shipments about 1/30/2013.  I also am seeing that PO lines for recieved items are not moving to Status 4 or 5.  They stay at status 2 until matched, at which it appears both the status and problem lines are disappearing.  

    I have at lease one occurence where IV10200 has the same PO line twice with different RCTSEQNM and DEX _ROW_IDs but only one entries in the IV10200 table.  Inventory is off by the duplicate entry.

    I also noticed that the DEX_ROW_TS for these lines is at some point later (date) than the first or last reciept dates, usiusly a few days, and appears to be at a time when there should be no one in the system.

    The last occurece was the 6th, but there were multiple days with multiple POs impacted, but not all POs were impacted.  I have a export of over 300 lines as of Friday, but today only 78.

    I still am trying to get my hands around this.

    We are on 2010 SP2.

    Thanks

  • Bron Profile Picture
    4 on at

    Steven -

    In my situation - I was using Integration Manager to bring in 'Purchase Receipts'. The integrations never failed and our duplicate transactions were really miniscule compared to number of successfully integrated items.

    In my case, the POP tables were never a problem - no problem with status - no problem with duplicates. In our case we had duplicates in the IV10200 table (just like you) and the IV30300 table (LNSEQNBR would be 16385 (instead of 16384) and the IV30301.

    The solution was to carefully write SQL delete statements to delete the duplicate records and then to run the IV Reconcile - in all cases, this worked.

    This happens to be very sporadic  - I will eventual write a business alert or a SQL trigger that looks for the record in the IV30300 table with a 16385 LNSEQNBR. If you know anything about GP Data schema - you know GP stores line records in increments of 16384 and therefore, a 16385 is a record which is very abnormal and worth looking at.

    Good Luck

  • Chris_L Profile Picture
    225 on at

    Hi Steven, I agree with Bron, i backed up the 3 tables and removed the duplicate records.  I am also led to believe that these may have been integrated.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

#2
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans