PostRank

顯示具有 Oracle XML Publisher 標籤的文章。 顯示所有文章
顯示具有 Oracle XML Publisher 標籤的文章。 顯示所有文章

2008/10/31

如何修改XML报表默认输出格式的设置

摘自:網路

完成XML报表的制作挂到系统中后, 默认的输出格式是PDF,想要修改的话还要点击'Option'按钮到另一个界面上去修改,客户不胜其烦,我们也很恼火直骂Oracle的娘。好在群众的智慧是无限的,在同事Allen和ERP100斑竹Phoenix的帮助下,找到了解决方法,效果不错。

方法一 Report Builder + XML 实现
Step(1) 在Report Bulder中添加Number类型参数P_CONC_REQUEST_ID;

Step(2) 修改Befor Report Trigger,添加以下代码。
--update layout
UPDATE fnd_conc_pp_actions
SET argument5='RTF'
WHERE concurrent_request_id=:P_CONC_REQUEST_ID
AND action_type=6;
注:此处将输入格式设置为Word,若想设成Excel或Html,可将'RTF'替换成'EXCEL'或'HTML'

方法二 PL/SQL Store Procedure + XML 实现;
Procedure XML_PRINT(Errbuf Out Varchar2,Retcode Out Varchar2) Is
ctx dbms_xmlgen.ctxhandle;
c_result clob;
b Varchar2(5000);
Type ref_cursor Is Ref Cursor;
v_source ref_cursor;
c_long Number;
c_int Int;
Begin
--设置XML报表模认输出格式
UPDATE_XML_OUTPUT_FORMAT ;
--定义数据,数据集必须为游标变量
Open v_source For
Select HEADER_ID DN_HEADER_ID ,
SOLD_TO_ORG_ID PICK_SEQUENCE_ID ,
CUST_PO_NUMBER PS_HEADER_BATCH_NUM ,
ORG_ID BATCH_ID ,
SOLD_TO_ORG_ID DELIVERY_ID ,
ORDER_NUMBER DN_NUMBER ,
BOOKED_FLAG PRINTED_FLAG
From OE_ORDER_HEADERS_ALL
where rownum < 15;
--定义XML CLOB文件
ctx := dbms_xmlgen.newContext(v_source);
-- generate the CLOB as a result.
c_Result := dbms_xmlgen.getXML(ctx);
--以文本形式输出XML文件
c_long := length(c_result);
c_int := c_long/50-0.5;
For a In 1..c_int+1 Loop
b := dbms_lob.substr(c_result,50,(a-1)*50+1);
fnd_file.PUT(fnd_file.OUTPUT,b);
--dbms_output.put_line(b);
End Loop;
dbms_xmlgen.closeContext(ctx);
Close v_source;
End xml_print;

注:这是斑竹Phoenix提供的用PL/SQL Store Procedure产生XML数据的方法,简单实用。


Procedure UPDATE_XML_OUTPUT_FORMAT Is
pragma autonomous_transaction;
BEGIN
UPDATE fnd_conc_pp_actions
SET argument5='RTF'
WHERE concurrent_request_id= fnd_profile.value('CONC_REQUEST_ID')
AND action_type=6;
COMMIT ;
END ;

2008/10/18

如何刪除只能失效的設定

在Oracle Application中,有部份設定是無法線上直接刪除的,當設定錯誤時,只能作失效處理,但是當某些情況下一定得刪除時該怎麼呢?!

我們可以直接調用Oracle EBS的API,通常此種作法官方是非常不建議的,後果請自行負責。

--刪除Program
BEGIN
fnd_program.delete_program('program_short_name','application_sort_name');
END;

--刪除Data Definitions
BEGIN
xdo_ds_definitions_pkg.delete_row('APPLICATION_SHORT_NAME','DATA_SOURCE_CODE');
END;

--刪除Templates
BEGIN
xdo_templates_pkg.delete_row('APPLICATION_SHORT_NAME','TEMPLATE_CODE');
END;

2008/09/12

How Do I Troubleshoot XML with Collections?

Subject: How Do I Troubleshoot XML with Collections?
Doc ID: Note:401619.1 Type: TROUBLESHOOTING
Last Revision Date: 22-JUL-2008 Status: PUBLISHED

