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 :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / MPK Reverse Issue - It...
Microsoft Dynamics GP (Archived)

MPK Reverse Issue - Item Stock Inq log is inaccurate

(0) ShareShare
ReportReport
Posted on by Community Member

When after posting a reverse issue of an MFG - MO MPK  issued item, all records are accurate accept the log entry for the item in the Item Stock Inquiry window.  The record is listed at an ambiguous date in this log. When the log entry is located, all Document date and GL date info is correct when highlighting and drilling to the Document Number.

Why is this log entry wrong? Can we fix this?

MPK_5F00_RevISSUE_5F00_StockInqLogError_5F00_1.JPG

MPK_5F00_RevISSUE_5F00_StockInqLogError_5F00_2.JPG

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    My guess is that the random date posted in the Stock Inquiry Log has something to do with the due date of the MO. The date is always before the MO due date so that was my educated guess. I don't know if that is why a random date is posted here while the actual transaction date is posted everywhere else.  

    If this is true, can it be fixed?

    Can anyone explain what is happening and what options I might have?

  • Community Member Profile Picture
    Community Member on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    I can't find anything on this symptom. Am I the only one with this issue?

  • Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    Hello there,

    This is definitely due to incoherent details between the internal inventory tables, the item stock inquiry retrieves data primarily form IV30300.

    For that, may I ask you to run the below queries on and provide us with the results. Don't forget to include the item number and document number in the declaration part below

    DECLARE @ItemNumber AS NVARCHAR(MAX)
DECLARE @DocumentNumber AS NVARCHAR(MAX)

SET @ItemNumber = 'XXX'
SET @DocumentNumber = 'YYY'

SELECT  TRXSORCE ,
        DOCNUMBR ,
        DOCDATE ,
        ITEMNMBR ,
        UOFM ,
        TRXQTY ,
        UNITCOST ,
        EXTDCOST ,
        TRXLOCTN
FROM    dbo.IV30300
WHERE   ITEMNMBR = @ItemNumber
        AND DOCNUMBR = @DocumentNumber
SELECT  ITEMNMBR ,
        TRXLOCTN ,
        DATERECD ,
        QTYRECVD ,
        QTYSOLD ,
        RCPTNMBR ,
        UNITCOST ,
        ADJUNITCOST
FROM    dbo.IV10200
WHERE   ITEMNMBR = @ItemNumber
        AND RCPTNMBR = @DocumentNumber
SELECT  ITEMNMBR ,
        LOCNCODE ,
        DOCDATE ,
        TRXQTY ,
        TRXQTYInBase ,
        UNITCOST ,
        DOCNUMBR ,
        UOFM ,
        JRNENTRY ,
        DEBITAMT ,
        CRDTAMNT
FROM    dbo.SEE30303
WHERE   ITEMNMBR = @ItemNumber
        AND DOCNUMBR = @DocumentNumber


SELECT  JRNENTRY ,
        TRXDATE ,
        ACTINDX ,
        DEBITAMT ,
        CRDTAMNT
FROM    dbo.GL20000
WHERE   JRNENTRY IN ( SELECT    *
                      FROM      dbo.SEE30303
                      WHERE     ITEMNMBR = @ItemNumber
                                AND DOCNUMBR = @DocumentNumber )


    Your feedback is highly appreciated,

  • Community Member Profile Picture
    Community Member on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    I didn't seem to find anything related in SEE30303.

    IV30300

    TRXSORCE DOCNUMBR DOCDATE ITEMNMBR UOFM TRXQTY UNITCOST EXTDCOST TRXLOCTN
    IVADJ00015133 IVADJ0015148          10/8/2015 6673-4005-M                    EA        2 15 30 Target_LOC

    IV10200

    ITEMNMBR TRXLOCTN DATERECD QTYRECVD QTYSOLD RCPTNMBR UNITCOST ADJUNITCOST
    6673-4005-M                    Target_LOC 10/8/2015 2 2 IVADJ0015148          15 15

    SEE30303

    NULL

    GL20000

    JRNENTRY TRXDATE ACTINDX DEBITAMT CRDTAMNT ORDOCNUM ORCTRNUM DOCDATE REFRENCE SEQNUMBR
    193236 11/12/2015 37 30 0 IVADJ0015148          IVADJ0015148          1/1/1900 MO-MORD001268-0004              16384
    193236 11/12/2015 1464 0 30 IVADJ0015148          IVADJ0015148          1/1/1900 MO-MORD001268-0004              32768 

    SELECT  JRNENTRY ,
            TRXDATE ,
            ACTINDX ,
            DEBITAMT ,
            CRDTAMNT
			,ORDOCNUM
			,ORCTRNUM
			,DOCDATE
			,REFRENCE
			,SEQNUMBR
    FROM    dbo.GL20000 with (nolock)
	where ORDOCNUM = @DocumentNumber and ( SEQNUMBR = 16384 or SEQNUMBR = 32768 )
   /* WHERE   JRNENTRY IN ( SELECT   JRNENTRY --*
                          FROM      dbo.SEE30303 with (nolock)
                          WHERE     ITEMNMBR = @ItemNumber
                                    AND DOCNUMBR = @DocumentNumber )
									*/


  • Suggested answer
    Tim Foster Profile Picture
    Tim Foster 8,515 on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    This is a known behavior of Dynamics GP Manufacturing.  When you Reverse Issue goods the date of "arrival" back into GP Inventory is the same as the Receipt Date the original Issue-Adjustment was made from i.e. It looks like the Inventory was returned on the same day it was issued.

    There is documentation available somewhere on this, but it is not handy to me right now.   When I find it, I will post back.

    Tim

  • Suggested answer
    Tim Foster Profile Picture
    Tim Foster 8,515 on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    There's even a third party to help with this problem.

    willoware.com/.../mfg-powerpack

    Tim

  • Verified answer
    Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    The issue has is crystal clear, let me add to the valuable suggestion made by Tim. This is due to the different document date since multiple dates are recorded, the original receipt date is recorded in IV30300 (Item Stock Inquiry), IV10200 (Purchase Receipt). On the other hand, IV30200 and SEE30303 (Historical Inventory Trial Balance) consider the retrieval date.


    I would find no issues at all in correcting the IV30300 table in order to match the details recorded in both (IV30200) and (SEE30303). It is a historical table and I don't find a huge risk in getting it updated in order to correct the item stock inquiry.

    On the other hand, playing with the IV10200 is not recommended. It does require high know-how since it is a primary table in the inventory module and several other tables are dependent on

     

    You might try to do this on your test company, never start with the live company

    DECLARE @ItemNumber AS NVARCHAR(MAX)
DECLARE @DocumentNumber AS NVARCHAR(MAX)
 
SET @ItemNumber = 'XXX'
SET @DocumentNumber = 'YYY'

UPDATE  dbo.IV30300
SET     DOCDATE = ( SELECT  TOP 1 DOCDATE
                    FROM    dbo.IV30200
                    WHERE   DOCNUMBR = @DocumentNumber
                  )
WHERE   ITEMNMBR = @ItemNumber
        AND dbo.IV30300.DOCNUMBR = @DocumentNumber

    Your feedback is highly appreciated,

  • Community Member Profile Picture
    Community Member on at
    RE: MPK Reverse Issue - Item Stock Inq log is inaccurate

    I appreciate all your help Mahmoud and Tim.  I will look into these options. It is good to know that this is not due to a config issue on my part.

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…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans