Monday, 16 July 2012

Know about XDO LOADER Utility

XDOLoader is Java-based command line program utility to load template files for XML Publisher
  • RTF
  • PDF
  • XSL-FO
  • XML
  • XSD
XDO Loader is a utility used to download and upload the XML Publisher files from one instance to the other. If a developer needs to upload the XML Publisher files and metadata in to other instance, He should use FND Loader to load the metadata and XDO Loader Upload mode to load the physical files.
The files download will be saved in a different name with the language, LOB code, Application Short name and type encoded in it. So the files can be uploaded programmatically by writing some UNIX script to parse and load the files to the target instance.
The files for the Data Template and the Data source can be uploaded by this XDO Loader. First the metadata should be loaded in the BI publisher responsibility by the FND Loader Command. The XDO Loader command will be used to load the physical files after the metadata has been loaded.
Download Syntax:
% java oracle.app.do.ox.until.XDOLoader DOWNLOAD \
-DB_USERNAME <do_user name> \
-DB_PASSWORD <do_password> \
-JDBC_CONNECTION <jibed_on_string> \
-LOB_TYPE <lob_type> \
-APPS_SHORT_NAME <application_short_name> \
-LOB_CODE <lob_code> \
-LANGUAGE <language> \
-TERRITORY <territory> \
-LOG_FILE <log file>

Upload Syntax:
% java oracle.app.do.ox.until.XDOLoader UPLOAD \
-DB_USERNAME <do_user name> \
-DB_PASSWORD <do_password> \
-JDBC_CONNECTION <jibed_on_string> \
-LOB_TYPE <lob_type> \
-APPS_SHORT_NAME <application_short_name> \
-LOB_CODE <lob_code> \
-LANGUAGE <language> \
-TERRITORY <territory> \
-LOG_FILE <log file>

The parameters LOB_CODE and LCT_FILE are optional, but one must be defined as follows:
  • LOB_CODE - use this parameter to download an individual template.
  • LCT_FILE - if you do not define an LOB_CODE then this parameter is required. If you want to download multiple templates, then you must provide the LCT file. The loaded needs this file to retrieve the templates. The LCT file can be found under XDO_TOP/patch/115/import/xdotmpl.let. When you use this option you will not only get the templates, but the let file for the templates will be generated for you as well.

Sunday, 15 July 2012

Know about FND LOADER:


      In an oracle implementation, usually setups are done in a development instance which need to be migrated to test and production instance. FNDLOAD can be used to create data files from the source instance and then this data file uploaded to target instance. The data file thus downloaded can be moved from one instance to another instance as a source controlled file.

Oracle provides a utility to download and upload the metadata files from one instance to the other. This utility will save lots of time in configuring an instance.

The FNDLOAD program can migrate entities like Attachment Definition, Concurrent Programs, Printers and Printer Styles, Value-Sets, Request Groups, Request Sets, Form Personalization, Lookups, Responsibilities, Applications, Profile Options, Users, Form, Functions and Menus, Document Sequences, Descriptive and Key Flex Fields.
BI publisher files and metadata also can be migrated from one instance to the other. I will discuss that in my next post.
To download data for a particular entity, it makes use of a definition file (called .lct file). These definition files are standard files (for each standard entity) and are available in the directory, $FND_TOP/patch/115/import/. For example, to download a concurrent program, a definition file afcpprog.lct is used.
Output data file is created with an extension .ldt. This data file can then subsequently be uploaded into other environment using FNDLOAD command with upload parameter.
For example, suppose there is a concurrent program defined in development instance. We want to migrate this concurrent program from development to Test instance. The can be achieved using the following two steps:
a. Run the FNDLOAD command (in Development instance) in DOWNLOAD mode, using definition file afcpprog.lct to create a .ldt file.
b. Run the FNDLOAD command (in Test instance) in UPLOAD mode, using the data file created in step (a) above.
This FNDLOAD program runs in UNIX environment. The mode can be Download or Upload. The configuration file .lct file will be present in $FND_TOP/patch/115/import directory. The output will be stored in the .ldt file.
There are some standard configuration files available. They are given in this link.
http://oracleapps4u.blogspot.in/2011/08/working-with-fndload-in-oracle-apps.html


Examples on Upload Download of Commonly used Entities
Concurrent Program
Download
FNDLOAD apps/<password> O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="<Short Application Name>" CONCURRENT_PROGRAM_NAME="<concurrent program short name>"
Upload
FNDLOAD apps/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt

Thursday, 12 July 2012

AP Suppliers in R12


I got a chance to work on R12 AP Suppliers. I am sharing the knowledge which I have gained when I tried to learn about supplier in payables. A supplier will have 3 main categories of information, the supplier detail, Site information and the contact information. These will be maintained in three separate tables. In R12 there are three base tables which will maintain the information about the suppliers.
In R12 the Supplier can be of main two types, the standard supplier and the employee supplier. The standard supplier is who supply some goods to the organization. The employee supplier is the employee of the organization who claim his money from the company for the service or travel he made for the company in iExpence module.
The tables are
AP_SUPPLIERS
AP_SUPPLIER_SITES
AP_SUPPLIER_CONTACTS
There are three related interface tables
AP_SUPPILERS_INT
AP_SUPPLIER_SITES_INT
AP_SUP_SITE_CONTACTS_INT
In 11i there where PO_VENDORS, PO_VENDOR_SITES, PO_VENDOR_CONTACTS table which was doing the same work which these supplier tables do. But in R12 these table has been changed to views to solve R12 and 11i compatibility. SO these tables also can be used to do the operations. Using of views for selecting the data is a good practice coz this will avoid the id logics in our code. The base tables will be stored with ids.
R12 version has a new module called TCA (Trading Community Architecture) which deals all the suppliers as parties. This module also makes an entry when a supplier is added.TCA tables also maintain separate tables for parties, Sites and contacts.
The suppliers from the flat files can be loaded in to the system. This can be done by running the oracle supplier interface programs.
Supplier Interface Programs:
1] Supplier Open Interface Import
2] Supplier Sites Open Interface Import
3] Supplier Site Contacts Open Interface Import
These programs will load the supplier information from the interface tables to the base table.

AP_SUPPLIER_INT_REJECTIONS table contains suppliers, sites, contacts rejections information.

Monday, 9 July 2012

Counting the files with different extensions in a directory (UNIX)

                For listing the files in UNIX we have a command called ls. It can also list multiple extension files at the same time. In a project I had to write a script for counting files with particular extensions alone i.e. XSL, RTF and XML.I wrote the code for counting the files. My manager suggested me to filter the files before counting to improve the process. I felt it was an amazing idea and it will come out of experienceJ.
For  f in `ls *.xml *.xsl *.rtf`
do
count_XSL=$(find  /tmp/files –type f –name “*.XSL” | wc -1)
done

Echo the string to the file which in different location.

                I had a UNIX wrapper script where in I will call two other shell scripts. The wrapper script and the other two scripts will be in the different location. The requirement is to write some useful information to the user from all the three files to the output file in the /tmp directory.
I tried to write with different methods. All of my efforts went in vain. At last came to know that, Path can be directly given in the echo command. At last Finished this requirement in the final day of delivery.
Echo ” My path in learning apps” >>/tmp/output.tmp