Skip to main content


Showing posts from February, 2016

Scripts to Update the Values for Requisition Approval Time-out Reminder Notifications for both New Requisitions and Requisition Change Orders

 Most of the times we receive requests from business to set the value for Requisition Approval Time-out Reminder Notifications for both New Requisitions and Requisition Change Orders.  In all these case, we have to download the corresponding workflow and update the Attribute Value from the corresponding workflow process. Once we made the changes, we have to migrate/save the workflow to the database. Also, in most of the cases it is not possible to Test the Time-out Notifications with Real Value (Eg:- 15 Days, we have to wait for 15 days to receive the Time-out Notification even in Test Instance). To avoid the work related to download and uploading of workflow, the below scripts are very much helpful. We can update to a least value(Eg:- 15 mins for Each Reminder to complete the testing in Test Instances before migrating to PROD). We need to run different scripts for Purchase Requisition and Requisition Change Orders. Note: In all queries, The Time-out value will be shown in Mi

Query to find the Whether the Approver Status is Active or Suspended.

Query to find the Assignment Status for a Particular Employee SELECT           P . full_name ,           PAST . per_system_status   STATUS ,           ORG . NAME                 ORG_NAME ,           p . employee_number ,   FROM     apps . per_people_f   p ,           apps . per_assignments_f   a ,           apps . hr_organization_units   org ,           apps . per_assignment_status_types   past   WHERE    a . person_id   =   p . person_id           AND   a . assignment_status_type_id   =   past . assignment_status_type         AND   a . primary_flag   =   'Y'           AND   Trunc ( sysdate )   BETWEEN   p . effective_start_date   AND                                      p . effective_end_date           AND   Trunc ( sysdate )   BETWEEN   a . effective_start_date   AND                                      a . effective_end_date           AND   a . assignment_type   IN   (   'E' ,   'C'   )           AND   a . organization_id   =   org . organization_id      

Steps to Enable Note To Buyer Field On Shopping Cart Page in iProcurement

 Note To Buyer entered in the iProcurement requisition checkout step applies for only line 1 in the Autocreate form, the below article explains how can the Note To Buyer column be enabled on the Shopping Cart page to allow requisition preparer to enter Note To Buyer for each requisition line. This functionality of Note To Buyer on the checkout page applies only to line 1 of the requisition.  The Note To Buyer value on the checkout step 2 of 3 in iProcurement is a header level value that is saved to PO_REQUISITION_HEADERS_ALL.NOTE_TO_BUYER. Note To Buyer column shown on   the Autocreate form is a line level value that is from PO_REQUISITION_LINES_ALL.NOTE_TO_AGENT.  Per Bug 14035820, iProcurement saves the Note To Buyer header level value to the First Requisition Line Note To Agent line level value, so that the value is shown to the buyer at auto-create in the Note to Buyer (PO_REQUISITION_LINES_ALL.NOTE_TO_AGENT) column. But it is only shown for the first requisition line. We