What is the best way for me to access the Part num from the configurator? When the configurator is launched, how to do I grab the part num they entered prior to launching the configurator? I need to perform some actions based on what is selected.
1 Like
Looks like it might be just Context.PartNumber.
Where do you need to access it? In the Configurator or pos configuration (like a customization or BPM)?
The field QuoteDtl.BasePartNum has the description of
The part number used to identify the configured part number initially entered on the line.
Also - I was wondering under what circumstance someone would assign the same configurator to two different part numbers. Seems like a headache waiting to happen.
We use it in the configurator. We have multiple parts linked with individual configurators. So, all of our chairs go to a chair configurator, all of our tables to to a table configurator, etc. There is no way we could maintain a separate configurator for every model (part). That my friend would be a headache to maintain.
If parts are similar, they go to a common configurator.
1 Like
Do you have to use a âTemplate styleâ configurator? (The kind where the BOM just has a few place holders, that the configurator sets the P/N, Qty, UOM EtcâŚ)
All of ours use âSuper BOMsâ (every available part that might be required - and the configurator uses âKeep Whenâ rules).
I orginally used the Template style, but was too confusing for others (who rarely ever designed configurators) to maintain. Turned out a BOM with 100 parts that - which the configurator only keeps 10 or so of - was the way to go for us.
Super BOM does not work for us. We need configurable sub assemblies of sub assemblies of sub assemblies. In one need, 6 sub assemblies deep.
We are really pushing the configurator logic. We have worked with Epicor specialists and with consultants trying to develop the one that will work for us.
On a positive side, working with Epicor, we have discovered 3 âbugsâ with the configurator logic which sound to be addressed in a recent flavor of 10.2.300.
Hi Joe, you can use Context.PartNumber - but another approach would be to ask the user to enter the part number during configuration instead of beforehand.
The way ours is set up, the part number is generated from other context fields from the sales order (sales order number, line etc.) then a document rule sets the part number on creation.
This also works with using several parts in a single configurator. The context.partnumber can reference the original part type you have selected, then use this to run specific rules generating the part number based on the part type.
1 Like