Mandatory field is completely coloured

Hi Friends,
We have upgraded from 5.2 to 7.0. We have an Account Plan and it has various Mandatory fields marked with a star. Now the problem is for one of the mandatory field apart from the star we have a red colour covered for that particular field. Now we need to remove that red colour to that field. Kindly give your thoughts on the same.

Hi Jaya Pal,
       The red borders will stay as long as the mandatory fields are empty. This behaviour is hardcoded as part of the input field rendering. If you absolutely must eliminate this behaviour, you can try modifying a CSS file. Open BSP application thtmlb_styles in SE80. Expand Mimes->sap_skins->default and edit thtmlb_stand.css. Look for a section like this and change it as you see fit.
/* <thtmlb:inputfield> tag Mandatory field                            */
.th-ip-sp-md .th-if,
input.th-ip-sp-md {
    border-color:      red !important;
Regards,
Arun Prakash

Similar Messages

Mandatory Fields in iView created from SHD0 (sceen variant)

I am experiencing an issue with the Portal display of an (IAC) iView. The iView displays PZ05 and a transaction variant was setup to handle Emergency contact info. I created a screen variant for the second screen of this transaction (screen 0200) in which I made 7 of the fields mandatory in the variant. When this is tested on the R/3 side the mandatory fields are displayed the way they are supposed to be (with the check mark in the box, denoting it as a required field) however when they are displayed in the iView on the Portal the mandatory fields are completely filled up with the "check mark in the box". In other words the "Name" field is 40 character... and there are 52 "check marks in the box" characters filling up the field. The iView works great but this looks ugly. Any suggestions on what I should do to rectify the situation?
We are running Portal 6.0 SP15 with a stand alone ITS on a 4.6c backend and the Business Package is 50.4.

Hi Balaji,
When you create Vendors properly in ECC it should not give such an error. You have to maintain basic data, Accounting data and purchasing data. Rest all are optional.
For replicating vendors from R/3 to SRM you should have a Vendor root org / group in SRM. BBPGETVD is used to replicate vendors to SRM by mentioning the logical system and Vendor Group ID.
Hope this makes you clear. Please explain the error clearly for further help.
Award points for helpful answers.
Rgds,
Teja

Mandatory field of " version completion "indicator

Hello gurus.
I want to mandatory field of " version completion indicator to tic , when any change in purchase order in me22n, me29n.
i am waiting your reply.
regard,
riten patel

Hello Sravanthi683 .
i want to make mandatory to tic in "vesion competion" indicator field when ever change of quantity or price.
i am waiting your reply.
regard,
riten patel

Credit memo and mandatory fields in Sales order

Dear all,
I have 2 problems, hoping these are not too basic questions I'm asking here.
1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
Many thanks!
Best regards.

Hi There,
> 1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
> The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
>
> Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
This is the standard SAP behavior. Simple thing, All the values are negative so when it will post to FI
It will be like
Dr Customer Invoice amount ( which is negative ) so end result is +ve. ( as Debit is -)
I hope its understandable.
For example:
While creation of simple invoice say of 1000 $
Entries were Dr Customer 1000 $
                     Cr Revenue    1000$
Now After Credit memo
                    Dr Customer    -1000 $
                     Cr Revenue    -1000 $
Which will nullify each other.
> 2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
The best way is to include these two fields in the Sales order incomplete procedure in OVA2. Put Error/warning as required by you.
Thanks,
Raja

Mandatory fields for delivery, GI BAPIs

Hi Folks,
scenario, i have an STO number for which i have to create an outbound delivery(like its done in VL10B). now that i have a delivery number, next i have to change the quantity of this delivery and post goods issue. after GI i need to post a GR. data is comming in from a non sap system.
bapis are -
BAPI_DELIVERYPROCESSING_EXEC
to create an outbound delivery
BAPI_OUTB_DELIVERY_CHANGE
to change the outbound delivery and then post GI
BAPI_GOODSMVT_CREATE
to creat GR
can anyone who has worked with the following bapis tell me what the mandatory fields are in each bapi. i am unable to post them. i would appreciate your help and thanks in advance.

Sample Code for BAPI_GOODSMVT_CREATE
Populate header data
Posting date
    x_goodsmvt_hdr-pstng_date = <deldate>.
Document date
    x_goodsmvt_hdr-doc_date   = <doc_date>.
User Name
    x_goodsmvt_hdr-pr_uname   = <ernam>.
User Name
    x_goodsmvt_hdr-ref_doc_no = <PO/Delivery No).
