Flex 4.1 Runtime CSS: CSS in module or just CSS

Hi,
I guess this question's answer is obvious but just in case I would like to ask.
I have application which loads a module. I would like to load some fonts before I load the module, so when the module is loaded it displays it's text correctly. So to do that at the moment I load one plain module with a stylesheet in it where I have the embedded fonts, and then I load the module with the text.
Should I not use a module with a stylesheet but compile a stylesheet separately and load it with StyleManager.loadStyleDeclarations() ?
NOTE: Also using the StyleManager I can set true to the second parameter of loadStyleDeclarations which will force updating the styles. How can I do that without loading new stylesheet? I want to do that in case the styles apply for something that is already on screen and I load the module with the styles at a later time.
Another thing is that If I recall correctly if I want to have the stylesheet in swf I need to compile it myself. And with the module with a stylesheet case that happens automatically.
So.. thoughts ?

Ok I read it (maybe for 5th time) to recall things a bit. So let me summarize after reading testing etc what I still don't understand:
1) In my application I have 1 custom skin extending Skin.
import custom.CSCSkin;
public var testSkinnn:CSCSkin;
and on creation complete I have:
var testSkin:Class = loaderInfo.applicationDomain.getDefinition("custom.CSCSkin") as Class;
trace(testSkin);
This returns [class CSCSkin].
But the same thing doesn't work in the module because the loaderInfo is null.
So how do you access the applicationDomain of a module ?
2) Looks like I can use almost any component as you say in the siblings and there is no problem, except for the managers classes and Alert. I guess that's because they are singletons with static vars and functions and they register their reference only once - for one application domain and get restrained by it.
I just tried to use Alert only in a module. Application is empty, just a moduleLoader.
import mx.managers.PopUpManager;
private var popUpManager:PopUpManager;
import mx.controls.Alert;
private var alert:Alert;
On creation complete I have:
Alert.show("TESTING","bla");
In the docs it says that registering the singletons/managers in module will make it throw error when you try to use it in a sibling module. But the fact is that the Alert doesn't work at all even in the module I registered them first - it throws error with the PopUpManager. To make the Alert work I had to move the Alert and PopUpManager declarations to the main application. Then they started working everywhere.
Why the Alert is not working if used only in one module?

