What is concurrent programming

Hi
what is concurrent programming?
any links or any Idea?

Not sure what you mean by "concurrent programming" - do you perhaps mean "concurrent processing" ? If so, concurrent processing is the mechanism within EBS thru which batch processes/programs are scheduled. More information in the System Administration docs for your EBS version at http://www.oracle.com/technetwork/documentation/applications-167706.html
HTH
Srini

Similar Messages

Schedulling Concurrent Program in Fixed Assets

Hi Team,
Currently we are working on the Oracle Assets implementation. We want to know that what all concurrent programs like Post Mass addition program that are normaly scheduled by the business? Client wants to plan the concurrent programs that should be scheduled in Fixed Assets. So based on the experience with the business users, kindly guide us that what all programs should be scheduled in Fixed Assets?
Thanks
Garima Arora
Ph no 9642355228

Hi Garima,
While uploading assets into the system you may have to run
1) Post mass additions for adding assets to corp books from interface table.
2) Periodic mass copy to copy assets into tax books from corp books.
Other than this you may have to schedule 'Depreciation run' request set to close the books at the end of every period.
Thanks,
Vinod

What are the concurrent programs or query for safe purge to claim space

I am using Apps R12.1.3 and database 11g Enterprise Edition(11.1.0.7.0) .Due to excess increase in the tablespace sizes,i want to know
What are the application tables which contains logs and unwanted information which we can purge safely without affecting user data.
And how to purge them (any query or concurrent program)?

Hi,
We discussed this many times before.
Please use the following link where you will get many (all) refereces
https://forums.oracle.com/forums/search.jspa?threadID=&q=Purge&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks

I can use concurrent program to do what

what can I use concurrent program for?

I think you should be able to connect an Apple TV to the projector via HDMI, then use AirPlay to mirror the iPad to the projector via the Apple TV. So the answer should be yes you can, you don't need any apps and you should be able to use any projector that can hook up to the Apple TV... but you do need to buy an Apple TV.

Error in running a order import concurrent program

Hi,
Please tell me what type of error is this ,i am using user 'operations',and i have inserted data to the interface table successfully but while running the concurrent program ,i am getting this error.
Cause: FDPSTP failed due to ORA-20100: File o0085033.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
ORA-06512: at "APPS.FND_FILE", line 396
ORA-06512

Hi,
Please see old threads as this error was discussed many times in the forum before.
ORA-20100
http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-20100&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Getting Error While Attaching Concurrent Program Output PDF file for POAPPRV Workflow

