If parents are currently non-inv items, do you put...
# arm
c
If parents are currently non-inv items, do you put the components on transactions currently? What's the relationship?
s
we put the parent on transaction at $0, and then the components right after with dollars assigned. this is how it's coming across from SFDC
c
How does the parent SKU influence the correct FV of the component?
Or, maybe the right question is, do you perform SSP at the parent or component level?
s
from how i understand it, what revenue accounting has said, SSP has to be at the component level, because the parent SKU will always be at $0
did more testing, Kits won't work for us as it uses static Components. ARM seems to treat the flat SKU structure (parent and component SKUs all set as non-inventory items, parent set to be excluded from allocations) vs. Group item structure the same. we for sure need FV dimensions to help us differentiate between a SKU used as a component of this bundle or another bundle, but is there a benefit (or negative) to using Group Items in general?
k
Having a group item on a transaction is a convenience of not selecting multiple items time after time after time.. Does not seem to be effective for you for the same reason kits won’t work. But this should not be a concern since you are not adding items manually . Assign dimensions, this should solve it
✔️ 1
c
Re what you said above that kit SSP has to be at the component level because the parent SKU is always $0 - this is not necessarily the case. You can uncheck auto-expand for ARM on kits and do all your SSP for just the parent while the costing remains at component. But you can't have it both ways - i.e if the SSP is dependent on the components you must do it all at compnents, and if not can do it all at the parent.
✔️ 1
But if dimensions work for you that's probably better than using a different item type
✔️ 1
s
yes, from our understanding SSP is dependent on the components. thanks for all the input on this! ☺️