Bill of lading
      x_goodsmvt_hdr-bill_of_lading =<BOL>.
Populate item data
Purchase order number
    i_goodsmvt_item-po_number = ebeln.
Line item number
    i_goodsmvt_item-po_item   = ebelp.
Plant
    i_goodsmvt_item-plant     = werks.
Movement type
    i_goodsmvt_item-move_type =movtype.
Movement indicator
    i_goodsmvt_item-mvt_ind   = mvt_ind.
GR quantity
    if p_movtype = c_101.
      i_goodsmvt_item-entry_qnt = menge.
   else.
     i_goodsmvt_item-entry_qnt = menge * -1.
    endif.
GR UOM
    i_goodsmvt_item-entry_uom = meins.
Storage location
    i_goodsmvt_item-stge_loc = lgort.
Production date
    i_goodsmvt_item-prod_date = doc_date.
Delivery completion indicator
    i_goodsmvt_item-no_more_gr = c_x.
Movement Reason
    if p_movtype = c_122.
      i_goodsmvt_item-move_reas = c_12.
    endif.
endloop.
For each PO create a GR document
if not i_goodsmvt_item[] is initial.
    call function 'TRANSACTION_BEGIN'
         importing
              transaction_id = l_trans_id.
    call function 'BAPI_GOODSMVT_CREATE'
         exporting
              goodsmvt_header = x_goodsmvt_hdr
              goodsmvt_code    = x_mvt_code
         importing
              materialdocument = l_mat_doc
              matdocumentyear = l_mat_doc_year
         tables
              goodsmvt_item    = i_goodsmvt_item
              return           = i_bapireturn.
endif.

Mandatory fields to create PO in SRM

Hi all,
I am working on data migration. Can you please tell me what are the mandatory fields to create PO in SRM. Please give the list of field names.
Regards,
Balaji.S

Hi Balaji,
Other than the mandatory fields mentioned above, you need to do some mandatory setting in SRM which would ensure that a Purchase order is created if the details in the shopping cart are complete.
Go to transaction SPRO -> Supplier Relationship Management ->SRM Server -> Cross Application Basic Settings -> Define Objects in the backend system.
Here you would need to mention the Purchasing group , the product category id , source system ( backend system). In the option External procurement - select the option Purchase order if the item data complete.
This would ensure that provided your shopping cart data is complete, a Purchase order would be generated.
Hope this helps.
Kindly award if the answer was helpful.
Regards,
Rajesh

Mandatory fields error messages in HCM forms and processes

Hi,
This may sound to be a very simple problem but I am unable to get to the root of the issue and thus need an expert advise here.
I have created several forms in the system out of which one is an OM form using SAP_PD service for create position. There are few mandatory fields in the form scenario such as
TITLE
ABBREVIATION
EMPLOYEE GROUP
EMPLOYEE SUBGROUP
As expected, system issues an error message if these field are left out blank but the error message is generic for all the fields and is missing the field name.
Actual Error Message
Complete the required entry field ""
Expected Error Message
Complete the required entry field "Employee Group"
Complete the required entry field "Employee Subgroup"
However, there are couple of fields in the form scenario which issues a correct error message
Complete the required entry field "Object abbreviator" (P1000-SHORT)
I am unable to identify the difference between the couple of fields that issues a correct message and rest 20 other fields which doesn't.
Regards,
Murtuza Kharodawala

No, if I enter all the mandatory fields on the form then there is no problem. It allows me to move ahead and submit the form successfully.
As recommended by Siddharth, I tried debugging the message class and what I observed was it passes the complete_fieldname value as Personnel Subarea (I1008_BTRTL) and system expects it to be I1008-BTRTL.
SAP as a fallback tries to read description from the table T5ASRFSCNFLDT but it has a_form_scenario as blank and complete_fieldname has a concatenated value "Personnel Subarea (I1008_BTRTL)" instead of "I1008-BTRTL".
Not sure what am I missing which causes it to have this wrong error message.
Regards,
MK

Mandatory fields!

Create Material Master Data (MMD) for Required Material ( MM01)
In the first Screen I am Entering the mandatory fields for creating a material
     Material
     Industry Sector
     Material type
