Please visit my new domain at http://ediyanto.co.cc

C U there…

Update (as of 08-Nov-2009):

- Oracle Top-N Query
- Bersyukurlah…
- Cinta Sejati
- Nice Story
- 5 Tips Agar Tak Mudah Lelah
- Belajar dari Alphabet
- How To Get the List of All Responsibilities Assigned To A User
- Query To Find Multi-Org Is Enabled Or Not
- How To Find A Patch Is Applied For A Bug
- Excel Limitations on Images
- BLOB Images in XML Publisher
- Today Is Beautiful Day And I Cannot See It
- Scheduled Ship Date Time Always Reset To 23:59:00 in Oracle Apps R11i
- Tandingan Antar Berkumis
- Hati yang Luka
- Mr. Pig
- Changing LOV using Forms Personalization on Oracle Apps R12
- Starting VMware Server Hangs/Crashes on Windows Vista
- Where Context XML File in Oracle Apps R12?
- Kekuatan Pikiran

Three possible errors can occur as below:

• The Output Post Processor is not running or does not pick up the request

…
+————- 1) PUBLISH ————-+
Unable to find an Output Post Processor service to post-process request [request_id].

Check that the Output Post Processor service is running.
+————————————–+
…

Solutions:
* Verify that the Output Post Processor is enabled and active.
* If confirmed, retrieve the OPP log file either via the Forms application or via the Oracle Application Manager.
- Via the Forms application:

1. Login to the application as SYSADMIN
2. Responsibility: System Administrator
3. Function: Concurrent –> Manager –> Administration
4. Select the Output Post Processor
5. Click on the Processes button
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Manager Log button to open the Output Post Processor log file

- Via the Oracle Application Manager

1. Login to the application as SYSADMIN
2. Responsibility: System Administration
3. Function: Oracle Applications Manager –> Concurrent Managers
4. Select the Output Post Processor Service and click on View Details
5. Click on View Processes
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Log button to open the Output Post Processor log file

• The Output Post Processor is running but has not picked up the request

...
+------------- 1) PUBLISH -------------+
The Output Post-processor is running but has not picked up
this request.No further attempts will be made to post-process
this request, and the request will be marked with Warning status.
Setting the profile option Concurrent: OPP Response Timeout
to a higher value may be necessary.
+--------------------------------------+
...

By default a timeout will occur if it takes longer then 120 seconds (2 min.) for the Output Post Processor to pick up the request from the Concurrent Manager process. In that case, the Concurrent Request will complete with status Warning and the Request log file will contain error message like above.

Solutions:
* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Response Timeout‘.

• The concurrent manager has timed out waiting for the Output Post-processor to finish this request

…
+————- 1) PUBLISH ————-+
The concurrent manager has timed out waiting for the Output Post-processor
to finish this request.

Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile.
+————————————–+
…

The concurrent manager process has successfully invoked the OPP but it a timeout is encountered as the OPP takes too long to complete the job.

The time that this takes will depends on various elements such as:

• size of the XML Data File
• complexity of the template
• performance of the server
• ….

By default a timeout will occur if it takes longer then 300 seconds (5 min.) for the XML Publisher engine to generate the output file. The Concurrent Request will complete with status Warning and the Request log file will contain error message like above.

Solutions:
* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Process Timeout‘.

Worked Example I – Securing a PDF output
You can now embed any of the XML Publisher properties into your RTF template <<reference to property lists>> These would then be resolved at runtime by the XML Publisher engine; you can either use hard coded values or embed the values inside the incoming XML data.

If you wanted to secure PDF output generated from a template you can use the XML Publisher pdf security properties and obtain the password value from the incoming XML data.

To add an XML Publisher property to a template use the Properties dialog (File -> Properties) :

picture 1: xdo-pdf-security

picture 2: xdo-pdf-open-password

The XML Publisher properties need to have ‘xdo-’ as a prefix to their regular names so ‘pdf-open-password’ becomes ‘xdo-pdf-open-password’. Just add the XML Publisher properties and their value to the document using the dialog. If you want to reference a data element in the XML, a password for instance then use the curly braces in enclose the path to the XML element.

Worked Example II – Securing a PDF output

Lets assume that the XML data you are using will contain a specific password that needs to be used to secure the output document. Again we can use the document properties to set the PDF security password and reference a value in the XML. Assuming the following XML data:

<EY>

 <security>true</security>

<password>welcome</password>

<EY_DETAILS>

..

<EY>

In the properties dialog we would enter two properties:

Name : xdo-pdf-security – this property sets whether the security feature is enabled or not

Type :Text

Value :{/EY/security}

Name : xdo-pdf-open-password – this property sets the password

Type :Text

Value :{/EY/password}

Storing the password in the XML data could be a security problem if the XML is going to persist in the system for any length of time. To avoid this you could achieve the same using a template parameter value that is generated and passed into the template at runtime. Assuming your parameters were called ‘PDFSec’ and ‘PDFPWD’ you would enter the following in the properties dialog:

Name : xdo-pdf-security – this property sets whether the security feature is enabled or not

Type :Text

Value :{$PDFSec}

Name : xdo-pdf-open-password – this property sets the password

Type :Text

Value :{$PDFPWD}

Both of these methods would then secure the output PDF document with a password that would only be know to the user.

When you submit the XML Report Publisher Program (XDOREPPB) you are prompted to select the Request ID for the data generation program. The LoV for this parameter is not being populated due to an incorrect profile option reference.

To work around this issue, you must change the references to the incorrect profile option in the XDO_REPORT_REQUEST_ID value set as follows:

1. Using the System Administrator responsibility, open the Value Set form. Navigation: Application > Validation > Set.
2. Query value set name XDO_REPORT_REQUEST_ID.
3. Click Edit Information.
4. Modify Where/Order By as follows:
   

