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