After filling these details   , click on SELECT VIEWS
For MM point of view select , Basic Data 1, Purchasing , Accounting 1
Basic Data 1 :
Give the material description -
Basic Unit of Measure -
Material Group----
Division -
General Item Category group----
After entering it therethese values will be copied or take the same values in the next screen also But there would be some of the fields again mandatory like in Purchasing..
Purchasing :
Purchasing Value key -
Reminder 1, 2, 3 , Standard Del time Varience
Shipping Instructions----
Under delivery tolerance , Over delivery tolerance , Minimum delivery Quantity in %
GR Processing time -
Accounting 1 :
Valuation Class -
Price Control- If it is S( standard price give the Standard Price value )
--If it is V( Moving average price , give moving average price from which date)
After completion of these details save the data
Material has been created
Now before creating a material there are screen in SD point of view
So what are the remaining fields that are mandatory in SD point of view
Regards
AK

Hi AK
in material master the Screen and Field selection depend upon the Client requirement anyway
i would like to add more screen and field in continuation of thread
Screen-General plant data 1/2
Field - Profit Center
as far as material creation cycle is concern
Run TCode MM01
after that Select Material Type
and Industry Type
after that click OK you will get another screen of Department view
select as per your requirement
1-Basic data 1/2
2-purchasing View
3-accounting
4-General plant data
5- sales data1/2/3
by putting enter you will get another Screen in this screen you will have to define the plant storage location Sales organization etc.........
Thanks

Help! Mandatory Field Coloring Stopped Working

I'm using LiveCycle 9 and ES2. I have built several forms with mandatory fields and these fields always show up with a red border in "preview" and in Adobe. Suddenly, this feature stopped working. Non of my forms are showing up with red borders on the mandatory fields.
Only things I have done recently is to publish one form to a repository (SharePoint). Could this have changed the viewing features on all my forms?
Thank you in advance for your help.

Hi,
The highlight colour can be changed in Acrobat/Reader preferences:
I would check there first, as any changes will be implemented in all forms.
Good luck,
Niall
Assure Dynamics
edit: glad you have it working

Default Back Button ( F3 ) with mandatory fields ( module pool program )

Guys,
I'm editing another persons dialog program and as mentioned in the subject line, there are mandatory fields. WIthout them being filled, I cannot use the back button to exit the program as it prompts me to first fill the mandatory fields.
How can I get past this?
I did a /h for debug mode and pressed Back but it did not even show the debugger.
Regards,
Kevin

<b>Use AT exit-command.</b>
MODULE mod [ AT {EXIT-COMMAND|CURSOR-SELECTION} ]
[ ON {CHAIN-INPUT|CHAIN-REQUEST} ]
[ SWITCH switch ].
Extras:
1. ... AT EXIT-COMMAND
Effect
The statement MODULE of the dynpro flow logic calls the dialog module mod of the ABAP program. You can use MODULE either as a keyword or as an addition of statement FIELD. When using it as an addition, the call of the dialog module depends on conditions for the screen fields.
As a keyword, the statement calls the dialog module mod of the respective ABAP program. At the event PAI, you can use the additions AT and ON to specify conditions for the call of the dialog module.
At the event PBO, you can call any dialog module defined in the ABAP program with the addition OUTPUT. At the events PAI, POH and POV, you can call any dialog module defined with the addition INPUT or without any addition. If the dialog module mod does not exist in the ABAP program, an untreatable exception is triggered. After processing a dialog module in the ABAP program, processing of the dynpro flow logic is resumed after the position of the call, unless the screen processing is completed within the dialog module.
You can use MODULE as a keyword only at the events PBO and PAI. At the events POH and POV, you can use MODULE only as an addition to the FIELD statement.
Note
Do not mix up the MODULE statement of the dynpro flow logic with the identically called statement MODULE for defining dialog modules in the ABAP program.
Addition 1
... AT EXIT-COMMAND
Effect
Addition AT EXIT-COMMAND at the event PAI causes module mod to be called exactly if:
The function used to trigger event PAI has function type "E"
Into the input field of the standard toolbar, the user entered a character string starting with "E" and confirmed it using ENTER.
The dialog module is called before the automatic input checks defined in the system or in the ABAP Dictionary and independent of its position in the event block. The only screen field transported to the ABAP program is the OK field. If the function that triggered the PAI event does not fulfill any of the above prerequisites, the MODULE statement is not executed.
If several MODULE statements have the AT EXIT COMMAND addition, only the first one is executed. If no MODULE statement has the addition AT EXIT COMMAND, a normal PAI processing is executed: The predefined input checks are executed and then the PAI event block is processed sequentially. Provided the screen processing is not terminated in the dialog module mod, after the return from the dialog module, the complete PAI processing is executed. You must not use the addition AT EXIT COMMAND in connection with the statement FIELD.
Note
The function type of a function is determined in the Screen Painter or Menu Painter. Usually those functions of the user interface are defined with function type "E" that are assigned to the icons Back, Exit and Cancel in the standard toolbar of the GUI status. Therefore, the called dialog module should terminate the screen processing and allow security checks, if required.