Current:

WHERE ( ( FND_PROFILE.VALUE(‘CONC_REPORT_ACCESS_LEVEL’) = ‘U’
AND R.REQUESTED_BY = :$PROFILES$.USER_ID ) or
( FND_PROFILE.VALUE(‘CONC_REPORT_ACCESS_LEVEL’) = ‘R’
AND R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID ) )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE=’XML’
AND R.STATUS_CODE not in (‘E’, ‘D’, ‘T’, ‘X’)
ORDER BY R.REQUEST_ID DESC

Modified to:

WHERE (R.REQUESTED_BY = :$PROFILES$.USER_ID or
R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE=’XML’
AND R.STATUS_CODE not in (‘E’, ‘D’, ‘T’, ‘X’)
ORDER BY R.REQUEST_ID DESC

Reference Note:404928.1

You can get the XML file from the XML/BI Publisher report based on concurrent request with the below steps:

1. *) View->Requests
2. *) Find the request you’re interested in
3. *) Click on Diagnostics button
4. *) Click the View XML
5. *) Save the file to your PC by doing File->Save As, *.xml

Or you can get it from this location $APPLCSF/$APPLOUT/o{REQUEST_ID}.out

BI Publisher provides the FNDLOAD and XDOLoader utilities to move component across eBusiness Suite instances.

The FNDLOAD utility is used to upload and download the concurrent program, data definition and data template created via created via System Administrator and XML Publisher Administrator responsibility.

The XDOLoader utility is used to upload and download the physical files (Template files, XSD Schema, Sample XML Data , Bursting Control File)

FNDLOAD : Download Concurrent Programs

*) Download all the concurrent programs in a specific product.

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=MPI

*) Download concurrent program for a specified concurrent program name.

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=MPI CONCURRENT_PROGRAM_NAME=MPISHIPPED

FNDLOAD : Upload Concurrent Programs

*) Upload the concurrent programs to an instance.

FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt – CUSTOM_MODE=FORCE

FNDLOAD : Download Data Definition and Data Template

*) Download all the data definitions and the corresponding Templates in a specific product.

FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=MPI

*) Download a particular data definitions and its corresponding Templates.

FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=MPI DATA_SOURCE_CODE=MPISHIPPED

FNDLOAD : Upload Data Definition and Data Template

*) Upload the data definitions and its corresponding Templates to an instance.

FNDLOAD apps/apps 0 Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt

XDOLoader : Download Physical Files

*) Download all the physical files for a specified application short name

java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION oradev:1522:DEV \
-APPS_SHORT_NAME MPI \
-LANGUAGE id \
-TERRITORY ID

*) Download a particular physical file for a specified XDO LOB code

java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION oradev:1522:DEV \
-APPS_SHORT_NAME MPI \
-LOB_TYPE TEMPLATE_SOURCE \
-LOB_CODE MPISHIPPEDT \
-LANGUAGE id \
-TERRITORY ID

XDOLoader : Upload Physical Files

*) Upload the RTF file

java oracle.apps.xdo.oa.util.XDOLoader \
UPLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION oradb:1521:PROD \
-LOB_TYPE TEMPLATE \
-APPS_SHORT_NAME MPI \
-LOB_CODE MPISHIPPEDT \
-LANGUAGE id \
-TERRITORY ID \
-XDO_FILE_TYPE RTF \
-FILE_CONTENT_TYPE ‘application/rtf’ \
-FILE_NAME /oracle/dev/appldev/devappl/MPI_MPISHIPPEDT.rtf \
-CUSTOM_MODE FORCE

-CUSTOM_MODE FORCE = FORCE the update if a data/lob already exists

Posted in Oracle Tagged: development, ebiz, XML/BI Publisher ]]> http://ediyanto83.wordpress.com/2009/01/02/moving-concurrent-programs-data-definitions-and-templates-between-ebusiness-suite-instances/feed/ 0 Edi http://ediyanto83.wordpress.com/2008/12/29/oracle-xml-publisher-bi-publisher/ http://ediyanto83.wordpress.com/2008/12/29/oracle-xml-publisher-bi-publisher/#comments Mon, 29 Dec 2008 10:40:54 +0000 Edi Yanto http://ediyanto83.wordpress.com/2008/12/29/oracle-xml-publisher-bi-publisher/ ]]>

While running XML Publisher report for EXCEL output, the Concurrent Program has the error message :

“ORA-1403: no data found”

The cause of this problem has been identified in Bug 4396843 by Metalink.

The output of the report can be viewed from menu Request > Monitor through System Administration Responsibility or you can solve this problem by 2 way :

1. Change the length of oftype variable from varchar2(4) to varchar2(5) in editor_pkg2.browser_show() of FNDCONC.PLL. Because output type “EXCEL” can’t be strored in that variable as it exceeds the size of the variable. After that, compile PLL with this syntax: “f60gen module=FNDCONC.pll userid=apps/apps module_type=library batch=yes output_file=FNDCONC.plx compile_all=special“
2. Apply patch 4396842 or later

Repeatable Row Headers

If your transactions/invoices break across a page and you want to repeat the column header row this can be achieved using MSWord’s functionality.

Highlight the header row

Table > Table Properties

Under the Row tab select the ‘Repeat as Header row at the top of each page’

If the transactions/invoices table breaks across a page the header row will be repeated.

Splitting Rows across pages

You can prevent rows splitting across a page break by using MSWord’s funtionality:

Highlight the data row

Table > Table Properties

Under the Row tab deselect the ‘Allow row to break across pages’

Rows that would normally be split across two pages will now be moved to the second page to preserve the row data.