MWA/MSCA Customization ERROR

Dear all,
My requirement is to Customize a Page
where i have FListener & Page file but not able to find Function File
I have checked the the menu>function>it adress to a different Function File... where on condition it is pointing to different Page ..bt my page is not listed
Now my Requirement is to_
Customize the Page of which i am not able to find the Function File
Edited by: 248 on Nov 18, 2012 10:02 PM

Hi,
Are you using MSCA Personalization/Did you recently apply any MSCA Patch?
Did you recent setup/updated DFF on receiving transactions/header? Just try recompiling the DFF.
or Did you change any profile option that has impact on MSCA?
Just bounce the MWA server, it should work.
Else, you will have to log a SR.
Hrishikesh

Similar Messages

  • How to Customize Error message in JXL

    Hi All,
    I want to customize error message in JXL. I.e. When we apply number validation to a cell and if you enter invalid data MS-Excel shows error message saying that "The value you entered is not valid". But I want to customize this message to "Data should be a decimal number". Can anyone help me how to acheive it. Thanks in Advance.
    Thanks
    Venkat.

    Thx alot...!! for all your valuable replies.
    And, I found a way to achieve my requirement in a declarative way.
    I just created an entity validator on EmployeeEO.
    - Rule_Type: Key Exists
    - Rule Definition:
    - Validation Target Type: Entity Object
    - Association Name : <Select Assiociation created > "EmpDeptFK"
    - Failure Handling:
    - Error Message: "Invalid Deparment ID {0} Entered. Please enter a valid Department ID."
    - Message Token for "0": Department ID
    And It fulfilled my requirement.

  • Customize error-pages in portal

    Hello!
    How to customize error-pages (e.g. error 500, 404, 403...) in an application
    running within the portal (e.g. BEx Web Analyzer) ?
    Via the visual administrator it is possible to customize error-pages for
    a single applications (=> Server => Services => Web Container => choose an
    application => Btn. View => Tab. Pages => Tab. Error Pages)
    - but how to costomize all error-pages for all applications running within the portal ?
    Greetings
    Frank Ruggaber

    Hi madhvika,
    One way you can modify the standard error msgs is using Custom Error msgs which you can define in the web.xml deployment descriptor of your application.
    (/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-infweb.xml):
    Check [custom error pages|http://help.sap.com/saphelp_nw04/helpdata/en/9a/e74d426332bd30e10000000a155106/frameset.htm
    you can use the first method - Error msgs mapped to error codes.You can create your own static html and write your own customised error msg in that instead of the usual 404 error : Resource not found.
    I think the standard error msgs are not stored in portal...not sure though.I think they are defined in the J2EE engine as parameters.Have to chek on that once.
    Or probably if u have KM installed then these error msgs can be directed to a file stored in KM and the respective msg can be displayed.....again storing as static html.
    Reward points if useful.
    Cheers,
    Abhishek
    P.S: How are you?

  • SAP CRM ISA for B2B B2C How I can set customize error page in SAP J2EE 6.40

    Hi,
    I am trying to change default error mesaage which is comming from SAP J2EE engine in SAP CRM ISA B2B and B2C application.
    I want to set different customize error(400, 401,403,500 etc..) pages designed in HTML in B2B and B2C of SAP CRM ISA application.
    If any one has any idea how to do it pl. let me know.
    Thanks.
    Ashish Patel.

    Hi,
    Except for the application error pages you should also keep in mind that some error pages are generated by SAP Webdispatcher - presuming you are using one in front of your J2EE-Engine 
    You find some information about this type of error pages under  <a href="http://help.sap.com/saphelp_webas630/helpdata/en/f6/3c0b0389cea34ba66f10d62b718a1a/frameset.htm">help.sap.com</a>
    Best regards,
    Frank

  • Customize Error Message Page - Oracle Portal

    Hi,
    Please how i can customize Error Message Page ? or just the page not found ?
    tks
    carlo

    This is documented in the Portal admin guides.
    Make a copy of the standard error page (in the navigator) then change the portal configuration (in builder) and tell it to use your own page.

  • Customize error-page

    Hi all,
    May I customize error page for HTTP Status 401 (http authentication error)? I am using <auth-method>BASIC</auth-method> , therefore
    <form-error-page>/xxx.jsp</form-error-page> is not working, please advise.
    Thx.
    Jacky

    Use <error-page>/error.html</error-page> element

  • CCX Editor Customizer Error

    I am running Windows 7 and I have installed CCX Editor in XP Mode
    The last version worked fine however when we upgraded to 7.0(1)SR04_Build443 I uninstalled the older editor and installed the new.  Now when I go to the properties of the steps I get a Error Box with the Title "Customizer Error" There is no wording in the window itself and thier is a red "X" and OK button.  After clicking the OK button it open the customize windown with the wording "Nothing to customize"  Has anyone ran into this error and know how to fix it?

    Hello All,
    I received this error msg too at uccx 7.0 sr5, i followed the wikidoc changes and then it gave another error msg of java.lan.nullpointer exception".  for troubleshooting , i followed the instructions from below mentioned link and got the problem fixed.
    http://www.cisco.com/en/US/products/sw/custcosw/ps1846/products_tech_note09186a0080b04518.shtml
    I hope, it would be useful for someone in future.
    Thanks
    Regards,
    Waqas

  • Oracle MSCA: Customization in Standard ShipLPN page

    Hi,
    I am trying to extend the standard ShipLPN page in Oracle MSCA, but when I am trying to run this page, after entering the value of organization id it is redirecting it to menu.
    Error in log file is:
    SM_EXCEPTION: Exception occurred with user KD34209
    java.lang.reflect.InvocationTargetException
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at oracle.apps.mwa.container.StateMachine.loadPage(StateMachine.java:1405)
         at oracle.apps.mwa.container.StateMachine.handleEvent(StateMachine.java:1056)
         at oracle.apps.mwa.container.StateMachine.handleEvent(StateMachine.java:898)
         at oracle.apps.mwa.container.StateMachine.handleEvent(StateMachine.java:1185)
         at oracle.apps.mwa.presentation.telnet.PresentationManager.handle(PresentationManager.java:743)
         at oracle.apps.mwa.presentation.telnet.ProtocolHandler.run(ProtocolHandler.java:849)
    Caused by: java.lang.NullPointerException
         at oracle.apps.inv.wshtxn.server.ShipLPNPage.initPrompts(ShipLPNPage.java:143)
         at oracle.apps.inv.wshtxn.server.ShipLPNPage.<init>(ShipLPNPage.java:55)
         at oracle.apps.inv.wshtxn.server.ShipLPNPageXX.<init>(ShipLPNPageXX.java:17)
         ... 10 more
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) SM_EXCEPTION: Exception occurred with user KD34209
    java.lang.NullPointerException
         at oracle.apps.inv.wshtxn.server.ShipLPNPage.initPrompts(ShipLPNPage.java:143)
         at oracle.apps.inv.wshtxn.server.ShipLPNPage.<init>(ShipLPNPage.java:55)
         at oracle.apps.inv.wshtxn.server.ShipLPNPageXX.<init>(ShipLPNPageXX.java:17)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at oracle.apps.mwa.container.StateMachine.loadPage(StateMachine.java:1405)
         at oracle.apps.mwa.container.StateMachine.handleEvent(StateMachine.java:1056)
         at oracle.apps.mwa.container.StateMachine.handleEvent(StateMachine.java:898)
         at oracle.apps.mwa.container.StateMachine.handleEvent(StateMachine.java:1185)
         at oracle.apps.mwa.presentation.telnet.PresentationManager.handle(PresentationManager.java:743)
         at oracle.apps.mwa.presentation.telnet.ProtocolHandler.run(ProtocolHandler.java:849)
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) (KD34209) handleEvent: entering new page (pageIx = 2)
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) (KD34209) callListeners: executing 1 listeners, action = 0
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) (KD34209) callListeners: PageBean
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN8
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN7
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN6
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN5
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN4
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN3
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN2
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN1
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN0
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) removeFieldBean: fieldName = oracle.apps.mwa.beans.MenuPageBean.MENUITEMBEAN-1
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) Parent page type 1 is unacceptable in pageEntered handler of MenuPageBean!
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) (KD34209) callListeners: AHException
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) (KD34209) handleEvent: backing off (pageEntered)
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) setCurrentPagePtr: ptr = 1
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) (KD34209) purgePageStack: purging at pageIx = 1
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - After switch action
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - curtSession not null
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - initialize new page
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) in initializePage...
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) Start getCustomPage, page=oracle.apps.mwa.beans.MenuPageBean at Mon Sep 17 16:16:45 IST 2012
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - newPage
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - initializeArrays
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - check for PageBean
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - updateObject
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - checkRefireEnter
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PM - renderScreen
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - after PM handle
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - while true
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - while true PM.m_drawScreen
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - while true PM.m_upArrow
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - while true PM.m_isNormalText
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - while true PM.m_highlightedList
    [Mon Sep 17 16:16:45 IST 2012] (Thread-15) PH.run - while true PM.m_highlightText
    [Mon Sep 17 16:16:52 IST 2012] (Thread-15) PH: User KD34209 got disconnected...
    [Mon Sep 17 16:16:52 IST 2012] (Thread-15) PH: caught IOException Connection reset
    [Mon Sep 17 16:16:52 IST 2012] (Thread-15) PH: caught IOException
    java.net.SocketException: Connection reset
         at java.net.SocketInputStream.read(SocketInputStream.java:168)
         at java.net.SocketInputStream.read(SocketInputStream.java:182)
         at java.io.FilterInputStream.read(FilterInputStream.java:66)
         at java.io.PushbackInputStream.read(PushbackInputStream.java:122)
         at oracle.apps.mwa.presentation.telnet.ProtocolHandler.readChar(ProtocolHandler.java:1370)
         at oracle.apps.mwa.presentation.telnet.ProtocolHandler.enterHighlight(ProtocolHandler.java:2045)
         at oracle.apps.mwa.presentation.telnet.ProtocolHandler.run(ProtocolHandler.java:753)
    [Mon Sep 17 16:16:52 IST 2012] (Thread-15) PH: session is not null and session is not killed session...calling markSessionDropped()
    [Mon Sep 17 16:16:52 IST 2012] (Thread-15) KD34209 connection has dropped. Session will be saved temporarily.
    [Mon Sep 17 16:16:52 IST 2012] (Thread-15) PH.run - exit
    In ShipPLNPageXX on line number 17 code is:
    super(ses);
    (Inside page constructor ).
    Please provide the solution ASAP.
    Thanks,
    Kopal

    Hi Kristofer,
    When the Employee pressed the Save button and if the status of timecard is Approved/Submitted , a popup should display.
    I have created a page with two buttons (Yes and No) with  warning  "By clicking yes, all previously submitted versions of this timecard will be retracted. The Timecard will need to be resubmitted and reapproved. Are you sure you wish to continue?"..
    If Employee pressed Yes...I need to save the timecard and normal process should follow..
    Here even if I called the PFR of the TimecardListCO(Standard) controller, It's not working.
    Is there a way to create the page dynamically with two buttons ?So that I can write the code in the extended controller itself rather than creating a new page.
    Which method should I follow to implement this?
    Kindly provide your suggestion...
    Thanks,
    Sukanya

  • Urgent MSCA Customization

    Hi
    I am trying to add new business logic on CycleCountPage in MSCA(Whse Mgmt Responsibility).
    I copied some files from the server and de-compile all of them and save the new files with CustomFileName.java
    Then change the classes’ code to meet the new file names and add my new logic in the following files
    • Function CustomCycleCountFunction.java
    • Page CustomCycleCountPage.java, CustomLotSerialPage.java
    • Field CustomItemLOV.java
    • Listener CustomCycleCountFListener.java
    Then I compiled the new classes on the server using javac successfully and generate the new .class files in the same original file’s folders
    And change the .class files attributes to 755.
    Then I added a new function and add it to the menu to run the new function class
    It appears in the menu but it gives me
    Unexpected error o >
    It seems that the application couldn’t read the new function class file
    After that I tried to modify the original .class files
    I decompiled them and add my new code and compile them in the server
    but the page still using the old logic as there is no new code have been added.
    I renamed the folder name to cause error reading the original class files
    /oracle_apps/testcomn/java/oracle/apps/inv/count/server
    to
    /oracle_apps/testcomn/java/oracle/apps/inv/count1/server
    but it still working?!!
    It seems that the telnet server reads from another location
    actually I copied the files to
    /oracle_apps/testcomn/java/oracle/apps/inv/count/server
    /oracle_apps/testcomn/java/oracle/apps/inv/lov/server
    /oracle_apps/testcomn/java/oracle/apps/inv/utilities/server
    as /oracle_apps/testcomn/java is the $JAVA_TOP
    I need to know
    How to force the application to read from the new copied classes.
    Thanks in advance

    Did you have any luck with this? I was wondering if you were grabbing the files from the Forms server or from the database server. We have separate machines for both tiers, and the MWA stuff runs on the Forms server, so you have to modify the Forms server code.
    If you were modifying the code on the database server, it makes sense that your MWA session would not see the changes.
    We built a robust set of custom methods to allow us to extend the standard apps, allowing us to add custom code on top of the existing code without modifying it (stuff like adding new fields, or simulating the user pressing Enter to move through standard fields that we make invisible). We call it the 'magic' and it works very well....until a patch comes along that adds a new field to the screen that we weren't expecting. Ahh - nothing comes for free.

  • OAM customization error

    I wanted to change the font colour of user manager application to red.To get this done i followed the instructions given in the document.the steps have been done in the process are as below.
    2.5.1 Prerequisites to Customizing Styles
    Be sure to complete the following prerequisites before you start to customize a style. This enables you to keep the original Classic Style (\style0) intact for reference and in case you need to return to it as a last resort.
    To prepare to customize styles
    As an Identity Administrator, add your own named style as described in the Oracle Access Manager Identity and Common Administration Guide.
    The original style stays in effect until an Identity Administrator makes your style the new system default.
    As an Identity Administrator, select the new style as the default style so that you can see the effect of any changes you make.
    2.5.2 Customization Facts
    Style Updates and Maintenance: Default wrapper files in \style0 and default global stylesheets in \shared are periodically updated to instantiate improvements through patches and product upgrades.
    The Release Notes notify you when such updates occur so you can propagate the changes to your custom styles. Oracle recommends that you compare the new file with your custom file and propagate any changes to your custom styles. It is risky to overwrite a default style with a customized style that bears the same name.
    Be sure to record the changes you make and the files that are involved so you can more quickly update custom stylesheets when you update default styles.
    Custom Directory: Stylesheet customization should occur only within your custom directory. Customized stylesheets must reside in your custom directory and relative pointers in all files must point to the files in your custom directory, not to files in \shared.
    Registration Files: As discussed in "General Content of Registration Files", a common registration file and each application's registration file contain the names of the stylesheets and schema files needed to present pages for the application. For example, when you look at the User Manager registration file in identity\oblix\apps\userservcenter\userservcenterreg.xml, you can see the application name and the names of the stylesheets the application calls during the completion of various functions.
    Also, given the application and the program name, you can locate the corresponding schema file name in the application's registration file.
    Oracle recommends that only experienced developers using extreme care consider editing a registration file. Registration files are covered in more detail at "Registration Files".
    Pointers: All wrapper files and stylesheets contain pointers as include statements that call another file. Most of these pointers are relative pointers that indicate where within the directory structure the file is without providing an absolute path name.
    For example, when you look at the usc_profile.xsl stylesheet called by User Manager functions, you can see that it contains include statements with relative pointers that call the following files:
    ./basic.xsl
    ./selectorinfo.xsl
    ./usc_searchform.xsl
    ./usc_navbar.xsl
    When you change the location of a file (place a copy of a stylesheet in your custom directory for customization), pointers to this file (whether relative or absolute) must be changed to reflect the new location in every file that calls it. All relative pointers in a stylesheet should point to files in your custom directory.
    In addition, many stylesheets contain relative pointers to object files. If Oracle Access Manager cannot instantiate an object when the page is loaded, unexpected behavior may result. All relative pointers to object files should be absolute pointers, as discussed in "Editing Stylesheets".
    Wrapper Files: Wrapper files include pointers to actual stylesheets in \shared. However, you cannot be assured that a wrapper file is called before the stylesheet because both the common registration file and the application's own registration file call stylesheets according to an internal ordering. For this reason, all wrapper files in your custom directory must be overwritten by a copy of the corresponding default stylesheet from the \shared directory.
    Important:
    Customizing stylesheets is an iterative process. Attempting to copy the entire contents of \shared into your custom directory at one time produce an error.
    Rather than copying all stylesheets at once, you start by investigating registration files to learn which functions (programs) call which stylesheets. You then selectively copy base stylesheets and a function-related stylesheet into your custom directory to overwrite their wrapper files, as discussed in "Copying Stylesheets to Your Custom Directory". You then customize and test the style for that function. When this returns satisfactory results you repeat the process to customize another function.
    2.5.3 Customization Guidelines
    The following guidelines should help ensure a successful customization.
    Retain all original files in the \style0 and \shared directories in pristine condition and store them safely for future use. Also, make a backup copy of your customized style files so that patches won't disrupt your customization.
    Record all changes you make and the files that are affected.
    Customize and test your new styles in a non-production environment before migrating them to your production environment.
    Important:
    Oracle recommends that you do not modify original style files in the \shared or \style0 directories. These may be overwritten by patch updates and product upgrades or you may want to refer to them later.
    When you use only one style, consider breaking the dependence on stylesheets in the \shared directory (again, to prevent patch\release updates to \style0 and \shared from disrupting customizations). This means that no stylesheet in your custom directory should inherit from or reference a stylesheet in \shared or \style0.
    When you use multiple custom styles, consider the pros and cons of sharing customizations between multiple custom styles with implementing individual customizations for each custom style. For example:
    Two styles that share the same stylesheet: When two custom styles (custom_style1 and custom_style2) can share the same stylesheet you may be tempted to customize the stylesheet in the \shared directory despite the risk of having your custom style overwritten by an updated stylesheet in a product patch or upgrade.
    Two individual styles: When two custom styles (custom_style1 and custom_style2) require their individually customized stylesheets you use the standard methodology and overwrite the wrapper files in your custom directory with the corresponding stylesheets in \shared.
    Consider using parameter stylesheet files for a custom style collection, rather than using hard-coded values (tab id's, attribute names, table/link properties, and so on); this is similar to how program code is written using header files.
    2.5.4 Customization Methodology Checklist
    As mentioned earlier, customization is an iterative process and more of an art than a science. This Guide does not attempt to give precise instructions for getting the presentation you want. Instead, this section outlines the recommended approach for a minor change.
    Important:
    Oracle recommends that you focus on stylesheets for one function at a time. Attempting to copy all stylesheets from \shared into your custom style directory results in an error.
    Table 2-28 Customization Methodology Checklist
    Check Action Description
    Add a New Style
    See the Oracle Access Manager Identity and Common Administration Guide for details about adding a style and selecting your new style as the default.
    Choose a Function to Customize
    Decide which function to customize first. Oracle recommends that you customize stylesheets related to one function at a time.
    Copy Selected Stylesheets into Your Custom Directory
    Copy selected stylesheets from \shared to your custom directory to overwrite corresponding wrapper stylesheets:
    Base stylesheets
    Stylesheets included in base stylesheets
    A function-related stylesheet identified in application registration file
    Function-related stylesheets identified in oblixbasereg.xml
    Customize Stylesheets in Your Custom Directory
    Change relative pointers in copied stylesheets to point to files in your custom directory.
    Change relative pointers to objects to absolute pointers.
    Complete other changes to implement the function's customization.
    Record Your Work
    Keep a record of the files you change and the changes you make.
    Copy Your Custom Directory Structure to WebPass
    Build a custom directory structure on WebPass and copy customized styles and images into it.
    Note: On WebPass, stylesheets are used only for client-side processing and are not required for server-side processing.
    Test Your Customized Style
    Test the customized style and make any alterations you need to the stylesheets in your custom directory.
    Record the changes.
    Customize Another Function
    Repeat this process on a function by function basis:
    Choose a function.
    Copy related stylesheets from \shared to your custom directory.
    Customize pointers and styles.
    Record and test your work.
    Propagate the Customized Style
    When you have copied and customized all stylesheets for the application, copy the custom style directory to all Identity Servers and WebPass hosts in your environment.
    2.6 Customizing the Identity System Pages
    This example shows a method for changing the way a page looks, without changing what it does. The change is a simple font color alteration for a specific page in one application. After making the change you must verify that the change is successful. When you finish this functional customization, you must create the same custom style directory structure on WebPass and copy all image files into it so WebPass can display the appropriate images in response to queries. You then test the implementation.
    The following topics demonstrate one sequence in the "Customization Methodology Checklist". You can complete the following procedures to gain first-hand experience:
    Task overview: Customizing Identity System pages includes
    Completing Prerequisites
    Choosing a Function to Customize
    Copying Stylesheets to Your Custom Directory
    Editing Stylesheets
    Copying Images and Styles to WebPass
    Testing Your Customized Style
    Propagating Styles
    See also:
    For details about localizing messages, see "Localizing XSL Files".
    2.6.1 Completing Prerequisites
    A prerequisite to customizing a style is to add a style and select the new style as the default, as described in the Oracle Access Manager Identity and Common Administration Guide. The resulting files and file structure provide the foundation for your customization.
    Suppose you added a new style named Pastel in a directory named Pastel and requested files be copied from Classic Style (in directory \style0).
    To confirm the results of adding a new style
    Add a style and select it as the default, as described in the Oracle Access Manager Identity and Common Administration Guide.
    New Custom Directory: Oracle Access Manager creates a directory that duplicates \style0 for the default language, English. If you have installed a Language Pack for French, Oracle Access Manager also creates a directory that duplicates \style0 in the French language directory.
    Locate your new custom directory.
    For example:
    Identity_install_dir \identity\oblix\lang\en-us\Pastel
    Identity_install_dir \identity\oblix\lang\fr-fr\Pastel
    Wrapper Stylesheets: Your custom directory contains wrapper stylesheets that point to actual stylesheets in another directory. If you selected the Classic Style to copy from, your custom directory duplicates the content of the \style0 directory.
    Open a wrapper stylesheet in your new custom directory, basic.xsl, and review the files that it includes.
    For this example:
    Identity_install_dir\identity\oblix\lang\en-us\Pastel\basic.xsl
    <?xml version="1.0" ?>
    - <!-- Copyright (c) 1996-2005, Oracle Inc. All Rights Reserved.
    -->
    - <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
    <xsl:include href="./style.xsl" />
    <xsl:include href="../msgctlg.xsl" />
    <xsl:include href="../../shared/basic.xsl" />
    </xsl:stylesheet>
    The basic.xsl wrapper stylesheet includes the following three files:
    style.xsl file in your custom directory
    msgctlg.xsl, one directory up from your custom directory (in identity\oblix\lang\en-us)
    basic.xsl in identity\oblix\lang\shared
    Locate and review the content of the basic.xsl stylesheet in \shared.
    For example:
    Identity_install_dir\identity\oblix\lang\shared\basic.xsl
    <?xml version="1.0" ?>
    - <!-- Copyright (c) 1996-2002, Oblix Inc. All Rights Reserved. -->
    - <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
    <xsl:include href="obstringutil.xsl" />
    - <!-- xsl:output indent="no"/ -->
    <xsl:include href="font.xsl" />
    <xsl:include href="title.xsl" />
    The basic.xsl stylesheet in the \shared directory includes additional files (font.xsl, title.xsl, obstringutil.xsl) and provides templates to define attributes and status and control display information. See "basic.xsl" for more information.
    During your customization process, you copy selected stylesheets from the \shared directory into your custom directory. This overwrites wrapper files with corresponding stylesheets you can then edit in your custom directory.
    New Custom XML Document: In addition to the custom directory structure, when you select the new custom style as the default style, Oracle Access Manager creates an XML document (a duplicate of style0.xml) named after the directory you created.
    Locate and open the custom xml document that was created when you added the new style.
    For this example:
    Identity_install_dir\identity\oblix\config\style\Pastel.xml
    <?xml version="1.0" ?>
    - <ParamsCtlg xmlns="http://www.oblix.com" CtlgName="style0">
    - <ValNameList ListName="">
    <NameValPair ParamName="styleReady" Value="TRUE" />
    </ValNameList>
    </ParamsCtlg>
    This new file, stored with style0.xml, provides the status of your custom style and the location of the original style directory from which wrapper files were copied. For example, if your custom style directory is named Pastel and you copied from Classic Style, the Pastel.xml file is created when you select Pastel as the default style.
    You do not need to edit this file. The original style0.xml remains unchanged. Also, there is a .lck version, Pastel.xml.lck, which is a lock file. No other new files are created when you add a new style.
    Updated styles.xml: The styles.xml file is updated to include a new NameValPair that provides both the directory and style names you supplied when creating the style.
    Locate and open the styles.xml file to confirm it was updated with your new style information.
    For example:
    Identity_install_dir\identity\oblix\config\style\styles.xml
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    - <ValNameList xmlns="http://www.oblix.com" ListName="styles.xml">
    <NameValPair ParamName="style0" Value="Classic Style" />
    <NameValPair ParamName="Pastel" Value="Pastel" />
    </ValNameList>
    In this example, both the default Classic Style and new custom Pastel style are identified. You do not need to edit this file.
    After confirming your custom directory structure, new and updated files, you are ready to choose a function and begin your customization.
    2.6.2 Choosing a Function to Customize
    The first step in the customization process is to choose a function to customize. For this example, suppose you want to change the font color to red on a specific page of the User Manager without changing anything else.
    To identify the function and source information
    Log in to the Identity System, as usual.
    Navigate to the desired page.
    For this example, click:
    Identity System Console, User Manager, and then click My Identity
    The page appears, as shown in Figure 2-6.
    Figure 2-6 Customization Example: A User Manager Page Displays Red Text
    The following information on each Identity System application page is useful for customizing styles:
    Application Name: The application name, User Manager, appears on a highlighted tab in the top left area of the screen.
    Each application's \bin directory contains the registration file that you need to identify functions. See "Registration Files".
    Page Name: The page name, in this example it is My Profile, is the first page that you want to customize so you can see text in a red font color.
    Registration File Path: The URL for each page includes a path to the application page, for example, identity\oblix\apps\userservcenter\bin\userservcenter.cgi. You can use this to locate the relevant registration file on the Identity Server.
    Function Name: The URL for each page also includes a segment, program=view in this case, that you can use to locate the relevant stylesheet name for the function in the registration file.
    Record the required information to assist you during the customization.
    For this example:
    Application: User Manager
    Page: User Profile
    Registration File Path: Identity_install_dir\identity\oblix\apps\userservcenter\bin\
    Function: program=view
    2.6.3 Copying Stylesheets to Your Custom Directory
    Once you have identified the function you want to customize, your next task in any customization is to copy relevant stylesheets into your custom directory from the \shared directory. This activity overwrites wrapper files in your custom directory with copies of stylesheets you can customize. This also retains the original stylesheets in \shared as well as the original default wrappers in \style0.
    Locating and copying relevant stylesheets is an iterative process in itself. In the following procedure you must locate and copy:
    Base stylesheets
    Stylesheets included in base stylesheets
    The specific function-related stylesheet identified for the program in the application's registration file, in this case the stylesheet associated with program=view
    Stylesheets included in the function-related stylesheet
    Eventually your custom directory must contain all stylesheets, including those identified in the application's registration file and in oblixbasereg.xml. Even if you do not need to edit a stylesheet, it must be copied to your custom directory.
    Important:
    Copying stylesheets is an iterative process that must be done in a selective manner. Attempting to copy all stylesheets from \shared to you custom directory at one time results in an error.
    To locate and copy relevant stylesheets
    Copy the base stylesheets to your custom style directory from \shared to overwrite the default wrappers with stylesheets you can customize.
    For example:
    Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ basic.xsl, font.xsl, searchform.xsl, navbar.xsl, title.xsl
    Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\
    This retains the original base stylesheets in \shared as well as the original default wrappers in \style0.
    Open each base stylesheet in your custom style directory and locate include statements that point to other stylesheets you must copy, as well as any style information you need to customize.
    For this example, see Table 2-29:
    Table 2-29 Base Stylesheet Pointers and Items to Customize
    Base Stylesheets in Custom Directory Pointers to Related Stylesheets and Items to Customize
    basic.xsl
    Contains implied relative include pointers to other stylesheets you need in your local custom directory:
    <xsl:include href="obstringutil.xsl" />
    <xsl:include href="font.xsl" />
    <xsl:include href="title.xsl" />
    Record the names of additional stylesheets you must copy into your custom directory from \shared. In this case, obstringutil.xsl.
    font.xsl
    Does not contain include pointers to other files.
    Does contain color information you can customize:
    <xsl:variable name="subHeadingColor">#006699...
    <xsl:variable name="contentTitleColor">#000000...
    <xsl:variable name="contentTextColor">#000000...
    searchform.xsl
    Does not contain include pointers to other files.
    Does not contain color information to customize. No changes needed to this stylesheet in your custom directory.
    navbar.xsl
    Does not contain include pointers to other files.
    Does contain color information you may customize later.
    title.xsl
    Does not contain include pointers to other files.
    Does contain color information you may customize later. No changes needed to this stylesheet in your custom directory.
    Copy stylesheets included in base stylesheets to your custom directory from \shared.
    For this example, obstringutil.xsl:
    Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ obstringutil.xsl
    Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\obstringutil.xsl
    Record the stylesheets you have copied from \shared to your custom directory so you can track your work.
    Locate the required registration files.
    For this example, oblixbasereg.xml and userservcenterreg.xml:
    Identity_install_dir\identity\oblix\apps\common\bin\oblixbasereg.xml Identity_install_dir\identity\oblix\apps\userservcenter\bin\ userservcenterreg.xml
    At some point, you typically need stylesheets included in the common registration file oblixbasereg.xml. However, stylesheets included in oblixbasereg.xml are not needed for this example.
    For this example, you must locate only the function-related stylesheet in the userservcenterreg.xml file.
    Open the application's registration file and locate the function-related stylesheet you need.
    For this example, locate ObProgram name="view":
    <?xml version="1.0" ?>
    - <ObProgramRegistry>
    - <ObApplication name="userservcenter">
    - <ObProgram name="front">
    <ObStyleSheet name="usc_profile.xsl" />
    <ObSchema name="usc_front.xsd" />
    </ObProgram>
    - <ObProgram name="commonNavbar">
    <ObStyleSheet name="usc_profile.xsl" />
    <ObSchema name="usc_front.xsd" />
    </ObProgram>
    - <ObProgram name="view">
    <ObStyleSheet name="usc_profile.xsl" />
    <ObButton name="initiateDeactivateUser" />
    - <!-- ObButton name="manageSubscriptions"/ -->
    <ObButton name="userreactivate" />
    <ObButton name="wfTicketDelete" />
    <ObButton name="userModify" />
    <ObSchema name="usc_profile.xsd" />
    </ObProgram>
    You can see in the registration file that the usc_profile.xsl stylesheet is associated with the function you want to customize (ObProgram name="view"). The usc_profile.xsl stylesheet is also associated with a number of other functions.
    Copy the function-related stylesheet, usc_profile.xsl, to your custom style directory from \shared and record the stylesheet name.
    For this example:
    Copy From: Identity_install_dir\identity\oblix\lang\en-us\shared\ usc_profile.xsl
    Copy To: Identity_install_dir\identity\oblix\lang\en-us\Pastel\ usc_profile.xsl
    Open the function-related stylesheet and locate include statements that point to other stylesheets you must copy, record any information you plan to customize.
    For this example, usc_profile.xsl:
    Table 2-30 usc_profile.xsl Pointers and Items to Customize
    usc_profile.xsl in Custom Directory Pointers to Related Stylesheets and Items to Customize
    usc_profile.xsl
    This main stylesheet for the User Manager includes stylesheets that must be copied to your custom directory:
    <xsl:include href="./basic.xsl" />
    <xsl:include href="./selectorinfo.xsl" />
    <xsl:include href="./usc_searchform.xsl" />
    <xsl:include href="./usc_navbar.xsl" />
    Note: selectorinfo.xsl, usc_searchform.xsl and usc_navbar.xsl should be copied.
    Also record pointers to objects that should be customized:
    <object id="cenroll" classid= ...
    codebase="../../common/bin/xenroll.cab" />
    and
    <script src="../../common/bin/installCert.vbx" ...
    Repeat steps to copy relevant stylesheets, then record their names and details you plan to change.
    For this example:
    Copy From:
    Identity_install_dir\identity\oblix\lang\en-us\shared\selectorinfo.xsl
    Identity_install_dir\identity\oblix\lang\en-us\shared\usc_searchform.xsl
    Identity_install_dir\identity\oblix\lang\en-us\shared\usc_navbar.xsl
    Copy To:
    Identity_install_dir\identity\oblix\lang\en-us\Pastel\selectorinfo.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_searchform.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_navbar.xsl
    These stylesheets do not contain include statements, other stylesheet names, nor parameters you need to change.
    You have collected, copied, and recorded relevant stylesheets for this example.
    2.6.4 Editing Stylesheets
    After copying relevant stylesheets, you may need to edit them. As described in Table 2-29 the information that needs to be customized for this example includes:
    Font colors defined in the base stylesheet font.xsl should be changed to red.
    Pointers to objects defined in usc_profile.xsl should change from a relative path to an absolute path.
    Note:
    To help streamline development and testing, consider implementing XSL stylesheet control parameters. See "Caching Considerations".
    To edit stylesheets for a simple font color change
    Open the font.xsl stylesheet in your custom directory in a text editor.
    For example,
    Identity_install_dir\identity\oblix\lang\en-us\Pastel\ font.xsl
    Edit the stylesheet to change all colors from the default color to red (FF0000), then save the change.
    For example,
    Change all Default Font Colors From:
    ... <xsl:variable name="pageHeaderColor">#006699</xsl:variable>
    <xsl:variable name="subHeadingColor">#006699</xsl:variable>
    <xsl:variable name="contentTitleColor">#000000</xsl:variable>
    <xsl:variable name="contentTextColor">#000000</xsl:variable>
    and others ...
    To Red (#FF0000):
    ... <xsl:variable name="pageHeaderColor">#FF0000</xsl:variable>
    <xsl:variable name="subHeadingColor">#FF0000</xsl:variable>
    <xsl:variable name="contentTitleColor">#FF0000</xsl:variable>
    <xsl:variable name="contentTextColor">#FF0000</xsl:variable>
    and others ...
    Record your changes to this file.
    If you restarted the Identity Server now you would not yet see your changes. This is because you have not yet customized the function-related stylesheet that identifies where to apply the changes.
    Edit the basic.xsl stylesheet in your custom directory as follows to add required include statements that were in the original basic.xml (but were lost when you copied over the basic.xsl from the shared folder).
    Locate the line containing the following:
    <xsl:include href="obstringutil.xsl"/>
    Add the following information so that it precedes the line identified in a):
    <xsl:include href="./style.xsl" />
    <xsl:include href="../msgctlg.xsl" />
    Edit the usc_profile.xsl stylesheet in your custom directory to change the relative path to objects, as shown in the following, then save the changes.
    For example:
    Change From a Relative Path:
    - <head>
    ...<object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="../../common/bin/xenroll.cab" />
    ... <script src="../../common/bin/installCert.vbx" language="VBScript" />
    </head>
    Change To an Absolute Path:
    - <head>
    ... <object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="/identity/oblix/apps/common/bin/xenroll.cab" />
    ... <script src="/identity/oblix/apps/common/bin/installCert.vbx" language="VBScript" />
    </head>
    This concludes the specific function-related change for this example.
    Ensure that file system access control for new custom style directories and files is set to match the ownership and permissions of \style0.
    Restart the Identity Server.
    If you log in to the Identity System now and view the My Identity page, you see the red font color. However, the images supplied by WebPass won't appear until they are included in a corresponding custom style directory structure on the WebPass host.
    After doing this i checked user manager application then iam being displayed the following error page.
    style shhet error report form.
    an error has occured while executing the application.
    your browser does not support sending email automatically.
    please send email to <a=" "><\a> with the following information.
    you name
    email adress
    make sure to append the trace back in the mail
    in the log file errors have been given as below
    Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl     
    "Failed to compile XSL file."     XSL file:^../../../lang/en-us/pastel2/usc_profile.xsl     
    Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl     
    "OIS_LOG_PASSED_ERROR"     Error^writer\obhtmlpage.cpp:276: Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl

    Hi Matt,
    I think the page you are being redirected to is servererror.jsp, which is deployed within oam-server.ear, within its own ngsso-web.war application. You could deploy your own version of this. I assume you could also modify the ErrorPage setting in oam-config.xml to define your own page, though I have not tested this. This would be a customisation, so you would be responsible for the system behaviour when doing this.
    Regards,
    Colin

  • Migration of  ADF 10g application to ADF 11g(Portlet Customization Error)

    Hi,
    Currently we are doing a migration of ADF/Webcenter 10g appication to 11g(11.1.1.6) and in the current 10g application portlet is used which contains the file based content and can be customized using a specific role say(admin).
    We have almost done the migration using the Jdeveloper 11.1.1.6 and most of the pages along with the portlet content are coming similar to the 10g look and feel but whenever we want to do portlet customization using the specific role we are getting the below exception. The content is file based system and the details of the versions are as below
    10g Environment:
    OC4J version. Oracle Containers for J2EE 10g (10.1.3.5.0)
    JDK version- java version "1.5.0_06"
    Webcenter and it’s version : Webcenter 10g(10.1.3.5.0)
    ADF version. Oracle ADF 10g
    Jdeveloper 10.1.3.3.0
    11g Environment: Currently I am using Jdeveloper 11.1.1.6 with Integrated weblogic server
    webcenter extension used: oracle.webcenter.framework_bundle/oracle.webcenter.customization_bundle
    Error which I am getting during portlet customization:
    [2013-02-20T14:47:42.162+05:30] [DefaultServer] [ERROR] [] [oracle.portlet.binding] [tid: [ACTIVE].ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: portaladmin] [ecid: 39e706a46ad531be:31f43ddc:13cf6ad5231:-8000-0000000000000386,0] [APP:TEST_DEV#V2.0] An error has occured for Portlet Binding portlet3.[[
    java.lang.NullPointerException
    at oracle.adfinternal.model.portlet.binding.PortletModelImpl.getRequireIframe(PortletModelImpl.java:907)
    at oracle.adfinternal.model.portlet.binding.ActivityPortletModelWrapper.getRequireIframe(ActivityPortletModelWrapper.java:71)
    at oracle.adf.model.portlet.binding.PortletBinding.prepareRenderPhase(PortletBinding.java:455)
    at oracle.adf.model.portlet.binding.PortletBinding._refresh(PortletBinding.java:377)
    at oracle.adf.model.portlet.binding.PortletBinding.refresh(PortletBinding.java:969)
    at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3273)
    at oracle.adf.model.binding.DCBindingContainer.refresh(DCBindingContainer.java:2876)
    at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.prepareRender(PageLifecycleImpl.java:561)
    at oracle.adf.controller.faces.lifecycle.FacesPageLifecycle.prepareRender(FacesPageLifecycle.java:82)
    at oracle.adf.controller.v2.lifecycle.Lifecycle$9.execute(Lifecycle.java:224)
    at oracle.adfinternal.controller.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:197)
    at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.access$1000(ADFPhaseListener.java:23)
    at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$5.before(ADFPhaseListener.java:402)
    at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.beforePhase(ADFPhaseListener.java:64)
    at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.beforePhase(ADFLifecyclePhaseListener.java:44)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:352)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:222)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.portlet.client.adapter.adf.ADFPortletFilter.doFilter(ADFPortletFilter.java:32)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.webcenter.framework.events.dispatcher.EventDispatcherFilter.doFilter(EventDispatcherFilter.java:44)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.wcps.client.PersonalizationFilter.doFilter(PersonalizationFilter.java:75)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.webcenter.content.integration.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:168)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.webcenter.lifecycle.filter.LifecycleLockFilter.doFilter(LifecycleLockFilter.java:151)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Any hellp or suggestion will be helpful for me to resolve this issue.
    Thanks in Advance
    Chetan

    Hi,
    given its a WebCenter question, you want to post it to the Webcenter forum: WebCenter Portal
    Frank

  • Customization error

    Hi,
    My requirement is to customize standard Supplier/Sites page.I wanna set some fileds readonly based on some condition.For that i have extended standard VendorVO and SitesVO and added to attributes
    VendorVO-> xxSupplierVO
    Attributes Added
    RenderSupplier_str(Included in Query which calls a function and return 'Y' or 'N' based on my requirement)
    IsRenderSupplier( contains Boolean based on RenderSupplier_str)
    Similarly in SitesVO also i have added 2 fileds.
    In JDeveloper it is working properly.But when i migrated to instance it is not working properly.I have done the substitution and also created personalization on one of the item in my requirement list.I am getting following error
    oracle.apps.fnd.framework.OAException: oracle.jbo.AttributeLoadException: JBO-27022: Failed to load value at index 146 with java object of type java.lang.String due to java.sql.SQLException.
    *     at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:896)*
    *     at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1169)*
    *     at oracle.apps.fnd.framework.webui.OAPageErrorHandler.processErrors(OAPageErrorHandler.java:1435)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2559)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1894)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:538)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:426)*
    *     at OA.jspService(_OA.java:212)*
    *     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)*
    *     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)*
    *     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)*
    *     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
    *     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)*
    *     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)*
    *     at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)*
    *     at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)*
    *     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)*
    *     at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395)*
    *     at OA.jspService(_OA.java:221)*
    *     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)*
    *     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)*
    *     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)*
    *     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
    *     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)*
    *     at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)*
    *     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)*
    *     at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)*
    *     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)*
    *     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)*
    *     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)*
    *     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)*
    *     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)*
    *     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)*
    *     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)*
    *     at java.lang.Thread.run(Thread.java:619)*
    *## Detail 0 ##*
    java.sql.SQLException: Invalid column index
    *     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)*
    *     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)*
    *     at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java:816)*
    *     at oracle.jbo.server.OracleSQLBuilderImpl.doLoadFromResultSet(OracleSQLBuilderImpl.java:1198)*
    *     at oracle.jbo.server.AttributeDefImpl.loadFromResultSet(AttributeDefImpl.java:1633)*
    *     at oracle.jbo.server.ViewRowImpl.populate(ViewRowImpl.java:2221)*
    *     at oracle.jbo.server.ViewDefImpl.createInstanceFromResultSet(ViewDefImpl.java:1066)*
    *     at oracle.jbo.server.ViewObjectImpl.createRowFromResultSet(ViewObjectImpl.java:3014)*
    *     at oracle.jbo.server.ViewObjectImpl.createInstanceFromResultSet(ViewObjectImpl.java:2907)*
    *     at oracle.jbo.server.QueryCollection.populateRow(QueryCollection.java:2272)*
    *     at oracle.jbo.server.QueryCollection.fetch(QueryCollection.java:2130)*
    *     at oracle.jbo.server.QueryCollection.get(QueryCollection.java:1504)*
    *     at oracle.jbo.server.ViewRowSetImpl.getRow(ViewRowSetImpl.java:3697)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.doFetch(ViewRowSetIteratorImpl.java:2818)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2674)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2634)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.getRowCountInRange(ViewRowSetIteratorImpl.java:699)*
    *     at oracle.jbo.server.ViewRowSetImpl.getRowCountInRange(ViewRowSetImpl.java:3195)*
    *     at oracle.jbo.server.ViewObjectImpl.getRowCountInRange(ViewObjectImpl.java:7027)*
    *     at oracle.apps.fnd.framework.server.OAViewObjectImpl.getRowCountInRange(OAViewObjectImpl.java:1980)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanBaseTableHelper.adjustViewRange(OAWebBeanBaseTableHelper.java:226)*
    *     at oracle.apps.fnd.framework.webui.OATableHelper.prepareNavigatorProperties(OATableHelper.java:1629)*
    *     at oracle.apps.fnd.framework.webui.OATableHelper.prepareForRendering(OATableHelper.java:495)*
    *     at oracle.apps.fnd.framework.webui.beans.table.OATableBean.prepareForRendering(OATableBean.java:1220)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanTableHelper.processRequestAfterController(OAWebBeanTableHelper.java:200)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:654)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanTableHelper.processRequest(OAWebBeanTableHelper.java:2141)*
    *     at oracle.apps.fnd.framework.webui.beans.table.OATableBean.processRequest(OATableBean.java:1035)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:350)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAHeaderBean.processRequest(OAHeaderBean.java:391)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.OASubTabLayoutHelper.processRequest(OASubTabLayoutHelper.java:434)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OASubTabLayoutBean.processRequest(OASubTabLayoutBean.java:465)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAHeaderBean.processRequest(OAHeaderBean.java:391)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:350)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1166)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2513)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1894)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:538)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:426)*
    *     at OA.jspService(_OA.java:212)*
    *     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)*
    *     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)*
    *     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)*
    *     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
    *     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)*
    *     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)*
    *     at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)*
    *     at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)*
    *     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)*
    *     at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395)*
    *     at OA.jspService(_OA.java:221)*
    *     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)*
    *     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)*
    *     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)*
    *     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
    *     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)*
    *     at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)*
    *     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)*
    *     at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)*
    *     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)*
    *     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)*
    *     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)*
    *     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)*
    *     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)*
    *     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)*
    *     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)*
    *     at java.lang.Thread.run(Thread.java:619)*
    java.sql.SQLException: Invalid column index
    *     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)*
    *     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)*
    *     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)*
    *     at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java:816)*
    *     at oracle.jbo.server.OracleSQLBuilderImpl.doLoadFromResultSet(OracleSQLBuilderImpl.java:1198)*
    *     at oracle.jbo.server.AttributeDefImpl.loadFromResultSet(AttributeDefImpl.java:1633)*
    *     at oracle.jbo.server.ViewRowImpl.populate(ViewRowImpl.java:2221)*
    *     at oracle.jbo.server.ViewDefImpl.createInstanceFromResultSet(ViewDefImpl.java:1066)*
    *     at oracle.jbo.server.ViewObjectImpl.createRowFromResultSet(ViewObjectImpl.java:3014)*
    *     at oracle.jbo.server.ViewObjectImpl.createInstanceFromResultSet(ViewObjectImpl.java:2907)*
    *     at oracle.jbo.server.QueryCollection.populateRow(QueryCollection.java:2272)*
    *     at oracle.jbo.server.QueryCollection.fetch(QueryCollection.java:2130)*
    *     at oracle.jbo.server.QueryCollection.get(QueryCollection.java:1504)*
    *     at oracle.jbo.server.ViewRowSetImpl.getRow(ViewRowSetImpl.java:3697)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.doFetch(ViewRowSetIteratorImpl.java:2818)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2674)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2634)*
    *     at oracle.jbo.server.ViewRowSetIteratorImpl.getRowCountInRange(ViewRowSetIteratorImpl.java:699)*
    *     at oracle.jbo.server.ViewRowSetImpl.getRowCountInRange(ViewRowSetImpl.java:3195)*
    *     at oracle.jbo.server.ViewObjectImpl.getRowCountInRange(ViewObjectImpl.java:7027)*
    *     at oracle.apps.fnd.framework.server.OAViewObjectImpl.getRowCountInRange(OAViewObjectImpl.java:1980)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanBaseTableHelper.adjustViewRange(OAWebBeanBaseTableHelper.java:226)*
    *     at oracle.apps.fnd.framework.webui.OATableHelper.prepareNavigatorProperties(OATableHelper.java:1629)*
    *     at oracle.apps.fnd.framework.webui.OATableHelper.prepareForRendering(OATableHelper.java:495)*
    *     at oracle.apps.fnd.framework.webui.beans.table.OATableBean.prepareForRendering(OATableBean.java:1220)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanTableHelper.processRequestAfterController(OAWebBeanTableHelper.java:200)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:654)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanTableHelper.processRequest(OAWebBeanTableHelper.java:2141)*
    *     at oracle.apps.fnd.framework.webui.beans.table.OATableBean.processRequest(OATableBean.java:1035)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:350)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAHeaderBean.processRequest(OAHeaderBean.java:391)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.OASubTabLayoutHelper.processRequest(OASubTabLayoutHelper.java:434)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OASubTabLayoutBean.processRequest(OASubTabLayoutBean.java:465)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAHeaderBean.processRequest(OAHeaderBean.java:391)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:350)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1166)*
    *     at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:964)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:931)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:655)*
    *     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:251)*
    *     at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2513)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1894)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:538)*
    *     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:426)*
    *     at OA.jspService(_OA.java:212)*
    *     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)*
    *     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)*
    *     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)*
    *     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
    *     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)*
    *     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)*
    *     at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)*
    *     at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)*
    *     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)*
    *     at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395)*
    *     at OA.jspService(_OA.java:221)*
    *     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)*
    *     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)*
    *     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)*
    *     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)*
    *     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)*
    *     at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)*
    *     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)*
    *     at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)*
    *     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)*
    *     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)*
    *     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)*
    *     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)*
    *     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)*
    *     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)*
    *     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)*
    *     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)*
    *     at java.lang.Thread.run(Thread.java:619)*
    Please advice me to get rid of this error
    Regards,
    Manoj

    Anyone please help.Its urgent
    --Manoj                                                                                                                                                                                                                       

  • Customization error during document reversal

    Hi,
    I am getting the following error:
    "Local Currency of cons unit C300 is not maintained"
    Does anyone know where in SPRO , i have to customize?
    Thanks

    It is CX1O(alphabet O not number 0) or in IMG, follow the path
    Implementation Guide for R/3 Customizing (IMG)
    -->Enterprise Controlling
       -->Consolidation
          -->Master Data
             -->Organizational Units
                -->Consolidation Units
                   -->Maintain Consolidation Units Individually
                      -->Change consolidation unit
    Srinivas

  • Oracle Composer Layout Customizable Error!

    I´ve been trying to develop a custom webcenter application using oracle composer, but everytime I have a Layout Customizable in my page, I keep getting the following error message in my server:
    <MDSRestrictionPolicy><_updateMDSRef> An error has occurred while finding the page for the component with client ID pt1:layoutCustomizable1.
    I have tried everything to avoid this message, but everytime I navigate between pages, it shows in the server log. I have tried using templates, and not using templates at all. I have also tried changing the ID. I´m using a menu model to navigate between pages, showned in the following article:
    http://www.oracle.com/technetwork/developer-tools/jdev/ccset43-all-090938.html
    The problem with this error is that after a few minutes navigating between the pages, the navigation flow just seems to stop working and I cant go from one page to the other anymore. Anyone has been through this before?
    I´m using Jdev 11g 11.1.1.3 and Webcenter 11.1.1.3

    Yup, I had tried setting the "Clean MDS after each run" before, but still got the same message. I have tried with both integrated and standalone WL.
    I just found out that if I set the "ShowIcon" and "ShowLayoutChanger" properties of the Layout Customizable to false, I dont get that message anymore..
    Now I only see the message when I navigate between pages with the "edit mode" on. Is there a way to disable a component (like the command navigation item button inside the navigation pane) when the edit mode is triggered? Thanks!

  • How to customize error page

    Hi,
    Reports 10g.
    I use a validation trigger for a parameter. When it returns FALSE, I have an error page with REP-546: Invalid parameter input.
    Is it possible to customize this page ? Change the text for example ?
    Thank you

    Hi,
    Customization of error messages is not supported.
    Navneet.

