Component Update/Display mode ... wierd behavior.

Hi,
I've a component having a effective dated record. and the component is available in all modes (Add , Update/Display , Correction).
When am in Update/Display mode and effective date is 01/01/1900 and i change something on the page and hit save .. it correctly gives me an alert window saying cannot change history records.
However... When am in Update/Display mode and effective date is any date other than 01/01/1900 and i change something on the page and hit save .. it saves without an alert :(.
I even tried winmessaging %mode it stays at U.
any idea how to correct this behavior? any help on this is appreciated.
Thanks in advance!
Kaushik.

Kaushik R wrote:
Hi,
I've a component having a effective dated record. and the component is available in all modes (Add , Update/Display , Correction).
When am in Update/Display mode and effective date is 01/01/1900 and i change something on the page and hit save .. it correctly gives me an alert window saying cannot change history records.
However... When am in Update/Display mode and effective date is any date other than 01/01/1900 and i change something on the page and hit save .. it saves without an alert :(.
I even tried winmessaging %mode it stays at U.
any idea how to correct this behavior? any help on this is appreciated.
Thanks in advance!
Kaushik.So, the 1900 row you changed was an already existing row??
and the other rows on the page..did you add them or are you trying to update an existing row..
If you added those rows, its perfectly normal behaviour.. books excerpt below
Action
Rule
Update/Display - Retrieves only current and future rows. You can change future rows but not current rows_. You can also add a new current row.
Include History - Retrieves all rows. However, you can modify future rows only. You can also add a new current row.
Correct History - Retrieves all rows and allows you to change or correct any row and insert new rows regardless of the effective date or sequence number.

Similar Messages

Determining Edit/Display Mode from Within Freestyle Component

I am new to FPM. We are running ESS.
I have enhanced a new Web Dynpro Component onto an Edit page of an OVP (as a Freestyle Component).
I want the new WDC to behave differently based on the mode I am in.
How, from within the new WDC, can I tell if I have entered the Edit page in Edit (pencil) or Display mode?
Thanks...
...Mike

Hello Mike,
Firstly, welcome to the wonderful world of FPM
Well, usually with FPM, you have an Edit (or Read-only) button in the top, underneath the title (Identification Region, IDR). This, being standard, has some standard FPM events behind it.
In your freestyle WD component, you implemented IF_FPM_BUILDING_BLOCK interface, and with it you have some additional methods in your COMPONENT CONTROLLER, such as FLUSH, PROCESS_EVENT, and so on...
In your PROCESS_EVENT method, you can basically catch all FPM events at application level. Usually you have a big CASE, something like:
case io_event->mv_event_id.
     when ...
     when 'FPM_EDIT'. "you can find some constants behind CL_FPM_EVENT=>GC... Right now I'm not sure how it's called exactly. But it's advised to use this constants!
          You can write your code here in order to change the behavior, basically, you can do whatever.
          also, it's the same with 'FPM_READ_ONLY'
     when others.
          return.
endcase.
I strongly recommend you download the latest version of FPM Cookbook, or the one that is suited with your SAP NW version.
FPM Developer's Handbook SAP NetWeaver 7.03/7.31 SP4
Hope I made things a little more clear!
Tudor

SAP Cloud SDK : Make Display mode when open Embed Component in Account TI screen

Hi Experts,
I have created the custom business object and assign some fields into it.
I have also assign some custom action into this custom business object. After that i have created the Embed component and and configured into Account_TI screen and its display data.
Now when I open Any Account and go to that newly embed component in silverlight 2 options comes ( Save and Cancel ) to remove this options or to make display mode by default I have followed the below steps:
1) Open Embed Component into UI designer.
2) Go to Properties Window.
3) In the top from the dropdown list select embed component.
4) In the Property go to Configuration --> WorkProtectRelevant equal to false.
5) After save and activate and check but still getting ( Save and Cancel ) option in embed component
Is there any other solution or any other settings require to remove this ( Save and Cancel ) option.
Regards,
Mithun

