New concepts in ECC 6.0

hi,
pls make me know throuh mail id ;[email protected]

Hello Satya
I am not sure if there have been big changes regarding OO concepts. Basically all of them are already available in 4.6c.
Of course on ERP 6.0 you have many more classes and more powerful classes (in terms of methods) available.
Major differences that I am aware of are:
- RTTI (runtime type identification) " e.g. CL_ABAP_TYPEDESCR and other classes
- functional method calls " e.g. go_msglist = cf_reca_message_list=>create( ) was not possible on 4.6c
- public type definitions " I think on 4.6c only protected and private ones were possible
Regards
Uwe

Similar Messages

New BADI concept in ECC 6.0

I am trying to gain an understanding of how I would implement one of the new BADIs in ECC 6.0 (badis implmented through and enhancement spot , get badi, call badi concept).
I am not looking for information on how to implement a classic badi through se18/se19.
I have also ready through the SAP help on the new badis and it is still not clear to me. So, please do not provide links to the standard SAP help. I have that.
I am wondering if anybody has a whitepaper, example, etc. that explains the details of how to implement, use, trigger the new badis linked to an enhancement spot.

Hi J.J,
enhancement spot
A repository object for the administration of explicitly created enhancement options. Enhancement spots are components of a tree structure hierarchy, of which the branches represent composite enhancement spots and the leaves are simple enhancement spots. Implicitly available enhancement options do not have any enhancement spots.
composite enhancement spot
Semantic combination of simple and other composite enhancement spots with the aim of providing structure.
simple enhancement spot
Reference to a set of enhancement spot element definitions. A simple enhancement spot can occur independently or as a component of a composite enhancement spot.
ENHANCEMENT-POINT
Defines a position in an ABAP program as an enhancement option,
at which one or more source code plug-ins can be inserted.
the syntax will be like
ENHANCEMENT-POINT enh_id SPOTS spot1 spot2 ...
STATIC
INCLUDE BOUND.
Enhancement Options
Definition
Enhancement options are positions in Repository objects where enhancements can be made. These options are either explicitly defined (by the developer) or exist implicitly. Explicit enhancement options are generally defined in a central initial system. Enhancements are made in follow-on systems.
Use
Explicit enhancement options can currently be defined by:
1. Explicitly flagging source code points or sections in ABAP programs. For an enhancement, these can be enhanced or replaced by source code plug-ins.
2. Including Business Add-Ins (BAdIs) in ABAP programs. These programs are then enhanced by object plug-ins with predefined interfaces.
Explicit enhancement options are managed by enhancement spots and enhanced by enhancement implementations.
Currently, implicit enhancement options are:
1. Specific options in ABAP programs such as the end of the program which can be enhanced by source code plug-ins.
2. Parameter interfaces of function modules, which can be enhanced with parameters.
3. Attributes and parameter interfaces of global classes, which can be enhanced with attributes or parameters.
Implicit enhancement options always exist and do not require enhancement spots. They are also enhanced by enhancement implementations.
BAdIs Embedded in the Enhancement Concept
Use
The definition of BAdIs is managed by enhancement spots. A simple enhancement spot for BAdIs can contain several BAdI definitions as enhancement spot element definitions. BAdIs that would otherwise be spread out in the system can be grouped together semantically.
This structuring is mirrored on the implementation side through the enhancement implementations. A BAdI can be implemented by several BAdI implementations that are managed by enhancement implementations. A simple enhancement implementation for object plug-ins can contain several BAdI implementations of an enhancement spot as enhancement implementation elements and can implement a BAdI multiple times. Therefore, several enhancement implementations can be assigned to one enhancement spot.
A BAdI is always assigned to the same package, like the enhancement spot, to which it belongs.
Example
The structuring features of BAdIs in enhancement spots can be of a technical or a subject nature.
If, in the definition of several BAdIs, you have the provision that they are to be used in the same context (this is a feature known only by the person who defines the BAdIs), they must be used by the same simple enhancement spot.
From a subject point of view, all BAdIs must then be grouped together by affiliation to functional units for example, payroll in combined enhancement spots.
Thanks and regards
suma sailaja pvn

New functionality in ECC 6.0 with Enhancement Package 3

Hi Experts,
Can any one tell me what new functionality is added in Enhancement package 3 (ECC 6.0)?
Thanks & Regards,
Simar

Hi,
There no new functionality in ECC 6.0 for auto clearing of bank clearing account. Still you need to depend on Manual / Electronic bank statement to clear them.
Thanks
Prasada

New functionality in ECC 6.0 and problems during sap implementation

Dear Gurus,
may i know the details of the New functionality in ECC 6.0 on (MM,SD,PP,QM,PS,HR,PM,FI/CO,BI,XI,DMS ) or what is the problems coming at the time of implementation of ECC 6.0.
THANKS AND REGARDS
RS

