Oracle Apps Interview Questions Part - 3

21) APPCORE API’S

APP_COMBO
APP_DATE
APP_EXCEPTION
APP_FIELD
APP_FIND
APP_ITEM
APP_ITEM_PROPERTY
APP_NAVIGATE
APP_RECORD
APP_REGION 7
APP_STANDARD
APP_WINDOW

22)FNDSQF API’S

FND_CURRENCY
FND_DATE
FND_GLOBAL
FND_ORG
FND_STANDARD
FND_UTILITIES.OPEN_URL
FND_UTILITIES. PARAM_EXISTS

23)How to call flex fields in the form

By using FND_FLEX.EVENT (EVENT varchar 2)
How to register an executable and define a concurrent program through backend
By using concurrent processing API’S
1. FND_CONC_GLOBAL.REQUES_DATA
.SET_REQUEST_GLOBALS
2. FND_CONCURRENT.AF_COMMIT
.AF_ROLLBACK
.GET_REQUEST_STATUS
.WAIT_FOR_REQUEST
.SET_COMPLETION_STATUS
3. FND_FILE . PUT
. PUT_LINE
.NEW_NAME 8
.PUT_NAMES
.CLOSE
4. FND-PROGRAM . MESSAGE
. EXECUTABLE
. REGISTER
. PARAMETER
. IN COMPATIBILITY
. EXECUTABLE_EXISTS
5. FND_REQUEST . SET-OPTIONS
.SET_REPEAT_OPTIONS
.SET_PRINT_OPTIONS
.SUBMIT_REQUEST
.SET_MODE
6. FND_REQUEST_INFO . GET_PARAM_NUMBER
. GET_PARAM_INFO
. GET_PROGRAM
. GET_PARAMETER
7. FND_SET . MESSAGE
.ADD_PROGRAM
.ADD_STAGE
.IN COMPATIBILITY
8. FND_SUBMIT . SET_MODE
.SET_REQUEST_STATUS
.SUBMIT_PROGRAM 9
.SUBMIT_SET
  FND_PROGRAM.EXECUTABLE
- is used to define a concurent program executable
- it takes 8 parameters ( all are IN mode )
syntax procedure FND_PROGRAM.EXECUTABLE
(executable IN varchar2,
(Full name)
description IN varchar2 default null
execution_method IN varchar2,
execution_file_name IN varchar2 default null,
icon_name IN varchar2 default null,
language_code IN varchar2 default (VS)
  FND_PROGRAM.REGISTER
- this procedure no used to define a concument program.
- It has 30 IN paranmeters. Out of which 9 are mandatory, the remaining are default.
(program IN varchar2,
application IN varchar2,
enabled IN varchar2,
short_name IN varchar2,
description IN varchar2, default null, 10
executable_application IN varchar2,
mls_function_shelt_name IN varchar2,
mls_function_application IN varchar2,
inerementor IN varhcar2);

24. How to register a table and columns through back end

  by using AD_DD package
- for registering a table
-
- AD_DD BPI doesn‟t check for the existence of the registered table or column in the data base schema, but only updates the required SQL tables.
- It should be ensured that, all the tables and columns registered exist actually and have the same format as that defined using AD_DD API.
- Views need not be registered.

25. How to write to a file through concurrent program.

  By using FND_FILE package and it can be used only for log and output files.
1. FND_FILE.PUT
- this is used to write text to a file with out a new line character
- Multilane calls to FND_FILE.PUT will produce consummated text.
Procedure FND_FILE.PUT (which IN Number, Buff IN varchar2);
- can be FND_FILE.LOG or FND_FILE.OUTPUT.
2. FND_FILE.PUT_LINE 11
- this procedure as used to write a line of text to a file followed by a new line character.
Procedure FND_FILE.PUT_LINE (which IN number, buff IN varchar2);
EX:- FND_FILE.PUT_LINE( FND_FILE.LOG, find_message_get);
3. FND_FILE.NEW_LINE
- this procedure is used to write line terminators to a file
procedure FND_FILE.NEW_LINE (which IN number LINES IN NATURAL:=1);
Ex:- to write two newline characters to a log file
Fnd_file.new_line (fnd_file.log,2);
4. FND_FILE.PUT_NAMES
- this procedure as used to set the temporary log file and output filenames and the temporary directory to the user specified values.
- This should be called before calling my other FND_FILE procedure and only once per a session.

26)Function FND_REQUEST.SUBMIT_REQUEST

