Friday, 7 June 2013

Value Sets:

It is list of values (LOV) with validations, it will be used to restrict the end user not to enter invalid data.
None: Used to give format conditions like maximum size, only numbers, only characters etc.
Independent: Create the value set name by giving the validation type as ‘independent’. Then enter the values for this set.
Dependent: The list of values will be depends on the independent value set.
Table: If we want to get the values from database table as LOV then we will use this value set.
Translation Independent & Translation Dependent:
Just like Independent and Dependent but values are visible in other than American English language which was mentioned.
Special and Pair: To display values of flex fields.
Executable: It is user defined window where we will mention execution filename, execution method and application name.
Concurrent Program: The combination of application name plus program name uniquely identifies your concurrent program.
Request Group: It is collection of concurrent programs and reports.
Responsibility: It is level of an authority where we will combine request group, menu and data group.
SRS(Standard Request Submission) Window: By using this window we can submit the Concurrent Programs.

SELECT * FROM FND_EXECUTABLES WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_CONCURRENT_PROGRAMS WHERE
TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_REQUEST_GROUPS WHERE
TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_USER WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)


Standards for Report Registration in Oracle Application:
Define one mandatory user parameter ‘P_CONC_REQUEST_ID’
Call the user exit from Before Report Trigger
SRW.USER_EXIT(‘FND SRWINIT’)
Call the another user exit from After Report Trigger
SRW.USER_EXIT(‘FND SRWEXIT’)

P_CONC_REQUEST_ID: We have to define this bind variable in reports where we are using user exits.
When we submit any Concurrent Program from SRS window request id will be generated, this will be transferred to this variable.
Based on this request id  USER_EXITS will be working in reports.
Value Sets:
It is list of values (LOV) with validations, it will be used to restrict the end user not to enter invalid data.
None: Used to give format conditions like maximum size, only numbers, only characters etc.
Independent: Create the value set name by giving the validation type as ‘independent’. Then enter the values for this set.
Dependent: The list of values will be depends on the independent value set.
Table: If we want to get the values from database table as LOV then we will use this value set.
Translation Independent & Translation Dependent:
Just like Independent and Dependent but values are visible in other than American English language which was mentioned.
Special and Pair: To display values of flex fields.
Executable: It is user defined window where we will mention execution filename, execution method and application name.
Concurrent Program: The combination of application name plus program name uniquely identifies your concurrent program.
Request Group: It is collection of concurrent programs and reports.
Responsibility: It is level of an authority where we will combine request group, menu and data group.
SRS(Standard Request Submission) Window: By using this window we can submit the Concurrent Programs.

SELECT * FROM FND_EXECUTABLES WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_CONCURRENT_PROGRAMS WHERE
TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_REQUEST_GROUPS WHERE
TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_USER WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)


Standards for Report Registration in Oracle Application:
Define one mandatory user parameter ‘P_CONC_REQUEST_ID’
Call the user exit from Before Report Trigger
SRW.USER_EXIT(‘FND SRWINIT’)
Call the another user exit from After Report Trigger
SRW.USER_EXIT(‘FND SRWEXIT’)

P_CONC_REQUEST_ID: We have to define this bind variable in reports where we are using user exits.
When we submit any Concurrent Program from SRS window request id will be generated, this will be transferred to this variable.
Based on this request id  USER_EXITS will be working in reports.
Value Sets:
It is list of values (LOV) with validations, it will be used to restrict the end user not to enter invalid data.
None: Used to give format conditions like maximum size, only numbers, only characters etc.
Independent: Create the value set name by giving the validation type as ‘independent’. Then enter the values for this set.
Dependent: The list of values will be depends on the independent value set.
Table: If we want to get the values from database table as LOV then we will use this value set.
Translation Independent & Translation Dependent:
Just like Independent and Dependent but values are visible in other than American English language which was mentioned.
Special and Pair: To display values of flex fields.
Executable: It is user defined window where we will mention execution filename, execution method and application name.
Concurrent Program: The combination of application name plus program name uniquely identifies your concurrent program.
Request Group: It is collection of concurrent programs and reports.
Responsibility: It is level of an authority where we will combine request group, menu and data group.
SRS(Standard Request Submission) Window: By using this window we can submit the Concurrent Programs.

SELECT * FROM FND_EXECUTABLES WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_CONCURRENT_PROGRAMS WHERE
TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_REQUEST_GROUPS WHERE
TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM FND_USER WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)


Standards for Report Registration in Oracle Application:
Define one mandatory user parameter ‘P_CONC_REQUEST_ID’
Call the user exit from Before Report Trigger
SRW.USER_EXIT(‘FND SRWINIT’)
Call the another user exit from After Report Trigger
SRW.USER_EXIT(‘FND SRWEXIT’)

P_CONC_REQUEST_ID: We have to define this bind variable in reports where we are using user exits.
When we submit any Concurrent Program from SRS window request id will be generated, this will be transferred to this variable.
Based on this request id  USER_EXITS will be working in reports.

USER EXISTS:
User Exit is one of the program which will transfer the control from report builder executable to 3rd generation language to get information and completes remaining process.
Total we have five user exits:
FND SRWINIT: We will call this user exist from before report trigger to retrieve user profile values like user id, Responsibility name etc.
FND SRWEXIT: We will call this user exist from after report trigger to freeze the memory which is occupied by user profile values.
FND FLEXSQL: Used to display the flex fields information.
FND FLEXIDVAL: Used to display the flex fields information.
FND FORMATCURRENCY: Used for multiple Currency Reporting.

REPORT PARAMETERS:
If report is having bind parameters we have to define those parameters while registering concurrent program.
 Select ‘parameters’ Button ,enter the seq no and give the parameter name.
VALUESET: It is nothing but list of values which will validate the data.
TOKEN: Token is one of the field which will be used to map concurrent program parameter with report builder bind variable. we have to mention the bind variable name in this token field.

Default Types:
When we want to pass default values for concurrent program parameter then we will use default types. We have 4 default types:
Constant: We can pass constant number or string default value.
Sql Statement: We can define valid SQL settlement (select statement), the result of this query will be pass as default value. This query should retrieve only one value.
Segment: When we want to get any other parameter value as default then we will use this one.
Profile: We will use this one to pass the profile values like org_id, user_id etc as default value.

Out parameters in procedure:
Errbuf: Will be used to send error messages into logfile if any error occurs inside of procedure.
Retcode: Will be used to find out concurrent program status whether it has been completed successfully.
Warnings or errors:
Successfulà0
Warningà1
Errorà2

Fnd File APIs:
We can’t use dbms_output.put_line in oracle applications we will use fnd_file APIs to write the message into output files as well as log files.
Fnd_file.put_line(fnd_file.output,’message’):   Writes the messages into output file.
Fnd_file.put_line(fnd_file.log,’message’):    Writes the messages into log file.

No comments:

Post a Comment