Xml publisher generate huge size excel file
hi,
we use xml publisher to generate excel file.
the problem is:
when there are over 100,000 rows, the excel file size will be very very huge,and it will take very very long time to open it.
i open the excel file with UltraEdit and find it is filled with html sytax.
When that excel file is opened with excel and saved as .xls file, the size will be dramatically reduced.
anyone can help?
Hello
I am getting the same problem, the EXCEL output file size is huge.
What I notice that it is stored as Web Pages *.htm; *.html (Save as Type) in Excel this is the reason it is huge.
If I save as Microsoft Office Excel Workbook *.xls it Reduce the size.
I don't know how to save as *.xls through XML Publlisher.
Any body knows? please Help..
Thanks.
Similar Messages
-
Generate and disaply excel file as iview in ep6?
Hello, everybody.
I built a iView in EP5 that can generate and display excel file on the run-time. I used contecttype in httpservletresponse to set the content type to excel so the browser will see the data as excel.
But it looks like the setcontenttype for httpservletresponse does not work anymore in EP6, does anybody know how to make the broswer "sees" the data as an excel file in EP6?
I am using EP6 SP9Hi Gary,
you definitely can set the content type if you call an AbstractPortalComponent and set all things within method doOnNodeReady (search for both terms on SDN forums, you'll find a heap of hints).
In addition, I don't know if you create "real" Excel data or use the html trick. If you don't know the latter, see Export Portal data to Excel
Hope it helps
Detlev -
Generate and display excel file
Hi guys,
Is there a way to generate and display excel file in sapgui without the need of downloading the excel file to local directory first?
I found the following 2 ways of doing it, but both require me to download the generated xls file to local directory:
#1 way:
1. Generate the xls file using GUI_DOWNLOAD with the filename = 'c:\test.xls'.
2. Call fm SAP_STARTS_EXCEL and pass in the parameter i_filename = 'c:\test.xls'
#2 way:
1. Generate the xls file using GUI_DOWNLOAD with the filename = 'c:\test.xls'.
2. Upload it back using the below so that i can get it in xstring format.
CALL FUNCTION 'GUI_UPLOAD'
exporting
filetype = 'BIN'
filename = 'C:\test.xls'
tables
data_tab = itab.
3. Then pass it to the cl_gui_html_viewer to display it.
call method html_control->load_data
exporting
url = 'test.xls'
type = 'application'
subtype = 'vnd.ms-excel'
importing
assigned_url = l_url
changing
data_table = l_pdf_data
exceptions
others = 1.
I prefer the #2 way as my program will get wrapped thru ITS server, and it seems the #1 way will not work. So is there any way i can get the excel file to be generated in xstring format so that i can pass to cl_gui_html_viewer straight away to display without having to save to local directory first?
Any other suggestion apart from the above 2 ways are welcome as well.
Thanks guys.Use function module ALV_XXL_CALL. It will solve ur prob immediately.
REPORT ZSKC_ALV_XXL.
TYPE-POOLS : KKBLO.
DATA : ITAB LIKE T100 OCCURS 0,
T_FCAT_LVC TYPE LVC_S_FCAT OCCURS 0 WITH HEADER LINE,
T_FCAT_KKB TYPE KKBLO_T_FIELDCAT.
START-OF-SELECTION.
* Get data.
SELECT * UP TO 20 ROWS
FROM T100
INTO TABLE ITAB
WHERE SPRSL = SY-LANGU.
CHECK SY-SUBRC EQ 0.
* Create the field catalog.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
EXPORTING
I_STRUCTURE_NAME = 'T100'
CHANGING
CT_FIELDCAT = T_FCAT_LVC[]
EXCEPTIONS
INCONSISTENT_INTERFACE = 1
PROGRAM_ERROR = 2
OTHERS = 3.
CHECK SY-SUBRC EQ 0.
* make sure you pass the correct internal table name in the field catalog.
t_fcat_lvC-tabname = 'ITAB'.
MODIFY T_FCAT_LVC TRANSPORTING TABNAME WHERE TABNAME NE SPACE.
* Transfer to KKBLO format.
CALL FUNCTION 'LVC_TRANSFER_TO_KKBLO'
EXPORTING
IT_FIELDCAT_LVC = T_FCAT_LVC[]
IMPORTING
ET_FIELDCAT_KKBLO = T_FCAT_KKB
EXCEPTIONS
IT_DATA_MISSING = 1
IT_FIELDCAT_LVC_MISSING = 2
OTHERS = 3.
CHECK SY-SUBRC EQ 0.
* Call XXL.
CALL FUNCTION 'ALV_XXL_CALL'
EXPORTING
I_TABNAME = 'ITAB'
IT_FIELDCAT = T_FCAT_KKB
TABLES
IT_OUTTAB = ITAB[]
EXCEPTIONS
FATAL_ERROR = 1
NO_DISPLAY_POSSIBLE = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
ENDIF.
It will open the Excel in front of you and populate the cells from your internal table
with color for Key columns.
Cheers
SKC. -
XML Publisher report not printing excel output due to special characters
Hello,
I am trying to create a xml publisher report which should display the output in excel. But the program completes with a warning status and the output is displayed as XML instead of excel, with some errors "An invalid character was found in text content. Error processing resource " and i think these errors are due to the special characters(eg: city/province - A Coruña, Cáceres). If i give rownum < 10 in my query, where there are no such characters it works fine and i am getting an excel output.
Tried changing the XML encoding and it doesn't help (both mentioned below)
<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml version="1.0" encoding="UTF-8"?>
Do anyone have a solution for this
Thanks in advance
Edited by: user10317098 on Jan 16, 2012 10:58 AMHi,
Check this links that might help you..
https://forums.oracle.com/thread/1018488
http://docs.oracle.com/cd/E10091_01/doc/bip.1013/e05000/toc.htm
Here the Exact solution from Oracle
In the XML PUBLISHER ADMINISTRATOR Resp..
Click the administration..
then Click HTML Output
Then in the Base Image URI Give the url of your application for example
http://Test.Test.com:8000/OA_MEDIA/
And then
Image File Directory give this as per your application setup
/u01/app/oracle/apps/apps_st/comn/java/classes/oracle/apps/media/
Thanks & Regards
Srikkanth.M -
XML publisher output report in excel format
Hi
I have created reports using XML Publisher, the default output preview format was PDF. While submitting the program, in the layout, I changed the format to EXCEL,it give me output in Excel. Now I need to send the output report as an attachment through e-mail.For this I have used a UNIX shell script to send the mail using uuencode and mailx commands.
I have fetched the name of the report from table using the following command.
SELECT file_name
FROM FND_CONC_REQ_OUTPUTS
WHERE FCR.CONCURRENT_REQUEST_ID = p_req_id;
The name of the report is : XXBG_PO_IFACE_SO_RPT_8556321_1.EXCEL
Following is the command to send the e-mail.
(cat $MAIL_BODY; uuencode XXBG_PO_IFACE_SO_RPT_8556321_1.EXCEL XXBG_PO_RPT.xls) | mailx -m -s "$MAIL_SUBJECT" $mail_id
I am receiving the mail with the attachement, but when i am trying to open the attachement it is throwing an error and nothing is displayed in the excel sheet.
Note: When I am sending the mail,in similar way, with 'PDF' attachement it is perfectly fine and the attachement is opening correctly.
Please help me.
Thanks in advance,
Madhu kumarHi schavali,
The error message is as follows
Microsoft Office Excel cannot access the file "https://xxxxxxx/Inbox/XXBG_PO_RPT.xls.
There are several possible reasons:
--The file path doesnot exist.
--The file is being used by another program.
--The workbook you are trying to save has the same name as a currently open workbook.
After throwing the error, it open s a balck excel sheet.
Hi hsawwan,
I have gone through the thread. I am able to see the report when I click the output tab on the concurrent request screen.
But the problem is, when I am sending the output report as an excel attachment then I am facing the problem.
There might be some problem with uuenocde or mailx command.
Thanks
Madhu Kumar. -
XML Publisher with output type EXCEL is taking time to finish than for PDF
Hi Guru's,
I got a strange problem.
When i submit a report by choosing output format type as EXCEL, it is taking much time to complete. The same report if i choose PDF finishing in half of the time of EXCEL report. Also when we go with "view output" it is taking 4 mins to show the output. Total number of records existed are 6000 only.
Please suggest me the solutions or alternatives if any.
Thanks in advance and waiting for your response.
Regards,
Phani Reddyit is taking much time to complete. The same report if i choose PDF finishing
in half of the time of EXCEL report. Excel is a complicated and proprietary file format. Whilst I know nothing about XML Publisher I do know that putting any sort of output into Excel format takes a long time. It's because it has to be done on a cell-by-cell basis. It's much faster to blat stuff out row-by-row.
Cheers, APC
Blog : http://radiofreetooting.blogspot.com/ -
XML Publisher does not attached pdf file java.lang.StackOverflowError
Hi there
I have Bursting program which email the pdf report, some times when I have all of data the report does not attached and send to the user, I get following messages in log file.
XML Publisher 5.6 Build 45
Oracle 11.5.10.2
Set Bursting parameters..
Start bursting process..
[081409_034350119][oracle.apps.xdo.batch.bursting.ProcessCoreDocument][EXCEPTION] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java:624)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:421)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:233)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1657)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:967)
at oracle.apps.xdo.batch.bursting.ProcessDocument.processTemplate(ProcessDocument.java:321)
at oracle.apps.xdo.batch.bursting.ProcessCoreDocument.processLayout(ProcessCoreDocument.java:112)
at oracle.apps.xdo.batch.BurstingProcessorEngine.addDocument2Queue(BurstingProcessorEngine.java:3206)
at oracle.apps.xdo.batch.BurstingProcessorEngine.createBurstingDocument(BurstingProcessorEngine.java:2112)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstDocument(BurstingProcessorEngine.java:2054)
at oracle.apps.xdo.batch.BurstingProcessorEngine.globalDataEndElement(BurstingProcessorEngine.java:1965)
at oracle.apps.xdo.batch.BurstingProcessorEngine.endElement(BurstingProcessorEngine.java:1124)
at oracle.xml.parser.v2.XMLContentHandler.endElement(XMLContentHandler.java:196)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1212)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingRequest(BurstingProcessorEngine.java:2153)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingEndElement(BurstingProcessorEngine.java:1802)
at oracle.apps.xdo.batch.BurstingProcessorEngine.endElement(BurstingProcessorEngine.java:1127)
at oracle.xml.parser.v2.XMLContentHandler.endElement(XMLContentHandler.java:196)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1212)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:227)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:959)
at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:903)
at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:269)
at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
Caused by: java.lang.StackOverflowError
at sun.text.normalizer.NormalizerBase.getNextNorm32(NormalizerBase.java:1268)
at sun.text.normalizer.NormalizerBase.access$1100(NormalizerBase.java:127)
at sun.text.normalizer.NormalizerBase$IsNextNFDSafe.isNextBoundary(NormalizerBase.java:1306)
at sun.text.normalizer.NormalizerBase.findNextIterationBoundary(NormalizerBase.java:1359)
at sun.text.normalizer.NormalizerBase.next(NormalizerBase.java:1436)
at sun.text.normalizer.NormalizerBase.nextNormalize(NormalizerBase.java:1473)
at sun.text.normalizer.NormalizerBase.next(NormalizerBase.java:797)
at java.text.CollationElementIterator.next(CollationElementIterator.java:189)
at java.text.RuleBasedCollator.compare(RuleBasedCollator.java:367)
at oracle.xdo.parser.v2.XSLSort.compareObjects(XSLSort.java:500)
at oracle.xdo.parser.v2.XSLSort.partitionIt(XSLSort.java:463)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:411)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
[081409_034350129][][EXCEPTION] Error while generating the Document...
[081409_034350160][][EXCEPTION] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java:624)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:421)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:233)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1657)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:967)
at oracle.apps.xdo.batch.bursting.ProcessDocument.processTemplate(ProcessDocument.java:321)
at oracle.apps.xdo.batch.bursting.ProcessCoreDocument.processLayout(ProcessCoreDocument.java:112)
at oracle.apps.xdo.batch.BurstingProcessorEngine.addDocument2Queue(BurstingProcessorEngine.java:3206)
at oracle.apps.xdo.batch.BurstingProcessorEngine.createBurstingDocument(BurstingProcessorEngine.java:2112)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstDocument(BurstingProcessorEngine.java:2054)
at oracle.apps.xdo.batch.BurstingProcessorEngine.globalDataEndElement(BurstingProcessorEngine.java:1965)
at oracle.apps.xdo.batch.BurstingProcessorEngine.endElement(BurstingProcessorEngine.java:1124)
at oracle.xml.parser.v2.XMLContentHandler.endElement(XMLContentHandler.java:196)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1212)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingRequest(BurstingProcessorEngine.java:2153)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingEndElement(BurstingProcessorEngine.java:1802)
at oracle.apps.xdo.batch.BurstingProcessorEngine.endElement(BurstingProcessorEngine.java:1127)
at oracle.xml.parser.v2.XMLContentHandler.endElement(XMLContentHandler.java:196)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1212)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:227)
at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:959)
at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:903)
at oracle.apps.xdo.oa.cp.JCP4XDOBurstingEngine.runProgram(JCP4XDOBurstingEngine.java:269)
at oracle.apps.fnd.cp.request.Run.main(Run.java:161)
Caused by: java.lang.StackOverflowError
at sun.text.normalizer.NormalizerBase.getNextNorm32(NormalizerBase.java:1268)
at sun.text.normalizer.NormalizerBase.access$1100(NormalizerBase.java:127)
at sun.text.normalizer.NormalizerBase$IsNextNFDSafe.isNextBoundary(NormalizerBase.java:1306)
at sun.text.normalizer.NormalizerBase.findNextIterationBoundary(NormalizerBase.java:1359)
at sun.text.normalizer.NormalizerBase.next(NormalizerBase.java:1436)
at sun.text.normalizer.NormalizerBase.nextNormalize(NormalizerBase.java:1473)
at sun.text.normalizer.NormalizerBase.next(NormalizerBase.java:797)
at java.text.CollationElementIterator.next(CollationElementIterator.java:189)
at java.text.RuleBasedCollator.compare(RuleBasedCollator.java:367)
at oracle.xdo.parser.v2.XSLSort.compareObjects(XSLSort.java:500)
at oracle.xdo.parser.v2.XSLSort.partitionIt(XSLSort.java:463)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:411)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
at oracle.xdo.parser.v2.XSLSort.quicksortObjects(XSLSort.java:413)
Bursting process complete..
Generating Bursting Status Report..
Thanks
ASIMhave to see the template.
analyse in the order below.
1. the xmlp version you have might not support some features you have in template, remove sorts in template and try, it should work
2. there are latest patches, which has several features and performance enhancement above, 5.6.3+
take a latest xmlp patch for this.
3. other configuration for performance -
XML publisher report with a template file missing
I get the following error
Active template file not found in the template definition <TEMPLATE_NAME> for date <EFFDT>. (235,2515)
PSXP_RPTDEFNMANAGER.TemplateDefn.OnExecute Name:GetActiveTemplateFile PCPC:15872 Statement:346
but in
Reporting Tools > XML Publisher > Report Definition > Template tab
I did have the setting Effective date, what cause the problem?Have a look at following post and run the sql in this post to see if your template definition is missing.
http://peoplesoft.wikidot.com/xml-publisher-template-file-missing
You could also run Application Engine PSXPCLEAN to clean orphan rows.
Are you running the report online or through PeopleCode?
In last case make sure the effdt is set correct in PeopleCode.
Also have a look if your server time settings are correct.
Hakan -
Hi,
I have a query that I execute in the analyzer. It doesn't contain so many data...
When I save it as an excel, i still have a file of 2 MB...
I want to mail this file as an attachment, but this results in an explosion of megabytes in the mailbox...
The receiver just have to see the data, he doesn't have to connect to the BW server...
Is there any way to reduce the size of that excel-file?
Ciao
JokeHi
I don't know why copy and paste is not working. If you want to copy the only the data portion it won't work.
But if you select the whole sheet , you can copy and paste to the new excel file.
Regs
Gopi -
XML Publisher Email through Bursting Control File 11i EBS HRMS
Hi there
Is there any body tells me about the security of the XML Publisher Bursting?
I have to email hrms pdf data from XML Bursting, Is it secure?
Is there any document I can read about the security?
Asim
ThanksHi Gareth
Thanks for your reply.
Some how RTF Template Properties does not work for me. But I found another way to protect the pdf with password, through XML Publisher responsibility.
XML Publisher--
Templates > View Template: XXPER_TEMPLATE_NAME >
Edit Confirguration
Enable PDF Security = True
Open document password = abcd
When I try to open the document it ask the password. works fine for me.
Thanks
ASIM -
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,
SmitaHi,
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 -
Report Server Generating big size trace file
We are using Report Service which is part of 9iAS suite. Its generating a trace file (server name.trc). This file keeps growing and depending on the number of requests we receive sometimes its size goes in Giga bytes. Anybody knows why its doing that and how to get rid of this behavior ?
Tracing is useful for troubleshooting purposes. If you do not need tracing please open the file
$OH\reports\conf\server_name.conf
and comment the "trace" element. You will need to restart the server for this to take effect
<!--trace traceOpts="trace_all"/-->
Thanks
The Oracle Reports Team -
XML Publisher generating XML output vs. PDF
Hi
When I run the report directly as a concurrent program, it generates PDF without any problem. But when I submit the report via a package, it generates XML output.
Actually, the package submits multiple XMLP reports. All the XMLP report submissions generate PDF output without any problem, except one which generates XML output. What could be the reason? Please advise.
Regards,
Smitatry add layout
FND_REQUEST.ADD_LAYOUTbefore
fnd_request.submit_requestsmth
v_request_id number;
v_layout boolean;
begin
v_layout := FND_REQUEST.ADD_LAYOUT('XXCST','XXSHORTNAME','en','US','PDF');
v_request_id := fnd_request.submit_request(application => 'XXCST',
program => 'XXSHORTNAME',
description => NULL,
start_time => NULL,
sub_request => FALSE,
argument1 => p_date
... -
When running an xml publisher report the xml output leads to 9 mb and the excel output file leads to 20 mb. The records contained in excel file is 4000 records. When taking the excel records and copy to new excel file the excel file size is 3.5 mb only.Why does the oracle software generates 20mb file?
Does any one knows the answer please advice?Hello,
This issue is because the Excel output from BI Publisher is MHTML (XML Publisher generates XHTML) not binary .xls.
MHTML and XHTML are more verbose formats than binary .xls.
It will be large because the current Excel output is just an HTML and not compressed like PDF. Please use the workaround (save it as .xls file). This is a known limitation of RTF layout templates.
BI Publisher Enterprise has a new feature True Excel Templates. The layouts generate binary Excel output.
Excel Output File Size Generated By BI Publisher is Very Large (Doc ID 760437.1)
Bogdan -
XML Publisher question - Not generating a valid XML file
I am working through an Oracle document that walks you through creating an XML Pub report. I am using HCM 8.9, Tools 8.49.15 and it has XML Pub installed and I have the Microsoft plug-in installed
I have created a query and have downloaded an rtf template and now am on a page where you enter your data source and then click ‘Generate’ for the sample data file. I did it and it created ‘PERSONAL_DATA_PAY.XML’ which is created from a PS Query. However if I click on ‘PERSONAL_DATA_PAY.XML’ it generates a blocky text file that is not an XML file and I can’t go any further.
Do you know why it’s not generating a valid XML file when I click on 'generate'?
Thanks
Allen H. Cunningham
Data Base Administrator - Oracle/PeopleSoft
Sonoma State UniversityYou mean to say that you create a new data source by specifying Data Source Type as 'PS Query' and Data Source ID as your query name, you are not able to generate a valid XML file (by clicking on Generate link).
did you cross check your query by running it?
On field change of Generate link, PeopleSoft uses PSXP_RPTDEFNMANAGER and PSXP_XMLGEN app packagaes and query objects to create the file
It should work if you query is valid..
Maybe you are looking for
-
How can I convert mpeg/mpg videos file to a WMV file?
I need to convert a few mpeg/mpg video files to WMV. What program can I use to do this? Your help is greatly appreciated.
-
Problem to add ADCP-DEPARTMENT into maintenance view
Hi All, I need help urgently on creating a maintenance view of a customized table. The Customized Table name is ZTSUBCON, it contains fields below:- MANDT - Client BNAME - User Name in User Master Record ... (and other fields) I would like to
-
ImageIO.read stripping alpha channel
I've been chasing this one for the last few hours and haven't gotten anywhere. I've been trying to load a 32 bit bitmap (I'm using photoshop and I put a gradient on the alpha channel), and no matter what I do, I keep getting a 24 bit image from the a
-
Is there a way to use a progress bar with Xerces XML Parser?
My program is parsing very long XML files that take several minutes to parse. I am using Xerces as the parser. I would like to use a progress bar to show the progress, but I haven't found any way to get Xerces to give progress updates. Is this possib
-
Mysteries behind Zen Micro on 2.20
2.20.05 worked fine for a week, then the super drainage came back!!! I re-flashed it to 2.20.05 everytime I experienced this drain (at least 0 times now). Here's what i have discovered last night. Sleep Timer (off as usual) Idel shutdown (off for thi