Hiding fields in screen area 031

Hello Masters,
I have query on hiding following fields in Quality Notification screen area 031of Notification Type Q2:
1) Windows-32 bit box (big box/window under Description field)
2) Long Text icon available next to big box/window which is also available next to Description field in header
I tried 'Field Selection: General Screens' configuration under Define Screen Templates, was unable to hide above mentioned field(window) and icon.
I hope I was able to describe what issue is and will get some help from you masters.
Thanks and regards,
Devang

Use (or Create) authorization [field|http://help.sap.com/saphelp_nw04/helpdata/en/52/67168c439b11d1896f0000e8322d00/frameset.htm] and [object|http://help.sap.com/saphelp_nw04/helpdata/en/52/6716a6439b11d1896f0000e8322d00/frameset.htm], in the BAdI [check this authorization|http://help.sap.com/abapdocu_70/en/ABAPAUTHORITY-CHECK.htm] and change the INVISIBLE field and not the ACTIVE field in SCREEN structure.
- [Programming Authorization Checks|http://help.sap.com/saphelp_nw04/helpdata/en/52/6712ac439b11d1896f0000e8322d00/frameset.htm]
Inform system admin to manage those new object and field in the user roles. ([SAP Authorization Concept Modules|http://help.sap.com/saphelp_banking463/helpdata/en/5c/deaa74d3d411d3970a0000e82de14a/frameset.htm])
Regards,
Raymond
NB: The "d" of BAdI should always been in lowercase, except in statement GET BADI...

Similar Messages

Fields from screen are not known by program.

Hi All.
I have this problem since I started using Dialog programming.
Since I didn't attended any course I might be doing something wrong.
When you define a field in a Dialog screen and you want to refer to it in the program that calls that screen you get a compilation error that there is no such field.
If you define the field as at TABLE-FIELD you can work around this compilation issue by defining the TABLE using "tables: TABLE" statement, but now I have a problem since I don't want to use the TABLE-FIELD definition for my field and thus I'm stuck Shocked
Any help will be appreciated.
Ayal.

Hai,
If suppose, if you define a field in the screen, it is not mandatory to declare same variable in program level. If we take the same name, after completion of PBO the data automatically transferred to the screen field. If u don't take the same name then you need to pass value of the variable to the screen field in the PBO.
Example :
If suppose, you have a I/O field in the screen with name TEXT.
In the program
data : text(10) type C.
if that is 100 screen.
Process before output.
module display_100.
with in this module
text = 'SRIKANTH'.
this will directly display on the screen.

Problem with Hiding fields of selection screen which is called as subscreen

Hello All,
I have problem while hiding the selection screen which is called as subscreen.
Flow of my logic:
Selection-screen with one field and three buttons CREATE,DISPLAY and CHANGE in application toolbar.
user enter some value in field and either he press change or dispaly
When change i need to call selection screen when it is in dispaly i need to stop calling this selection screen.
Upto my knowledge we can't stop calling selection screen in display mode so there is only one possibility is hiding the fields when it is in display mode.
How can i hide the fields and where i need to hide fields?
Please post some codes.
Regards,
Lisa

you can refer the sample code which i mentioned in your previous post. that will solve the problem.

Hiding field in LDB PERAS selection screen

Hi all,
I need to generate a report on which I wanted to use the LDB PERAS to help me for the data selection.
But I don't want to use the "selection criteria" selection block of LDB PERAS selection screen.
On which there are criteria such as:
1. Personnel Number
2. Employment Status
3. Personal Area
4. Personal Subarea
5. Employee Group
6. Employee Subgroup.
Is there anyway to hide the "selection criteria" selection block?
Many Thanks

Hi,
Test the following Sample Code it is working Fine for me.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    if screen-name = '%_PNPPERNR_%_APP_%-TEXT' " For Text Lable
     or screen-name = 'PNPPERNR-LOW'                     " For Text Field
     or screen-name = '%_PNPPERNR_%_APP_%-VALU_PUSH'. " For Extension Button
      screen-active = '0'.
      screen-invisible = '1'.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
Please Reply if any Issue,
Best Regards,
Faisal

Hiding fields in a screen using BADI

Hi Experts
I want to invisible certain fields in the screen for certain users and it should be made visible for certain users,the requirement is to do with badi.Can anyone help me regarding this issue.
Thanks & Regards
Pravitha

Use (or Create) authorization [field|http://help.sap.com/saphelp_nw04/helpdata/en/52/67168c439b11d1896f0000e8322d00/frameset.htm] and [object|http://help.sap.com/saphelp_nw04/helpdata/en/52/6716a6439b11d1896f0000e8322d00/frameset.htm], in the BAdI [check this authorization|http://help.sap.com/abapdocu_70/en/ABAPAUTHORITY-CHECK.htm] and change the INVISIBLE field and not the ACTIVE field in SCREEN structure.
- [Programming Authorization Checks|http://help.sap.com/saphelp_nw04/helpdata/en/52/6712ac439b11d1896f0000e8322d00/frameset.htm]
Inform system admin to manage those new object and field in the user roles. ([SAP Authorization Concept Modules|http://help.sap.com/saphelp_banking463/helpdata/en/5c/deaa74d3d411d3970a0000e82de14a/frameset.htm])
Regards,
Raymond
NB: The "d" of BAdI should always been in lowercase, except in statement GET BADI...

Hiding fields in HCM forms

Hi Experts,
I have following requirement for hiding fields in my form.
I have two screens MANAGER and HR screen.
now i have some input fields which has to be visible in MANAGER screen and
and should be hidden in HR screen.
please let me know how can i achieve this using form calc or java script.
any code will be helpful.
Thanks,
Santosh

Hi sushmita,
Thanks for ur reply.
The solution which you have given i have already tried but not working.
my requirement is like MGR or HR can initiate the process.
if only MGR intiates the process the solution which u have given will work.
but here i have a diff scenario.i have created separate process for HR also but im not able
to see that process on the process list.
so i have to use only one process and resolve this.whatever im writing validation is working
only when MGR initiates the process but fails when HR initiates.
Hope u got my point.any suggestions will be helpful.
Thanks,
santosh

Hiding fields in phtmlb:formLayout (new thread)

Original Thread:
hiding fields in a bsp...
What Kevin is talking about, is some special development we did for HR eRecruitement. Well, let us turn it around. They helped us, and we returned the favour. And yes, this is actually some of the more interesting bits and pieces of BSP. (Fresh meat to discuss:).
Effectively, the <phtmlb:formLayout> has two functionalities. The first is a very easy way to layout a form. The second is a way via customization to dynamically have customers overwrite the visibility/required property of each field. So the SAP puts the maximum number of fields into the formlayout, and the customer can then via customization remove some, flag some as required, etc.
(If anybody should feel like writing a long weblog on this, I will provide technical detail, plus examples offline.)
The interesting database tables are these PHTMLB_FLI* ones. Part of the agreement was that the application itself provides for a UI to update the table. Also, the application itself controls which fields are changable.
If you really want to play, look at SBSPEXT_PHTMLB, the formLayout example. In the top part, there are also a serious of dropdown listboxes. What these do, is that they update the customization tables first, before the formlayout is rendered. So what you are seeing is actually the formlayout as it has been programmed, plus then the effects of a (customer) customization on it.
Also the example shows the effect of using an XML bee to dynamically add entries into the fieldLayout (if the application added these hooks).
brian

Hallo Thomas,
No, unfortunately we never build something to also customize the labels. They HR colleagues did not ask for this :).
I first started to write you here a loong text with answers. But then I got lazy, and searched my archive mailbox. Here below is the draft input that I wrote initially for the documentation. It describes everything pretty good. (But it is draft document, never proofread again, so read it lightly!)
bye, brian
Why?
Typically when an application is developed at SAP, the developer must make provision for all possible fields of information that must be displayed and/or queried from the user. However, in specific business cases, or depending on specific country laws, all fields might not be required. Also in some cases, fields in one scenario can be flagged required, versus in another they are only optional.
The typical starting point will be a complete formlayout done during the development. On top of this a customization layer is placed. The automatic reading and applying of the customization layer is automatically done by the phtmlb fL.
What?
For each field, a default behaviour is assumed. This is the behaviour that is defined by the developer during development time. For example, it could be specified that email address must be required. During the runtime it is now possible to overwrite the default behaviour with a customization entry for the field.
The following options are supported:
As Defined: The formLayoutItem in displayed as it has been defined during development.
Invisible: The formLayoutItem is not placed on the formLayout. It is immediately removed. All following items below it, will be moved up to fill its position.
Hidden: In this case, the formLayoutItem is placed on the formLayout, but not displayed. The item reserves its slot, and an empty slot will be displayed. However, after all items have been placed on the formLayout, a row "compression" is done, whereby all rows that contain only hidden elements are removed. Hidden is important for cases where columns next to one another must align. A typical example would be name & surname horizontally aligned. If now one item is invisible before this row, the two items will not be aligned anymore. With hidden, this alignment will be kept, and we still have the benefit of empty rows been removed.
Required: Sets the required flag for the item. Label of item will be rendered an indication that it is required (usually little red asterix after the label).
Optional: Can be used to customize a required field to be not required.
Read Only: Field value is only displayed.
What is index?
Customization is stored for a formLayout under the key that is build from the BSP application namespace, BSP application name, plus the page/view on which the formLayout is placed. It is assumed that there will only be one formLayout per view. A typical example would be:
SAP/SBSPEXT_PHTMLB/FORMLAYOUTSAMPLE.HTM
In addition, a customization key must be specified. Typical examples would be to say this is the default customization for USA, or for the specific branchen Losuegn. The customization key must be supplied with the <phtmlb:fL> tag, and only then will the customization data be read from the database.
Tables
For customization there are three interesting tables.
The first table PHTMLB_FLI is completed by the developer, and defines a list of all the formLayout items that can be customized. Only for those flItems which customization is possible, will entries be made in this table. The table contains three components:
NS_APPL_PAGE This is the unique key that identies the formLayout, consisting of namespace, application and page/view.
FLI_ID Id string of the specific formLayoutItem.
COMPONENT This is software component to which development applies, for example SAP_BASIS for all BSP development work done by us.
The second table PHTMLB_FLI_TEXT is just a language dependant text table that describes each item in the formLayout.
The tables PHTMLB_FLI and PHTMLB_FLI_TEXT are not using during the runtime. They are only of interest for design time. Note that NO tools are provided to make any entries in these tables. This is considered to be in the application domain, and will usually be part of the customization process of the application.
The third table PHTMLB_FLI_CUST is the only table that is read during the runtime. It is assumed that a customization tool has made the relevant entries for this table.
NS_APPL_PAGE see above
VARIANT_KEY This is the specific customization layer that is currently active. This string is equavalent to <pthmlb:fL customizationKey>. It is used to pull a specific customization.
FLI_ID see above
MODIFIER This is the new value to apply. For the possible values, see DDIC domain PHTMLB_FLI_MODIFIER.
For an example of customization, see BSP application SBSPEXT_PHTMLB, pages formLayout.htm. In this example, the customization can quickly be set via dropdown listboxes. On each request the PHTMLB_FLI_CUST is quickly updated and then the formLayout will find the set of new customization data to use.

Field Bus. Area is a required field for G/L account company code g/l ac

hi ,
I am getting this following error when trying to post a cenvat in the tcode of J1iEX .
"Field Bus. Area is a required field for G/L account <companycode> <cenvat g/l acct.no.> "
Message no. F5808
Diagnosis
The value for field "Bus. Area" in the interface to Financial Accounting is an initial value but you are required to make an entry in the field selection for G/L account "13113920" in company code "LECS" linked to the field selection for posting key "50".
System Response
Error
Procedure
It might be an error in the configuration of the G/L account field selection. The initial application, used to call up the interface must otherwise define a value for field "Bus. Area". If this is the case, contact the consultant responsible for the application used to call up the interface or get in contact with SAP directly.
Plz help me ..
Regards
Deepa

Hi Deepa,
At Easy access screen :
1.Go to the master account of that G/L (F-02).
2.Check the field status variant defined there.
At Customization screen (SPRO):
3.Go to the master account of that field status variant.
4.Change the status of business area field optional.
Nikhil Garg

Error when displaying a field on Screen with Table Control

Hi,
It is going to 'Dump' when I am trying to display data on the screen with the help of Table Control. From the dump, What I have observed is , there is a field 'ZTSV_FSRDATA-ANZFEHLER'. If this field has negative value, then it is going to 'Dump' saying that the length is not enough. If it has a positive value then it is working fine. But the type of the field in the Internal table & on the screen are same.
Please help me to resolve this error.
I am posting here the Dump message also:
A conversion error occurred while the program was trying todisplay data on the screen.
The ABAP output field and the screen field may not have the same format.
Some field types require more characters on the screen thanin the ABAP program. For example, a date field on a screen needstwo characters more than it would in the program. When attempting to display the date on the screen, an error will occur that triggers the error message.
Thanks,
Sreenivas Reddy Maddi.

Hi Sreenivas,
Refer this thread:
how to display negative values in a screen field of a screen
Re: negative values not allowed
Regards,
Sampath

Enlarge size of a field on screen

Hello,
I'm looking for a way to enlarge the size of a field on screen. For instance when you have the Delivery screen the field where the name of the customer is shown is quite short. When the customers name is in total 60 characters you only can view 30 characters.
So the see all the characters it would be nice that you could enlarge this field.
I know that the are programs like Screen Painter and add on's like B1UP to alter your screen, but do you really need to use these programs to alter what I would like to do. If so is Screen Painter the only free program to do so.
Best regards,
Tim

Tim,
Just painter is just a tool at design the screen layout, I do not believe you would be able to manipulate an existing B1 form using this.
What tools like B1UP do is generate SDK Code in the background based on your selection and setting in the GUI.
So the answer is you could do it without any Addon's by using SAP's SDK tools
Suda

SOME FIELDS OF WORK AREA ARE CONVERTED TO ***** AT AT NEW STATEMENT

HELLO
SOME OF THE FIELDS OF WORK AREA ARE CONVERTED INTO *********** AT AT NEW STATEMENT .FIND BELOW THE CODE
*& Report YTEST_OBJECTS7
REPORT YTEST_OBJECTS7.
Program Description
Author.........: Jitendra Dash *
Creation date..: 17/09/2010 *
GAP ID/FS Id...: *
Transport......: *
Description u2026..: *
CHANGE HISTORY u2013 Should be completed in reverse date order *
Revised by........: <Developer name> *
Change date.......: Date of creation> *
CR/Defect No......: <Change Request No>/ <Defect#<xxx> *
Transport.........: <Request No> *
Description.......: Description about modification *
Data Declaration
TYPES: BEGIN OF gx_input,
 NEMI TYPE EXT_UI,
 DIVISION TYPE SPARTE ,
 DATE TYPE ERDAT,
 DATE1 TYPE ERDAT,
 END OF gx_input.
TYPES: BEGIN OF gx_input1,
 NEMI TYPE EXT_UI,
 DIVISION TYPE SPARTE ,
 DATE TYPE ERDAT,
 DATE1 TYPE ERDAT,
 int_ui TYPE INT_UI,
 ANlage type anlage,
 SERVICE TYPE SERCODE,
 SERVICEID TYPE SERVICE_PROV,
 SPARTE TYPE SPARTE,
 END OF gx_input1.
TYPES : BEGIN OF gx_euitrans,
 INT_UI TYPE INT_UI,
 EXT_UI type EXT_UI,
 END OF gx_euitrans.
TYPES : BEGIN OF gx_eservice,
 INT_UI TYPE INT_UI,
 SERVICE TYPE SERCODE,
 SERVICEID TYPE SERVICE_PROV,
 SPARTE TYPE SPARTE,
 END OF gx_eservice.
TYPES : BEGIN OF gx_inst,
 int_ui TYPE INT_UI,
 ANlage type anlage,
 END OF gx_inst.
TYPES : BEGIN OF gx_ever,
 ANLAGE TYPE anlage,
 EINZDAT TYPE EINZDAT,
 AUSZDAT TYPE AUSZDAT,
 VERTRAG type VERTRAG,
 vkonto TYPE VKONT_KK,
 END OF gx_ever .
TYPES : BEGIN OF gx_fkkvkp,
 VKONT type VKONT_KK,
 GPART type GPART_KK,
 END OF gx_fkkvkp.
DATA : GIT_INPUT TYPE STANDARD TABLE OF GX_INPUT,
 git_euitrans TYPE STANDARD TABLE OF gx_euitrans,
 git_eservice TYPE STANDARD TABLE OF gx_eservice,
 git_inst TYPE STANDARD TABLE OF gx_inst,
 git_ever TYPE STANDARD TABLE OF gx_ever,
 GIT_INPUT1 TYPE STANDARD TABLE OF GX_INPUT1,
 GIT_fkkvkp TYPE STANDARD TABLE OF GX_fkkvkp,
 WA_INPUT TYPE gx_input,
 wa_euitrans LIKE LINE OF git_euitrans,
 wa_eservice like LINE OF git_eservice,
 WA_inst LIKE LINE OF git_inst,
 wa_ever LIKE LINE OF git_ever,
 wa_INPUT1 like LINE OF git_INPUT1,
 wa_fkkvkp like LINE OF GIT_fkkvkp.
DATA: gv_v_localfile TYPE localfile,
 gv_g_localfile type string,
 gv_g_alocalfile type string,
 gv_g_sender type SERVICE_PROV,
 gv_g_reciever type SERVICE_PROV.
CONSTANTS : GC_AINP TYPE c LENGTH 50 VALUE '/tmp'.
************Selection screen for input *********************
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE t1.
PARAMETERS : p_rad1 RADIOBUTTON GROUP grp DEFAULT 'X' USER-COMMAND chk,
 p_rad2 RADIOBUTTON GROUP grp,
 p_file TYPE file_table-filename MODIF ID m1,
 p_afile TYPE file_table-filename MODIF ID m2.
SELECTION-SCREEN END OF BLOCK b1.
***************Initialization*****************************
INITIALIZATION.
t1 = text-001.
***Selection of Appl ser and Presen ser for I/P file******
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
 IF p_rad1 = 'X'.
 IF screen-group1 = 'M2'.
 screen-active = 0.
 MODIFY SCREEN.
 ENDIF.
 ELSEIF p_rad2 = 'X'.
 IF screen-group1 = 'M1'.
 screen-active = 0.
 MODIFY SCREEN.
 ENDIF.
 ENDIF.
ENDLOOP.
**F4 help for inputting the Filename from presentation Ser*
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 program_name = sy-repid
 dynpro_number = sy-dynnr
 field_name = p_file
 CHANGING
 file_name = gv_v_localfile
 EXCEPTIONS
 mask_too_long = 1
 OTHERS = 2.
IF sy-subrc = 0.
 MOVE gv_v_localfile TO p_file.
 move gv_v_localfile to gv_g_localfile.
ENDIF.
***F4 help for file on Application Server*******************
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_afile.
CALL FUNCTION '/SAPDMC/LSM_F4_SERVER_FILE'
 EXPORTING
 directory = GC_AINP
 filemask = ' '
 IMPORTING
 serverfile = p_afile
 EXCEPTIONS
 canceled_by_user = 1
 OTHERS = 2.
IF sy-subrc = 0.
 move p_afile to gv_g_alocalfile.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
START-OF-SELECTION.
IF p_rad1 = 'X'.
*************Upload file into Itab from pres server*********
 CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = gv_g_localfile
FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = '|'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
VIRUS_SCAN_PROFILE =
NO_AUTH_CHECK = ' '
IMPORTING
FILELENGTH =
HEADER =
 TABLES
 DATA_TAB = GIT_INPUT
 EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17
 IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
ELSEIF p_rad2 = 'X'.
*************Upload file into Itab from Applic server*********
************file should be ; seperated and not tab seper******
 TRANSLATE gv_g_alocalfile USING '\/'.
 OPEN DATASET gv_g_alocalfile FOR INPUT MESSAGE gv_LC_MESSAGE in TEXT MODE ENCODING DEFAULT.
 IF sy-subrc = 0.
 DO.
 READ DATASET gv_g_alocalfile INTO wa_xls.
 IF sy-subrc IS NOT INITIAL.
 EXIT.
 ELSE.
 APPEND wa_xls TO git_xls.
 ENDIF.
 ENDDO.
 ENDIF.
 close DATASET gv_g_alocalfile.
ENDIF.
SELECT INT_UI EXT_UI from EUITRANS
 into CORRESPONDING FIELDS OF TABLE git_euitrans
 for ALL ENTRIES IN GIT_INPUT
 WHERE ext_ui = GIT_INPUT-NEMI.
SElect INT_UI
 SERVICE
 SERVICEID
 SPARTE from ESERVICE
 into CORRESPONDING FIELDS OF TABLE git_eservice
 FOR ALL ENTRIES IN git_euitrans
 where INT_UI = git_euitrans-INT_UI .
SELECT INT_UI
 ANLAGE from euiinstln
 into CORRESPONDING FIELDS OF TABLE GIT_INST
 FOR ALL ENTRIES IN git_eservice
 WHERE INT_UI = git_eservice-INT_UI.
LOOP AT git_eservice into wa_eservice.
 READ TABLE git_euitrans into wa_euitrans
 with KEY int_ui = wa_eservice-int_ui.
 IF SY-SUBRC = 0.
 READ TABLE git_input into wa_input
 WITH key NEMI = wa_euitrans-EXT_UI.
 IF SY-SUBRC = 0.
 READ TABLE GIT_INST into WA_INST
 with key int_ui = wa_eservice-int_ui.
 IF Sy-subrc = 0.
 wa_input1-NEMI = wa_input-NEMI .
 wa_input1-DIVISION = wa_input-DIVISION.
 wa_input1-DATE = wa_input-DATE.
 wa_input1-DATE1 = wa_input-DATE1.
 wa_input1-int_ui = wa_eservice-int_ui.
 wa_input1-anlage = WA_INST-anlage.
 wa_input1-SERVICE = wa_eservice-service.
 wa_input1-SERVICEID = wa_eservice-serviceid.
 wa_input1-SPARTE = wa_eservice-sparte.
 Append wa_input1 to git_input1.
 ENDIF.
 ENDIF.
 ENDIF.
 clear : wa_eservice,wa_input,WA_INST,wa_euitrans,wa_input1 .
ENDLOOP.
SELECT anlage
 EINZDAT
 AUSZDAT
 VERTRAG
 VKONTO from ever
 into CORRESPONDING FIELDS OF TABLE git_ever
 FOR ALL ENTRIES IN git_input1
 WHERE anlage = git_input1-ANLAGE
 and EINZDAT = git_input1-DATE
 or AUSZDAT = git_input1-DATE1.
Select Vkont Gpart from fkkvkp
 into CORRESPONDING FIELDS OF TABLE git_fkkvkp
 for ALL ENTRIES IN git_ever
 where Vkont = git_ever-Vkonto.
LOOP AT git_input1 INTO wa_input1 .
IF wa_input1-SPARTE = 01 .
CASE wa_input1-SERVICE.
WHEN 'FRMP'.
 gv_g_sender = wa_input1-SERVICEID.
WHEN 'LNSP'.
 gv_g_reciever = wa_input1-SERVICEID.
ENDCASE.
ELSEIF wa_input1-SPARTE = 02 .
CASE wa_input1-SERVICE.
WHEN 'FRO'.
 gv_g_sender = wa_input1-SERVICEID.
WHEN 'DB'.
 gv_g_reciever = wa_input1-SERVICEID.
ENDCASE.
ENDIF.
data : int_ui TYPE INT_UI.
*int_ui = wa_input1-int_ui .
AT NEW int_ui .
READ TABLE git_ever into wa_ever with key anlage = wa_input1-anlage.
READ TABLE git_fkkvkp INTO wa_fkkvkp with key Vkont = wa_ever-Vkonto.
CALL FUNCTION 'ZIN_COMEV_CUSTDETAILNOTIF_OUT'
EXPORTING
 Y_SENDER = gv_g_sender
 Y_RECEIVER = gv_g_reciever
 Y_PARTNER = wa_fkkvkp-gpart
 Y_BASIC_PROCESS = 'ZCDNO'
Y_SWITCHNUM =
Y_SEN_LOAD =
 Y_INTUI = wa_input1-int_ui
Y_TRANSACTIONID =
 Y_DATE = wa_input1-DATE
IMPORTING
X_TASK_ID =
TABLES
 IDOC_STATUS =
 IDOC_CONTRL =
 XYT_ERROR =
EXCEPTIONS
GENERAL_FAULT = 1
NOT_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.
ENDAT.
ENDLOOP.
IN THIS PROGRAM AT AT NEW STATEMENT IN LOOP SOME OF THE FIELDS OF wa_input1 IS CONVERTED TO ***** E.G wa_input1-anlage.
pLEASE HELP ME OUT

HELLO
My Q is some fields at AT NEW statement turns into *****.Please help me out
TYPES: BEGIN OF gx_input1,
 NEMI TYPE EXT_UI,
 DIVISION TYPE SPARTE ,
 DATE TYPE ERDAT,
 DATE1 TYPE ERDAT,
 int_ui TYPE INT_UI,
 ANlage type anlage,
 SERVICE TYPE SERCODE,
 SERVICEID TYPE SERVICE_PROV,
 SPARTE TYPE SPARTE,
 END OF gx_input1.
GIT_INPUT1 TYPE gx_input1.
LOOP AT git_input1 INTO wa_input1 .
AT NEW int_ui .----
>hERE FIELDS OF wa_input1 ARE TURNED INTO *
EX: wa_input1-ANLAGE =******** AFTER AT IN COMMAND.
END AT
eNDLOOP

In the component overview screen of CO01 I want to disable all the field in screen of table control.I want to make it as output screen only.

Hi all
In the component overview screen of CO01 I want to disable all the field in screen of table control.I want to make it as output screen only.
Thanks & Regards,
Rajib.

Isn't that just exactly what transaction CO02 does? CO01 is for creating production orders so what sense does it make to have it display mode only?
Maybe your goal is to stop then end user changing the component assignment that is automatically detected by the system. If so, personally I think a better starting point would be PP configuration or user authorizations rather than looking to change the screen by whatever method. As we don't know what you are trying to achieve it's hard to offer much more advice maybe all you need is to change transaction to CO02

Use of enhancement to add field in screen

please explain me how to add fields in standard transaction screen by using enhancement 6 in version 6.0 ?

SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen u2013 where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen u2013 so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool u2013 including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton u2018SAP Applicationsu2019. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest u2013 for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number u2013 20 characters
Location 2 u2013 15 Characters.
Model no u2013 20 characters
Location 2 should start with u2018Lu2019.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be u2018CUSTu2019 (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with u2018Lu2019 will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module u2018EXIT_SAPLAIST_002u2019, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module u2018EXIT_SAPLAIST_003u2019, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done u2013 otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton u2018Enhancement Assignmentsu2019 in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to u2018Componentsu2019.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field u201CLocation 2u201D, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything u2013 the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page u2018Generalu2019 of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class u20181000u2019 and click on folder u2018General Assignment of Layoutu2019.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout u2018SAPu2019 cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout u2018SAPu2019 to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder u2018Tab page titlesu2019.
You want to put your custom fields in the tab page u201CGeneralu201D. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page u201CGeneralu201D are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with u201CUu201D padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themu2026save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
I hope you read it all
Thanks and Regards
Santosh K.

F4 help for two fields in screen

hello,
I have two fields in my table control which need F4 help in the screen.
But one F4 search exit is implemented, but it populates only one field.
but, on clicking f4 for one field, it should populate both the fields together.
do help me with this issue...
Can POH in the screen populate up two fields together???

Hi Krithika ,
In addition to checking up the export parameters for the Search healp you will have to define the Search Help attachment also. I'll paste the SAP Help Text below but in Simple terms
You Define a structure with the fields to be returned and define the screen elements based on that structure . So on selection the structure is returned with all values and the screen elements are in referance to structure so all values get posted in screen.
Here is the SAP HELP part
"" From SAP HELP
A search help attachment is an assignment of a search help to a table, structure or data element, causing the corresponding search help to be automatically used to describe the input help process at this field when an ABAP Dictionary field is used in a screen.
You can attach a search help as follows:
1. Attach a search help to a structure or table field: The attached search help is available for all screen fields that refer to the table or structure field. There must be an assignment between the interface parameters of the search help and the fields of the table or structure for this type of attachment. In the input help process, this assignment results in a value transport between the corresponding fields (if they are known at least to the module pool of the screen) and the search help parameters. As for the foreign key definition, you can assign nothing, a constant or any other field (which is then sought in the module pool) to indivdiual search help parameters.
2. Attach a search help to a table: The assigned search help is available for all screen fields for which the table is a check table. There must also be an assignment between the search help parameters and the key fields of the table for this type of assignment.
3. Attach a search help to a data element: The attached search help is available for all screen fields that refer to the data element. If the search help is attached to a data element, an export parameter of the search help must be assigned to the data element. If the user chooses a row of the hit list in the input help, the contents of this parameter are returned in the corresponding screen field. More than one value is not returned when a search help is attached to a data element.
The described attachments only take effect if the field was not yet assigned an input help in the screen definition. Such an assignment can be made with the mechanism PROCESS ON VALUE-REQUEST in the flow logic or by attaching a search help to the screen field in the attribute maintenance screen. A F4 help can also be assigned to the field in the flow logic by using VALUES or SELECT. In the latter case, the input help here behaves as if the table specified under SELECT were assigned to the field as check table.
If more than one of the described mechanisms compete in defining the input help method of a screen field, the first one named will take effect. If none of the described mechanisms is available, the domain fixed values of the field will be used for the input help if necessary. If the domain of the field has no fixed values but has data type DATS or TIMS, the input helps that are assigned to these types are used for the input help. Otherwise there will be no input help available for the field.
A search help attachment always belongs to the definition of the object to which the attachment is made (structure, table or data element). It is also maintained in the maintenance transaction for this object and transported with this object.
REWARD IF USEFUL. It Works for me here..get back if any doubts.

Passing values to hidden fields in screens

Hi ,
I have designed a screen which has i field which is output only, and two fields which are hidden.. the output only field gets populated when i select value from an alv tht pops up on the screen based on certain conditions.. the hidden fields should also be populated than.. but the hidden fields are not getting populated i think..
i have assigned a t-code to this screen,
and i need to call this transaction from another program passing values to all the fields.. i used parameter id for all teh fields, but values are not getting populated in the hidden and display fields. i gets in when i make it input enabled.. but i cannot let users enter values in 1 field, and i do not want users to see the other field.. What do i do???? please give your valuable suggestions. .a ny idea how to correct the issue?
Regards,
Suzie

Hi,
If you want one of the fields to be grey mode you can do that statically in the screen painter or dynamically in the progarm
in PBO
loop at screen
if screen-name = 'TO_BE_GREY_MODE'.
SCREEN-INPUT = 0
ENDIF
endloop
for hidden fields if the screen name and the variable name in the program are same the data transfer takes place but the users cannot see this.
Regards
Ramchander Rao.K

Hiding fields in screen area 031

Similar Messages

Maybe you are looking for