In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
Recommended Patch Level for using XML with Collections is 11i.IEX.H RUP #4 and XML Publisher 5.5 or above is the minimum but 5.6 is recommended.
There are two options when using XML to Print, Fax or Email:
Profile Option Setup for CUPS:
IPP Troubleshooting and Setup:
Convert PDF to PS:
CUPS with a UserID/Password:
Some of the most common errors in the XML Generate and Delivery concurrent process are:
Locating the Issue with IPP
Locating Issue with Writing to the Temp Directory:
References


Applies to:

Oracle Advanced Collections - Version: 11.5.10
Information in this document applies to any platform.

Purpose

This troubleshooting guide will help you troubleshoot XML Printing with Oracle Advanced Collections.

Last Review Date

March 20, 2008

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Recommended Patch Level for using XML with Collections is 11i.IEX.H RUP #4 and XML Publisher 5.5 or above is the minimum but 5.6 is recommended.

As of Release 11i.IEX.H, you can now send your correspondence using XML instead of One to One Fulfillment. In Release 12, XML will be the only option, as One to One Fulfillment will be removed. The addition of XML to Collections resulted in a new Concurrent Process (IEX: XML Generated and Delivery) and a few additional setup steps. Please be sure to review the section in the Oracle Collections Implementation guide that covers how to set this up and use the appropriate templates and profile options. Please keep in mind that the word fulfillment is used in these setups whether you are using XML or 1 to 1 Fulfillment. This word is not representative of your choice of delivery methods.

When you run the Workflow Background Process - IEX: Strategy Fulfillment Mailer to process your work items that require email, printing or faxing, a new concurrent process will automatically start, IEX XML Generated and Delivery concurrent process. This is the actual process that will email, fax or print the correspondence. This concurrent process will run once for each work item that needs to be processed. It processes one letter at a time.

You'll probably log an SR when the IEX XML Generated and Delivery process fails. However, the very first thing to check would be if you can see the OUTPUT (Correspondence Letter) via the View Output button on the request screen? If the OUTPUT or letter is viewable then the issue is not going to be with the Collections process, but rather with the setup of the printer, XML or XDO. In this case, you will need to work with the XML Publisher team to get the output to print, fax or email correctly.

If you do View Output and it's not correct or available, then the problem is with the Collections side and you should log an SR to the Collections team, letting them know you tried this test.

There are two options when using XML to Print, Fax or Email:

1. IPP - this requires an XDODELIVERY.cfg file in the $XDO_TOP/resource directory and special patching - 5004894 and 5120935. IPP is used as an MS (Microsoft) Solution. See below for setup and troubleshooting of the XDODELIVERY.cfg file.

2. CUPs - Common Unix Printing System (CUPS) is a free, server-style, IPP-based software that can accept IPP requests and dispatch those requests to both IPP and non-IPP based devices, such as printers and fax machines. See http://www.cups.org/ for more information about CUPS. See Setting Up Cups, page 11-36 for additional information. CUPS will actually convert the PDF file into a PS file and allow it to print on the printer or fax.

Do I Need to Configure xdodelivery.cfg if I'm Using CUPS to Handle my XML Printing?

Yes and No, if you are using CUPS to print, then you do not need the XDODELIVERY.cfg file, the application uses the profile options. Unless you setup CUPS with a username/password. Then you will need to use the XDODELIVERY.cfg file and include the username/password in the definition.

Oracle Collections sends the output to the CUPS server and the CUPS server converts the PDF to Postscript and then allows it to print correctly

Also, keep in mind that when setting up the printer, you MUST use Port 631. The other thing to keep in mind is if you are setting up a FAX server, then you must use the XDODELIVERY.cfg file.

The XDODELIVERY.cfg file is not something that Oracle supplies, this is a file that is manually created by you, the customer. A Sample XDODELIVERY.cfg file is documented in the XML Publisher User's Guide ex. B13817_06 and is supported by the XML Publisher Support team.

Make sure it is valid xml file and placed in $XDO_TOP/resource directory
You need to install pdftops utility for PDF to PS conversion for MS printing