Similar Messages

  • How to read runtime constants in ejb Module?

    Hi all,
    Anyone knows how to have special access to Runtime Constants at ejb Modules? I've searched and all I found is for Java and ABAP Mapping ...I hope it is possible! I want to read the interface name in order to choose which code my module should apply, as a case statement I mean.
    Thanks in advance,
    Ricardo.

    Hi Ricardo !
    Check these links:
    http://help.sap.com/saphelp_nw70/helpdata/en/b3/9a2aeb24dc4ab6b1855c99157529e4/content.htm
    Parameter MessageId
    Regards,
    Matias.

  • IView deployed using the Flex 2.0 runtime returns a blank screen

    Hello Everybody,
    We upgraded Visual Composer for NetWeaver 7.0 to SP Stack 21 and  now when we run a Visual Composer iView, deployed using the Flex 2.0 runtime, a blank screen appears instead of the application.
    We use windows server and mssql as db.
    Please help.
    Thanks,
    MD

    Hi Maulin,
    to solve your issue perform the following procedure:
               1. In Visual administrator, go to the HTTP Provider service of the server.
               2. Click the "Properties" tab.
               3. Find the "Never Compressed" property.
               4. Add "*. swf" and also "application/x-shockwave-flash" to the list.
               5. Click "Update", and then "Save"
               6. Restart the J2EE server and test the result
    If it still not working you should create an OSS Note,
    hope been helpful,
    best regards,
    Marco.

  • Ionic Side Menu Template - Javascript JavaScript runtime error: [$injector:nomod] Module 'ngLocale' is not available!

    I am using VS 2013 ,CTP 3.1
    When I tried to run the Ionic side menu template on Emulator 8.1, the javascript console shows below exception  -
    Exception was thrown at line 9576, column 11 in ms-appx://io.cordova.myapp8724a31325644ec29a8d2d88682b7987/www/lib/ionic/js/ionic.bundle.js
    0x800a139e - JavaScript runtime error: [$injector:nomod] Module 'ngLocale' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
    http://errors.angularjs.org/1.3.6/$injector/nomod?p0=ngLocale
    There was no code changes to any of the files.
    Please advise.

    Yes. I am using the same template.
    I am not able to attach the screenshot here.
    This is the error -
    'WWAHOST.EXE' (Script): Loaded 'Script Code (MSAppHost/2.0)'. 
    Exception was thrown at line 9576, column 11 in ms-appx://io.cordova.myapp8724a31325644ec29a8d2d88682b7987/www/lib/ionic/js/ionic.bundle.js
    0x800a139e - JavaScript runtime error: [$injector:nomod] Module 'ngLocale' is not available! You either misspelled the module name or forgot
    to load it. If registering a module ensure that you specify the dependencies as the second argument.
    http://errors.angularjs.org/1.3.6/$injector/nomod?p0=ngLocale

  • [svn:cairngorm3:] 16403: Added runtime support for latest module library ( LazyModuleLoadPolicyTag).

    Revision: 16403
    Revision: 16403
    Author:   [email protected]
    Date:     2010-06-02 12:47:11 -0700 (Wed, 02 Jun 2010)
    Log Message:
    Added runtime support for latest module library (LazyModuleLoadPolicyTag).
    Modified Paths:
        cairngorm3/trunk/libraries/Module/src/com/adobe/cairngorm/CairngormModuleXMLSupport.as
        cairngorm3/trunk/libraries/ModuleTest/src/CairngormModuleLibRuntimeSample.mxml
        cairngorm3/trunk/libraries/ModuleTest/src/runtimeContext.xml

    Bing,
    I think one thing you might want to do is to post your code on the Web somewhere. Maybe you can open a Weblog and post this there.
    http://www.jroller.com will let you open a blog for free we'll love to see more customers of JDeveloper opening weblogs and sharing their experience over the Web.

  • Gatherer\CSS connector failed to connect to CSS net.tcp

    Hi,
    Hope someone can help me out here. Have SharePoint 2013 running fine and has been for a while. Recently have been getting Event ID 1400 SharePoint server search 'Gatherer\CSS connector failed to connect to CSS net.tcp //servername/C7A30B. If I restart the
    server then all runs fine again but within a day it starts coming up with the same warning. The event ID is followed by Event id 2580 and 2581. Any help would be most appreciated.

    Hi alfatec,
    It should be related to the search service account permission issue, please try the following steps on your search servers which are running the "Search Host Controller Service", then check results again.
    1. "Start" -> "Administrative Tools" -> "Local Security Policy" (or run: Secpol.msc).
    2. Expand "Local Policies".
    3. Click on "User rights assignment".
    4. Make sure that the search service account has the following privileges.
    "Replace a process level token"
    "Adjust memory quotas for a process"
    "Impersonate a client after authentication"
    "Log on as a service"
    (5) Run gpupdate /force
    Thanks
    Daniel Yang
    TechNet Community Support

  • CSS without SSL Module needing sticky sessions

    Hello All,
    If anyone can help with this sticky situation I'd appreciate it.
    I have a customer with a CSS11501. He does not have an SSL module installed.
    He has 2 blade servers, when he adds a web site, which is accessible over SSL, the CSS load balances client requests causing lost sessions, mostly lost pop-ups, it does not want stick to the same server.
    I've configured the following:-
    service web1
    protocol tcp
    port 443
    keepalive type tcp
    ip address 192.168.200.50
    string web1
    active
    service web2
    rotocol tcp
    port 443
    eepalive type tcp
    ip address 192.168.200.51
    string web2
    active
    content SSL_Web
    add service web1
    add service web2
    rotocol tcp
    port 443
    vip address 1.2.3.4
    application ssl
    advanced-balance sticky-srcip-dstport
    active
    group web_Farm
      add service web1
      add service web2
      vip address 1.2.3.4
      active
    I was attempting to get the client to stick to the server but unfortunately, this didn't work, the CSS seems to continue to send requests to both servers and they are getting scripting errors.
    Once the customer turns off the second blade, all is ok.
    I did try adding the string value to the service and configuring 'advanced-balance arrowpoint-cookie' in the content but the clients were unable to reach any web sites.
    Best Regards Tony

    Tony,
    The config looks fine other than the "application SSL" under the content rule, and right now you are probing the servers with a tcp probe on port 80. If you want the probe to be on port 443 you should add the command "keepalive port 443" to both of the services. The CSS will default to port 80 for a tcp probe.
    Regards
    Jim

  • HTTPS ans SSL with CSS (No SSL Module)

    Hi,
    My customers have two server and need to load balance.
    These servers initiate SSL.
    and VIP address is :
    https://erpappl.erp.mis.blabla.tgc:8005
    My CSS has no ssl module. An dconfiguration is:
    service venice
    ip address 10.200.104.32
    protocol tcp
    port 8005
    keepalive type tcp
    keepalive port 8005
    redundant-index 120
    active
    service calgary
    ip address 10.200.104.33
    protocol tcp
    port 8005
    keepalive type tcp
    keepalive port 8005
    redundant-index 121
    active
    owner ERPAPPL
    content erpapp_test
    add service venice
    add service calgary
    redundant-index 60
    vip address 10.200.104.28
    protocol tcp
    port 8005
    url "/*"
    arrowpoint-cookie expiration 00:00:03:00
    advanced-balance arrowpoint-cookie
    application ssl
    active
    After this configuration I cannot reach the URL shown above.
    Can you help me?

    if this is encrypted traffic [HTTPS] the CSS can't see the content of the packet.
    So the CSS can't see the url [-> so the command url "/*" is incorrtect and should be removed] and the CSS can't see cookies [so the arrowpoint-cookie command is wrong and should be removed].
    If we sell an SSL module, there is a reason :-)
    The only sticky option you can use are :
    - sticky based on srcip
    - sticky on sslid
    The first option [srcip] has a problem with mega proxy [many users being nated with the same ip] and the 2nd option has the problem that it only works with SSLV2 and that some browsers do not use the sslid.
    Gilles.

  • How can I change the link color css in one module but not the whole site?

    I have a site built in muse but using modules from BC.  I changed the link color in the css for the online store and blog but of course it is applying it to everypage.  Is there a way to change the link color in an individual BC module instead of the whole site.?  I'm new to CSS obviously.
    Thanks
    Josh

    I don't think you can do it right in Muse but you can easily if you have access to the code of the page and the css file.
    You need to create a css class something like:
    .secondLink a      {     /*  secondLink can be any class name, I just chose that randomly
         color: #990000;     /* of course substitute your color code in there
    Then in your code add:
    class="secondLink"
    to your link's <a> tag. This will give any links with the class of secondLink the color assigned. Hope that helps get you started.

  • CSS 11503 SSL Module: .pfx file export to sftp

    Hello
    I wanted to know of there was a way to export the .pfx files off of the SSL Module to an SFTP server.....preferably in bulk not one at a time.  I want a central storage location for these files in the event that the CSS or the SSL module crashes.
    Thanks

    Hi Jay,
    Sure you can export the .pfx files out of the CSS but you need to do this one by one, there is no way you can get them out all at once.
    To export the files you first need to define your SFTP server IP address, username and passwd:
    CSS(config)# ftp-record SFTP_Server 10.10.10.1 username "password"
    Once you have the file name you need to enter this command:
    CSS# copy ssl sftp SFTP_Server export Certificate.pfx PKCS12 "passphrase" "password"
    : This is the password used to protect the file when it was created.
    : This is a local significant password on the CSS used when the file was
                imported into the box.
    * If you don't know these passwds you can't export the files out of the CSS.
    HTH
    Pablo

  • CSS with SSL module - how many certs do we need

    Hello,
    currently moving from server-based certs to CSS/SSL based.
    We have two sites, two CSS/SSL on each in ASR mode.
    There are two real servers behind each SSL rule for load balancing.
    The question becomes how many certificates do we need
    for such design ?
    For sure we need one per site, then on each site we have Active/Standby CSS's.
    Do we need separate certificate for each CSS?
    I dont think so, cause only one is active at the time.
    I tested it with same certificate on both CSS's on one site, no problem.
    The question is will it be ok for production ?
    So total number would be 2 cert for such design (one per VIP) if we have one SSL rule per site, and 4 if we have 2 SSL rule per site - is it ok ?
    Thank you,
    Alex

    the certificate is linked to a host name ie: www.mycompany.com.
    So, if you have 4 css, all handling traffic for www.mycompany.com, then they can all share the same certificate.
    Even if you have the 4 CSS split over 2 sites, using different vip, as long as they handle the same hostname, then they can share the certificate.
    Actually, the CSS itself does not care about hostname/certificate mapping.
    The CSS will use whatever certificate you configure it to use.
    However, browsers make a check url <-> certificate and if there is a mismatch, they pop up an error message.
    Regards,
    Gilles.

  • Spry Menu Bar 2.0 (1.0) - Handling of widget generated CSS, placement and rendering problems in CSS

    Hello:
    I wanted to repost my question to re-frame the issue based on what I have learned thus far.
    I am working on a website that has been developed using the Spry Menu Bar Framework UI (2.0) I.0, that has some peculiar rendering problems that affect IE 6 in particular.  The CSS is reprinted below.
    In particular, when I post the widget generated CSS in the head as it is orginally situated by the framework, the menu bar works fine.  However, it seemed to me that I should be able to reduce page weight (an important consideration considering my target population) by placing it in the general style sheet governing the entire site.
    When I place the styles at the beginning of the style sheet the menu doesn't render at all in any of the browsers (IE 6+, Firefox, Opera, Safari, Netscape, etc.) as it conflicts with the general rules governing links that appear later in the style sheet.  When I place the styles specific to the Menu bar at the end of the style sheet, then the menu bar renders properly in all browsers except IE 6.
    The odd thing is that the only way to ensure that the menu bar works in IE 6 is to keep the menu related styles in the head of each page.  This raises problems related to page weight (not an insurmountable consideration if no other solution can be found) but still an issue.  Likewise I need to support IE 6, again given the target audience/population.  The issue obviously has something to do with specificity, but I am not certain that is the only consideration at work here.  I have not tried the !important selector in regard to the menu, as IE 6 seems to only partially support this.
    Thanks in advance for any advice or insight that can be provided.  Thanks in particular to Martin for his contributions to my earlier question related to this issue.
    Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>
    The CSS governing the site generally is reproduced below:  (my belief is that it is the a:link, a:visited,  a:hover, a:active styles that may be in conflict).
    @charset "utf-8";
    body  {
        font: 100% Verdana, Arial, Helvetica, sans-serif;
       min-height: 0; /* This is necessary to overcome the "haslayout" bugthat is found in Windows 7 in conjuction with IE8.  For Moreinformation see: URL -- http://reference.sitepoint.com/css/haslayout.html */
        margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
        padding: 0;
        text-align:center; /* This allows for the centering of the container and overcomes a bug inherent in IE 5 */
        color: #000000;
        list-style-image: none;
        background-color: #FCFCFC;
    h1,h2,h3,h4,h5,h6 {
    color:#000066;
    a:link {
        color: #151A96;
        text-decoration: underline;
    a:visited {
        text-decoration: underline;
        color: #1B8DCD;
    a:hover {
        text-decoration: none;
        color: #F30A0A;
    a:active {
        text-decoration: underline;
        color: #151A96;
    #container {
        width: 960px;   
        margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
        text-align: left; /* this overrides the text-align: center on the body element. */
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Midsection %20_960.png);
        background-repeat: repeat-y;
    #header {
           padding: 0;  /* this padding matches the left alignment of the elementsin the divs that appear beneath it. If an image is used in the #headerinstead of text, you may want to remove the padding. */
            width:960px;
            height:332px;
            background-image:
            url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Header_960 .png);
            background-repeat:no-repeat;
    #header h1 {
        margin-right: 0px; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
        padding: 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
        display:none;
    #header img {
        display: none;
    #Main_nav_contents {
        padding: 0;
        margin-top: 0px;
        height: 39px;
        width: 950px;       
        padding-top: 275px; 
        padding-left: 39px;
        z-index: 3; 
    #MenuBarVertical {
        margin-bottom: 50px;
        padding-top: 50px;
        padding-bottom:200px;
        padding-left: 15px;
        padding-right: 15px;
    .mainContent_left {
       margin: 0;/* the right margin on this div element creates the columndown the right side of the page - no matter how much content thesidebar1 div contains, the column space will remain. You can removethis margin if you want the #mainContent div's text to fill the#sidebar1 space when the content in #sidebar1 ends. */
        padding-left:30px;
        padding-right:20px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
        width: 600px;
        float: left;
    .sidebar_right {
        float: right; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:0;
        margin-right:10px;
        font-size:90%;
    .mainContent_right {
        margin-left: 10px;
        padding-left:30px;
        padding-right:20px;
        width: 600px;
        float: right;
    .sidebar_left {
        float: left; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:30px;
        margin-right:0;
        overflow: hidden;
        font-size:90%;
    .main_content_centered {
        width: 650px;
        margin-left: 155px;
    .main_content_centered_header {
        margin-left: 75px;
    .sidebar_textbox {
        margin: 0px;   
        width: 260px;
        padding: 2px;
    .sidebar_textbox_header {
        width:255px;
        height:58px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Header.png);
    .sidebar_textbox_background_middle {
         width: 255px;   
        padding-top: 12px;   
        padding-bottom: 10px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Middle.png);
        background-repeat: repeat-y;
    .sidebar_textbox_content {
       /* The width and padding are set as follows to accomodate quirks inbrowser rendering and to ensure that text is contained within thebackground of the text box */
        width: 230px;
        padding-left: 20px;
        padding-right: 40px;
    .sidebar_textbox_footer {
        width:255px;
        height:64px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Port rait%20Textbox%20Footer.png);
    #issues_menu a:link {
        color: #151A96;
        text-decoration: none;
        font-weight:bold;
    #issues_menu a:visited {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #issues_menu a:hover {   
        color: #F30A0A;
        font-weight:bold;
        font-style: oblique;
        text-decoration: none;
    #issues_menu a:active {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #archives {
        padding-top: 15px;
        padding-right: 15px;
        padding-bottom: 20px;
        padding-left: 0px;
    .landscape_textbox {
        width: 500px;
        margin-right: 0px;
        margin-left: 30px;
        padding-top:35px;
        padding-bottom: 25px;
        font-style: normal;
        font-weight: normal;
    .landscape_textbox_hdr {
        width:500px;
        height:38px;
        margin:auto;
        padding:0;
        background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Landscape%20Textbox%2 0Header.png);
    .landscape_textbox_middle {
        width:auto;
        margin:auto;
        padding-top: 12px;
        padding-bottom: 12px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/lan dscapte%20Textbox%20Middle.png);
        background-repeat:repeat-y;
    .landscape_textbox_content {
        width:450px;
        padding:25px;
    .landscape_textbox_ftr {
        width:500px;
        height:44px;
        margin:auto;
        padding:0;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Lan dscape%20Textbox%20Footer.png);
    #footer {
        padding: 0; /* this padding matches the left alignment of the elements in the divs that appear above it. */
        width: 960px;
        height: 222px;
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Footer%20_ 960.png);
        background-repeat:no-repeat;
    #footer p {
       margin: 0px; /* zeroing the margins of the first element in the footerwill avoid the possibility of margin collapse - a space between divs */
        padding:0px; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
        text-align:center;
        margin-left: 50px;
        margin-right: 50px;
        padding: 10px;
        font-size: small;
    #footer h5 {
    text-align:center;
    .fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
        float: right;
        margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .dropcap {
        display: block;
        float: left;
        line-height: 80%;
        font-size: 250%;
        font-weight: bolder;
        color: #000066;   
        padding: .03em .1em 0 0;
    .red_arrows {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Arrow%20Large.png);    
    .blue_bullets {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Bullet%20Medium%20Fu ll.png);   
    .attention {
        color: #F30A0A;
        font-size:x-large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .attention_small {
        color: #F30A0A;
        font-size:large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .table {
        table-layout:fixed;
    .blue {
        color: #00F;
    #container .mainContent_left p .blue {
        color: #0303A0;

    Hi Nancy:
    The specific code that I am referring to is the CSS code governing the styling of the spry menu widget that only works in IE 6 if, and only if, it remains in the head of the web page.  If removed and placed in a stylesheet, the IE plugins fail to compensate for the IE 6 "gap" bug.  As I said, it doesn't make sense to me that, assuming specificity is addressed, that these can not be included in an external style sheet.  I am looking for a) an explanation why they must remain embedded in the web page; and 2) any means by which I might be able to export them.
    I will reproduce the specific css style (code) below:  it should also be visable through reveal source --
    Thanks again, Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>

  • BAPI Runtime Error DBIF_RSQL_INVALID_REQUEST with module "KONV_BEARBEITEN"

    Hi Experts
    I am trying to create a sales order using BAPI FM BAPI_SALESORDER_CREATEFROMDAT1. After executing the program it shows in output screen that the sales order created and also displays the newly created sales order number. But when I want to check the order from VA03 it shows Express document "Update was terminated" received by author AAA, where AAA is login name.
    I also analysis the sort dump for which the update process was terminated. I give the error details
    Runtime Errors         DBIF_RSQL_INVALID_REQUES
    Error analysis
        An invalid request was made to the SAP database interface in a statement
         in which the table "KONV " was accessed.
    Below are the module name and report from where the error is coming.
    Function Module name  RV_SALES_DOCUMENT_ADD
    Program Name  SAPLV45U
    Include  LV45UF0K
    Row  26
    Source code from Rruntime Error
      Line  SourceCde
    1 *****************************************************************
        2 *  Unterroutinen RV-Auftragsabwicklung alphabetisch sortiert:
        3 *  ----------------------------------------------------------
        4 *  Buchstabe K:
        5 *
        6 *****************************************************************
        7
        8 *----------------------------------------------------------------
        9 *       FORM KONV_BEARBEITEN
       10 *----------------------------------------------------------------
       11 FORM KONV_BEARBEITEN.
       12
       13   CHECK: FKONV_GEAENDERT NE SPACE OR
       14          VORGANG = CHARH.
       15
       16   IF VORGANG NE 'H'.
       17     DELETE FROM KONV WHERE KNUMV = VBAK-KNUMV.
       18 ENHANCEMENT-POINT KONV_BEARBEITEN_10 SPOTS ES_SAPLV45U.
       19   ENDIF.
       20
       21   LOOP AT FXKOMV.
       22     FXKOMV-MANDT = VBAK-MANDT.
       23     FXKOMV-KNUMV = VBAK-KNUMV.
       24     MODIFY FXKOMV.
       25   ENDLOOP.
    >>>>>   INSERT KONV FROM TABLE FXKOMV.
       27   IF SY-SUBRC NE 0.
       28     MESSAGE A100 WITH
       29   ENDIF.
       30
       31 ENHANCEMENT-POINT KONV
       32 ENDFORM.
       33 *eject
    Below is my source code.
    *& Report  Z_BAPI_SALESORDER
    REPORT  z_bapi_salesorder.
    * Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    * Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    * Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE dzmengc  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapiitemin  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapireturn1    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapisdhedu
                             WITH HEADER LINE.
    * Initialization.
    INITIALIZATION.
      v_text   = 'Order type'.
      v_text1  = 'Sales Org'.
      v_text2  = 'Distribution channel'.
      v_text3  = 'Division'.
      v_text4  = 'Sold-to'.
      v_text5  = 'Ship-to'.
      v_text6  = 'Material'.
      v_text7  = 'Quantity'.
      v_text9  = 'Plant'.
    * Start-of-selection.
    START-OF-SELECTION.
    * Header data
    * Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    * Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    * Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    * Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    * Partner data
    * Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    * Ship to
      partner-partn_role = 'WB'.
      partner-partn_numb = p_ship.
      APPEND partner.
    * ITEM DATA
      itemx-updateflag = 'I'.
    * Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    * Material
      item-material = p_matnr.
      itemx-material = 'X'.
    * Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    * Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
    *   Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
    *   Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
        EXPORTING
          order_header_in           = header
    *     WITHOUT_COMMIT            = ' '
    *     CONVERT_PARVW_AUART       = ' '
       IMPORTING
         salesdocument              = v_vbeln
    *     SOLD_TO_PARTY             =
    *     SHIP_TO_PARTY             =
    *     BILLING_PARTY             =
    *     RETURN                    =
        TABLES
          order_items_in            = item
          order_partners            = partner
    *     ORDER_ITEMS_OUT           =
    *     ORDER_CFGS_REF            =
    *     ORDER_CFGS_INST           =
    *     ORDER_CFGS_PART_OF        =
    *     ORDER_CFGS_VALUE          =
    *     ORDER_CCARD               =
    *     ORDER_CFGS_BLOB           =
         order_schedule_ex          = lt_schedules_in
    * Check the return table.
      IF v_vbeln <> space.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ELSE.
        WRITE: / 'Error in creating document'.
      ENDIF.
    I am unable to trace the exact reason. Please help and thanks in advance.
    Edited by: Joy Banerjee on Oct 12, 2009 7:47 AM

    Hi Prashant,
    Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
    If it doesn't work, see in transaction db02 if there is sufficient tablespace.
    Let me knoe the status of tablespaces.
    Regards,
    Sabita

  • Runtime Error in HR module t-code PPOCE [upgraded 4.7 to ECC6]

    HI Gurus!
    at my client site , we have upgraded 4.7 to ECC6. Now functional consultants are testing the system.When HR consultant working on PPOCE t-code ,the patch no of SAP HR - 0007. its giving runtime error.
    Runtime Errors  CREATE_DATA_UNKNOWN_TYPE                              
    Except.     CX_SY_CREATE_DATA_ERROR          Date and Time                    19.08.2008     14:42:44          
    Short text                    
    CREATE DATA: The specified type "HRP1680" is no valid data type.                                        
    What happened?                    
    Error in the ABAP Application Program          
    The current ABAP program "SAPLRHDB" had to be terminated because it has come across a statement that unfortunately cannot be executed.                                        
    Error analysis :An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not  caught in
    procedure "FILL_I777D" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
    The reason for the exception is:
    The dynamically specified type "HRP1680" at CREATE DATA is no valid data type.
    The type is either unknown or an object type.
    Missing RAISING Clause in Interface          
    Program     SAPLRHDB
    Include     LRHDBF00
    Row     177
    Module type  (FORM)
    Module Name FILL_I777D
    Trigger Location of Exception               
    Program     SAPLRHDB
    Include     LRHDBF00
    Row     308
    Module type(FORM)
    Module Name     FILL_I777D
    Source Code Extract          
    Line          SourceCde
    278          **                HEADER   = FI_HEADER                    "ANDBCEK008264
    279          **           TABLES                                       "ANDBCEK008264
    280          **                FIELDTAB = FI_TAB                       "ANDBCEK008264
    281          **           EXCEPTIONS                                   "ANDBCEK008264
    282          **                OTHERS   = 4.                           "ANDBCEK008264
    283          *                                                         "ANDBCEK008264
    284          *      CALL FUNCTION 'DDIF_FIELDINFO_GET'                 "ANDBCEK008264
    285          *           EXPORTING                                     "ANDBCEK008264
    286          *                tabname        = fi_tabname              "ANDBCEK008264
    287          **               FIELDNAME      = ' '                     "ANDBCEK008264
    288          **               LANGU          = SY-LANGU                "ANDBCEK008264
    289          **               LFIELDNAME     = ' '                     "ANDBCEK008264
    290          **               ALL_TYPES      = ' '                     "ANDBCEK008264
    291          *           IMPORTING                                     "ANDBCEK008264
    292          *                x030l_wa       = fi_header               "ANDBCEK008264
    293          **               DDOBJTYPE      =                         "ANDBCEK008264
    294          **               DFIES_WA       =                         "ANDBCEK008264
    295          **          TABLES                                        "ANDBCEK008264
    296          **               DFIES_TAB      =                         "ANDBCEK008264
    297          *          EXCEPTIONS                                     "ANDBCEK008264
    298          *               not_found      = 1                        "ANDBCEK008264
    299          *               internal_error = 2                        "ANDBCEK008264
    300          *               OTHERS         = 3.                       "ANDBCEK008264
    301          *
    302          *      IF sy-subrc EQ 0.
    303          *        i777d-tbtab_tabof = fi_header-tablen - tabnr_intlen.
    304          *        i777d-pnnnn_tabof = i777d-tbtab_tabof - 8.
    305          *      ENDIF.
    306          
    307          *      ASSIGN char TO <any_field> CASTING TYPE (fi_tabname).  "ANDDDIF
    >>>>>                create data anyfield type (fi_tabname).                "ANDUNI
    309                assign anyfield->* to <any_field>.                     "ANDUNI
    310          
    311          *     we need a character view of <any_field> !!!            "ANDUNI
    312                assign <any_field> to <char_field> casting type c.     "ANDUNI
    313          
    314          *      DESCRIBE FIELD <any_field> LENGTH tablength            "ANDDDIF
    315          *                                 IN BYTE MODE.               "ANDDDIF
    316          
    317                DESCRIBE FIELD <char_field> LENGTH tablength           "ANDUNI
    318                                            IN CHARACTER MODE.         "ANDUNI
    319          
    320                <i777d>-tbtab_tabof = tablength - tabnr_intlen.        "ANDDDIF
    321                <i777d>-pnnnn_tabof = <i777d>-tbtab_tabof - 8.         "ANDDDIF
    322          
    323             ENDIF.
    324              IF <i777d>-ext_infty NE space.                             "VWMEXT
    325                READ TABLE i77id
    326                     WITH KEY infty = <i777d>-infty
    327                     BINARY SEARCH.
    i have check the table HRP1680 in SAP4.7c but in ECC 6 it is not there. So i have create that table. Is it Info-type? or i have apply OSS notes.
    regards
    Rahul
    Edited by: rahul deshmukh on Aug 20, 2008 11:52 AM

    Hello,
    I receive the same error when trying to change records of an infotype. Did you find a solution to this problem? I know your message is from 2008, but maybe you remember what you did to solve it
    Thank you!
    Iuliana

  • Important information regarding the Flex 2.0 runtime and UNIX

    Hi,
    There's an issue with Flex 2.0 when the J2EE is installed on a UNIX server.
    upon deployment and running an iView, the runtime shows only a blank grey area.
    upon refreshing the browser, the iView is displayed as ussual.
    the source of this issue, as we discovered, lays in the configuration of the J2EE engine.
    and so - in order to solve this issue, one should access the J2EE Visual administrator and perform the next steps:
    1. In Visual administrator, go to HTTP Provider service of the server.
    2. Look for the "Never Compressed" property.
    3. Add "*.swf" and also "application/x-shockwave-flash" to the list. Make sure that you also add commas properly...
    4. Restart the J2EE server and test the result.

    Hi,
    Please try to delete the browser cache ("Delete temporary files" in IE).
    I know that sounds silly, but it could really solve the issue
    afterwards you can deploy and run as ussual.
    If that works, please let as all know.
    (points is also good..)
    Amir
    Edited by: Amir Mimran on Apr 15, 2008 8:59 AM

Maybe you are looking for