Ritesh,
Question is bit confusing
may i know the details of the New functionality in ECC 6.0 on (MM,SD,PP,QM,PS,HR,PM,FI/CO,BI,XI,DMS )
That means you are going to upgarde from some earlier version .what is that version ?
Then you might find some specific information at
https://websmp102.sap-ag.de/uda -
>Upgrade Dependency Analyzer
what is the problems coming at the time of *implementation* of ECC 6.0.
If its a new implemenation you will not face problem , but you need to configure everything accordingly.
Problem depends upon what all you are using from standard and customizing.
Above provided link will help you.
Just add up
http://wiki.sdn.sap.com/wiki/display/ERPLO/NewfunctionalityinECC6.0%28+MM%29
Regards,

New functionality in ECC 6.0 for auto clearing of bank clearing account.

Is there any new functionality in ECC 6.0 for auto clearing of bank clearing account.
Regards,
Kishore

Hi,
There no new functionality in ECC 6.0 for auto clearing of bank clearing account. Still you need to depend on Manual / Electronic bank statement to clear them.
Thanks
Prasada

How to get murrine dust theme to work? (new concept theme for ubuntu)

hello!
i just want to try and install the new concept theme for ubuntu - DustTheme!
but i don't get it to work. it uses the murrine-engine - but when i want to select it via gtk-chtheme or gtk2_prefs it does not sets the colors or anything else. when i hit apply, the standard ugly gtk-theme will be selected.
anyone here who actually uses the theme?
more information:
DustTheme Ubuntu Wiki
installed packages:
gtk-engine-murrine 0.53.1
also tried: gtk-engine-murrine-svn rev 94
please help, thanks...
bye iggy
Last edited by iggy (2008-10-22 10:04:48)

