R12.1.3 :- XML concurrent request giving completed and "WARNING"

Dear All,
One particular Concurrent request was not running fine.
Its show compleated* in Phase and in Status it showing *"warning"*.
Actually its a "Supplier Invoice Aging"
and the log file says like below
:++---------------------------------------------------------------------------++
XXXXX Custom Application: Version : UNKNOWN
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XXOMNSOS module: XXXXX Supplier Invoice Aging report
++---------------------------------------------------------------------------++
Current system time is 18-FEB-2011 11:24:40
++---------------------------------------------------------------------------++
++-----------------------------+
+| Starting concurrent program execution...+
++-----------------------------+
Arguments
P_COMP_FR='008'
P_COMP_TO='008'
P_VENDOR_ID='115'
p_account='320001'
P_PERIOD_TYPE='Weekly Aging'
p_as_of_date='2009/08/19 00:00:00'
+-- Start of Reports Command --+
+/ebiz/apps/TEST/inst/apps/TEST_odhdbtest/ora/10.1.2/bin/appsrwrun.sh+
P_CONC_REQUEST_ID=1429988
P_COMP_FR='008'
P_COMP_TO='008'
P_VENDOR_ID='115'
p_account='320001'
P_PERIOD_TYPE='Weekly Aging'
p_as_of_date='2009/08/19 00:00:00'
report=/ebiz/apps/TEST/apps/apps_st/appl/xxomn/12.0.0/reports/US/XXOMNSOS.rdf
batch=yes
destype=file
desname=/ebiz/apps/TEST/inst/apps/TEST_odhdbtest/logs/appl/conc/out/o1429988.out
desformat=XML
+-- End of Reports Command --+
Request language is :
AMERICAN
Request territory is :
AMERICA
Forcing NLS_NUMERIC_CHARACTERS to: '.,' for XDO processing
APPLLCSP Environment Variable set to :
Previous NLS_LANG Environment Variable was :
American_America.UTF8
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
+'.,'+
Enter Password:
Report Builder: Release 10.1.2.3.0 - Production on Fri Feb 18 11:24:41 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Reset original NLS_LANG in environment as :
American_America.UTF8
++---------------------------------------------------------------------------++
Start of log messages from FND_FILE
++---------------------------------------------------------------------------++
++---------------------------------------------------------------------------++
End of log messages from FND_FILE
++---------------------------------------------------------------------------++
++---------------------------------------------------------------------------++
Executing request completion options...
Output file size:
+12664+
++------------- 1) PUBLISH -------------++
Beginning post-processing of request 1429988 on node ODHDBTEST at 18-FEB-2011 11:24:55.
Post-processing of request 1429988 failed at 18-FEB-2011 11:24:56 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
++--------------------------------------++
++------------- 2) PRINT -------------++
Not printing the output of this request because post-processing failed.
++--------------------------------------++
Finished executing request completion options.
++---------------------------------------------------------------------------++
Concurrent request completed
Current system time is 18-FEB-2011 11:24:56
++---------------------------------------------------------------------------++
i have traced the concurrent request log file and its log says;-
[2/18/11 11:06:41 AM] [1926299:RT1429947] Completed post-processing actions for request 1429947.
[2/18/11 11:24:56 AM] [OPPServiceThread1] Post-processing request 1429988.
[2/18/11 11:24:56 AM] [1926299:RT1429988] Executing post-processing actions for request 1429988.
[2/18/11 11:24:56 AM] [1926299:RT1429988] Starting XML Publisher post-processing action.
[2/18/11 11:24:56 AM] [1926299:RT1429988]
Template code: XXOMNSOS
Template app: XXOMN
Language: en
Territory: US
Output type: RTF
[2/18/11 11:24:56 AM] [1926299:RT1429988] Output file was found but is zero sized - Deleted
[2/18/11 11:24:56 AM] [UNEXPECTED] [1926299:RT1429988] java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:570)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:235)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:182)
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:1665)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5936)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:302)
at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
Caused by: org.xml.sax.SAXParseException: <Line 1, Column 3>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.xdo.parser.v2.XMLError.flushErrorHandler(XMLError.java:441)
at oracle.xdo.parser.v2.XMLError.flushErrors1(XMLError.java:303)
at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:343)
at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:285)
at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:289)
... 16 more
[2/18/11 11:24:56 AM] [1926299:RT1429988] Completed post-processing actions for request 1429988.
[2/18/11 12:19:47 PM] [OPPServiceThread1] Post-processing request 1430104.
[2/18/11 12:19:47 PM] [1926299:RT1430104] Executing post-processing actions for request 1430104.
[2/18/11 12:19:47 PM] [1926299:RT1430104] Starting XML Publisher post-processing action.
I am not able to understand this,, Is this a issue of DBA or Functional or Developers ??
i have refered few documents here i would like to mention
1) Troubleshooting Oracle XML Publisher For The Oracle E-Business Suite [ID 364547.1]
2) R12: Tax Reconciliation By Taxable Account: Post-Processing Action Failed [ID 740223.1]
3) Statement Generation Program ending in XDOException "java.lang.reflect.InvocationTargetException" [ID 869522.1]
i througly checked with the above 3rd Document, ever settings are very fine,, no changes in this,, then i bounced the concurrent. the notes says ths problem may occure because of insufficient of space or not proper setup of xml, !;(
Can any one kindly tell me from where i have to start,, ;(
Thanks in Advance
Hameed
Edited by: Hameed on Feb 18, 2011 6:37 AM

Yes ,, there is some data's
encoding="UTF-8"?>
++
+<T04101344>+
+<LIST_G_COM_ACC>+
+<G_COM_ACC>+
+<COMACC>008320001</COMACC>+
+<ACCOUNT>Trade Payables[320001]</ACCOUNT>+
+<COMPANY>OP08-BINARY</COMPANY>+
+<LIST_G_VEN>+
+<G_VEN>+
+<VENDOR_NAME>XXXXXXX</VENDOR_NAME>+
+<LIST_G_INV>+
+<G_INV>+
+<INV_CURR>AED</INV_CURR>+
+<VENDOR_NAME1>XXXXXX</VENDOR_NAME1>+
+<PAID_AMOUNT>404167</PAID_AMOUNT>+
+<INVOICE_NUM>2652</INVOICE_NUM>+
+<DUE_DATE>27-NOV-08</DUE_DATE>+
+<INVOICE_AMOUNT>416668</INVOICE_AMOUNT>+
+<DUE_DAYS>265</DUE_DAYS>+
+<AMOUNT_REMAINING>12501</AMOUNT_REMAINING>+
+<AMT_PER>3</AMT_PER>+
+<DUE1></DUE1>+
+<DUE2></DUE2>+
+<DUE3></DUE3>+
+<DUE4></DUE4>+
+<DUE5>12501</DUE5>+
+<DUE6></DUE6>+
+<DUE7></DUE7>+
+<CF_1></CF_1>+
+</G_INV>+
+<G_INV>+
+<INV_CURR>AED</INV_CURR>+
+<VENDOR_NAME1>XXXXXX</VENDOR_NAME1>+
+<PAID_AMOUNT>104167</PAID_AMOUNT>+
+<INVOICE_NUM>2668</INVOICE_NUM>+
+<DUE_DATE>27-NOV-08</DUE_DATE>+
+<INVOICE_AMOUNT>208334</INVOICE_AMOUNT>+
+<DUE_DAYS>265</DUE_DAYS>+
+<AMOUNT_REMAINING>104167</AMOUNT_REMAINING>+
+<AMT_PER>50</AMT_PER>+
+<DUE1></DUE1>+
+<DUE2></DUE2>+
+<DUE3></DUE3>+
+<DUE4></DUE4>+
+<DUE5>104167</DUE5>+
+<DUE6></DUE6>+
+<DUE7></DUE7>+
+<CF_1></CF_1>+
+</G_INV>+
+<G_INV>+
+<INV_CURR>AED</INV_CURR>+
+<VENDOR_NAME1>XXXXXX</VENDOR_NAME1>+
+<PAID_AMOUNT>104167</PAID_AMOUNT>+
+<INVOICE_NUM>2696</INVOICE_NUM>+
+<DUE_DATE>29-NOV-08</DUE_DATE>+
+<INVOICE_AMOUNT>208334</INVOICE_AMOUNT>+
+<DUE_DAYS>263</DUE_DAYS>+
+<AMOUNT_REMAINING>104167</AMOUNT_REMAINING>+
+<AMT_PER>50</AMT_PER>+
+<DUE1></DUE1>+
+<DUE2></DUE2>+
+<DUE3></DUE3>+
+<DUE4></DUE4>+
+<DUE5>104167</DUE5>+
+<DUE6></DUE6>+
+<DUE7></DUE7>+
+<CF_1></CF_1>+
+</G_INV>+
+<G_INV>+
Tail of the .out file
+</LIST_G_COM_ACC>+
+<DUE1_RANGE_FR>1</DUE1_RANGE_FR>+
+<DUE2_RANGE_FR>8</DUE2_RANGE_FR>+
+<DUE3_RANGE_FR>15</DUE3_RANGE_FR>+
+<DUE4_RANGE_FR>22</DUE4_RANGE_FR>+
+<DUE5_RANGE_FR>29</DUE5_RANGE_FR>+
+<DUE6_RANGE_FR></DUE6_RANGE_FR>+
+<DUE7_RANGE_FR></DUE7_RANGE_FR>+
+<DUE1_RANGE_TO>7</DUE1_RANGE_TO>+
+<DUE2_RANGE_TO>14</DUE2_RANGE_TO>+
+<DUE3_RANGE_TO>21</DUE3_RANGE_TO>+
+<DUE4_RANGE_TO>28</DUE4_RANGE_TO>+
+<DUE5_RANGE_TO>9999</DUE5_RANGE_TO>+
+<DUE6_RANGE_TO></DUE6_RANGE_TO>+
+<DUE7_RANGE_TO></DUE7_RANGE_TO>+
+<TITLE1>1 Week</TITLE1>+
+<TITLE2>2 Weeks</TITLE2>+
+<TITLE3>3 Weeks</TITLE3>+
+<TITLE4>4 Weeks</TITLE4>+
+<TITLE5>Over 4 weeks</TITLE5>+
+<TITLE6></TITLE6>+
+<TITLE7></TITLE7>+
+<DUE1_NET>325307.5</DUE1_NET>+
+<DUE2_NET></DUE2_NET>+
+<DUE3_NET></DUE3_NET>+
+<DUE4_NET></DUE4_NET>+
+<DUE5_NET>1071029</DUE5_NET>+
+<DUE6_NET></DUE6_NET>+
+<DUE7_NET></DUE7_NET>+
+<AMT_REM_NET>1396336.5</AMT_REM_NET>+
+<P_VENDOR_NAME>XXXXXX</P_VENDOR_NAME>+
+<P_COMPANY_FR>OP08-BINARY</P_COMPANY_FR>+
+<P_COMPANY_TO>OP08-BINARY</P_COMPANY_TO>+
+<P_PERIOD_NAME>Weekly Aging</P_PERIOD_NAME>+
+<P_ACCOUNT_NAME>Trade Payables</P_ACCOUNT_NAME>+
+<P_DATE>2009/08/19 00:00:00</P_DATE>+
+</T04101344>+
These are the data's its showing.. :(
Regards,
Hameed

Similar Messages

How To Schedule a Concurrent Request on completion of a Spawned Request

As soon as the concurrent request submitted through Oracle Form(Consolidation Transfer)is completed we need to schedule another Concurrent Request which had to be kicked off automatically on completion of the First concurrent request. Since, the First concurrent request of Consolidation Transfer is a Spawned Program, the request set could not be created, to kick off the second concurrent program.
I would Appreciate if anyone can advise any solution to achieve this objective.

Hi Harish,
Doesn't matter what you need to do all you need is the hook!
a) Nice. Force the request to print and use print driver to call CONCSUB to submit your new "child" request
-- Since the Consolidation Trasnfer concurrent request could only be submitted through Consolidation Trasnfer Form only, I am not sure how we can do Force Print for this request.
GR: Set printer and style on concurrent program definition. Set profile option "Concurrent:Report Copies" to 1 (even by Forms Personalization if you want to). Sorted. Still think this is the best option.
c) Abstraction. Replace the C executable with a shell script that takes arguments and calls the C program and then submits new "child" request via CONCSUB
-- Appreciate, if you can elaborate this option. I think we can try this, with the help of your detailed input.
GR: Change the executable on the concurrent program to a host shell script under your mods application. Initially just get the shell script to capture program call and arguments. Run the program to get arguments. Next iteration, change shell script to call the C program from your shell script with correct arguments. Verify okay. Next iteration do the same plus call CONCSUB to submit request / set.
d) Nasty. Trigger on fnd_concurrent_requests to call new "child" request via fnd_request.submit_request - NB: very unsupported! Make sure trigger doesn't raise an exception.
-- On completion of the Consolidation Transfer concurrent request, we tried to submit the request set using the Trigger on Consolidation History table and/or fnd_concurrent_requests table. But it is entering into infinite loop.
GR: Need to use trigger condition to capture update of status_code to C (Completed) and other codes e.g. Warning. Personally I'd avoid this option because you have others! Although once I did use this method when I wanted absolute transparency :-)
Update: Changed "Print: Copies" to "Concurrent:Report Copies"
Regards,
Gareth
Edited by: gareth.roberts on Dec 8, 2008 4:55 PM

