Oracle Apps Technical Interview Preparation Guide

Download PDF

Using FNDLOAD commands, which creates.ldt files and import
those .ldt files in new instance using same command.

We use instead of triggers, when dml operations perform on the complex views.

we can use rollback operation in exception block

We can create po three ways
(1)required sheet->requisition->RFQ->Quotation->po
(2) required sheet->requisition->po
(3) required sheet-po(with out requisition for po)

you can create two more dummy parameters(like
p2_dummy,p3_dummmy ) and set display property to no.

now set the default value for p2_dummy as "decode
(p1,'a','Y',null) in the same way for p3_dummmy.

now in the valueset for p2 use where $FLEX$.p2_dummy ='Y'
and similarly for p3.

From Application Developer responsibility, navigate to
Application --> Register. Query for the custom application
name. The value in the field Basepath, is the OS system
variable that stores the actual directory info.

while defining Parameters you can set range option(in
concurrent prog parameters window).
Select low for from_Date and high for to_Date.Then it will
not allow for from_date > to_date.

Request group is where the concurrent programs are attached
to which internally make them available under a
responsibility that the request group is attached to. If
request groups won't be there the program will not be
visible to the user who has a responsibilty attahced.
Data group is nothing but the data base user details with
oracle apps connects UI to DB

RA_INTERFACE_LINES_ALL ,
RA_INTERFACE_DISTRIBUTIONS_ALL ARE THE TWO INTERFACE TABLES
MAINLY USED BT AUTOINVOICE.

FURTHER DATA READ FROM THESE TABLES WILL BE INSERTED INTO
RA_CUSTOMER_TRX_ALL , TA_CUSTOMER_TRX_LINES_ALL ,
RA_CUST_TRX_LINE_GL_DIST_ALL , AR_PAYMENT_SCHEDULES_ALL
AFTER VALIDATING.

Order header status is in oe_order_headers_all table
reference with flow_status_code column and order line
status would be oe_order_lines_all table reference with
flow_status_code column.

In Order ManagementOM) Error Tables are as follows

1.OE_EXP_INTERFACE_ERRORS
2.OE_UPGRADE_ERRORS

There are few reasons that a scheduled order could be
backordered during pick release process.

1. In-sufficient onhand
2. Order might be put as 'Pick release hold'
3. If it's a lot controlled item being involved then some
of the factors will be checking at picking rule setup (like
Lot- expiration date, etc) and tured to 'Backordered'
incase the criteria does not meet.

shiping >>release sales order>>release sales order

after releasing sales order

after executing release sales order automatically 3
concurrent programs will run

one of the conc prg is pick selection list

the output of conc prg tells what orders has been booked

in po_headers_all authorization_status coloumn is their
we can find through this coloumn
select distinct authorization_status from po_headers_all

Result if count(*), count(1), count(0) will be same.

Howevenr,

When we use count(*) then
first oracle query executer gets all the rows in buffure
cache, including all column and then counts all the rows.
this will impact with less performance.


select count(1) or count(0)
This reduces unwanted I/O by selecting just '1' against all
the rows.


Best practice to getting rowcount of table is

select count(rowid) from table_name;

The Oracle standard interface code stays in the oracle apps
database in the form of PL/SQL routines. Without the
database up and running, we can not run the interface code.
After all why do we run the interface, when the oracle apps
is not available.

Set the profile option Concurrent: Debug Level to 5.
Run the report and get the debug log.