Hi All,
I am getting the below error when I am trying to attach concurrent program output to the PO Approval Notification.
An Error occurred in the following Workflow.
Item Type = POAPPRV
Item Key = 1040589-528378
User Key =945871
Error Name = WF_ERROR
Error Message = [WF_ERROR] ERROR_MESSAGE=3835: Error '-20002 - ORA-20002: [WFMLR_DOCUMENT_ERROR]' encountered during execution of Generate function 'WF_XML.Generate' for event 'oracle.apps.wf.notification.send'. ERROR_STACK=
Wf_Notification.GetAttrblob(3604701, ZZ_PREVIOUS_PO_COMPARE, text/html)
WF_XML.GetAttachment(3604701, text/html)
WF_XML.GetAttachments(3604701, http://oraerp.am.corp.xxxx.com:8099/pls/DEV, 11283)
WF_XML.GenerateDoc(oracle.apps.wf.notification.send, 3604701)
WF_XML.Generate(oracle.apps.wf.notification.send, 3604701)
WF_XML.Generate(oracle.apps.wf.notification.send, 3604701)
Wf_Event.setMessage(oracle.apps.wf.notification.send, 3604701, WF_XML.Generate)
Wf_Event.dispatch_internal()
Error Stack =
Activity ID = 190844
Activity Label = AL_NOTIFY_APPROVER_PROCESS:ZZ_PO_PO_APPROVE_ATTCH
Result Code = #MAIL
Notification ID = 3604701
There are several threads for this error however I cannot find any specific solution to the problem.
Please find the code below -
    wf_engine.setitemattrdocument(itemtype=>itemtype,
                                  itemkey=> itemkey,
                                  aname=>'ZZ_PREVIOUS_PO_COMPARE',
                                  documentid =>'PLSQLBLOB:zz_po_reqapproval_init1.xx_notif_attachments/' || to_char(l_request_id_prev_po)||':'||to_char(l_document_num));
-- here l_request_id_q_and_s is the request id of the program and l_document_num is the PO document number
PROCEDURE xx_notif_attachments(p_request_id    IN VARCHAR2,
                               p_document_num IN VARCHAR2,
                               p_document      IN OUT BLOB,
                               p_document_type IN OUT VARCHAR2) IS
v_lob_id          NUMBER;
v_document_num    VARCHAR2(15);
v_document_prefix VARCHAR2(100);
v_file_name       VARCHAR2(500);
v_file_on_os      BFILE;
v_temp_lob        BLOB;
v_dest_offset     NUMBER := 1;
v_src_offset      NUMBER := 1;
v_out_file_name   VARCHAR2(2000);
v_conc_prog_name VARCHAR2(500);
v_conc_req_id     NUMBER;
CURSOR get_output_file(p_concurrent_request_id NUMBER) IS
    SELECT cr.outfile_name, cp.concurrent_program_name
      FROM fnd_concurrent_requests cr, fnd_concurrent_programs_vl cp
     WHERE request_id = p_concurrent_request_id
       AND cp.concurrent_program_id = cr.concurrent_program_id;
BEGIN
--    set_debug_context('xx_notif_attach_procedure');
v_conc_req_id := to_number(substr(p_request_id,
                                     1,
                                     instr(p_request_id, ':') - 1));
v_document_num := substr(p_request_id,
                           instr(p_request_id, ':') + 1,
                           length(p_request_id) - 2);
OPEN get_output_file(v_conc_req_id);
FETCH get_output_file
    INTO v_out_file_name, v_conc_prog_name;
CLOSE get_output_file;
v_out_file_name := substr(v_out_file_name,
                            instr(v_out_file_name, '/', -1) + 1);
v_file_name     := to_char(v_document_num) || '-Previous_PO_Rev.pdf';
utl_file.fcopy(src_location => 'APPS_OUT_DIR',
                 src_filename => v_out_file_name,
                 dest_location => 'PO_DATA_DIR',
                 dest_filename => v_file_name);
-- v_lob_id := to_number(v_document_id);
v_file_on_os := bfilename('PO_DATA_DIR', v_file_name);
dbms_lob.createtemporary(v_temp_lob, cache => FALSE);
dbms_lob.fileopen(v_file_on_os, dbms_lob.file_readonly);
dbms_lob.loadblobfromfile(dest_lob    => v_temp_lob,
                            src_bfile   => v_file_on_os,
                            amount      => dbms_lob.getlength(v_file_on_os),
                            dest_offset => v_dest_offset,
                            src_offset => v_src_offset);
dbms_lob.fileclose(v_file_on_os);
p_document_type := 'application/pdf;name=' || v_file_name;
dbms_lob.copy(p_document, v_temp_lob, dbms_lob.getlength(v_temp_lob));
EXCEPTION
WHEN OTHERS THEN
    wf_core.CONTEXT('ZZ_PO_REQAPPROVAL_INIT1',
                    'xx_notif_attachments',
                    v_document_num,
                    p_request_id);
    RAISE;
END xx_notif_attachments;
Please help me find a to the above mentioned error.
Thanks,
Suvigya

There are two ways to look at what error the PLSQLBLOB API is throwing.
1) Call your PLSQLBLOB API GNE_PO_CREATE_FILE_ATTACHMENT.Gne_Create_File_Attachment directly from a PLSQL block and verify that it returns the BLOB data successfully.
You could also call another WF API that in turn executes the PLSQLBLOB API internally. For example,
<pre>
declare
l_document blob;
l_doctype varchar2(240);
l_aname varchar2(90);
begin
dbms_lob.CreateTemporary(l_document, true, dbms_lob.Session);
-- 207046 - This is the notification id of your failed workflow
-- PO_REPORT - Document type attribute
-- 'text/html' - Content Type being generated for
Wf_Notification.GetAttrBLOB(207046, 'PO_REPORT', 'text/html', l_document, l_doctype, l_aname);
-- Print the size of the document here to verify it was fetched correctly
end;
</pre>
2) Turn on log for SYSADMIN user with following attributes.
Log Enabled = TRUE
Log Level = ERROR
Log Module = wf.plsql%
Restart the Workflow Deferred Agent Listener and Workflow Notification Deferred Agent Listener and run your workflow process. Search for log messages written for above context and you can identify the error at wf.plsql.WF_XML.GetAttachment module with message starting as "Error when getting BLOB attachment ->"
Hope this helps.
Vijay

Error while running a concurrent program.

