Optional/mandatory fields highlighted

hi
in a form, i want to higlight which field is mandatory and which field is optional,
it is possible?

Hello,
Look at my [blog post|http://roelhartman.blogspot.com/2008/12/apex-how-to-emphasis-required-fields.html].
Greetings,
Roel
http://roelhartman.blogspot.com/
http://www.bloggingaboutoracle.org/
http://www.logica.com/
You can award this reply to your question by marking it as either Helpful or Correct ;-)

Similar Messages

Select-option mandatory field

Hi,
I have a select option on the selection screen which i have made mandatory.
I want to enter the values directly through multiple selection and not on the single field, but when i click on the multiple selection option, it is giving me error to fil the mandatory field first before going to the multiple selction.
Regards,
Sonika

Dont make it mandatory..
U can do like this.
Start-of-selection.
if (Name of selection option) is initial.
message s(102) (Here give msg like: it is mandatory to fill this field).
leave list-processing.
endif.
Regards,
Nishant

Mandatory Fields of an Infotype

Hi all,
I am trying to retrieve the mandatory fields for specific infotypes.Can anyone suggest a code for this???
Just Analyze this scenario....
When we hire one employee using PA40,some screens of various infotypes will be active which contains some mandatory fileds...
For this particular screen ,there will be one Module Pool,Screen number and variable key and some mandatory fileds.This will be stored in T588M table.
In T588M table lot of entries are there with same module pool name and screen number.But screen number and variable key combination will be unique.
i want to know these values for all infotypes.
In system->status we get only module pool and screen number..but not variable key.Also its very difficult to see for each infotype like this..
so how to retieve the following fields REPNA(Module Pool),DYNNR(Screen Number) VARKY(Variable Key) from T588M table of a particular infotype....??????
also i need to know how to get the mandatory fields from T588M table which is encoded as '+ + - -'(in DBILD field)
Thanks in Advance
Merlin.

Hi,
first to identify VARKEY for table T588M you have to evaluate the feature which is named in field ZYKLS of that row with empty varkey and default screen.
Teh return value of the feature depends on individual empl. values in P0001.
Include RPUMKC00 in your program, define TABLES: PME04 and get the return-value of said feature as follows:
move-corresponding p0001 to pme04.
perform re549d using
              T588M-ZYKLS
              space
              back
              status.
Field back contains varkey for the relevant choice.
Now for field DBILD, there are th following options:
'+'         mandatory field
'.'          optional field
'-'          field invisible
'*'          field not editable
' '          screen default for field
The position of each option in field DBILD indicates the value of screen-group1.
All fields with that screen-group1 value will behave similar.
I.E. DBILD ' +          ' will assign mandatory to all fields of screen-group1 = '2'
hope that helps.
Regards
JW

How to make mandatory field in f-02 to optional field

hi. SAP Gurus
In t-code f-02 Company code and currency these two fields header data are required fields...Is it possible to make them optional fields in SPRO....If possible then please let me what is the path and T-code????

Hi,
Company Code and Currency are mandatory fields for entering any FI posting. If Company Code is left blank in which company code should post the transaction. Similarly, without indicating the currency how will the system know in which currency the transaction is to be posted.
One option is through authorizations, we can restrict to which Company codes an end user can post the transactions.
Thanks
Murali.

MB11 552 Mvt Type Cost Center as Mandatory Field,Want to change to optional

Hi
In MB11 552 Mvt Type Cost Center as Mandatory Field, Requirement here is to change the filed to optional.
Whr are the settings?
Vijay

Hi,
Go to OMJJ...then enter MVT 552....Select line for MVT 552 then click on on left hand side you will see Field selection (from 201)/Batch search procedure...Double click on mvt 552...double clik on Additional account assignments---here make cost center as optional.
Cheers
Utsav

At least one required field was empty on export. Please fill in the required fields (highlighted)

"At least one required field was empty on export. Please fill in the required fields (highlighted)"
I'm tearing my hair out with this one. Have checked all the fields to confirm if I had set the Type as User Entered - Required. Can't find any such field. Any help would be appreciated. Is there an email id where I can send the form?

Hi,
In your script when you make an object visible, you also make it mandatory. No problem there!
However the script that hides the object goes through this sequence:
hide the object, THEN
make it optional/not mandatory.
This is where the problem lies.
You FIRST need to make the object optional/not mandatory AND THEN hide the object. It should just be a simple case of work through the various scripts and having the mandatory line before the presence line.
There is an example here: http://assure.ly/hxHupW.
Hope that helps,
Niall

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

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

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

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 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

Value for mandatory field is missing

