Results 1 to 5 of 5

Thread: Need help figuring out BI Publisher bursting issue.

  1. #1

    Need help figuring out BI Publisher bursting issue.

    Hi Everyone,

    I'm trying to set up a BI publisher report for a 9.2 JDE environment that has to send a customer statement to the selected customers, and has to burst into multiple PDF files if more than 1 customer was selected in the data selection...

    Attached you can find the xml output of the job. The Burst field is set to:

    /R5503B3001/A_R_Detail_Reports_S3_Group/Customer_Level_Break_S7

    When we run the report for more than one customer (so when it has to burst the report) the status turns out to "FX" with the following errors in the XML publisher kernel:

    5140/6536 Fri Aug 05 07:17:11.928000 XMLPBurstUtils.cpp400
    Failure found in burst status file, please see debug log for additional details.

    5140/6536 Fri Aug 05 07:17:11.928001 XMLPBurstUtils.cpp402
    *** In case of blank reports, the most common cause for this failure is an invalid burst field. ***

    5140/6536 Fri Aug 05 07:17:11.928002 XMLPBurstUtils.cpp400
    Failure found in burst status file, please see debug log for additional details.

    5140/6536 Fri Aug 05 07:17:11.928003 XMLPBurstUtils.cpp402
    *** In case of blank reports, the most common cause for this failure is an invalid burst field. ***

    5140/6536 Fri Aug 05 07:17:11.928004 XMLPBurstUtils.cpp400
    Failure found in burst status file, please see debug log for additional details.

    5140/6536 Fri Aug 05 07:17:11.928005 XMLPBurstUtils.cpp402
    *** In case of blank reports, the most common cause for this failure is an invalid burst field. ***

    5140/6536 Fri Aug 05 07:17:11.928006 XMLPUtil.cpp2742
    Unable to read burst status file. Return Code 13

    I did already set up a temp directory and added it to the xdo.cfg file on the enterprise server, and still get the same errors.
    I can't figure out what is going wrong with the bursting of the report. When just a single customer is selected everything else works properly. Have I set up the burst field incorrectly? Any input would be appreciated.
    Attached Images Attached Images
    Attached Files Attached Files

  2. #2
    I have similar issue. Please let me know if you were able to find out the solution.

  3. #3
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,258
    Ours is based on

    /R03B5001/A_R_Statement_Detail_S9_Group/Payor_Level_Header_S14

    works for us
    Larry Jones
    E1 9.2 - TR 9.2.2.6 on Win 2016 R2. SQL Server 2016
    Wintel, BI Publisher

  4. #4
    Member Mike Mackinnon's Avatar
    Join Date
    Nov 2000
    Location
    Halifax, Canada
    Posts
    195
    We burst on the individual customer number - our variable is "ElectronicAddress_ID67".
    This is what our burst field looks like: /RHO03B50/Statement_of_Account_View_S1/ElectronicAddress_ID67


    Looking at your XML it seems that the field you are bursting on has no values in it. Maybe give this a try?

    /R5503B3001/A_R_Detail_Reports_S3_Group/Customer_Level_Break_S7/AddressNumber_ID2


    I think the program will try to burst when the field being bursted on changes values. Maybe it is a problem since this 'field' is not changing?
    Mike MacKinnon
    IMP Group International
    EnterpriseOne tools RL 9.2.2.6, Application RL 9.2
    BI Desktop Publisher 11.1.1.7
    Browser IE10 & Chrome 62.0.3202.94

    - Financials, Inventory (Sales & Procurement), MRP, Manufacturing, Development Tools, BI Publisher

  5. #5
    Member Mike Mackinnon's Avatar
    Join Date
    Nov 2000
    Location
    Halifax, Canada
    Posts
    195
    PS - This should probably be moved to the BI Publisher sub-forum
    Mike MacKinnon
    IMP Group International
    EnterpriseOne tools RL 9.2.2.6, Application RL 9.2
    BI Desktop Publisher 11.1.1.7
    Browser IE10 & Chrome 62.0.3202.94

    - Financials, Inventory (Sales & Procurement), MRP, Manufacturing, Development Tools, BI Publisher

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.