In Customised screen in IW53,fields are editable,how to make it output fild
Hello experts,
I am doing screen exit in IW51, i have 4 fields in this transaction. I can save the data through this transaction to database table, and i can see my data in IW52/IW53.
But the problem is that in transaction IW53 my fields are editable i.e they are input fields not output fields.I tried doing screen modifications by doing screen-input = '0' for that particular screen name but doesn't work.
Any advice please.
Thanks and Regards,
Swapnil
Dear Experts,
I Developed Screen-exit For IW51 t.codeTypically the custom fields are displayed in the notification on a separate tab, or at the bottom of the u201CGeneralu201D or u201CMainu201D tab. These are configuration decisions that could be made in the build phase.
Sets of custom fields need to be added based on the notification type. The following table provides a list and details of the custom fields required. The table to be extended is the VIQMEL table (to be verified by developer).
Also to extend header fields on the notification you need to include them in the include CI_QMEL where OPEX M&I has already fields in.
All fields should go on the notification header. There are no custom fields on the task or activity level.
All fields should be reviewed for consistency with the M&I design, specifically, Thomas Brothers, Atlas Sheet, district code. See Dale Alano.
Please any Body Helped Coding For this, Already i Created Customfields , I design Subscreen also using Enhancement QQMA0001. Using Exit name EXIT_SAPMIWO0_008 USIN SUBSCREEN 0104 PLEASE ANY BODY help me Coding for this IW52
Regards,
Santosh Ballyapelli
Similar Messages
-
Loop at screen - not all fields are available
Hi all,
I want to set some fields on the screen invisible.
When I do the loop at screen in PBO not all fields from the screen are available.
Just four fields are available. In the screen there are about 20 fields.
I try to use the chain. field xyz. endchain... But it was not the problem.
Any ideas?
regardsTry this ,May be Help ful
{ SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(10) FOR FIELD r_cars.
PARAMETERS : r_cars RADIOBUTTON GROUP rgb USER-COMMAND usd .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 20(10) FOR FIELD r_toyota .
PARAMETERS : r_toyota RADIOBUTTON GROUP rgb1 DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 20(10) FOR FIELD r_ford .
PARAMETERS : r_ford RADIOBUTTON GROUP rgb1 .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(10) FOR FIELD r_bus .
PARAMETERS : r_bus RADIOBUTTON GROUP rgb DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 20(10) FOR FIELD r_volvo .
PARAMETERS : r_volvo RADIOBUTTON GROUP rgb2 .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 20(10) FOR FIELD r_merced .
PARAMETERS : r_merced RADIOBUTTON GROUP rgb2 DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
AT SELECTION-SCREEN OUTPUT. " AT SELECTION-SCREEN OUTPUT
IF r_cars = 'X'. " If R_CURS radiobutton is selected
LOOP AT SCREEN . " Looping at screen
IF screen-name CS 'R_VOLVO' OR
screen-name CS 'R_MERCED'.
screen-active = 0. " Hiding the R_VOLVO and R_MERCED
MODIFY SCREEN.
ENDIF.
ENDLOOP.
ELSE.
LOOP AT SCREEN .
IF screen-name CS 'R_TOYOTA' OR
screen-name CS 'R_FORD'.
screen-active = 0.
ENDIF.
MODIFY SCREEN.
ENDLOOP.
ENDIF. } -
How to make report output non editable
Hi can any body give me sample code on how to make the report output non editable.
thanks in advance
kpHi
What are you meaning?
U don't want to allow to change the data in the selection-screen?
If it's so:
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
SCREEN-INPUT = 0.
MODIFY SCREEN.
ENDLOOP.
If you need to change only certain fields:
PARAMETERS: P1 ......,
P2 ...... MODIF ID AAA.
SELECT-OPTIONS: SO_1 FOR .....,
SO_2 FOR ..... MODIF ID AAA.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
CHECK SCREEN-GROUP1 = 'AAA'.
SCREEN-INPUT = 0.
MODIFY SCREEN.
ENDLOOP.
Max -
Captivate 7: How to make the output fit-to-screen
Hi Everyone,
For the long time, I was in search of making the published SWF be able to display the project as fitting to the screen. I was previously using Captivate 5.5. But now, I'm using Captivate 7. Does anyone know how to make the same thing happen to the SWF file? I previously had to make a change in the HTML script. But that same script line does not exist in the HTML file published from Captivate 7.
Please be aware that I don't know much about HTML scripts. So please be explicit with your assistance.
Thank you in advance for any assistance that you can provide.Hi there
In Captivate 7, when you publish in SWF format, choose the option titled "Scalable HTML Content".
Cheers... Rick -
Ok, so before the big change in iTunes, the iTunes window fit perfectly on the screen and there were no issues. Now, the iTunes window is blown up largely where I cannot even see my scroll bar. Even if I change the dimensions of the computer screen, nothing is working. Help!
Resize the iTunes Window.
-
Alv grid: editable individaul fields or editable rows
Hi All,
i want to have the individual fields in an ALV or a complete row editable...
Currently i am using the REUSE_ALV_GRID_DISPLAY where in the fieldcatalog if i use the edit=X then the whole column is editable...
But instead i want the particular field or the entire row to be editable...
Also let me know if it is possible using the SALV classes(Alv using classes? if so provide the releavant class and method)
Can anyone provide the solution regarding this...
Thanks
ShivaHi,
The fields you want editable just set the fieldcatlog parameter edit = 'X' for that field.
This will make that field only editable .
Below is the sample code where only specific fields are editable .
This code will also help you in many aspects.
REPORT ZMSTR0022.
CONSTANTS: C_FORM_NAME TYPE TDSFNAME VALUE 'ZMST_PER_APPL'.
TABLES :ZMST_PERMIT.
TYPE-POOLS: SLIS.
TYPE-POOLS :VRM. "Value Request Manager
TYPES:BEGIN OF STRU_ZMST_PERMIT,
CHECKBOX(1) TYPE C, " Checkbox
ZPIDNUM TYPE ZMST_PERMIT-ZPIDNUM, " Permit ID No.
ZARBDSC TYPE ZMST_PERMIT-ZARBDSC, " Arabic description
ZENGDSC TYPE ZMST_PERMIT-ZENGDSC, " English description
ZENQUAN TYPE ZMST_PERMIT-ZENQUAN, " Qty in English
ZARQUAN TYPE ZMST_PERMIT-ZARQUAN, " Qty in Arabic
ZENUOM TYPE ZMST_PERMIT-ZENUOM, " UoM
ZTARIFF TYPE ZMST_PERMIT-ZTARIFF, " Tariff No
ZARRPRT TYPE ZMST_PERMIT-ZARRPRT, " Port code
ZPRT_NAME(60) TYPE C, " Port name in Arabic
ZPERNUM TYPE ZMST_PERMIT-ZPERNUM, " Reference No
ZEFFDT TYPE ZMST_PERMIT-ZEFFDT, " Valid from
ZEXPDT TYPE ZMST_PERMIT-ZEXPDT, " Valid to
ZARB_DT(15) TYPE C, " Arabic Date of letter
ZNAME_AUTH(50) TYPE C, " Name of Authority
ZPERM_MIN(50) TYPE C, " Permit Ministry
END OF STRU_ZMST_PERMIT.
TYPES:BEGIN OF STRU_PERMIT,
ZPIDNUM TYPE ZMST_PERMIT-ZPIDNUM, " Permit ID No.
ZENGDSC TYPE ZMST_PERMIT-ZENGDSC, " English description
ZARBDSC TYPE ZMST_PERMIT-ZARBDSC, " Arabic description
ZTARIFF TYPE ZMST_PERMIT-ZTARIFF, " Tariff No
ZPERNUM TYPE ZMST_PERMIT-ZPERNUM, " Reference No
ZARRPRT TYPE ZMST_PERMIT-ZARRPRT, " Port code
ZEFFDT TYPE ZMST_PERMIT-ZEFFDT, " Valid from
ZEXPDT TYPE ZMST_PERMIT-ZEXPDT, " Valid to
END OF STRU_PERMIT.
TYPES: BEGIN OF STRU_FORM_PERMIT,
ZARBDSC TYPE ZMST_PERMIT-ZARBDSC, " Arabic description
ZENGDSC TYPE ZMST_PERMIT-ZENGDSC, " English description
ZENQUAN TYPE ZMST_PERMIT-ZENQUAN, " Qty in English
ZARQUAN TYPE ZMST_PERMIT-ZARQUAN, " Qty in Arabic
ZENUOM TYPE ZMST_PERMIT-ZENUOM, " UoM
ZTARIFF TYPE ZMST_PERMIT-ZTARIFF, " Tariff No
ZPRT_NAME(60) TYPE C, " Port name in Arabic
END OF STRU_FORM_PERMIT.
DATA: IT_PERMIT TYPE TABLE OF STRU_PERMIT.
DATA: IT_ZMST_PERMIT TYPE TABLE OF STRU_ZMST_PERMIT,
WA_ZMST_PERMIT LIKE LINE OF IT_ZMST_PERMIT,
IT_FORM_PERMIT TYPE TABLE OF STRU_FORM_PERMIT,
WA_FORM_PERMIT LIKE LINE OF IT_FORM_PERMIT.
DATA: WA_LAYOUT TYPE SLIS_LAYOUT_ALV,
WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV,
IT_FIELDCAT TYPE TABLE OF SLIS_FIELDCAT_ALV.
DATA: W_FORM TYPE RS38L_FNAM.
DATA: W_NAME_AUTH(50),
W_ZARBDT(15),
W_ZENGDT(10),
W_ZPRT_NAME(70).
DATA: W_PARAM TYPE SSFCTRLOP.
DATA:W_NAME1 TYPE DFIES-FIELDNAME,
W_NAME2 TYPE HELP_INFO-DYNPROFLD .
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-023.
SELECT-OPTIONS:S_PIDNUM FOR ZMST_PERMIT-ZPIDNUM ,
S_ENGDSC FOR ZMST_PERMIT-ZENGDSC NO INTERVALS LOWER CASE,
S_ARBDSC FOR ZMST_PERMIT-ZARBDSC NO INTERVALS LOWER CASE,
S_TARIFF FOR ZMST_PERMIT-ZTARIFF NO INTERVALS,
S_PERNUM FOR ZMST_PERMIT-ZPERNUM NO INTERVALS,
S_ARRPRT FOR ZMST_PERMIT-ZARRPRT NO INTERVALS MATCHCODE OBJECT ZMST_PORTS.
PARAMETER:P_PERTYP(2) TYPE C AS LISTBOX VISIBLE LENGTH 20.
SELECTION-SCREEN END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_PIDNUM-LOW.
W_NAME2 = 'S_PIDNUM-LOW'.
W_NAME1 = 'ZPIDNUM'.
PERFORM F4_HELP USING W_NAME1 W_NAME2 . "calling subroutine to provide desired F4 help
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_PIDNUM-HIGH.
W_NAME2 = 'S_PIDNUM-HIGH'.
W_NAME1 = 'ZPIDNUM'.
PERFORM F4_HELP USING W_NAME1 W_NAME2 . "calling subroutine to provide desired F4 help
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_ENGDSC-LOW.
W_NAME2 = 'S_ENGDSC'.
W_NAME1 = 'ZENGDSC'.
PERFORM F4_HELP USING W_NAME1 W_NAME2 . "calling subroutine to provide desired F4 help
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_ARBDSC-LOW.
W_NAME2 = 'S_ARBDSC'.
W_NAME1 = 'ZARBDSC'.
PERFORM F4_HELP USING W_NAME1 W_NAME2 . "calling subroutine to provide desired F4 help
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_TARIFF-LOW.
W_NAME2 = 'S_TARIFF'.
W_NAME1 = 'ZTARIFF'.
PERFORM F4_HELP USING W_NAME1 W_NAME2 . "calling subroutine to provide desired F4 help
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_PERNUM-LOW.
W_NAME2 = 'S_PERNUM'.
W_NAME1 = 'ZPERNUM'.
PERFORM F4_HELP USING W_NAME1 W_NAME2 . "calling subroutine to provide desired F4 help
AT SELECTION-SCREEN.
IF SY-UCOMM = 'ONLI'.
PERFORM CHECK_INPUT. "calling subroutine to check inputs on selection screen
ENDIF.
INITIALIZATION.
PERFORM VAL_PERTYP.
START-OF-SELECTION.
PERFORM FILL_FIELDCAT. "calling subroutine for filling fieldcatalog
If Permit ministry is blank then fetch data from ZMST_PERMIT otherwise from ZMST_PERMITHI--
IF P_PERTYP IS INITIAL.
PERFORM FETCH_PERMIT. "calling subroutine to fetch data from ZMST_PERMIT
ELSE.
PERFORM FETCH_PERMITHI. "calling subroutine to fetch data from ZMST_PERMITHI
ENDIF.
END-OF-SELECTION.
*& Form fill_fieldcat
text
--> p1 text
<-- p2 text
FORM FILL_FIELDCAT .
-passing the parameters of layout--
WA_LAYOUT-ZEBRA = 'X'.
WA_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
WA_LAYOUT-BOX_FIELDNAME = 'CHECKBOX'.
WA_LAYOUT-BOX_TABNAME = 'IT_ZMST_PERMIT'.
-Passing the parameters of fieldcatalog--
WA_FIELDCAT-FIELDNAME = 'ZPIDNUM'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-001.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZARBDSC'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-002.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-LOWERCASE = 'X'.
WA_FIELDCAT-OUTPUTLEN = 120.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZENGDSC'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-003.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-LOWERCASE = 'X'.
WA_FIELDCAT-OUTPUTLEN = 120.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZENQUAN'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-004.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZARQUAN'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-005.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZENUOM'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-006.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZTARIFF'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-007.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-OUTPUTLEN = 15.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZARB_DT'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_L = TEXT-013.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZNAME_AUTH'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-014.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-OUTPUTLEN = 50.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZPRT_NAME'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-009.
WA_FIELDCAT-EDIT = 'X'.
WA_FIELDCAT-OUTPUTLEN = 60.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZARRPRT'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-008.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZPERNUM'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-010.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZEFFDT'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-011.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZEXPDT'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-012.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-FIELDNAME = 'ZPERM_MIN'.
WA_FIELDCAT-TABNAME = 'IT_ZMST_PERMIT'.
WA_FIELDCAT-SELTEXT_M = TEXT-019.
WA_FIELDCAT-OUTPUTLEN = 50.
WA_FIELDCAT-LOWERCASE = 'X'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
ENDFORM. " fill_fieldcat
*& Form alv_disp
text
--> p1 text
<-- p2 text
FORM ALV_DISP .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = 'ZMSTR0022'
I_CALLBACK_PF_STATUS_SET = 'PF_STATUS'
I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
I_GRID_TITLE = TEXT-015
IS_LAYOUT = WA_LAYOUT
IT_FIELDCAT = IT_FIELDCAT
I_SAVE = 'A'
TABLES
T_OUTTAB = IT_ZMST_PERMIT
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " alv_disp
*& Form PF_STATUS
text
This subroutine sets the GUI status
FORM PF_STATUS USING RT_EXTAB TYPE SLIS_T_EXTAB.
SET PF-STATUS 'ZSTANDARD_FULLSCREEN'.
ENDFORM. "PF_STATUS
*& Form USER_COMMAND
FORM USER_COMMAND USING R_UCOMM TYPE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD.
*For Printing Smartform
IF R_UCOMM = 'PRT'.
CLEAR WA_FORM_PERMIT.
REFRESH IT_FORM_PERMIT.
LOOP AT IT_ZMST_PERMIT INTO WA_ZMST_PERMIT WHERE CHECKBOX = 'X'.
MOVE-CORRESPONDING WA_ZMST_PERMIT TO WA_FORM_PERMIT.
APPEND WA_FORM_PERMIT TO IT_FORM_PERMIT .
*Check for First occurence of Name of authority
IF WA_ZMST_PERMIT-ZNAME_AUTH NE SPACE.
IF W_NAME_AUTH = ' '.
W_NAME_AUTH = WA_ZMST_PERMIT-ZNAME_AUTH.
ENDIF.
ENDIF.
*Check for First occurence of Arabic date
IF WA_ZMST_PERMIT-ZARB_DT NE SPACE.
IF W_ZARBDT = ' '.
W_ZARBDT = WA_ZMST_PERMIT-ZARB_DT.
ENDIF.
ENDIF.
IF WA_ZMST_PERMIT-ZPRT_NAME NE SPACE.
IF W_ZPRT_NAME = ' '.
MOVE WA_ZMST_PERMIT-ZPRT_NAME TO W_ZPRT_NAME.
CONDENSE W_ZPRT_NAME.
ENDIF.
ENDIF.
CLEAR : WA_FORM_PERMIT, WA_ZMST_PERMIT.
ENDLOOP.
CONCATENATE SY-DATUM0(4) '/' SY-DATUM4(2) '/' SY-DATUM+6(2) INTO W_ZENGDT.
*Printing Subroutine
IF NOT IT_FORM_PERMIT[] IS INITIAL.
PERFORM PRINT_FORM.
ELSE.
MESSAGE TEXT-018 TYPE 'I'.
ENDIF.
ENDIF.
ENDFORM. "user_command
*& Form F4_HELP
text
--> p1 text
<-- p2 text
FORM F4_HELP USING: W_VAR TYPE DFIES-FIELDNAME
W_VAR1 TYPE HELP_INFO-DYNPROFLD .
Fetching data from zmst_permit for F4 help on PERMIT ID No.--
IF IT_PERMIT[] IS INITIAL.
SELECT ZPIDNUM
ZENGDSC
ZARBDSC
ZTARIFF
ZPERNUM
ZARRPRT
ZEFFDT
ZEXPDT
FROM ZMST_PERMIT INTO CORRESPONDING FIELDS OF TABLE IT_PERMIT.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = W_NAME1 " 'ZPIDNUM'
DYNPPROG = 'ZMSTR0022'
DYNPNR = SY-DYNNR
DYNPROFIELD = W_NAME2 "'S_PIDNUM'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = IT_PERMIT
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " F4_HELP
*& Form check_input
text
--> p1 text
<-- p2 text
FORM CHECK_INPUT .
IF S_PIDNUM[] IS INITIAL AND
S_ENGDSC[] IS INITIAL AND
S_ARBDSC[] IS INITIAL AND
S_TARIFF[] IS INITIAL AND
S_PERNUM[] IS INITIAL AND
S_ARRPRT[] IS INITIAL .
MESSAGE TEXT-016 TYPE 'E'.
LEAVE TO TRANSACTION 'ZMSTR022'.
ENDIF.
ENDFORM. " check_input
*& Form print_form
text
--> p1 text
<-- p2 text
FORM PRINT_FORM .
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
FORMNAME = C_FORM_NAME
IMPORTING
FM_NAME = W_FORM
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
W_PARAM-LANGU ='AR'.
CALL FUNCTION W_FORM
EXPORTING
CONTROL_PARAMETERS = W_PARAM
W_NAME_AUTH = W_NAME_AUTH
W_ZARBDT = W_ZARBDT
W_ZENGDT = W_ZENGDT
W_ZPRT_NAME = W_ZPRT_NAME
TABLES
IT_FORM_PERMIT = IT_FORM_PERMIT
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " print_form
*& Form fetch_Permit
text
--> p1 text
<-- p2 text
FORM FETCH_PERMIT .
-Fetching data from zmst_permit based on the inputs on selection screen--
SELECT
ZPIDNUM
ZARBDSC
ZENGDSC
ZENQUAN
ZARQUAN
ZENUOM
ZTARIFF
ZARRPRT
ZPERNUM
ZEFFDT
ZEXPDT
FROM ZMST_PERMIT INTO CORRESPONDING FIELDS OF TABLE IT_ZMST_PERMIT
WHERE ZPIDNUM IN S_PIDNUM
AND ZENGDSC IN S_ENGDSC
AND ZARBDSC IN S_ARBDSC
AND ZTARIFF IN S_TARIFF
AND ZPERNUM IN S_PERNUM
AND ZARRPRT IN S_ARRPRT.
IF SY-SUBRC <> 0.
MESSAGE TEXT-017 TYPE 'I'.
LEAVE TO TRANSACTION 'ZMSTR022'.
ELSE.
LOOP AT IT_ZMST_PERMIT INTO WA_ZMST_PERMIT.
WA_ZMST_PERMIT-ZPERM_MIN = TEXT-020.
MODIFY IT_ZMST_PERMIT INDEX SY-TABIX FROM WA_ZMST_PERMIT TRANSPORTING ZPERM_MIN .
ENDLOOP.
PERFORM ALV_DISP. " calling subroutine for ALV display
ENDIF.
ENDFORM. " fetch_Permit
*& Form fetch_permithi
text
--> p1 text
<-- p2 text
FORM FETCH_PERMITHI .
-Fetching data from zmst_permit based on the inputs on selection screen--
SELECT
ZPIDNUM
ZARBDSC
ZENGDSC
ZENQUAN
ZARQUAN
ZENUOM
ZTARIFF
ZARRPRT
ZPERNUM
ZEFFDT
ZEXPDT
FROM ZMST_PERMITHI INTO CORRESPONDING FIELDS OF TABLE IT_ZMST_PERMIT
WHERE ZPIDNUM IN S_PIDNUM
AND ZENGDSC IN S_ENGDSC
AND ZARBDSC IN S_ARBDSC
AND ZTARIFF IN S_TARIFF
AND ZPERNUM IN S_PERNUM
AND ZARRPRT IN S_ARRPRT
AND ZPERTYP = P_PERTYP.
IF SY-SUBRC <> 0.
MESSAGE TEXT-017 TYPE 'I'.
LEAVE TO TRANSACTION 'ZMSTR022'.
ELSE.
LOOP AT IT_ZMST_PERMIT INTO WA_ZMST_PERMIT.
CASE P_PERTYP.
WHEN 'I'.
WA_ZMST_PERMIT-ZPERM_MIN = TEXT-021.
MODIFY IT_ZMST_PERMIT INDEX SY-TABIX FROM WA_ZMST_PERMIT TRANSPORTING ZPERM_MIN .
WHEN 'H'.
WA_ZMST_PERMIT-ZPERM_MIN = TEXT-022.
MODIFY IT_ZMST_PERMIT INDEX SY-TABIX FROM WA_ZMST_PERMIT TRANSPORTING ZPERM_MIN .
ENDCASE.
ENDLOOP.
PERFORM ALV_DISP. " calling subroutine for ALV display
ENDIF.
ENDFORM. " fetch_permithi
*& Form val_PERTYP
text
--> p1 text
<-- p2 text
FORM VAL_PERTYP .
DATA: W_NAME TYPE VRM_ID,
IT_LIST TYPE VRM_VALUES,
WA_VALUE LIKE LINE OF IT_LIST.
WA_VALUE-KEY = ' '.
WA_VALUE-TEXT = TEXT-020.
APPEND WA_VALUE TO IT_LIST.
CLEAR WA_VALUE.
WA_VALUE-KEY = 'I'.
WA_VALUE-TEXT = TEXT-021.
APPEND WA_VALUE TO IT_LIST.
CLEAR WA_VALUE.
WA_VALUE-KEY = 'H'.
WA_VALUE-TEXT = TEXT-022.
APPEND WA_VALUE TO IT_LIST.
CLEAR WA_VALUE.
W_NAME = 'P_PERTYP'.
P_PERTYP = ' '.
CALL FUNCTION 'VRM_SET_VALUES'
EXPORTING
ID = W_NAME
VALUES = IT_LIST
EXCEPTIONS
ID_ILLEGAL_NAME = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " val_PERTYP -
How to make all fields mandatory in sales order T- code VA01 initial screen
Dear all,
how to make all fields mandatory in sales order T- code VA01 initial screen itself
The fields are
Sales Organization
Distribution Channel
Division
Sales Office
Sales Group
Regards,
Amar ReddyHi,
You can use Transaction Variant to achieve this functionality.Please go through the following link which helps you in creating the same.
[Link|http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
Regards,
Phani Prasad -
Hi ,
I am using cl_gui_alv_grid .
please let me know how to make a particular cell is editable
eg: cell corresponding to first row second column should be editabel but remaining all are non editableHi,
Loop at your internal table.
Eg: i have total 5 fields in my internal table itab_zqmeinz. in that 3 fields are editable as below.
declare DATA: lt_celltab TYPE lvc_t_styl.
internal table with celltab as one of the column
DATA: BEGIN OF itab_zqmeinz OCCURS 0. "TYPE STANDARD TABLE OF zqmseqkopf
INCLUDE STRUCTURE zqmseqeinz.
DATA: celltab TYPE lvc_t_styl.
DATA: END OF itab_zqmeinz.
LOOP AT itab_zqmeinz INTO wa_zqmeinz.
l_index = sy-tabix.
REFRESH lt_celltab.
CLEAR wa_zqmeinz-celltab.
PERFORM fill_celltab1 USING 'RW'
CHANGING lt_celltab.
INSERT LINES OF lt_celltab INTO TABLE wa_zqmeinz-celltab.
MODIFY itab_zqmeinz FROM wa_zqmeinz INDEX l_index.
ENDLOOP.
FORM fill_celltab1 USING value(p_mode)
CHANGING pt_celltab TYPE lvc_t_styl.
Refresh pt_celltab.
clear ls_celltab.
IF p_mode EQ 'RW'.
l_mode = cl_gui_alv_grid=>mc_style_enabled. "to enable the required fields
ELSE. "p_mode eq 'RO'
l_mode = cl_gui_alv_grid=>mc_style_disabled.
ENDIF.
ls_celltab-fieldname = 'NEBENSEQUEN'. " field1
ls_celltab-style = l_mode.
INSERT ls_celltab INTO TABLE pt_celltab.
ls_celltab-fieldname = 'BEZEICHNUNG'. "field2
ls_celltab-style = l_mode.
INSERT ls_celltab INTO TABLE pt_celltab.
ls_celltab-fieldname = 'SORTIERUNG'. "field3
ls_celltab-style = l_mode.
INSERT ls_celltab INTO TABLE pt_celltab.
Endform.
It works. I have done it in my program.
Thanks, -
Hi All,
In my instance MTL_RELATIONSHIP_TYPES lookup is disabled for editing , how to make it editable?
Any profile options?
Please help
Thanks,Verify you are not in read only responsiblity.
-
Make Screen field non editable
Hi All,
We have following requirement in our project:
When entering infotype 1 in any action a check should be made to set default values in Work Contract. If Employee Group =u2019 1u2019, Work Contract u2018ZFu2019 should be set and this value must not be changed. If Employee Group u20181u2019 the Work Contract could be all other values except u2018ZFu2019.
We are using badi HRPAD00INFTY to handle the above requirement. But there is a problem. When we perform an action and go to infotype 1 screen the contract field is populated with correct value and is display only field. Once you press enter on the screen the field becomes an editable field and can be changed by the user. I debugged the program and found that PSYST-NSELC is set as NO (0) in the program MP000130 and is checked if it has a value YES in module p0001 called in PBO of screen 2000 include MP000120. If the value is YES only then BADI is called else not.
Can someone suggest what could be the problem area or any other way to meet the requirement ?
BR Jaideep,
Duplicate Post. Continue here: Screen field not getting editable..
Edited by: kishan P on Sep 9, 2010 2:20 PMCan you explain how a physical inventory is done in your company., and what problems come up if a wrong date is entered?
In my company we create and print the inventory documents immediatly before counting, and we are making sure, that the volume can be counted, entered and difference posted on the same day.
Further we are setting a posting block in SAP, and of course we make sure that no physical movement happens during the count.
And of course we make sure that everyting what was received or issued prior to the count is already entered in sAP before we start creating the documents.
SAP takes the book inventory in the moment the counted quantity is entered in this case. No matter if the user enters a count date of today or of last week.
But if you close the field (which is not possible with customizing), then you have to make sure that you enter the count on the same day you have counted, because if you would enter the count on the next day, then your counting date would be wrong and you would not have a chance to enter the correct counting date.
And as SAP stores everything what a user enters, it is easy to identy the user who has fooled the system, and then the HR guy should do his job, especially as the physical inventory is in most countries a legal requirement, which has to be done seriously.
don't give authorization to the guys who dont follow your policies. -
Making the Business Area field as editable
Hi
We have business area field as compulsory field for document splitting. The same is picking up on the Business Area assignment in SD. However, the field for the same is seen as greyed out field in Sales Order at line item level. we would like to make the same field as editable. How can the same be done?
Regards
Rahul SharmaHi
The fields in a sales order can be made optional / mandatory by following this menu path - IMG - S&D-> Basic > Functions-> Log of incomplete Procedures => select the fields > from the tables and the system will check for them (OVA2/VUA2)
To make a filed entry enabled or grey (non-entry allowed):
User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields. To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP.
If a field has no field name, it cannot be allocated to a group. The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains LOO for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit. This FORM routine is called up by the module FELDAUSWAHL.
Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
Below is the sample code
IF SCREEN-NAME = VBKD-ABSSC.
AUTHORITY-CHECK OBJECT ZMV45AFZZ ID SCRFNAME FIELD SCREEN-NAME.
IF sy-subrc = 0.
SCREEN-INPUT = 1.
else.
SCREEN-INPUT = 0.
ENDIF.
endif.
You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit. -
How to make screen fields editable
Hi all,
iam writing a validation for FD32 transaction in exit, if the validation fails showing error message.
Porblem is when ever error message comes and after that if i press enter fields are going to mode of non editable ( Display mode), how to make them editable which were already editable ( before error message comes).
Iam not using module pool program for this, iam writing code in include exit and throwing the message.
Thanks,Hi,
You can use pop up window to display error message as below:
-Quote-
AT SELECTION-SCREEN ON ABCD.
IF <condition fails>.
CALL FUNCTION 'FC_POPUP_ERR_WARN_MESSAGE'
EXPORTING
popup_title = 'Error'
IS_ERROR = 'X'
message_text = 'Error message description'
start_column = 25
start_row = 6
STOP.
ENDIF.
-Unquote-
You may also use:
-Quote-
IF <condition fails>.
MESSAGE 'abcd' TYPE 'E'.
ENDIF.
-Unquote-
Kindly let me know whether this is of any help or not.
Regards,
Shayeree. -
PO screen custom fields are not in correct order
Hi Experts,
After creating Shopping cart and purchase order successfully created.
Added my custom fields for PO structure INCL_EEW_PD_ITEM_CSD_PO fields are visible in PO screen automatically with out adding my custom fields in PO layout /SAPSRM/WDC_DODC_PO_I_BD
when i go to PO screen i can see my custom fields but all fields are not in correct order.How can my fields should be in order.
and i added two custom buttons in my PO layout for WD component /SAPSRM/WDC_DODC_PO_I_BD i am not able to see my buttons?
Could you please help me out in this issues its urgent.
Thanks,
Venkatesh GI've had this problem. There may be a more elegant solution, but what I do is make a playlist of the album and put the movements in the correct order in the playlist. I've also put numbers (01, 02, etc.) in front of the name of the movements. Either one works.
Hope this helps.
Ben -
How to make fields not editable in screen
Hi gurus,
I have a table and i need to make some fields not editable depending on the values of other fields of the table .
Example :
my table have these fields : begin_date, name.
If the begin_date < sy-datum --> then the field ' name' should not be editable.
Tankyou.Hi,
OK. I did some code and was able to get the results as you want. Created a table YTESTHV with two fields YYDATE and NAME. Generated a two screen maintenence for the table. Screen 2 - Overview screen, screen 3 Detail screen.
Overview screen.
PBO.
PROCESS BEFORE OUTPUT.
MODULE LISTE_INITIALISIEREN.
LOOP AT EXTRACT WITH CONTROL
TCTRL_YTESTHV CURSOR NEXTLINE.
MODULE LISTE_SHOW_LISTE.
MODULE DISABLE_FIELDS.
ENDLOOP.
MODULE DISABLE_FIELDS
move extract to YTESTHV.
if YTESTHV-yydate > sy-datum.
loop at screen.
if screen-name = 'YTESTHV-NAME'.
screen-input = '0'.
modify screen.
else.
screen-input = 1.
modify screen.
endif.
endloop.
endif.
Details screen PBO.
PROCESS BEFORE OUTPUT.
MODULE detail_init.
module change_mode.
module change_mode
if YTESTHV-yydate > sy-datum.
loop at screen.
if screen-name = 'YTESTHV-NAME'.
screen-input = 0.
modify screen.
endif.
endloop.
endif.
When YYDATE is greater than sy-datum field NAME is display only.
Regards,
Himanshu -
How to make a field un editable in one screen
Dear Experts,
I want to know how to make one field as un editable in one screen.I will explain in detail. I want to make "Reconciliation account" field as un editable in XD02 t-code.
Regards,
Surendra babu.Hi Surendra,
Use this path in spro:
Financial Accounting-> A/P&A/R-> CustomerAccounts->MasterData->Preparatons for CreatingCustomerMasterData
use the transactions & u can update for creation of customer master or hange of customer master.
Hope this helps you
Award points if helpful
chaitanya
Maybe you are looking for
-
External Hard Drive Suddenly Loaded With Corrupt Image Files (Mac User)
I'm using an iMac with CS6. I have an external Maxtor 1TB drive that is 13 months old. I have had no issues at all with it until today, when I attempted to access a PSD file from the drive and received an error message telling me that the document w
-
What is an ISO Image? and how do I use bootcamp?
What is an ISO Image? and how do I use Bootcamp
-
I'm using LabVIEW 2010 SP1 (32-bit) and I noticed today that I cannot place my custom controls on a VI's front panel when I use the "Select a Control..." option on the "Controls" pop-up palette. I'm wondering if anyone else is having this same proble
-
I've extracted a set of BOM from Table: STPO Kindly refer to image link [http://i.imgur.com/R6MxS.png] Is there a way to filter out those old component? In PP, is there a table where it stores the status like Deletion Indicator? Btw, i'm using query
-
Still in logic 8.0.2. When using specific plug-ins like limiter, TC linearphase eq et cetera, the timeline spl is not in sync with the waveform overview during playback. Is this normal or expected behaviour? Anything I can change? Its hard to cut reg