We want to improve our data understanding and inputs, and we have a configurator for two of our product lines that shows all the 12 different options that go into these highly customizable machines. My boss would like to be able to see better data on what types of pumps are being sold, and which options are most popular.
My question is, can we create reports based on the frequency of parts with specific configurator choices? I am the new Epicor admin, but it was the gentleman who was here before me that set it up, and I have lot of learning to do on it. However, I didn’t want to put the time in right this moment if it won’t be able to reach the end goal I’m looking to achieve.
TL;DR
Can I run reports that show what configurator options are being sold the most based on sales orders?
I’m sure he’s busy or taking his holiday, otherwise @MikeGross has done this.
tl;dr version is that all of the configurations are stored in a record as an XML file. At one point, Epicor created a view for it so you can get it via a BAQ. It was called PCInputs or something similar.
@Mark_Wonsil is correct, PcInputs should contains the configurator information you’re looking for.
Rather than parsing PcInputs, I would query the orders (OrderDtl table) or quotes (QuoteDtl). The inputs at the Configurator should manifest in some characteristic in the orders. This would also find anything that was changed manually.
Actually did this two ways. Note - Epicor provides a View in the database that versions prior to 2021.2(?) can’t see, but then it is was magically available. It can be used a variety of ways - for a single field or a group of fields.
SQL Query/script that pulls together Quote data and data from the view into a UD table. This makes big data sets nice to analyze - and it’s quick. I just run this every night for the quotes that are new/changed. Works for uploading to PowerBI or EDA and for my AM reports that get emailed out to Sales people.
In my BAQs, I create a column for each CFG variable I want to have in the result set. I usually do this as a CTE so SQL will process ahead of time, and my base query can be a little sloppy if need be.
the table PcInvalue does expose each control and its associated values similar to what you got in E9 and E8. As with E8/9 you need to use the relatedToFile along with the Key1 and Key2 to link to the OrderDtl/QuoteDtl as appropriate. Typically as others have mentioned if something is important to be reported on regularly have the configurator copy it out to a User Defined field on the order/quote/job.
If everything is needed outside of the configurator most of the time that isn’t true if you drill into what you do with the data.
