Version? PUs?

location details or Item Inquiry?  i guess a picture(s) might help.  We experience odd things once in a while but only really with Item Inquiry.

They are currently on 2023.1 but I uploaded an old copy of a v2019 database and loaded it in v2022.3 and same results.

Location Detail.   Here you can see, same item, different locations but one shows order details and the other doesn't.  (old data because its an old backup to test- but same results in live database)

Does Sage IC Data Integrity report any problems with this item? 

Their DI is full of errors but nothing for this sample item.  I am currently running DI with Fix on IC/OE for this test database.

Unfortunately it is also not a single item that is the issue.  Finding it difficult to pinpoint the issue.

Are any of the orders on hold?

I 100% didn't realize you could drill down from that table.  I don't see how that is useful as all that info is better presented in Item Inquiry EXCEPT that this is sorted based on the expected ship date.  That's pretty neat. 

if they were on hold, then the QTY would not show as on sales order.  

are some of the items possibly "on sales" within a KIT?  if so, those would show as a sales order in location details but I bet that drill down wouldn't show them.  You can spot check that by looking in Item Inquiry and those items would show in the KIT section of the sales orders tab

I created an order with the single non-kitted item.  Still does not display

Orders are confirmed not on hold.

is the location details drill down and Item Inquiry reacting the same way?

When it works- it's great.  You can look at qty on PO, SO and Committed.  Easy to see what transactions make up the value.  (you can drill down further to the individual transactions too)

No.  No issues within Item Inquiry or any of the IC/OE reports.  The transactions are accounted for- just not displaying.

What's the collation of the database?  Is this issue restricted to the MAIN location vs the numeric locations?

Item Inquiry works way better than the info I see on these drill downs.  my my opinion though

SQL_Latin1_General_CP1_Cl_AS    And no, other items in Main display without issue and some within a numeric location do not.

Client likes location details as it displays per location and totals qty.   Ops is the bandaid... client wants the cure.

Run RVSpy along with DBSpy. This will tell you what filters are being used and that should point to where the issue is.

that makes no sense.  the location tab in item inquiry shows all that too.  And it shows WAY more information .  It's the only way I can navigate stock across our 20 locations without having to open a bunch of screens.  To each their own I guess. 

I agree a lot of information in Ops.  But it also worries me that the underlining issue might be something not to be ignored.  

Both contain a lines  119 <DBS_NOT_FOUND> after looking at the order header table.  Any ideas?

Unfortunately that's not enough to go on. The full log will be needed. Typically you find the first error lines and then work your way up to see what Sage was doing just before it hit the error.

UPDATE:  SOLUTION FOUND

A previous business partner had attempted a clean up by deleting the order headers but not details leaving millions of orphaned records.  We used Musick's FixIT tool to clean up the records and the location details returned.