Barcode's in R12.1.1 xml report output's (English and Arabic)

Dear Frednds,
we are using R12.1.1 and we need to get the barcode output's (in place of numbers) in out xml report output's.
We need it in English report and also in Arabic reports (it has seperate arabic template file)
Please let us know the method?
Regards,
DB

Desar Hussein,
1) we have downloaded and installed the Font Code128bWinLarge.ttf on windows PC.
2)Set the barcode font for the required field in the rtf Template.
3) Copied the font file, Code128bWinLarge.ttf to $OA_JRE_TOP/lib/fonts
4) Copied xdo.cfg file from our local desktop where we have BI publisher installed to
$OA_JRE_TOP/lib Directory.
5)added these lines locating barcode font location ($OA_JRE_TOP/lib/fonts
/Code128bWinLarge.ttf)accordingly.
Now For English reports we are getting the barcode
But for Arabic reports we are getting junk characters
so is there any other font available for Arabic barcode.Plerase suggest
Regards,
DB

XML Reports completes in warning

Hi gurus,
I am having trouble our developer have made XML report and registered it when he is running the concurrent request is completing in warning (yellow color) and no output is generate and below is the log file for the concurrent request.
we never had any XML report in our environment this is the first time so do we need to do any setup for XML reports to generate fine ?
also where is OPP service log files location ?
Thanks
Regards,
HASSAN
General Ledger: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
GLTS module: GL_TRIAL BALANCE ACCOUNT WISE SUMMARY
Current system time is 22-OCT-2011 12:20:40
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
p_set_of_books_id='1001'
P_CHART_OF_ACCOUNTS_ID='30008'
p_company='001'
COMP2='001'
p_project='1101'
p_project_to='1101'
p_period='200612'
p_period_to='201112'
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.UTF8
Enter Password:
Report Builder: Release 10.1.2.3.0 - Production on Sat Oct 22 12:20:42 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 785118 on node TEST at 22-OCT-2011 12:20:57.
Post-processing of request 785118 failed at 22-OCT-2011 12:20:58 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
------------- 2) PRINT -------------
Not printing the output of this request because post-processing failed.
Finished executing request completion options.
Concurrent request completed
Current system time is 22-OCT-2011 12:20:58
---------------------------------------------------------------------------