Hi All,
I have written a plsql procedure and registered it with apps. When i run the program it is giving
FDPSTP failed due to ORA-20100: File l0137058.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
I am not able to find out what is the problem with this. When i remove the FND_FILE.PUT_LINE statement from my code and execute it is executing properly without errors. Please suggest me what might be the problem. Also please suggest me where i can find this .tmp file or where i can find the request log.
Thanks and Regards,
Mahesh

Mahesh,
On the instance where this concurrent program fails to run, please verify the following:
1) Make sure that APPLPTMP is set to a valid directory as shown above (Verify from the OS by issuing "echo $APPLPTMP" as applmgr user)
2) Make sure that both the applmgr user and the database user "oracle" have read/write permissions on $APPLPTMP
3) Make sure that APPLPTMP is the first entry in utl_file_dir (utl_file_dir is set in the init<SID>.ora file). To verify to what "utl_file_dir" is set:
SQL> connect / as sysdba
SQL> show parameter UTL_FILE_DIRPlease go through the first document referenced in my first reply (Note: 261693.1), it should be helpful.
Regards,
Hussein

Rtf template not showing as uploaded in concurrent program

Hello
I have created xml data definition and uploaded a rtf template. Then linked it to my concurrent program. But when i ran the concurrent program successfully all i get is the xml output. Upon closer inspection it shows that no template is uploaded. Yet in xml publisher it shows as uploaded.
so my question is: what can prevent a rtf template from attaching to a concurrent program?

If you and send the template, it would be helpful.
kindly send it to [email protected]
Deepa

How to EXPORT a concurrent program from one instance to another

Hi,
I am new to EBS.
How to EXPORT a concurrent program from one instance to another. I dont want to use FNDLOAD.
Is there any other way from where we can export the concurrent program to anothere instance from CLIENT connection server.
Thanks
Asis

Hi;
What is EBS version? Why you dont use FNDLOAD?
Pelase see below thread
Move concurrent program to prod
Move concurrent program to prod
Regard
Helios

How to Submit a Concurrent program from OAF page Button?

