Creating screen area

Hi
I dont have much expeience in abap so any help is deeply appreciated.
This is what i am supposed to do.
someone please explain me step by step method as i how to ahieve this assuming that i am a beginner in sap abap.
also how can i see sap note number 86050
Create the screen area.
Double-click SAPLCJWB0205_CUSTSCR1_SAPLXCN10600 and then choose Fullscreen. The screen has been preconfigured by SAP. You can delete these fields and add new ones:
Choose Goto -> Dict./Program fields
Maintain the table/field name PROJ and select the fields to appear on the screen.
Generate the screen.
For detailed information, see SAP Note number 86050.

> Hi
> I dont have much expeience in abap so any help is
> deeply appreciated.
> This is what i am supposed to do.
> someone please explain me step by step method as i
> how to ahieve this assuming that i am a beginner in
> sap abap.
> also how can i see sap note number 86050
>
> Create the screen area.
> Double-click SAPLCJWB0205_CUSTSCR1_SAPLXCN10600 and
> then choose Fullscreen. The screen has been
> preconfigured by SAP. You can delete these fields and
> add new ones:
> Choose Goto -> Dict./Program fields
> Maintain the table/field name PROJ and select the
> fields to appear on the screen.
> Generate the screen.
> For detailed information, see SAP Note number 86050.
hi,
if u want to add new fields in the transaction,
First create a project in cmod and attach the enhancement CNEX0006 to the project.
1.go to se11 and in the PROJ table u will find ci_proj include , in this add ur custom fields.
2.go to se51 give SAPLXCN1 in the program name with screen number 0600 , create the subscreen and in the layout choose Dict./Program fields and drag and drop in the screen .
3. if u want to write any logic before the screen is displayed do it in PBO.
4. now in the function exit EXIT_SAPLCJWB_002 , go in the   INCLUDE ZXCN1U11 and write this logic
move-corresponding sap_proj_imp to proj.
5.4. now in the function exit EXIT_SAPLCJWB_003 , go in the    INCLUDE ZXCN1U12. and write this logic
move-corresponding proj to cnci_proj_exp.
Activate the project .
Regards
Syed