( application in varchar2 default null,
program in varchar2 default null,
description in varchar2 default null,
start-time in varchar2 default null,
sub_request in bookan default False,
argument1,
arguemnt2,
argument 100) return number;
  If this is submitted from oracle forms, all the arguments ( 1 to 100 ) must be specified. 12

27. How to submit concurrent programs through OS

- From the operating system the utility .CONCSUB is used to submit is concurrent propgram.
- This is basically used to test a concurrent program .
- By using the WAIT token. The utility checks the request status every 60 seconds and returns the OS prompt upon completion of the request.
- Concurrent manager doesnot abort, shutdown or start up until the concurrent request completes.
  If the concurrent program is compatible with it self, it can be checked for data integrity and dead locks by submitting it many times so that it runs concurrently with it self.
 PL/SQL procedures can submit a request to run a program as a concurrent process by calling.
FND_REQUEST. SUBMIT_REQUEST.
  Before submitting a request, the following functions also should be called optionally.
FND_REQUEST.SET_OPTIONS
FND_REQUEST.SET_REPEAT_OPTIONS
FND_REQUEST.SET_PRINT_OPTIONS
FND_REQUEST.SET_MODE

28. How to checks the request states

- A PL/SQL procedure can check the status of a concurrent request by calling.
FND_CONCURENT.GET_REQUEST_STATUS
FND_CONCURRENT.WAIT_FOR_REQUEST
- FND_CONCURRENT.GET_REQUEST_STATUS
- This function returns the status of a concurrent request
- If the request is already computed, it also returns the completion message.
- This function returns both user friendly (translatable) phase and status values as well as developer phase and status vales that can drive program logic. 13
( request_id in out number,
application in varchar2 default null,
program in varchar2 default null,
phase out varchar2,
status out varchar,
dev_phase out varchar2,
dev_status out varchar2,
message out varchar2) return BOOLEAN;
- when application and program are specified, the request_id of the last request for the specified program should be returned to request_id.
- Phase, and status values should be taken from
FND_LOOKUPS
dev_phase dev_status
pending normal, standby, scheduled, paused
running normal, waiting, resuming, terminating.
Complete normal, Error, warning, cancelled, terminated
Inactive disabled, on-hold, No-manager, supended
- FND_REQUEST.WAIT_FOR_REQUEST
- This function waits for request completion, then returns the request phase/status and completion message to the caller.
- Goes to sleep between checks for request completion.
Syntax
( request_id in number default null,
interval in number default 60,
max_wait in numbe default 0, 14
phase out varchar2,
status out varchar2,
dev_phase out varchar2,
dev_status out varchar2,
message out varchar2) return BOOLEN;
  FND_CONCURRENT.SET_COMPLETION_STATUS
- this function should be called from a concurrent program to set its completion states.
- This function returns TRUE on success, other wise FALSE.
ENT.SET_COMPLETION_STATUS
( status in varchar2,
message in varchar2) return BOOLEAN;
normal
status warning
Error

29. What is the reason for not getting any data when a multi org view is quired

- to get the data correctly, the xxx-ALL must be referenced and the ORG_ID value should be specified to extract portioned data.
- Multiorg views are partitioned by using ORG_ID.
- So access through multiorg views will not return any roes, as the CLIENT_INFO Value is not set
- Use HR_OPERATING UNITS to identify the organization _id of the OU on which query is based.
- Use FND_CLIENT_INFO package to set the value in CLIENT INPO using set_org_contest.
- Execute fnd_client_info. Set_org_context („<org_id>‟);
- Now qurying of multiorg views can be done. 15

30. How do you find that muliorg is installed

- multi organization architecture is meant to allow muliple companies or subsidiaries to store their records with in a single data base.
- Multiple organization Architecture allows this by partitioning data through views in APPS schema.
- Implementation of Multi org generally includes more than one business group.
  To know whether multiorg is existing or not
select multi_org_flag
form fnd_product_groups)
- if the result is „Y‟ means the database is group for multiorg

Oracle Apps Interview Questions Part - 2

16 In which tables FF are stored

A) FND - ID - FLEXS
B) FND-ID-FLEX-STRUCTURES 5

17)Oracle Applications Architecture

