Display mode in me23n

Hi,
I have added a new field in me23n transaction.Its coming in change mode.iam using user exit MM06E005 for adding the new field.How can i change the field to come in display mode?Can anyone suggest the function module in this exit where can i code.
Thanks,
Aparna.

I made i_no_screen value 'X' but its not working.
When i create a PO using me21n,the value of the new field is getting saved in EKPO table.But when i use ME22N,ME23N,the value which is been saved in the EKPO table should get displayed in that field,but its not happening.
Also,the new field is coming in change mode in ME23N.
Which function module exit can i use here to do the above changes.
Thanks,
Aparna.

Similar Messages

  • Unable to capture value inside parameter T_LFBK of FK03 in display mode

    Hi Experts,
    I have to trigger a mail whenever there is a change in fields that are captured in parameter t_ffbk.
    However i am unable to capture the the screen values for this parameter as FK03 is in display mode.Please tell me how can i capture the screen field values in parameter T_LFBK.
    <Point offer removed by moderator>
    Thanks in advance.
    Edited by: Vinod Kumar on Jul 28, 2011 5:48 PM

    Hi Experts,
    I have to trigger a mail whenever there is a change in fields that are captured in parameter t_ffbk.
    However i am unable to capture the the screen values for this parameter as FK03 is in display mode.Please tell me how can i capture the screen field values in parameter T_LFBK.
    <Point offer removed by moderator>
    Thanks in advance.
    Edited by: Vinod Kumar on Jul 28, 2011 5:48 PM

  • Apple Mini DVI to DVI Adapter to connect Win7 tower to iMac / Target Display Mode

    I currently run Windows on bootcamp on the iMac (Mid-2011), although the tasks I perform (3D modelling, rendering and such) cause the Mac to get very hot, and as a result hae a slight burn mark on the LED LCD screen.
    I am buying a Windows machine, and am to uninstall bootcamp and use the Mac purely for OSX, but use the iMac screen as a monitor for the tower using Target Display Mode. My issue is - the Windows 7 tower only has DVI output. And as I understand, the Mid-2011 iMac only supports Target Display Mode via a thunderbolt cable.
    My question is - Will the Apple Mini DVI to DVI adapter allow me to connect the DVI-only tower to the iMac? Thanks in advance x

    Oh, I should mention also that the iMac is the 27" model. Mid-2011 3.4Ghz Intel Core i7 with 4GB RAM and 1TB Harddrive. And ATI HD5450 1GB Graphics.

  • Can windows 8.1 in boot Camp display in target display mode on an IMac?

    I have given up on Windows 7 running in Boot Camp on my 15" MacBook Pro and displaying it on my 27" IMac via thunderbolt and Target Display Mode. 
    The FAQ concerning Target Dsiplay Mode farily clearly says Windows 7 won't work. 
    But it  does not say Windows 8.1 will or will not drive Target Display Mode via thunderbolt.
    see:  http://support.apple.com/kb/HT5219, question 29
    Has anyone found that running Windows 8.1 in BootCamp on a MacBook Pro Retina mid 2012 will display via a thunderbolt cable in to Target Display Mode on a late 2013 IMac 27"? 
    I don't want to go to the trouble of installing Windows 8.1 and trashing my otherwise functional Windows 7 Boot Camp installation unless it is going to display properly on my late 2013 27" IMac running OSX 10.9.3 via thunderbolt.
    Thanks in advance!

    no, tdm doesn't work under bootcamp regardless of which windows is being used, imho i don't think it will ever work under bootcamp

  • IllegalStateException when changing display mode of JFrame

    My application has an information console inside a JFrame. The console is continually updating and repainting.
    I let the user drag this window wherever they want, resize it how they want, etc. I also give them the ability to select one of three display modes:
    - "Decorated Window"
    - "Undecorated Maximized Window"
    - "Undecorated Fullscreen Exclusive Window"
    The toggling between modes normally works well, but occasionally an "IllegalStateException: Buffers have not yet been created" is thrown by (from what I can tell), a component on the console that's trying to be repainted.
    Seems obvious to me that something doesn't like the fact that the JFrame has been disposed for an instant and can't deal with it appropriately. Question is, what the hell can I do about it?
    I believe everything continues fine despite the exception (although I have a hard time reproducing on my system), but still, it's a wart and I'd like to chop it off.
    Here's my code for changing the window mode.
    public void setDisplayMode(Component parent,
             ConsoleDisplayMode newDisplayMode) {
         GraphicsDevice device = this.getGraphicsConfiguration().getDevice();
         int state;
         switch (newDisplayMode) {
         case DisplayAsDecoratedWindow:
             // Add the decorations
             this.dispose();
             this.setUndecorated(false);
             this.setVisible(true);
             device.setFullScreenWindow(null);
             // De-iconify
             state = this.getExtendedState();
             state &= ~JFrame.ICONIFIED;
             this.setExtendedState(state);
             // Minimize
             state = this.getExtendedState();
             state &= ~JFrame.MAXIMIZED_BOTH;
             this.setExtendedState(state);
             break;
         case DisplayAsUndecoratedWindow:
             // Remove the decorations
             this.dispose();
             this.setUndecorated(true);
             this.setVisible(true);
             device.setFullScreenWindow(null);
             // Make sure it is de-iconified
             state = this.getExtendedState();
             state &= ~JFrame.ICONIFIED;
             this.setExtendedState(state);
             // Maximize
             state = this.getExtendedState();
             state |= JFrame.MAXIMIZED_BOTH;
             this.setExtendedState(state);
             break;
         case DisplayFullScreenExclusive:
             if (device.isFullScreenSupported()) {
              int choice = JOptionPane
                   .showConfirmDialog(
                        parent,
                        "Warning:\n\n"
                             + "This mode is meant for users with a multiple-monitor configuration.\n"
                             + "In this mode, the console controls the graphics device exclusively\n"
                             + "and other windows (such as the other TM windows and dialogs) cannot\n"
                             + "be displayed over the console.\n\n"
                             + "If you have a single monitor, use the mode called\n"
                             + "\""
                             + ConsoleDisplayMode.DisplayAsUndecoratedWindow
                                  .toString() + "\".\n\n"
                             + "Continue with this mode?",
                        "Confirm full-screen mode",
                        JOptionPane.YES_NO_OPTION,
                        JOptionPane.WARNING_MESSAGE, ChipIconFactory
                             .getWarningChipIcon());
              if (choice == JOptionPane.YES_OPTION) {
                  this.dispose();
                  this.setUndecorated(true);
                  this.setVisible(true);
                  state = this.getExtendedState();
                  state &= ~JFrame.ICONIFIED;
                  this.setExtendedState(state);
                  device.setFullScreenWindow(this);
             } else {
              JOptionPane
                   .showMessageDialog(
                        null,
                        "Your graphics device does not support full-screen mode",
                        "Unable to display in full-screen mode",
                        JOptionPane.ERROR_MESSAGE, ChipIconFactory
                             .getErrorChipIcon());
             break;
        }

    jneau wrote:
    My application has an information console inside a JFrame. The console is continually updating and repainting.
    The toggling between modes normally works well, but occasionally an "IllegalStateException: Buffers have not yet been created" is thrown by (from what I can tell), a component on the console that's trying to be repainted.Are you certain all your interaction with the GUI happens on the EDT?

  • Output types are not getting displayed in Outbound Delivery in Display mode

    Hello,
    The actual requirement is that output types should get attched to the outbound delivery when we do GI(Good Issue) on the outbound delivery.
    So, I have created an outbound delivery and did GI on it through IDoc. But, I can not see output types on the delivery (To see output types, go to Extra -> Output -> Header in VL03N) in the display mode. However, I can see in change mode (VL02N).
    Could you please suggest the solution for this?

    Hi sreeram,
    go to crm -> transactions -> basic settings -> define transaction types
    copy default email cx03 and create new zemail.
    assign that zemail to bus2000126 business activity.select the business activity and click on customizing header.assign the category email. click on channel. maintain the channels 1)GUI crm webclient UI, 2)ICW Interaction center webclient.
    save the changes.
    go to crm -> transactions -> basic settings -> settings for activities -> maintain categories, goals, priorities -> click on assign categories to transaction types.
    assign the category email(which you have assigned above) to the transaction type zemail.
    even check maintain categories as well
    click on maintain categories -> check 401 email assigned to class G email.
    Regards
    Krishna

  • I am Not Getting a Additional Tab in ZMIGO in Display mode

    Dear Gurus ,
                          I have Impelemented a Migo Badi and Created a Additional Tab in MIGO . The Additional Tab is getting Displayed in Create Mode but the same is not getting in Dispay Mode . Can Any Body help me for the same .
                                      I have Created two screen for the same .
    0001 is for Created and 0002 is for Display mode . And in PBO i rave checked the condition for the same which i am pasing below for your refrence . Can any body please help me .
    READ TABLE gt_scrn_active INTO ls_scrn_active
                                WITH KEY line_id = i_line_id .
      CHECK ls_scrn_active-active EQ 'X'.
    External subscreen:
    The content of global field G_NO_INPUT (set in method MODE_SET) will
    influence the number of external subsreen:
      IF g_no_input IS INITIAL.
        e_cprog   = 'SAPLZCFG_JEWELLERY'.
        e_dynnr   = '0001'.                     "External fields: Input
        e_heading = 'Additional Unit'(004).
      ELSE .
        e_cprog   = 'SAPLZCFG_JEWELLERY'.
        e_dynnr   = '0002'.                     "External fields: Input
        e_heading = 'Additional Unit'(004).
      ENDIF .
    Regards
    S.B.Shankar

    hi,
    just i basice ? have you checked the status of BADI is it implemented.
    Atul

  • Field value is not getting populated in Display mode

    Hello All,
    I have created a custom drop down field in the DEAL component through EEWB. From the GUI, I could able to select a value form the drop down list field and save it.
    In DISPLAY mode,  the value is not showing but when I change the screen to EDIT mode then the value is getting populated.
    Please advise.
    Thanks in advance.

    When debugging the set_property method I see the following code:
    If ME->IS_CHANGEABLE( ) = ABAP_TRUE and                  "CLASS=CL_CRM_BOL_ENTITY
               LV_PROPS_OBJ->GET_PROPERTY_BY_IDX( LV_IDX ) ne IF_GENIL_OBJ_ATTR_PROPERTIES=>READ_ONLY
    *     change value
          <VALUE> = IV_VALUE.
    In display mode none of these conditions are fulfilled, meaning value is not set.
    So, is there a way of avoiding this behavior?

  • Why not all fields dimmed or show in display mode after system status TECO and CLSD for Project

    Dear All,
    When Sets the system status TECO or even CLSD all fields for WBS Elements are not goes to Display mode. User can still edit them or change then.
    The fields are:
    1. WBS Element Description, technical name: PRPS-POST1
    2. Person responsible number, technical name: PRPS-VERNR
    Other Progress and Customer enhancement tab pages for WBS Element all fields there also editable in TECO and CLSD system status.
    The client do not want to set LOCK system status for master data option.
    Is there any enhancement or standard way of doing that?
    Regards
    Saqib Usman

    Dear Saqib,
    Its a standard behavior of the system. In CLSD status, transactional data like Procurement gets restricted along with WBSE no and its scheduling details. But it allows to you change like WBSE desc./Responsible person.
    Also go thru the below link for clarification of WBSE system status:
    http://help.sap.com/saphelp_470/helpdata/en/ee/41f82246ee11d189470000e829fbbd/content.htm
    For locking all master data, as above experts suggest, you should use MDLK/LKD.
    Regards
    Shishir

  • Performance Issues with Debugging even in Display Mode

    Hi not certain if this would sit in Security, ABAP or Basis, but lets start here as it is security related.
    S_DEVELOP with any activity on DEBUG on a production system is a concern, but what are the performance related issues when a super user has to go into debug in display only on a production system because of a really complex issue?
    I've heard in the past of a scenario where system performance was impacted, and we have notes around the allocation of S_DEVELOP display DEBUG access to this point. (I've summarised these below)
    The risk with debug is associated with the length of time that the actual debugging process is being performed.
    u2022     Work processes are dedicated solely to the users for the duration of the debug. If these are being performed for a long time, these can cause issues with not enough work processes being available.
    u2022     It can cause DB2 locks. If the debug session last awhile, DB2 locks are not released. This impacts the availability of tablespaces, thus, affecting various transactions running across the system.
    Even with these concerns, security will often get asked for debug display access.
    As security is about risk identification, assessment and then controlled access what do other organisations do?
    Options (not exhaustive) are "No Debug ever" or "Debug display only via a fire fight or super user on a time limited basis".
    We are currently in the "debug display only via fire fight" camp, but would like to canvas opinion on this.
    As one of the concepts of security is Availability of data (and to an extent ensuring the systems are up and running) do the performance risks push the security function to the "No Debug Ever" stance.

    If you need to debug in production, then 9 times out of 10 you need to do root-cause analysis: The developer is the problem.
    Writing sloppy code and not testing properly should not be an excuse for debugging in production.
    But of course, there are exceptions even when you do try to keep them to a minimum.
    To add to Jurjen's comments, also note that the debugger only has a limited capability of doing a rollback. So you can quite easily and unintentionally create inconsistencies in the system - also in display mode - which is an integrity problem, and typically more critical than availability problems or even potential confidentiality concerns.
    Cheers,
    Julius
    Edited by: Julius Bussche on May 15, 2009 10:50 AM

  • TS3775 Hi I am trying to connect my mba mid 2011 with an imac 27" 2011 with target display mode tdm. When I am using a thunderbolt cable nothing will work. When I use a minidisplay cable, both screens turn blue but eventually nothing happens. What is the

    Hi I am trying to connect my mba mid 2011 with an imac 27" 2011 with target display mode tdm. When I am using a thunderbolt cable nothing will work. When I use a minidisplay cable, both screens turn blue but eventually nothing happens. What is the problem

    Your answer is likely in Target Display Mode: Frequently Asked Questions (FAQ) - Apple Support If you are familiar with this document, please re-read it and I suspect you may find something you either missed or are doing incorrectly.

  • How can I use my 27" iMac (2010) as an additional display to my Windows 7 PC (target display mode)?

    So I have purchased a windows machines so that I can play all my favourite games on, and it's not so much a problem rather I have a 27" iMac that I would like to use as an additional monitor for said games.
    I have had a look at this article on using the iMac as a display for another computer and things looked promising. I think I need a bit of help getting there though as I can't find definitively anything online to tell me exactly what I need. Most stuff talks about connecting other Apple computers that have mini display ports.
    My PC's video card is an nVidia Geforce GTX 650 Ti that sports 2 DVI ports and a mini HDMI port (adaptor to full HDMI was included). The iMac has a mini display port. I went out and got a HDMI cable and Moshi Mini DisplayPort to HDMI Adapter (with audio) to try to use the iMac as the additional display. I connected the PC with [a generic] HDMI cable to the adaptor which ran to the iMac and went through the appropriate steps (ie. pressing CMD + F2) to initiate target display mode. Nothing happened.
    I have read that other people with different situations tried an SMC reset, but this didn't work for me either.
    At this stage I wanted to see if the DVI port would do anything, or perhaps looking at a particular kind of HDMI cable, but wanted to see what the community can offer up as advice.
    Any assistance would be greatly appreciated.
    Thank you.

    Hi,
    have a read here http://support.apple.com/kb/HT3924
    Regards
    Stefan

  • IMac 27" Target DIsplay Mode + Answer to Windows 7 Boot Camp Install

    First, I'd like to address the handful of complaints I've come across about installing Windows 7 via Boot Camp on the new 27"iMac.
    The issue of the screen going blank when almost done has an easy albeit annoying answer. Simply connect the iMac to an external display, I used a small vga lcd with the Mini DisplayPort to VGA adapter. When the iMac's screen goes black the external lcd will continue, and when Windows 7 starts up it will download the updated ATI drivers. From there alls well.
    Second, my problem.
    Target Display Mode is a great feature. It worked great when I first used it, and it works great now except for the fact that the Command+F2 button combination stopped working. I have to manually unplug my MacBook Pro in order to get my iMac's original screen up. At first Command+F2 would allow me to switch back and forth, and now it does nothing.
    Any suggestions?

    Well, the usual first things to try for a display-related issue are
    Reset PRAM
    http://support.apple.com/kb/HT1379
    and of that does not help, reset SMC
    http://support.apple.com/kb/HT1543
    which is basically unplugging the iMac from power and reconnecting it following the precise procedure.
    Note: After resetting PRAM, you should go to System Preferences +Startup Disk+ pane to make sure your internal drive is selected (highlighted) as the startup disk.

  • Target Display Mode - Connecting pre-Thunderbolt Macbook Air to Thunderbolt iMac.

    I want to use Target Display Mode in order to display my late-2010 Macbook Air (pre-Thunderbolt) to a Thunderbolt-based iMac. Is there an adapter solution to connect, say, a mini display port + USB port on the MB Air to the iMac Thunderbolt port, such that TDM would work?

    Depends upon the situation.  Take a look at this blog:
    http://blog.macsales.com/10899-target-display-mode-and-thunderbolt

  • Target Display Mode not working iMac 27(2012) Bootcamp to iMac 27(2013)

    Hi All,
    I recently purchased an iMac 27" 2013 which replaced my iMac 27" 2010.
    ===============
    PREVIOUS SETUP
    ===============
    (1) iMac 27" 2012 - Running Windows 8.1
    (2) iMac 27" 2010 - Running OS X Mavericks
    (1)+(2) were connected with a Mini-Display-Port cable.
    (1) was using (2) as external display while (2) was set to Target Display Mode using CMD+F2
    ==============
    CURRENT SETUP
    ==============
    (1) iMac 27" 2013 - Running Windows 8.1
    (2) iMac 27" 2012 - Running OS X Mavericks
    (1)+(2) are connected with Thunderbolt cable.
    (1) can't use (2) as external display anymore becuase CMD+F2 has no effect anymore on (2) in this scenario.
    If (1) and (2) are both running OS X all works as expected.
    I am aware about the support hint from Apple where they state TDM is not working under Bootcamp.
    And I agree, while booted into Windows Bootcamp this machine can't serve as external display. Makes sense because TDM is baked into OS X display drivers.
    Anyone had the same experience and came to a soltuion?
    Thanks,
    Martin

    "Apple has no plans to implement a client driver for Windows since there is no Thunderbolt SW stack available for Windows like there is for Display Port."
    That is a little bit funny since Gigabyte and other big companies have said that 2014 is the year that they are going to implement Thunderbolt in many motherboards.
    "GIGABYTE 7 series motherboards are the very first to offer fully certified dual onboard Thunderbolt™ ports. Capable of connecting up to 12 devices plus 3 digital displays simultaneously with breathtaking data transfer speeds that can transfer 1TB of data in only five minutes, GIGABYTE Thunderbolt™ motherboards offer the fastest connection interface on the desktop PC."
    Have you asked Apple about that? I dont understand why Apple is crippling Thunderbolt on their devices...

Maybe you are looking for