ERP Genius Guide

Restrict Creation of #PO without a #P R Sometimes Businesses do not allow a #PO to be created manually. There are several ways through which we can restrict the creation of #PO without a requisition in #Oracle #EBS #R12. The blog discusses two different methods to achieve this goal. Introduction:  At times, businesses necessitate a requisition as a prerequisite for generating a #Purchase_Order (#PO). This blog will enlighten you on the procedure to prevent users from creating a #PO without a corresponding requisition. In #Oracle Purchasing, there are two methods for #PO creation: • Manual creation via the #Purchase #Order form. • Automatic creation from a requisition through the Autocreate function. There are instances where manual creation of a PO is not permissible. In #Oracle #EBS, there are two distinct approaches to enforce the restriction on creating a #PO without a linked requisition: Option 1 Employing form personalization on the #Oracle Purchasing form, speci...

  Track User activity in #Oracle Application - #EBS R12 / Query to #Audit user activity on #Oracle  #Forms How to Audit User Activity in Oracle Database *---------------------------------------------------------------* Pre-requisite: Set the Profile option "Sign-On:Audit Level" = 'Form' This profile option can be enabled at Site level or any specific user. It will populate the data in below tables: FND_LOGINS FND_LOGIN_RESPONSIBILITIES FND_LOGIN_RESP_FORMS SQL Query Run below #SQL query to extract the user activity details on #ERP application: "SELECT frtl.RESPONSIBILITY_NAME , fft.USER_FORM_NAME , flf.START_TIME, flf.END_TIME   FROM FND_LOGIN_RESP_FORMS flf,        FND_LOGINS fl,        FND_LOGIN_RESPONSIBILITIES flr,        FND_RESPONSIBILITY_TL FRTL,        FND_FORM_TL fft  WHERE     FLf.LOGIN_ID = FL.LOGIN_ID        and FLR.LOGIN_ID = FL.LOGIN_ID ...