XML Bursting program completing in error

Hi,
I am trying to send the output of XML Publisher report to a specific email id. I have created the following XML Bursting File:
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
<xapi:request select="/XXIDEA_HWSW_BUYERWISE/LIST_G_CIRCLE/G_CIRCLE">
<xapi:delivery>
<xapi:email id="emailToMgrID" server="svhj0366.ideaconnect.com" port="25" from="[email protected]" reply-to="[email protected]">
<xapi:message id="emailToMgrID" to="[email protected]" attachment="true" subject="Dear Manager : "> Please review the attached list of managers </xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output-type="xls" delivery="emailToMgrID">
<xapi:template type="rtf" location="xdo://XXIDEA.XXIDEA_HWSW_BUYERWISE.en.US/?getSource=true" filter="">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
I have added the before report and the after report triggers in the rdf report. However, when I run the report, the XML Bursting program ends in error. The logs print:
Bursting propertes.....
{user-variable:cp:territory=US, user-variable:cp:ReportRequestID=89025049, user-variable:cp:language=en, user-variable:cp:responsibility=50435, user-variable.OA_MEDIA=http://oraideaapps.ideaapps.com:8050/OA_MEDIA, burstng-source=EBS, user-variable:cp:DebugFlag=N, user-variable:cp:parent_request_id=89025049, user-variable:cp:locale=en-US, user-variable:cp:user=IBMAMSTEAM, user-variable:cp:application_short_name=XDO, user-variable:cp:request_id=89025952, user-variable:cp:org_id=102, user-variable:cp:reportdescription=IDEA HW SW Buyer Wise report}
Start bursting process..
Bursting process complete..
Generating Bursting Status Report..
--Exception
ZIP file must have at least one entry
java.util.zip.ZipException: ZIP file must have at least one entry
     at java.util.zip.ZipOutputStream.finish(ZipOutputStream.java:315)
     at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.zipOutputFiles(JCP4XDOBurstingEngine.java:534)
     at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:292)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
Please help.
Thanks in advance.
Regards,
Anoop

Hi,
The reason for the exception is we don't have any data in the file to zip. If you are sending xml data to the data definition check the path in select clause in bursting control file.
Regards,
Raavi

