Share
ReportI read that there is a procedure called IN_Debug that helps find the issues to this problem...are there any instructions as to what the return data means when running IN_Debug?
You’re offline. This is a read only version of the page.
150
I read that there is a procedure called IN_Debug that helps find the issues to this problem...are there any instructions as to what the return data means when running IN_Debug?
I asked one of our distribution specialist if there were general instructions on how to read the file after its generated.
what I do is that I usually will first narrow the INTRAN section down to the unreleased trans. Then hide all the fields in the other tables NOT related to that item. Also, review in conjunction with the event log with database calls turned on to see WHY the items weren't releasing. Then review the debug in that context
I'm sure I'd get different answers from other agents, which is probably why there isn't a guide to it.
Best Regards,
Jana MacDonald
Thanks Mark E...I was able to run the IN_Debug procedure...I wanted to know if there were instructions on what the return values meant. The video doesn't go over that. I figured out my issue as to why I needed it. Users were getting the cost to imbalance in itemsite when trying to release certain parts, turned out that in the ItemSite table the Totcost was not equaling QtyOnHand * stdcost, so when I fixed the Totcost value, users were able to release their Issues (InTran) batches
Thanks again.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,532
Super User 2024 Season 2
#2
Martin Dráb
228,501
Most Valuable Professional
#3
nmaenpaa
101,148
All responses (
Answers (