- Internet computing Architecture is a frame work for 3-tired, distributed computing that supports Oracle Applications products.
- The Three tiers are
1 Data Base Tier
2 Application Tier
3 Desk Top Tier
- Database tier manages Oracle 8i database.
- Application tier manages Oracle Applications and other tools.
- Desktop tier provides the user interface displace.
- With internet computing architecture, only the presentation layer of Oracle Applications is on the Desk Top tier in the form of a plug-in to standard internet brows

18) List of some API’S

FND_PROGRAM.EXECUTABLE
FND_PROGRAM.REGISTER
FND_PROGRAM.PARAMETER
FND_PROGRAM.ADD_TO_GROUP
FND_REQUEST.SUBMIT_REQUEST
FND_PROFILE.VALUE
FND_PROFILE.GET

19)How to get second parameter value based on first parameter

$fle x $ value set name.

20)How to call WHO columns into the form

By using FND_STANDARD API‟S
1. FND_STANDARD.FORM_INFO 6
Provides information about the form.
Should be called form when_new_form - instance - instance trigger.
2. FND_standard.set_who
loads WHO columns with proper user information.
Should be called from PRE_UPDTE and PRE_INSERT
Triggers for each block with WHO fields
If this is used FND-GLOBAL need not be called. (FND_GLOBAL.WHO)
3. FND_STANDARD.SYSTEM_DATE
This is a function which returns date.
Behave exactly like SYSDATE built-in.
4. FNID_STANDARD.USER
This is a function which returns varchar2
Behaves exactly like built in USER.

Oracle Apps Interview Questions Part - 1

1) What is SET-OF-BOOKS OR Ledgers?

Collection of Chat of Accounts and Currency and Calendars, Convention is called SOB

2) How can u call a standard interface program from sql or pl/sql code

FND_REQUEST.SUBMIT_REQUEST (PO,EXECUTABLE NAME,,,,PARAMETERS)

3) API’s FOR CUSTOMER INTERFACE

HZ_CUST_A/C_VZPUB.UPDATE_CUST_A/C
HZ_CUST_A/C_VZPUB.CREATE_CUST_A/C
FND_PROFILES
FND_APPLICATIONS
FND_GLOBAL
FND-FILE
FND_CONCSUB(can submit conc program in host environment)

4) PL/SQL stored procedure parameters or what are the two parameters that are mandatory for pl/sql type concurrent program

Procedure/function (ERRBUF OUT RETCODE OUT ………………….)
ERRBUF :- Used to write the error message to log or request file.
RETCODE :- Populate log request file with program submission details info.

5) What is Value Set

--The value set is a collection (or) container of values.
--When ever the value set associated with any report parameters. It provides list of values to the end user to accept one of the values as report parameter value.
-- If the list of values needed to be dynamic and ever changing and define a table based values set.

6) What r the validation types

1) None -------- validation is minimal.
2) Independent ------input must exist on previously defined list of values
3) Dependent ------input is checked against a subset of values based on a prior value.
3) Table ----- input is checked against values in an application table
4) Special ------values set uses a flex field itself.
5) Pair ------ two flex fields together specify a range of valid values.
6) Translatable independent ----- input must exist on previously defined list
of values;
translated values can be used.

7) Translatable dependent ------- input is checked against a subset of values
based on a prior values; translated value can be used.

7) What is template

a) The TEMPLATE form is the required starting point for all development of new Forms.
b) The TEMPLATE form includes platform–independent attachments of several Libraries.
APPSCORE :- It contains package and procedures that are required of all forms to support the MENUS ,TOOLBARS.
APPSDAYPK :- It contains packages that control the oracle applications CALENDER FEATURES.
FNDSQF :- it contains packages and procedures for MESSAGE DICTONARY, FLEX FIELDS, PROFILES AND CONCURRENT PROCESSING.
CUSTOM :- it allows extension of oracle applications forms with out modification of oracle application code, you can use the custom library for customization such as zoom ( such as moving to another form and querying up specific records)

8) What are ad-hoc reports

Ans.: Ad-hoc Report is made to meet one-time reporting needs. Concerned with or formed for a
particular purpose. For example, ad hoc tax codes or an ad hoc database query

9) What is responsibility

Is collection of menus, request security groups and data groups
Menus: collection of forms is nothing but menus
Request security groups: collection of programs.
Data groups: is a group of modules to be made accessible by the user through Responsibility
System admin

10) What are different execution methods of executabls