Hello again,
I created an application how descripted in 95 Implementing Remote Persistency with CAF and RFCs (Service).
The problem occurred when I try to search for an entry. I get the following error:
german: "ERROR. Wert für Pflichtattribut ... fehlt:"
english: "Value for mandatory field ... is missing"
The option mandatory=true seems to be the problem. But I need this option to make these fields available for the mapping with the create method. After I while of tinkling I find out that the errormessage appears when I set more than to fields to mandatory.
Do anybody know how to resolve this error?
Thanks!

Hi Martin,
I reported this issue to development and they said that this is "by design". Here is the recommendation.
1. set the "Mandatory" flag to false for each attribute that is not required by your external interface.
2. perform mappings for only the mandatory attributes in the create method.
3. perform mappings for mandatory and optional attributes in the update method. The update method allows you to map optional attributes.
4. At runtime, first call the create method with only the required attributes, then call the update method to fill any optional attributes.
This should eliminate the error that you get in the Service Browser.
Best Regards,
Austin.

Mandatory fields for mapping in ORDERS idoc.

Hi
I m working on File to idoc scenario for creation of sales order in ECC 6.0 , now I want to know what are the mandatory fields in ORDERS idoc which needs to be populated or else disbaled so that the sales order gets created properly in the ECC 6.0..
Pl let me know the method of finding mandatory field for mapping for any idoc and which fileds of idoc are to be disabled.
Pl help ..
ans will be rewarded .
thanks & rgds
mojib

HI,
U can disable the control record segment and in the IDOC adapter use the option apply control record from payload.
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
·        MESCOD
·        MESCFT
·        TEST
·        EXPRSS
·        STD
·        STDVRS
·        STDMES
·        SNDSAD
·        SNDLAD
·        RCVSAD
·        RCVLAD
·        REFINT
·        REFGRP
·        REFMES
·        STATUS
·        DIRECT
·        OUTMOD
·        CREDAT
·        CRETIM
read the information in below link:
http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm
thnx,
chirag

Manually created submit buttons & mandatory fields

Hi,
I included a Submit & an Email button in some of my forms. I've set them up as Regular buttons and coded them myself to do what I want eg:
if(xfa.host.messageBox("Please save this form before emailing or data will be lost","Save Form",1,1))
app.execMenuItem("SaveAs");
var sEmail = form1.Pg2.PtESF.Mgremail.rawValue;
var sSubject = ("Permit to Train Request by " + form1.Pg1.PtASF.FirstNameFld.rawValue + " " + form1.Pg1.PtASF.LastNameFld.rawValue);
var sBody = "Please approve the Permit to Train Request as attached.";
event.target.submitForm({cURL:"mailto: "+ sEmail +"?subject=" + sSubject +"&body=" + sBody,cSubmitAs:"PDF",cCharset:"utf-8"});
If I set them up as Submit buttons, they don't try to run the script more than once. I assumed this was because I had the code built in with the Submit option and it ran that as well as my own code.
So I changed the button to be a Regular button and then it worked perfectly - except for one thing.
It no longer validated the mandatory fields.
Can anyone tell me what's built into the Submit button (that I can't see), that I need to reproduce in my script for my regular button?
Thanks,
Peta

Hi,
The Submit buttons validate the from behind the scenes.
You can use execValidate() in an if statement, and if passes then execute script.
See an example here for execValidate():
http://assure.ly/hM2A5y (see last button)
http://assure.ly/flbjXB
Both of the above examples use validationState and cancelAction so are targeted to Acrobat/Reader version 9.1. Please note that execValidate() can be used in earlier versions:
http://assure.ly/lZhrSS
http://assure.ly/dYQFb4
Hope that helps,
Niall

Mandatory fields in dynpro

Hi!
I have some mandatory fields in my dynpro, but i also have a option to fill data in the dynpro after filling 2 fields and clickin a button.
The problem is that if I click the button, it says that I have to fill the mandatory fields. Is there a way to stop the control-function only for this button-click?
i tried it with exit-commands, but so i don´t get the data from the 2 filled fields, because it only transports the user-command.
thank you in advance!
Andreas

Hii Andreas..
This is the Solution for u..
You are using the Module AT EXIT-COMMAND to avoid the Mandatory field checks. But in this module the Screen fields are not Copied to Program Variables.
Only the OK_CODE(SY-UCOMM) will be copied.
But you can read the Values of the SCREEN FIELDS by Calling the FM
<b>DYNP_VALUES_READ</b>
(This Fm reads the Screen field values even before they are transported to program)
EG:
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
dyname = sy-cprog
dynumb = sy-dynnr
TABLES
dynpfields = h_dynpfields
EXCEPTIONS
OTHERS = 1.
Let me know if there are any issues.
<b>Reward if Helpful</b>

Optional/mandatory fields highlighted

Similar Messages

Maybe you are looking for