So the company I work for provides services to numerous (thousands) of locations that are billed back thru the Parent customer. Over the past few months we’ve been migrating this into the system with orders vs misc invoices loaded via DMT.
Last month was a big one and we moved over some big accounts, and discovered that if the child customers weren’t exactly matching in terms/billing dates, etc it wouldn’t load into a single invoice with multiple lines. (actually discovered that for some reason one of our salespersons was causing an error as well, for a different day).
Went to transition more over and instead of one invoice with 2800 lines… I ended up with 2800 invoices of 1 line. No good. Reverified all the customer data was good, no luck. Changed some settings, created new fake test orders, nada, wouldn’t work.
Got the wise idea to go back and recreate last months order with customers that worked flawlessly before the 2024.1.15 upgrade. Didn’t work. It’s not consolidating any orders, and the invchead_consolidated box is no longer checking despite being the same bill to customer/same period. The text on this field reads “Default is false. This is only set to true if this invoice was generated via Get Shipments and shipments were combined based on common Bill To customer. This is used by ARInvoice Entry to properly enable/disable Bill To customer field (InvcHead.CustNum) and to identify the record as a consolidated Invoice.”
I believe the consolidated invoice function got broke in this last update. Submitted ticket, but curious to see if anyone else on 2024.1.15 that uses consolidated invoices is experiencing the same thing.
Was provided a “hot fix” to attempt to remedy the problem. Same thing.
So i got my shovel and did some more digging and making of test orders.
Since 2024.1.15 was installed, it will only consolidate orders if they’re to the same SOLD TO and BILL TO; whereas in the past, it took any orders to the same BILL TO (in the same period) and combined them into a single invoice with multiple lines.
I ran the same test in pilot thats been updated to 2024.2.3, and AR Invoices to different customers (but same bill to) form one invoice, as had previously. Will be testing again on 2024.2.4 when updated this week. Epicor support has been horribly slow on this matter, knowing that you could literally shut down ALL BILLING for a company… and it’s been crickets. Unacceptable.
@WarmPepsi do you have the case number? I have already sent an alert internally… but the case number would help.
Also note that we DID do a funcitonal ADDITION to consolidations… this should NOT have affected current behaviour in either 2024.1 or 2024.2… so this surprises me. The fact that this was found in 2024.1.15 tells me that it was probably a bug fix of some kind that didn’t get properly implemented.
ALSO… for your case, did you know that you can request it to be escalated? if you do that, the Tech Support management will be notified.
I just confirmed that this is being worked on and should be fixed in Kinetic 2024.1.18 as well as in 2024.2… This was reported by another customer, and transferred to PRB0289974… so if you inform support that this is the PRB, then you will be connected to it as well.
Regarding future updates… you would need to look at your cloud update schedule. if you are on-prem, there are definitely updates past the 2024.2 rollout, but when in the cloud, some of those updates dont apply since they are after the 2024.2 release to production.
Gotcha. On Epicor Cloud. If it isn’t fixed, or we don’t get to a workable version before the beginning of December, it means we’re forced to DMT thousands of invoices into the system. We’re lucky that we were about 75% transitioned and still had DMT as an option, so we had a fall back, but definitely not ideal for sure.
