Sei sulla pagina 1di 5

SOME IMPORTANT APIS

FND_PROFILE: User Profile APIs

FND_PROFILE.PUT

Procedure FND_PROFILE.PUT
(name IN varchar2,
value IN varchar2);

Puts a value to the specified user profile option. If the option does not exist, you can also
create it with PUT.

Arguments (input)
name -- The (developer) name of the profile option you want to set.
value -- The value to set in the specified profile option.

FND_PROFILE.GET

procedure FND_PROFILE.GET
(name IN varchar2,
value OUT varchar2);
Gets the current value of the specified user profile option, or NULL if the profile does not
exist.

Arguments (input)
name -- The (developer) name of the profile option whose value you want to retrieve

Arguments (output)
value --The current value of the specified user profile option as last set by PUT or as
defaulted in the current users profile.

Example
FND_PROFILE.GET (USER_ID, user_id);

FND_PROFILE.VALUE

function FND_PROFILE.VALUE
(name IN varchar2) return varchar2;
VALUE works exactly like GET, except it returns the value of the specified profile option
as a function result.

Arguments (input)

name --The (developer) name of the profile option whose value you want to retrieve.
FND_CONCURRENT Package
FND_CONCURRENT.GET_REQUEST_STATUS
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;

Returns the status of a concurrent request. If the request has already completed, also
returns a completion message.

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 Short name of the concurrent program (not the executable). 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 userfriendly request phase from FND_LOOKUPS.
Status--The userfriendly 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;
FND_CONCURRENT.WAIT_FOR_REQUEST (Client or Server)\

function FND_CONCURRENT.WAIT_FOR_REQUEST
(request_id IN number default NULL,
interval IN number default 60,
max_wait IN number default 0,
phase OUT varchar2,
status OUT varchar2,
dev_phase OUT varchar2,
dev_status OUT varchar2,
message OUT varchar2) return boolean;

Waits for request completion, then returns the request phase/status and completion
message to the caller. Goes to sleep between checks for request completion.

Arguments (input)

request_id The request ID of the request to wait on.

interval Number of seconds to wait between checks (i.e., number of seconds to


sleep.)
max_wait The maximum time in seconds to wait for the requests completion.

Arguments (output)

Phase--The userfriendly request phase from the FND_LOOKUPS table.

Status--The userfriendly request status from the FND_LOOKUPS table.

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 already completed.


FND_FILE: PL/SQL File I/O
FND_FILE.PUT_LINE
procedure FND_FILE.PUT_LINE
(which IN NUMBER,
buff IN VARCHAR2);

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.

fnd_file.put_line(FND_FILE.LOG,Warning: Employee || l_log_employee_name|| (||


l_log_employee_num || ) does not have a manager.);

FND_PROGRAM: Concurrent Program Loaders


FND_PROGRAM.EXECUTABLE
procedure FND_PROGRAM.EXECUTABLE
(executable IN VARCHAR2,
application IN VARCHAR2,
description IN VARCHAR2 DEFAULT NULL,
execution_method IN VARCHAR2,
execution_file_name IN VARCHAR2 DEFAULT NULL,
subroutine_name IN VARCHAR2 DEFAULT NULL,
icon_name IN VARCHAR2 DEFAULT NULL,
language_code IN VARCHAR2 DEFAULT US);
Use this procedure to define a concurrent program executable. This procedure
corresponds to the Concurrent Program Executable window accessible from the System
Administrator and Application Developer responsibilities.
Arguments (input)
executable Name of executable (for example, FNDSCRMT).
application The short name of the executables application, for example, FND.
description Optional description of the executable.
execution_method The type of program this executable uses. Possible values are
Host, Immediate, Oracle Reports, PL/SQL Stored Procedure, Spawned,
SQL*Loader, SQL*Plus.
execution_file_name The operating system name of the file. Required for all but
Immediate programs. This file name should not include spaces or periods unless the file
is a PL/SQL stored procedure.
subroutine_name Used only by Immediate programs. Cannot contain spaces or periods.
icon_name Reserved for future use by internal developers
only. Specify NULL.
language_code
Language code for the name and description, for example, US.