Topics to summarize 1. Outputpost processor. 2. XML publisher. 3. Report review agent. 1. Output post Processor a).

Concurrent processing uses the output post processor to enfo rce post-processing actions for concurrent requests. b). Post-processing actions are actions taken on concurrent requ est output. An example of a post-processing action is that used in publishing concurrent requests with xml publisher. c). The output post processor is an enhancement to concurrent pr ocessing and is designed to support XML publisher as post-processing action for concurrent request. If a request is s ubmitted with an xml publisher template specified as a layout for the concurrent request output, then after the concu rrent manager finishes running the concurrent program, it will contact the OPP to apply the XML publisher template and create the final output. d). The output post processor makes use of the oracle streams ad vanced queuing (AQ) database feature. Every OPP service instance monitors fnd_cp_gsm_opp_aq queue for new messages and this queue has been created with no value specified for primary_instance(link). This implies that the queue monitor scheduling and propagation i s done in any available instance. e). The maximum amount of memory or maximum java heap size a sin gle OPP process can use is by default set to 512 MB. This value is seeded by the loader data file: $FND_TOP/patch/115/impo rt/US/afoppsrv.ldt which specified that the DEVELOPER_PARAMETERS is "J:oracle.apps.fnd.cp.gsf.GSMServiceCont roller:-mx512m". 2. XML publisher 1.The flexibility of XML publisher is a result of the separation of the presentation of the report from its data structure. The Collection of the data is still handled by your concurrent reque st, but now you can desing and control how the report outputs will be presented in a separate template files. 2. At runtime, the concurrent managers output post processors c alls XML publisher to merge your designed template files with the report data to create rich, published documents in PDF that can support supports colors, images, font sytels, headers and footers, and countless other formatting options. 3. The core components of XML publisher are a java-based set of publishing tools accessible via java APIs from oracle e-business suite or any java-based application. a) FO Processor - The formatting object that results fro m the application of the XSL-FO template to the XML data is used by the FO Processor to generate the required output docu ment. Currently the FO processor only supports PDF as an output format, other formats such as HTML and RTF will be suppo rted in future releases of XML publisher. b). PDF Document Merger - The pdf document merger accept

s XML DATA and a pdf document as input and uses a mapping between the xml and the fields in the document to merge the data into the PDF document. C). PDF Form Processor - The pdf form processor is used to add attributes such as watermarks to a merged document. d). RTF Template Parser - Report templates can be create d in the Rich text format (RTF) document format, and converted to XSL-FO format that can be applied to XML data. 3. Report review agent 1. RRA stands for report review agent. RRA is nothing but FNDFS which is part of apps listener. RRA is to pick the log/out file from the file system and show on the editor when u press vi ew log/out button in view concurrent request form. 2. The output from a concurrent processing job goes through seve ral stages before being displayed to the user. i. The concurrent processing server communicates with th e database server via oracle net. ii. The log or output file associated with a concurrent request is passed back to the report review agent, also known as the web review agent. iii. The report review agent passses a file containing t he entire report to the forms services. iv. The forms services pass the report back to the user' s browser one page at a time. 3. In the case if you are not able to see the log and out file b y clicking on the form in the browser then perform the following taks 1. Check the web listener is running or not. 2. Check the profile option with RRA 2.1. Check the RRA:SERVICE_PREFIX ( BY default t he value is null). problem with the report server 1. error rep3000( display must be provided as it is not set so it is giving erro r) 2. if your report output show garbage data, then check the nls_lang, as the befo re generating the report the report server picks up the value nls_lang environmnet variable to generate the report in the respective language. Information related to discoverer 1. grep disco $CONTEXT_FILE If the output contains a tag value like <disco_standalone oa_var="s_disco_standalone">false</dis co_standalone> It means the discoverer that is here is inbuilt discover er which comes by default installation of the EBS. Important interview questions 1. We can find the general locks with the following query select * from sys.dba_dml_locks order by session_id; 2. We can find the dead locks with the following query select * from v$lock where lmode>0 and id1 in (select distinct id1 from v$lock where request > 0); 3. To find the database/sqlplus version

select banner from v$version; 4. Why do we keep the same password for APPS and APPLSYS? => During oracle applications login 1. initial sing on (http://hostname.domain.com:port) This uses APPLSYSPUB schema to authenticate and validate AOL use rname and password. Once this authentication is validated successfully we get to see the responsibility page. 2. Selecting the assigned responsibility requires applsys schema validat ion and then it connects to APPS schema. 3. Since it uses both applsys and apps during signon process this expert s both the password to be identical. 5) What would happen if you change the passwords for APPS,APPLSYS with "alter us er" command. Changing the apps password using "alter user " corrupts the password. oracle application stores passwords in FND_USER AND FND_ORACLE_USERID The APPLSYS.FND_ORACLE_USERID table contains all the oracle applications related database accounts- there is one database account for each oracle applications module(id, GL=General Ledger). The application needs access to these database schemas to perform various functions, this it must have access to the database a ccount password. All the paswords in the fnd_oracle_userid table are encrypted using the apps password in FND_ORACLE_USERID. 6). re profile_option_name='APPS_FRAMEWORK_AGENT') AND LEVEL_VALUE=0; Table that stores the application url select profile_option_value from fnd_profile_option_values where profile_option_id=(Select profile_option_id from fnd_profile_options whe