XML/BI Publisher Interview Questions

What is BI Publisher?

A. It is a reporting tool for generating the reports. More than tool it is an engine that can be

    integrated with systems supporting the business.

Is BI Publisher integrated with Oracle Apps?

Yes, it is tightly integrated with Oracle Apps for reporting needs. In 11.5.10 instances xml publisher 
was used, in R12 we can it BI Publisher

What is the difference between xml publisher and BI Publisher?
Name is the difference, initially it was released on the name of xml publisher( the initial patchset),
 later on they have added more features and called it Business Intelligence Publisher.
 In BI by default we have integration with Datadefinitions in R12 instance. 
 Both these names can be used interchangeably

What are the various components required for developing a BI publisher report?

Data Template, Layout template and the integration with Concurrent Manager.

How does the concurrent program submitted by the user knows about 
the datatemplate or layout template it should be using for generating the output?

The concurrent program ‘shortname’ will be mapped to the ‘code’ of the Datatemplate.
Layout template is attached to the datatemplate, this forms the mapping between all the three.

What is a datatemplate?

Datatemplate is an xml structure which contains the queries to be run against the database so
that desired output in xml format is generated, this generated xml output is then applied on to
the layout template for the final output

What is a layout template?

Layout template defines how the user views the output, basically it can be developed 
using Microsoft word document in rft (rich text format) or Adobe pdf format.
The data output in xml format (from Data template) will be loaded in layout template at run time and 
the required final output file is generated.

What are the output formats supported by layout template?

xls, html, pdf, eText etc are supported based on the business need.

Do you need to write multiple layout templates for each output type like html/pdf?

No, only layout template will be created, BI Publisher generates desired output format when
the request is run

What is the default output format of the report?

The default output format defined during the layout template creation will be used to generate the output,
the same can be modified during the request submission and it will overwrite the one defined 
at layout template

Can you have multiple layout templates for a singe data template?

Yes, multiple layouts can be defined, user has a choice here to use one among them at run time during
conc request submission

Where do you register data and layout templates?

Layout template will be registered under xml publisher administrator responsibility>Templates tab
Data template will be registered under xml publisher admininstrator responsibility> Data Definitions

I want to create a report output in 10 languages, do I have to create 10 layout templates?

No, BI Publisher provides the required translation for your templates, based on the number of languages 
installed  in your oracle apps environment requires outputs are provided

What is the required installation for using BI Pub report?

BI Publisher desktop tool has be installed. Using this tool you can preview or test the report before
deploying the same on to the instance.

How do you move your layout or data template across instances?

xdoloader is the utility that will be used. 

What is the tool to map required data output and layout templates so that they can be
tested in local machine?

Template viewer will be used for the same.

Which component is responsible for generating the output 
in xml format before applying it to layout template?

DataEngine will take DataTemplate as the input and the output will be generated in xml format which will 
then be applied on layout template

Can BI publisher reports be used in OAF pages?

XDO template utility helper java classes are provided for the same.

Name some business use cases for BI  reports?

Bank EFT, customer documents, shipping documents, internal analysis documents
or any transactional documents

How do you pass parameters to your report?

Concurrent program parameters should be passed, ensure that the parameter name/token
are same as in the  conc prog defn and the data template

What are the various sections in the data template?

        Parameter section

        Trigger Section

        Sql stmt section

        Data Structure section

        Lexical Section

What does lexical section contain?

The required lexical clause of Key Flex field or Descriptive FF are created under this section

What triggers are supported in Data template?

Before report and After report are supported

Where is the trigger code written?

The code is written in the plsql package which is given under ‘defaultpackage’ tag of data template.

 what is the file supporting the translation for a layout template?

 xliff is the file that supports the translation, you can modify the same as required.

How do you display the company logo on the report output?

A. Copy and paste the logo (.gif. or any format) on the header section of .rtf file .
 Ensure you resize per the company standards.

HOW TO CREATE TKPROF FILE IN ORACLE APPS R12

HOW TO CREATE TKPROF FILE
-----------------------------------------------

Trace file

-------------

The main use of enabling trace for a concurrent program comes during performance tuning.
By examining a trace file, we come to know which query/queries is/are taking the longest
time to execute, there by letting us to concentrate on tuning them in order to improve the
overall performance of the program.
The following is an illustration of how to Enable and View a trace file for a Concurrent  Program.

 Navigation: Application Developer–>Concurrent–>Program

Check the Enable Trace Check box. After that go to that particular Responsibility and run the Concurrent Program.

Check that the Concurrent Program has been completed successfully.