FlexRpt The execution file is wrnitten using the FlexReport API.
FlexSql The execution file is written using the FlexSql API.
Host The execution file is a host script.
Oracle Reports The execution file is an Oracle Reports file.
PL/SQL Stored Procedure The execution file is a stored procedure.
SQL Loader The execution file is a SQL script.
SQL Plus The execution file is a SQL Plus script.
SQL Report The execution file is a SQL Report script.
Spawned The execution file is a C or Pro C program.
Immediate The execution file is a program written to run as a subroutine of the concurrent manager. We recommend against defining new immediate concurrent programs, and suggest you use either a PL/SQL Stored Procedure or a Spawned C Program instead.
Composite Data types :
PL/SQL TABLES / PL/SQL RECORDS / Nested TABLE / VARRAY
What is the sequence of functions – group by, having , order by in a select statements
Select…..Group by…Having…Order by..
Difference between User and Super User
User : login user or front end user
Super user : it has full access of particular module

11) Oracle E-Business suite

Oracle apps + analytical components software.
(Oracle discover) (Oracle sales analyzer) (Oracle financial analyzer) (Oracle marketing analyzer)

12) What is multi org

Legal entity has more than one operating unit is called as multi org
a) Business group --- Human resources information is secured by Business group
b) Legal entity. --- inter-company and fiscal/tax reporting.
operating unit.
c) Operating unit --- secures AR, OE, AP, PA and PO Information.
d) Organizations --- is a specialize unit of work at particular locations

13) What is ERP and Architecture of apps

A packaged business software system that lets a company automate and integrate the majority of its business processes; share common data and practices across the enterprise; [and] produce and access information in a real-time environment.

. 14)What is invoice and Send you a request for payment

15 Data Link

- Data links relate the results of multiple queries.
- A data link (Parent - Child Relation Ship) causes the child query to be executed once for each instance of its parent group.

Concurrent Processing APIs for PL/SQL Procedures

This POSTdescribes concurrent processing APIs you can use in both client–side and server–side PL/SQL procedures. This section also includes example PL/SQL procedure code using these concurrent processing APIs.
The following packages are described:
FND_CONC_GLOBAL.REQUEST_DATA: Sub–request Submission
FND_CONCURRENT: Information on Submitted Requests
FND_FILE: PL/SQL: File I/O
FND_PROGRAM: Concurrent Program Loaders
FND_SET: Request Set Creation
FND_REQUEST: Concurrent Program Submission
FND_REQUEST_INFO: Request Information
FND_SUBMIT: Request Set Submission

FND_CONC_GLOBAL Package
This package is used for submitting sub–requests from PL/SQL concurrent programs.
FND_CONC_GLOBAL.REQUEST_DATA
Summary  :-function FND_CONC_GLOBAL.REQUEST_DATA return varchar2;
Description :- FND_CONC_GLOBAL.REQUEST_DATA retrieves the value of the REQUEST_DATA global.
FND_CONC_GLOBAL.SET_REQ_GLOBALS
Summary   :- function FND_CONC_GLOBAL.SET_REQ_GLOBALS();
Description :-  FND_CONC_GLOBAL.REQUEST_DATA retrieves the value of the REQUEST_DATA global.
Example
/*
* This is sample PL/SQL concurrent program submits 10 * sub–requests. The sub–requests are submitted one at a
* time. Each time a sub–request is submitted, the parent * exits to the Running/Paused state, so that it does not
* consume any resources while waiting for the child * request, to complete. When the child completes the
* parent is restarted.
*/
create or replace procedure parent (errbuf out varchar2, retcode out number) is
i number;
req_data varchar2(10);
r number;
begin
––
–– Read the value from REQUEST_DATA. If this is the

–– first run of the program, then this value will be
–– null.
–– Otherwise, this will be the value that we passed to
–– SET_REQ_GLOBALS on the previous run.
––
req_data := fnd_conc_global.request_data;
––
–– If this is the first run, we’ll set i = 1.
–– Otherwise, we’ll set i = request_data + 1, and we’ll
–– exit if we’re done.
––
if (req_data is not null) then
i := to_number(req_data);
i := i + 1;
if (i < 11 ) then
errbuf := ’Done!’;
retcode := 0 ;
return;
end if;
else
i := 1;
end if;
––
–– Submit the child request. The sub_request parameter
–– must be set to ’Y’.
––
r := fnd_request.submit_request(’FND’, ’CHILD’,
’Child ’ || to_char(i), NULL,
TRUE, fnd_conc_global.printer);
if r = 0 then
––
–– If request submission failed, exit with error.
––
errbuf := fnd_message.get;
retcode := 2;
else
––
–– Here we set the globals to put the program into the
–– PAUSED status on exit, and to save the state in
–– request_data.
––
fnd_conc_global.set_req_globals(conc_status => ’PAUSED’,
request_data => to_char(i));
errbuf := ’Sub–Request submitted!’;
retcode := 0 ;
end if;
return;
end;

