Making field in notification screen as mandatory

HI,
We have a notification screen where we have a
- button 'Reject' and
- a textbox 'Rejection reason' under the response section
We want to make the 'Rejection Reason' text box as mandatory.
Basically user should not be able to reject without giving a proper reason in the rejection field.
Please suggest how to achieve this.
Thanks,
Kamath.

Hi,
Use the below code in a standard workflow procedure,
if (funcmode = 'RESPOND') then
l_nid := WF_ENGINE.context_nid;
l_result := wf_notification.GetAttrText(l_nid, 'RESULT');
if l_result = 'REJECT' then
l_note := wf_notification.GetAttrText(l_nid,<Internal name for rejection reason field>);
l_note_text := wf_engine.GetItemAttrText (itemtype => itemtype,
itemkey => itemkey,
aname => <Internal name for rejection reason field>);
if(l_note is null) then
<Add ur message into application developer -> messages and call ur message here>
fnd_message.set_name(<application short name>, <message name>);
app_exception.raise_exception;
end if;
end if;
resultout := wf_engine.eng_completed || ':' || wf_engine.eng_null;
return;
end if;
Edited by: Nandeep CB on Mar 11, 2009 6:31 AM

Similar Messages

Making a field in selection screen dynamic mandatory

I have a parameter in the select option of a selection screen. The code is below:
TABLES:vbak,kna1,ekko,lfa1.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.
PARAMETERS: rd1 RADIOBUTTON GROUP rd DEFAULT 'X' USER-COMMAND abc,
                            rd2 RADIOBUTTON GROUP rd,
                            rd3 RADIOBUTTON GROUP rd.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE TEXT-002.
SELECT-OPTIONS:s_erdat FOR VBAK-ERDAT MODIF ID SAL,
                                   s_vbeln FOR VBAK-VBELN MODIF ID SAL,
                                   s_kunnr FOR KNA1-KUNNR MODIF ID SAL.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE TEXT-003.
SELECT-OPTIONS:p_aedat FOR EKKO-AEDAT MODIF ID PUR,
                                   p_ebeln FOR EKKO-AEDAT MODIF ID PUR,
                                   p_lifnr FOR EKKO-AEDAT MODIF ID PUR.
SELECTION-SCREEN END OF BLOCK b3.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    IF rd1 EQ 'X'.
      IF SCREEN-GROUP1 = 'SAL' OR SCREEN-GROUP1 EQ 'PUR'.
        SCREEN-ACTIVE = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDIF.
    IF rd2 EQ 'X'.
      IF SCREEN-GROUP1 EQ 'PUR'.
        SCREEN-ACTIVE = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDIF.
    IF rd3 EQ 'X'.
      IF SCREEN-GROUP1 EQ 'SAL'.
        SCREEN-ACTIVE = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDIF.
ENDLOOP.
Now the parameters s_erdap & _aedat should both be dynamic mandatory. How this can be achieved?

Hi,
This can be done in two ways:
1.
At selection-screen output.
loop at screen.
IF rd1 EQ 'X'.
   if screen-name = 's_erdat-low' or screen-name = 'P_AEDAT'.
   screen-required = 1.
modify screen.
endif.
endif.
endloop.
the above code would make the lower value in select-option s_erdat and parameter p_aedat mandatory.
2.
at selection-screen.
if rd1 eq 'X'.
if s_erdat is initial.
message 'PLease enter date'.
endif.
endif.
The above will fire an error when you hit execute and the rd1 is choosen and date is not entered
Himanshu

Making field invisible on screen shifts rest of the fields Up..

Hi All,
I am facing a problem that when i make one of my screen fields invisible the rest of the fields shifts up and fill up the space.
Can this be avoided...
please suggest
thanks in advance,
kushagra sharma

Hi,
Try to make that field with different block and then make them as invisible. it will solve ur problem
Thanks
kishore

Mandatory field in Notification

Dear Experts,
The field for damage code in notification screen has been made mandatory as part of the quality department requirement. It is required for only QM notifications but the above settings affect all PM notifications also.How to effect these changes only for QM notifications.
Thanks.

Hi,
When u go to the field selection for Maintenance notifications, there is "influencing" button. click on it. You'll have a list of Influencing field. double click on Notification type. In contents choose ur QM Notification type and make the required field "Required". Save it. Test it.
Hope this resolves ur problem.
Saurabh.

Mandatory field in selection screen of pnp logical database report

Hi experts,
Im using pnp logical database in my report.
It give the standard selection screen. I need to make some fields in the selection screen as mandatory like pnpwerks.
How its possible. Give me some solution.
Thanks,
Priya.

how about if u do this step
1. Goto- Attribute.
2. Click "Change"
3. Click 'HR Report Category'
4. Click 'Create Report Category'
5. Click 'new entries' for careating Report Category
5. Select newly create report category
6. Click the folder 'Definition of Organizational Selection'.
7. Click 'New entries'.
8. Here you assign the required fields to be displayed, for eg pywerks - personal area.
9. finally assign this newly created 'report category' in the screen you will get upon clicking 'HR report Category' button in the Program attribute screen.
Hope this may help you. I am not much into hr abap. but sharing the info which i am aware.