How to hide Mandatory field

Dear Gurus,
I need to hide location field from the master agreement screen.This field is mandatory field.
I went to page customisation and made this field as hidden.But still it is not working.
Please give your inputs in completing this.
Thanks and Advance,
sai.

Venkat,
If you are using 5.1 the HIDDEN Yes functionality works on the Location field. The proper container for the Master Agreement is contracts.contract.ui.buyside.default and for Agreements it is contracts.agreement.ui.buyside.default.
Keep in mind that this field is required and passed into this field from the user object so you will have to maintain data on the user object.
But on a 5.1 system the page customization works.
Regards,
James

PDF Form Mandatory Field Validation Issue in Workspace

If we open a PDF Form with mandatory fields (e.g. Mortgage-Prebuilt sample PDF form) in Workspace and then click the Workspace Complete button without completing the mandatory fields, there will be mandatory validation check which will highlight all the mandatory fields and display the mandatory fields error message dialog box.
However, if we click the Workspace Complete button again afterwards, the mandatory fields error message dialog box will not be displayed. The dialog box will be displayed only if our mouse is moved to any active/enabled fields/buttons in PDF form.
Does anyone encounter this strange issue before?
Kindly advice what should we do to solve this issue.

Hi Patrick,
As this is the modal popup, there is a close button .
Now in the ACTIONS tab try to create an action for CLOSE.
Once you get the window reference,
wd_comp_controller->gref_w_popup_split type ref to IF_WD_WIINDOW.
SET_ON_CLOSE_ACTION
SET_CLOSE_BUTTON
CALL METHOD wd_comp_controller->gref_w_popup_split->set_close_button
        EXPORTING
          close_button = abap_true.
      CALL METHOD wd_comp_controller->gref_w_popup_split->set_on_close_action
        EXPORTING
          view        = wd_comp_controller->gref_v_controller_split
          action_name = wd_assist->gc_close_split.
   "Action Name
In the CLOSE action -
IF wd_comp_controller->gref_w_popup_split IS NOT INITIAL.
      CALL METHOD wd_comp_controller->gref_msg_manager->clear_messages
        EXPORTING
          including_permanent_msg = abap_false
          only_permanent_msg      = abap_false.
      CALL METHOD wd_comp_controller->gref_w_popup_split->set_close_in_any_case
        EXPORTING
          close_in_any_case = abap_true.
      CALL METHOD wd_comp_controller->gref_w_popup_split->close.
    ENDIF.                      "   if wd_comp_controller->GREF_W_POPUP is not initial.
Regards,
Lekha.

Mandatory dropdown in red colour

Hi all, I need to put a dropdown in a red marked colour if the user don't select anything on it.
I have try these method:
a)   wd_this->message_manager->report_attribute_error_message(
      message_text = text
      element = wd_context_element
      attribute_name = attribute ).
b)     lo_view_controller = wd_this->wd_get_api( ).
    cl_wd_dynamic_tool=>check_mandatory_attr_on_view(
    EXPORTING
    view_controller = lo_view_controller
    IMPORTING
    messages = msg_tab ).
But the dropdown in red is never been marked.
Am I forgetting something please?
Help please.

Just thought to update that I am using a DropDownByIndex for this coding:
Suppose I have a context node by name NODE_IDX & have 2 attributes under this KEY & VALUE. I have associated a supply function POPULATE_NODE with my context node to fill it with values as how shown below:
METHOD populate_node .
* data declaration
DATA lt_node_idx TYPE wd_this->elements_node_idx.
DATA ls_node_idx LIKE LINE OF lt_node_idx.
DATA lv_str TYPE string.
*** If I ommit writing 3 lines below then the system will by default have the 1st value of my
*** dropdown as selected & so would assume that the user has already selected 1 value
*** Try running the component with and without these 3 lines & check the difference
ls_node_idx-key = ''.
ls_node_idx-value = ''.
APPEND ls_node_idx TO lt_node_idx.
DO 10 TIMES.
    lv_str = sy-index.
    CONCATENATE 'TEXT'
                lv_str INTO lv_str SEPARATED BY space.
    ls_node_idx-key = sy-index.
    ls_node_idx-value = lv_str.
    APPEND ls_node_idx TO lt_node_idx.
    CLEAR ls_node_idx.
