INSiteStatus: values no longer changing in database after 2024R1 upgrade?

Question

From the Inventory Allocation Details (IN402000 screen) page, I’m interested in these fields:

I used to get these values from the database using this SQL query:

select [QtySOBackOrdered],[QtySOShipping],[QtySOBooked],[QtySOPrepared]

FROM [dbo].[INSiteStatus] (NOLOCK) ss

where InventoryID=19560 and CompanyID=2

Unfortunately, these values aren’t changing in the database on a daily basis even though they are changing on the Inventory Allocation Details (IN402000 screen) page. In fact, they haven’t changed at all since the upgrade from 22R2 to 24R1. It looks like the InventoryQtyByPlanType code is used to populate this grid in 24R1 but, looking at the refactored code, I’m not seeing how these fields are calculated or which database tables they are derived from.

Does anyone know where these values are stored in the Acumatica SQL database?

Best answer by Naveen Boga

@bpgraves Have you checked the INSiteStatusbyCostCenter table?

This change is happened from 23 R2 but not from the 24 R1. Please find the screenshot below from 23 R2 Release Notes.

Naveen Boga · Accepted Answer

​@bpgravesHave you checked theINSiteStatusbyCostCenter table?This change is happened from 23 R2 but not from the 24 R1. Please find the screenshot below from 23 R2 Release Notes.

kyle90 · Answer

Just updated to 25R1 and seeing the same issue in one of two tenants - INSiteStatus isn’t being updated, which kills dozen’s of active GI’s and dashboards.. possibly even more issues I’m not thinking of here

How do I even run down all the references to this table? Also, why is this working for one tenant and not the other?

In the release note above it states that we can still use these fields but that the data will come from INSiteStatusbyCostCenter - Does anyone understand what this means? Clearly we can’t use these tables if we want valid results

It’s worth noting here - Neither the DAC Schema Browser, nor the Data Source or Results Grid give any sort of warning that INSiteStatus is depreciated and no longer being updated.

This is going to create an enormous amount of work if we need to go and rebuild all the tables/relations/formulas etc and there appears to be no added value - Aside from CostCenterID & tstamp, the two tables appear to be identical

Sign up

Social Login

Login to the community

Social Login

Scanning file for viruses.

This file cannot be downloaded