The trace file by default is post fixed with oracle Process_id which helps us to identify which trace file belongs to which concurrent request. The below SQL Query returns the process_id of the concurrent request:

Select oracle_process_id from fnd_concurrent_requests where request_id=’123456′

(This query displays Process Id)

The path to the trace file can be found by using the below query:

SELECT * FROM V$PARAMETER WHERE NAME=’user_dump_dest’
(This Query displays the path of trace file)

The Trace File generated will not be in the readable format. We have to use TKPROF utility to convert the file into a readable format.

 Run the below tkprof command at the command prompt.

TKPROF < Trace File_Name.trc> <Output_File_Name.out> SORT=fchela

A readable file will be generated from the original trace file which can be further
analyzed to improve the performance. This file has the information about the
parsing, execution and fetch times of various queries used in the program.

PL/SQL RECORDS

PL/SQL RECORDS

PL/SQL RECORDS ARE SIMILAR TO STRUTCURES IN C PROGRAMMING. A STRUCTURE IS AN

OBJECT WHERE WE CAN STORE MORE THAN ONE DATATYPE IN A SINGLE VARIABLE.

SYNTAX:-

DECLARE

TYPE <TYPE NAME> IS RECORD ( <FIELD NAME> <DATA TYPE> [NOT NULL],......);

<VARIABLE NAME> <TYPE NAME>;

BEGIN

----

END;

DECLARE

TYPE EMP_TYPE IS RECORD (EMPNO NUMBER(4),ENAME VARCHAR2(10),JOB VARCHAR2(10));

VEMP EMP_TYPE;

BEGIN

SELECT EMPNO,ENAME,JOB INTO VEMP FROM EMP WHERE EMPNO=7788;

DBMS_OUTPUT.PUT_LINE(VEMP.EMPNO||VEMP.ENAME||VEMP.JOB);

END;

-----------------------------------------------------

WE CAN DECLARE ANY NUMBER OF VARIABLES WITH RECORD TYPE THAT WE DEFINED

DECLARE

TYPE EMP_TYPE IS RECORD (EMPNO NUMBER(4),ENAME VARCHAR2(10),JOB VARCHAR2(10));

VEMP EMP_TYPE;

VEMP1 EMP_TYPE;

BEGIN

SELECT EMPNO,ENAME,JOB INTO VEMP FROM EMP WHERE EMPNO=7788;

SELECT EMPNO,ENAME,JOB INTO VEMP1 FROM EMP WHERE EMPNO=7902;

DBMS_OUTPUT.PUT_LINE(VEMP.EMPNO||VEMP.ENAME||VEMP.JOB);

DBMS_OUTPUT.PUT_LINE(VEMP1.EMPNO||VEMP1.ENAME||VEMP1.JOB);

END;

/

-----------------------------------------------------

WE CAN DIRECTLY ASSIGN ONE TYPE TO ANOTHER.

DECLARE

TYPE EMP_TYPE IS RECORD (EMPNO NUMBER(4),ENAME VARCHAR2(10),JOB VARCHAR2(10));

VEMP EMP_TYPE;

VEMP1 EMP_TYPE;

BEGIN

SELECT EMPNO,ENAME,JOB INTO VEMP FROM EMP WHERE EMPNO=7788;

VEMP1:=VEMP;

DBMS_OUTPUT.PUT_LINE(VEMP.EMPNO||VEMP.ENAME||VEMP.JOB);

DBMS_OUTPUT.PUT_LINE(VEMP1.EMPNO||VEMP1.ENAME||VEMP1.JOB);

END;

DECLARE

TYPE EMP_TYPE IS RECORD (EMPNO NUMBER(4),ENAME VARCHAR2(10),JOB VARCHAR2(10));

VEMP EMP_TYPE;

VEMPNO EMP.EMPNO%TYPE;

BEGIN

VEMPNO:='&EMPNO';

SELECT EMPNO,ENAME,JOB INTO VEMP FROM EMP WHERE EMPNO=VEMPNO;

DBMS_OUTPUT.PUT_LINE(VEMP.EMPNO||VEMP.ENAME||VEMP.JOB);

END;

PL/SQL TABLE

----------------------

A PL/SQL TABLE IS SIMILAR TO AN ARRAY IN C, WE CAN STORE MULTIPLE VALUES IN A

VARIABLE THAT IS DECLARED AS A PL/SQL TABLE.

SYNTAX:-

DECLARE

TYPE <TYPE NAME> IS TABLE OF <DATA TYPE> INDEX BY BINARY_INTEGER;