Hi Brad and Sumeet,
Thanks for you reply on this post.
In my requirement we do not want to save record anymore.
Also my scenario : We have consuming the on-premise web service into c4c we have created the custom business object ( Not Screen) and based on this custom business object we have created the embed component and design the screen to embed with Account_TI.
We have Read the Account ID from Account _TI screen and assign to embed component element Alternative key AccountID.
We have created of configured the embed component Inport to Read and Assign the Account ID as below:
My Custom business object :
businessobject ECC_recordBO {
[AlternativeKey] [Label("Customer Number")] element AccountID : BusinessPartnerInternalID;
element CtLimit : LANGUAGEINDEPENDENT_LONG_Text;
element AvailCLimit : LANGUAGEINDEPENDENT_LONG_Text;
element AccCurrency : CurrencyCode;
action ViewAcc;
My embed component InPort event :
ReadEvent
In ReadBOEvent I have add below actions:
BO Operation
Condition
And under the condition I have use the below actions :
To create BOOperation
Second DataOperation as below :
Assign AccountID from Account_TI to AccountID of embed component.
Also once the user come into the Account_TI screen and go to embed component first its in display mode and when he click on any action under embed component its in edit mode but we do not want to save data anymore.
Regards,
Mithun

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?

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

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.

How to set "display mode" from external keyboard

I have an EliteBook 8570p in a docking station, with an external monitor and keyboard attached.
I typically have my display mode as "duplicate", with the same thing showing on both my laptop screen and external monitor. I use the external monitor as the main screen. This might be uncommon, but I prefer it this way. I've been working this way for quite a while.
I very recently started using MS PowerPoint 2013. Today I discovered an annoying bug with this combination. I was in "slideshow mode" for a pptx I was working on, and I pressed ESC to get back to editing the doc. What happened was that the external monitor just showed my background wallpaper, and the laptop screen showed the normal display, along with my background wallpaper. I then had to slide over to my laptop keyboard and press Fn-F4 and set it to "Duplicate", and that restored my external monitor display.
I'm definitely going to pursue this weird behavior with PowerPoint, but I'm going to assume out of the box that this will be difficult to change. What I'd like to get from this forum is simply a quicker way to restore the "Duplicate" display mode. Is there a keyboard shortcut I can use from my external keyboard to change the display mode? There's no "Fn" key.

Although I'd still like to get an answer to this, my original problem has been solved, as I was able to disable the feature in PowerPoint 2013 that mucked with my display mode (turn off "Use Presenter View").

How to activate Target Display Mode on iMac 27", Late 2009?

Hi all,
I'm trying to use my iMac as a display for my PC. Unfortunately I can't activate the iMac's Target Display Mode (TDM) through a DVI-to-miniDisplayPort cable.
As far as I know, the TDM exists on my iMac (27 inch, Late 2009).
I am following these steps:
(1) start the iMac,
(2) start the PC,
(3) press Cmd+F2,
but nothing happens on the iMac (as if I didn't press anything).
The PC's DVI output works on another screen, though.
Here are my settings:
- iMac: 27 inch, Late 2009, 2.8 GHz Intel Core i7 with miniDisplayPort, OS X 10.8.4 (12E55)
- PC: Gigabyte's GTX 770 graphic card with DVI-I output, Windows 8 fully updated
- between the two: DVI-D cable plugged into Apple's DVI-to-miniDiplayPort adapter
Any advice?
Thanks a lot :-)

Please very carefully read:
support.apple.com/kb/ht3924
In it you will see that TDM only works on a late 2009 iMac in Mini Display Port to Mini Display Port, no other configurations will work. If your iMac is an early 2009 iMac (please check the Tech Specs for each on Apple's website) TDM is not supported on that model.

Fields not greyed out in display mode in screen exit

Hi all,
i am working on an screen exit for CJ02 transaction. the values in the customer subscreen are getting updated in database and even it is reflecting in fields when viewed again. the problem is that in display mode (CJ03) the fields are still editable. though there is no save button, but the fields should be greyed out.
i have tried to modify screen using LOOP AT SCREEN in the function exit provided in PBO.....but it is not picking the subscreen.
please provide any solution as soon as possible.
thanks in advance

In the PBO in your screen exit:
IF sy-tcode EQ 'CJ03'.
LOOP AT SCREEN .
if screen-name 'your field'
screen-input = 0.
screen-output = 1.
MODIFY SCREEN.
ENDIF.
endif.
what enhancement are you using?
bye

Brightness iMac in target display mode: who has it working in 10.6.8?

"With Target Display mode, you can use your iMac (27-inch, Mid 2010) or iMac (27-inch, Late 2009) with Mac OS X as an external display.": http://support.apple.com/kb/ht3924 . "Use the keyboard of the 27-inch iMac to adjust display brightness and sound volume and to control media playback of applications running on the 27-inch iMac in Target Display mode."
This used to work perfectly for me. But under 10.6.8, the brightness control stopped working. Sound and media control still work as expected. I posted before on this.
Now I know more people are experiencing this problem... I am looking for people who DO have it working under 10.6.8!
I'm looking for anything I can do to get it to work, maybe the info from people who have it working gives me some clues.
Lion is just around the corner. Please let me know if Lion fixes this problem for you.
Thanks!
Maarten

I'm using two 27" imacs and one of them is still on 10.6.8 one has been upgraded to Lion just now.
I thought it was the Lion update which caused this issue for me because I installed 10.6.8 on both of them today as well.
Now I can't adjust the brightness in target display mode on either 27" imac.... worse that that it sets it to full brightness too.
I don't know of I want to try to go back to before 10.6.8 with time machine, talk about gutted ?
can you use monitor calibration as a work around ?
I found TS3919 but it doesn't work BTW , it says to set the brigthness before entering target display mode..
Simon

Invalid Token while viewing Slide Show Component in Design Mode

Hi Guys,
I am having an issue where my SWF files that appear in a slide show component are displaying an invalid token error while in design mode in Xcelsius. When I export the SWF file to Infoview, this error flashes on the screen for a second before the logon token is passed and the child SWF is loaded.
I am trying to find a way to solve my issue so the invalid token error message does not appear and therefore does not get flashed to the user before the file actually loads.
I downloaded Fix Pack 1 for SP3 because there was a line in the fixed issues detailing:
"An Invalid logon token message appeared in Infoview when you viewed Flash objects (SWF files) that contain a QaaWS or Live Office connection."
"This issue has been resolved".
It is still happening even with FP 1 installed.
Has anyone ever encountered this issue before and found a solution for it.
Thanks in advance!!
- Anthony

Ok, I found out it has definitively something to do with the "Design mode could not load swiz-framework-1.0.0-RC1.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)" warning. This somehow affects the loading of the mx:Image.
Recompiling the SWC might work with the swiz swc, but there are more swc's giving this error like the google maps swc which does not have the source avalable freely.
This is a real pain as I like to use a mockup image in Design Mode to place components exactly as provided by the design team.

Broken Graphics card Target Display mode

I have a 2009 iMac that now has a faulty graphics card, the computer crashes once photoshop runs.
I don't have the mac at the moment to test, but could I still get target display mode to work?
How well does the mac need to run before TDM can work?. If I power it up, sometimes it won't get any further than the apple logo, can it work then?
Thanks
Matt

I purchased a Belkin AV360 and it did not work with Target Display Mode on my new mid 2011 iMac.
After a bit of searching on why it didn't work I've found all sorts of articles on this issue with older display port devices not working with target display mode on the new Thunderbolt macs. I sure hope this can be resolved with a firmware update, or by someone (Belkin/Kanex) making a new Thunderbolt compatible adapter.
And I don't know if anyone has confirmed it yet since the feature is so hard to take advantage of now, but I'm hoping this years iMac at least accepts 1080P signals in addition to 720P and the native panel resolution. It would be worth the wait for an adapter if it accepts 1080P as well, which would make it at least more future proof since everything has gone to 1080P so rapidly.
I was really counting on my new iMac doubling as a TV/Console display in my room - it was part of what justified the high price of the investment and the convenience of the all-in-one design. I would be very pleased if Apple can help resolve this.

10.7.2 breaks Target Display Mode

You might find that Target Display Mode stops working after you update to 10.7.2 The solution, discovered by JohnAtBurn in https://discussions.apple.com/thread/3363289, is to use Disk Utility to repair permissions. (This may be the first time repairing permissions has actually fixed anything.)

Tight VNC Viewer runs on Windows 7 and is used to connect to PCs running VNC such as Mac OS X with Screen Sharing enabled. Tight VNC has never been installed on the Mac OS X box.
The only difference between when this worked and when it stopped working is the 10.7.2 update which seems to have broken VNC.

Input field in display mode; but F4 help has to be avail

Hi,
            i have a input field in my view and i want that one to be in display mode ( the intention is that i want to have the value to be filled from F4 help values only). I have set the read only set for the input field. I have tried all the cases of normal ddic help;OVS;Freely input help; context node info value set but no luck.
In the below forum message Re: how to provide f4 help to the read only input field i could see the input from Thomas that the Freely input help will be useful in this case;I tired this way too but no luck.
Can you please let me know do i missed any point ;your inputs are higly appreciated.
Thanks and Regards,
Satish A.

hi,Satish A.
After check your requirement, i think you can use "Freely programmed Input help".You can search them in this forum or google, i think you will get some clue.
As a reply, i summarize this topic simply. Take one example.
Scenario:
F4-help component will be used for "F4". It displays all the data in table, and you can select one record, then the F4-help will be closed and the "CARRID" will be returned to the Read-only field in your main component.
F4-help-component
(1). You should implement one WD Component which implemented the WD interface "IWD_VALUE_HelP".
(2).In this component, you can add one "Interface event", for example, named "Select". And this event has one parameter "CARRID".
(3).In the table's OnSELECT event, you can use:
method ONACTIONSELECT_ROW .
data:
    lo_Node      type ref to If_Wd_Context_Node,
    lo_Elem      type ref to If_Wd_Context_Element,
    ls_elem      type wd_this->element_table,
    lt_elem      type wd_this->elements_table.
*1. get the Solution-list context node
lo_Node = wd_context->get_child_node( Name = 'TABLE' ).
*2. set the lead selection of table
lo_node->set_lead_selection( element = NEW_LEAD_SELECTION ).
*3. get the attribute value of selected row
NEW_LEAD_SELECTION->get_Static_Attributes(
    importing
       Static_Attributes = ls_elem ).
*4. Fire interface event:
"will return the CARRID parameter
WD_COMP_CONTROLLER->Fire_select_Evt(
      CARRID = ls_elem-carrid ).
*5. close the F4 help
WD_COMP_CONTROLLER->F4_LISTENER->CLOSE_WINDOW( ).
endmethod.
In your main component:
(1). Use your F4-help component as used-component
(2). set your context attribute's input help mode as "Freely programmed". At the same time, input your component usage which is added in step 1.
(3). You should add one Event-handler for your F4-help component Interface event, for example, named "On_f4_help". you can use:
method ON_F4_HELP .
"This event handler will has one parameter named "CARRID" automatically
wd_context->set_attribute(
    EXPORTING
      name = 'IPFIELD'
      value = CARRID
endmethod.
Hope it can help you a little.
Best wishes.

Component Update/Display mode ... wierd behavior.

Similar Messages

Maybe you are looking for