SQL Query to identify the user who ran the concurrent program from backend....................

-

Query will help to know who ran the concurrent program from backend.

select a.request_id,
a.request_date,
a.user_concurrent_program_name,
a.requestor,
a.completion_text,
a.actual_start_date,
a.actual_completion_date,
a.phase_code,
a.status_code,
a.argument_text,
b.logfile_name,
b.logfile_node_name,
b.outfile_name,
b.outfile_node_name,
a.responsibility_id,
c.request_group_id,
c.RESPONSIBILITY_NAME,
c.description,d.*
FROM FND_CONC_REQ_SUMMARY_V a,
fnd_concurrent_requests b,
FND_RESPONSIBILITY_VL c ,
FND_REQUEST_GROUPS d
where 1=1
and a.responsibility_id = c.responsibility_id
-and trunc(a.request_date) >= trunc(sysdate)-8
--and trunc(a.request_date) = '14-Feb-2007'
and a.request_id = b.request_id
and c.request_group_Id = d.request_group_id
- and a.requestor not in ('SYSADMIN')
--and a.user_concurrent_program_name like '%DMR - CANADA BANK CHECK RECONCILIATION OUTBOUND%(CCN)%'--'%AS400%PO%'
and a.user_concurrent_program_name = 'FPC Aging - 4 Buckets by Collector'--'%AS400%PO%'
--and a.argument_text = 'pospoaord14020724093529'
ORDER BY a.request_date desc

Comments

Post a Comment

Popular posts from this blog

Oracle Purchasing Module Step by Step in R12

-
Image
PURCHASING  All the Purchasing related activity information will be declared in Purchasing              Procure 2 Pay Cycle : Requisition à RFQ à Quotation à Quotation Analysis à Purchasing à Receiving à Invoice  à  Payment à Reconciliation PO-Integration :  PO  is integrated by GL, AP, I Supplier, Procurement, and Project Accounting  PO  Responsibility             Step1: Define  PO  Responsibility                         Nav: System administrator à Security à Responsibility à Define             Step2: Assign  PO  options to the PO Responsibility                         Nav: System administrator à Profile à system             Step3: Assign  PO  Responsibility to User                         Nav: System administrator à security à user à define Note:  PO  is including some of i.e. Options, Supplier, Item, Expenses, and Purchasing . Options : Options nothing but a Controlling future at the operating unit level.                         Th
Read more

Difference between ATO and PTO in oracle apps

-
Difference between ATO and PTO in oracle apps 1) MAKE TO ORDER: This is based on Customer specification, you make the product and supply it to them. This is applicable for Engineering items or any Product which you can make based on Customer order Example: Engineering Items 2) ASSEMBLE TO ORDER: This is you have items in parts and it needs to be assembled according to customer requirements For example you have Laptop coming with standard configuration of 160GB Hard disk and 1 GB RAM. But there are customer orders coming in asking for 200GB Hard Disk and 2 GB RAM and if you can assemble them to suit Customer Requirement 3) CONFIGURE TO ORDER: This is Configuring the Product itself to suit Customer requirements Example. The Thread Manufacturing unit Machineries are configured. I have seen Laxmi Machine Works in INDIA which manufactures textile Machineries configure the machineries based on No.of spindles 4) PICK TO ORDER: This is same as Computer Example in ATO. But the  difference is
Read more

Sub Ledger Accounting SLA (Complete Functional Information)

-
Image
SubLegder Accounting in R12 SLA Part -1 In these article, we will explore the very basics of SLA and why it exists. Firstly, what exactly does SLA do? SLA is a module which now sits between the SubLedgers like AP/AR etc and the General Ledger. Have a look at this diagram below.  As you will notice, SLA can act as a mediator between the subledgers and Oracle General Ledger. Before we progress, some terminologies of R12 must be revisited. In 11i we had set of books, and in R12 we call them Ledgers. Likewise in R12 we also have secondary ledgers and reporting ledgers. Hence from 11i perspective think of Ledger as Set of Books. As for Subledger, a Subledger is nothing but a module like AP/AR/PO/Inventory etc. In the diagram below, the second scenario is explained whereby let's say that payables module generates a charge account segment combination for an invoice distribution line as A.B.C.D. In such case, if SLA module is not customized, then the very same A.B.C.D
Read more