By using this website, you agree to our Terms of Use (click here)
Hi,
I am trying to create a GI which gives the Qty on POs and SOs at different stage. I have tried it with two different tables,
- InventoryAllocDetEnqFilter on Inventory Allocation Details screen.
- InventorySummaryEnquiryResult on Inventory Summary screen.
When I viewed the GI, I get the "Invalid object name..." error.
Any idea what needs to be changed here?
Thank you.
This is one of the most infuriating things I have come across in our system: It allows you to select virtual tables, or "Views" in SQL.
You cannot access these directly. You'll need to pair up your SOOrder and POOrder tables by hand. Just be careful to avoid duplicate lines if you add in the SOLine and POLine tables.
If you're new to SQL a View is a table that is created on the fly. Therefore nothing exists when you call it via a GI, thus it claims the name for your object is invalid. I still don't see why these "tables" aren't blocked from our table lists as they're just filler and are highly misleading. I have no idea how to identify these tables other than trying them in a GI where I only have that singular table and a single result entry. Wish I had better news for you. Maybe Tim knows a way to get that table to appear, possibly by passing a param to it?
Michael,
I agree with you, those tables should not have been available on GI if we cannot use them. I have found another screen, "Prepare Replenishment", which has all the information I need. Although, it does not give me any error messages, it does not list any items either. I have tried to put the "Warehouse" and "*Purchase Date" in conditions tab but still did not work.
Thank you for your suggestion. I will give it a try.
Everything in Acumatica is actually a Data Access Class (DAC), not a SQL Table or SQL View. For more on that, click here.
I'm not sure though if there is any marker on a DAC to tell you if it's intended to be temporary or not.
You will see this especially in the inventory area because the screens are doing a lot of work to summarize information in the screen itself. Then they dump the results into a DAC. So the DAC needs to exist, but it only gets populated when you are in a specific screen, like Prepare Replenishment. If you want to find a DAC that you can use, I suggest looking at the inventory reports in Report Designer. Those will show you DACs that have data in them that you can use in a Generic Inquiry.
After reading your link, I can see some differences, but for this specific case they're oddly synonymous.
I would love to get my hands on a list of persistent DACs. If anyone has an intern who needs a terrible project, this would be a great one to get them interfacing with the DACs.
Yes, I would guess that about 90% of the DACs are also SQL Tables. But it's important to know that you are actually interacting with DACs when building a Generic Inquiry, not a SQL Table directly.
If you built a list of persistent DACs, I'd love to see it. You'd probably find that it doesn't take that many DACs to come up with most of the data that you care about.
Doug Johnson came up with this slide of most relevant DACs:
+1 for posting that and +3 to Doug for making it!