When is AR InvcHead.Consolidated = true

So working through what may be a SSRS bug.

What do we know about the consolidated flag on InvcHead table? When is it set to true?

We don’t yet do Parent-child customer billings but I assume this flag is true for those, can anyone confirm?

What we are doing is Consolidated Milestone Billing which is a relatively new feature that’s introduced a few bugs and this may be another.

Theory being: Before Consolidated Milestone Billing feature was recently added, InvcHead.Consolidated field was true only when you were doing Parent-child customer invoices so the BTName line on ARInv was useful. But now they are checking consolidated on ARHead for milestone billings to the same customer (not parent-child) so the line prints erroneously for milestone billings to a single customer. Makes sense?

Thinking through how to test this theory but want to confim the assumption when consolidated is true.

1 Like

From the data dictionary:
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.

2 Likes

Thanks. Slightly ambiguous but I take that to mean something like a shipment invoice having more than one BillTo across lines. Again I’m aware of some such but haven’t used that scenario so that’s why I’m asking.

I suspect they are now also flagging for consolidated milestone billings which have the same BillTo. Id consider that a bug since it breaks the report logic.

The consolidation settings are on the customer record. Best thing to do is set up each scenario in pilot and test it through to confirm.

1 Like

Delightfully all of these have field help on them.

1 Like

Thanks yeah we have extensively tested our milestone scenarios. Just trying to understand the other scenarios relating to consolidated flag.

We’ve found the Sold To line prints for all consolidated milestone billing’s. (ADV not CUS invc) regardless of the BillTo on customer record.

I don’t believe this is intended. Basically they’re now using that flag for two purposes and it broke the report logic.

It’s going to be faster to just customize it to work the way you want it to than to convince Epicor that the system report is wrong. Just my 2 cents.

2 Likes

Right. Done. We suppressed the line for all ADV bills. Hope they don’t simply carry forward these horrible reports and black box RDDs. I gather doing so from Crystal has a lot to do with why they’re so convoluted. Time to payback the tech debt. :crossed_fingers:

They absolutely will. The reason they picked bold reports is brcause it does not require changing the reporting architecture or the rdls.

2 Likes

Im sure you’re right. It’s just such a trashy thing to do. And twice? :face_vomiting:

1 Like