Mandatory fields in a LOV

I have a view in which I've added attributes from an entity to make a LOV. These attributes are mandatory in said entity. Foreign key in the view (and in an underlying entity) is not mandatory however (it can be null).
When I drop this LOV column onto a page as an InputText with ListOfValues, resulting form field is required (and it will show an error if I leave it empty and try to submit the form). That is not what I expect. The entity referenced from a view is not updatable, the underlying entity is.
How can I have an optional field with a LOV, not making referenced entity columns non-mandatory?

Hi,
Try after remove required attribute in your LOV
required="#{bindings.YourField.hints.mandatory}"

Similar Messages

  • Mandatory fields on the same page with dependent LOVs

    Hi,
    I am working on an ADF-BC application using JDeveloper 10.1.3.4
    I have an ADF Creation form with dependent LOVs and while implementing dependent LOVs we set the autoSubmit property of the selectOneChoiceListBox as true.
    If I have some mandatory fields on the same page then because of the autoSubmit property set as true whenever I select a value in the list the page gets submitted and the mandatory fields give an error that the values are required therefore I had to remove the mandatory fields.
    I tried using f:subview but even that dint serve the purpose because what I want is something like partialSubmit so that my mandatory fields do no give an error when I select a value in the list.
    Can somebody help me on this, how to have a dependent list and mandatory fields on the same page.
    P.S: It is very crucial for my application
    Thanks,
    Raksha

    Hello,
    This bug has been around since 10.1.3, its even still present in Trinidad and now in 11.
    One of the ways to avoid is to make your fields use:
    showRequired="true"instead of
    required="true"I have not found a decent way to avoid this in general.
    My idea was that this shiould be possible with a phaselistener and determine if this is a partial page event instead of a normal submit, but this didnt work.
    -Anton

  • Form Layout LOV on mandatory field

    Hi,
    I have an LOV on a mandatory field in a form layout. When I am entering a new record and click on the LOV icon the LOV page displays but the calling page gives an error of "Value Required". I have noticed that if I manually change the Immediate property of the field to "false" then I do not get the error.
    This error does not occur in table layout.
    Thanks,
    Gavin

    Gavin,
    Do you have multiple LOV's on the page and/or dependent items?
    Is the Value Required message related to the LOV item on which you invoke the LOV window, or is it another item?
    Steven Davelaar,
    JHeadstart Team.

  • Combo LOV firing mandatory field validation

    Hello,
    I am using Jdev 11.1.1.6.
    My VO is entity based. I have 3 fields in this VO as F1, F2, F3
    All 3 fields are mandatory.
    F1 has model based Combo Lov implemented. List Attribute lookupId from LOV is returned to F1 and List Attribute lookupDesc to F2.
    F2 is mandatory and editable. Idea is that default text is returned by lov and then user can update the description.
    Scenario 1: <does not work>
    At runtime, in create mode, when I try to select a value for this combo lov, it fires mandatory field validation for F2 (only for F2 and not F3) and does not show list of values. I can not make it to show list until enter some data in F2.
    <af:inputComboboxListOfValues> has autoSubmit="true" and immediate="false" and F2 has partialTriggers="id of F1"
    Scenario 2: <works>
    For test purpose, if I make F2 read-only then it works perfectly but F2 is editable and mandatory as well.
    <af:inputComboboxListOfValues> has autoSubmit="true" and immediate="false" and F2 has partialTriggers="id of F1"
    Scenario 3: <works>
    On other pages, I have implemented combo lov where the lov is implemented on reference field and returning the value to only Id column and not to any other field. This scenario works perfectly even with mandatory fields present on page.
    <af:inputComboboxListOfValues> has autoSubmit="true" and immediate="false".
    Thanks,
    Jai

    Try to remove partialTrigger from F2 (has partialTriggers="id of F1"),
    and attach valueChangeListener on F1, in which you can partially refresh F2 (by code)
    Of course, make F1 autoSubmit.
    Scenario 1: <does not work>
    At runtime, in create mode, when I try to select a value for this combo lov, it fires mandatory field validation for F2 (only for F2 and not F3) and does not show list of values. I can not make it to show list until enter some data in F2.
    <af:inputComboboxListOfValues> has autoSubmit="true" and immediate="false" and F2 has partialTriggers="id of F1"

  • Mandatory Fields Color

    Hi All,
    I have a custom form with 2 fields.
    FieldA- LOV(XX,YY)
    FieldB becomes required when YY is chosen.
    I am able to make fieldB as required, but I am not able to get proper color(yellow).
    to achieve this I created a visual group and assigned that to fieldB in runtime using below code:
    SET_ITEM_INSTANCE_PROPERTY('FieldB',CURRENT_RECORD,VISUAL_ATTRIBUTE,'DATA_REQUIRED1')
    The background color of DATA_REQUIRED1 is r100g100b55. But still I am not able to find the exact yellow that is used for other required field in APPS, my yellow(r100g100b55) is little bit brighter.
    Please let me know how to get the visual_attribute of mandatory fields, and assign them in FIELDB.
    Note: the entry in registry.dat is:
    app.ui.requiredFieldVABGColor=255,0,0(not sure what it means)
    Regards,
    Debanjan

    Hi...
    Use the following code in your List (When list changed trigger)
    IF :list_value = 'XX' THEN
    SET_ITEM_INSTANCE_PROPERTY('B',CURRENT_RECORD,VISUAL_ATTRIBUTE,'YOUR VISUAL ATTRIBUTE');
    ELSIF :list_value = 'YY' THEN
    SET_ITEM_INSTANCE_PROPERTY('B',CURRENT_RECORD,VISUAL_ATTRIBUTE,'YOUR DEFAULT VISUAL ATTRIBUTE');
    END IF;
    And if you have problem with making a field required or not then...
    You have to set the property in both  'B' field WHEN VALIDATE ITEM and your list's WHEN LIST CHANGED trigger...
    Hope this will help you...
    Regards,
    Soofi

  • When we change the non-mandatory field in the form, it doesn't get updated

    Hi... I have one question here..
    If I have non-mandatory fields in a custom form, and when I query the form and change the value in the non-mandatory field and click on save, then it doesn't save. It says 'No Changes to Save'. But, it's not the same for non-mandatory fields.
    Can you please suggest me?
    -vrdida

    VRdida,
    If I understand correctly, you have a non-Required item in your form that has an LOV assigned. While this item is Required=No, it works correctly. When you change the Required property of the item to 'Yes' then it fails. When this occurs, do you get an error message? Are you able to select a value from the LOV?
    It sounds like the Required=Yes property might be preventing you f rom opening the LOV. Try setting the Module property: Defer Required Enforcement = Yes. This is the typical setting in an EBS form. This is what allows you to navigate out of a Required field if the value is NULL, but will give you a Required message when you attempt to save the record if the value is still NULL.
    Hope this helps,
    Craig B-)
    If someone's response is helpful or correct, please mark it accordingly.
    Edited by: CraigB on Apr 6, 2011 11:43 AM

  • What are the mandatory fields while creation of material master in differen

    what are the mandatory fields while creation of material master in different views?

    Hi Gopi,
      This is purely depends on the function configuration, which would be done MM consultants.  Kindly check with them.
    thanks & regards
    Kishore Kumar Maram

  • Dynamic mandatory field error message is not getting displayed in webui

    Hi,
    In Appointment if the importance is HIGH i made Location as mandatory.For this i enhanced BT126H_APPT/ApptDetails. In the get_p_location() method of BTACTIVITYYH i have written the code.
    Now the problem is Error message for this dynamic mandatory field is not getting displayed in webui.
    I debugged in DO_FINISH_INPUT error message is getting generated but it is not getting displayed in ui.
    Can anybody tell where the problem is?
    Thanks,
    Hari.

    Hi Hari,
    Really sorry do not know how to convert this nug file to text
    How ever quick solution for your problem would be just keep your validation in 'DO_VALIDATE_INPUT' method of the view controller.
    Means even if the User clicks on SAVE , Since it fails here , it would not allow you to go further.
    Thanks,
    Rajesh P

  • Mandatory fields while using Group chart of accounts

    Hi,
    Which are the mandatory fields while maintaining GL accounts in FS00 if i am using Group chart of accounts.
    And how attached these group chart of accounts gl to the operational chart of account GL.
    raj

    Hi,
    the assignment from operational chart of accounts to group chart of accounts is done in OB13. Follow the steps in Customizing IMG FIn. Acc. (new) / Consolidation preparation (new) / General specifications / G/L and FS Charts of accounts...
    Best regards, Christian

  • What are all the mandatory fields of the BAPI_PO_GETDETAIL?

    Hi friends,
    I am new to XI. I am using the "BAPI_PO_GETDETAIL1" in my scenario to get details of a particular Purchase Order. Can you tell me the mandatory fields of this BAPI?
    Where should i look to identify the mandatory fields of a BAPI?
    Thanks.
    Senthil Nathan.

    Hi you can see this in SE37 under the Import Tab. Here you see that the only mandatory input field is PURCHASEORDER. So if you provide the purchaseorder number you get alle the details for that.
    Kind regards
    Mikkel

  • What are the Mandatory fields????

    Hi.... Experts...
       Please spend your valueble time for me.... I can get back to you with 10 points....
    Here I got a requirement to create contract with VA41 transaction...
    But I am in confusion with feilds which should be must record...
    Please guide me on mandatory fields of VA41 transaction....
    Thanks,
    Naveen.I

    Hi,
    When ever you want to know the required fields for any transaction just try to run the Transaction In SHDB in forgroud mode with a recording name.
    You will easily get to know the required fields to be entered for a given transaction.
    Sometimes when we run this VA41, eventhough some fields are not mandatory we dont pass them but we willnt b able to create the document eventhough some fields are not mandatory to fill> To have the clear idea abt the manadotry fields try to run in SHDB.
    for this VA41, ther mandatory fields are-
    contract type (VBAK-AUART)
    Sales Area is a combintaiotn of SAles Org, SAles divnsion, Distirbution channel hende all 3 are required to be filled.
    1st screen-
    Sales Area(VBAK-VKORG)
    Division(VBAK-SPART)
    D.Channel(VBAK-VTWEG),
    2nd screen-
    Customer code(kunnr),
    Contract validity,
    material code(matnr),
    quantity
    plant(werks).
    Best Wishes,
    Chandralekha
    Edited by: Craig Cmehil on Jun 30, 2008 11:24 AM

  • What are the Mandatory Fields in Transaction ME51

    Hello Seniors,
    I have a requirement about purchase order creation. In this process, I am using the BAPI named   " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2"  and I see an error which reads "" All mandatory fields are missing"". I have even created a PO  in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
    Your reply is most awaited and rewarded.
    Thanks and Regards,
    MARKIV

    hi ,
    Functionality
    Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
    Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
    Functionality in Detail
    Authorization
    The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
    M_BEST_BSA (document type in PO)
    M_BEST_EKG (purchasing group in PO)
    M_BEST_EKO (purchasing organization in PO)
    M_BEST_WRK (plant in PO)
    Controlling adoption of field values via X bar
    For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
    Transfer
    Header data
    The header data of the Enjoy purchase order is transferred in the table PoHeader.
    Item data
    The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
    Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
    Services and limits
    Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
    Conditions
    Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
    Vendor and delivery address
    The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
    Note
    In this method, the following restrictions apply with regard to addresses:
    Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
    When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
    Partner roles
    The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
    Import/export data
    Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
    Texts
    Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
    Version Management
    You can make use of the Version Management facility via the table AllVersions.
    Return
    The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
    Return messages
    Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
    Example
    Example of population of BAPI interface in the Function Builder
    Parameter: POHEADER
    COMP_CODE = 1000
    DOC_TYPE = NB
    ITEM_INTVL = 00001
    VENDOR = 0000001000
    PMNTTRMS = 0001
    PURCH_ORG = 1000
    PUR_GROUP = 001
    CURRENCY = EUR
    Parameter: POHEADERX
    COMP_CODE = X
    DOC_TYPE = X
    ITEM_INTVL = X
    VENDOR = X
    PMNTTRMS = X
    PURCH_ORG = X
    PUR_GROUP = X
    Parameter: POITEM
    PO_ITEM = 00001
    MATERIAL = 100-100
    PLANT = 1000
    STGE_LOC = 0001
    QUANTITY = 15.000
    TAX_CODE = V0
    ITEM_CAT = 0
    ACCTASSCAT = K
    Parameter: POITEMX
    PO_ITEM = 00001
    MATERIAL = X
    PLANT = X
    STGE_LOC = X
    QUANTITY = X
    TAX_CODE = X
    ITEM_CAT = X
    ACCTASSCAT = X
    Parameter: POSCHEDULE
    PO_ITEM = 00001
    SCHED_LINE = 0001
    DELIVERY_DATE = 02.12.2002
    QUANTITY = 6.000
    PO_ITEM = 00001
    SCHED_LINE = 0002
    DELIVERY_DATE = 03.12.2002
    QUANTITY = 5.000
    PO_ITEM = 00001
    SCHED_LINE = 0003
    DELIVERY_DATE = 04.12.2002
    QUANTITY = 4.000
    Parameter: POSCHEDULEX
    PO_ITEM = 00001
    SCHED_LINE = 0001
    PO_ITEMX = X
    SCHED_LINEX = X
    DELIVERY_DATE = X
    QUANTITY = X
    PO_ITEM = 00001
    SCHED_LINE = 0002
    PO_ITEMX = X
    SCHED_LINEX = X
    DELIVERY_DATE = X
    QUANTITY = X
    PO_ITEM = 00001
    SCHED_LINE = 0003
    PO_ITEMX = X
    SCHED_LINEX = X
    DELIVERY_DATE = X
    QUANTITY = X
    Parameter: POACCOUNT
    PO_ITEM = 00001
    SERIAL_NO = 01
    QUANTITY = 15.000
    GL_ACCOUNT = 0000400000
    COSTCENTER = 0000001000
    CO_AREA = 1000
    Parameter: POACCOUNTX
    PO_ITEM = 00001
    SERIAL_NO = 01
    QUANTITY = X
    GL_ACCOUNT = X
    COSTCENTER = X
    CO_AREA = X
    Parameter: POCOND
    ITM_NUMBER = 000001
    COND_ST_NO = 001
    COND_TYPE = PB00
    COND_VALUE = 79.900000000
    CURRENCY = EUR
    CURRENCY_ISO = EUR
    COND_UNIT = KG
    COND_P_UNT = 1
    CHANGE_ID = U
    Parameter: POCONDX
    ITM_NUMBER =  000001
    COND_ST_NO =  000
    ITM_NUMBERX =  X
    COND_TYPE =  X
    COND_VALUE =  X
    CURRENCY =  X
    CHANGE_ID =  X
    Parameter: POPARTNER
    PARTNERDESC =  OA
    LANGU =  EN
    BUSPARTNO =  0000001100
    PARTNERDESC =  GS
    LANGU =  EN
    BUSPARTNO =  0000001200
    PARTNERDESC =  PI
    LANGU =  EN
    BUSPARTNO =  0000001000
    Help in the Case of Problems
    1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
    2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
    3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
    Customer Enhancements
    The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
    EXIT_SAPL2012_001 (at start of BAPI)
    EXIT_SAPL2012_003 (at end of BAPI)
    The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
    EXIT_SAPL2012_002 (at start of BAPI)
    EXIT_SAPL2012_004 (at end of BAPI)
    These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
    There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
    Further information
    1. Note 197958 contains up-to-date information on the purchase order BAPIs.
    2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
    3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
    4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
    5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
    regards
    reena

  • Mandatory Field in ALV Grid

    Hello,
    i've a editbale alv grid.
    Is it possible to set a field/colum as mandatory field?
    Best regards,
    TomSd

    Hi,
    Have a look at the report BCALV_EDIT_03.
    In this report the program logic is such that if the user enters an incorrect value an error is displayed.
    Instead you can check if the field of your ALV filelds are null and validate them accordingly.
    Regards,
    Sandeep

  • Mandatory field validation on Page links.

    We have created a Portal application where we included different applications as taskflows. We have also created a tabbed interface which helps us to communicate from one task flow to another taskflow. When we are in one page of taskflow and try to move to another page of different taskflow using tabbed interface we receive mandatory field validation error which prevents us to move to any other page until we fill all the mandatory fields. We need to move to different page of taskflow by using the tabbed interface even without filling all the necessary mandatory fields. Can anyone help us to resolve this issue as this is very important for our project.

    <b>Layout</b>
    <%@page language="abap" %>
    <%@extension name="htmlb" prefix="htmlb" %>
    <htmlb:content design="design2003" >
      <htmlb:page title="Check Pernr " >
        <htmlb:form>
          <htmlb:textView text   = "Personnel No."
                          design = "EMPHASIZED" />
          <htmlb:inputField id    = "pernr"
                            value = "<%= lv_pernr %>" />
    <%
    if lv_no_pernr = 'X'.
    %>
    <script language="Javascript">
    alert ("Personnel no. is not Valid")
    </script>
    <%endif.%>
       </htmlb:form>
      </htmlb:page>
    </htmlb:content>
    <b>ONINPUTPROCESSING</b>
    DATA: l_pernr TYPE persno.
      DATA: data TYPE REF TO cl_htmlb_inputfield.
      data ?= cl_htmlb_manager=>get_data( request = runtime->server->request
                                             name     = 'inputField'
                                             id       = 'pernr' ).
      IF data IS NOT INITIAL.
        l_pernr = data->value.
      ENDIF.
    CLEAR lv_no_pernr.
    SELECT SINGLE pernr FROM pa0000 INTO l_pernr WHERE pernr EQ lv_pernr.
    IF sy-subrc NE 0.
      lv_no_pernr = 'X'.
    ENDIF.
    <b>PAGE ATTRIBUTES</b>
    lv_no_pernr     TYPE     FLAG
    lv_pernr     TYPE     PERSNO
    hope this helps.
    A

  • How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice

    Hi,
    Kindly solve, How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice.
    Regards,
    Rajeev.

    Follow this step..
    1. In SQL Server, go to the SAP B1 Database you're using. 
    2. then on the Object Explorer , go to Database Folder, explode the SAP DB->Programmability->Stored Procedures->SBO_SP_TransactionNotification * the only Stored Procedure that is allowed to be edited. Just right click and modify
    3.  Try to paste this -> and click F5
    If
    @object_type ='13' and @transaction_type in ('A','U')
    Begin
    If EXISTS
    select DocEntry from ONIV
    Where DocEntry = @list_of_cols_val_tab_del
    and  SlpCode<>'-1'
    Begin
    set @error_message = 'Please select the Sales Employee'
    set @error = 1
    END
    END
    Regards
    Kennedy

Maybe you are looking for