NOTE: The following error in the IEX: XML Generate and Delivery concurrent process can be ignored if you are using CUPS without an xdodelivery.cfg file.

"Config file /erp/dev/apps/snoopyappl/xdo/11.5.0/resource/xdodelivery.cfg does not exist"

Profile Option Setup for CUPS:

Here is our example:

This is the URL to get to our sample CUPS printer -
http://celalnx7.us.oracle.com:631/printers/orlprt1_ipp

So based on this the profiles are set as follows:

IEX: Print IPP Host - celalnx7.us.oracle.com
IEX: Print IPP Port - 631
IEX: IPP Printer Name - /printers/orlprt1_ipp

The application will take these profile results and build the URL string that is used to get to the profile.

IPP Troubleshooting and Setup:

In order to use IPP for print/fax, you must setup the XDODELIVERY.cfg file. XDODELIVERY.cfg is validated by opening the file on a browser. This will show any errors on the xml file or if any xml tags are missing or incomplete.

Sample XDODELIVERY.cfg file:





ipp://devora8.us.oracle.com:631/printers/test1


ipp://reston2-prt-3199a.us.oracle.com:631
/usr/bin/pdftops {infile} {outfile}


rgmamersmtp.oracle.com
25



/tmp
true
"application/pdf"

Some rules:

1. CUPS will always have a URI that starts with HTTP:
2. Type for CUPS and IPP will always be ipp_printer
3. If using IPP, then you must have pdftops
4. The Port is always 631
5. IPP will always have a URI that starts with IPP
6. For Email - Server name is always mysmpt1

Collections selects the hostname from the printer URI and checks whether it is valid machine name I.E. it should translate into IP address. (you can ping machine at the UNIX/DOS prompt)

Convert PDF to PS:

You may need to specify the filter to convert PDF to postscript. Please find the pdftops command in the local machine (can be downloaded from internet if not available) and specify it in a full path (bold part) in the config file XDODELIVERY.cfg like following.

/usr/bin/pdftops {infile} {outfile}

IPP printing also requires filtercontentType to application/postcript

ipp://myserver:80/printers/Myprinter1/.printer
/usr/local/bin/pdftops {infile} {outfile}
application/postscript

CUPS with a UserID/Password:

If you want to add a Userid/Password on a CUPS server, you will need to supply the XDODELIVERY.cfg file with the information to pass:

The sample config file shows how the XDODELIVERY.cfg should be set as:

http://myprinter2.oracle.com:631/printers/myprinter2
basic
cupsuser
cupspwd

Some of the most common errors in the XML Generate and Delivery concurrent process are:

1. String Index -1, this is usually an issue with the printer/fax/email setup.

2. Sending process failed: no address to send, this usually means that there is an
issue with the contact. See Note 382837.1 for details

3. In order to use IPP you must have installed patch - 5584501 IEXXMLGEN : UNABLE TO PRINT IPP PRINTER AND XDODELIVERY.CFG from the XML Publisher team for version 5.5.0 of XML Publisher.

Locating the Issue with IPP

1. Please check the profile ‘IEX: IPP printer name’ matches the printer server name section in the XDODELIVERY.cfg file.

2. Confirm the printer is IPP ready:

A. With the following command from the prompt:

%telnet myprinter.oraclesoutsourcing.com:631

If it immediately returns with the message "telnet: Unable to connect to remote host: Connection refused", this means it is not accepting requests. If the prompt doesn't come back, it means it is waiting for the request, that's a good sign.