hassanksa wrote:
the desktop version of xml pub which our developer used for report development was not compatible with our apps
then i recommended developer with the correct version once he used the right one the reports worked fineThanks for the update and for sharing the solution!
Hussein

Concurrent request -one at a time

I am going to run this request from PL/SQL,
this is going to be called more than 1 time simultaniously, if more than 1 user runs the report at a time.
I want to make it run one at a time, instead of running 2 different calls at same time.
like i want to make the first request get completed and then run the next.
How do i do it?
FND_REQUEST.SUBMIT_REQUEST('BOM','BMCOIN','Import Bills and Routings',
NULL,FALSE,
org_id,'1','1','1','1');

Hi,
Please see these threads.
running cuncurrent request
Re: running cuncurrent request
Concurrent request compatibility Issue
Concurrent request compatibility Issue
Thanks,
Hussein

Calling a concurrent request from within the trigger

Oracle apps r12.
Calling a concurrent request from within the trigger.
Does it requre apps initilization.
Thanks,
Lavan

Hi,
Whether apps initialization needed or not will depend on followings
1. Trigger is written on which table seeded or custom. In case of seeded tables, there is no need for apps initialization (although oracle does not recommend writing trigger on seeded tables).
2. Triggering Table Update/Insert/Delete event processing is done from apps front end or Backend. In case of front end apps initialization is not required.
Regards,
Saurabh

