Thank you for your reply!!

Yes, we just upgraded. Where do I access it? I get this error:

Hi @thoyt76 

You need to work with your development team to adjust the tables and remove the deprecated table.

I believe this is a customization in the report and requires developer assistance.

Please use the standard Inventory balance if needed.

Thank you, will do.

Where is the standard inventory balance?

IN615000.rpx

Please find the report above link

I cannot access that report. That is the one showing the error.

We can’t access your sharepoint link.  Shows we do not have access.

I am also experiencing the same issue. 
We have multiple clients have have been upgraded to 23R2. 

but only one is having the issue of not accessing the report. All report versions have the Insitecoststatus table but are working fine except one. 

The stock Acumatica report link that you provided, I am not able to access. Can you provide a downloaded link in this thread?

When clicking on the link you provided @thoyt76 it takes me here:

 

Same think for me: Unable to acces IN615000 since upgrade from 2023R1 to 2023R2.

If you have access to Demo site for 2023 R2 - it has working version of the report.

Please follow https://acumatica-builds.s3.amazonaws.com/builds/23.2/ReleaseNotes/AcumaticaERP_2023R2_ReleaseNotes_for_Developers.pdf release note.

On page no 70 it’s mentioned that

“The INSiteCostStatus and INLotSerialCostStatus projections DACs have been deleted from the PX.Objects.IN namespace. The new INSiteCostStatusByCostLayerType and INLotSerialCostStatusByCostLayerType from the PX.Objects.IN.DAC.Projections namespace should be used instead.”

Hi,

Could someone explain to me please why standard oobx inventory balance reporte uses INSITECOSTSTATUS and didnt present error in a customer that the version is the same since the creation of the instance but when an UPGRADE to 2023R2 occurs it appeared the error?

The image above is the schema of an oobx inventory balance report from a customer that didnt UPGRADE.

Thanks.

As outlined from multiple Members above, you need to adjust Tables from the old names to the new ones.

Still currently working through this myself on a Custom Report that follows the normal Report but here is what I gathered so far.

Replace INSiteCostStatus with INSiteCostStatusbyCostLayerType including using the Refresh/Refactor option to map all fields after removing INSiteCostStatus

Replace INLotserialCostStatus with INLotSerialCostStatusbyCostLayerType including using the Refresh/Refactor option to map all fields after removing INLotSerialCostStatus

Depending on how your Report is structured there could be more but these two definitely changed and have been replaced with the byCostLayerType Tables.

Custom Reports are not updated. If native Reports have Modifications to it, the Update usually does not apply correctly either.

I hope this helps everyone a little on resolving these issues.