B. If step 1 works (the prompt doesn't come back for a while), try to setup the IPP on windows to see how it works. Here are the steps to complete this:

-From the remote Windows, choose 'Printers and Faxes' from the start menu.
-Double click 'Add Printer'
-Choose 'A Network printer' radio button and next
-Choose 'Connect to a printer on the internet...' radio button, type
http://test.oracleoutsourcing.com:631/printers/yourprintername
WHERE - test.oracleoutsourcing.com is the CUPS server name.
-Choose the printer driver and submit.
-If you could successfully create the printer, right click that printer and choose 'properties'
-Click 'Print Test Page' in the property dialog.

C. If step 2A fails, it means the printer is IPP enabled, but somehow it rejects IPP requests. Try Step 1 again, only this time use port 80 instead of 631 - %telnet myprinter.oraclesoutsourcing.com:80

D. If 'C' works (prompt doesn't come back for a while), try the same thing
as previously noted with the value http://test.oracleoutsourcing.com:80/printers/yourprintername (not 631).

E. If 'D' works (prompt doesn't come back for a while), please also try xml publisher with port 80.
Please don't forget the trailing slash. Also, if possible, turn on the Apps debug logging to 'STATEMENT' Note 264196.1 mode before running the request so that it shows all the debug info to the log, including IEX and XDO.

F. If it's the IPP printer, please try also followings.
ipp://test.oracleoutsourcing.com:631/
ipp://test.oracleoutsourcing.com:80/

G. f it's the IPP printer on Windows IIS and the name is "yourprintername" , please try followings.
ipp://test.oracleoutsourcing.com:631/printers/yourprintername/.printer
ipp://test.oracleoutsourcing.com:80/printers/yourprintername/.printer

Locating Issue with Writing to the Temp Directory:

Sometimes the IEX: XML Delivery and Generate process may have a problem locating the TEMP Directory to write to. In this case, you will have to use the xdodelivery.cfg file to define a TEMP directory even if you are using CUPS. Here is a sample:





ipp://xdodev2:631/printers/dummyPrinter



d:/tmp
true


2008/09/06

如何用XML Publisher繪製圖表

好一陣子沒碰XML Publisher了,最近有個任務需求,需要產出報表中帶圖表(長條圖、折線圖…),直覺就又想到這個老夥計了。假設要作個部門人數趨勢圖,首先準備一個Table,存放所需的部門每月人數信息。

Table aftest ( yearmonth ,employee )


















建立Oracle Reports 程式,當作XML Publisher的Data Source只要在Data Model填寫SQL即可,不需要創建Layout。然後將程式上傳至Oracle EBS指定的路徑下。















在Oracle EBS上註冊該報表,注意Output要改為 XML 喔。















提交運行剛才建立的報表,執行成功後,點擊View Output,可以得到一個XML文件。將此文件保存放在本機端。例如:AFTEST.XML

打開MS Word,用 XML Publisher Desktop 工具,進行建立模版。

1.資料->載入XML資料,選擇剛才保存的AFTEST.XML


2.插入->圖表,設定圖表信息


3.先以.rtf格式保存。AFTEST.rtf

4.預覽->PDF,以PDF格式預覽看看,結果是否符合。




登入Oracle EBS的XML Publisher Adminstrator權限,

1.註冊Data Definitions
XML Publisher Adminstrator->Data Definitions->Create Data Definition


2.註冊Templates
XML Publisher Adminstrator->Templates->Create Template
這裡需要個Template File就是剛才保存的AFTEST.rtf


回到Oracle EBS再次提交這支報表AFTEST。

哎呀,報錯了........

+---------------------------------------------------------------------------+
xxxxxxxxxxx: Version : UNKNOWN - Development

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

AFTEST module: AFTEST
+---------------------------------------------------------------------------+

Current system time is 06-SEP-2008 22:01:26

+---------------------------------------------------------------------------+


+-----------------------------
| Starting concurrent program execution...
+-----------------------------


APPLLCSP Environment Variable set to :

XML_REPORTS_XENVIRONMENT is :
/xxxxxxxxxora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb

XENVIRONMENT is set to /xxxxxxxxxxora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb


Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8

'.,'

Spawned Process 6204
REP-3000: Internal error starting Oracle Toolkit.

Report Builder: Release 6.0.8.25.0 - Production on Sat Sep 6 22:01:27 2008

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Enter Username:
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+


+---------------------------------------------------------------------------+
Executing request completion options...

+------------- 1) PUBLISH -------------+
Beginning post-processing of request 265146 on node xxxxxxx at 06-SEP-2008 22:01:33.
Post-processing of request 265146 failed at 06-SEP-2008 22:01:33 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.

看來是在XML Publisher產生時出錯了,得檢查Output Post Processor的Logfile。

進入System Administrator權限,Concurrent->Manager->Administer->Output Post Processor->Process->Manager Log

@_@" 呃~~這是什麼問題呀?? 可惡,就差這最後一步就完成了。

我的環境是:Oracle EBS:11.5.10.2 Database:9.0.2.8 XML Publisher 5.0

[9/6/08 10:01:33 PM] [2046:RT265146] Executing post-processing actions for request 265146.
[9/6/08 10:01:33 PM] [2046:RT265146] Starting XML Publisher post-processing action.
[9/6/08 10:01:33 PM] [2046:RT265146]
Template code: AFTEST
Template app: xxxxxxxx
Language: en
Territory: US
Output type: PDF
[9/6/08 10:01:33 PM] [UNEXPECTED] [2046:RT265146] java.lang.ArrayIndexOutOfBoundsException: 0
at oracle.apps.xdo.common.image.ImageReader.checkFormat(ImageReader.java:107)
at oracle.apps.xdo.common.image.ImageReader.analyze(ImageReader.java:144)
at oracle.apps.xdo.common.image.ImageReader.load(ImageReader.java:310)
at oracle.apps.xdo.generator.pdf.PDFGenerator.createPDFImageReference(PDFGenerator.java:1760)
at oracle.apps.xdo.generator.pdf.PDFGenerator.getImage(PDFGenerator.java:1848)
at oracle.apps.xdo.template.fo.area.AreaTree.getImage(AreaTree.java:507)
at oracle.apps.xdo.template.fo.area.InstreamForeignObjectArea.(InstreamForeignObjectArea.java:40)
at oracle.apps.xdo.template.fo.elements.FOInstreamForeignObject.doLayout(FOInstreamForeignObject.java:80)
at oracle.apps.xdo.template.fo.elements.FOBlock.doLayout(FOBlock.java:180)
at oracle.apps.xdo.template.fo.elements.FOBlock.doLayout(FOBlock.java:142)
at oracle.apps.xdo.template.fo.elements.FOBlock.doLayout(FOBlock.java:76)
at oracle.apps.xdo.template.fo.elements.FOFlow.doLayout(FOFlow.java:76)
at oracle.apps.xdo.template.fo.elements.FormattingEngine.startLayout(FormattingEngine.java:148)
at oracle.apps.xdo.template.fo.elements.FormattingEngine.run(FormattingEngine.java:95)
at oracle.apps.xdo.template.fo.FOHandler.endElement(FOHandler.java:238)
at oracle.xml.parser.v2.XMLContentHandler.endElement(XMLContentHandler.java:196)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1212)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
at oracle.apps.xdo.template.fo.FOProcessingEngine.process(FOProcessingEngine.java:266)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:959)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:1766)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:1277)
at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:229)
at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)