Similar Messages

  • Print a custom Error message in the XML bursting program's log file...

    Hi,
    I having this requirement, where i need to print a custom error message in the xml bursting program's log file.
    Actually i am having a report where i create invoices and then those invoices are emailed to the respective customers, now say if a customer has three contacts and there is only two valid email id's so what happens is bursting will be successful for two contacts whereas the third contact dosen't get any emails. when this happens i need to log a message in the bursting programs log file stating a custom message.
    Two things i want to know..
    1- Whether is it possible to write into the xml bursting programs log file
    2- If yes, then how..
    note: it ll be greatly appreciated if the answer is elaborated.
    thanks,
    Ragul

    Hi,
    I having this requirement, where i need to print a custom error message in the xml bursting program's log file.
    Actually i am having a report where i create invoices and then those invoices are emailed to the respective customers, now say if a customer has three contacts and there is only two valid email id's so what happens is bursting will be successful for two contacts whereas the third contact dosen't get any emails. when this happens i need to log a message in the bursting programs log file stating a custom message.
    Two things i want to know..
    1- Whether is it possible to write into the xml bursting programs log file
    2- If yes, then how..
    note: it ll be greatly appreciated if the answer is elaborated.
    thanks,
    Ragul

  • XML Bursting Never Complete.

    Hi
    The XML Bursting program neither complete nor error out.
    I am using PLSQL for 1. Generating XML 2. SUbmit the concurrent programs.
    I have three programs : 1. To Submit the XML Report and Bursting Program. 2. To Generate the XML Report. 3. XML Bursting.
    My Program 1 and 2 completes Normal. But XML Bursting Neither completes nor throws the error.
    I am using Control file
    =============
    <xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
    <xapi:request select="/EMPLOYEE_REPORT/EMPLOYEE">
    <xapi:delivery>
    <xapi:email id="123" server="271.91.2.11" port="25" from="[email protected]" reply-to="[email protected]">
    <xapi:message id="123" to="[email protected]" attachment="true" subject=" Test PDF">
    Please review the attached Test PDF
    </xapi:message>
    </xapi:email>
    </xapi:delivery>
    <xapi:document output-type="PDF" delivery="123">
    <xapi:template type="RTF" location="xdo://XBOL.TEST_ABCINC_XML.en.US/?getSource=true">
    </xapi:template>
    </xapi:document>
    </xapi:request>
    </xapi:requestset>
    Any help is Appreciated.

    Hi Asif,
    We have applied this patch but I think the issue was the rtf in the server having a different name.I will test this in another environment without the patch. Now the issue I'm facing is Bursting Control files gets all null value passed.Hence the report and the all the details are null. Also I have changed my approach from rdf to XML data definition file. Below is the control file:
    <?xml version="1.0" encoding="UTF-8"?>
    -<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi"> -<xapi:request select="/XLAAARPT/LIST_G_RUN_LONG_REPORT/G_RUN_LONG_REPORT"> -<xapi:delivery> -<xapi:email reply-to="${CP_REQUESTED_BY}" from="${CP_REQUESTED_BY}" port="port_number" server="outbound mail server"> <xapi:message subject="${CP_SUBJECT} ${SEGMENT2} and Period: ${PERIOD_NAME}" attachment="true" cc="" to="${CF_1}" id="123"> ${CP_EMAIL_VERBAGE} </xapi:message> </xapi:email> </xapi:delivery> -<xapi:document delivery="123" output-type="excel" output="${BAL_DATA}_${SEGMENT2}"> <xapi:template location="/d11/appluat/F12UAT/apps/apps_st/appl/twpco/12.0.0/bin/TWPCO_GLRGNL2_XMLB.rtf" type="rtf"> </xapi:template> </xapi:document> </xapi:request> </xapi:requestset>
    Also I could notice that xapi:request select="/XLAAARPT/LIST_G_RUN_LONG_REPORT/G_RUN_LONG_REPORT". If I give anything below this tags I do not see any variable getting the value assigned in the Burst output. But all the tags in the Control file are under some other hierarchy i.e  /XLAAARPT/LIST_G_RUN_LONG_REPORT/G_RUN_LONG_REPORT/LIST_BALANCE_CCID/BALANCE_CCID/LIST_CCID_S/CCID_S/LIST_PERIOD_S/PERIOD_S.
    The SEGMENT2 and BAL_DATA are under the above mentioned hierarchy and these do not get passed. The other variables like CP_REQUESTED_BY,CP_SUBJECT,CF_1 are assigned in the afterTrigger section in the XML and getting Null values.
    Thanks,
    Ashwini

  • Issue with XML bursting program

    Hi All,
    We have a Oracle concurrent program which generates PDF output using XML data and RTF template. This output is sent as attachment to a designated user using XML bursting.
    The issue that we are facing is, the mail is sent to the recipients correctly when the program is run from my login. But when the same is run from anyone else’s login, the bursting program fails.
    Suppose the receiver’s email id is [email protected], the error faced is
    [oracle.apps.xdo.batch.DeliveryHelper][EXCEPTION] javax.mail.internet.AddressException: Illegal character in domain in string ``[email protected]@xyz.com''
    On examining the XML bursting program log file for successful and error runs, I could see the below property in the log file-
    For successful run: [SMTP_TO_RECIPIENTS:String] [[email protected]]
    Whereas for unsuccessful run: [SMTP_TO_RECIPIENTS:String] [[email protected]@xyz.com]
    Any pointers in this regard are highly appreciated.
    Regards,
    Kiranmayi.

    Thanks for your quick response.
    I believe the HP printer is an old one and I did have a couple of issues with it while using XML Publisher.However we've overcome those issues.
    We have installed xpdf and have been using the pdf2ps utility.We have PASTA set up and printing works fine when Bursting is not used.
    Is there some change I have to make to the configuration file/Bursting Control file to be able to use this pdf2ps utility to print to this Printer?
    Nevertheless I will also try using ipp on one of our newer printers...
    Thanks,
    Lavina

  • XML BURSTING PROGRAM QUESTION

    Hello All,
    I have customized an oracle application program with xml publisher.The program prints the report in PDF format.
    My questions is where this output copied in the server .I am not able to find the pdf report in $APPLCSF/out/.
    Do i need to use XML bursting program to achieve this?If yes i am new to xml coding can anyone help in creating busting control file.
    My object is to print the pdf report to unix server directory
    THanks

    Pl post details of OS, database and EBS versions.
    >
    My questions is where this output copied in the server .I am not able to find the pdf report in $APPLCSF/out/.
    >
    The xml and PDF output of concurrent programs should be available in $APPLCSF/$APPLOUT directory.
    >
    Do i need to use XML bursting program to achieve this?If yes i am new to xml coding can anyone help in creating busting control file.
    >
    Pl see if these links can help
    http://blogs.oracle.com/xmlpublisher/2007/04/bursting_with_bip.html
    http://blogs.oracle.com/xmlpublisher/2007/04/e_business_suite_bursting.html
    >
    My object is to print the pdf report to unix server directory
    >
    Pl clarify what you mean by this.
    HTH
    Srini

  • XML BURSTING PROGRAM

    Hello All,
    I have customized an oracle application program with xml publisher.The program prints the report in PDF format.
    My questions is where this output copied in the server .I am not able to find the pdf report in $APPLCSF/out/.
    Do i need to use XML bursting program to achieve this?If yes i am new to xml coding can anyone help in creating busting control file.
    My object is to print the pdf report to unix server directory
    THanks

    Duplicate post.
    XML BURSTING PROGRAM QUESTION
    Re: XML BURSTING PROGRAM QUESTION

  • XML Publisher Report Bursting Program ends in error

    We have a report that generates the XML output (ACH notification)
    In the after report we have a call to the Bursting program.
    The ACH notification completes with the correct output but the bursting ends in error showing
    Set Bursting parameters..
    Temp. Directory:/tmp
    [101211_072452383][][STATEMENT] Oracle XML Parser version ::: Oracle XDK Java 9.0.4.0.0 Production
    [101211_072452385][][STATEMENT] setOAProperties called..
    Bursting propertes.....
    {user-variable:cp:territory=US, user-variable:cp:ReportRequestID=28081235, user-variable:cp:language=en, user-variable:cp:responsibility=50274, user-variable.OA_MEDIA=http://xxx/OA_MEDIA, burstng-source=EBS, user-variable:cp:DebugFlag=Y, user-variable:cp:parent_request_id=28081235, user-variable:cp:locale=en-US, user-variable:cp:user=xxx, user-variable:cp:application_short_name=XDO, user-variable:cp:request_id=28081236, user-variable:cp:org_id=83, user-variable:cp:reportdescription=xxx ACH Payment Nofitication}
    Start bursting process..
    Bursting process complete..
    Generating Bursting Status Report..
    --Exception
    /tmp/101211_072452427/xdo1_2.pdf (No such file or directory)
    java.io.FileNotFoundException: /tmp/101211_072452427/xdo1_2.pdf (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at java.io.FileInputStream.<init>(FileInputStream.java:66)
         at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.zipOutputFiles(JCP4XDOBurstingEngine.java:523)
         at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:292)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
    The temp directory variable in the XML Publisher is /tmp which has all the permissions.
    The control file calls the delivery method (email 123 in the example) and uses the following template
    <xapi:document key="" output-type="pdf" delivery="123">
    <xapi:template type="rtf"
    location="XDO://XBOL.ACHPAYNOTIF.en.US/?getSource=true" filter=""/>
    </xapi:document>
    This template is defined for English language and Territory United States.
    I covered everything I could find here and in metalink and still cannot make it work.
    Any ideas?

    Hi;
    Similar issue mention at below notes, Please review:
    NPE Error While Bursting Using XDOBURSTREP in EBS R12 [ID 754790.1]
    Bursting Engine Ends With Java.Lang.Nullpointerexception[Article ID 559443.1]
    XDOBURSTREP - XML Publisher Report Bursting Program Fails with InvalidPropertyValueException[Article ID 603424.1]
    If its not help I suggest rise SR
    Regard
    Helios

  • XML Bursting Program erroring out.

    Hi All,
    When I am trying to use the bursting, I get the below error:
    XML/BI Publisher Version : 5.6.3
    --Exception
    For input string: ""
    java.lang.NumberFormatException: For input string: ""
         at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
         at java.lang.Integer.parseInt(Integer.java:468)
         at java.lang.Integer.parseInt(Integer.java:497)
         at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:142)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
    Code for Bursting:
    function submit_request_burst RETURN BOOLEAN
    IS
    l_conc_req_id NUMBER;
    l_out_req_id NUMBER;
    BEGIN
    l_conc_req_id := fnd_global.conc_request_id;
    l_out_req_id :=
    FND_REQUEST.SUBMIT_REQUEST ('XDO',
    'XDOBURSTREP',
    NULL,
    NULL,
    FALSE,
    l_conc_req_id);
    RETURN TRUE;
    EXCEPTION
    WHEN OTHERS THEN
    NULL;
    END ;
    Thanks in advance.
    Abdul.

    Hi,
    There is a difference in parameters for the Concurrent program XDOBURSTREP (XML Bursting...) in 11i and R12...
    Please find below...
    **For 11i**
    FND_REQUEST.SUBMIT_REQUEST
    ('XDO',
    'XDOBURSTREP',
    FALSE,
    :P_CONC_REQUEST_ID,
    'Y',
    **For R12**
    FND_REQUEST.SUBMIT_REQUEST
    ('XDO',
    'XDOBURSTREP',
    NULL,
    NULL,
    FALSE,
    'N',
    to_char(:P_CONC_REQUEST_ID),
    'Yes'
    Hope this will clear the issue...
    Sunil Dasari
    Oracle Applications Technical Consultant

  • XML Bursting program was messed up the report format and output, not sure what is causing an issue

    Hi All,
    I need burst the report based on the customer number for some customers and burst based on invoice number for some customers in the same bursting program. I have made the changes accordingly and sending email attachments as expected, but when the output sent for as an attachment for each invoice the report does not printing in full format, its completely ignore one child block. Not sure what was the issue. This is very very urgent please help me out.
    Following is my bursting code:
    <?xml version="1.0" encoding="UTF-8"?>
    <xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
       <xapi:request select="/XXARINVOICE/LIST_G_CUST_HDR/G_CUST_HDR">     
          <xapi:delivery>
             <xapi:email id="123" server="${SMTP_SERVER_NAME}" port="25" from="${XX_EMAIL}" reply-to = "">
            <xapi:message id="123" to="${EXCLUDED_BILL_TO_EMAIL}" attachment="true"
               subject="Confirmation for your Invoice(s)">
    Dear Customer,
    Thank you for placing an order with XX cust.
    Please review the attached invoice(s).
    Regards,
    Customer Service
            </xapi:message>
             </xapi:email>
          </xapi:delivery>     
          <xapi:document output="XX_INVOICE_EMAIL_${CUST_NO}" output-type="pdf" delivery="123">
             <xapi:template type="rtf" location="xdo://xxabc.XXARNONEDIINVOICE.en.00/?getSource=true" filter=".//G_INVOICE_HDR[EXCLUDED_BILL_TO_EMAIL!='N']"/>
          </xapi:document>  
       </xapi:request>
       <xapi:request select="/XXARINVOICE/LIST_G_CUST_HDR/G_CUST_HDR">     
          <xapi:delivery>
             <xapi:email id="123" server="${SMTP_SERVER_NAME}" port="25" from="${XX_EMAIL}" reply-to = "">
            <xapi:message id="123" to="${EXCLUDED_BILL_TO_FAX}" attachment="true"
               subject="Confirmation for your Invoice(s)">
    Dear Customer,
    Thank you for placing an order with XX cust.
    Please review the invoice(s).
    Regards,
    Customer Service          
            </xapi:message>
             </xapi:email>
          </xapi:delivery>     
          <xapi:document output="XX_INVOICE_FAX_${CUST_NO}" output-type="pdf" delivery="123">
             <xapi:template type="rtf" location="xdo://xxabc.XXARNONEDIINVOICE.en.00/?getSource=true" filter=".//G_INVOICE_HDR[EXCLUDED_BILL_TO_FAX!='N']"/>      
          </xapi:document>  
       </xapi:request> 
       <!-- START Sending email for each invoice in CR2197-->
       <xapi:request select="/XXARINVOICE/LIST_G_CUST_HDR/G_CUST_HDR/LIST_G_INVOICE_HDR/G_INVOICE_HDR">     
          <xapi:delivery>
             <xapi:email id="123" server="${SMTP_SERVER_NAME}" port="25" from="${XX_EMAIL}" reply-to = "">
            <xapi:message id="123" to="${BILL_TO_EMAIL}" attachment="true"
               subject="Confirmation for your Invoice ${INVOICE_NO}">
    Dear Customer,
    Thank you for placing an order with XX cust.
    Please review the attached invoice.
    Regards,
    Customer Service
            </xapi:message>
             </xapi:email>
          </xapi:delivery>     
          <xapi:document output="XX_INVOICE_EMAIL_${INVOICE_NO}" output-type="pdf" delivery="123">
             <xapi:template type="rtf" location="xdo://xxabc.XXARNONEDIINVOICE.en.00/?getSource=true" filter=".//G_INVOICE_HDR[BILL_TO_EMAIL!='N']"/>
          </xapi:document>  
       </xapi:request>
       <xapi:request select="/XXARINVOICE/LIST_G_CUST_HDR/G_CUST_HDR/LIST_G_INVOICE_HDR/G_INVOICE_HDR">     
          <xapi:delivery>
             <xapi:email id="123" server="${SMTP_SERVER_NAME}" port="25" from="${XX_EMAIL}" reply-to = "">
            <xapi:message id="123" to="${BILL_TO_FAX}" attachment="true"
               subject="Confirmation for your Invoice ${INVOICE_NO}">
    Dear Customer,
    Thank you for placing an order with XX cust.
    Please review the invoice.
    Regards,
    Customer Service          
            </xapi:message>
             </xapi:email>
          </xapi:delivery>     
          <xapi:document output="XX_INVOICE_FAX_${INVOICE_NO}" output-type="pdf" delivery="123">
             <xapi:template type="rtf" location="xdo://xxabc.XXARNONEDIINVOICE.en.00/?getSource=true" filter=".//G_INVOICE_HDR[BILL_TO_FAX!='N']"/>      
          </xapi:document>  
       </xapi:request>  
       <!-- END Sending email for each invoice in CR2197-->
       <xapi:request select="/XXARINVOICE/LIST_G_CUST_HDR/G_CUST_HDR/LIST_G_INVOICE_HDR/G_INVOICE_HDR">     
          <xapi:delivery>
               <xapi:filesystem output="${OUT_DIR}/INV_${SALES_ORDER}_${ORG_ID}_${INVOICE_NO}_${REQUEST_ID}_${INVOICE_DATE}.pdf">
               </xapi:filesystem>
          </xapi:delivery>     
          <xapi:document output-type="pdf">
             <xapi:template type="rtf" location="xdo://xxabc.XXARNONEDIINVOICE.en.00/?getSource=true" filter=".////XXARINVOICE[P_ATTACH='Y']"/>    
          </xapi:document>  
       </xapi:request>  
    </xapi:requestset>
    Thanks in Advance,
    Jagadish

    Initialize this:
                        String pet = "":>
    error is H:\JAVA\PetAdvice.java:88: variable pet might not have been initialized
                        return pet;Geez, the error tells you the source file and the line # at which the problem occurred, in addition to a lucid description. Why couldn't you figure it out for yourself?
    %

  • Bursting Program Ends in Error with nothing in the Log file

    Hi All
    I have a RDF which calls a bursting program in After report trigger, the problem i'm facing is that the bursting program is completing successfully for a set of parameters and when again the program is run for the same set of parameters the bursting program is ending in error, i have checked the log file but nothing in the log file
    below is my log file
    +---------------------------------------------------------------------------+
    XML Publisher: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XDOBURSTREP module: XML Publisher Report Bursting Program
    +---------------------------------------------------------------------------+
    Current system time is 30-SEP-2013 15:11:15
    +---------------------------------------------------------------------------+
    XML/BI Publisher Version : 5.6.3
    Request ID: 574533
    All Parameters: Dummy for Data Security=N:ReportRequestID=574532:DebugFlag=Y
    Report Req ID: 574532
    Debug Flag: Y
    Updating request description
    Updated description
    Retrieving XML request information
    Node Name:T1DEVEBSAPP1
    Preparing parameters
    null output =/u01/oracle/CRP2/inst/apps/CRP2_t1devebsapp1/logs/appl/conc/out/o574533.out
    inputfilename =/u01/oracle/CRP2/inst/apps/CRP2_t1devebsapp1/logs/appl/conc/out/o574532.out
    Data XML File:/u01/oracle/CRP2/inst/apps/CRP2_t1devebsapp1/logs/appl/conc/out/o574532.out
    Set Bursting parameters..
    Temp. Directory:/tmp
    [093013_031118656][][STATEMENT] Oracle XML Parser version ::: Oracle XML Developers Kit 10.1.3.130 - Production
    [093013_031118657][][STATEMENT] setOAProperties called..
    Bursting propertes.....
    {user-variable:cp:territory=US, user-variable:cp:ReportRequestID=574532, user-variable:cp:language=en, user-variable:cp:responsibility=20678, user-variable.OA_MEDIA=http://t1devebsapp1.travelzoo.com:8001/OA_MEDIA, burstng-source=EBS, user-variable:cp:DebugFlag=Y, user-variable:cp:parent_request_id=574532, user-variable:cp:locale=en-US, user-variable:cp:user=SETUPUSER, user-variable:cp:application_short_name=XDO, user-variable:cp:request_id=574533, user-variable:cp:org_id=81, user-variable:cp:reportdescription=Travelzoo Invoice Print Selected Invoices-Child, user-variable:cp:Dummy for Data Security=N}
    Start bursting process..
    Bursting process complete..
    Generating Bursting Status Report..
    +---------------------------------------------------------------------------+
    Start of log messages from FND_FILE
    +---------------------------------------------------------------------------+
    +---------------------------------------------------------------------------+
    End of log messages from FND_FILE
    +---------------------------------------------------------------------------+
    +---------------------------------------------------------------------------+
    Executing request completion options...
    Output file size:
    602
    Finished executing request completion options.
    +---------------------------------------------------------------------------+
    Concurrent request completed
    Current system time is 30-SEP-2013 15:11:41
    +---------------------------------------------------------------------------+
    and the output says..
    "Error!! Could not deliver the output for Delivery channel:null "
    Wondering What might be the issue, any help on this is greatly appreciated.
    -Ragul

    Ram,
    Is this a custom or standard concurrent program?
    Was this working properly before? If yes, what changes have been done recently?
    Did you try to relink the concurrent program executable file and see if this helps? Also, you could enable trace/debug and submit the request again and see if more details are collected in the logs -- See (Note: 296559.1 - FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12).
    Regards,
    Hussein

  • How to make Email XML Bursting program end in Warning

    Hi All,
    We are calling athe Bursting program in After parameter form trigger
    req_id :=
    fnd_request.submit_request ('XDO',
    'XDOBURSTREP',
    NULL,
    NULL,
    FALSE,
    'N',
    TO_CHAR (:p_conc_request_id),
    'Yes'
    This bursting program will work on customer(Sales Order) bill to site email address that is defined for that customer of our Sales order report.
    NOW the requirement is, if email address is NULL then the Bursting program should end in warning.(For parameters Sales order number from:33 to:33, if email id is null, then Bursting program is ending in Error. But if I give a parameter range sales order num from 33 to 35 and if only 33 so customer has email id, then program is completing in Normal.
    I want it to end in WARNING)
    Please help

    Some possible workaround would be
    - add filter to your bursting control file to just process records with email address
    - or make the change on the calling program to invoke bursting only for records with email address
    - or make too much effort catching the exact error message and force-changing the concurrent job completion status on the fly :|
    Good luck.

  • India - Receiving Transaction Processor program completing in Error status

    Hi All
    We are getting below error message in program "India - Receiving Transaction Processor". We are on R12.1.3 version.
    *** List of Transactions whose processing is skipped due to the below errors ***
    Transaction_id->5002 Error Message->Error in Line Number 1 - jai_rgm_claims_pkg.get_term_id => Location ID cannot be NULL
    Please suggest the solution.
    Thanks
    Ganesh

    Hi,
    The reason for the exception is we don't have any data in the file to zip. If you are sending xml data to the data definition check the path in select clause in bursting control file.
    Regards,
    Raavi

  • Bursting Program in error 'error while generating the document'

    Hi All,
    We have a requirement to place EXCEL output generated through BI XML report, in EBS path. ex: /usr/tmp
    Parent Concurrent program is generating output file and program got completed normal and Bursting program got submitted.
    But, Bursting program completing in error, saying 'Error While Generating Document'
    Other programs which use Bursting are working normal and they are using same path (/usr/tmp)
    Anyone faced similar issue ? Any sample bursting control file that sends .xls file will also be helpful.
    Below is the bursting file that we created:
    <xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
      <xapi:request select="/XXPREDICT/G_DATA_GROUP">
        <xapi:delivery/>
        <xapi:document output="/usr/tmp/XXYYZZ_${RUN_DATE}_${RUN_TIME}.xls" output-type="excel">
          <xapi:template type="xsl-fo" location="xdo://<APPLSHORTNAME>.<TEMPLATECODE>.en.US/?getSource=true" />
        </xapi:document>
      </xapi:request>
    </xapi:requestset>
    P.S: When we give template type as 'rtf', then we are getting a different error i.e., "No such file or directory"
    Regards,
    Rupa

    You should use:
    <xapi:template type="rtf" location="CUSTOME_TOP_PATH/US/REPORT_RTF_NAME.rtf"/>
    You need to check that there should rtf file present with the same name as you mentioned in above code. Also verify the port number.
    Example:
    <?xml version="1.0" encoding="US-ASCII"?>
    <xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
    <xapi:request select="/DEBIT_MEMO/LIST_G_1/G_1">
    <xapi:delivery>
    <xapi:email id="123" server="localhost" port="1028" from="[email protected]" reply-to="[email protected]">
    <xapi:message id="123" to="[email protected] ${EMAIL}" attachment="true" subject="Invoices for VENDOR_NO:${SEGMENT1} and Period ${CF_4}">
    Please ignore this report.It is for Testing,For INVOICES of vendor ${VENDOR_NAME} for the Period ${CF_4}</xapi:message>
    </xapi:email>
    </xapi:delivery>
    <xapi:document output="${SEGMENT1}||TSRL HM||${CF_4}" output-type="pdf" delivery="123">
    <xapi:template type="rtf" location="/ebiz/app01/appldev/DEV/apps/apps_st/appl/xxabrl/12.0.0/reports/US/XXTSRL_DEBIT_CREDIT_MEMO_PRINT_LATEST_TSRL_HM.rtf">
    </xapi:template>
    </xapi:document>
    </xapi:request>
    </xapi:requestset>
    HOP! it will help you.

  • XML Publisher generates PDF but concurrent program still completes in error

    Hello,
    I have a concurent program that is used everyday. It generates PDF output with an average of 500 pages. It completes normal majority of the times, but completes in error sporadicallly. Interestingly, when it completes in error, it still generates the PDF output successfully.
    Question is why does it complete in error when all is good?
    Please note that we just went live on R12 from 11i beginning of this year. This issue never occurred in 11i. Please advise what can be done to fix this issue.
    Below is a log from one such submission. The log was rather long, so I'm only posting chunks from the beginning and end of the log, stripping the middle portion:
    Receivables: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XXBREG_RAXINV_NEW_XMLP module: Breg Invoice Print New Invoices - XMLP
    Current system time is 22-JAN-2013 06:46:58
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    p_order_by='TRX_NUMBER'
    p_cust_trx_class='INV'
    p_cust_trx_type_id='1'
    p_open_invoice='Y'
    p_check_for_taxyn='N'
    p_choice='NEW'
    p_header_pages='1'
    p_debug_flag='N'
    p_message_level='10'
    Forcing NLS_NUMERIC_CHARACTERS to: '.,' for XDO processing
    APPLLCSP Environment Variable set to :
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.AL32UTF8
    Enter Password:
    MSG-00100: DEBUG: AfterPForm_Trigger +
    MSG-00100: DEBUG: Multi Org established.
    MSG-00100: DEBUG: AfterParam_Procs.Get_Country_Details
    MSG-00100: DEBUG: AfterParam_Procs.Switch_On_Debug
    MSG-00100: DEBUG: AfterParam_Procs.Get_Trx_Number_Low
    MSG-00100: DEBUG: AfterParam_Procs.Get_Trx_Number_High
    MSG-00100: DEBUG: AfterParam_Procs.Get_Tax_Option
    MSG-00100: DEBUG: AfterPForm_Trigger -
    MSG-00100: DEBUG: BeforeReport_Trigger +
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Tax_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Message_Details
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Org_Profile.
    MSG-00100: DEBUG: Organization Id: 106
    MSG-00100: DEBUG: BeforeReport_Trigger.Build_Where_Clause
    MSG-00100: DEBUG: P_Choice: NEW
    MSG-00500: DEBUG: About to build WHERE clause.
    MSG-00500: DEBUG: WHERE clause built.
    MSG-00555: :p_choice:NEW
    MSG-00100: DEBUG: Choice is other than ADJ, setting ORDER BY.
    MSG-00555: :p_sel_trx_number:a.trx_number
    MSG-00555: :p_sel_trx_date:a.trx_date
    MSG-00555: :p_sel_trx_id:a.customer_trx_id
    MSG-00555: :p_sel_trx_type:types.type
    MSG-00555: :p_br_where_clause:
    MSG-00500: DEBUG: Table 1: AR_ADJUSTMENTS COM_ADJ,
    AR_PAYMENT_SCHEDULES P,
    RA_CUST_TRX_LINE_GL_DIST REC,
    RA_CUSTOMER_TRX A,
    HZ_CUST_ACCOUNTS B,
    RA_TERMS T,
    RA_TERMS_LINES TL,
    RA_CUST_TRX_TYPES TYPES,
    AR_LOOKUPS L_TYPES,
    HZ_PARTIES      PARTY,
    HZ_CUST_ACCT_SITES A_BILL,
    HZ_PARTY_SITES PARTY_SITE,
    HZ_LOCATIONS LOC,
    HZ_CUST_SITE_USES U_BILL
    MSG-00500: DEBUG: Table 2: RA_TERMS_LINES TL,
    RA_CUST_TRX_TYPES TYPES,
    AR_LOOKUPS L_TYPES,
         HZ_CUST_ACCOUNTS B,
    HZ_PARTIES      PARTY,
    HZ_CUST_SITE_USES U_BILL,
    HZ_CUST_ACCT_SITES A_BILL,
    HZ_PARTY_SITES PARTY_SITE,
    HZ_LOCATIONS LOC,
    AR_ADJUSTMENTS COM_ADJ,
    RA_CUSTOMER_TRX A,
    AR_PAYMENT_SCHEDULES P,
    RA_TERMS T
    MSG-00500: DEBUG: Where 1: A.BILL_TO_CUSTOMER_ID = B.CUST_ACCOUNT_ID
    AND REC.CUSTOMER_TRX_ID = A.CUSTOMER_TRX_ID
    AND REC.LATEST_REC_FLAG = 'Y'
    AND REC.ACCOUNT_CLASS = 'REC'
    AND P.PAYMENT_SCHEDULE_ID + DECODE(P.CLASS,
    'INV', 0,
    = COM_ADJ.PAYMENT_SCHEDULE_ID(+)
    AND COM_ADJ.SUBSEQUENT_TRX_ID IS NULL
    AND 'C' = COM_ADJ.ADJUSTMENT_TYPE(+)
    AND A.COMPLETE_FLAG = 'Y'
    AND A.CUST_TRX_TYPE_ID = TYPES.CUST_TRX_TYPE_ID
    AND L_TYPES.LOOKUP_TYPE = 'INV/CM/ADJ'
    AND A.PRINTING_OPTION IN ('PRI', 'REP')
    AND L_TYPES.LOOKUP_CODE =
    DECODE( TYPES.TYPE,'DEP','INV', TYPES.TYPE)
    AND NVL(P.TERMS_SEQUENCE_NUMBER,nvl(TL.SEQUENCE_NUM,0))=nvl(TL.SEQUENCE_NUM,nvl(p.terms_sequence_number,0))
    AND DECODE(P.PAYMENT_SCHEDULE_ID,'',0, NVL(T.PRINTING_LEAD_DAYS,0))=0
    AND A.BILL_TO_SITE_USE_ID = U_BILL.SITE_USE_ID
    AND U_BILL.CUST_ACCT_SITE_ID = A_BILL.CUST_ACCT_SITE_ID
    AND A_BILL.party_site_id = party_site.party_site_id
    AND B.PARTY_ID = PARTY.PARTY_ID
    AND loc.location_id = party_site.location_id
    AND NVL(LOC.LANGUAGE,'US') = 'US'
    AND NVL(P.AMOUNT_DUE_REMAINING,0) <> 0
    AND A.CUST_TRX_TYPE_ID = 1
    AND TYPES.TYPE = 'INV'
    AND A.TERM_ID = TL.TERM_ID(+)
    AND A.TERM_ID = T.TERM_ID(+)
    AND A.CUSTOMER_TRX_ID = P.CUSTOMER_TRX_ID(+)
    AND A.PRINTING_PENDING = 'Y'
    AND NVL(TL.SEQUENCE_NUM, 1) > NVL(A.LAST_PRINTED_SEQUENCE_NUM,0)
    MSG-00500: DEBUG: Where 2: A.BILL_TO_CUSTOMER_ID = B.CUST_ACCOUNT_ID
    AND P.PAYMENT_SCHEDULE_ID + DECODE(P.CLASS,
    'INV', 0,
    = COM_ADJ.PAYMENT_SCHEDULE_ID(+)
    AND COM_ADJ.SUBSEQUENT_TRX_ID IS NULL
    AND 'C' = COM_ADJ.ADJUSTMENT_TYPE(+)
    AND A.COMPLETE_FLAG = 'Y'
    AND A.CUSTOMER_TRX_ID = P.CUSTOMER_TRX_ID
    AND A.CUST_TRX_TYPE_ID = TYPES.CUST_TRX_TYPE_ID
    AND L_TYPES.LOOKUP_TYPE = 'INV/CM/ADJ'
    AND A.PRINTING_OPTION IN ('PRI', 'REP')
    AND L_TYPES.LOOKUP_CODE =
    DECODE( TYPES.TYPE,'DEP','INV', TYPES.TYPE)
    AND NVL(T.PRINTING_LEAD_DAYS,0) > 0
    AND A.BILL_TO_SITE_USE_ID = U_BILL.SITE_USE_ID
    AND U_BILL.CUST_ACCT_SITE_ID = A_BILL.CUST_ACCT_SITE_ID
    AND A_BILL.PARTY_SITE_ID = PARTY_SITE.PARTY_SITE_ID
    AND B.PARTY_ID = PARTY.PARTY_ID
    AND LOC.LOCATION_ID = PARTY_SITE.LOCATION_ID
    AND NVL(LOC.LANGUAGE,'US') = 'US'
    AND NVL(P.TERMS_SEQUENCE_NUMBER,TL.SEQUENCE_NUM)=TL.SEQUENCE_NUM
    AND NVL(P.AMOUNT_DUE_REMAINING,0) <> 0
    AND A.CUST_TRX_TYPE_ID = 1
    AND TYPES.TYPE = 'INV'
    AND T.TERM_ID = P.TERM_ID
    AND TL.TERM_ID(+) = T.TERM_ID
    AND A.PRINTING_PENDING = 'Y'
    AND P.TERMS_SEQUENCE_NUMBER > NVL(A.LAST_PRINTED_SEQUENCE_NUM,0)
    MSG-00100: DEBUG: BeforeReport_Trigger -
    MSG-05000: DEBUG: Trx No... 1010441
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00010: 06:47 1 Transaction: 1010441
    MSG-00001: Line type : Line
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-05000: DEBUG: Remit To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: PO Box 849991
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: Dallas
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: TX
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 75284
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name:
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 6
    MSG-05000: DEBUG: Height Max: 6
    MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
    Dallas TX 75284
    MSG-05000: DEBUG: Trx No... 1010442
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00010: 06:47 2 Transaction: 1010442
    MSG-05000: DEBUG: Bill To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 6560 W ROGERS CIR
    MSG-05000: DEBUG: Address 2: STE 19
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: BOCA RATON
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: FL
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 33487-2746
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: THE BRACE SHOP
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name: LORI
    MSG-05000: DEBUG: Last Name: ESCALANTE
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Bill To Formatted... LORI ESCALANTE
    THE BRACE SHOP
    6560 W ROGERS CIR
    STE 19
    BOCA RATON FL 33487-2746
    MSG-05000: DEBUG: Ship To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 7014 E Appleton Circle
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: CENTENNIAL
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: CO
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 80112-1155
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: Kenneth Grimm
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Ship To Formatted... Kenneth Grimm
    7014 E Appleton Circle
    CENTENNIAL CO 80112-1155
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00100: Oracle Error in call to arp_adds.location_description -6503
    MSG-05000: DEBUG: Remit To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: PO Box 849991
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: Dallas
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: TX
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 75284
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name:
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 6
    MSG-05000: DEBUG: Height Max: 6
    MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
    Dallas TX 75284
    MSG-05000: DEBUG: Trx No... 1010930
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00010: 06:47 506 Transaction: 1010930
    MSG-05000: DEBUG: Bill To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 4412 MANILLA ROAD SE
    MSG-05000: DEBUG: Address 2: UNIT 7
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: CALGARY
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State:
    MSG-05000: DEBUG: Province: ALBERTA
    MSG-05000: DEBUG: Postal Code: T2G 4B7
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: CA
    MSG-05000: DEBUG: Customer Name: MEDLINES INC DBA PRO CARE MEDICAL LTD
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Bill To Formatted... Attn: Accounts Payable
    MEDLINES INC DBA PRO CARE MEDICAL LTD
    4412 MANILLA ROAD SE
    UNIT 7
    CALGARY ALBERTA T2G 4B7
    Canada
    MSG-05000: DEBUG: Ship To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 4412 MANILLA ROAD SE Unit 7
    MSG-05000: DEBUG: Address 2: PH:403 287 0993
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: CALGARY
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: ALBERTA
    MSG-05000: DEBUG: Province: ALBERTA
    MSG-05000: DEBUG: Postal Code: T2G 4B7
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: CA
    MSG-05000: DEBUG: Customer Name: MEDLINES INC DBA PRO CARE MEDICAL LTD
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Ship To Formatted... MEDLINES INC DBA PRO CARE MEDICAL LTD
    4412 MANILLA ROAD SE Unit 7
    PH:403 287 0993
    CALGARY ALBERTA ALBERTA T2G 4B7
    Canada
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-05000: DEBUG: Remit To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: PO Box 849991
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: Dallas
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: TX
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 75284
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name:
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 6
    MSG-05000: DEBUG: Height Max: 6
    MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
    Dallas TX 75284
    MSG-05000: DEBUG: Bill To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 8206 LEESBURG PIKE
    MSG-05000: DEBUG: Address 2: STE 409
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: VIENNA
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: VA
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 22182
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name: TAYLOR
    MSG-05000: DEBUG: Last Name: CRIGLER
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Bill To Formatted... TAYLOR CRIGLER
    NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    8206 LEESBURG PIKE
    STE 409
    VIENNA VA 22182
    MSG-05000: DEBUG: Ship To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 8206 LEESBURG PIKE
    MSG-05000: DEBUG: Address 2: STE 409
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: VIENNA
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: VA
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 22182
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name: TAYLOR
    MSG-05000: DEBUG: Last Name: CRIGLER
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Ship To Formatted... TAYLOR CRIGLER
    NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    8206 LEESBURG PIKE
    STE 409
    VIENNA VA 22182
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    REP-0069: Internal error
    REP-57054: In-process job terminated:Finished successfully
    MSG-00100: DEBUG: BeforeReport_Trigger +
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Tax_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Message_Details
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Org_Profile.
    MSG-00100: DEBUG: Organization Id: 106
    MSG-00100: DEBUG: BeforeReport_Trigger.Build_Where_Clause
    MSG-00100: DEBUG: P_Choice: NEW
    MSG
    Report Builder: Release 10.1.2.3.0 - Production on Tue Jan 22 06:47:00 2013
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Program exited with status 1
    Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 945196.
    Review your concurrent request log and/or report output file for more detailed information.
    Successfully resubmitted concurrent program XXBREG_RAXINV_NEW_XMLP with request ID 953242 to start at 23-JAN-2013 05:15:00 (ROUTINE=AFPSRS)
    Executing request completion options...
    Output file size:
    13010844
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 945196 on node EBSAPPPROD at 22-JAN-2013 06:49:36.
    Post-processing of request 945196 completed at 22-JAN-2013 06:49:59.
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 22-JAN-2013 06:49:59
    Regards,
    Smita

    Hi,
    Since you said the behavior is sporadic and also the program was running good in 11i instance, I think its a problem with the data [or select query in the concurrent program] .
    Ideal scenario:
    1. Upon the concurrent program completing in error the pdf should not be generated in first place, since it misguides the obtained report. [Concurrent Program should be modified accordingly, before calling the pdf generation logic you need to check the status of the concurrent program].
    2. It is not likely that the pdf generation should error out upon concurrent program's error, since the concurrent program could have a soft closure of its schema definition [inspite of an uncaught/unhandled exception]
    eg:
    <schema def>
    <Xml element 1> </Xml element 1>
    <Xml element 2> </Xml element 2>
    <Xml element 3> </Xml element 3>
    *_ <while generating elements 4, 5 and so on concurrent program could have errored out, but still the schema definition is valid so the pdf is generated>_*
    </schema def>
    Solution:
    Next time when you get the same behaviour, try running the concurrent program and handle the exception for that scenario, this should resolve your issue.
    Regards,
    Yuvaraj

  • XML Publisher Report Bursting Program (XDOBURSTREP) is failing after ATG7

    Hello
    After upgrading ATG RUP7, we have issue related to the XML Bursting Program.
    XML Publisher Report Bursting Program (XDOBURSTREP Short Name) is failing with error when there is no output is generated by the Oracle Report, this was working fine before the ATG RUP7.
    Oracle XML Publisher Template Builder for Word
    Version 5.6 Build 45
    Oracle RDBMS : 10.2.0.4.0
    Oracle Applications : 11.5.10.2
    Concurrent Program: XML Publisher Report Bursting Program
    Concurrent Short Name:XDOBURSTREP
    Executable: XDOBURSTRPT
    The following is the log file of Bursting
    XDOBURSTREP module: XML Publisher Report Bursting Program
    Current system time is 22-OCT-2010 08:41:09
    0.932: [GC 0.932: [DefNew: 1792K->191K(1984K), 0.0190521 secs] 1792K->243K(6080K), 0.0193017 secs] [Times: user=0.01 sys=0.00, real=0.02 secs]
    1.637: [GC 1.638: [DefNew: 1983K->45K(1984K), 0.0279269 secs] 2035K->283K(6080K), 0.0281136 secs] [Times: user=0.03 sys=0.00, real=0.03 secs]
    2.369: [GC 2.369: [DefNew: 1837K->192K(1984K), 0.0249747 secs] 2075K->597K(6080K), 0.0251559 secs] [Times: user=0.02 sys=0.00, real=0.03 secs]
    3.186: [GC 3.186: [DefNew: 1984K->130K(1984K), 0.0208499 secs] 2389K->713K(6080K), 0.0210453 secs] [Times: user=0.02 sys=0.01, real=0.02 secs]
    3.938: [GC 3.939: [DefNew: 1922K->114K(1984K), 0.0219872 secs] 2505K->825K(6080K), 0.0221742 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
    4.781: [GC 4.781: [DefNew: 1906K->192K(1984K), 0.0271288 secs] 2617K->1258K(6080K), 0.0273437 secs] [Times: user=0.03 sys=0.00, real=0.03 secs]
    4.931: [GC 4.931: [DefNew: 1983K->192K(1984K), 0.0114155 secs] 3049K->1575K(6080K), 0.0116308 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
    4.978: [GC 4.978: [DefNew: 1974K->1K(1984K), 0.0032511 secs] 3357K->1415K(6080K), 0.0034360 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
    5.001: [GC 5.001: [DefNew: 1790K->34K(1984K), 0.0020751 secs] 3204K->1448K(6080K), 0.0022582 secs] [Times: user=0.01 sys=0.01, real=0.00 secs]
    5.023: [GC 5.023: [DefNew: 1814K->68K(1984K), 0.0021542 secs] 3228K->1481K(6080K), 0.0023365 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
    5.273: [GC 5.273: [DefNew: 1860K->119K(1984K), 0.0055906 secs] 3273K->1533K(6080K), 0.0057779 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
    5.451: [GC 5.451: [DefNew: 1911K->58K(1984K), 0.0059780 secs] 3325K->1587K(6080K), 0.0061632 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
    5.653: [GC 5.653: [DefNew: 1850K->103K(1984K), 0.0034036 secs] 3379K->1632K(6080K), 0.0035865 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
    5.813: [GC 5.813: [DefNew: 1895K->86K(1984K), 0.0053900 secs] 3424K->1667K(6080K), 0.0055748 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
    5.932: [GC 5.932: [DefNew: 1878K->124K(1984K), 0.0035633 secs] 3459K->1705K(6080K), 0.0037447 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
    6.057: [GC 6.057: [DefNew: 1916K->147K(1984K), 0.0043476 secs] 3497K->1760K(6080K), 0.0045299 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
    6.214: [GC 6.214: [DefNew: 1939K->192K(1984K), 0.0120992 secs] 3552K->2141K(6080K), 0.0122907 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
    XML/BI Publisher Version : 5.6.3
    Updating request description
    Retrieving XML request information
    Preparing parameters
    7.104: [GC 7.104: [DefNew: 1982K->192K(1984K), 0.0200714 secs] 3932K->2346K(6080K), 0.0202692 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
    Set Bursting parameters..
    Bursting propertes.....
    {user-variable:cp:territory=US, user-variable:cp:ReportRequestID=16649488, user-variable:cp:language=en, user-variable:cp:responsibility=23202, user-variable.OA_MEDIA=http://d1at2.atco.ca:8010/OA_MEDIA, burstng-source=EBS, user-variable:cp:DebugFlag=N, user-variable:cp:parent_request_id=16649488, user-variable:cp:locale=en-US, user-variable:cp:user=URU4.ASHAFI, user-variable:cp:application_short_name=XDO, user-variable:cp:request_id=16649506, user-variable:cp:org_id=43, user-variable:cp:reportdescription=XXPAY Database Audit Series Change Register}
    Start bursting process..
    7.845: [GC 7.845: [DefNew: 1984K->158K(1984K), 0.0181146 secs] 4138K->2495K(6080K), 0.0183025 secs] [Times: user=0.01 sys=0.00, real=0.02 secs]
    7.885: [GC 7.885: [DefNew: 231K->14K(1984K), 0.0055622 secs]7.891: [Tenured[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor2]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor1]
    : 2486K->2073K(4096K), 0.2881229 secs] 2568K->2073K(6080K), 0.2940010 secs] [Times: user=0.29 sys=0.02, real=0.29 secs]
    8.682: [GC 8.682: [DefNew: 1787K->170K(1984K), 0.0120166 secs] 5861K->4243K(6080K), 0.0122079 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
    9.163: [GC 9.163: [DefNew: 1524K->74K(1984K), 0.0086781 secs]9.171: [Tenured: 4237K->2299K(4352K), 0.2773675 secs] 5597K->2299K(6336K), 0.2863681 secs] [Times: user=0.28 sys=0.00, real=0.29 secs]
    9.472: [GC 9.473: [DefNew: 90K->17K(1984K), 0.0025361 secs]9.475: [Tenured: 4299K->2311K(6104K), 0.2718601 secs] 4390K->2311K(8088K), 0.2747072 secs] [Times: user=0.28 sys=0.00, real=0.27 secs]
    9.822: [GC 9.822: [DefNew: 585K->42K(1984K), 0.0027399 secs]9.825: [Tenured: 4311K->2085K(6104K), 0.3354828 secs] 4897K->2085K(8088K), 0.3385340 secs] [Times: user=0.34 sys=0.00, real=0.34 secs]
    Bursting process complete..
    Generating Bursting Status Report..
    --Exception
    /oracle/appl/orad1at2/product/comn/temp/102210_084117484/AUDIT_GS_BI-WEEKLY.pdf (No such file or directory)
    java.io.FileNotFoundException: /oracle/appl/orad1at2/product/comn/temp/102210_084117484/AUDIT_GS_BI-WEEKLY.pdf (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at java.io.FileInputStream.<init>(FileInputStream.java:66)
         at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.zipOutputFiles(JCP4XDOBurstingEngine.java:532)
         at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:299)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
    Heap
    def new generation total 1984K, used 194K [0xb1000000, 0xb1220000, 0xb4780000)
    eden space 1792K, 10% used [0xb1000000, 0xb1030a98, 0xb11c0000)
    from space 192K, 0% used [0xb11c0000, 0xb11c0000, 0xb11f0000)
    to space 192K, 0% used [0xb11f0000, 0xb11f0000, 0xb1220000)
    tenured generation total 6104K, used 4085K [0xb4780000, 0xb4d76000, 0xd0400000)
    the space 6104K, 66% used [0xb4780000, 0xb4b7d490, 0xb4b7d600, 0xb4d76000)
    compacting perm gen total 12288K, used 7424K [0xd0400000, 0xd1000000, 0xd8400000)
    the space 12288K, 60% used [0xd0400000, 0xd0b402a8, 0xd0b40400, 0xd1000000)
    ro space 8192K, 80% used [0xd8400000, 0xd8a73430, 0xd8a73600, 0xd8c00000)
    rw space 12288K, 59% used [0xd8c00000, 0xd9330510, 0xd9330600, 0xd9800000)
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Executing request completion options...
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 22-OCT-2010 08:41:20
    Any Help Appreciated
    Thanks

    Hi;
    Similar issue mention at below notes, Please review:
    NPE Error While Bursting Using XDOBURSTREP in EBS R12 [ID 754790.1]
    Bursting Engine Ends With Java.Lang.Nullpointerexception[Article ID 559443.1]
    XDOBURSTREP - XML Publisher Report Bursting Program Fails with InvalidPropertyValueException[Article ID 603424.1]
    If its not help I suggest rise SR
    Regard
    Helios

Maybe you are looking for

  • Files are not applying in Stand by server.

    Hi All, We are getting the bellow error in standby server while applying log files. Media Recovery Log /oracle/DB7/saparch/DB7arch1_97211_627008903.dbf Errors with log /oracle/DB7/saparch/DB7arch1_97211_627008903.dbf ORA-310 signalled during: ALTER D

  • Connecting 2 Bw systems to the one R/3.

    Hi, Could you please explain the risk and impact while Connecting 2 Bw systems to the one R/3. And also i need information How the delta queues( RSA7) will be available  for a single datasource. Regards, Kranthi

  • Workflow not starting in QA

    Hi, I have created and tested WF in DEV but after transporting to QA, WF in not starting in QA. I ran SWU_OBUF and WF_BATCH is also available in QA. I checked SWETYPV and link is active there. I have used SAP_WAPI_CREATE_EVENT for the WF. This FM is

  • BOBJ 3.1 DI Install Issues

    I had no trouble at all on the core BOBJ EDGE 3.1 (Step 1) using the Express Install (MySQL DB all local).  When it came to Step 2 - Install Data Integrator I had numerous issues.  1) The install doc for this portion was not in the base package that

  • ACR 5.6 for Photoshop Elements 7?

    Hello, The release candidate of Adobe Camera Raw 5.6 includes support for Canon G11 and is available for Photoshop.  I have a Canon G11, but use Photoshop Elements 7.  Will the final release of Adobe Camera Raw 5.6 include support for Canon G11 and b