Hi,
I have tried this but its not submitting the request
String shipId = pageContext.getParameter("shipId");
OADBTransaction tr = am.getOADBTransaction();
Connection conn = tr.getJdbcConnection();
OracleCallableStatement ocs = null;
String stmt = new String("");
if(pageContext.getParameter("SubmitRequest") != null) {
try {
stmt = "begin fnd_request.submit_request( application => 'XX',
program => 'SHIPG_MATRL_PKP',
description => NULL,
start_time => sysdate,
argument1 => :1 ); end;";
ocs = (OracleCallableStatement)conn.prepareCall(stmt);
ocs.setString(1,shipId);
ocs.execute();
catch(SQLException se)
throw OAException.wrapperException(se);
What is the mistake in the syntax.
Can anyone provide the syntax for this?
Krishna

Hi Anil,
I got the same requirment. The requirement was we need to create a Print PO button on the OAF page and when we click the button, we need to display the PO in pdf format by calling a concurrent program(XML) based on the PO type.
My approach was below.
1. Create the button using Personilization.
2. Extend the controller class and add the code to call the concurent request.
Can you please guide me how to create the button using personilization. When I created the button, this was shown on the OAF page. But I don't get the hand symbol on that button to click that button.
Also please give me the approach of extending the controller and AM.
Thanks for your help

Report runs OK through concurrent program, but not when called through URL

We have a custom 6i report developed that works successfully 100% of the time when run through a concurrent program.
We are now attempting to integrate this into an OAF application. To do this, we build the necessary call to the reports server by reading different profile options, etc and come up with a URL like this:
http://ebsd777.xxxxx.com:8000/dev60cgi/rwcgi60?d777_APPS+report=XXMFG_ESPEC_REPORT.rdf+P_SPEC_ID=43+DESFORMAT=PDF
This report works 90% of the time when called like this, but the other 10%, we get the following error:
"Error: The requested URL was not found, or cannot be served at this time.
Incorrect usage."
Trying to find what the differences are between the reports that work and those that don't - found that reports which fail seem to extend out further to the right than the reports that do work. But, these reports still fit on standard letter paper in landscape format - as we can verify through the concurrent program call.
Is there some sort of report server setting or parameter which we can change to get this to work when called through the reports server URL?
Any thoughts would be appreciated!
Thanks,
Craig

Hi,
Please post the application release along with the database version and OS.
But when i call the same program through the pl/sql executable of another concurrent program , it does not print the pdf output by defaultHow do you call the program? What is the value of the number of copies profile option?
Please see if these docs help.
Note: 757901.1 - How To Restrict The Number Of Copies To 1?
Note: 729117.1 - How To Specify the Number of Copies to Print by Report?
Thanks,
Hussein

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

Questions on Concurrent program.

Hi
1. How do I know, how many concurrent program is running in service contract and their status ?
2. Is there a place, where I cango and check the following details for a particular concurrent program ?
1. When it ran last ?
2. Was there any error ?
3. logfile or logfile location ? etc
thanks
siva
Edited by: sivapara on Nov 21, 2008 12:05 PM

And if this is a BDC running in background, or a call transaction, then placing the cursor on a given field has no effect unless it is needed for navigation to the next screen.
When you record a BDC using SHDB there are a lot of statements like this that are added in but are not needed for the BDC to work.
Another example is the "BDC_SUBSCR" field name - this does not in most cases appear to have any effect on how the BDC is processed.
Also, the recording will include fields which have default values on the screen that you do not need to overwrite with the same value from the BDC.
I often delete these statements from the recording, taking care that I understand what the impact is. You can try commenting out the line and see what difference it makes to processing.
When using a BDC for updating a lot of records, having less of these types of lines in the BDCDATA table will speed performance a bit.
Andrew

Single concurrent program for multiple operating units

HI
I am working on XML/BI publisher to generate AR invoice reports.
We have single rdf report using which rtf templates are generated.
There are 10 operating units (10 ORG_ID's) and 10 rtf templates, one for each operating unit. There are 4 different responsibilities for each ORG_ID
Eg: ORG_ID's = 11, 12, 13, 14..........etc
Eg: Responsibility = xx, yy, zz...........etc
I want to register a single concurrent program. When a user submits a request from "XX" responsibility, then the template associated with that org_id should be generated. Whichever responsibility the user is accessing from, that particular template must be shown as output.
How can i register one concurrent program for multiple operating units.
Thanks!
Edited by: 994628 on Mar 18, 2013 4:39 PM
Edited by: 994628 on Mar 18, 2013 4:42 PM

>
There are 10 operating units (10 ORG_ID's) and 10 rtf templates, one for each operating unit. There are 4 different responsibilities for each ORG_ID
Eg: ORG_ID's = 11, 12, 13, 14..........etc
Eg: Responsibility = xx, yy, zz...........etc
I want to register a single concurrent program. When a user submits a request from "XX" responsibility, then the template associated with that org_id should be generated. Whichever responsibility the user is accessing from, that particular template must be shown as output.
>
interesting case for 10 OE set 10 template
what is purpose? for each OE different requirements for layout?
BTW
if each Responsibility associated with one org_id then
- you can get current org_id when you run concurrent program
- create main template (will be #11) with condition like
<?choose:?>
<?when: ORG_ID=11?>
<?import:xdo://FND.XX11_SUB.en.00/?>
<?call:TEMPLATE11?>
<?end when?>
<?when: ORG_ID=12?>
<?import:xdo://FND.XX12_SUB.en.00/?>
<?call:TEMPLATE12?>
<?end when?>
<?otherwise:?>
<?import:xdo://FND.XX21_SUB.en.00/?>
<?call:TEMPLATE21?>
<?end otherwise?>
<?end choose?>so based on org_id will be import of needed subtemplate
- re-register your "10 rtf templates" as subtemplates
another way is substitution of template for concurrent then it running
in before_report trigger set needed template
l_conc_request_id := fnd_global.conc_request_id;
    if ORG_ID = 11 then
      UPDATE fnd_conc_pp_actions t
         SET t.argument2 = 'XX11'
       where t.concurrent_request_id = l_conc_request_id
         and t.action_type = 6;
if ORG_ID = 21 then
      UPDATE fnd_conc_pp_actions t
         SET t.argument2 = 'XX21'
       where t.concurrent_request_id = l_conc_request_id
         and t.action_type = 6;

Submitting XML Publisher Concurrent Program through PL/SQL

Hi,
I am trying to submit a XML Publisher concurrent program through PL/SQL API fnd_request.submit_request.
The request gets fired and completes successfully but it doesn't pick up the default template attached to it. Its output is plain XML but expected output is PDF report.
However when I submit this report from SRS, it picks up the default template and gives output in PDF.
Please let me know what could be going wrong?
Regards,
Nitin

Check out the FND_REQUEST.ADD_LAYOUT API. You need to call it before you submit your report.
Cheers,
Dave

What is concurrent programming

Similar Messages

Maybe you are looking for