Skip to main content

Posts

What is Pre-Approved Status of Requisition/Purchase Order in Oracle purchasing?

Pre-Approved Status Definition Pre–Approved document is one in which a person with the final authority to approve the purchasing document approves it, but then forwards it to someone else for additional approval, thus changing its status to Pre–Approved. OR If we uses encumbrance budgeting (reserves funds for documents), and the purchasing document is eligible for approval but funds have not yet been reserved for it. Even if someone with sufficient approval authority approves this document, its status may still remain Pre–Approved if funds were not able to be reserved at the time of approval. Once funds have been reserved for the approved document, the document changes its status to Approved. A Pre–Approved Requisition does not show up in Auto Create window for PO Creation until its status changes to Approved.
Post a Comment
Read more

Query to find the ERROR Workflow Activities for a Particular Item Type

SELECT   ias . item_type ,         IAS . item_key ,         pa . instance_label ,         pa . process_name   activity ,         ias . activity_result_code ,         Count ( * ) FROM     apps . wf_item_activity_statuses   ias ,         apps . wf_process_activities   pa WHERE    1   =   1         AND   ias . item_type   LIKE   :item_type -- Eg: REQAPPRV for Requisition Approval         AND   ias . process_activity   =   pa . instance_id         AND   ias . activity_status   =   'ERROR' GROUP    BY   ias . item_type ,      ...
Post a Comment
Read more

Query to find the Rejected and In Process POs

SELECT   pha . segment1 ,         pha . authorization_status ,         pha . creation_date ,         pha . last_update_date ,         ( SELECT   pa . segment1          FROM     apps . pa_projects_all   pa          WHERE    pa . project_id   =   pda . project_id )   project_name ,         ( SELECT   task_name          FROM     apps . pa_tasks   pt          WHERE    pt . project_id   =   pda . project_id                 AND   pt . task_id   =   pda . task_id ) ...
Post a Comment
Read more

Grouping of Requisitions to PO During Auto Create

We have 2 Options for Grouping while Auto Creating the Requisition to Purchase Order. Default:  Combine requisition lines for the same item, revision, line type, unit of measure, supplier item number, and transaction reason onto one purchase order line. Additionally, we can add need-by date or ship-to organization and location to the default grouping by using the profiles       a) PO: Use Need-by Date for Default Autocreate grouping and       b) PO: Use Ship-to Organization and Location for Default Autocreate grouping. Requisition: Create document with one line for each requisition line. Used only when you select lines on a single requisition. We can also control the values (Default or Requisition) using a Profile PO: Default Requisition Grouping
Post a Comment
Read more

Query to verify the locked session on a Table

Query to verify the locked session on WF_NOTIFICATIONS Table SELECT do.owner,        do.object_name,        do.object_type,        dl.session_id,        vs.serial#,        vs.program,        vs.machine,        vs.osuser FROM   dba_locks dl,        dba_objects do,        v$session vs WHERE  do.object_name = 'WF_NOTIFICATIONS'        AND do.object_type = 'TABLE'        AND dl.lock_id1 = do.object_id        AND vs.sid = dl.session_id; 
Post a Comment
Read more

Query to find all POs Over a Particular Amount for a Period of time

SELECT   segment1 ,         Sum ( pl . unit_price   *   pl . quantity ) FROM     po_lines_all   pl ,         po_headers_all   ph WHERE    ph . po_header_id   =   pl . po_header_id         AND   ph . creation_date   >   sysdate   -   400 GROUP    BY   segment1 HAVING   Sum ( pl . unit_price   *   pl . quantity )   >=   250000  
Post a Comment
Read more