PCUI Display Mode Error
Hi All,
I am able to display data in the PCUI CRM 5.0 (This occurs when a user does not have authorization or the BP is locked), but when this BP data is displayed the settings in the field group are not adhered to I.E. hidden fields are displayed and they are out of order.
Please help, will reward points!
Warm Regards,
Gareth Clarke
Need alittle more info, are you sure that the view(BLVIEW) is the same when you are displaying data and then the second time? Possibly the BSP is switching views on you and that would explain the hidden fields displaying.
Just a guess.
-Alex
Similar Messages
-
I have the 27-inch (late 2009) iMac with mini-Display port input. Whenever I return from Target Display Mode, I get the attached error message and iPhoto becomes unresponsive (the window is still active, but clicking on it produces the error/warning system sound), I have to Force Quit it. The current screen resolution is not optimal for iPhoto (sometimes the error message is a little off the screen in the lower left and only the top of the window can be seen. This also seems to affect iTunes at the same time (by resizing the window to be super small), but without the error message or unresponsiveness.
Has anyone else gotten this problem, and or might know of a fix?Yes, I have the same problem. I have checked the resolution in Sysyem Preferences - display and it is properly set to the highest resolution (which is recommended). I have no idea why this is ocurring but it is annoying.
-
Transaction goes to display mode after an error message / POPUP - Urgent
Hi All,
We have a requirement that, in the Service order transaction IW31/ IW32 in the components tab , based on the material numbers entered by the user we need to call a Popup and inform user to fill in the correct value for special stock indicator.
I tried using the BADI Workorder_update , but within that I could not call a pop up or a message. I tried using the exit EXIT_SAPLCOMK_014 where
in I collect the incorrect components and call a POP UP with all of them. But once I call the POP UP the IW31/IW32 screen in the background goes
to display mode and then we are not able to change the value as per information from the POP UP. This is the same problem that we faced with the
BADI.
Please let me know if this could be handled in any other way.
Regards,
Prabaharan.Gcheck with exit
Transaction Code - IW31 Create Order
Exit Name Description
IWO10012 Maintenance order: Priority handling on central header
No of Exits: 1
Transaction Code - IW32 CHANGE ORDER
Exit Name Description
IWO10012 Maintenance order: Priority handling on central header
No of Exits: 1
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.........
Minal -
A field of type I is showing Zero in display mode
Hi,
I have module pool program, with create, change and display buttons.
Here I have a field PERNR type PERNR_D.
This field is not a mandatory field. so, I am creating a record without entering any value in this.
But when I go into display for this record, it is showing '0'.
How to remove single zero in display mode?
I tried with the following code but it is not working for me.
if zstruct-zpernr eq '00000000'.
write zstruct-zpernr to zstruct-zpernr no-zero.
endif.
Please advise me hereI tried all the ways except using char08.
as permy spec, I should not use this type.
So,
I tried to remove '0' by using the following code.but it is giving error as follows.
Please help me
Code:
if Zstruct-zpernr CO '0'.
if ( Zstruct-zpernr eq '00000000' ) or (Zstruct-zpernr is initial ).
write Zstruct-zpernr to Zstruct-zpernr no-zero.
endif.
error log:
Value is not numeric
Message no. E2135
Diagnosis
A value that is not numeric has been entered for a domain with a numeric data type. This is not allowed.
System Response
The system cannot accept the value.
Procedure
Correct your entry. You must enter a numeric value. -
Limited to one display mode with new nvidia drivers
I have a problem with nvidia drivers after 8178
I can get any display mode to work as long as i specify only one mode.
If i enter more modes in my xorg.conf, it will ignore all those modes and revert back to nvidia-auto-select (wich is 1024x768 in my case)
Anyway, i'm not able to change resolutions using xrandr for example. I need this for some applications that require to run in a different display mode ( old windows games i run using wine for example)
When i run X -logverbose 5 it becomes clear that all my monitor's supported modes are in the display pool.
I have also put in gtp generated modelines for all the modes i might need.
I really need a solution to this as i will probably no longer be able to use 8178 when xorg7.1 hits current.
This is what i have in my xorg.conf:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "AlwaysCore"
InputDevice "Mouse1" "CorePointer"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/cyrillic/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
SubSection "extmod"
# Option "omit xfree86-dga"
EndSubSection
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
Load "bitmap"
Load "ddc"
Load "int10"
Load "record"
# Load "speedo"
Load "vbe"
# Load "xf8_32bpp.so"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "evdev"
# Option "Protocol" "Explorerps/2"
Option "Device" "/dev/input/mx1000"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "11 12"
Option "Dev Name" "Logitech USB Receiver" # cat /proc/bus/input/devices
Option "Dev Phys" "usb-*/input0" # cat /proc/bus/input/devices
Option "Buttons" "12"
Option "Resolution" "800"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "microsoftinet"
Option "XkbLayout" "us"
Option "XkbVariant" ",qwerty"
EndSection
Section "Monitor"
Identifier "Monitor0"
# VendorName "Iiyama"
# ModelName "A901HT"
ModelName "IVM:0119"
HorizSync 27.0 - 115.0
VertRefresh 50.0 - 160.0
# Option "DPMS"
Modeline "1600x1200_100.00" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
Modeline "1600x1200_85.00" 234.76 1600 1720 1896 2192 1200 1201 1204 1260 -HSync +Vsync
Modeline "1600x1200_75.00" 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -HSync +Vsync
Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync
Modeline "1280x1024_100.00" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
Modeline "1280x1024_85.00" 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -HSync +Vsync
Modeline "1280x1024_75.00" 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync
Modeline "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
Modeline "1152x864_100.00" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
Modeline "1152x864_85.00" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
Modeline "1152x864_75.00" 104.99 1152 1224 1352 1552 864 865 868 902 -HSync +Vsync
Modeline "1152x864_60.00" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
Modeline "1024x768_100.00" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
Modeline "1024x768_85.00" 94.39 1024 1088 1200 1376 768 769 772 807 -HSync +Vsync
Modeline "1024x768_75.00" 81.80 1024 1080 1192 1360 768 769 772 802 -HSync +Vsync
Modeline "1024x768_60.00" 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync
Modeline "800x600_85.00" 56.55 800 840 928 1056 600 601 604 630 -HSync +Vsync
Modeline "800x600_75.00" 48.91 800 840 920 1040 600 601 604 627 -HSync +Vsync
Modeline "800x600_60.00" 38.22 800 832 912 1024 600 601 604 622 -HSync +Vsync
Modeline "640x480_85.00" 35.71 640 672 736 832 480 481 484 505 -HSync +Vsync
Modeline "640x480_75.00" 30.72 640 664 728 816 480 481 484 502 -HSync +Vsync
Modeline "640x480_60.00" 23.86 640 656 720 800 480 481 484 497 -HSync +Vsync
Modeline "320x240_60.00" 5.26 320 304 336 352 240 241 244 249 -HSync +Vsync
Modeline "320x200_60.00" 4.19 320 304 328 336 200 201 204 208 -HSync +Vsync
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NvAGP" "3"
Option "RenderAccel" "TRUE"
Option "NoLogo" "on"
Option "RandRRotation" "TRUE"
# Option "CursorShadow" "FALSE"
# Option "ConnectedMonitor" "CRT"
# Option "UseEDIDFreqs" "FALSE"
# Option "UseEDIDDpi" "FALSE"
# Option "ModeValidation" "NoEdidModes"
# Option "ModeValidation" "AllowNon60HzDFPModes"
# Option "UseEDID" "FALSE"
Option "IgnoreDisplayDevices" "CRT"
Option "DPI" "96 x 96"
Option "Coolbits" "1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 32
Modes "1280x1024"
# Visual StaticGray
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024_85"
# Modes "1280x1024_85 1152x864 1024x768 800x600 640x480 320x240 320x200"
# Visual StaticGray
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024_85"
# Visual StaticGray
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600_75"
# Visual StaticGray
EndSubSection
EndSection
#Section "DRI"
# Mode "0666"
#EndSection
All the EDID specific options i have commented out appeared to be useless.
The following Xorg.0.log was generated using only one mode, resulting in X running in 1280x1024@85hz (logverbose level 5)
[code]
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-ARCH i686
Current Operating System: Linux Orthanc 2.6.17.11 #1 PREEMPT Fri Aug 25 08:31:05 CEST 2006 i686
Build Date: 21 June 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 29 13:57:46 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Mouse1"
(WW) The directory "/usr/share/fonts/local/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/CID/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/PEX" does not exist.
Entry deleted from font path.
(**) FontPath set to "/usr/share/fonts/misc/:unscaled,/usr/share/fonts/100dpi/:unscaled,/usr/share/fonts/75dpi/:unscaled,/usr/share/fonts/misc/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,/usr/share/fonts/cyrillic/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1"
(**) RgbPath set to "/usr/share/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.8
X.Org XInput driver : 0.5
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(--) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2560 card 1043,80b2 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,2561 card 0000,0000 rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,24c2 card 1043,8089 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24c4 card 1043,8089 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24c7 card 1043,8089 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24cd card 1043,8089 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 82 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24c0 card 0000,0000 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24cb card 1043,8089 rev 02 class 01,01,8a hdr 00
(II) PCI: 01:00:0: chip 10de,0312 card 1043,80e7 rev a1 class 03,00,00 hdr 00
(II) PCI: 02:05:0: chip 14e4,4401 card 1043,80a8 rev 01 class 02,00,00 hdr 00
(II) PCI: 02:0c:0: chip 105a,4d69 card 105a,4d68 rev 02 class 01,80,85 hdr 00
(II) PCI: 02:0d:0: chip 1102,0004 card 1102,0051 rev 03 class 04,01,00 hdr 80
(II) PCI: 02:0d:1: chip 1102,7003 card 1102,0040 rev 03 class 09,80,00 hdr 80
(II) PCI: 02:0d:2: chip 1102,4001 card 1102,0010 rev 00 class 0c,00,10 hdr 80
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xde000000 - 0xdfdfffff (0x1e00000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xdff00000 - 0xefffffff (0x10100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[1] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[2] -1 0 0x00009800 - 0x000098ff (0x100) IX[B]
[3] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]
[4] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]
[5] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]
[6] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]
[7] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]
[8] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[9] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[10] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]
[11] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xdb800000 - 0xdd7fffff (0x2000000) MX[B]
(II) Bus 2 prefetchable memory range:
[0] -1 0 0xdfe00000 - 0xdfefffff (0x100000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV31 [GeForce FX 5600] rev 161, Mem @ 0xde000000/24, 0xe0000000/28, BIOS @ 0xdffe0000/17
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf0000000 from 0xf7ffffff to 0xefffffff
(II) Active PCI resource ranges:
[0] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[1] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[2] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[3] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[4] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[5] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[6] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[7] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[8] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[10] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[11] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[12] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[13] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[14] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[15] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[16] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[17] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[18] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[19] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[20] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[21] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[1] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[2] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[3] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[4] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[5] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[6] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[7] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[8] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[10] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[11] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[12] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[13] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[14] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[15] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[16] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[17] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[18] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[19] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[20] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[21] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[6] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[7] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[8] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[9] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[10] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[11] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[12] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[13] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[15] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[18] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[19] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[20] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[21] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[22] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[23] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[24] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[25] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[26] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[27] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Reloading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts/libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.0.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8774
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "bitmap"
(II) Reloading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Loading font Bitmap
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules/libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension RECORD
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.8
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8774
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 0.0.0, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.4
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5
(II) NVIDIA dlloader X Driver 1.0-8774 Tue Aug 1 20:55:35 PDT 2006
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) Found 1 NVIDIA X Screens
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.8
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[6] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[7] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[8] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[9] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[10] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[11] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[12] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[13] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[15] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[18] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[19] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[20] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[21] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[22] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[23] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[24] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[25] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[26] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[27] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) resource ranges after probing:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x2fffffff (0x2ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdb800000 - 0xdb803fff (0x4000) MX[B]
[6] -1 0 0xdc000000 - 0xdc0007ff (0x800) MX[B]
[7] -1 0 0xdfe00000 - 0xdfe03fff (0x4000) MX[B]
[8] -1 0 0xdc800000 - 0xdc803fff (0x4000) MX[B]
[9] -1 0 0xdd000000 - 0xdd001fff (0x2000) MX[B]
[10] -1 0 0x30000000 - 0x300003ff (0x400) MX[B]
[11] -1 0 0xdd800000 - 0xdd8003ff (0x400) MX[B]
[12] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[13] -1 0 0xdffe0000 - 0xdfffffff (0x20000) MX[B](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[15] -1 0 0xde000000 - 0xdeffffff (0x1000000) MX[B](B)
[16] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[17] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[18] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[21] -1 0 0x00009800 - 0x00009807 (0x8) IX[B]
[22] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[23] -1 0 0x0000a400 - 0x0000a40f (0x10) IX[B]
[24] -1 0 0x0000a800 - 0x0000a803 (0x4) IX[B]
[25] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[26] -1 0 0x0000b400 - 0x0000b403 (0x4) IX[B]
[27] -1 0 0x0000b800 - 0x0000b807 (0x8) IX[B]
[28] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[29] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[30] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[31] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[32] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[33] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "on"
(**) NVIDIA(0): Option "NvAGP" "3"
(**) NVIDIA(0): Option "RenderAccel" "TRUE"
(**) NVIDIA(0): Option "RandRRotation" "TRUE"
(**) NVIDIA(0): Option "Coolbits" "1"
(**) NVIDIA(0): Option "DPI" "96 x 96"
(==) NVIDIA(0): Using HW cursor
(**) NVIDIA(0): Enabling RENDER acceleration
(==) NVIDIA(0): Video key set to default value of 0x101fe
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5600 at PCI:1:0:0
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(II) NVIDIA(0): GPU Architecture: 0x30
(II) NVIDIA(0): GPU Implementation: 0x31
(II) NVIDIA(0): GPU Revision: 0xa1
(--) NVIDIA(0): VideoBIOS: 04.31.20.28.00
(--) NVIDIA(0): Found 2 CRTCs on board
(II) NVIDIA(0): Supported display device(s): CRT-0, CRT-1, DFP-0, DFP-1, TV-0
(II) NVIDIA(0): Bus detected as AGP
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(II) NVIDIA(0):
(II) NVIDIA(0): Mode timing constraints for : GeForce FX 5600
(II) NVIDIA(0): Maximum mode timing values :
(II) NVIDIA(0): Horizontal Visible Width : 8192
(II) NVIDIA(0): Horizontal Blank Start : 8192
(II) NVIDIA(0): Horizontal Blank Width : 4096
(II) NVIDIA(0): Horizontal Sync Start : 8184
(II) NVIDIA(0): Horizontal Sync Width : 504
(II) NVIDIA(0): Horizontal Total Width : 8224
(II) NVIDIA(0): Vertical Visible Height : 8192
(II) NVIDIA(0): Vertical Blank Start : 8192
(II) NVIDIA(0): Vertical Blank Width : 256
(II) NVIDIA(0): Veritcal Sync Start : 8191
(II) NVIDIA(0): Vertical Sync Width : 15
(II) NVIDIA(0): Vertical Total Height : 8193
(II) NVIDIA(0):
(II) NVIDIA(0): Minimum mode timing values :
(II) NVIDIA(0): Horizontal Total Width : 40
(II) NVIDIA(0): Vertical Total Height : 2
(II) NVIDIA(0):
(II) NVIDIA(0): Mode timing alignment :
(II) NVIDIA(0): Horizontal Visible Width : multiples of 8
(II) NVIDIA(0): Horizontal Blank Start : multiples of 8
(II) NVIDIA(0): Horizontal Blank Width : multiples of 8
(II) NVIDIA(0): Horizontal Sync Start : multiples of 8
(II) NVIDIA(0): Horizontal Sync Width : multiples of 8
(II) NVIDIA(0): Horizontal Total Width : multiples of 8
(II) NVIDIA(0):
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5600 at PCI:1:0:0:
(--) NVIDIA(0): Iiyama (CRT-0)
(--) NVIDIA(0): Iiyama (CRT-0): 350.0 MHz maximum pixel clock
(--) NVIDIA(0):
(--) NVIDIA(0): --- EDID for Iiyama (CRT-0) ---
(--) NVIDIA(0): EDID Version : 1.1
(--) NVIDIA(0): Manufacturer : IVM
(--) NVIDIA(0): Monitor Name : Iiyama
(--) NVIDIA(0): Product ID : 6401
(--) NVIDIA(0): 32-bit Serial Number : 0
(--) NVIDIA(0): Serial Number String :
(--) NVIDIA(0): Manufacture Date : 2000, week 30
(--) NVIDIA(0): DPMS Capabilities : Standby Suspend Active Off
(--) NVIDIA(0): Prefer first detailed timing : No
(--) NVIDIA(0): Supports GTF : No
(--) NVIDIA(0): Maximum Image Size : 360mm x 270mm
(--) NVIDIA(0): Valid HSync Range : 31 kHz - 106 kHz
(--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 85 Hz
(--) NVIDIA(0): EDID maximum pixel clock : 229.5 MHz
(--) NVIDIA(0):
(--) NVIDIA(0): Established Timings:
(--) NVIDIA(0): 640 x 480 @ 60 Hz
(--) NVIDIA(0): 640 x 480 @ 72 Hz
(--) NVIDIA(0): 640 x 480 @ 75 Hz
(--) NVIDIA(0): 800 x 600 @ 56 Hz
(--) NVIDIA(0): 800 x 600 @ 60 Hz
(--) NVIDIA(0): 800 x 600 @ 72 Hz
(--) NVIDIA(0): 800 x 600 @ 75 Hz
(--) NVIDIA(0): 1024 x 768 @ 60 Hz
(--) NVIDIA(0): 1024 x 768 @ 70 Hz
(--) NVIDIA(0): 1024 x 768 @ 75 Hz
(--) NVIDIA(0): 1280 x 1024 @ 75 Hz
(--) NVIDIA(0):
(--) NVIDIA(0): Standard Timings:
(--) NVIDIA(0): 1600 x 1200 @ 60 Hz
(--) NVIDIA(0): 1600 x 1200 @ 70 Hz
(--) NVIDIA(0): 1600 x 1200 @ 75 Hz
(--) NVIDIA(0): 1600 x 1200 @ 85 Hz
(--) NVIDIA(0):
(--) NVIDIA(0): --- End of EDID for Iiyama (CRT-0) ---
(--) NVIDIA(0):
(II) NVIDIA(0): Frequency information for Iiyama (CRT-0):
(II) NVIDIA(0): HorizSync : 31.000-106.000 kHz
(II) NVIDIA(0): VertRefresh : 56.000-85.000 Hz
(II) NVIDIA(0): (HorizSync from EDID)
(II) NVIDIA(0): (VertRefresh from EDID)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Modes in ModePool for Iiyama (CRT-0) ---
(II) NVIDIA(0): "nvidia-auto-select" : 1024 x 768 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1920x1200" : 1920 x 1200 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1920x1200_70" : 1920 x 1200 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1920x1200_60" : 1920 x 1200 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1856x1392" : 1856 x 1392 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1856x1392_60" : 1856 x 1392 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1792x1344" : 1792 x 1344 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1792x1344_60" : 1792 x 1344 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1680x1050" : 1680 x 1050 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_85" : 1680 x 1050 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_75" : 1680 x 1050 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_70" : 1680 x 1050 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1680x1050_60" : 1680 x 1050 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1600x1200" : 1600 x 1200 @ 85.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_85" : 1600 x 1200 @ 85.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_75" : 1600 x 1200 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_70" : 1600 x 1200 @ 70.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1200_65" : 1600 x 1200 @ 65.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1600x1200_60" : 1600 x 1200 @ 60.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1600x1024" : 1600 x 1024 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1600x1024_60" : 1600 x 1024 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050" : 1400 x 1050 @ 85.3 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_85" : 1400 x 1050 @ 85.3 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_85_0" : 1400 x 1050 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_75" : 1400 x 1050 @ 74.8 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_70" : 1400 x 1050 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_70_0" : 1400 x 1050 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1400x1050_60" : 1400 x 1050 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x1024" : 1280 x 1024 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x1024_85.00" : 1280 x 1024 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_75.00" : 1280 x 1024 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_60.00" : 1280 x 1024 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_85_0" : 1280 x 1024 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x1024_85" : 1280 x 1024 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_75" : 1280 x 1024 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1280x1024_75_0" : 1280 x 1024 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x1024_60_0" : 1280 x 1024 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x1024_60" : 1280 x 1024 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1280x960" : 1280 x 960 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x960_85" : 1280 x 960 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x960_60" : 1280 x 960 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1280x800" : 1280 x 800 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800_85" : 1280 x 800 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800_75" : 1280 x 800 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800_70" : 1280 x 800 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x800d60" : 1280 x 800 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "1280x800_60" : 1280 x 800 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768" : 1280 x 768 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_85" : 1280 x 768 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_75" : 1280 x 768 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_70" : 1280 x 768 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x768_60" : 1280 x 768 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720" : 1280 x 720 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_85" : 1280 x 720 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_75" : 1280 x 720 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_70" : 1280 x 720 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1280x720_60" : 1280 x 720 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864" : 1152 x 864 @ 85.1 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_85.00" : 1152 x 864 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_75.00" : 1152 x 864 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_60.00" : 1152 x 864 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_85_0" : 1152 x 864 @ 85.1 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_85" : 1152 x 864 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_85_1" : 1152 x 864 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_75_0" : 1152 x 864 @ 75.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1152x864_75" : 1152 x 864 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_75_1" : 1152 x 864 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_70" : 1152 x 864 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "1152x864_60" : 1152 x 864 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1152x864_60_0" : 1152 x 864 @ 60.0 Hz (from: X Server)
(II) NVIDIA(0): "1024x768_85.00" : 1024 x 768 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1024x768_75.00" : 1024 x 768 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_60.00" : 1024 x 768 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_85" : 1024 x 768 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_85_0" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1024x768_75_1" : 1024 x 768 @ 75.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "1024x768_75" : 1024 x 768 @ 75.0 Hz (from: EDID)
(II) NVIDIA(0): "1024x768_75_0" : 1024 x 768 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "1024x768_70" : 1024 x 768 @ 70.1 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1024x768d60" : 1024 x 768 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "1024x768_60" : 1024 x 768 @ 60.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "1024x768_60_0" : 1024 x 768 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "960x720" : 960 x 720 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x720d60" : 960 x 720 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600" : 960 x 600 @ 75.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d75" : 960 x 600 @ 75.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d73" : 960 x 600 @ 72.8 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d70" : 960 x 600 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "960x600d60" : 960 x 600 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "928x696" : 928 x 696 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "928x696d60" : 928 x 696 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "896x672" : 896 x 672 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "896x672d75" : 896 x 672 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "896x672d60" : 896 x 672 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "848x480" : 848 x 480 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "848x480_85" : 848 x 480 @ 85.0 Hz (from: X Server)
(II) NVIDIA(0): "848x480_75" : 848 x 480 @ 75.0 Hz (from: X Server)
(II) NVIDIA(0): "848x480_70" : 848 x 480 @ 70.0 Hz (from: X Server)
(II) NVIDIA(0): "840x525" : 840 x 525 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d85" : 840 x 525 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d75" : 840 x 525 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d70" : 840 x 525 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "840x525d60" : 840 x 525 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "832x624" : 832 x 624 @ 74.5 Hz (from: X Server)
(II) NVIDIA(0): "832x624_75" : 832 x 624 @ 74.5 Hz (from: X Server)
(II) NVIDIA(0): "800x600" : 800 x 600 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "800x600_85.00" : 800 x 600 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_75.00" : 800 x 600 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_60.00" : 800 x 600 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_85_0" : 800 x 600 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "800x600_85" : 800 x 600 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600d85" : 800 x 600 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_75_0" : 800 x 600 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600_75" : 800 x 600 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x600d75" : 800 x 600 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_72" : 800 x 600 @ 72.2 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x600d70" : 800 x 600 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600d65" : 800 x 600 @ 65.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_60" : 800 x 600 @ 60.3 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x600_60_0" : 800 x 600 @ 60.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "800x600d60" : 800 x 600 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x600_56" : 800 x 600 @ 56.2 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "800x512" : 800 x 512 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "800x512d60" : 800 x 512 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "720x400" : 720 x 400 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "720x400_85" : 720 x 400 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "700x525" : 700 x 525 @ 85.3 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d85" : 700 x 525 @ 85.3 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d85_0" : 700 x 525 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d75" : 700 x 525 @ 74.8 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d70_0" : 700 x 525 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d70" : 700 x 525 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "700x525d60" : 700 x 525 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512" : 640 x 512 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512d85" : 640 x 512 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512d75" : 640 x 512 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x512d60" : 640 x 512 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480" : 640 x 480 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480_85.00" : 640 x 480 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480_75.00" : 640 x 480 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480d85" : 640 x 480 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480_85_0" : 640 x 480 @ 85.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x480_85" : 640 x 480 @ 85.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480_75" : 640 x 480 @ 75.0 Hz (from: X Server, VESA, EDID)
(II) NVIDIA(0): "640x480_75_0" : 640 x 480 @ 75.0 Hz (from: Custom ModeLine)
(II) NVIDIA(0): "640x480_73" : 640 x 480 @ 72.8 Hz (from: EDID)
(II) NVIDIA(0): "640x480_73_0" : 640 x 480 @ 72.8 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x480d60" : 640 x 480 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x480_60_0" : 640 x 480 @ 60.0 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x480_60" : 640 x 480 @ 60.0 Hz (from: EDID)
(II) NVIDIA(0): "640x400" : 640 x 400 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x400_85" : 640 x 400 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x400d85" : 640 x 400 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x400d75" : 640 x 400 @ 75.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x400d70" : 640 x 400 @ 70.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x400d60" : 640 x 400 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384" : 640 x 384 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d85" : 640 x 384 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d75" : 640 x 384 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d70" : 640 x 384 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x384d60" : 640 x 384 @ 60.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360" : 640 x 360 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d85" : 640 x 360 @ 85.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d75" : 640 x 360 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d70" : 640 x 360 @ 70.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x360d60" : 640 x 360 @ 60.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "640x350" : 640 x 350 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "640x350_85" : 640 x 350 @ 85.1 Hz (from: X Server, VESA)
(II) NVIDIA(0): "576x432" : 576 x 432 @ 85.2 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d85" : 576 x 432 @ 85.2 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d85_0" : 576 x 432 @ 85.1 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d75" : 576 x 432 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0): "576x432d75_0" : 576 x 432 @ 75.0 Hz DoubleScan (from: X Server)
(II) NVIDIA(0It turns out it won't do any lower than 640x480. These are my changes:
Modeline "800x600_85.00" 56.55 800 840 928 1056 600 601 604 630 -HSync +Vsync DoubleScan
Modeline "800x600_75.00" 48.91 800 840 920 1040 600 601 604 627 -HSync +Vsync DoubleScan
Modeline "800x600_60.00" 38.22 800 832 912 1024 600 601 604 622 -HSync +Vsync DoubleScan
Modeline "640x480_85.00" 35.71 640 672 736 832 480 481 484 505 -HSync +Vsync DoubleScan
Modeline "640x480_75.00" 30.72 640 664 728 816 480 481 484 502 -HSync +Vsync DoubleScan
Modeline "640x480_60.00" 23.86 640 656 720 800 480 481 484 497 -HSync +Vsync DoubleScan
Modeline "320x240_60.00" 5.26 320 304 336 352 240 241 244 249 -HSync +Vsync DoubleScan
Modeline "320x200_60.00" 4.19 320 304 328 336 200 201 204 208 -HSync +Vsync DoubleScan
and
Modes "1280x1024_85" "1280x1024_75" "1280x1024_60" "1152x864_85" "1152x864_75" "1152x864_60" "1024x768_85" "1024x768_75" "1024x768_60" "800x600_75" "800x600_60" "640x480_75" "640x480_60" "320x240_60" "320x200_60"
I'm not sure if i did that doublescan thingy right, but it gets completely ignored. -
Profit Center Field (Display Mode) During Asset Postings
We are using document splitting functionality with profit center mandatory for any kind of posting.
Scenario-Asset purchase through PO:
1.Purchase Order -created
2.At goods receipt error is coming balancing filed is not filled (bcoz asset is not a material), for materials we are giving profit center. in the asset master i assigned cost center, still profit center is not deriving.
Scenario-Asset Purchase from vendor
purchasing asset directly from vendor through F-90, against asset line item we have to assign profit center. Cost center & profit center is coming in display mode. in the asset master i already maintained cost center, still profit is not deriving.
I already done config for field status [asset account number (G067) andPosting Keys (70,75)]. I also checked note no.684659.
how profit center will be derived for any kind of asset postings.
Thanks
SaiHi
Guess - Check settings in ACSET
Thank You, -
Unable to open the PM order in change and display mode
Dear All,
Am facing some issue that am unable to open the Maintenance Order in Change and Display mode.
Can you provide the solution.Hi Thirupathi,
Can you send us a screenshot or the error message information ?
If it is due to status missing (SAP note available for the same)
Regards
Terence -
How do I connect a DVD play to iMac through "monidisplayport to HDMI" adopter?
hello;
i am finding that even Apple employees do not know the correct answers.
i purchased a new 27 inch iMac last night at MainPlace in Naperville, Illinois.
Two Apple sales associates told me that it would work with the mac mini which
i purchased less than a month ago or with the macbook pro 13in. i knew it would
not work with any of the three macbook pro 17inch.
after much testing it is apparent that the "Target Display Mode" will only work
if both computers have Thunderbolt/Mini DIsplayPort technology. It will not work
with the current shipping mac mini.
Apple really needs to clue in the retail store sales associates and rename these
Thunderbolt/Mini DIsplayPorts something different since they will not work with
the plain vanilla Mini DisplayPorts.
I am debating about returning the 27 inch iMac based on this gross error on the
Apple Sales Associates part. -
How to know if an transaction is in display mode or change mode
Hi,
I have to set an information message if any transaction is in display mode and an error message if it is in change mode for a particular condition.
How would I know programmatically that it is in display mode or change mode for a screen?>
Neela M B wrote:
> Hi,
>
> You can use the importing parameter I_ACTIVITY of the method SET_DATA in the BADI. Pass this flag along with the data and use it to determine the Create/Change or Display Mode.
>
>
> CASE I_ACTIVITY.
> WHEN 'H' or 'V'. " Create or Change
> ...
> WHEN 'A'. " Display
> ...
> ENDCASE.
You sure are a direct collegue and have access to his problem or you are indeed the successor of Uri Geller.
I never would have guessed he's using SET_DATA in a BADI.
Test: what am i thinking right now? -
Developer Mode Error: Stale Data
The requested page contains stale data. This error could have been caused through the use of the browser's navigation buttons (the browser Back button, for example). If the browser's navigation buttons were not used, this error could have been caused by coding mistakes in application code. Please check Supporting the Browser Back Button developer guide - View Object Primary Key Comparison section to review the primary causes of this error and correct the coding mistakes.
Cause:
The view object XxEmployeeAM.XxEmployeeSearchVO1 contained no record. The displayed records may have been deleted, or the current record for the view object may not have been properly initialized.
To proceed, please select the Home link at the top of the application page to return to the main menu. Then, access this page again using the application's navigation controls (menu, links, and so on) instead of using the browser's navigation controls like Back and Forward.
can you please help me with this error,that will be helpful to me
i am using jdeveloper version 12.1.3package xxcuso.oracle.apps.fnd.emprec.server;
import oracle.apps.fnd.framework.server.OAApplicationModuleImpl;
import oracle.jbo.Row;
import xxcuso.oracle.apps.fnd.emprec.server.XxEmployeeSearchVO1Impl;
import xxcuso.oracle.apps.fnd.emprec.server.XxEmployeeVO1Impl;
import xxcuso.oracle.apps.fnd.emprec.server.XxEmployeeVO1RowImpl;
//import java.lang.Number;
import java.lang.String;
import oracle.jbo.domain.Number;
import xxcus.oracle.apps.fnd.emprec.server.XxEmployeeSearchVOImpl;
import xxcus.oracle.apps.fnd.emprec.server.XxEmployeeVOImpl;
//import oracle.jbo.domain.Number;
// --- File generated by Oracle ADF Business Components Design Time.
// --- Custom code may be added to this class.
// --- Warning: Do not modify method signatures of generated methods.
public class XxEmployeeAM1Impl extends OAApplicationModuleImpl
/**This is the default constructor (do not remove)
public XxEmployeeAM1Impl()
public void searchEmployee(String empNum, String empName) {
try {
XxEmployeeSearchVO1Impl vo = getXxEmployeeSearchVO1_1();
vo.setMaxFetchSize(-1);
vo.setWhereClause(null);
vo.setWhereClauseParams(null);
vo.setWhereClause("EMPNO = nvl(" + empNum + ",EMPNO)" +
"AND UPPER(ENAME) like UPPER('%" + empName + "%')");
System.out.println("search query - " + vo.getQuery());
vo.executeQuery();
} catch(Exception e) {
e.printStackTrace();
public void initCreateEmp() {
try {
XxEmployeeVO1Impl empCreateVO = getXxEmployeeVO1_1();
empCreateVO.setMaxFetchSize(0);
XxEmployeeVO1RowImpl row = (XxEmployeeVO1RowImpl)empCreateVO.createRow();
// here we are setting the employee number using a DB Sequence
Number empNum = (Number)getOADBTransaction().getSequenceValue("EMPLOYEE_NUMBER_S");
row.setEmpno(empNum);
empCreateVO.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
} catch (Exception e) {
e.printStackTrace();
public void initUpdateEmp(String empNum) {
try {
XxEmployeeVO1Impl employeeVO = getXxEmployeeVO1_1();
employeeVO.setWhereClause(null);
employeeVO.setWhereClauseParams(null);
employeeVO.setWhereClause("EMPNO = :1");
employeeVO.setWhereClauseParam(0, empNum);
employeeVO.setMaxFetchSize(-1);
employeeVO.executeQuery();
} catch (Exception e) {
e.printStackTrace();
public void commit() {
try {
XxEmployeeVO1Impl employeeVO = getXxEmployeeVO1_1();
XxEmployeeVO1RowImpl row = (XxEmployeeVO1RowImpl)employeeVO.first();
String savedEmp = row.getEmpno().toString();
getOADBTransaction().commit();
//return savedEmp;
} catch (Exception e) {
e.printStackTrace();
/**Sample main for debugging Business Components code using the tester.
public static void main(String[] args)
launchTester("xxcuso.oracle.apps.fnd.emprec.server", /* package name */
"XxEmployeeAM1Local" /* Configuration Name */);
/**Container's getter for XxEmployeeSearchVO1_1
/* public XxEmployeeSearchVO1Impl getXxEmployeeSearchVO1_1()
return (XxEmployeeSearchVO1Impl)findViewObject("XxEmployeeSearchVO1_1");
/**Container's getter for XxEmployeeVO1_1
public XxEmployeeVO1Impl getXxEmployeeVO1_1()
return (XxEmployeeVO1Impl)findViewObject("XxEmployeeVO1_1");
public XxEmployeeSearchVO1Impl getXxEmployeeSearchVO1_1()
return (XxEmployeeSearchVO1Impl)findViewObject("XxEmployeeSearchVO1_1");
/**Container's getter for XxEmployeeVO1_1
public XxEmployeeVO1Impl getXxEmployeeVO1_1()
return (XxEmployeeVO1Impl)findViewObject("XxEmployeeVO1_1");
} -
How to change qty field as change mode to display mode in VL32N
Hi Guru's,
My requirement is for particular users quantity field in VL32N to display mode remaining users it should be in change mode.
We are already created a Security Object for this.
Can you please anyone help how to approach this requiremnt. Is there any standard BAdI for this.
Thanks in Advance.
Regards,
Sai RamaHi
There are Badi for this T-code
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
V53W0001 User exits for creating picking waves
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53C0001 Rough workload calculation in time per item
V50S0001 User Exits for Delivery Processing
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50R0002 Collective processing for delivery creation
V50R0001 Collective processing for delivery creation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT Delivery: Item Status Calculation
V02V0004 User Exit for Staging Area Determination (Item)
V02V0003 User exit for gate + matl staging area determination (headr)
V02V0002 User exit for storage location determination
V02V0001 Sales area determination for stock transport
You can try with any one of them V53W0001, V50S0001, V50Q0001, V02V0004, also you can proceed with table auhtorization as there is need to check one table before entring in T-code as if user id is there then not able to edit.
Here don't make code like need to maintain all id's, if id is there then not able to edit, so to whom you don't want to allow maintain their id's in that.
Thanks
Bhupinder Singh Arora -
Display mode for certain orders
Calling PCUI for service tickets ( CRMD_BUS2000116 ) - CRM ver 4.0
In the search results I have a number of orders, some of which need to be editable and
some of which aren't. If a non-editable one is selected, then all the details ( line items, dates
etc) for the order need to be shown in display mode.
In the model access class for search results, I can make the relevant lines of the results list view-only by populating table ET_FIELD_ATTRIBUTE in the read method. In order to make the order details display-only I have also tried calling CRM_INTLAY_SET_PROCESS_MODE to set the process mode to C, however this only seems to affect the fieldgroups processed by this model access class. All the other details ( spare parts, dates, partners etc - dealt with by other model access classes) remain in change mode.
How do you tell PCUI that once an order has been selected in the search results, it is to be treated as display-only ( exactly the same as what happens if you select an order which someone else has locked) ? Surely there is an easier way than bespoking every single MAC and playing with ET_FIELD_ATTRIBUTE ?
Thanks
IanHi Lan,
I dont have any idea about specific orders but if u want for particular user(Partner) who are not created/involved in particular orders they cannot search or open others orders.
u can achive above scenario by creating diffrent iview for diffrent user with some MAC configuration.
Hope it'll help u.
Thanks,
Dipesh. -
Order qty is in display mode in qty contract
HI GURU
kapil & Raghavendra YN ,
I follow your instructions but it is not working.
guru i want to put target qty & order qty both,
say---target qty 1000 & order qty 200 like that . but in standard sap system order qty is in display mode .
note- i simply copied qty contract from standard qty contract(QC) in sales document header.
According to Raghavendra YN , when i change Screen sequence gr in vov8 ,it works but only order qty comes instead of target qty. but i want to put both qty.
so please help me.Hi
This is Standard SAP Practice
Actually in The quantity contract the target quantity field is how much contract quantity for the line Item, you are making Agreement with your customer typically this is agreement Quantity
When you are creating sales order with reference to Quantity Contract system propose you How much quantity you want to capy
you can click Selection list in the popup window
for eg You contract Quantity say 100 (Target quantity)
you are coping to sales order say 40 Quantity
now system will update your Quantity in the Contract Document like 60Qty
this is actually to compare your Target quantity with Order quty
if the order quantity Excide the target qty system will through the error Message
thanks
prasannavengadesan -
Starting the application in display mode
Hi there,
For PCUI application, is it possible that when the user clicks on a search results for a transaction, it will go to Display mode, instead of Edit mode automatically? As for now, whenver we click on a transaction number in PCUI, it will automatically go to Edit mode when we view the details!
Let me know if you guys have come across such requiremnts.
Cheers,
JHello Joshua,
- Create an event DISPLAY
- add it to your toolbar group.
- in the process_event method of your MAC, put the 'display' info in a global variable
- in the read method, check this global variable. if your are in display mode, put all field attributes to A in table et_field_attribute.
Example for application CRMM_ACCOUNT.
There is an event 'DISPLAY' in the process_event method. When called, a value 09 is set to gv_activity (display mode).
In the read method, when gv_activity = (09), the field attributes are set to read only via
Activity "display": don't allow to change anything
IF gv_activity = gc_activity-display.
CALL METHOD cl_bsp_bp_global_service=>set_field_attr
EXPORTING
iv_object_key = ls_object-object_key
iv_screen_structure_name = iv_screen_structure_name
iv_field_property = gc_no_change
CHANGING
ct_field_attribute = et_field_attribute
ct_dd03p = gt_dd03p.
ENDIF.
Hope this will help you,
Regards,
Fred -
Jerky Video and Display Driver Error
We use CS3 at our production house. My editor has told me he is now getting jerky videos and the following error. This pops up in a yellow triangle at the bottom of the screen which when I click on it, an Events Window is opened.
Error: "Desktop Display Mode has been reset because the video card returned an error. Please reset the Desktop Display Mode in the Playback Settings dialog as this may impact your playback performance."
The computer is a Sony Vaio with 1GB RAM, P4 w/HT, RAID5 of SCSI drives, and ATI Radeon 1600 Pro. We are running Windows XP Pro and Premiere Pro CS3. Supposedly the video just started being jerky the last month or two. Windows update issue? I have tried updating the video card drivers (released March 2009) and also changed the Desktop Display to all three options ... Comptable, Standard and GPU. The video still plays back and exports to tape jerky. However, if we export to an AVI on the local disk, then pull that video back into an older version of Premiere Pro we can export to tape.
Any thoughts!?!?! I have found similar qusetions in other forums, but it seems like no one has an answer.It is very common for OS updates to render display drivers obsolete, and most people do not even know that these are installed. If you have tried the most recent driver (replaceing an older one), and not helped, it might be something else.
The aspect of the video Exporting poorly, leads me to believe that your system might be underpowered, especially in the I/O sub-system. A slow, fragmented, or full HDD can do the same. That would NOT address the warning message, though. That almost has to be a vid-card, or driver issue.
Also, if your Assets have to be decoded by PrPro, that will tax the system. If you Export as DV-AVI, then the CPU does not need to work overtime on the conversion.
Please give a complete description of the Assest, especially their CODEC's. Please give a system breakdown, paying special attention to the I/O sub-system (HDD's specs. and all configuration details).
Good luck,
Hunt
Maybe you are looking for
-
Outlook 2010 takes a long time to open emails with embedded images
Hello, outlook 2010 on windows 7 both with latest updates applied. outlook is in online mode and the option "Don't download automatically in HTML email messages or RSS tiems" is not selected. it takes a long time to open the message with an embedded
-
How do I add an outline around an image in Elements 10
I have an image that I created via Elements 10... The main body of the image is black and I am wanting to add a white outline around the image so I can place the image on a black background... Can someone advise how to add an outline including colori
-
If empty internal table in select for all entries what is the result?
In select all entries statement , if empty internal table is there then what is the result.
-
IDVD: 'ME BROK'N' Message in series 5 and 6 Theme Previews
When Deciding on what theme to use after just installing iLife '08, the themes under 5.0 and 6.0 have a preview message saying 'Me Brok'n' in purple writing with a lime background, it looks very childish writing however all the other themes work fine
-
Any Blogs related to Work Flow in PI.
Hai Experts! Any Blogs related to Work Flow in PI. Our Requirement is there is need of User Decision. Only when the user Approve the Record the Data should get interfaced to the Target System. We are having a Portal Application. So the Approval Scree