How to open Report output in RTF format using concurrent request form.

Hi
I have created a report using BI publisher and RTF format. This report is working fine in PDF format. User can submit report using consurrent request form and can see report preview in PDF format.
Now user wants to submit another request and wants to see report output in RTF format.
User submitted a request, request successfully completed and generated a output RTF file in unix box but when user wants to see report output using concurrent request form (View Output) then window is showing raw data instead of RTF output.
Can any body tell me about solutions?
Thanks
Ravi

Hi Ravi
I did little R&D on it and found following 2 solutions.I am sure that you also find something but for my shake i am putting it here.If you already find the solution then ignore it.
I) 1st Solution
1)Change the profiles 'Viewer: Application for Text' and put value as 'Browser'
2) Change the profiles 'Viewer: Text' and put value as 'Browser'.Either change it system level or concerned user.
3) Log out from Current session and close all internet explorer application.
4) Log in again to check the result
II) 2nd Solution
1) Navigate to: Sys admin --> Install -> Viewer Options to open the Form "Viewer Options".
Do the entry as shown below:
File_Format     Mime Type               Description
RTF          application/rtf Microsoft Word(.rtf)
RTF          application/msword          Microsoft Word(.rtf)
2) Then ensure that the profile option Viewer: Application for Text is set to BLANK at the Site Level and User Level.
3) Then ensure that the profile option Viewer: Text is set to 'browser' at the Site Level.
-- It will pop-up the screen to choose application name from above two values.
Hope this will work it for you. For me i replicated the scenario and both solutions were working for me.
With Best Regards
Darshan Bhavsar