Making fields mandatory in tab pages in OM

Hello,
Can anyone tell me how to make an individual field within an OM infotype mandatory e.g. the employee group and the employee subgroup on IT1013 on the Working Schedule tab within PPOME?
I don't seem to be able to track down the module pool.
Thanks
Sandra.

Hi,
I think, you can use the screen control to make a field mandatory.
This is found in Tcode PM01-> GOTO-> Screen Control.
You will have to maintain the infotype feature to call the alternate screen with your screen modifications.
Details in SAP Help under Developing an Infotype in Personnel Administration -> Infotype Screen -> Control
Hope this info helps you...
Best Regards,
Venkat.

How to make input field as mandatory field in sub screen

Hi All,
I need to display the input selection parameters in tab strip sub screen. The input screen is not giving an error while processing with blank values, but I made the input field as required in sub screen input filed settings. Can some one please help me how to make the input field as mandatory field in sub screen.
Thanks in advance.
Regards,
Kannan

Hi Kannan,
Try this out.
1. Goto screen painter
2. Enter the program name and screen number ( screen # 1000 - in case if its a custom report prg)
3. Double click on the field which u`ve got to make mandatory.You`ll get Screen painter attributes window.
4. U`ll find three tabs here - Dict, Program, Display
5. Go to Program tab, and change the first attribute - Input field`s input value as "Required".
6. Save and activate it.
7. Now execute ur program and this should make ur field as mandatory on the screen.
This works with input fields, but I`m not sure about the input field in tab strip control.
Hope this helps
Regards,
Farhana

How to make WBS element field in Notification a mandatory.

How to make WBS element field in Notification a mandatory.
Should I use USer Exit.
In cutomization I didnt find ant standard customization

Hi,
If it is about WBS element field in Maintenance Order then check up user exit ;- IWO10009 PM Order: Customer Check for 'Save' Event
For Notification i am not sure whether this field is ther , but anything u can perform checkings via
QQMA0014 QM/PM/SM: Checks before saving a notification
Alternatively u can also explore via Transaction variant SHD0 ..
regards
pushpa

Saving Notifications with blank Mandatory Fields

Dear Experts,
I have an observation.
The tabs 10\TAB02 and 10\TAB06 of a notification are having mandatory fields.
Saving of this notification is refused without filling the mandatory fileds of tab 10\TAB02, but the same thing is not happening with the other tab namely 10\TAB06. (This notification is saving without filling the mandatory fields of this tab).
How to avoid this?
Regards
Jogeswara Rao

10\TAB01     Notification 1     Header Info
10\TAB02     Additional data 1     Equipment/Material
10\TAB06     Location
10\TAB10     Item     Catalogs & Codes
10\TAB11     Tasks     Tasks
10\TAB17     Additional data 4     Additional Data
20\TAB01     Item overview     Object Part & Damage
20\TAB02     Item causes     Causes
20\TAB03     Item tasks     Tasks
20\TAB04     Item activities     Activities
This is the set-up.
-Jogeswara Rao
Edited by: K Jogeswara Rao on Jul 16, 2010 7:21 AM

How to make the obligate field in selection screen

Hi ,
In my report two radio buttons and two bloc selection screens are there.When we select the first radio button first screen will be editable second screen will be non-editable vice-versa.
but the problem is in each selection screen one mandatory field is required suppose if i give the one field obligatory in first block screen it is not allowing the second readout please help me regarding this how i will make the mandatory field in both screens.
Thanks,
Harinath

Hi...
Dont Declare your field as OBLIGATORY.
Instead perform the validation in AT SELECTION-SCREEN event. But validation should be only when Particular Radiobutton is selected.
And Generate only Error Message (Type E).
Try this code:
AT SELECTION-SCREEN on <yOUR mandatory field>.
 IF PA_UPD = 'X'.
 IF <YOUR MANDATORY FIELD> IS INITIAL.
 Message 'Entry is must in this field' type 'E'.
 ENDIF.
 ENDIF.
AT SELECTION-SCREEN OUTPUT.
IF pa_udp = 'X'.
LOOP AT SCREEN.
IF screen-group1 = 'ABC'. "#CCE
screen-active = 1.
ELSEIF screen-group1 = 'DEF'.
screen-input = 0.
ENDIF.
MODIFY SCREEN.
ENDLOOP.
ELSEIF pa_rep = 'X'.
LOOP AT SCREEN.
IF screen-group1 = 'ABC'. "#CCE
screen-input = 0.
ELSEIF screen-group1 = 'DEF'.
screen-active = 1.
ENDIF.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
Reward if Helpful

ABAP Query : Obligatory fields on selection screen!

Hi Experts,
I would like to know the differrent ways through which we can define mandatory fields on selection screen.Options availabel in Infosets (SQ02) as well as Query(SQ01).
Selection Screen:
Document Date in Document: (Mandatory Select-Option)
Plant : (Mandatory Select-Option)
Thanks,
Yogesh

Hi, Everyone .
We can do that .
At selection-screen output (code section 13), set "1" to the field REQUIED by using MODIFY SCREEN code .
(You can get Dynpro number by F1 key or T-cd SE51 )
Masao .
Edited by: MASAO NONAKA on Oct 20, 2008 9:11 AM

Need created by field in notification

Hi,
In notification i want to see a field like Created by (notification creater) for all notification types.
I dont want to see that info from action log, I need a field which shows the created by person name. I want the filed like reported by field in notification.
Is there any customization settings or any user exit to do. Please suggest me.
Regards,
Bhanu

The following enhancement/user exit can be used to carry out the necessary changes to the screen
QQMA0001
User parameters
User exit u2013 QQMA0001
1. Create the project using the CMOD transaction and include the above enhancement in it.
2. Create the append structure with the new field
3. Go to the desired function group and create the sub screen with the new field. Write PBO and PAI of the sub screen if required. The field details should be as follow
Name u2013 Created by
Character length u2013 20 CHAR
4. Use function exit in the inside the enhancement to link the PBO and PAI of the sub screen to the main programme
5. Maintain the link between the standard screen of the SAP programme and the sub screen programme in CMOD transaction
6. Activate the project
Hope this helps
Sarang

Adding field dynamically on screen.

Hi All,
I have to add fields dynamically on screen based on the no. of data records.
Is there any way to add field dynamically.
I need field like this:
first a check box       second not editable field third editable field.
Table control is another way to solve the problem but only constraint about check box.
Please help me find out any solution.
Thanks in advance.
Piyush Mathur

write your code as :
AT SELECTION-SCREEN OUTPUT.
for making data set 2# inactive
IF rdt1 = c_x.
    LOOP AT SCREEN.
      IF screen-name EQ 'S_BELNR-LOW' OR
         screen-name EQ 'S_BELNR-HIGH' OR
         screen-name EQ 'P_GJAHR'.
        screen-input ='0'.
      ENDIF.
      MODIFY SCREEN.
    ENDLOOP.
ENDIF.
for making data set 1# inactive
IF rdt2 = c_x.
    LOOP AT SCREEN.
      IF screen-name EQ 'S_BUDAT-LOW'
         OR screen-name EQ 'S_BUDAT-HIGH'
         OR screen-name EQ 'S_KUNNR-LOW'
         OR screen-name EQ 'S_KUNNR-HIGH'
         OR screen-name EQ 'RDS1'
         OR screen-name EQ 'RDS2'.
        screen-input ='0'.
      ENDIF.
      MODIFY SCREEN.
    ENDLOOP.
ENDIF.
END-OF-SELECTION.

Addition of field on notification header

Hi,
I want to add the extra field on the notification header to capture the client specific data. I tried to find user field or field key to that but i am unable to find both these options in SPRO.
Then i have found one user exit i.e. QQMA0001 and documentation of this exit says that this is the exit best suitable for the addition of extra field on notification header.
Inside this user exit, following two function module
EXIT_SAPMIWO0_008
EXIT_SAPMIWO0_009
and some screen areas exist.
Now my understanding is that using one of the available screen area can we add the necessary field on header level or do i need to prepare new screen area and the assignment with the current user exit is required?
Am i on right track or is there any other way to achieve the desired result.
Waiting for the solution from the experts.
Thanks in advance

Hello,
The simplest option is to define a single custom sub-screen. This is screen area 090. Just assign this in customizing as you would any other subscreen to a notification type. This references screen SAPLXQQM / 0100. You can add the custom fields to this screen via SE51. You must append your custom fields to QMEL so they are included in structure VIQMEL and are saved with the notification.
Associated with enhancement QQMA0001 there are two function modules:
1-EXIT_SAPMIWO0_008, Transfer notification data to user screen
2-EXIT_SAPMIWO0_009, Transfer Notification Data from User Screen
You can add code to the relevant includes to verify your own data, etc.
Check the documentation for this enhancement QQMA0001 in transaction SMOD.
-Paul

How to make a field on the screen of any transaction 'display only' in BADI

Hello All,
I am working on BADI. The requirement is that for a specific condition, the user should not be able to change the 'plant' field on the screen of the standard MM transactions ME22N or ME23N.
The field 'plant' should be grayed out and the user should not be able to even enter anything in that field. Is that possible? If yes, how?
Please help, it is urgent.

hi radhika
yes u can do that
probably u will have to do the customization using exits
the possible exits fotr these trxns are
Exit Name Description
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
regards
ravish
plz dont forget to reward points if useful

Making field in notification screen as mandatory

Similar Messages

Maybe you are looking for