http://www.applikast.net/technical/msca/oracle-msca--mobile-supply-chain-applications
Oracle MSCA- Mobile Supply Chain Applications
http://www.applikast.net/technical/msca/oracle-msca--mobile-supply-chain-applications
XML Model Report - Oracle configurator
http://www.applikast.net/technical/tools/xml-model-report---oracle-configurator
################################################################################
################################################################################
Developers who have worked on Oracle Configurator have always realised that there has been a requirement to understand the changes between existing repository models and the published version of those models in Oracle configurator.

- There was no existing tool to check changes that were made to a Model.
Oracle e-business Code Migration Tool
For the latest content please refer to :
http://www.applikast.net/technical/tools/oracle-e-business-customization-installation-tool
Updating Supplier Name on Supplier
NLS_LENGTH_SEMANTICS -BYTE/CHAR
Free Code Migration Tool for Oracle Applications Release 12
Oracle OPM: Updating Batch Material Line based on the source Formula Line
RTF Template Labels get displayed as Junk Characters when generated as PDF
Converting the PLD to PLL and PLX
/* Query for Data Definition */
SELECT xddt.data_source_name "Data Source Name",
xddb.data_source_code "Code",
fat.application_name "Application Name"
FROM xdo_ds_definitions_b xddb,
xdo_ds_definitions_tl xddt,
fnd_application fa,
fnd_application_tl fat
WHERE xddb.data_source_code LIKE 'XX%'
AND xddt.data_source_code = xddb.data_source_code
AND xddt.LANGUAGE = 'US'
AND fa.application_short_name = xddb.application_short_name
AND fat.application_id = fa.application_id
AND fat.LANGUAGE = 'US'
/* Query for Templates */
SELECT xtt.template_name "Template Name",
xtb.template_code "Template Code",
fat.application_name "Application Name",
xddt.data_source_name "Data Definition",
xtb.template_type_code "Template Type",
xtb.default_language "Language",
xtb.default_territory "Territory",
xl.file_name "File Name",
xl.file_data "File"
FROM xdo_templates_tl xtt,
xdo_templates_b xtb,
fnd_application_tl fat,
xdo_ds_definitions_tl xddt,
xdo_lobs xl
WHERE (xtt.template_name LIKE '
AND xtt.LANGUAGE = 'US'
AND xtb.template_code = xtt.template_code
AND fat.application_id = xtb.application_id
AND fat.LANGUAGE = 'US'
AND xddt.data_source_code = xtb.data_source_code
AND xddt.LANGUAGE = 'US'
AND xl.lob_code = xtb.template_code
AND NVL (xl.program, 'X') <> 'RTF2XSLParser 5.6.3'
AND xl.LANGUAGE = xtb.default_language
AND xl.territory = xtb.default_territory
Migrating Oracle e-business Business Events
To run the Workflow XML Loader manually, run java / jre against oracle.apps.fnd.wf.WFXLoad.
You must specify your CLASSPATH pointing to the Java Runtime Environment, the directory containing the Workflow JAR files, the Oracle JDBC implementation, and the following Workflow JAR files:
• wfjava.jar - Workflow Java utilities
• wfapi.jar - Workflow Java APIs
java -classpath "$
- Specify whether you want to upload(-u) or download(-d)
- Specify the apps user name and password
- Provide the server details i.e the servername/port/sid
- Provide the name of the file to which you want to download or from which you want to upload
- Specify whether you want to download subscriptions/events
- Specify the name of the event for download
adjava oracle.apps.fnd.wf.WFXLoad -d aapps **** myserver:1541:sid thin US ./xx_oracle_apps_po_rfq_event_RFQActiveEvent.wfx EVENTS xx.oracle.apps.po.rfq.event.RFQActiveEvent
Sample for downloading subscriptions:
adjava oracle.apps.fnd.wf.WFXLoad -d apps **** myserver:1541:sid thin US ./xx_oracle_apps_po_rfq_event_RFQActiveEventSubscription.wfx SUBSCRIPTIONS xx.oracle.apps.po.rfq.event.RFQActiveEvent
Sample for uploading events
adjava oracle.apps.fnd.wf.WFXLoad -u apps **** myserver:1554:sid thin US xx_oracle_apps_po_rfq_event_RFQActiveEvent.wfx
Sample for uploading subscriptions
adjava oracle.apps.fnd.wf.WFXLoad -u apps **** myserver:1554: sid thin US xx_oracle_apps_po_rfq_event_RFQActiveEventSubscription.wfx
How to create a host concurrent program in the Oracle e-business suite
1: Write the script and call it
A sample script is presented in the article Copying Output of Concurrent Program to a given directory
Running a java concurrent program from command line in Oracle e-business
java -Ddbcfile=<my_dbc_file >
- The parameter -Ddbcfile=
<my_dbc_file > is the dbc file for your environment. This is usually located in $FND_TOP/secure - Drequest.logfile represents the location of your log file. If you do not provide this value it would get defaulted.
<concurrent_program_class> This represents the underlying java class that you would implement for you java concurrent program. This needs to implement the interface JavaConcurrentProgram and also needs to provide a concrete implementation of the method: public void runProgram(CpContext pCpContext)
java -Ddbcfile=$FND_TOP/secure/env.dbc -Dreqeust.requestid=123456789 -Drequest.logfile=./myreq.log oracle.apps.fnd.cp.request.Run oracle.apps.xx.fax.XxFaxDocument "TOKEN1=./fax:TOKEN2=12345
"
XDOLoader : Wrapper Tool
Download here (https://sites.google.com/a/applikast.net/applikast/file-cabinet/xdoload.pl?attredirects=0&d=1)
Also create a file called install.txt in your installation directory with the following contents and replace with the appropriate values:
db_sid=mydb
db_port=1561
db_server=localhost
Ensure that each entry remains on a different line in the text file. It is also important that the text file doesn't have any ^M characters.
Please note that the xml publisher files should follow the naming convention that is followed by XDOLoader DOWNLOAD. This helps the tool identify the Product short name/ lob code and the lob type as well. Once these are derived the only parameter that is needed to run xdoloader is the apps password that is passed as a commandline argument.
Sample files names when downloaded using XDOLoader download are:
BURSTING_FILE_AR_ARDLP_NON_SRS.xml
TEMPLATE_SOURCE_AR_ARDLP_NON_SRS_en.rtf
The file in the link needs to be downloaded and renamed as xdoload.pl
Once this is done you can run this in your unix shell as
perl xdoload.pl apps_pwd
You can put this in the /bin directory and create an alias so that you don't need to type perl xdoload.pl all the time.
eg. cp xdoload.pl $CUSTOM_TOP/bin
alias xdoload='perl $CUSTOM_TOP/bin/xdoload.pl'.
Then run the command using xdoload directly
This wrapper internally calls out to the XDOLoader class with the appropriate parameters as described in the post: Migrating BI Publisher Files: using XDOLoader FNDLOAD
Please do leave your feedback and comments it will help me provide something more meaningful going forward.
Migrating BI Publisher Files: using XDOLoader FNDLOAD
• Metadata that defines the details about the data definition and templates
• BI Publisher files i.e Data Definition Files/RTF Template/Bursting file etc
• RDF files in case of reports based BI Files
• Concurrent programs to run the report.
In Order to move the entire definition of the BI Publisher report from one instance to other you need to move each of the components described above. The tools namely XDOLoader and FNDLOAD are used to migrate these files across instances.
You can use the following commands to download :
• Metadata:
FNDLOAD apps/****0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct XXJW_ARDLP_NON_SRS.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=AR DATA_SOURCE_CODE=ARDLP_NON_SRS
• BI Publisher files i.e BI Publisher Data definition template/Bursting File/RTF Template for ARDLP_NON_SRS Data definition:
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD ***** \
-JDBC_CONNECTION db_server:db_port:db_sid \
-APPS_SHORT_NAME AR \
-LCT_FILE ${XDO_TOP}/patch/115/import/xdotmpl.lct \
-DS_CODE ARDLP_NON_SRS
• Copy the RFD file if any from the instance directly
• Download the concurrent program using:
FNDLOAD apps/**** 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_ARDLP_NON_SRS.ldt PROGRAM CONCURRENT_PROGRAM_NAME="ARDLP_NON_SRS"
Once the files have all been downloaded you need to take them to the middle tier of another instance and upload them back. This can be done using the following commands:
• Metadata:
FNDLOAD apps/****0 Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct XXJW_ARDLP_NON_SRS.ldt
• Upload each of the xml publisher files using commands below:
o Bursting File:
java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \ -DB_USERNAME apps \ -DB_PASSWORD **** \ -JDBC_CONNECTION db_server:db_port:instance_sid \ -LOB_TYPE BURSTING_FILE \ -APPS_SHORT_NAME AR \ -LOB_CODE ARDLP_NON_SRS \ -LANGUAGE en \ -TERRITORY US \ -NLS_LANG American_America.WE8ISO8859P1 \ -XDO_FILE_TYPE XML-BURSTING-FILE \ -FILE_CONTENT_TYPE 'text/html' \ -FILE_NAME ./xmlpub/BURSTING_FILE_AR_ARDLP_NON_SRS.xml
o RTF Template:
java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \ -DB_USERNAME apps \ -DB_PASSWORD **** \ -JDBC_CONNECTION db_server:db_port:instance_sid \ -LOB_TYPE TEMPLATE_SOURCE \ -APPS_SHORT_NAME AR \ -LOB_CODE ARDLP_NON_SRS \ -LANGUAGE en \ -TERRITORY US \ -NLS_LANG American_America.WE8ISO8859P1 \ -XDO_FILE_TYPE RTF \ -FILE_CONTENT_TYPE 'text/html' \ -FILE_NAME ./xmlpub/TEMPLATE_SOURCE_AR_ARDLP_NON_SRS_en.rtf
o Data Definition Template:
java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \ -DB_USERNAME apps \ -DB_PASSWORD **** \ -JDBC_CONNECTION
• Copy the RFD file if any to the reports/US folder directly. If it is customised then copy to
• Upload the concurrent program using:
FNDLOAD apps/**** 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct
You can find a wrapper program to the xdoloader methods here:
XDOLoader : Wrapper Tool