Reg Screen attributes

Hi,
  When i copy a selection screen from a existing program to re use it, the screen copied has normal screen as its screen type and iam unable to change the attribute since selection screen option is disabled.And also when i try to create a new screen with screen number 1000 again the selection screen option is disabled so i get run time error each time i try to execute the program.Can someone help me please.

Hi..,
The screen number 1000 will not be displayed in SE80..
The screen number 1000 is reserved for the Standard selection screen.
This screen is automatically generated by SAP with some ABAP statements. It will not be listed in the Object navigator.
You can create onli user defined screens with numbers other than 1000. These will be listed out in Object navigator.
Plz do remember to close the thread, when ur problem is solved !! reward all helpful answers !!
regards,
sai ramesh.

Similar Messages

  • MM06E005 - how to set screen attributes for custom fields?

    Hi all,
    I have implemented enhancement MM06E005. I have added my custom fields to CI_EKPODB.  I have created and activated all the dynpros.  I modified subscreen 0111 (items) to contain my new custom fields.  I have activated the function exits (016,017,018) for the item screens.  I am able to save data using the new custom fields on subscreen 0111.
    What I am having trouble with is modifying the screen attributes for the new custom fields that I placed on subscreen 0111. I know it should be in exit 016(PBO) and I need to check the action type.  I tried a "loop at screen" but my fields were not there. 
    How do I modify the screen attributes?  Also, can I change the "Tab" text from "Customer Data" to be something else?
    Any help would be appreciated.
    Thanks, Mark

    Hi,
      In the PBO of the screen 0111, create a module. And in that module you can do LOOP AT SCREEN..where the screen elements will be available..
    Thanks
    Naren

  • Change Screen Attributes of Standard Fields on ME22N

    Hello Fellows.
    I'm facing a problem trying to change a screen attribute of a ME22N standard field at Item Detail:
    My requeriment:
    I need to change the Delivery Completed Indicator (MEPO1313-ELIKZ) from Delivery Tab in ME22N, to Display Only, everytime it's flagged on (marked).
    So, something like this:
    - Call ME22N
    - Delivery Completed Indicator marked?
      - Yes: Change it to Display Only
      - No: Leave it openned.
    I was able to change it to Display Only changing it's atrribute at SPRO - Customizing, but I need it only at certain conditions.
    Any idea?
    Thank's.

    Thank you for your reply Weston.
    Since I don't have too much OO skills and I'm new to BADI's, any document explaning how to use a BADI?
    I heard about this BADI, that it can only change custom fields attributes. Have you sure I can use it for standard one's?
    Thank's.

  • How to change activity number screen attribute

    Dear :
    Can I change activity number field to "display" attribute? I find all PS config, but can not change screen attribute only for "activity number" field.

    Hi Jennifer,
    Please follow the steps given below:
    1. Using transaction OK02 create a user profile, preferably by copying from an existing profile
    2. Now go in for detailed screen of the created user profile
    3.Enter status number (you can number them as 1,2,3..),status in short form (like "PROD' for "under production"),
    3.Now select the status created by clicking on the left side and click "object types" at the top. Among the objects listed select "Network Header & Activity"
    4.Go back to the detailed screen and double click the status. Here you select "Change activity / element number" as forbidden.
    Now set this status to your network.
    You can select the status profile by opening the network in CJ20N ->edit->Status->System/User Status, or by assigning the user profile to the transaction in customizing transaction:OPSC
    Reagds
    Muraleedharan.R

  • Upload screen attributes

    I have downloaded the screen attributes for a screeen, now i want the same screen attributes to be applied to another screen. what i did was. i downloaded the screen attributes of that particular screen
    and when i try to upload the same screen attributes, it gives me error saying editing the screen would like to continue.... if i say yes or no then the screen attributes are not copied .
    can anyone explain how to upload the same screen attributes

    Hello MS,
    Go thought the below link u can find the way. I think this is usefull for u.
    http://help.sap.com/saphelp_nw04/helpdata/en/17/5bf1b22ba211d2954f0000e8353423/frameset.htm
    Regards,
    Lakshman.A

  • Setting screen attributes for select-option in subscreen

    Hello SDN Community,  I have researched this extensively in forums and found much helpful information in getting the select-option working in a subscreen.  Also found information that discussed using standard AT SELECTION-SCREEN statements to process the sub-screen with. 
    I encountered problems when that from the LOOP AT SCREEN within the AT SELECTION-SCREEN OUTPUT,  I set the INPUT/OUPUT attributes to zero, the field was still open for input when it displayed.  For when I do this on other fields of my screen, they are "greyed out".
    Has anyone any experience setting field attributes from within loop at screen for embedded select-option subscreen?  Would appreciate any insight you might have.
    Thank you,
    Dean Atteberry.
    P.S.- I put this thru the debugger and I can see the INPUT and OUTPUT attributes getting changed.  But when displays, it is like the change didn't happen.
    Full description of my processing below...
    I have a screen with four radio-buttons.  Under the first radio-button is my embedded subscreen with one SELECT-OPTION for AUFNR.  Under the other three radio-buttons are single fields declared regular way in main screen.
    In my PBO of main screen I have loop at screen that enables/disables INPUT and OUPTUT attributes based on which radio-button is selected.  This prevents confusion from user entering values in fields other than the one the radio-button is selected for.
    For my embedded select-option subscreen, I have an AT SELECTION-SCREEN OUTPUT statement in which I have a LOOP AT SCREEN.  Within that, based on radio-buttons, I either enable or disable the INPUT and OUTPUT attributes for the S_AUFNR-LOW and S_AUFNR-HIGH fields.
    Edited by: Dean Atteberry on Mar 25, 2009 4:39 PM

    >> I think that you are trying to change select options within main screen, whereby it should be
    >> changed in PBO of that subscreen. You said you do it in AT SELECTION-SCRREN OUTPUT which
    >>  will be only applicable for selection screen (I guess your main screen here). Do loop at screen in
    >>  PBO module of this subscreen not in PBO of the selection screen and see if that helps.
    Hi Marcin,  thank you for your reply.  My "main screen" is not my "selection screen".  Please allow me to further clarify...
    My "main screen" has four radio buttons with a subscreen area under the first one and single fields under the others.
    My "subscreen" is auto-generated by Selection-Screen and Select-Options statements which are in my TOP module.
    I call my auto-generated select-option subscreen in my PBO with...
         call subscreen sca_ordr including sy-repid scr_0121.
    and in my PAI with...
         call subscreen sca_ordr.
    In order to do LOOP AT SCREEN for my system-generated select-option subscreen, I use the AT SELECTION-SCREEN OUTPUT event in which to put my loop. 
    When I walk thru this in the debugger, I can see it setting INPUT/OUTPUT fields to zero, but when the screen displays, there are no changes to my subscreen....  Fields should be "greyed out" instead they are open for intput.
    Doing my best to accurately describe in as few words as possible.  Thank you for your ideas!
    Dean.

  • Screen Attributes in Module Pool Programming

    Dear Experts,
    In Module Pool Programming, if we write LOOP AT SCREEN we can see and modify SCREEN-ACTIVE, SCREEN-INVISIBLE and other fields. But where we can modify Data Type and Other Attributes of the field dynamically?
    Thanks in advance.
    Regards,
    Kumar

    Hello Kumar,
    you can not change data type of a screen field dynamically. What you can change is an output length of a field. This can be done changing the value of SCREEN-LENGTH.
    Regards
    Adrian

  • HR Infotype Screen attributes

    Hi
    What attributes are there in the screen code that I can distinguish whether the infotype is currently being edited or displayed. Attribute FCODE is not always filled. I was thinking of checking whether FCODE = 'DIS', but that won't work because in the module from the screen code FCODE is blank. I have seen that if you loop at the screen, the INPUT attribute is set to 0 for when you are in display mode. Is there a better option?
    Thanks
    Corne

    Hi,
    Values for psyst-ioper (actual operation for infotype):
    DISPLAY 'DIS ',
    DISPLAY_NO_LIST 'DIS2',
    MODIFY 'MOD ',
    INSERT 'INS ',
    COPY 'COP ',
    DELETE 'DEL ',
    LIST_DISPLAY 'LIS0',
    LIST_MODIFY 'LIS1',
    LIST_DELIMIT 'LIS9',
    ENQUEUE_RECORD 'EDQ '.
    Hope it helps,
    Regards.

  • Reg:Screen output without connection to user.

    Hi All
    I am having an issue when I open Form 16 application in ess role under benefits and payments  subfolder .
    But I am getting an Critical error as shown below .
    Screen output without connection to user. error key: RFC_ERROR_SYSTEM_Failure.
    Can any please guide me how to resolve this error.
    As its very urgent requirement ..
    Thanks & Regards
    Deepika
    Edited by: deepika_indian on Feb 9, 2012 7:49 AM

    Hi,
    Please check out in the Infotype 105 Sub Type 0001, Is there any user maintained there, As it is
    required.
    I could see a possible problem, in the past we've
    encountered issues like this, but relevant to environments using Central User Administration(CUA). Please refer to SAP Note no:350619. The note makes following changes to the table t77SO by changing the value of TRSPCORR to ''X'' or 'T'. Please verify if the note is relevant to your environment if so kindly apply.
    Please look at this [Help|http://forums.sdn.sap.com/thread.jspa?threadID=1038064] and [Help-1|http://forums.sdn.sap.com/thread.jspa?threadID=1925679]
    Hope This is Help full for you!!!
    Best Regards
    Vijay K

  • Reg : Fillable attribute in adobe form

    Hi all,
    i would like to have a clarification ..
    when i set
    fp_docparams-FILLABLE = 'X'. i am not getting the pdf simply i m getting a error message "ADS : Start time ...."
    and when i set
    fp_docparams-FILLABLE = 'N' i m getting the pdf and able to enter the value in the text field .. but not able to save..
    should i apply any SAP note reg this.. If anybody knows plz let me know..
    Rgrds.

    Please ignore this Question.. this already runs in another thread..

  • Change PNP standard selection screen attributes

    Hi experts,
    I need to change the standard PNP selection screen parameter BUKRS into "obligatory".
    I know it can be done for all reports using PNP through SPRO, but I need it only for one customer report.
    Best regards,
    A. Cepa.

    You can hide the standard field on the screen using this -
    INITIALIZATION.
    LOOP AT SCREEN.
    IF screen-name = 'PNPBUKRS-LOW'.
    screen-active = '1'.
    screen-input = '0'.
    screen-invisible = '1'.
    ENDIF.
    IF screen-name = 'PNPBUKRS-HIGH'.
    screen-active = '1'.
    screen-input = '0'.
    screen-invisible = '1'.
    ENDIF.
    MODIFY SCREEN.
    ENDLOOP.
    Regards,
    Amit

  • Reg Navigational Attribute in Query

    HI
    Iam having a strange problem,I wasnt to include a channel levl that is a navigable attribute to customer in my query.The query is reporting from an multi provider.I find that the navigable attribute is checked in my Infocube ,but its not appearing in my query to drag it in the columns.
    Is it because it is reporting from Multiprovider should it be generated.If so how?
    Thanks
    BR

    You need to make it as navigational in the multiprovider definition too. Navigational attr of underlying cubes are not automatically included in the multi. You need to manually include them as you do for the chars and KF's

  • Reg: visual attribute for list item

    hi frs,
    i have created a listitem i have used
    APP_ITEM_PROPERTY2.SET_PROPERTY('list4',VISUAL_ATTRIBUTE, 'color');
    in keylistval Trigger.
    when i select one particular item in the list it should have background color mentioned in the VISUAL_ATTRIBUTE 'color'.
    but what is happening is when i select one particular item visual attribute is set to all items in list.
    why it is so?
    how can i solve this problem.
    any one help pls.
    Thanks
    Rajesh

    1- I have three list box on the form as well so whether post-text-item works over therei have no issues with this and it is working fine in my forms list box
    2- and i have 3 datablock among which 2nd and thid datablock is multirecord datablock where i set current record visual attribute so what is the behaviour @ run time either current record Visual attribute override current item VA or it works fine
    it is working perfectly in multi record also..you need to remember in post text trigger use the same visual attribute used for current record visual attribute

  • Exit for Modifying screen attributes during ME22N

    Hi Experts,
    I need to make some fields output only at item level in transaction ME22N i.e. during PO change. Is there any exit or BADI available for that.
    Regards

    > Hi Experts,
    >
    > I need to make some fields output only at item level
    > in transaction ME22N i.e. during PO change. Is there
    > any exit or BADI available for that.
    >
    > Regards
    This is mainly config.
    Check in SPRO - IMG
    Materials Management > Purchasing > Purchase Order > Define Screen Layout at Document Level 
    Also these BAdis are available:
    ME_PROCESS_PO_CUST - For Custom logic in Enjoy transactions
    ME_GUI_PO_CUST - For Additional Custom screens in ME2xn
    Read the documentation, it will help.
    Also, read the config section about enhancements in Purchasing using old enhancement technology. See below.
    OSS is also a good place for documentation. OSS 496083.
    Good luck!
    Leonardo De Araujo
    Develop Enhancements for Purchasing
         In this step, you develop enhancements for Purchasing.
         The following SAP enhancements are available for the Purchasing area:
         o   AMPL0001
             User subscreen for additional AMPL data (Manufacturer part number)
         o   LMELA002
             Adoption of batch number from shipping notification at time of
             posting of a goods receipt
         o   LMELA010
             Incoming shipping notification: adoption of item data from IDoc
         o   LMEQR001
             User exit for source determination
         o   M06B0001
             Role determination for release of requisitions
         o   M06B0001
             Changes to communication structure for release of requisitions
         o   M06B0003
             Number range and document number
         o   M06B0004
             Number range and document number
         o   M06B0005
             Changes to communication structure for overall release of purchase
             requisitions
         o   M06E0004
             Changes to communication structure for release of purchasing
             document
         o   M06E0005
             Role determination for release of purchasing documents
         o   ME590001
             Grouping of requisitions for PO split in transaction ME59
         o   MEETA001
             Determination of schedule line type (backlog, immediate requirement,
             forecast)
         o   MEFLD004
             Determination of earliest delivery date for checking at time of
             goods receipt (PO only)
         o   MELAB001
             Generation of forecast delivery schedule: realization via creation
             profile
         o   MEQUERY1
             Enhancement for document overview ME21N / ME51N
         o   MEVME001
             Calculation of default GR quantity and over/underdelivery tolerances
         o   MM06E001
             User exits for inbound EDI messages and outbound purchasing
             documents
         o   MM06E003
             Number range and document number
         o   MM06E004
             Control of import data screens in purchase orders
         o   MM06E005
             Customer fields in purchasing documents
         o   MEREQ001
             Customer's own data in purhcase requisitions
         o   MM06E007
             Change document for requisitions when converting into POs
         o   MM06E008
             Monitoring of contract target value in case of release orders
         o   MM06E009
             Relevant texts for "Texts exist" indicator
         o   MM06E010
             Field selection for vendor address
         o   MM06E011
             Activation of requisition block
         o   MM06L001
             Exits for determination of ratings in vendor evaluation
         o   MMAL0001
             ALE source list distribution: outbound processing
         o   MMAL0002
             ALE source list distribution: inbound processing
         o   MMAL0003
             ALE purchasing info record distribution: outbound processing
         o   MMAL0004
             ALE purchasing info record distribution: inbound processing
         o   MMDA0001
             Default values for delivery addresses
         o   MMFAB001
             User exit for generation of releases
         o   MRFLB001
             Control items during release creation
         o   LWBON001
             Enhancement of LIS update through extension of the communication
             structure MCKONA (business volumes and rebate income)
         o   LWBON003
             Change settlement data for end-of-period rebate settlement before
             creation of settlement documents
         o   LWSUS001
             Customer-specific source determination in Retail
         Activities
         1.  Either create a new project or use an existing one and then enter
             the enhancement.
         2.  Activate the project
             Your enhancement will only become effective after activation.
         Further notes
         In contrast to modifications, enhancements are basically
         release-insensitive since they are not implemented in the SAP original
         but in a name range that is reserved for the customer.
         The general procedure for creating enhancements can be found in the
         enhancement transaction at Help -> Application help.
         If you want to display the documentation for an enhancement, choose Goto
         -> Documentation in the enhancement transaction.
    Return ->
         Application

  • Reg : Screen Flow and Progress States /Progress Bar

    Hi All,
    I've used 'Screen Flows' for the user to navigate to different screens based on the user input.
    By doing so, I'm not been able to use Progress Stages or Progress Bar features :(
    If i remove the screen flow, then Progress Stages/ Progress Bar shows up.
    But as per the screen order, it shows up all the screens, even if I don't want to display it to the user on certain conditions.
    I'm using OPA 10.4.
    How do i display the Progress Stages/ Progress Bar ,using the screen flow..
    Any help would be greatly appreciated
    Regards,
    Kumar

    Only screen orders support progress stages. Screen flows do not.
    The recommended approach is to organize the screens into folders. It is only the top-level (screens or folders) that are then shown as the stages.
    Davin.

Maybe you are looking for