FND_CONCURRENT Package

FND_CONCURRENT.AF_COMMIT
Summary  :- function FND_CONCURRENT.AF_COMMIT;
Description :-  FND_CONCURRENT.AF_COMMIT is used by concurrent programs that use a particular rollback segment. This rollback segment must be  defined in the Define Concurrent Program form.
FND_CONCURRENT.AF_COMMIT executes the COMMIT command for the specified rollback segment. FND_CONCURRENT.AF_COMMIT has no arguments.


FND_CONCURRENT.AF_ROLLBACK
Summary :-  function FND_CONCURRENT.AF_ROLLBACK;
Description:-  FND_CONCURRENT.AF_ROLLBACK is used by concurrent programs that use a particular rollback segment. This rollback segment must be defined in the Define Concurrent Program form. FND_CONCURRENT.AF_ROLLBACK executes the ROLLBACK command for the specified rollback segment.
FND_CONCURRENT.AF_ROLLBACK has no arguments.



FND_CONCURRENT.GET_REQUEST_STATUS (Client or Server)
Summary:-  function FND_CONCURRENT.GET_REQUEST_STATUS
(request_id IN OUT number,
application IN varchar2 default NULL,
program IN varchar2 default NULL,
phase OUT varchar2,
status OUT varchar2,
dev_phase OUT varchar2,
dev_status OUT varchar2,
message OUT varchar2) return boolean;

Description :- Returns the status of a concurrent request. If the request has already completed, also returns a completion message.
FND_CONCURRENT.GET_REQUEST_STATUS returns both
“user–friendly” (i.e., translatable) phase and status values, as well as “developer” phase and status values that can drive program logic.
Arguments (input)  request_id  The request ID of the program to be checked.
Application :- Short name of the application associated with the concurrent program. This parameter is necessary
only when the request_id is not specified.
Program :- Name of the concurrent program. This parameter is necessary only when the request_id is not
specified. When application and program are provided, the request ID of the last request for this
program is returned in request_id.

Arguments (output)
Phase :- The user–friendly request phase from
FND_LOOKUPS.
Status The user–friendly request status from
FND_LOOKUPS.
dev_phase  The request phase as a constant string that can be used for program logic comparisons.
dev_status The request status as a constant string that can be used for program logic comparisons.
Message  The completion message supplied if the request has completed.
Example
begin
call_status boolean;
rphase varchar2(80);
rstatus varchar2(80);
dphase varchar2(30);
dstatus varchar2(30);
message varchar2(240);
call_status :=
FND_CONCURRENT.GET_REQUEST_STATUS(<Request_ID>, ’’, ’’,
rphase,rstatus,dphase,dstatus, message);
end;
In the above example, rphase and rstatus receive the same phase and
status values as are displayed on the Concurrent Requests form. The
completion text of a completed request returns in a message.
Any developer who wishes to control the flow of a program based on a
request’s outcome should use the following values to compare the
request’s phase and status.
Possible values for dev_phase and dev_status are:



_
FND_FILE: PL/SQL File I/O
The FND_FILE package contains procedures to write text to log and output files. In Release 11i, these procedures are supported in all types of concurrent programs. For testing and debugging, you can use the procedures
FND_FILE.PUT_NAMES and FND_FILE.CLOSE. Note that these two procedures should not be called from a concurrent program.
FND_FILE supports a maximum buffer line size of 32K for both log and output files.
Attention: This package is not designed for generic PL/SQL text I/O, but rather only for writing to request log and output files.

FND_FILE.PUT
Summary ;- procedure FND_FILE.PUT
(which IN NUMBER,
buff IN VARCHAR2);
Description  :- Use this procedure to write text to a file (without a new line character).
Multiple calls to FND_FILE.PUT will produce concatenated text.
Typically used with FND_FILE.NEW_LINE.
Arguments (input)
which :  Log file or output file. Use either FND_FILE.LOG or FND_FILE.OUTPUT.
buff  : Text to write.