ENDDO.
* bind all the elements
node->bind_table( new_items            = lt_node_idx
                    set_initial_elements = abap_true ).
ENDMETHOD.
I have bound the "texts" property of my DropDown to the attribute "Value" & I have changed the "state" property to "Required".
I also put the below coding within my WDDOAFTERACTION method to trigger error messages for any mandatory fields which the user hasn't filled out.
METHOD wddoafteraction .
DATA: lt_msg TYPE cl_wd_dynamic_tool=>t_check_result_message_tab,
        lo_view_controller TYPE REF TO if_wd_view_controller.
DATA lo_message_manager    TYPE REF TO if_wd_message_manager.
lo_view_controller ?= wd_this->wd_get_api( ).
lo_message_manager = lo_view_controller->get_message_manager( ).
lo_view_controller = wd_this->wd_get_api( ).
cl_wd_dynamic_tool=>check_mandatory_attr_on_view(
    EXPORTING
      view_controller = lo_view_controller
      display_messages = abap_true
    IMPORTING
      messages = lt_msg ).
ENDMETHOD.
Regards,
Uday
Edited by: Uday Gubbala on Jun 9, 2009 11:39 AM

How to validate incoming messages with mandatory field coming as null/empty

Hi,
I want to validate the incoming messages received by the file adpater.
1. Need to check that all the mandatory fields(minoccurs=1) has values, else it should return fault. But what happening now is even though the mandatory fields are empty/null, file is being read by the file adapter and not getting faulted.
2. I have tried using the Validate Activity/Assign Activity but this is a business fault and not sytem fault, hence no faults are auto generated.
3. We are presently using the if/switch activity and putting the conditions manually in order to validate the mandatory fields and hence it is throwing the business faults explicitly.
4. But if there is 200 fields mandatory out of 500 fields schema, then we need to hardocde manually all 200 fields. Please advise me if this is possible in any dynamic way.
Thanks
Edited by: 902781 on 15.mar.2012 07:33

Dear vijay,
This is my xsd::
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org"
targetNamespace="http://www.example.org"
elementFormDefault="qualified">
<xsd:element name="exampleElement">
<xsd:annotation>
<xsd:documentation>
A sample element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
*<xsd:element name="element1" type="xsd:string" minOccurs="0"*
nillable="false"/>
*<xsd:element name="element2" type="xsd:int" minOccurs="0"*
nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
I tried the above xsd as well as
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org"
targetNamespace="http://www.example.org"
elementFormDefault="qualified">
<xsd:element name="exampleElement">
<xsd:annotation>
<xsd:documentation>
A sample element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
*<xsd:element name="element1" type="xsd:string" minOccurs="1"*
nillable="false"/>
*<xsd:element name="element2" type="xsd:int" minOccurs="1"*
nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
But instance is getting completed even though the mandatory string field(element 1) is empty/null like:
<element1></element1>
What I feel is, string will accept all the values whether it is int, date, long and in the same way it is accepting null character.
Please let me know if you have any solutions to overcome this.
Thanks again.

How can you ensure all mandatory fields are filled, before pressing the submit button?

Hi all,
I've got a complex form with many different pages (17 so far) and I'm using visible/hidden to change the layout so only 1 page appears at a time.
What I want to do is have a better check for what mandatory fields have not been filled out in my form. The submit buttons checks that all of the mandatory fields have been completed, but if that's 1 field on page 1, searching through my entire document would cause the users to lose the will to live!
I am after either returning more meaningful information to the user when a submit fails, or being able to run the mandatory check field every time the page changes. I already dynamically set most of the mandatory fields according to what is/isn't visible so adapting my form wouldn't take long but I have no idea how to get it to check if all the fields have been filled in.
Many thanks,
Tom

Right, I have pretty much all of my validations working now... and here's the word you're waiting for... but, I am having a problem with fields that are already visible when the rest of the layout changes.
Basically, one of the options above the field with the problem is being changed, which makes the layout above that field change. This is triggering the validate event.
This wouldn't stop anyone using my form, but it is an annoyance.
Anyone able to help?
Many thanks,
Tom

Mandatory field is completely coloured

Similar Messages

Maybe you are looking for