[9/6/08 10:01:33 PM] [2046:RT265146] Completed post-processing actions for request 265146.

Note:362496.1:How to Determine the Version of Oracle XML Publisher for Oracle E-Business Suite 11i and Release 12

轉自Metalink:Note:362496.1

Goal

How can the current version of Oracle XML Publisher on an Oracle E-Business Suite environment be determined? This document applies to both the Oracle E-Business Suite 11i and the Oracle E-Business Suite Release 12.

Solution

There are various ways to find the version of Oracle XML Publisher.

1. Based upon an output file generated by XML Publisher

  • PDF Output
    1. Open the PDF document in Adobe Reader
    2. Open the menu File
    3. Select Document Properties
    4. Click on the tab Description
    ==> The property ‘PDF Producer’ will show e.g. Oracle XML Publisher 5.6.3.
  • RTF Output
    1. Open the RTF document in Microsoft Word
    2. Open the menu File
    3. Select Properties
    4. Click on the tab Summary
    ==> The property ‘Comments’ will show .e.g. Generated by Oracle XML Publisher 5.6.3
  • HTML and Excel output
    1. Open the document in Notepad (or any other plain text editor)
    ==> line 4 or 5 will show e.g. Generated by Oracle XML Publisher 5.6.1
One option to generate an output file is via the Preview functionality which is available under the XML Publisher Administrator responsibility. Navigation path :
  1. Responsibility: XML Publisher Administrator
  2. Function: Templates
  3. Select a Template for which a Preview Data file has been uploaded before
  4. Click on the Preview icon
  5. Save the PDF to the client PC
  6. Determine the version either by the above instructions OR provide the PDF file to Global Customer Support..