Similar Messages

  • Hiding fields in screen area 031

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

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

  • Startx on a vmware is throwing a "failed to create screen resources"

    The Bottom line error is:
    Fatal server error:
    [ 1431.076] (EE) failed to create screen resources(EE)
    I am trying to get a browsers running on my new Arch Linux, so I can cut and paste better for questions. I have installed xorg, chromium, firefox. If I try and start "startx", it say the server did not start. I think it is the failed to create screen resources.
    I have edit the video settings to give it 32meg of memory. Also I hack the .vmx file to enable the 3d opttion. I have installed all the vmtools (open version) Again, new to Arch Linux so I sure it is something stupid.
    Not sure if it helps but here are the errors when I try and run the browsers.
    chromium
    [320:320:1121/142755:Error:browser_main_loop.cc(209) Gtk: cannot open display:
    firefox
    (process:354): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
    Error: no display specified
    Entire log Xorg.0.log
    [ 1430.963]
    X.Org X Server 1.16.2
    Release Date: 2014-11-10
    [ 1430.965] X Protocol Version 11, Revision 0
    [ 1430.965] Build Operating System: Linux 3.17.2-1-ARCH x86_64
    [ 1430.967] Current Operating System: Linux PingBuild 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64
    [ 1430.967] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=36544952-8a9a-41c9-b169-87189310b752 rw quiet
    [ 1430.969] Build Date: 10 November 2014 07:52:13PM
    [ 1430.970]
    [ 1430.970] Current version of pixman: 0.32.6
    [ 1430.972] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 1430.972] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1430.975] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 21 12:53:21 2014
    [ 1430.976] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 1430.976] (==) No Layout section. Using the first Screen section.
    [ 1430.976] (==) No screen section available. Using defaults.
    [ 1430.976] (**) |-->Screen "Default Screen Section" (0)
    [ 1430.976] (**) | |-->Monitor "<default monitor>"
    [ 1430.976] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 1430.976] (==) Automatically adding devices
    [ 1430.976] (==) Automatically enabling devices
    [ 1430.976] (==) Automatically adding GPU devices
    [ 1430.976] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 1430.976] Entry deleted from font path.
    [ 1430.976] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 1430.976] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 1430.976] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 1430.976] (II) Loader magic: 0x818d80
    [ 1430.976] (II) Module ABI versions:
    [ 1430.976] X.Org ANSI C Emulation: 0.4
    [ 1430.976] X.Org Video Driver: 18.0
    [ 1430.976] X.Org XInput driver : 21.0
    [ 1430.976] X.Org Server Extension : 8.0
    [ 1430.979] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
    [ 1430.979] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 1430.983] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
    [ 1431.010] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xd8000000/67108864, 0xd0800000/8388608, I/O @ 0x000010d0/16, BIOS @ 0x????????/32768
    [ 1431.010] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 1431.010] (II) LoadModule: "glx"
    [ 1431.011] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 1431.016] (II) Module glx: vendor="X.Org Foundation"
    [ 1431.016] compiled for 1.16.2, module version = 1.0.0
    [ 1431.016] ABI class: X.Org Server Extension, version 8.0
    [ 1431.016] (==) AIGLX enabled
    [ 1431.016] (==) Matched vmware as autoconfigured driver 0
    [ 1431.016] (==) Matched vmware as autoconfigured driver 1
    [ 1431.016] (==) Matched modesetting as autoconfigured driver 2
    [ 1431.016] (==) Matched fbdev as autoconfigured driver 3
    [ 1431.016] (==) Matched vesa as autoconfigured driver 4
    [ 1431.016] (==) Assigned the driver to the xf86ConfigLayout
    [ 1431.016] (II) LoadModule: "vmware"
    [ 1431.017] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
    [ 1431.044] (II) Module vmware: vendor="X.Org Foundation"
    [ 1431.044] compiled for 1.16.0, module version = 13.0.2
    [ 1431.044] Module class: X.Org Video Driver
    [ 1431.044] ABI class: X.Org Video Driver, version 18.0
    [ 1431.044] (II) LoadModule: "modesetting"
    [ 1431.044] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 1431.044] (II) Module modesetting: vendor="X.Org Foundation"
    [ 1431.044] compiled for 1.16.0, module version = 0.9.0
    [ 1431.044] Module class: X.Org Video Driver
    [ 1431.044] ABI class: X.Org Video Driver, version 18.0
    [ 1431.044] (II) LoadModule: "fbdev"
    [ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 1431.045] (II) Module fbdev: vendor="X.Org Foundation"
    [ 1431.045] compiled for 1.16.0, module version = 0.4.4
    [ 1431.045] Module class: X.Org Video Driver
    [ 1431.045] ABI class: X.Org Video Driver, version 18.0
    [ 1431.045] (II) LoadModule: "vesa"
    [ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 1431.045] (II) Module vesa: vendor="X.Org Foundation"
    [ 1431.045] compiled for 1.16.0, module version = 2.3.2
    [ 1431.045] Module class: X.Org Video Driver
    [ 1431.045] ABI class: X.Org Video Driver, version 18.0
    [ 1431.045] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
    [ 1431.045] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 1431.045] (II) FBDEV: driver for framebuffer: fbdev
    [ 1431.045] (II) VESA: driver for VESA chipsets: vesa
    [ 1431.045] (++) using VT number 1
    [ 1431.045] (--) controlling tty is VT number 1, auto-enabling KeepTty
    [ 1431.045] (WW) Falling back to old probe method for modesetting
    [ 1431.045] (WW) Falling back to old probe method for fbdev
    [ 1431.045] (II) Loading sub module "fbdevhw"
    [ 1431.045] (II) LoadModule: "fbdevhw"
    [ 1431.046] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 1431.046] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 1431.046] compiled for 1.16.2, module version = 0.0.2
    [ 1431.046] ABI class: X.Org Video Driver, version 18.0
    [ 1431.046] (WW) Falling back to old probe method for vesa
    [ 1431.046] (II) vmware(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 1431.046] (--) vmware(0): DRM driver version is 2.6.1
    [ 1431.046] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
    [ 1431.046] (==) vmware(0): RGB weight 888
    [ 1431.046] (==) vmware(0): Default visual is TrueColor
    [ 1431.046] (--) vmware(0): Min width 1, Max Width 8192.
    [ 1431.046] (--) vmware(0): Min height 1, Max Height 8192.
    [ 1431.047] (II) vmware(0): Output Virtual1 has no monitor section
    [ 1431.047] (II) vmware(0): Output Virtual2 has no monitor section
    [ 1431.047] (II) vmware(0): Output Virtual3 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual4 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual5 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual6 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual7 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual8 has no monitor section
    [ 1431.048] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
    [ 1431.049] (II) vmware(0): Printing probed modes for output Virtual1
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
    [ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 1431.049] (II) vmware(0): EDID for output Virtual2
    [ 1431.049] (II) vmware(0): EDID for output Virtual3
    [ 1431.049] (II) vmware(0): EDID for output Virtual4
    [ 1431.049] (II) vmware(0): EDID for output Virtual5
    [ 1431.049] (II) vmware(0): EDID for output Virtual6
    [ 1431.049] (II) vmware(0): EDID for output Virtual7
    [ 1431.049] (II) vmware(0): EDID for output Virtual8
    [ 1431.049] (II) vmware(0): Output Virtual1 connected
    [ 1431.049] (II) vmware(0): Output Virtual2 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual3 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual4 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual5 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual6 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual7 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual8 disconnected
    [ 1431.049] (II) vmware(0): Using exact sizes for initial modes
    [ 1431.049] (II) vmware(0): Output Virtual1 using initial mode 800x600
    [ 1431.049] (II) vmware(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 1431.049] (==) vmware(0): DPI set to (96, 96)
    [ 1431.049] (II) Loading sub module "fb"
    [ 1431.049] (II) LoadModule: "fb"
    [ 1431.049] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 1431.050] (II) Module fb: vendor="X.Org Foundation"
    [ 1431.050] compiled for 1.16.2, module version = 1.0.0
    [ 1431.050] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1431.050] (II) Loading sub module "dri2"
    [ 1431.050] (II) LoadModule: "dri2"
    [ 1431.050] (II) Module "dri2" already built-in
    [ 1431.050] (II) UnloadModule: "modesetting"
    [ 1431.050] (II) Unloading modesetting
    [ 1431.050] (II) UnloadModule: "fbdev"
    [ 1431.050] (II) Unloading fbdev
    [ 1431.050] (II) UnloadSubModule: "fbdevhw"
    [ 1431.050] (II) Unloading fbdevhw
    [ 1431.050] (II) UnloadModule: "vesa"
    [ 1431.050] (II) Unloading vesa
    [ 1431.050] (==) Depth 24 pixmap format is 32 bpp
    [ 1431.050] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
    [ 1431.064] (II) vmware(0): Gallium3D XA version: 2.2.0.
    [ 1431.064] (II) vmware(0): Path of drm device is "/dev/dri/card0".
    [ 1431.064] (II) vmware(0): [DRI2] Setup complete
    [ 1431.064] (II) vmware(0): [DRI2] DRI driver: vmwgfx
    [ 1431.064] (--) vmware(0): Render acceleration is enabled.
    [ 1431.064] (==) vmware(0): Rendercheck mode is disabled.
    [ 1431.064] (--) vmware(0): Direct rendering (3D) is enabled.
    [ 1431.064] (==) vmware(0): Direct presents are disabled.
    [ 1431.064] (==) vmware(0): Hardware only presents are disabled.
    [ 1431.064] (==) vmware(0): Backing store enabled
    [ 1431.064] (==) vmware(0): Silken mouse enabled
    [ 1431.064] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 1431.064] (==) vmware(0): DPMS enabled
    [ 1431.064] (--) RandR disabled
    [ 1431.075] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 1431.075] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 1431.075] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 1431.075] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 1431.075] (II) AIGLX: Loaded and initialized vmwgfx
    [ 1431.075] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 1431.076] (EE)
    Fatal server error:
    [ 1431.076] (EE) failed to create screen resources(EE)
    [ 1431.076] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 1431.076] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 1431.076] (EE)
    [ 1431.076] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 1431.076] (WW) vmware(0): drmDropMaster failed: Invalid argument
    [ 1431.079] (EE) Server terminated with error (1). Closing log file.
    Journal since boot
    -- Logs begin at Wed 2014-11-19 16:23:50 CST, end at Fri 2014-11-21 14:25:54 CST. --
    Nov 21 14:17:03 PingBuild kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xfeff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:00.0: [8086:7190] type 00 class 0x060000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: [8086:7191] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.0: [8086:7110] type 00 class 0x060100
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: [8086:7111] type 00 class 0x01018a
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: reg 0x20: [io 0x10c0-0x10cf]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: [8086:7113] type 00 class 0x068000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1040-0x104f] claimed by PIIX4 SMB
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: [15ad:0740] type 00 class 0x088000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x10: [io 0x1080-0x10bf]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x14: [mem 0xd0000000-0xd0001fff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: [15ad:0405] type 00 class 0x030000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x10: [io 0x10d0-0x10df]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x14: [mem 0xd8000000-0xdbffffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x18: [mem 0xd0800000-0xd0ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x00007fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: [1000:0030] type 00 class 0x010000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x10: [io 0x1400-0x14ff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x14: [mem 0xd0040000-0xd005ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x1c: [mem 0xd0020000-0xd003ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x00003fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: [15ad:0790] type 01 class 0x060401
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [32] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [33] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [34] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [35] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [36] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [37] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [38] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [39] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [40] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [41] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [42] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [43] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [44] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [45] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [46] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [47] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [48] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [49] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [50] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [51] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [52] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [53] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [54] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [55] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [56] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [57] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [58] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [59] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [60] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [61] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [62] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [63] registered
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: [8086:100f] type 00 class 0x020000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x10: [mem 0xd1020000-0xd103ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x18: [mem 0xd1000000-0xd100ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x20: [io 0x2000-0x203f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000cc000-0x000cffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0d00-0xfeff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xd3e00000-0xd3efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xd4200000-0xd42fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [io 0x7000-0x7fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd2700000-0xd27fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [io 0xb000-0xbfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd2b00000-0xd2bfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0xf000-0xffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd2f00000-0xd2ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd3300000-0xd33fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd3700000-0xd37fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd3b00000-0xd3bfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd3f00000-0xd3ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd4300000-0xd43fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
    Nov 21 14:17:03 PingBuild kernel: ACPI: Enabled 2 GPEs in block 00 to 0F
    Nov 21 14:17:03 PingBuild kernel: vgaarb: setting as boot device: PCI:0000:00:0f.0
    Nov 21 14:17:03 PingBuild kernel: vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none
    Nov 21 14:17:03 PingBuild kernel: vgaarb: loaded
    Nov 21 14:17:03 PingBuild kernel: vgaarb: bridge control possible 0000:00:0f.0
    Nov 21 14:17:03 PingBuild kernel: PCI: Using ACPI for IRQ routing
    Nov 21 14:17:03 PingBuild kernel: PCI: pci_cache_line_size set to 64 bytes
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: can't claim BAR 13 [io 0xf000-0xffff]: no compatible bridge window
    Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
    Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0xbfef0000-0xbfffffff]
    Nov 21 14:17:03 PingBuild kernel: NetLabel: Initializing
    Nov 21 14:17:03 PingBuild kernel: NetLabel: domain hash size = 128
    Nov 21 14:17:03 PingBuild kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Nov 21 14:17:03 PingBuild kernel: NetLabel: unlabeled traffic allowed by default
    Nov 21 14:17:03 PingBuild kernel: HPET: 16 timers in total, 0 timers will be used for per-cpu timer
    Nov 21 14:17:03 PingBuild kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
    Nov 21 14:17:03 PingBuild kernel: hpet0: 16 comparators, 64-bit 14.318180 MHz counter
    Nov 21 14:17:03 PingBuild kernel: Switched to clocksource hpet
    Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI init
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1000-0x103f] could not be reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1040-0x104f] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x0cf0-0x0cf1] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
    Nov 21 14:17:03 PingBuild kernel: system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:08: [dma 2]
    Nov 21 14:17:03 PingBuild kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0700 (active)
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [io 0x1060-0x107f] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xd0200000-0xd03fffff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI: found 10 devices
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [io 0x1000-0x0fff] to [bus 07] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [io 0x1000-0x0fff] to [bus 08] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [io 0x1000-0x0fff] to [bus 09] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [io 0x1000-0x0fff] to [bus 0a] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [io 0x1000-0x0fff] to [bus 0e] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [io 0x1000-0x0fff] to [bus 0f] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [io 0x1000-0x0fff] to [bus 10] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [io 0x1000-0x0fff] to [bus 11] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [io 0x1000-0x0fff] to [bus 12] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [io 0x1000-0x0fff] to [bus 16] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [io 0x1000-0x0fff] to [bus 17] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [io 0x1000-0x0fff] to [bus 18] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [io 0x1000-0x0fff] to [bus 19] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [io 0x1000-0x0fff] to [bus 1a] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0x1000-0x0fff] to [bus 1d] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [io 0x1000-0x0fff] to [bus 1e] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [io 0x1000-0x0fff] to [bus 1f] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [io 0x1000-0x0fff] to [bus 20] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [io 0x1000-0x0fff] to [bus 21] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [io 0x1000-0x0fff] to [bus 22] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0xd1010000-0xd101ffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bri

    Trilby wrote:
    Thanks, that all sounds correct to me, unfortunalte I can't provide more help as I've never used vmware.  But a couple pointers for pacman use:
    There is no need to use that pipe, `pacman -Q <searchterm>` will work.
    The reason you don't see the mouse package is that grep is case sensitive.  `pacman -Q | grep -i vmware` should also show the mouse package, but this would be much easier as `pacman -Qs vmware` which allows pacman to do the search.  Pacman's search is case-insensitive by default and is a bit more effient that listing all packages and grepping through them.
    Got it. Yes using the 'vmware' the vmmouse shows up. Also searching 'svga' shows Mesa DRI drivers. That is another advantage for letting pacman search, since my search term was svga and what was dispalayed did not have that in the string, pacman search can see behind the covers. :-)
    All this learning is good, now if I could just figure out why 'startx' is failing to create screen resource. ;-)
    Question, does it matter what tty it starts on? I am using 0 (obvious from the log name), could that be an issue? Just thinking out loud.

  • How to create screen resolution in bdc table control

    hi gurus
    can anyone suggest me
    how to create screen resolution in bdc table control
    thanks&regards
    mark.

    Hi ,
    Using CTU_PARAMS table for screen resolution .
    For this sample code.
    This is for Transation  FB60.
    report ZZFB60
           no standard page heading line-size 255.
    tables t100.
    PARAMETERS : p_file1  like  rlgrap-filename,
                 p_doctyp like  RF05A-BUSCS,
                 p_invdat like  INVFO-BLDAT,
                 p_posdat like  INVFO-BUDAT.
    CONSTANTS  :  C_TRANS_FB60(4) VALUE 'FB60'.
    *Parameter string for runtime of CALL TRANSACTION
    data : l_option type ctu_params,
           l_subrc type sysubrc.
    DATA :  l_mstring(150).
    data      accnt type char17.
    data       : day   type char2,
                 month type char2,
                 year  type char4,
                 date1 type char10,
                 date2 type char10.
    data      :  cnt(2) TYPE n,
                 cnt1 type i,
                 fld(25) TYPE c.
    data : begin of excel occurs 0,
            fieldname(255) type c,
           end of excel.
    DATA:BEGIN OF it_mess OCCURS 0,
             msgtyp(5),
             lms(200),
              msgv1(50),
         END OF it_mess.
    data: begin of t_record occurs 0,
             BUKRS(004),
            ACCNT(017),
            XBLNR(016),
            WRBTR1(016),
            WAERS(005),
            SECCO(004) ,
            SGTXT(050),
            HKONT(010),
            WRBTR2(017),
            MWSKZ(002),
            GSBER(004),
            KOSTL(010),
         end of t_record.
    *Internal Table for Header Data
    DATA :  BEGIN OF t_head OCCURS 0,
            BUKRS(004),      "Company Code
            ACCNT(017),      "Account or Vendor
            XBLNR(016),      "Reference
            WRBTR1(017),     "Amount in document currency
            WAERS(005),      "Currency
            SECCO(004),      "Section Code
            SGTXT(050),      "Text
            END OF t_head.
    *Internal table for Item Data
    DATA :  BEGIN OF t_item OCCURS 0,
            ACCNT(017),      "Account
            HKONT(010),     "GL Account
            WRBTR2(017),    "Line item Amount in document currency
            MWSKZ(002),     "Tax Code
            GSBER(004),     " Business Area
            KOSTL(010),     "Cost centre
            END OF t_item.
    DATA: IT_BDCDATA      LIKE  BDCDATA OCCURS 0 WITH HEADER LINE,
          IT_BDC_MESSAGES LIKE  BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
    *include bdcrecx1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
      PERFORM  file_selection.
      PERFORM  data_upload.
      PERFORM  table_control.
    start-of-selection.
    l_option-defsize = 'X'.
    l_option-dismode = 'A'.
    l_option-updmode = 'S'.
    day = p_invdat+6(2).
    month = p_invdat+4(2).
    year =  p_invdat+0(4).
    concatenate day month year into date1 SEPARATED BY '.'.
    day = p_posdat+6(2).
    month = p_posdat+4(2).
    year =  p_posdat+0(4).
    concatenate day month year into date2 SEPARATED BY '.'.
    *perform open_group.
    loop at t_head.
    CLEAR    IT_BDCDATA.
    REFRESH  IT_BDCDATA.
    perform bdc_dynpro      using   'SAPLACHD'         '1000'.
    perform bdc_field       using   'BDC_OKCODE'        '=ENTR'.
    perform bdc_field       using   'BKPF-BUKRS'        t_head-bukrs.
    perform bdc_dynpro      using   'SAPMF05A'          '1100'.
    perform bdc_field       using   'BDC_OKCODE'        '/00'.
    perform bdc_field       using   'RF05A-BUSCS'       p_doctyp.
    perform bdc_field       using   'INVFO-ACCNT'       t_head-accnt.
    perform bdc_field       using   'INVFO-BLDAT'       date1.
    perform bdc_field       using   'INVFO-BUDAT'       date2.
    perform bdc_field       using   'INVFO-XBLNR'       t_head-xblnr.
    perform bdc_field       using   'INVFO-WRBTR'       t_head-wrbtr1.
    perform bdc_field       using   'INVFO-WAERS'       t_head-waers.
    perform bdc_field       using   'INVFO-SECCO'       t_head-secco.
    perform bdc_field       using   'INVFO-SGTXT'       t_head-sgtxt.
    cnt = 1.
    cnt1 = 1.
    loop at t_item where accnt = t_head-accnt.
    *if cnt > 4.
    *cnt = 4.
    *endif.
    if cnt1 gt 1.
    CONCATENATE 'ACGL_ITEM-MARKSP(' cnt ')' INTO fld.
    perform bdc_field      using   fld                   'X'.
    perform bdc_dynpro      using 'SAPMF05A'          '1100'.
    perform bdc_field       using 'BDC_OKCODE'        '=0005'.
    endif.
    perform bdc_dynpro      using 'SAPMF05A'          '1100'.
    perform bdc_field       using   'BDC_OKCODE'        '/00'.
    CONCATENATE 'ACGL_ITEM-HKONT(' cnt ')' INTO fld.
    perform bdc_field       using  fld                t_item-hkont.
    CONCATENATE 'ACGL_ITEM-WRBTR(' cnt ')' INTO fld.
    perform bdc_field  using       fld                t_item-wrbtr2.
    CONCATENATE 'ACGL_ITEM-MWSKZ(' cnt ')' INTO fld.
    perform bdc_field       using  fld                t_item-mwskz.
    CONCATENATE 'ACGL_ITEM-GSBER(' cnt ')' INTO fld.
    perform bdc_field       using  fld                t_item-gsber.
    CONCATENATE 'ACGL_ITEM-KOSTL(' cnt ')' INTO fld.
    perform bdc_field       using  fld                t_item-kostl.
    perform bdc_field      using  'BDC_CURSOR'  fld.
    *CONCATENATE 'ACGL_ITEM-MARKSP(' cnt ')' INTO fld.
    *perform bdc_field      using   fld                   'X'.
    cnt1 = cnt1 + 1.
    *cnt = cnt + 1.
    *if cnt > 1.
    *perform bdc_dynpro      using 'SAPMF05A'          '1100'.
    *perform bdc_field       using 'BDC_OKCODE'        '=0005'.
    **perform bdc_field       using 'BDC_OKCODE'        '=0006'.
    *endif.
    endloop.
    perform bdc_dynpro      using 'SAPMF05A' '1100'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=BS'.
    perform bdc_dynpro      using 'SAPMSSY0' '0120'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=BU'.
    *perform bdc_transaction using 'FB60'.
    CALL TRANSACTION C_TRANS_FB60 USING IT_BDCDATA  options from l_option
                                 MESSAGES INTO IT_BDC_MESSAGES.
    perform error.
    perform errordownload.
    endloop.
    *perform close_group.
    *Form  data_upload
    FORM data_upload .
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
       FILENAME              =  p_file1
       FILETYPE              = 'DAT'
      TABLES
        DATA_TAB             =  t_record.
    ENDFORM.                    " data_upload
    *Form  file_selection
    FORM file_selection .
    CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          program_name  =  syst-cprog
          dynpro_number =  syst-dynnr
          field_name    = 'p_file1'
        IMPORTING
          file_name     =  p_file1.
    ENDFORM.                    " file_selection
    Form  BDC_DYNPRO
    FORM BDC_DYNPRO using program dynpro.
      CLEAR IT_BDCDATA.
      IT_BDCDATA-PROGRAM = PROGRAM.
      IT_BDCDATA-DYNPRO = DYNPRO.
      IT_BDCDATA-DYNBEGIN = 'X'.
      APPEND  IT_BDCDATA.
    endform.
    *Form  BDC_FIELD
    FORM  bdc_field using fnam fval.
      CLEAR  IT_BDCDATA.
      IT_BDCDATA-FNAM = FNAM.
      IT_BDCDATA-FVAL = FVAL.
      APPEND  IT_BDCDATA.
    ENDFORM.
    Table Control
    FORM table_control .
      LOOP AT t_record.
        ON CHANGE OF t_record-accnt.
          MOVE-CORRESPONDING t_record TO t_head.
          APPEND t_head.
        ENDON.
      loop at t_head.
             t_item-accnt   =  t_head-accnt.
             t_item-hkont   =  t_record-hkont.
             t_item-wrbtr2  =  t_record-wrbtr2 .
             t_item-mwskz   =  t_record-mwskz .
             t_item-gsber   =  t_record-gsber .
             t_item-kostl   =  t_record-kostl.
        APPEND t_item.
    endloop.
         If t_record-level = 'H'.
             t_head-bukrs   =  t_record-text1.
             t_head-accnt   =  t_record-text2.
             t_head-xblnr   =  t_record-text3.
             t_head-wrbtr1  =  t_record-text4.
             t_head-waers   =  t_record-text5.
             t_head-secco   =  t_record-text6.
             t_head-sgtxt   =  t_record-text7.
          APPEND t_head.
         else.
            t_item-accnt   =  t_head-accnt.
            t_item-hkont   =  t_record-text1.
            t_item-wrbtr2  =  t_record-text2.
            t_item-mwskz   =  t_record-text3.
            t_item-gsber   =  t_record-text4.
            t_item-kostl   =  t_record-text5.
         APPEND t_item.
         endif.
      ENDLOOP.
    ENDFORM.
    FORM error .
      LOOP AT IT_BDC_MESSAGES.
        IF IT_BDC_MESSAGES-msgtyp = 'E'.
       SELECT single  * FROM t100  WHERE
                                    sprsl = it_BDC_MESSAGES-msgspra
                                    AND   arbgb = IT_BDC_MESSAGES-msgid
                                    AND   msgnr = IT_BDC_MESSAGES-msgnr.
          IF sy-subrc = 0.
            l_mstring = t100-text.
            IF l_mstring CS '&1'.
              REPLACE '&1' WITH IT_BDC_MESSAGES-msgv1 INTO l_mstring.
              REPLACE '&2' WITH IT_BDC_MESSAGES-msgv2 INTO l_mstring.
              REPLACE '&3' WITH IT_BDC_MESSAGES-msgv3 INTO l_mstring.
              REPLACE '&4' WITH IT_BDC_MESSAGES-msgv4 INTO l_mstring.
            ELSE.
              REPLACE '&' WITH IT_BDC_MESSAGES-msgv1 INTO l_mstring.
              REPLACE '&' WITH IT_BDC_MESSAGES-msgv2 INTO l_mstring.
              REPLACE '&' WITH IT_BDC_MESSAGES-msgv3 INTO l_mstring.
              REPLACE '&' WITH IT_BDC_MESSAGES-msgv4 INTO l_mstring.
            ENDIF.
            CONDENSE l_mstring.
            it_mess-msgtyp = IT_BDC_MESSAGES-msgtyp.
            it_mess-lms = l_mstring.
            it_mess-msgv1 = IT_BDC_MESSAGES-msgv1.
            APPEND it_mess.
          ELSE.
            it_mess-msgtyp = IT_BDC_MESSAGES-msgtyp.
            it_mess-lms = l_mstring.
            it_mess-msgv1 = IT_BDC_MESSAGES-msgv1.
            APPEND it_mess.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDFORM.
    form errordownload.
    *down the internal table to excel file.
    call function 'EXCEL_OLE_STANDARD_DAT'
               EXPORTING
                    file_name                 = 'c:/Error.xls'
               TABLES
                    data_tab                  = it_mess
                    fieldnames                = excel
               EXCEPTIONS
                    file_not_exist            = 1
                    filename_expected         = 2
                    communication_error       = 3
                    ole_object_method_error   = 4
                    ole_object_property_error = 5
                    invalid_filename          = 6
                    invalid_pivot_fields      = 7
                    download_problem          = 8
                    others                    = 9.
    endform.
    Reward if useful
    Regards,
    Narasimha
    Edited by: narasimha marella on May 13, 2008 12:12 PM

  • Cannot select the newly created Screen variant in ENJOY transactions.

    Hello All,
    I have created a screen variant for a specific requirement from the client in transaction SHD0.
    However I am unable to select this new screen variant in all ENJOY transactions.
    When I try to select the screen variant in FB50-Post GL through>EDIT>Screen Variant, Select,Reset and Create Screen variants are greyyed out.
    I have checked the setting in SU3, as well as FB00 for the Parameters, it appears to be correct.
    Kindly help at the earliest!!
    Regards
    Shrutika

    Hi,
    Shrutika.
    Try this I hope this may help you.
    Go to FB50 at above left hand side will see Tree On option button. Click on that you will see Screen vairants for items option with drop down object. Simply click on that now select your desired screen variant by double clicking applied. 
    I hope this may help you to solve your issue. If you have any doubts feel free to ask.
    Regards,
    Pankaj A Bhalerao.

  • Why some screens are hiddens in BDC record mode?

    I'm trying to create a BDC record in VA01 transaction but in this mode some screens are hidden  just like screen "Material substitution(selecting a material)" Dynpro 800 Program "SAPMV45A"
    Is it possible to show this screen in BDC recorder? how can i do it?
    Regards

    Hi,
    i´m no expert in this but for a recording of material substitution you could try with transactions VB12 or VB13
    Best regards.

  • How to create screen variant in search criteria in POWL.

    Hi All,
    i have requirement to create screen data variant in POWL.
    am using standard POWL application and custom feeder class, in which i created my selection screen fields.
    User wants to save data entered in selection screen fields in the form of variant. He would like to use the variant everytime he inputs data instead of manually filling all the selection screen fields.
    Is it possible to give user an option of saving variants in POWL selection criteria.
    Thanks,
    Praveen

    hi,
    To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
    Double clicking on this exit will takes us to function builder (SE37) . This function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04 . This include will be used to write our custom code .
    Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
    e.g. E_KUNNR = 301.
    Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined customer .
    regards
    sadhu kishore

  • How to Create Personnel Area

    All HCM (HR) Community -
    I am new to SAP and I just started online training on SAP HCM...is there anyone out there who can help me with creating Personnel Area? My question is that I am trying to Create Personnel Area and I'm kind of lost in transition. I would really appreciate any help I can get.
    Regards,
    Obra

    Obra,
    Is there an existing Personnel Area to copy? If not, search though SAP web sites for direction. If so, go through the IMG as you have.
    Double click the activity u201CCopy, delete, check personnel areau201D.
    Press the u201CCopyu201D button. Press u201CEnteru201D.
    Provide the Personnel Area to be copied.
    Provide the Personnel Area to be created.
    Press u201CContinueu201D. Press u201CEnteru201D three times.
    Then SAVE.
    There will be a delay while the system copies the record.
    Press the u201CEnteru201D button.
    Press the green u201CBacku201D arrow.
    Double click the activity u201CPersonnel areasu201D.
    Press the u201CPositionu201D button near the bottom of the screen.
    Enter the newly created u201CPersonnel Areau201D, and then press u201CEnteru201D.
    Select the Personnel Area, and then press the u201CDetailsu201D button.
    Change the appropriate fields.
    Press the last button on the tool bar that resembles an envelope.
    Maintain what is required.
    Then SAVE.
    The navigation path supplied earlier also leads to Personnel Subareas, Employee Groups, and Employee Subgroups. These may already be defined. If not, you need may help brainstorming the ultimate requirements for the future. One of the things to consider is whether or not you are now or will be using the Payroll module. Personnel subareas could be used to define the shift on which an employee works if youu2019ll have people doing shift work. Employee group and subgroup fields sound like a good place to define direct and indirect employees.
    Navigate as follows to assign a Personnel Area to a Company Code:
    Enterprise Structure > Assignment > Human Resources Management > Assignment of Personnel Area to Company Code
    If you are running payroll in the US, Personnel Area is the basis for accumulating wage and tax information by legal entity. The Tax Company Code is SAP terminology for the legal entity. To assign a Personnel Area to a Tax Company Code, navigate as follows:
    Payroll > Payroll: USA > Tax > Tax Companies > Assign tax company to personnel area
    You may find the following Wiki helpful, although it doesnu2019t directly relate to creating Personnel Areas. The URL is:
    http://wiki.sdn.sap.com/wiki/display/ERPLO/SAPSDFrequentlyAskedQuestions
    Regards,
    Howard
    Edited by: Howard Gardner on Jun 29, 2011 12:55 AM

  • Someone has a tutorial for creating screen exit?

    I have a development and I do not know how to create screen exit.
    Case Someone has a tutorial for creating screen exit please help me
    Thank you
    <b><i>Wagner Duarte
    Consultant - SAP ABAP</i></b>

    hI
    Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
    1. Go to the screen>System>Status-->Program (Double
    click this program. It will take you to the program.
    2. Now, Goto-->Object Directory Entry.
    3. Make a note the package name.
    4. Now run the transactions SMOD, press F4 and enter the
    above noted package, press enter.
    5. It will display list of Exits.
    6. Now go back to the initial screen SMOD.
    7. Specify the exit name here and select the radio button
    Components.
    8. It will display four group boxes one for FM, second
    for Fcodes, thrid for Screen areas and last for
    includes.
    9. Goto transaction CMOD, create a new project, and
    click the button "Enhancement assignments" and
    specify your enhancements that you got in SMOD.
    10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
    Have a look at below link It will definately help you to undestand the same.
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    check these links.
    http://help.sap.com/saphelp_46c/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
    http://www.allsaplinks.com/screen_exit.html
    USER EXITS
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
    How to implement screen exit for a SAP standard transaction
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
    1. Go to the screen>System>Status-->Program (Double
    click this program. It will take you to the program.
    2. Now, Goto-->Object Directory Entry.
    3. Make a note the package name.
    4. Now run the transactions SMOD, press F4 and enter the
    above noted package, press enter.
    5. It will display list of Exits.
    6. Now go back to the initial screen SMOD.
    7. Specify the exit name here and select the radio button
    Components.
    8. It will display four group boxes one for FM, second
    for Fcodes, thrid for Screen areas and last for
    includes.
    9. Goto transaction CMOD, create a new project, and
    click the button "Enhancement assignments" and
    specify your enhancements that you got in SMOD.
    10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
    and you just go through these links also
    Screen exit
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    screen-exits
    Check the following link.
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all

  • Creating Screen Savers

    Can anyone tell me how to go about creating my own screen saver for MAC 0S 10.4? Do I need any special type of software to do this? What kind of files are the screen savers like "flurry". Please help.

    HI, Tim.
    Screen savers like Flurry are Quartz Compositions created with Quartz Composer. This Google search will provide you with links to a variety of Web pages discussing Quartz Composer and using it to create screen savers.
    You can use your own pictures as a screen saver: see "Mac OS X 10.4 Help: Using your own pictures as a screen saver."
    If you use iPhoto, you can make an album or a selection of photos your screen saver: see "iPhoto 6.0 Help: Making an album your screen saver."
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X

  • How to create screen shots

    hello,
    i am having one basic question. How to create screen shots.
    i have forgot the path. can anybody help immediately.

    Hii,
    If u want take the screen shot there are different free software are there eg: Screen grabber: this is very useful for grabbing the desired the area from the required screen.
    2. if u wanna take the comple screen shot then press hot key ALT + Print screen and save it in the word document. if u want add it as a saperate image paste that screen shot in the MS paint and save it as JPEG, so that the size wil in very less.
    if it is helpful, reward points.
    Regards,\
    Muralidharan

  • Updating another custom table from create screen

    Hi,
    In create screen i have some fields which has to be updated in another custom table. I created package and procedure in it and i am passing the parameters into it.But somehow it is is updating 4 filed and remaining two are not updated.
    How to check that what are the values passed in the package,so that i can find out the reason behind it.
    Kindly reply asap..

    Put some debug statement and check the root cause.
    http://oracleanil.blogspot.com/2009/04/favourite.html
    And if you are running page locally then use
    System.out.println("Test");Thanks
    --Anil
    http://oracleanil.blogspot.com

  • Screens are freezing before quiz slides

    Hi,
    I am working with a course where the screen right before a quiz slide will freeze when you click Forward and it won't load the quiz slides. It doesn't happen for every browser, but its happening for the majority (IE 10,9; all versions of Chrome).
    I'm using Captivate 7 on Windows 7 and testing in Chrome 32.
    Has anyone experienced this before? I've never seen this happen.
    Thanks,
    Kristen

    Does anyone else have any thoughts about how this could be happening? I had it happen in another course and the screens only freeze on slides right before quiz slides. Each of those slides happened to have Advanced Actions on them...the actions are there to show/hide smart shapes with text so that it acts as a button.
    Does that create any issues with the freezing?
    The quiz settings are 80% passing grade, they have 2 attempts for each quiz slide, they are only multiple choice questions, they get 10 points for correct answers...what other settings do you need to know?
    The screens are only freezing in IE10, Chrome 31, Chrome 23, and Chrome 17. It doesn't seem to be happening in IE 11, Chrome 32, or Safari. Could the older browsers be creating a problem? Or our SWF output? We're setting it at Flash Player 10.
    Thanks for any help. I can't figure this one out...
    Kristen

  • Creating Personal Area and Subarea.

    To create personal area and subarea, do i maintain them in transaction SM30 ? If yes, is there any reference on how to go about it ?

    Hi,
    can you be more precise on the requirement i.e. do you want to create Sub Screen (using module pool programing) or do you want to create a maintenanve dilog for the custom table.
    Regards,
    Raghu

  • Custom screen area for notification

    Dear Gurus ,
      As per customer requirement I need to create a screen area called Z10 , how can I create the same .I can not use existing 090 / 091 custom screen areas , since I have devoloped the custom screen in screen area 090 as well as 091 but this screen areas are calling in another transactions also (like in IW21)which I must not modify.Please suggest me asap.
    Thanks in advance
    Anil

    Not answered but closing due to lack of inputs

Maybe you are looking for