Sreekanth Reddy Pothula's Oracle ERP Blog

This article discussed how the accounting flexfield is generated in Oracle iExpenses when employee submits his or her expense report.  For simplicity sake, let’s assume the expense report does not have any multi-currency or credit card items. And as example, let’s assume we are using a simple chart of accounts containing of three segments: Company-Cost Center-Account Our employee belongs to company 100, and cost center 1000. Oracle iExpenses follows these steps to generate his account during the expense report entry: Step 1 : The Default Expense Account Defined in employee’s HR assignment: 100-1000-55555 Step 2 : Employee enters the Expense Report Header. If he does not override the Cost Center, iExpenses proceeds to Step 3. If he does override the Cost Center (e.g. 2000), Oracle iExpenses builds an initial accounting combination of his Default Expense Account with his new Override Department. 100- 2000 -55555 The Feature : If this initial combinati

Query to find All VO Substitutions SELECT   PATH . path_docid                                     PERZ_DOC_ID ,           jdr_mds_internal . Getdocumentname ( PATH . path_docid )   PERZ_DOC_PATH   FROM     jdr_paths   PATH   WHERE    PATH . path_docid   IN   ( SELECT   DISTINCT   comp_docid                               FROM     jdr_components                               WHERE    comp_seq   =   0                                      AND   comp_element   =   'customization'                                      AND   comp_id   IS   NULL )           AND   (   jdr_mds_internal . Getdocumentname ( PATH . path_docid )   )   LIKE   '%VO%'   ORDER    BY   perz_doc_path ;   In order to delete the customization definition, use the below call - BEGIN   jdr_utils . Deletedocument ( '/oracle/apps/icx/por/reqmgmt/server/customizations/site/0/AllReqsVO' ) ; END ;   BEGIN   jdr_utils . Deletedocument ( '/oracle/apps/fnd/server/customizations/site/

1) For all Modules SELECT   PATH . path_docid                                     PERZ_DOC_ID ,           jdr_mds_internal . Getdocumentname ( PATH . path_docid )   PERZ_DOC_PATH   FROM     jdr_paths   PATH   WHERE    PATH . path_docid   IN   ( SELECT   DISTINCT   comp_docid                               FROM     jdr_components                               WHERE    comp_seq   =   0                                      AND   comp_element   =   'customization'                                      AND   comp_id   IS   NULL )   ORDER    BY   perz_doc_path ;   2) For iProcurement Module SELECT   PATH . path_docid                                     PERZ_DOC_ID ,           jdr_mds_internal . Getdocumentname ( PATH . path_docid )   PERZ_DOC_PATH   FROM     jdr_paths   PATH   WHERE    PATH . path_docid   IN   ( SELECT   DISTINCT   comp_docid                               FROM     jdr_components                               WHERE    comp_seq   =   0            

I) OAF Personalization – Objective – Make a field read only through personalization Bean Name – Search Published Negotiations available on Sourcing Page 1)        Open the page where personalization is required and Click on Personalize Page link available on right top of the page 2)        Check for the target bean and click the pencil symbol 3)        Check for the read only property  4)         Set the property value for Read Only = TRUE at Responsibility level and press apply button. 5)        Return to Application and check the personalized bean            II) Migration of OAF Personalization – Responsibility Purchasing Super User  Personalized the header detail of supplier page to make fields read only   2         Check the personalization from back end BEGIN JDR_UTILS . LISTCUSTOMIZATIONS ( '/oracle/apps/pos/supplier/webui/QuickUpdatePG' ); END; / /oracle/apps/pos/supplier/webui/customizations/responsibi