Page Break is adding Blank Page in BI Publisher output

Ankush1988

Member
Hello All,

I am novice to BIP and need some help.

I have created a BIP template for invoice and wants to get page break after every new invoice number and if an invoice number extends 16 rows it should be printed on next page with same format.

In order to achieve the same i have used Nested For each and page breaks , unfortunately page break is creating blank pages for me , Can some one please assist me on the same. Any help will be appreciated.

Attaching the RTF and XML doc
 

Attachments

  • invoice (2).zip
    39.6 KB · Views: 74

rsvconsulting

VIP Member
Extra Blank pages in BI publisher outputs can occur due to empty section tags in XML source or improper design of the templates.

Here is an extract from a document that might help you.................

E1: XMLP: How To Avoid Extra Blank Pages in BI Publisher Outputs? (Doc ID 854882.1)

Applies to:
JD Edwards EnterpriseOne Tools - Version 8.96 and later
Information in this document applies to any platform.
Goal

A custom BI Publisher template has been designed to print data for sales order. The output using this template contains an extra blank page in between two sales orders when the report is run for multiple sales orders. What can cause these undesired blank pages to print in the output and how can we avoid them?
Solution
Removal of empty section tag or empty node from xml source has been fixed. Review Document 1921419.1 E1: XMLP: Empty Section Tag or Empty Node Removed in XML Source Starting From Tools Release 9.1.4.7.

Extra Blank pages in BI publisher outputs can occur due to empty section tags in XML source or improper design of the templates.

Following are few known reasons for this behavior :

Empty Section tags in XML Source

If the XML Source contains empty section tags , the output might contain blank pages. Empty tags may appear if UBE contains hidden sections . The workaround is to add some condition to check the existence of some element in the hidden section.

For example: If you have a For-each defined for a Section tag such as
<[email protected]: Level_Break___On_Address_Number_S10?>
This should be changed to :
<[email protected]: Level_Break___On_Address_Number_S10[count(Parent_Driver___Join_of_F07351_and_F07350_S2/Employee_Number___lcl_ID44)!=0]?>

Template contains Native Word Tables and Table rows are not aligned properly to fit in the page

If the XML Publisher template contains a table , there is a possibility that the table row elements are crossing the page boundaries, which may not be obvious during the design time. In this case either try to shrink the table height or table row height or redesign the template without Table elements near the page boundaries.
Redundant page break controls used in the template

Please ensure that only one page break command is used in the template. It might be possible that multiple occurrences of "Split-by-page-break" exist for single desired page break. <split-by-page-break> can be specified explicitly in the template. It is important to have just just one <split-by-page-break> defined. Also, <for-each> loops implemented with either section break or page-break would require removal of explicit <split-by-page-break> from templates .

Using IF Blocks for suppressing values

Some times, when a portion of template needs to be printed conditionally, a blank page appears when the condition is false.For example:

<[email protected]:SOME_XML_TAGGROUP?>
<?if:SUPPRESS_FLAG!='Y'?>
------ "The conditional content"------

<?end if?>
<?end for-each?>

This might produce undesired SPACES if SUPPRESS_FLAG='Y' against the expected suppression of content. This is because the 'IF' condition will add a new block. Output will not show the values (conditional content), but the placeholder still exists and as a result you will see an extra page/spaces. This may be worked around by using the XPATH predicate as shown below:
<[email protected]:SOME_XML_TAGGROUP[SUPPRESS_FLAG!='Y']?>



Sometimes the RD job can produce a complete plain blank page as output based on the conditional logic in the template, in this case the RD job still prints this plain blank page on the printer. To avoid this, you should edit your template condition in such a way that the blank PDF is not produced. Following core BI Publisher community thread can provide information on how to edit the XSL condition: https://community.oracle.com/thread/975057?tstart=0

Additional modifications might be required in the template design, which should be tested prior to report submission.

The list above is not meant to be all inclusive, there may be additional scenarios that cause extra blank pages.
 
Top