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

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP 2013: SQL script or utility for fixing incorrect lot numbers entered during receipt

(0) ShareShare
ReportReport
Posted on by

Does anyone out there have an SQL script to fix incorrect lot numbers entered during an item receipt.  I know that one is best off doing a return and then re-receipt with the right lot number.  But, if the item has already been invoiced this becomes a lot of extra work (return with credit - fake credit memo, fake new invoice number, etc.).  It would be nice if there were a utility or SQL script that could repair what can be a simple typo by someone doing a receipt.  Of course, what we've been doing is fixing this with an inventory adjustment (item transaction), but I am looking for alternatives.

Thanks!

*This post is locked for comments

I have the same question (0)
  • Verified answer
    coquisalsa Profile Picture
    2,725 on at
    RE: GP 2013: SQL script or utility for fixing incorrect lot numbers entered during receipt

    I doubt there is a utility for it. Though it is possible to do it in SQL, I wouldn't recommend it, the whole idea of posting a document is that it has been finalized. What's more you might have problems with the auditors (if you have any) for manipulating data that has been posted.

    As general rule, data manipulation using SQL should be restricted to correct data errors and not wrong data entry. I said general rule because there could be certain exceptions to it.

  • Verified answer
    Redbeard Profile Picture
    12,931 on at
    RE: GP 2013: SQL script or utility for fixing incorrect lot numbers entered during receipt

    I don't think this is "small potatoes". I checked in with a couple of developers who have existing augmentations for Serial/Lot tracking in Dynamics GP, and they don't offer this feature. When users make mistakes in the system, it can be tempting to fix them in an easy fashion, using SQL, utilities or tools; Professional Services Tools Library boasts dozens of said tools.

    I ran a quick query to determine the total number of tables containing the SERLTNUM field, here are the results:

    BM10400

    BM30400

    IS010202

    IV00702V

    IV10002

    IV10004

    IV10302

    IV30004

    IV30400

    IV30702

    IVC10102

    MOP1020

    MOP1030

    MOP1040

    MOP1043

    MOP1050

    MOP1090

    MOP1120

    MOPA1040

    MOPV2003

    MOPV2005

    MOPV2006

    MOPV2011

    MOPV2012

    POP10330

    POP30330

    QA010132

    QA010232

    QA010332

    QA020332

    QAD10132

    QAD10232

    QAD10332

    RVPS0132

    SOP10201

    SVC00250

    SVC00702

    SVC05250

    SVC05251

    SVC06120

    SVC30250

    SVC30702

    While I am sure you likely wouldn't have data in all of these tables for any particular Lot Number, any utility meant for this purpose would have to take them into account. It is perhaps instructive your desired utility is not a tool included in PSTL.

    On a side note, there are numerous reasons why a company might track Serial and Lot information (warranties, product recalls, product expiration and compliance purposes). Jorge has the right of it, if compliance is the reason, editing lot information using SQL could create much more trouble that it is worth.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans