Making Password Field Non-Mandatory in OIM

Hi,
I would like to make Password and Confirm Password Fields in OIM Create User Form as Non-Mandatory (removing the asterick and also modifying the background Java code).Is it possible?.
Thanks.

HI,
You can also edit the FormMetaData.xml and make the password optional.
Here is the link to how you can do it.
http://download.oracle.com/docs/cd/E10391_01/doc.910/e10362/fieldconf.htm#sthref112
Manasa

Similar Messages

  • Making "Room" field Non Mandatory - PM Notifications

    Dear PM Experts,
    Can any one tell me where to make field Room under Tab Loctions of PM Notificaitons (in brakedown notifications) non mandatory. Because in my client this field is mandatory. Although I have a place to make this fields optional for PM Orders, I don't find the same field in the place where we can make fields optional for notificaitons (under T-Code OQM1).
    Please Help.
    Cheers
    Deepal

    Hi,
    As the field is part of location/account assignment data the same customizing would be effective for both orders and notifications. This group of fields can be customized with transaction OIAZ.
    If you have different behaviour between notifications and orders then the customizing is based on influencing fields - Possibly order type and notification type.
    To check this - Run OIAZ and select the 'influences' icon.
    -Paul

  • To make the "req.delivery date" field non-mandatory in VA01 Transaction

    Hi All,
    I want to make "req. delivery date"(RV45A-KETDAT) field non mandatory in VA01 transaction.
    I have already checked on screen 4440 .This field is not mentioned as required field.
    Please help me to find where can i make this field non-mandatory.
    Thanks and Regards,
    Dipali.

    Hi,
    this is a required field, as far as the standard SAP code goes: everytime this field is touched the following function is executed in programme FV45EF0V_VBEP-EDATU_EINGEBEN:
        call function 'PERIOD_AND_DATE_CONVERT_INPUT'
          exporting
            external_date     = rv45a-etdat
            external_period   = rv45a-prgbz
          importing
            internal_date     = vbep-edatu
            internal_period   = vbep-prgrs
            ev_date_in_past   = lv_date_in_past
            ev_period_in_past = lv_period_in_past
          exceptions
            no_data           = 1
            period_invalid    = 2
            date_invalid      = 3.
        case sy-subrc.
          when 1.
            set cursor field 'RV45A-PRGBZ' line sy-stepl.
    * Bitte Datum eingeben
            message e394.
    The only way to avoid this is create an implicit enhancement at the beginning of this form, copy the exisitng code in there, delete the message after WHEN 1. and put RETURN at the end of the enhancement. But this would be HIGHLY UNRECOMMENDED, because I am positive you cause a lot of misery later on in the process: this field is mandatory for a reason!
    Roy

  • Make project profile field non mandatory in CJ20n Transaction

    Hi All,
    I want to make project profile field non mandatory in my CJ20n transaction. I tried through OPUA, OPUK, OPUC but of no use. The field over there is just an input field. I need to make it non mandatory either through configuration or through code. Please suggest.
    Regards,
    Jayant

    Hi,
    this is a required field, as far as the standard SAP code goes: everytime this field is touched the following function is executed in programme FV45EF0V_VBEP-EDATU_EINGEBEN:
        call function 'PERIOD_AND_DATE_CONVERT_INPUT'
          exporting
            external_date     = rv45a-etdat
            external_period   = rv45a-prgbz
          importing
            internal_date     = vbep-edatu
            internal_period   = vbep-prgrs
            ev_date_in_past   = lv_date_in_past
            ev_period_in_past = lv_period_in_past
          exceptions
            no_data           = 1
            period_invalid    = 2
            date_invalid      = 3.
        case sy-subrc.
          when 1.
            set cursor field 'RV45A-PRGBZ' line sy-stepl.
    * Bitte Datum eingeben
            message e394.
    The only way to avoid this is create an implicit enhancement at the beginning of this form, copy the exisitng code in there, delete the message after WHEN 1. and put RETURN at the end of the enhancement. But this would be HIGHLY UNRECOMMENDED, because I am positive you cause a lot of misery later on in the process: this field is mandatory for a reason!
    Roy

  • Making the "incoterms" field non-mandatory

    For the time being, "incoterms" field in XD01 (Create customer) for the domestic customers is mandatory. On the other hand, I want to make it non-mandatory. How can I do it?
    Thanx in advance.

    In OBD2 u  can do this
    Select the account grp and enter.
    Double click sale data
    Double click Billing
    make incoterms optional
    Message was edited by:
            sam masker

  • How to Set field non mandatory in PA40

    Is there a way to make non-mandatory field RP50G-EINDA in PA40?
    Many Thanks
    Alfonso

    Hi
    Go to t588m table make that field as required field
    Warm Regards

  • Unable to make field non-mandatory using SM30/T588M

    Hello Gurus -
    My client would like the field LAND1 (country key) to be optional in infotype 21 (Family Members/Dependants).  Standard delivery appears to be that this field is mandatory if any of the address fields are populated.  We have tried to make this non-mandatory by setting it as Optional or Hiding it in T588M.  No matter how we set this field up, it still behaves as mandatory if any address field is populated.  We are certain we are at the correct Mod Pool/Variable Key combination as we have successfully changed other field requirements for this infotype.
    Does anyone have any input as to why we are encountering this problem and/or suggestions as to how to get around it?
    Thanks!
    Zaj

    Hi,
    Follow IMG path -> Personnel Management -> Personnel Administration -> Customizing User Interfaces-> Change Screen Modifications
    Try using the below screen for modification for IT 0021:
    Module Pool          MP002100
    Standard screen      2001
    Alternative screen   2001
    Feature         P0021
    In feature see that you maintain for which MOLGA Country Grouping and subtyes you want to use.
    I hope this will help you.
    Thanks,
    Padmaja.

  • Making Screen fields Non editable in Migo

    Hi TO ALL,
    In MIGO T-code , aganist oubound delivery under Batch Tab i want to make fields Non editable.
    I am unable to find suitable exit for this,can any body help me regarding this.
    Thanks

    Hi,
    Use Transaction variant (Tcode : SHD0) to make fields display only.
    Regards,
    Ashok.

  • Making screen fields non-editable in standard SAP screen

    Hi All,
    I have a reuirement. In transaction code CAA2 I have to make the field 'Incoming payment method' (EZAWE) as read only/non-editable. This field is available in table FKKVKP. We can make this field as read only by performing some configuration setting. But this field needs to be disabled based on some validations.
    For example EZAWE field should appear in changable mode when user has the role 'ZDJ: SUPER_USER' assigned to him. If the user does not hold this role the EZAWE fields needs to be disabled.
    One more thing here I don't have to use screen variants for this.
    Thanks,
    Venkat

    >
    Vijay Babu Dudla wrote:
    > Try with Transaction Variants , if there is no exit available to modify the screen dynamically, check the Transaction code SCDO.
    >
    > Search SDN with Transaction Variants
    Hi,
    I think it is SHD0. correct me if am wrong
    Rhea.
    Edited by: rhea on Oct 17, 2008 12:39 PM

  • How to make a process form field non updatable in OIM 11G PS1

    Hello all - I have a filed in process form, which once filled should be not be updated. Could you please let me know how to achieve this?
    Should we create a process task, where in we can say 'updating this filed is not possible' ?
    I tried this. But OIM shows the filed with updated value but 'Resource History' shows status as Rejected.
    Please help. Thanks
    Manju

    The only way i would see this possible would be through an event handler if you can make it work for this form. On your pre-update, you would need to make sure to always return the original value back to the form so even if changed, it would change it back.
    -Kevin

  • How to make a field non-Editable in Web UI

    Hello Experts,
    I am new to Web UI CRM 7.2. Could anyone pls guide me in making a field non-editable on Web UI.I have the field in one of the custom assignment block. Could you pls guide me with some sample code how to achieve this ?
    Thanks in advance.

    Hi experts,
    For the component 'ICCMP_EMP_SRCH' there is a view 'BUPAEMPSEARCH' , which has 2 context nodes 'CUSTOMER' AND 'SEARCHEMPLOYEE' , i need to add the field 'NICKNAME' which is part of the 'CUSTOMER' context node on the search screen. Currrently all the fields on the screen screen are from the 'SEARCHEMPLOYEE' context node. when i did the configuration , the 'NICKNAME' field is greyed out . I have already generated the Getter ,Setter , GET_I, GET_M methods for the 'NICKNAME' field and the context node and controller class and context class are all active .
    on debugging the GET_I method, i see that rv_disabled = 'TRUE' and the current = collection_wrapper->get_current( ) is returning empty value .
    for this rv_disabled to be set false , the code below is not triggered since there is no value in current.
    IF current->is_property_readonly(
    'NICKNAME' ) = abap_false. "#EC NOTEXT
    rv_disabled = 'FALSE'.
    ENDIF.
    when i check for other search fields of context node 'SEARCHEMPLOYEE' , all the fields are set to rv_disabled = 'FALSE'.
    can anyone suggest how to approch this. iam i missing any binding between context nodes or any activations ?
    The field properties are set as Input field and the display checkbox is not checked.

  • Make non-mandatory field in Logical Database 'SDF'  mandatory.

    Hi all,
    I want to make a non-mandatory field 'Chart of Accounts'  in Logical Database 'SDF'  mandatory in my Z program.
    Please let me know how this can be done?
    I tried defining the select-option in my zprogram but it gives error saying the parameter has already been defined in LDB.
    Regards,
    Atrinandan
    Edited by: raj on Aug 3, 2009 7:46 PM

    Hi,
      You can try like below:
    at selection-screen output.
    loop at screen.
    if screen-name = 'NAME OF THE PARAMETER'.
    screen-required = 1.
    modify screen.
    endif.
    endloop.
    Regards,
    Himanshu

  • Conditionally Mandatory or non-Mandatory field in Isupplier banking Detail Form.

    Hi OA Experts
    I need to make a field mandatory or Non-Mandatory based on Lov item in page "/oracle/apps/pos/sbd/webui/SuppRegActPG", Can I do this by using VO extension , if yes, Kindly guide me as I am new to OAF.

    You need to do VO extension first and add transient attribute in the same VO. Set SPEl to the required field using Controller code.For this You need to do controller extension.
    ++++++++++++++++++++++++++++++++++++++++++++++++
    In PR,
    Set SPEL to the field by initializing the field according to its Style.(OAMessagetextinputBean or OAMessageStyledTextBean etc...)
    +++++++++++++++++++++++++++++++++++++++++++++++++
    Then in PFR use Lov event as below.
    if (pageContext.isLovEvent())
              String lovInputSourceId = pageContext.getLovInputSourceId();
              if ("myLovInput".equals(lovInputSourceId)) // "myLovInput" is the item id of LOV, replace with your LOV on page
                   rendVO.getCurrentRow().setAttribute("xxRenderApprove",Boolean.FALSE);//here handle the SPEL
    I hope this will be enough for your requirement.

  • How to make Resource Forms fields non editable (OIM)

    Hi all!
    I would like to know if there's any way to make some resource fileds non editable.
    I have one resource which is getting 3 fileds from the oim user profile. When i change the oim user profile, these values are updated on the resource form associated.
    But i want to prevent the situation in which those fields are directly updated on the resouce form.
    I now i can propagate those changes back to oim profile but it will be much appropiate for what we want if we just could prevent anyone from changing those values on the resource form.
    Is it possible to make those fields non editable? How?
    OIM version is 9.1.0.1.
    Thanks in advance.

    Hi, thanks.
    Finally i found this: http://kr.forums.oracle.com/forums/thread.jspa?threadID=591683
    and after setting the fields to required=false, it worked without any errors ("The Resource has not been configured properly" because of the prepopulate adapters)
    Bye

  • Making screen field mandatory

    hi can any one help in making the field email as a mandatory in su01 t-code and kindly help with process where to go and what are the steps do i take to make the field mandatory

    Go to SHD0,
    give the transaction as SU01 and give the name of transaction variant for example 'USR1'. click create. Since your requirement is only for email give some dummy name and click on create. In the next screen give some dummy name and enter and continue till you reach the screen with this title "Screen values 0900 Program SAPLSZA5" . In this screen for the field 'Email' check the box under 'required' column. now click exit&save. give some short text in the next screen and save it under appropriate package, Transport requests.
    Note : you can default your transaction variant as the standard variant. (SHD0 - standard variants tab-> Activate/Deactivate as standard variant)
    Now go to se93 and click on create , give transaction code as for example 'SU01N' (this will be your new transaction for creating user with email as mandatory field) and choose start object as 'Transaction with variant'
    In the resultant screen, give the transaction code as SU01 and transaction variant as 'USR1' (the one we created earlier), check on all gui support box's accordingly, and save it under appropriate package and Transport request.
    From here on you can use SU01N as the transaction for creating users with email as a mandatory field.

Maybe you are looking for