Sreekanth Reddy Pothula's Oracle ERP Blog

Oracle officially announced on Sep 15th 2016 that Oracle E-Business Suite Release 12.2.6 is now available. Please refer the below links/Metalink notes for more details about R12.2.6  1) Read Me :     Oracle E-Business Suite Release 12.2.6 Readme (Doc ID 2114016.1) 2) EBS 12.2.6 highlights video with Cliff Godwin, Senior Vice President of Application Development  3) Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for Release 12.2.6 (Doc ID 2149555.1) 4) Refer the Below Release Content Documents (RCD) Metalink Note to identify the major differences/enhancements in R12.2.6 compared to previous versions. R12.1 / R12.2 : Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Documents (Doc ID 1302189.1) 5) Common Questions and Answers About Upgrading a)  Is there a direct upgrade path from Release 11i to Release 12.2.6?       No. Release 11i customers must first upgrade to Release 12.2 before applying 12.2.6. b)  Is there a direct u

When we use AME for Expense Report approvals, When an authorized delegate submits an expense report for another employee, the 'AME Approval Process/CC Direct Manager' sends a FYI notification t to the supervisor of the preparer. This is a new feature introduced in R12.1.3 as part of RUP4. This is a good feature from a manager perspective to track the activities performed by all the employees reporting to him. But some companies don't like this feature depends upon their business needs. Here are the steps to follow to disable this extra notification -  Method1 :Download the workflow file and modify the WF attribues 1. Open the APEXP.wft file and double click on 'IS_MANAGER_IN_THE_APPR_PROCESS' Process 2. Click on the Node Attributes and here we have an attribute named 'CC Direct Manager Notification'. 3. Update the value to No, save the workflow file to the database. 4. Bounce the workflow listeners as well as the mid-tier servers.  M

Once the Expense Repot is converted to Invoice using the standard 'Expense Report Export Program' The invoice date  is  nothing but  'week_end_date' column populated on the ap_expense_report_headers_all table. Below is the logc used behing the screens to populate 'week_end_date' 1) If Expense Report Header is just entered and saved, the Expesne report header entry day will be the week_end_date 2) While entering an expense report line, you can select date on the expense report line: which is stored as expese_start_date 3) Also in the details when you enter No of days: expense_end_date will be calculated as expese_start_date+no.of.days 4) Once the expense_end_Date is populated, the weekend_date on the expense report header or Invoice_date, is nothing but the maximum value of the expense_end_Date of all lines.

 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 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