Sei sulla pagina 1di 3

1.

Why do we call FND SRWINIT from Before Report Trigger


A. FND SRWINIT fetches concurrent request information and sets up the profile op
tions. It must be included if one is using any ORACLE APPLICATION OBJECT LIBRARY
features in his report (such as concurrent processing)
2.Why do we call FND SRWEXIT from After Report Trigger
A.FND SRWEXIT frees all the memory allocations done in other Oracle Applications
user exits. It must be included if one is using any ORACLE APPLICATION OBJECT L
IBRARY features in his report (such as concurrent processing)
3. Why do we call FND FLEXSQL from the Before Report Trigger?
A.One need to pass the concatenated segment values from the underlying code comb
inations table to the user exit so that it can display appropriate data and deri
ve any description and values from switched value sets as needed. One gets this
information by calling the AOL user exit FND FLEXSQL from the before report Trig
ger.
4. If u call the user exit FND FLEXSQL with MODE = WHERE from the Before Report T
rigger. What will it do?
A. This user exit populates a lexical parameter that you specify with the approp
riate SQL fragment at run time. You include this lexical parameter in the WHERE
clause of the report query. This user exit is called once for each lexical to be
changed.
5. If u call the user exit FND FLEXSQL with MODE = ORDER BY from the Before Repor
t Trigger. What will it do?
A. This user Exit populates the lexical parameter that one specifies with the ap
propriate SQL fragment at run time. One includes this lexical parameter in the O
RDER BY clause of the report query. This user exit is called once for each lexic
al to be changed.
6. How can we display flexfield segment values, descriptions, and prompts on the
report?
A. Create a formula Column. Call the user exit FND FLEXIDVAL as the formula for
this column. This user exit automatically fetches more complicated information s
uch as descriptions and prompts so that one does not has to use complicated tabl
e joins to the flex field tables.
7. Name some options of the FND FLEXSQL user exit
A CODE, APP_SHORT_NAME, OUTPUT, MODE, DISPLAY, SHOWDEPSEG, NUM or MULTINUM, TABL
EALIAS, OPERATOR, OPERAND1, OPERAND2.
8. Describe CODE option of the FND FLEXSQL user exit
A. Specify the flex field code for the report (for example, GL#, MCAT).
9. Describe the APP_SHORT_NAME option of the FND FLEXSQL user exit
A. Specifies the short name of the application that owns the flex field (for exa
mple: SQLGL, INV)
10. Describe the OUTPUT option of the FND FLEXSQL user exit
A. Specify the name of the lexical parameter to store the SQl fragment. One uses
this lexical later in the report when defining the SQL statement that selects t
he flexfield values. the datatype of this parameter should be character.

11. Describe the MODE option of the FND FLEXSQL user exit
A. Specify the mode to use to generate the SQL fragment . valid mode are :
SELECT: Retrieves all segments values in an internal (non- displayable format).
WHERE: Restrict the query by specifying constraints on flexfield columns. The fr
agment returned includes the correct decode statement if one specifies MULTINUM.
One must also specify an OPERATOR and OPERANDS.
HAVING: Same calling procedures and functionality as WHERE.
ORDER BY: Order required information by flexfield columns. The fragment Orders y
our flexfield columns and separates them with a comma. The fragment returned inc
ludes the correct decode statement, one specifies in MULTINUM.
12. Describe the DISPLAY option of the FND FLEXSQL user exit
A. One uses the DISPLAY token with the MODE token . the DISPLAY parameter allows
you to specify segments that represent specified flexfield qualifiers or specif
ied segments numbers , where the segment numbers are the order in that the segme
nts appear in the flexfield window, not the segment number specified in the Defi
ne Key Segments form.
Eg. If your MODE is SELECT and you specify DISPLAY = ALL then the SELECT statement
includes all the segments of the flexfield. . Similarly, if your MODE is WHERE
and you specify DISPLAY = ALL , then your WHERE clause includes all segments.
13. Describe the SHOWDEPSEG option of the FND FLEXSQL user exit
A. SHOWDEPSEG = N disables automatic addition of depended upon segments to the ord
er criteria. The default is Y . This token is valid only for MODE = ODER BY In FLEXSQ
L.
14. Describe the NUM option of the FND FLEXSQL user exit
A. Specify the name or lexical or source column that contains the flexfield stru
cture information. If the flexfield uses just one structure, specify NUM only an
d use a lexical parameter to hold the value. If the flexfield uses multiple stru
ctures, specify MULTINUM only and use a source column to hold the value. The def
ault value is 101.
15. Describe the TABLE ALIAS option of the FND FLEXSQL user exit
A. You use TABLE ALIAS if your SELECT joins to other flexfield tables or uses a
self join.
16. Describe the OPERATOR option of the FND FLEXSQL user exit
A. Specify an operator to use in the WHERE clause.
17. Describe the OPERAND1 option of the FND FLEXSQL user exit
A. Specify an operand to use in the WHERE clause,
18. Describe the OPERAND2 option of the FND FLEXSQL user exit
A. Specify a second operand to use with OPERATOR = BETWEEN
19. Where is FND FLEXIDVAL user exit used
A. Call this user exit to populate fields for display. You pass the key flex fie
lds data retrieved by the query into this user exit from the formula column. Wit
h this exit you can display values, descriptions and prompts by passing appropri
ate token (any one of VALUE, DECRIPTION<APROMPT or LPROMPT).
21. Name the interface tables used for the customer interface?
A. 1. RA_CUSTOMERS_INTERFACE_ALL
2. RA_CUSTOMER_BANKS_INT_ALL
3. RA_CUST_PAY_METHOD_INT_ALL
4. RA_CUSTOMER_PROFILES_INT_ALL
5. RA_CONTACT_PHONES_INT_ALL
22 What is the name of the column in CUSTOMER_INTERFACE_TABLE that indicates whe
ther you are inserting new or updating existing information?
A: When importing data into the interface tables, the column INSERT_UPDATE_FLAG
indicates whether you are inserting new or updating existing information. This c
olumn is required in RA_CUSTOMERS_INTERFACE.
23 If the INSERT_UPDATE_FLAG is not set correctly or the required column is miss
ing the value, will CUSTOMER INTERFACE reject the entire record or just the attr
ibutes u want to update?
A Reject the entire record.
24 List some of the required columns for the RA_CUSTOMERS_INTERFACE?
A. ORIG_SYSTEM_CUSTOMER_REF
INSERT_UPDATE_FLAG
CUSTOMER_NAME
CUSTOMER_NUMBER (if you are not using Automatic Customer Numbering)
CUSTOMER_STATUS
LAST_UPDATED_BY
LAST_UPDATE_DATE
CREATED_BY
CREATION_DATE
If you are importing an address and a business purpose, you must also populate t
he following columns:
PRIMARY_SITE_USE_FLAG (if you are inserting an address)
LOCATION (if you are not using Automatic Site Numbering)
SITE_USE_CODE (if you are inserting an address)
ADDRESS1
25 List some of the production tables that Customer Interface transfers customer
data from the interface tables into?
A. AR_CUSTOMER_PROFILES
AR_CUSTOMER_PROFILE_AMOUNTS
RA_ADDRESSES
RA_CONTACTS
RA_CUSTOMERS
RA_CUSTOMER_RELATIONSHIPS
RA_CUST_RECEIPT_METHODS
RA_PHONES
RA_SITE_USES
AP_BANK_ACCOUNT_USES
AP_BANK_ACCOUNTS
AP_BANK_BRANCHES
Find more questions in attachement -

Receive Free Email Updates:: Jobs , Interview Questions, Placement Paper


Read more: http://www.placementpapers.us/oracle_apps/364-oracle_apps_11i_intervi
ew_questionnaire.html#ixzz1BTy7Xo5T
Under Creative Commons License: Attribution

Potrebbero piacerti anche