Skip to main content

OAF Personalization & Migration


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/responsibility/2007/QuickUpdatePG

** 2007 – Responsibility ID

     Check the xml code generated by system for personalization
BEGIN
JDR_UTILS.PRINTDOCUMENT('/oracle/apps/pos/supplier/webui/customizations/responsibility/2007/QuickUpdatePG');
END;

     <?xml version='1.0' encoding='UTF-8'?>
<customization xmlns="http://xmlns.oracle.com/jrad" version="9.0.6.0.0_35" xml:lang="en-US" customizes="/oracle/apps/pos/supplier/webui/QuickUpdatePG">
   <modifications>
      <modify element="SupplierName" readOnly="true"/>
</modifications>
</customization>

      Save the above xml code as QuickUpdatePG.xml
     Create the below files structure at your local disk and place the QuickUpdatePG.xml in 2007/
     xxXXX/oracle/apps/pos/supplier/webui/customizations/responsibility/2007/

    Create another folder under responsibility named 2008 for responsibility Payables Manager and place the QuickUpdatePG.xml
   xxXXX/oracle/apps/pos/supplier/webui/customizations/responsibility/2008/

    Zip the xxXXX folder to xxXXX.zip
     Place the xxXXX.zip file and install script (XXXXX_OAF_PERS_RESP_LEVEL.sh) to unix box
     Execute script - XXXXX_OAF_PERS_RESP_LEVEL.sh with following parameters
1)      APPS username
2)      APPS pwd
3)      DB IP Address – Host Name
4)      DB Port Number
5)      DB SID
6)      Responsibility Id – Target Responsibility Id
7)      Log File Name


POST Successful execution of Install script -

Responsibility XXX Co Payables Manager –

10)   Check the personalization from back end
BEGIN
JDR_UTILS.LISTCUSTOMIZATIONS('/oracle/apps/pos/supplier/webui/QuickUpdatePG');
END;
/

/oracle/apps/pos/supplier/webui/customizations/responsibility/2007/QuickUpdatePG
/oracle/apps/pos/supplier/webui/customizations/responsibility/2008/QuickUpdatePG


** 2008– Responsibility ID for XXX Co Payables Manager


11)   Check the xml code generated by system for personalization
BEGIN
JDR_UTILS.PRINTDOCUMENT('/oracle/apps/pos/supplier/webui/customizations/responsibility/2008/QuickUpdatePG');
END;

<?xml version='1.0' encoding='UTF-8'?>
<customization xmlns="http://xmlns.oracle.com/jrad" version="9.0.6.0.0_35" xml:lang="en-US" customizes="/oracle/apps/pos/supplier/webui/QuickUpdatePG">
   <modifications>
      <modify element="SupplierName" readOnly="true"/>
     
</modifications>
</customization>

12)   Sometime personalization does not reflect immediate to the target responsibility. Please
Logout and login again to application. Open the Page, click on personalization link.
Click on pencil symbol for any personalized item check the field value and press apply. 

  III) OA Personalization using Functional Administrator Responsibility

a)      Login to Application
b)      Select Functional Administrator Responsibility
c)       Click the Personalization Tab then Application Catalog
d)      Give the complete path with page name in Document Path field and press Go

e)      If there exist any personalization It has Personalized = Yes otherwise No.
f)       To do any personalization on this page click the pencil icon on Personalize Page, It will navigate you to same page as you click on personalization link on this page
g)      Using Manage Personalization pencil icon, you can delete or activate/deactivate the existing personalization.

Import Export of OA Personalization –
1)      Set the path to profile FND: Personalization Document Root Path (path where the exported personalization will reside)
2)      Click on Import/Export link followed by Personalization Repository link
3)      Search for your personalization and select those need to be exported
4)      Click Export To File System button
5)      Personalized file ( with xml extn) with full repository structure exported to given path

6)      To import the existing personalization place the xml file with complete file structure to the root path defined
7)      For single file import select the check box or directly check the root path for all files and click Import From File System.

SQL Script to Delete Personalization –

Begin
jdr_utils.deletedocument(p_document=>'/oracle/apps/pos/supplier/webui/customizations/site/0/QuickUpdatePG');
END;


Comments

Post a Comment

Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  
Post a Comment
Read more

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l
Post a Comment
Read more

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table
Post a Comment
Read more