Maybe you are looking for

  • Upload saved emails from Thunderbird to Verizon Message Center?

    I have used T-Bird for Verizon email for a long time.  Now, for sync reasons with my Verizon phone, I would like to switch to Verizon Message Center.  Can I upload my saved emails to VMC?  How about contacts and calendar?  (There are instructions for

  • Xml.getBytes("UTF-8")

    Hi I have seen xml.getBytes("UTF-8"). What is the use of this and Where can i get the other methods like getBytes(). e.g: xml.someMethod(). Please help. Edited by: Monadear on Oct 18, 2007 11:37 AM

  • After last maverick update macbook pro can't be shut down anymore - only by using the power button

    Hello! I hope that someone can help: after the last Maverick update I can't shut down the computer anymore - or restart. I need to use the power button. Furthermore several apps don't close when they are supposed to be closed - I always have to check

  • WLS 7: "Bean is already undeployed" error

    Hi all, Been beating againt WLS 7.0 some more. Originally, we had our application running in Tomcat and using WLS purely for EJBs. Now, we've been trying to get the WAR to work within WLS, and made some layout changes in order to accomodate WLS. But

  • Launch programs from file.jsp ?

    i am working about a web application in jsp and i must submit an input, for example pasted by the user in the html form,as an input for others programs which are not written in java but in c or perl. have you ever done something like that ? are there