FND_FILE.PUT_LINE
Summary : - procedure FND_FILE.PUT_LINE
(which IN NUMBER,
buff IN VARCHAR2);
Description :- Use this procedure to write a line of text to a file (followed by a new
line character). You will use this utility most often.


Arguments (input)
Which  Log file or output file. Use either FND_FILE.LOG or FND_FILE.OUTPUT.
Buff  Text to write.
Example
Using Message Dictionary to retrieve a message already set up on the server and putting it in the log file (allows the log file to contain a translated message):
FND_FILE.PUT_LINE( FND_FILE.LOG, fnd_message.get );
Putting a line of text in the log file directly (message cannot be translated because it is hardcoded in English; not recommended):
fnd_file.put_line(FND_FILE.LOG,’Warning: Employee ’||
l_log_employee_name||’ (’||
l_log_employee_num ||
’) does not have a manager.’);



FND_REQUEST Package

FND_REQUEST.SUBMIT_REQUEST (Client or Server)
Summary : function FND_REQUEST.SUBMIT_REQUEST
(application IN varchar2 default NULL,
program IN varchar2 default NULL,
description IN varchar2 default NULL,
start_time IN varchar2 default NULL,
sub_request IN boolean default FALSE
argument1,
argument2, ..., argument99,
argument100) return number;
Description : - _
Submits a concurrent request for processing by a concurrent manager. If the request completes successfully, this function returns the concurrent request ID; otherwise, it returns 0.
Attention: FND_REQUEST must know information about the user and responsibility from which the request is submitted. Therefore, this function only works from concurrent programs or forms within Oracle Applications. The FND_REQUEST.SUBMIT_REQUEST function returns the concurrent request ID upon successful completion. It is then up to the caller to issue a commit to complete the request submission. Your code should retrieve and handle the error message generated if there is a submission problem (the concurrent request ID returned is 0). Use FND_MESSAGE.RETRIEVE and FND_MESSAGE.ERROR to retrieve and display the error (if the request is submitted from the client side).
You must call FND_REQUEST.SET_MODE before calling FND_REQUEST.SUBMIT_REQUEST from a database trigger. If FND_REQUEST.SUBMIT_REQUEST fails from anywhere but a database trigger, database changes are rolled back up to the point of the function call. After a call to the FND_REQUEST.SUBMIT_REQUEST function, all
setup parameters are reset to their default values.
Arguments (input)  application  Short name of the application associated with the
concurrent request to be submitted.
Program :-  Name of the concurrent program for which the
request should be submitted.
description  :- Description of the request that is displayed in the Concurrent Requests form (Optional.)
start_time  Time at which the request should start running, formatted as HH24:MI or HH24:MI:SS (Optional.)
sub_request  Set to TRUE if the request is submitted from another request and should be treated as a sub–request.
Starting with Release 11, this parameter can be used if you are submitting requests from within a PL/SQL stored procedure concurrent program.
argument1...100 Arguments for the concurrent request; up to 100 arguments are permitted. If submitted from Oracle
Forms, you must specify all 100 arguments.