2. Based upon the applied patches

Every patch that is installed on the system will have a record in the table AD_BUGS. Either one of the following SQL statements can be used to determine which Oracle XML Publisher patches are applied, depending on the release of Oracle Applications that is installed.

2.1. Oracle E-Business Suite 11i

The following SQL statement will show which patches and thus with version of Oracle XML Publisher is installed on an Oracle E-Business Suite 11i environment:

SELECT DECODE (bug_number

, '3554613', '4.5.0', '3263588', 'XDO.H', '3822219', '5.0.0'

, '4236958', '5.0.1', '4206181', '5.5.0', '4561451', '5.6.0'

, '4905678', '5.6.1', '5097966', '5.6.2', '5472959', '5.6.3'
) PATCH, bug_number
FROM ad_bugs
WHERE
bug_number IN
('3554613', '3263588', '3822219', '4236958', '4206181'

, '4561451', '4905678', '5097966', '5472959');

PATCH BUG_NUMBER
----- ------------------------------
XDO.H 3263588
4.5.0
3554613
5.0.0 3822219
5.5.0 4206181
5.0.1 4236958

2.2. Oracle E-Business Suite Release 12

The following SQL statement will show which patches and thus with version of Oracle XML Publisher is installed on an Oracle E-Business Suite Release 12 environment:

SELECT DECODE (bug_number, '4440000', '5.6.3') PATCH, bug_number

FROM ad_bugs
WHERE bug_number IN('4440000');

PATCH BUG_NUMBER
----- ------------------------------
5.6.3 4440000

Note: Patch 4440000 is in fact the base release of the Oracle E-Business Suite Release 12. It is provided via the Oracle E-Business Suite Applications Release 12.0 Media Pack and not as a standalone patch.

3. Based upon the file version of the MetaInfo.class

The version of a specific Java Class has a one to one relationship with the currently installed version of Oracle XML Publisher. This method is suitable for both Oracle E-Business Suite 11 and Release 12.

$ adident Header
$OA_JAVA/oracle/apps/xdo/common/MetaInfo.class
$Header MetaInfo.java 115.19 2004/11/30 02:45:52 tsuzuki noship $

The following matrix shows the corresponding XML Publisher version for each version of MetaInfo.class:

Metainfo.class XML Publisher Patch Reference Included in ...
... for the Oracle E-Business Suite Release 12
120.6 5.6.3 Patch 4440000 Note 422508.1
Release 12 (12.0.0)

... for the Oracle E-Business Suite 11i
115.28 5.6.3 Patch 5472959 Note 422508.1 11i.ATG_PF.H.delta.5
115.27 5.6.2 (core)
Patch 5097966 Note 367394.1
115.26 5.6.1 Patch 4905678 Note 357308.1
115.24
5.6.0 Patch 4561451 Note 337999.1
115.22 5.5.0 Patch 4206181 Note 316447.1
115.21 5.0.1 (core)
Patch 4236958

115.19 5.0.0 Patch 3822219 Note 295036.1 11.5.10.1 / 11.5.10.2 / 11i.ATG_PF.H.RUP3 and RUP4
115.15 4.5.0 (XDO.H) Patch 3263588 Note 269605.1 11.5.10
115.12 4.3.0 (core)
Patch 3395631


In order to upgrade to a newer release, there's no requirement to apply all previous versions. For example, if the current version is Oracle E-Business Suite 11.5.10, then one can directly upgrade to XML Publisher 5.6.3 by following the instructions as described Note 422508.1.

Note: The 'core' patches provide ONLY the XML Publisher core classes and do not upgrade e.g. the User Interface (UI) within the Oracle E-Business Suite. The 'core' patches only offer specific bug fixes on top of the previous version, e.g. XDO 5.6.2 is a core patch on top of 5.6.1. Is NOT recommended to apply ONLY a core patch as it may break the UI.