<VARIABLE NAME> <TYPE NAME>;

BEGIN

---

---

END;

-----------------------------------------------------

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME(1000));

END;

-----------------------------------------------------

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME(1)||VENAME(0));

END;

-----------------------------------------------------

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

END;

-----------------------------------------------------

COUNT:- WILL COUNT THE TOTAL NO OF ELEMENTS WITHIN THE ARRAY

DELETE: - IT WILL DELETE THE ROWS IN A PL/SQL TABLE

<VARIABLE NAME>.DELETE

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

VENAME.DELETE; -- THIS WILL DELETE ALL THE ROWS FROM THE PL/SQL TABLE

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

END;

-----------------------------------------------------

TO DELETE A PARTICULAR ROW FROM THE PL/SQL TABLE

<VARIABLE NAME>.DELETE(INDEX)

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

VENAME.DELETE(0);

VENAME.DELETE(1000);

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

END;

-----------------------------------------------------

EXISTS:- WILL CHECK IF THE SPECIFIED PL/SQL TABLE ROW IS EXISTING OR NOT

<VARIABLE NAME>.EXISTS(INDEX)

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

VENAME.DELETE(0);

VENAME.DELETE(1000);

IF VENAME.EXISTS(1) THEN

DBMS_OUTPUT.PUT_LINE(VENAME(1));

END IF;

DBMS_OUTPUT.PUT_LINE(VENAME.COUNT);

END;

-----------------------------------------------------

FIRST:- WILL RETURN THE FIRST ELEMENT OF THE ARRAY

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.FIRST);

END;

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

VENAME.DELETE(0);

DBMS_OUTPUT.PUT_LINE(VENAME.FIRST);

END;

-----------------------------------------------------

LAST:- WILL RETURN THE LAST ELEMENT OF THE ARRAY

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.LAST);

END;

-----------------------------------------------------

LOOP FOR PL/SQL TABLE

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

I NUMBER;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

I:= VENAME.FIRST;

LOOP

EXIT WHEN I>VENAME.LAST;

DBMS_OUTPUT.PUT_LINE(VENAME(I));

I:=VENAME.NEXT(I);

END LOOP;

END;

-----------------------------------------------------

NEXT :- IT WILL RETURN THE NEXT INDEX AFTER THE SPECIFIED INDEX

<VARIABLE NAME>.NEXT(<INDEX VALUE>);

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.NEXT(1));

END;

-----------------------------------------------------

PRIOR :- IT WILL RETURN THE PREVIOUS INDEX BEFORE THE SPECIFIED INDEX

<VARIABLE NAME>.PRIOR(<INDEX VALUE>);

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

DBMS_OUTPUT.PUT_LINE(VENAME.PRIOR(1));

END;

-----------------------------------------------------

PRINTING ALL THE ARRAY ELEMENTS USING A LOOP AND NEXT

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

I NUMBER;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

I:= VENAME.FIRST;

LOOP

DBMS_OUTPUT.PUT_LINE(VENAME(I));

EXIT WHEN I=VENAME.LAST;

I:=VENAME.NEXT(I);

END LOOP;

END;

-----------------------------------------------------

PRINTING THE ARRAY ELEMENTS IN REVERSE USING PRIOR

DECLARE

TYPE EMP_TYPE IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;

VENAME EMP_TYPE;

I NUMBER;

BEGIN

VENAME(1):='SMITH';

VENAME(2):='ALLEN';

VENAME(0):='JAMES';

VENAME(1000):='KING';

I:= VENAME.LAST;

LOOP

DBMS_OUTPUT.PUT_LINE(VENAME(I));

EXIT WHEN I=VENAME.FIRST;

I:=VENAME.PRIOR(I);

END LOOP;

END;

AP TABLES FOR 11i

Account payables data model (Important tables) Ver 1.0

For preliminary understanding, we will break the Module functionality into following components:

1)      AP setups

2)      Invoice Workbench

3)      Payments workbench

4)      Invoice and Payments accounting

5)      Interfaces

We will take each component one by One:

1)      AP setups

Vendors

Vendors                                  :           PO_VENDORS

                                                           

Vendors Sites                          :           PO_VENDOR_SITES_ALL

Banks

Banks and bank branches       :           AP_BANK_BRANCHES

Bank accounts                         :           AP_BANK_ACCOUNTS_ALL

Payable Documents                :           AP_CHECK_STOCKS_ALL

Pay terms

Payment Terms                       :           AP_TERMS

Pay Term Lines                       :           AP_TERM_LINES