Example Request Submissions
Example 1     /* Submit a request from a form and commit*/
:parameter.req_id :=
FND_REQUEST.SUBMIT_REQUEST (
:blockname.appsname,
:blockname.program,
:blockname.description,
:blockname.start_time,
:blockname.sub_req = ’Y’,
123, NAME_IN(’ORDERS.ORDER_ID’), ’abc’,
chr(0), ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’,
’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’, ’’);
IF :parameter.req_id = 0 THEN
FND_MESSAGE.RETRIEVE;
FND_MESSAGE.ERROR;
ELSE
IF :SYSTEM.FORM_STATUS != ’CHANGED’ THEN
IF app_form.quietcommit THEN
/*form commits without asking user to save changes*/
fnd_message.set_name(’SQLGL’,
’GL_REQUEST_SUBMITTED’);
fnd_message.set_TOKEN(’REQUEST_ID’,
TO_CHAR(:PARAMETER.REQ_ID), FALSE);
fnd_message.show;
ELSE
fnd_message.set_name(’FND’,
’CONC–REQUEST SUBMISSION FAILED’);
fnd_message.error;
END IF;
ELSE
DO_KEY(’COMMIT_FORM’);
IF :SYSTEM.FORM_STATUS != ’CHANGED’ THEN
/*commit was successful*/
fnd_message.set_name(’SQLGL’,
’GL_REQUEST_SUBMITTED’);
fnd_message.set_TOKEN(’REQUEST_ID’,
TO_CHAR(:PARAMETER.REQ_ID), FALSE);
fnd_message.show;
END IF;
END IF;
END IF;
Example 2
/* Submit a request where no setup is required */
declare
req_id number;
begin
req_id := FND_REQUEST.SUBMIT_REQUEST (’FND’,
’FNDMDGEN’, ’Message File Generator’,
’01–NOV–02 00:00:00’, FALSE, ...arguments...);
if (req_id = 0) then
/* Handle submission error */
FND_MESSAGE.RETRIEVE;
FND_MESSAGE.ERROR;
else
commit;
end if;
end;
Example 3
/* Submit a request from a database trigger */
result := FND_REQUEST.SET_MODE(TRUE);
req_id := FND_REQUEST.SUBMIT_REQUEST (FND’,
’FNDMDGEN’, ’Message File Generator’,
’01–NOV–02 00:00:00’, FALSE, ...arguments...);
Example 4
/* Submit a request inserting NULL arguments.
This call inserts 6 arguments with arguments 1, 3,
4, and 6 being NULL */
req_id := FND_REQUEST.SUBMIT_REQUEST (’FND’,
’FNDPROG’,
’Description of FNDPROG’,
’01–FEB–01 00:00:00’, FALSE,
’’, ’arg2’, ’’, NULL, arg5, ’’);
Example 5
/* Submit a repeating request */
result := FND_REQUEST.SET_REPEAT_OPTIONS (’’, 4, ’HOURS’,
’END’);
req_id := FND_REQUEST.SUBMIT_REQUEST (’CUS’,
’CUSPOST’, ’Custom Posting’,
’01–APR–01 00:00:00’, FALSE,
...arguments...);
Attention: You may not want to submit a request if
FND_REQUEST.SET_REPEAT_OPTIONS returns failure.
Thus, you may wish to test the result of
FND_REQUEST.SET_REPEAT_OPTIONS before issuing the
call to FND_REQUEST.SUBMIT_REQUEST.
Example 6
/* Submit a request for 5 copies of a menu report */
result := FND_REQUEST.SET_PRINT_OPTIONS (’hqunx138’,
’Landscape’,
5,
’Yes’,
FALSE);
req_id := FND_REQUEST.SUBMIT_REQUEST (’FND’,
’FNDMNRMT’,
’’,
’’,
’N’, 0, 101);
Example 7
/* Submit a protected request that repeats at noon */
result := FND_REQUEST.SET_OPTIONS (’YES’);
result := FND_REQUEST.SET_REPEAT_OPTIONS (’12:00’);
req_id := FND_REQUEST.SUBMIT_REQUEST (’CUS’,
’CUSPOST’, ’Custom Posting’,
’01–APR–01 00:00:00’, FALSE,
... args ...);

create concurrent programs from database

Concurrent program register from Back End using FND API's

API's used are
1)FND_PROGRAM.executable  is used for defining executable .

Tables Affecting FND_EXECUTABLES and FND_EXECUTABLES_TL

BEGIN
  FND_PROGRAM.executable(executable => XX_TT_TEST' ,    -- Executable Name
  application=>'XXTT' ,    -- Application Short Name
  short_name=>'XX_TT_TEST' ,    -- Executable Short Name
  description=>'Test Executable created from Backend' ,     -- Description,DEFAULT NULL
  execution_method=>'PL/SQL Stored Procedure',              -- Execution Method
  execution_file_name=>'XXTT_TEST_PROCEDURE' ,              -- Execution File Name,DEFAULT NULL
  subroutine_name=>NULL ,                                   -- Subroutine Name,DEFAULT NULL
  icon_name=>NULL ,                                         -- Icon Name,DEFAULT NULL
  language_code=>'US' ,                                     -- Language Code,DEFAULT 'US'
  execution_file_path=>NULL                                 -- Execution File Path, DEFAULT NULL
  );
  COMMIT;
END;

Exploring Oracle Apps

I am Oracle Techno Functional . By publishing this blog , my aim to is to share my knowledge and finding on Oracle Apps . I will try to update this blog as much I can possible to share our knowledge . If you like my blog and you think that my blog can help so many like you then please refer my blog to your friends . You can send your queries and feed back to me so that I can help and improve myself also .