Error after viewing Concurrent Request logfile--tools-Copy file

Hi ALL,
Navigation Path
==============
After concurrent request gets complete--View Log-tools -copy Logfile-
I am getting error "The Applications File Server could not open the file for read".
Can you please put some light on this error.
Your help is highly appreciated.
Cheers,
Sridhar

Hi,
What is the application release?
Has this ever worked? If yes, any changes have been done recently?
Can you reproduce the issue with all reported?
Please make sure that the application listener is up. Also, run AutoConfig and make sure it completes successfully.
Regards,
Hussein

Concurrent requests failing due to Linux CUPS service

Dear all,
We have a customer running their production instance on e-business suite -11.5.10.1 with Rdbms - 10.2.0.3. It is a single-node, single-tier installation running on Redhat Linux 3 (Update-8)
Whenever, concurrent programs are submitted with Print option, the concurrent requests keep hanging and never complete. At this time, the CUPS service uses 25% of the CPU time. If we restart the CUPS service, all requests complete with warning -
lpr: unable to print file: server-error-service-unavailable
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. An error occurred while AOL tried
to spawn the print process
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. An error occurred while AOL tried to spawn the
print process.
The only workaround, is to run the concurrent request, without print option. But, this is not an option.
Please suggest a fix for this CUPS issue.
Thanks

Check Note: 359890.1 - Apps Print Requests Fail with lp: unable to print file: client-error-not-found (Or lp: unable to print file: server-error-service-unavailable)
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=359890.1

Purging All the Concurrent Requests after Cloning

Hi DBAs,
After performing the cloning to SANDBOX instance (12.0.4), I found more than 2000 pending conc request. I want to get rid of all concurrent request. What is the best way to purge all Concurrent Requests from Cloned instance.
Thanks
Samar