Payables options

            Payables options                     :           AP_SYSTEM_PARAMETERS

            Distribution sets

            Distribution sets                      :           AP_DISTRIBUTION_SETS_ALL

            Distribution set lines               :           AP_DISTRIBUTION_SET_LINES_ALL

     2)    Invoice Workbench     :

            Invoice Batch                          :           AP_BATCHES_ALL

            Invoice Headers                      :           AP_INVOICES_ALL

            Invoice Distributions              :           AP_INVOICE_DISTRIBUTIONS_ALL

            Invoice Scheduled Payments  :           AP_PAYMENT_SCHEDULES_ALL

            Invoice Holds                         :           AP_HOLDS_ALL

      3)   Payments Workbench :

            Payment Batch Sets                :           AP_PBATCH_SETS_ALL

                                                                        AP_PBATCH_SET_LINES_ALL

            Payments                                 :           AP_CHECKS_ALL

                                                                        AP_INVOICE_PAYMENTS_ALL

            Payment Distributions                        :           AP_PAYMENT_DISTRIBUTIONS_ALL

4)      Invoice and payments accounting :

Accounting Events                 :           AP_ACCOUNTING_EVENTS_ALL

Accounting Headers               :           AP_AE_HEADERS_ALL

Accounting Lines                    :           AP_AE_LINES_ALL

5)      Interfaces

Invoice interface                     :           AP_INVOICES_INTERFACE

                                                            AP_INVOICE_LINES_INTERFACE

      Supplier/Vendor interface       :           AP_SUPPLIERS_INT

AP_SUPPLIER_SITES_INT

AP_SUP_SITE_CONTACT_INT

Oracle Apps: LDT Commands

Oracle Apps: LDT Commands

LDT Commands for Upload and Download of Programs:

Download
FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XXMLBEX.ldt PROGRAM APPLICATION_SHORT_NAME="XXTTY" CONCURRENT_PROGRAM_NAME="XXMLBEXPGAL"


Upload:
FNDLOAD apps/<appspwd> O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XXMLBEX.ldt 

------------------------------------------------------------------------------------------------------------
Request group download for Specific Program

Download:
FNDLOAD apps/<appspwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XXMREQ.ldt REQUEST_GROUP REQUEST_GROUP_NAME="All Project Billing Programs" UNIT_NAME="XXMLBEGAL"

------------------------------------------------------------------------------------------------------------
Request Group (NEW request group creation)

Download:
FNDLOAD apps/<Pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_XXX_DTC_Request_Gr.ldt REQUEST_GROUP REQUEST_GROUP_NAME="ALL Programs" APPLICATION_SHORT_NAME="XX"

Upload:
FNDLOAD apps/<apps> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_XXX_DTC_REQUEST_GR.ldt

------------------------------------------------------------------------------------------------------------
Oracle Menu (New Menu)

Download:
FNDLOAD apps/<Pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXX_DTC_GLOBAL_MENU.ldt MENU MENU_NAME="XXX_DTC_GLOBAL"

Upload:
FND_TOP/bin/FNDLOAD apps/<apps> 0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct XXX_DTC_GLOBAL_MENU.ldt

------------------------------------------------------------------------------------------------------------
Oracle Responsibility (New Responsibility)

Download:
FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XXX_DTC_GLOBAL_RESPO.ldt FND_RESPONSIBILITY RESP_KEY="XXX_DTC_GLOBAL"


Upload
FNDLOAD apps/<apps> 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XXX_DTC_GLOBAL_RESPO.ldt

------------------------------------------------------------------------------------------------------------

Lookup Type:

DownLoad:
FNDLOAD apps/pwd 0 Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct XX_OA_STATUTORY_ACCT_MAPPING.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="XX" LOOKUP_TYPE="XX_OA_STATUTORY_ACCT_MAPPING"

Upload:
FNDLOAD apps/<Pwd> 0 Y UPLAOD $FND_TOP/patch/115/import/aflvmlu.lct XX_OA_STATUTORY_ACCT_MAPPING.ldt

------------------------------------------------------------------------------------------------------------

Value set only :

Download:
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"

Upload:
FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

Value set with values :

Download:
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"

Upload:
FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

------------------------------------------------------------------------------------------------------------

Descriptive flex field :

Download:
FNDLOAD apps/apps_pwd 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XX_OA_EXP_RPT_SEG_MAP_DFF.ldt DESC_FLEX APPLICATION_SHORT_NAME="FND" DESCRIPTIVE_FLEXFIELD_NAME="FND_COMMON_LOOKUPS" DESCRIPTIVE_FLEX_CONTEXT_CODE="XX_OA_EXP_RPT_SEG_MAP"