andrek wrote:There's a difference between the new SVN version of the Murrine engine and the Dust theme - you've got to change "profile" into "style" in theme's gtkrc file.
Hrm, I'm not quite sure what you mean. I don't see "profile" anywhere in the gtkrc - everything seems to be labeled as "style" already.
# Dust theme
# by Rico Sta. Cruz and Ricardo (Kido) Mariano III
# Last rev: Oct 4
# Set GtkSettings color scheme property.
# This can be overriden (via an xsetting) with eg. the gnome-appearance-properties.
#gtk_color_scheme = "fg_color:#323232\nbg_color:#e4e0d8\nbase_color:#fff\ntext_color:#323232\nselected_bg_color:#996B5C\nselected_fg_color:#fff\ntooltip_bg_color:#ebeab8\ntooltip_fg_color:#323232"
gtk_color_scheme = "fg_color:#323232\nbg_color:#D9D4CC\nbase_color:#fff\ntext_color:#323232\nselected_bg_color:#996B5C\nselected_fg_color:#fff\ntooltip_bg_color:#ebeab8\ntooltip_fg_color:#323232"
include "scrollbars/scrollbar.rc"
style "murrine-default"
# Style Properties
GtkScrolledWindow ::scrollbar-spacing = 3
GtkScrolledWindow ::scrollbar-within-bevel = 1
GtkButton ::child-displacement-x = 1
GtkButton ::child-displacement-y = 1
GtkButton ::default-border = { 0, 0, 0, 0 }
GtkButton ::focus-padding = 0
GtkCheckButton ::indicator-size = 14
GtkPaned ::handle-size = 6
GtkRange ::trough-border = 0
GtkRange ::slider-width = 15
GtkRange ::stepper-size = 15
GtkScale ::slider-length = 20
GtkScale ::trough-side-details = 0 # 0 = thin slider, >0 = thick slider
GtkScrollbar ::min-slider-length = 30
GtkMenuBar ::internal-padding = 0
GtkExpander ::expander-size = 16
GtkToolbar ::internal-padding = 1
GtkTreeView ::expander-size = 14
GtkTreeView ::vertical-separator = 0
GtkMenu ::horizontal-padding = 0
GtkMenu ::vertical-padding = 0
WnckTasklist ::fade-overlay-rect = 0
xthickness = 1
ythickness = 1
fg[NORMAL] = @fg_color
fg[PRELIGHT] = @fg_color
fg[SELECTED] = @selected_fg_color
fg[ACTIVE] = @fg_color
fg[INSENSITIVE] = darker (@bg_color)
bg[NORMAL] = @bg_color
bg[PRELIGHT] = shade (1.02, @bg_color)
bg[SELECTED] = @selected_bg_color
bg[INSENSITIVE] = @bg_color
bg[ACTIVE] = shade (0.9, @bg_color)
base[NORMAL] = @base_color
base[PRELIGHT] = shade (0.95, @bg_color)
base[ACTIVE] = shade (0.9, @selected_bg_color)
base[SELECTED] = @selected_bg_color
base[INSENSITIVE] = @bg_color
text[NORMAL] = @text_color
text[PRELIGHT] = @text_color
text[ACTIVE] = @selected_fg_color
text[SELECTED] = @selected_fg_color
text[INSENSITIVE] = darker (@bg_color)
engine "murrine"
animation = TRUE # FALSE = disabled, TRUE = enabled
colorize_scrollbar = TRUE # FALSE = disabled, TRUE = enabled
contrast = 1.0 # 0.8 for less contrast, more than 1.0 for more contrast on borders
glazestyle = 0 # 0 = flat highlight, 1 = curved highlight, 2 = concave style, 3 = top curved highlight, 4 = beryl highlight
gradient_shades = {1.1,1.0,1.0,0.87} # default: {1.1,1.0,1.0,1.1}
gradients = TRUE # FALSE = disabled, TRUE = enabled
highlight_ratio = 1.0 # set highlight amount for buttons or widgets
lightborder_ratio = 1.0 # sets lightborder amount for buttons or widgets
lightborderstyle = 0 # 0 = lightborder on top side, 1 = lightborder on all sides
listviewheaderstyle = 1 # 0 = flat, 1 = glassy, 2 = raised
listviewstyle = 0 # 0 = nothing, 1 = dotted
menubaritemstyle = 0 # 0 = menuitem look, 1 = button look
menubarstyle = 1 # 0 = flat, 1 = glassy, 2 = gradient, 3 = striped
menuitemstyle = 1 # 0 = flat, 1 = glassy, 2 = striped
menustyle = 0 # 0 = no vertical menu stripe, 1 = display vertical menu stripe
reliefstyle = 2 # 0 = flat, 1 = inset, 2 = shadow
rgba = FALSE # FALSE = disabled, TRUE = enabled
roundness = 2 # 0 = squared, 1 = old default, more will increase roundness
scrollbarstyle = 2 # 0 = nothing, 1 = circles, 2 = handles, 3 = diagonal stripes, 4 = diagonal stripes and handles, 5 = horizontal stripes, 6 = horizontal stripes and handles
sliderstyle = 0 # 0 = nothing added, 1 = handles
stepperstyle = 1 # 0 = standard, 1 = integrated stepper handles, 2 = unknown
style = MURRINE # engine style options: CANDIDO, CLEARLOOKS, MIST, MURRINE, NODOKA
toolbarstyle = 0 # 0 = flat, 1 = glassy, 2 = gradient
style "murrine-wide"
xthickness = 2
ythickness = 2
style "murrine-wider"
xthickness = 3
ythickness = 3
style "murrine-dark"
bg[NORMAL] = shade(0.24,@bg_color)
bg[SELECTED] = shade(0.9,@selected_bg_color)
bg[PRELIGHT] = shade (0.5, @selected_bg_color)
bg[ACTIVE] = mix (0.5, @selected_bg_color, shade(0.2,@bg_color))
bg[INSENSITIVE] = shade(0.2,@bg_color)
fg[NORMAL] = mix (0.7, '#ffffef', @fg_color)
fg[PRELIGHT] = mix (0.8, '#ffffef', @fg_color)
fg[SELECTED] = mix (0.8, '#ffffef', @fg_color)
fg[ACTIVE] = mix (0.8, '#ffffef', @fg_color)
fg[INSENSITIVE] = mix (0.4, '#ffffef', @fg_color)
style "murrine-button"
xthickness = 3
ythickness = 3
bg[NORMAL] = shade (1.2, @bg_color)
bg[PRELIGHT] = shade (0.9, @bg_color) #mix(0.82,shade (1.3, @bg_color),@selected_bg_color)
bg[ACTIVE] = shade (0.85, @bg_color)
# SZ07: button engine changed to clearlooks.
# Change back to murrine to get the old dotted focus ring.
engine "clearlooks" {
contrast = 1.0
radius = 2.0
style = GUMMY
reliefstyle = 1
style "murrine-toolbar" = "murrine-default"
xthickness = 4
ythickness = 3
bg[NORMAL] = shade(0.88,@bg_color)
bg[PRELIGHT] = shade(0.88,@bg_color)
bg[ACTIVE] = shade(0.88,@bg_color)
bg[SELECTED] = shade(0.88,@bg_color)
bg[INSENSITIVE] = shade(0.88,@bg_color)
fg[NORMAL] = @text_color
fg[PRELIGHT] = @text_color
fg[SELECTED] = @text_color
fg[ACTIVE] = @text_color
fg[INSENSITIVE] = @text_color
fg[NORMAL] = @text_color
text[NORMAL] = @text_color
#engine "murrine" {
# gradient_shades = {1.1,1.0,1.0,0.85}
engine "pixmap"
image {
function = BOX
file = "toolbar_light.png"
border = {1,1,1,1}
image {
function = HANDLE
overlay_file = "handlebox.png"
overlay_stretch = FALSE
orientation = HORIZONTAL
image {
function = HANDLE
overlay_file = "handlebox.png"
overlay_stretch = FALSE
orientation = VERTICAL
style "murrine-toolbar-item" = "murrine-toolbar"
bg[NORMAL] = shade(0.88,@bg_color)
bg[PRELIGHT] = shade(1.1,@bg_color)
bg[ACTIVE] = shade(0.6,@bg_color)
fg[INSENSITIVE] = shade(0.6,@bg_color)
fg[ACTIVE] = @selected_fg_color
text[ACTIVE] = @selected_fg_color
engine "clearlooks" {
contrast = 1.0
radius = 2.0
style = GUMMY
reliefstyle = 1
style "murrine-toolbar-sep" = "murrine-toolbar-item"
bg[NORMAL] = shade(0.5, @bg_color)
style "murrine-dark-toolbar" = "murrine-dark"
xthickness = 6
bg[PRELIGHT] = mix (0.3, @selected_bg_color, shade(0.2,@bg_color))
bg[SELECTED] = mix (0.3, @selected_bg_color, shade(0.2,@bg_color))
bg[ACTIVE] = mix (0.5, @selected_bg_color, shade(0.2,@bg_color))
engine "murrine"{
gradient_shades = {1.3,1.1,1.1,0.9}
style = MURRINE
style "murrine-dark-toolbar-sep" = "murrine-dark-toolbar"
{ xthickness = 2 }
style "pixmap-dark-toolbar" = "murrine-dark-toolbar"
# To-do: make the toolbar recolorable, possibly without using pixmaps
# We only like this because of the top line, anyway.
engine "pixmap"{
image {
function = BOX
file = "toolbar_o.png"
border = {1,1,1,1}
image
function = HANDLE
overlay_file = "handlebox.png"
overlay_stretch = FALSE
orientation = HORIZONTAL
image
function = HANDLE
overlay_file = "handlebox.png"
overlay_stretch = FALSE
orientation = VERTICAL
style "murrine-notebook-bg" = "murrine-default"
bg[NORMAL] = shade (1.05, @bg_color)
bg[SELECTED] = shade (1.05, @bg_color)
xthickness = 2
style "murrine-notebook" = "murrine-notebook-bg"
xthickness = 2
style "murrine-tasklist"
xthickness = 3
ythickness = 3
style "murrine-panel" = "murrine-dark" {
bg[NORMAL] = shade (0.15, @bg_color)
engine "murrine" {
style "murrine-menu" = "murrine-dark"
xthickness = 0
ythickness = 2
bg[NORMAL] = shade (0.15, @bg_color)
text[NORMAL] = @bg_color
text[PRELIGHT] = @selected_fg_color
style "murrine-menu-item" = "murrine-dark"
xthickness = 0
ythickness = 3
engine "murrine" {
roundness = 0
contrast = 0.2
gradient_shades = {1.0,0.9,0.9,0.7}
style "murrine-separator-menu-item"
GtkSeparatorMenuItem::horizontal-padding = 0
GtkWidget::wide-separators = 1
GtkWidget::separator-width = 1
GtkWidget::separator-height = 1
xthickness = 1
ythickness = 0
style "murrine-treeview"
# Based on the default style so that the colors from the button
# style are overriden again.
style "murrine-treeview-header" = "murrine-default"
xthickness = 2
ythickness = 1
bg[NORMAL] = shade(0.9, @bg_color)
bg[PRELIGHT] = shade(1.0, @bg_color)
bg[ACTIVE] = shade(0.8, @bg_color)
GtkWidget::focus-line-width = 0
engine "murrine" {
gradient_shades = {1.3,1.0,1.0,1.1}
style = MURRINE
contrast = 0.5
glazestyle = 1
listviewheaderstyle = 1
# SZ07: This is added to tell the theme how to color checkmarks and radio items that are not in menus.
style "murrine-radiocheck" = "murrine-default"
text[NORMAL] = shade (1.15, @bg_color) # Color for checks/radio items.
text[PRELIGHT] = @selected_fg_color # Color for selected checks/radio items.
engine "murrine"{
style "murrine-tooltips"
xthickness = 4
ythickness = 4
bg[NORMAL] = @tooltip_bg_color
fg[NORMAL] = @tooltip_fg_color
style "murrine-progressbar"
xthickness = 1
ythickness = 1
fg[PRELIGHT] = @selected_fg_color
engine "murrine"
style = NODOKA
#I want my shiny progressbar!
#gradient_shades = {1.3,1.1,0.9,1.0}
style "pixmap-statusbar" = "murrine-default"
ythickness = 3
xthickness = 3
engine "pixmap"
image
function = RESIZE_GRIP
recolorable = TRUE
detail = "statusbar"
overlay_file = "statusgrip.png"
overlay_border = {0,0,0,0}
overlay_stretch = TRUE
image
function = SHADOW
shadow = IN
file = "blank.png"
image
function = SHADOW
shadow = OUT
file = "blank.png"
image
function = SHADOW
shadow = ETCHED_IN
file = "blank.png"
image
function = SHADOW
shadow = ETCHED_OUT
file = "blank.png"
style "murrine-comboboxentry"
style "murrine-spinbutton"
style "murrine-scale"
bg[PRELIGHT] = shade(0.9,@bg_color)
engine "murrine"{
gradient_shades = {1.3,1.1,0.9,1.0}
style "murrine-hscale" = "murrine-scale"
style "murrine-vscale" = "murrine-scale"
style "murrine-scrollbar"
bg[ACTIVE] = "#fff"
bg[NORMAL] = @bg_color
bg[PRELIGHT] = shade(0.9,@bg_color)
engine "murrine"{
gradient_shades = {1.1,1.0,1.0,0.9}
contrast = 1.4
style "murrine-hscrollbar" = "murrine-scrollbar"
style "murrine-vscrollbar" = "murrine-scrollbar"
style "murrine-menubar" = "murrine-dark"
engine "murrine"{
gradient_shades = {1.0,0.9,0.9,0.75}
style "murrine-frame"
#Uncomment for dark statusbars. Breaks some apps.
#bg[ACTIVE] = shade(0.2,@bg_color)
#fg[NORMAL] = mix (1.5, @fg_color, '#ffffff')
#fg[PRELIGHT] = mix (1.4, @fg_color, '#ffffff')
style "murrine-frame-title" = "murrine-frame"
fg[NORMAL] = lighter (@fg_color)
style "murrine-nautilus-location"
bg[NORMAL] = mix(0.60, shade (1.05,@bg_color), @selected_bg_color)
# Matches
# murrine default style is applied to every widget
class "GtkWidget" style "murrine-default"
# Increase the x/ythickness in some widgets
class "GtkRange" style "murrine-default"
class "GtkFrame" style "murrine-frame"
class "GtkSeparator" style "murrine-wide"
class "GtkEntry" style "murrine-wider"
class "GtkStatusbar" style "pixmap-statusbar"
class "GtkMenuBar" style:highest "murrine-menubar"
# Toolbar default: dark
#class "*HandleBox" style "pixmap-dark-toolbar"
#class "GtkToolbar" style "pixmap-dark-toolbar"
#widget_class "*HandleBox" style "pixmap-dark-toolbar"
#widget_class "*<GtkToolbar>.*" style "murrine-dark-toolbar"
# Toolbar default: light
class "*HandleBox" style "murrine-toolbar"
class "GtkToolbar" style "murrine-toolbar"
widget_class "*HandleBox" style "murrine-toolbar"
widget_class "*<GtkToolbar>.*" style "murrine-toolbar-item"
# Place this fix far above so overrides work better
# Affects: gedit sidebar, GCstar, meld
style "murrine-toolbar-flat"
engine "murrine"
toolbarstyle = 0
widget_class "*.*.*.*.*.*Toolbar*" style "murrine-toolbar-flat"
widget_class "*.*.*.*.*.*HandleBox*" style "murrine-toolbar-flat"
# Toolbar exceptions:
# Browser-type and viewer-type applications get a dark toolbar.
# Everything below the toolbar for these apps are the content. This will make
# a separation on function (toolbar) and content (client area).
# Work around for http://bugzilla.gnome.org/show_bug.cgi?id=382646
style "murrine-text-is-fg-color-workaround"
text[NORMAL] = @fg_color
text[PRELIGHT] = @fg_color
text[SELECTED] = @selected_fg_color
text[ACTIVE] = @fg_color
text[INSENSITIVE] = darker (@bg_color)
widget_class "*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround"
style "murrine-text-is-fg-color-workaround-dark"
#Make it work with this theme!
text[NORMAL] = mix (1.5, @fg_color, '#ffffff')
text[PRELIGHT] = mix (1.4, @fg_color, '#ffffff')
# Nautilus toolbar: dark
widget_class "*Nautilus*Toolbar*" style "pixmap-dark-toolbar"
widget_class "*Nautilus*Tool*GtkButton" style "murrine-dark-toolbar"
widget_class "*Nautilus*Tool*.*.*" style "murrine-dark-toolbar"
widget_class "*Nautilus*Tool*GtkToggleButton" style "murrine-dark-toolbar"
widget_class "*Nautilus*Tool*Separator*" style "murrine-dark-toolbar-sep"
widget_class "*Nautilus*Tool*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
# Evince/EOG: dark
widget_class "*EggEditable*Toolbar*" style "pixmap-dark-toolbar"
widget_class "*EggEditable*Toolbar*.*.*.*" style "murrine-dark-toolbar"
widget_class "*EggEditable*Tool*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
widget "*fullscreen-toolbar" style "pixmap-dark-toolbar"
widget "*fullscreen-toolbar.*" style "murrine-dark-toolbar"
# Epiphany: dark
widget_class "*EphyToolbar*" style "pixmap-dark-toolbar"
widget_class "*EphyToolbar*.*.*.*" style "murrine-dark-toolbar"
widget_class "*EphyTool*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
# F-Spot(?): dark
widget_class "*Spot*Toolbar*" style "pixmap-dark-toolbar"
widget_class "*Spot*Toolbar*.*.*.*" style "murrine-dark-toolbar"
widget_class "*Spot*Toolbar*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
# Gedit: Dark
widget_class "*edit*Toolbar*" style "pixmap-dark-toolbar"
widget_class "*edit*Toolbar*.*" style "murrine-dark-toolbar"
widget_class "*edit*Toolbar*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
# Brasero: Dark
widget_class "*rasero*Toolbar*" style "pixmap-dark-toolbar"
widget_class "*rasero*Toolbar*.*" style "murrine-dark-toolbar"
widget_class "*rasero*Toolbar*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
#gThumb: dark
widget_class "*Gth*Toolbar*" style "pixmap-dark-toolbar"
widget_class "*Gth*Toolbar*.*" style "murrine-dark-toolbar"
widget_class "*Gth*Toolbar*.<GtkComboBox>.<GtkCellView>" style "murrine-text-is-fg-color-workaround-dark"
widget_class "*GthFull*" style "pixmap-dark-toolbar" #Doesn't work
class "GtkSpinButton" style "murrine-spinbutton"
class "GtkScale" style "murrine-scale"
class "GtkVScale" style "murrine-vscale"
class "GtkHScale" style "murrine-hscale"
class "GtkScrollbar" style "murrine-scrollbar"
class "GtkVScrollbar" style "murrine-vscrollbar"
class "GtkHScrollbar" style "murrine-hscrollbar"
class "GtkButton" style "murrine-button"
class "GtkRadioButton*" style "murrine-radiocheck" # SZ07: Added for the checkmarks/radio
class "GtkCheckButton" style "murrine-radiocheck" # SZ07: Added for the checkmarks/radio
# General matching following, the order is choosen so that the right styles override each other
# eg. progressbar needs to be more important then the menu match.
widget_class "*<GtkNotebook>*<GtkEventBox>" style "murrine-notebook-bg"
widget_class "*<GtkNotebook>*<GtkDrawingArea>" style "murrine-notebook-bg"
widget_class "*<GtkNotebook>*<GtkLayout>" style "murrine-notebook-bg"
widget_class "*<GtkNotebook>" style "murrine-notebook"
widget_class "*<GtkComboBoxEntry>*" style "murrine-comboboxentry"
widget_class "*<GtkCombo>*" style "murrine-comboboxentry"
widget_class "*<GtkMenu>*" style "murrine-menu"
widget_class "*<GtkMenuItem>*" style "murrine-menu-item"
widget_class "*<GtkSeparatorMenuItem>*" style "murrine-separator-menu-item"
widget_class "*<GtkFrame>" style "murrine-frame"
widget_class "*.<GtkFrame>.<GtkLabel>" style "murrine-frame-title"
widget_class "*.<GtkTreeView>*" style "murrine-treeview"
widget_class "*<GtkStatusbar>*" style "murrine-wider"
widget_class "*<GtkProgressBar>" style "murrine-progressbar"
# Treeview header
widget_class "*.<GtkTreeView>.<GtkButton>" style "murrine-treeview-header"
widget_class "*.<GtkCTree>.<GtkButton>" style "murrine-treeview-header"
widget_class "*.<GtkList>.<GtkButton>" style "murrine-treeview-header"
widget_class "*.<GtkCList>.<GtkButton>" style "murrine-treeview-header"
#Panel
widget "*PanelWidget*" style "murrine-panel"
widget "*PanelApplet*" style "murrine-panel"
widget "*fast-user-switch*" style "murrine-panel" # Workaround for Fast User Switch applet
class "PanelApp*" style "murrine-panel"
class "PanelToplevel*" style "murrine-panel"
#The panel menubar
widget_class "*Panel*<GtkMenuBar>*" style:highest "murrine-panel"
# The window of the tooltip is called "gtk-tooltip"
widget "gtk-tooltip*" style "murrine-tooltips"
# Special cases and work arounds
# Workarounds for Evolution
widget_class "*.ETable.ECanvas" style "murrine-treeview-header"
widget_class "*.ETree.ECanvas" style "murrine-treeview-header"
#Firefox isn't nice to dark themes, so unset the dark stuff.
widget "MozillaGtkWidget*Toolbar*" style "murrine-default"
#widget "MozillaGtkWidget*Frame*" style "murrine-default"
#Thunderbird too. But since Thunderbird uses the same theming engine as FF2, things are worse for us.
style "murrine-menuitem-text-is-fg-color-workaround"
#text[NORMAL] = @fg_color
#text[PRELIGHT] = @selected_fg_color
#text[SELECTED] = @selected_fg_color
#text[ACTIVE] = @fg_color
#text[INSENSITIVE] = darker (@bg_color)
#Make it work with this theme!
text[NORMAL] = mix (1.5, @fg_color, '#ffffff')
text[PRELIGHT] = mix (1.4, @fg_color, '#ffffff')
widget "*.gtk-combobox-popup-menu.*" style "murrine-menuitem-text-is-fg-color-workaround"
# Work around the usage of GtkLabel inside GtkListItems to display text.
# This breaks because the label is shown on a background that is based on the
# base color set.
style "murrine-fg-is-text-color-workaround"
fg[NORMAL] = @text_color
fg[PRELIGHT] = @text_color
fg[ACTIVE] = @selected_fg_color
fg[SELECTED] = @selected_fg_color
fg[INSENSITIVE] = darker (@bg_color)
widget_class "*<GtkListItem>*" style "murrine-fg-is-text-color-workaround"
# The same problem also exists for GtkCList and GtkCTree
# Only match GtkCList and not the parent widgets, because that would also change the headers.
widget_class "*<GtkCList>" style "murrine-fg-is-text-color-workaround"
style "murrine-evo-new-button-workaround"
engine "murrine"
toolbarstyle = 0
widget_class "EShellWindow.GtkVBox.BonoboDock.BonoboDockBand.BonoboDockItem*" style "murrine-evo-new-button-workaround"
#Rhythmbox toolbar near the search entry. Use default + wide so that it doesn't turn dark.
style "murrine-rhythmbox-header" = "murrine-default"
xthickness = 3
ythickness = 3
engine "murrine" {
widget "*RBSourceHeader*" style:highest "murrine-rhythmbox-header"
widget "*swt*toolbar*" style "murrine-default"
# RSC: Fix for CPU frequency applet
style "applet-text" = "murrine-panel"
fg[NORMAL] = @bg_color
widget_class "*CPUFreqApplet*" style:highest "applet-text"
style "murrine-dialog" = "murrine-dark"
bg[NORMAL] = mix(0.4, @selected_bg_color, shade(0.7, @bg_color))
fg[NORMAL] = shade(0.5, @fg_color)
text[NORMAL] = shade(0.5, @text_color)
style "murrine-dialog-button" = "murrine-dark"
bg[NORMAL] = shade(0.15, @bg_color)
bg[PRELIGHT] = shade(0.18, @bg_color)
# Dialog boxes...?
# widget_class "*Dialog*" style "murrine-dialog"
# widget_class "*Dialog*.*" style "murrine-dialog"
# widget_class "*Dialog*.*Button*" style "murrine-dialog-button"

New tcodes in ECC 6.0 for obsolete tcodes in 4.6C

We are doing security upgrade from 4.6C to ECC 6.0.
There are some tcodes have been deleted in ECC 6.0, but I don't which new tcodes will replace them.
I am looking for the new tcodes in ECC 6.0 for list of tcodes in 4.6C (below) which have been deleted in ECC 6.0:
AL02, AL08, AL10, AL18, AL21, AL22, CN90, CN92, CN94, KSRP, SAPSAP_IA,
SB02, SO80, ST08, S_P9C_18000155, S_P9C_18000155
Note: i verify the table PRGN_CORR2 in ECC 6.0, and the list provides from OSS note 991377, however both of them not include those tcodes I mention above.
Your input with the new tcodes, that replace the tcodes above, will be appreciated.
Thank you
Steve

Hi,
This thread may help you with the required information.
Re: TCode set for ECC6.0 compared to 4.7
Rgds,
Raghu Boddu

What's new in SAP ECC version(Technically)

Hi ALL,
iam and ABAPer new to SAP ECC version.
can u post me th document related to SAP ECC version (what are the technical changes in ECC& Syntax change in ECC)
thank u

Hi,
Welcome to SDN!
In SE38, click the blue icon (Information) with the "I" in it.
Click "New Features in ABAP".
There should be a subfolder there which says "ABAP Changes by Release".
There is also a very good document from Thomas Jung here in the SDN
that contain a lot of hardcopies of the changes.
/people/thomas.jung3/blog/2005/05/15/abap-46c-to-640-delta-training
Also, check the following threads:
Re: ABAP Changes for release ECC 5.0
Re: Technical difference between 4.7 and ECC 5.0
best regards,
Thangesh

New Concepts

Hello All
I am just curious to know the latest Happenings in BASIS module.What new concepts have come up after Solman and EHP??

Hi,
These days mostly basis people talk about HANA and Cloud computing.
-Sanjay

Want to learn new concepts, Help...

Hi
I am good in oracle up to version 7.x.
After 7.x there are many new concepts have come in
8, 8i, 9i, 10g ...
Coming to D2K, upto forms5.0,reports3.0 I am OK, again
later versions 6, 6i, 9i, etc...
How do I train my self on these new concepts right from
table partitioning to all new concepts?
I am looking for some sort of documents which will have examples for practicing.. Please guide me in this
Thanks
Sai

The various new features guides on http://tahiti.oracle.com are probably good places to start looking. Most will have an example or two for many of the newer features.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

How is 9iJD able to run this much Faster? Any new concept ur using. Please Tell Us...

We are very much eager to see the production release of 9iJD. When will it be available for Download?
How is 9iJD is running this much Faster? Any new concept uve used to develop this. Please let us know the Java Community. Its much faster than any application developed with Microsoft Tools or even VB/VC++...
Yours,
Sankar.B

Please see:
http://technet.oracle.com:89/ubb/Forum104/HTML/000054.html
thanks.

New concept performance

Hi, all
Can you describe difference in performance when using 3.x emulated and migrated DS and old and new concept IS?
It is very important for us because we start new project on 2004s, and should choose Data flow concept.
Loads of large amount of data are supposed.

In general, I would choose the new data flow concept as it has tons of benefits over the old concept. The performance while loading, in general, is more parallelized with the new data flow, so you will generally get a ton better performance. You can run some tests if you need numbers, but I think you'll find the new data flow concept a ton better to work with.

New GL Concept in ECC 6

Hi Friends,
Could you please can any one explain me new GL concept in ECC6
Thanks & Regards,
Vas
Moderator: Please, search SDN

Hi,
Please go thru the below mentioned link.
http://help.sap.com/saphelp_erp60/helpdata/en/29/830e405c538f5ce10000000a155106/content.htm
Also you can refer the document AC210 - New General Ledger Accounting
Best Regards,
Madhu

New Features in ECC 6.0

Dear Experts,
I was just going through the latest release notes of SAP ERP Central Component (Release 6.0). I would request you to explain the concept of a couple of new features that am listing below, in the simplest possible way. I need to give a presentation to one of our clients regarding the same and would like to explain them the concepts of these new features in a manner in which they can easily understand it.
My queries are listed below. Kindly respond.
1) What is the concept of iPPE? How doest it work in conjuction with PS? How to best explain the concept of iPPE for a layman to understand?
2) Easy Cost Planning has been enhanced with the following new features,
a) Aggregated Items & b) Archiving
What is the concept for these new features? What are the clarifications that need to be given in order to use these new features?
Waiting for all you experts to respond.
Thanks in advance.
Regards,
Gokul

Dear Gokul,
I can answer to one part
iPPE and PS can be integrated so that there will be logical link between objects in PVS (Product Varient Strucutre) and Project in PS.
there n:n relationship between WBS element and iPPE node , also betn Network and iPPE nodes/varients.
Use can use data from iPPE for project procurements.
Using reference points you can tranfer material from iPPE structure to PS Network.
Thanks,
Niketan

Migrating SU24 to new system properly (ecc 5.0 to ecc 6.0)

Hello,
We are currently upgrading from ECC 5.0 to 6.0. As part of this cutover to the new system, I need to download SU24 properly from the 5.0 system and upload it to the new 6.0 environment because we heavily use SU24 for custom tcodes and to add additional auth objects to SAP delivered transactions.
The good thing is that SU24 has a download capability in the transaction, but the problem is that it gives you three option of downloads, in which all three can be selected.
1) SAP Data
2) Original Data
3) Customer Data
I know that we will obviously want to use the "Customer Data" due to our Ztcodes, but what is the difference between SAP Data and Original Data?
Our goal would be to download and upload only our custom changes (to both custom transactions and SAP transactions), but we do not want to overwrite any newly delivered SU24 updates that SAP may have implemented in ECC 6.0.
Has anyone ever done this or does anyone have an idea what these mean? Of course, the SAP help is useless on this issue.
I looked for such messages and read them here, I guess I still have some anxiety about ensuring that I download only what my company has maintained since our older 5.0 system went live. If I download all of the "Customer Data" option, I think that covers all of our custom transaction codes, but will that cover the auth objects associations to SAP delived tcodes we have made as well?
Also, It seems that I will have to use SU25 to activate. Any information of the best way to to do this our situation would be greatly appreciated!
Thanks,
Ryan

Thanks for responding.
The thing is that the person asking the questions does not give a hoot about points until they have an answer, and then only maybe... so forget about points.
Answering questions with random links or wild guesses in the hope that one of them scores a few points makes a big mess of the forums and renders the search almost useless when all these link-farms turn up.
Take a look at this thread for an extreme example => work flow
It is okay to post a link when there is a good reason for it, embedded within a discussion or to support an answer as a reference.
Please take a look at this thread for a more detailed discussion => How Far it is Good???
Now, back to the discussion...
I am not logged on, but if I remember correctly there is a function module which uses combinations of these three flags to read the SAP data (current SU22 data), the original data (SU22 data without the "update" flag - because in the past SAP rolled out some support pack notes to change SU22 and some customers maintained SU22 anyway instead of SU24...) and the customer data (which is what you are looking for). Additionally the function module parameter has a 4th flag for when nothing is checked, and then it downloads everything (?). The name of the function was something like SU22LISTVALUES but you should be able to find it via the Object Navigator from the download screen - Menu => System => Status => double-click the GUI Screen program. I remember there being lots of comments in the coding as well to help understand it.
But this was some time ago and on a 4.7 system when I had looked into it, so please also check how many entries are downloaded and compare these to your USOBT_C and USOBX_C tables before you do anything like an upload... - as the download might not deliver information you are expecting (assuming that you ran SU25 after making changes or made some changes to SU22 without importing them via support packages, etc).
Let us know what you find. I will take a look in the next days as well when I find a system with some data in it...
Cheers,
Julius

New concepts in ECC 6.0

Similar Messages

Maybe you are looking for