Skip to main content
Solved

Generic Inquiry for Kits with Stock and Nonstock items


Forum|alt.badge.img+1

Hello,

I have a customer who would like a generic inquiry that presents the list of kit components like a BOM (i.e. a column for the parent id and a column with all of the components of that parent). The problem is that stock and nonstock components are in separate tables.

Has anyone been successful with this?

Best answer by Neil Cantral

Looking back, I misunderstood the original post. Since the stock and non-stock components exist on separate tables we would need to get creative since union operators are not supported natively (if I recall correctly).

Customization is always an option. Subreports would be more accessible but loses out on the great functionality of GIs. 

Simplest option would be to join the non-stock detail to the stock detail on KitInventoryID, RevisionID, and LineNbr. This assumes you always have more stock items than non-stock on a given kit. 

Not my favorite solution since it’s not the best user experience having the data organized like this. Below is an example:

 

 

 

View original
Did this topic help you find an answer to your question?

5 replies

Neil Cantral
Jr Varsity I
Forum|alt.badge.img+3
  • Jr Varsity I
  • 60 replies
  • April 22, 2022

It may not be pretty, but I think an IsNull, Switch, or IIF function for each component field will be the way to go.

=ISNULL( [INKitSpecStkDet.CompInventoryID], [INKitSpecNonStkDet.CompInventoryID])


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2679 replies
  • April 28, 2022

Hi @donnadeskins55 have you been able to resolve your issue? Thank you!


Forum|alt.badge.img
  • Freshman I
  • 41 replies
  • January 10, 2024

@Neil Cantral ,

I stumbled across this thread, and I’m looking to accomplish the same thing.  I have a GI created, however, if we search for a component item, it does not bring it up.  The addition of the side panel does assist the user in seeing what is in the kit, but the search abilities are not working the way I thought they would. 

This is the GI Results Grid that I have currently:

 

This is the output from the GI:

 

This is the current set up for relationships:

 

Any ideas how to set this up so that it will show all the components and kit assembly parent numbers?  Would the formula you mentioned in the above post help this GI?

Thank you,

Trisha


Neil Cantral
Jr Varsity I
Forum|alt.badge.img+3
  • Jr Varsity I
  • 60 replies
  • Answer
  • January 11, 2024

Looking back, I misunderstood the original post. Since the stock and non-stock components exist on separate tables we would need to get creative since union operators are not supported natively (if I recall correctly).

Customization is always an option. Subreports would be more accessible but loses out on the great functionality of GIs. 

Simplest option would be to join the non-stock detail to the stock detail on KitInventoryID, RevisionID, and LineNbr. This assumes you always have more stock items than non-stock on a given kit. 

Not my favorite solution since it’s not the best user experience having the data organized like this. Below is an example:

 

 

 


kkeating24
Jr Varsity II
Forum|alt.badge.img
  • Jr Varsity II
  • 75 replies
  • June 20, 2024
Neil Cantral wrote:

Looking back, I misunderstood the original post. Since the stock and non-stock components exist on separate tables we would need to get creative since union operators are not supported natively (if I recall correctly).

Customization is always an option. Subreports would be more accessible but loses out on the great functionality of GIs. 

Simplest option would be to join the non-stock detail to the stock detail on KitInventoryID, RevisionID, and LineNbr. This assumes you always have more stock items than non-stock on a given kit. 

Not my favorite solution since it’s not the best user experience having the data organized like this. Below is an example:

 

 

 

with the new ability to use a GI as a Data Source, should be able to accomplish this now.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings