How do I handle pagebreaks with nested DWs in trailer or summary band?

[Former Member]

I am using PB12.5.2 Classic.  My report has nested datawindows in trailer and summary bands, which works fine except that where there should be a page break in the trailer or summary bands, the final page is neither displayed nor printed.   I have tried autosized or fixed heights for the bands, but the problem is the same with both (though really my report requires autosized).  Looking on the net, it seems that an issue was raised for this in PB9.0.   Has the problem been solved in PB12.6 or is there some work around that would work with PB12.5.2?

[Former Member · Accepted solution]

Hi David,

I would not wait for possible changes/fixes. 

In my experience flexible heights in a sub-report in the sub-report's non-detail bands invariably fails to properly communicate height requirements to the main report. Equally placing sub-reports in the footer band should not be too tall.  I don't recommend using the summary band in the main report for sub-reports.

Workaround could be to place the summary sub-report in the detail but only show it for the last row. Of course showing it once and retrieving it many times is not a good idea....

Alternatively create a new composite report with the existing main-report as a sub-report followed by the offending summary sub-report, if that makes sense.

Lars

[Former Member · Accepted solution]

Thanks Lars,

I'd come to much the same conclusion myself.   Unfortunately there's a requirement for subtotals within the report, which is why I was using trailer groups.  Another alternative is to generate all totals and subtotals explicately using Powerscript or stored procedures (which takes me back to my Cobol days).  The nested DWs looked really good, but losing the last page was a bit of a show stopper.  My plan is to see if we can do without the subtotals and rework the report as a composite DW.

[Former Member]

Hi David;

  FWIW: There has been changes to the DW and PB run-time support since PB 12.5.x. To get a definitive answer, I would suggest downloading the PB v12.6 "trial" version and give your DWO a quick test. If the issue still persists in v12.6, I would suggest opening a support ticket with SAP technical support and providing your DWO source and some screen captures as a test case.

Regards ... Chris

[Former Member]

Thanks for the prompt reply Chris.  Upgrading PB is not an option for us at present.   Should we go down this route, I'll check this out.