You need to update fnd_concurrent_requests and set all pending concurrent requests to Completed/Error.
SQL> UPDATE fnd_concurrent_requests
SET phase_code = 'C', status_code = 'E'
WHERE phase_code = 'P';Note: 152209.1 - What are the Meaning of the Codes in the STATUS_CODE and PHASE_CODE Columns of FND_CONCURRENT_REQUESTS Table?
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=152209.1
To purge concurrent managers/requests tables and output/log files, submit "Purge Concurrent Request and/or Manager Data" concurrent request.

Query to find the long running concurrent requests morethan 2 hours

Can any one please provide the " Query to find the long running concurrent requests which are running more than 2 hours"

You need to find the different between the current time/date and FND_CONCURRENT_REQUESTS.ACTUAL_START_DATE for the running requests.
More details can be found in the following notes:
Note: 187504.1 - bde_request.sql - Process and Session info for one Concurrent Request (11.5)
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=187504.1
Note: 134035.1 - ANALYZEREQ.SQL - Detailed Analysis of One Concurrent Request (Release 11 and up)
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=134035.1
Note: 751438.1 - How To Check List , Start And End Dates Of A Parent Concurrent Request And All Childs
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=751438.1

Need to retrive the name-value pair of concurrent request

Hello All,
I need to write a query that takes the concurrent request ID (executed concurrent request) as input and retrives the concurrent request parameter names and the values submitted to run that request.
we have considered the following tables to acheive the result:
fnd_descr_flex_col_usage_tl
fnd_concurrent_requests
fnd_concurrent_programs
however unable to map the parameter name-value pairs properly.
Thanks
Krrish

declangallagher .. I am sorry for not being very clear ...
I am sorry for taking your time.But I appreciate your effort .and time ..
I
I have two servlets 1. result (existing) 2. preResult ( probable wrap around)
The servlet
1.result : takes in the Name and gets the result from the db ( Actually uses Castor and JDO ) to get the result
and the GET is as follows
http://128.173.99.68:8080/WebApplication/result?queryFor=Experiment&Name="john"
where "queryFor" is for the name of the form and Name is the text in the VTL ( View)
2.preResult is supposed to be a wrapper around the servlet "result" this takes in the ID from the user
and is of the form
http://128.173.99.68:8080/WebApplication/preResult?queryFor=Wrapper&ID="1234"
There exists a DB mapping to ID and Name .
So Instead of calling the result servlet ..I'll directly call the preResult servlet ...get the ID from the user ...
and get the corresponding Name from the db
....here
I wish to (If possible) tweak the "request" parameter
change
1.The queryFor value to Experiment
2. add The Name="john"
and send this to the result servlet so that it process it ...........

Sql tuning advisor for concurrent requests

Dear all,
I am having one doubt in my mind from very long time.Can we use sql tuning advisor from 10G(EM) to tune concurrent requests and reports?
Regards

Hi Helios,
I am just thinking wiht voice. If you have one code blog which is typed in sql-pl/sql for your concurrent request, its going and run on dbtier. So it has one SQL'ID and also can be check on AWR report. So i belive you can use sqltuning adviser for to can tune related sqlAFAIK, some Instances a single concurrent request may contain multiple SQLID's and in that scenario tuning approach is difficult. Any information how can we consolidate it. If tune one specific sql then the explain plan for other sql become more worst. I came across this situation so many time.
Any information or inputs on this is really appreciated.
thanks,
X A H E E R

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

In R12 Invoice Register Concurrent Request running long time

Hi
In R12, Invoice Register Concurrent Program Running more than 30 mins , before its use to finish with in 10 mins, any suggestions.
Thanks

I don't wanna hear sorry from gurus,Thanks. By the way, I do not consider myself a guru, just a simple guy who is still learning new things everyday and at the same time like to share what he knows :)
Sawwan, I checekd locks there iare no locksWell, in this case I would suggest you wait for the request to complete. Once it is done, bounce the application as well as the database and run the request again (if possible) after enabling trace and see if takes that long to complete.
If the request keeps running (i.e. does not seem to complete), then cancel the request, kill all associated process from the backend, and follow the action plan above (bounce, and enable trace).

R12.1.3 :- XML concurrent request giving completed and "WARNING"

Similar Messages

Maybe you are looking for