Upload:
FNDLOAD apps/apps_pwd 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct XX_OA_EXP_RPT_SEG_MAP_DFF.ldt


------------------------------------------------------------------------------------------------------------
Concurrent Program :

Download:
FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XXOAGLTSIMP_CONC.ldt PROGRAM APPLICATION_SHORT_NAME="XX" CONCURRENT_PROGRAM_NAME="XXOAGLTSIMP"

Upload:
FNDLOAD <apps>/<apps> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XXOAGLTSIMP_CONC.ldt PROGRAM APPLICATION_SHORT_NAME="XX" CONCURRENT_PROGRAM_NAME="XXOAGLTSIMP"

Conc program assignment to Request Group :

Download:
FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XXOAGLTSIMP_RG.ldt REQUEST_GROUP REQUEST_GROUP_NAME=" DTC Global" APPLICATION_SHORT_NAME="XX" REQUEST_GROUP_UNIT UNIT_NAME="XXOAGLTSIMP"

Upload:
FNDLOAD <apps>/<apps> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XXOAGLTSIMP_RG.ldt REQUEST_GROUP REQUEST_GROUP_NAME=" DTC Global" APPLICATION_SHORT_NAME="XX" REQUEST_GROUP_UNIT UNIT_NAME="XXOAGLTSIMP"
FNDLOAD <apps>/<apps> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_CW_EVAL_NOTIFY_CONC_RG.ldt REQUEST_GROUP REQUEST_GROUP_NAME="PO All Reports" APPLICATION_SHORT_NAME="PO" REQUEST_GROUP_UNIT UNIT_NAME="XX_CW_EVAL_NOTIFY"


-----------------------------------------------------------------------------------------------------------

Forms:

Download
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXFRMNAME.ldt FORM APPLICATION_SHORT_NAME="PN" FORM_NAME="XXFRMNAME"

Upload:
FNDLOAD apps/apps 0 Y UPLOAD @FND:patch/115/import/afsload.lct XXFRMNAME.ldt

Functions:

Download
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXFUNNAME.ldt FUNCTION FUNC_APP_SHORT_NAME="PN" FUNCTION_NAME="XXFUNNAME"

Upload 
FNDLOAD apps/apps O Y UPLOAD @FND:patch/115/import/afsload.lct XXFUNNAME.ldt

-----------------------------------------------------------------------------------------------------------

Form Personalization :

Download:
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct XX_PERWSHRG.ldt FND_FORM_CUSTOM_RULES function_name="PERWSHRG-404"

Upload:
FNDLOAD apps/<Pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct XXGLJOURNALIMP.ldt

------------------------------------------------------------------------------------------------------------

FND Load for DFF Context :

FNDLOAD apps/password 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XXAPdff_CUST_DECL.ldt DESC_FLEX APPLICATION_SHORT_NAME="SQLAP" DESCRIPTIVE_FLEXFIELD_NAME="AP_INVOICES" DFF_CONTEXT DESCRIPTIVE_FLEX_CONTEXT_CODE="CUST_DECL"

------------------------------------------------------------------------------------------------------------

FND Load for Messages :

Donwload:
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='ICX' MESSAGE_NAME=XX_ICX_POR_LIFECYCLE_PAY_TIP
or for all messages
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ALL_GMS_MESSAGES_00.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='XXGMS'

Upload:
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt

------------------------------------------------------------------------------------------------------------

FND Load for Alert :

Download
FNDLOAD apps/apps 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct Email_to_requestes_for_PO_Receipt.ldt ALR_ALERTS APPLICATION_SHORT_NAME='PO' ALERT_NAME=' Email to requestes for PO Receipt'

Upload
FNDLOAD apps/apps 0 Y UPLOAD $ALR_TOP/patch/115/import/alr.lct Email_to_requestes_for_PO_Receipt.ldt

------------------------------------------------------------------------------------------------------------

XML Publisher Data Definition and Templates :

a) To download all Templates defined for a particular Data Definition
FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct ldt_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=[APPSHORTNAME] DATA_SOURCE_CODE=[DATADEFINITIONCODE]


b) To download for a particular Template and Data Definition
FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct ldt_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=[APPSHORTNAME] DATA_SOURCE_CODE=[DATADEFSHORTCODE] TMPL_APP_SHORT_NAME=[APPSHORTNAME] TEMPLATE_CODE=[TEMPLATECODE]