Cookie insert in the CSM module

Hello
I would like to ask if anbody know why when I use the "cookie insert" option in the CSM configuration with the timeout of 60 minutes, from the browser point of view the cookie expires in 2010? I have checked in on the CSM and CSM-S and in both of them it works the same way.
Thanks in advance
Regards
Lukas

Its because of the variable (COOKIE_INSERT_EXPIRATION_DATE) that sets the expiry date to Jan 2010. Use "show mod csm X
variable" to see it.
xyz#sh mod csm 3 var | include EXPIRATION
COOKIE_INSERT_EXPIRATION_DATE Fri, 1 Jan 2010 01:01:50 GMT
Setting this variable to none makes it a session cookie ( expire at
the end of the session -- cookie will be erased when the browser is closed).
(config-module-csm)#variable COOKIE_INSERT_EXPIRATION_DATE ""
With "cookie insert feature" on the CSM ,
the timeout value configured in the sticky has no affect. You will always see a timeout of zero.
Syed Iftekhar Ahmed

Similar Messages

  • CSM Modules and Server availability project

    I have 2 geographically separated sites, site A in the main office and site B is the Disaster recovery office. These 2 sites are connected by a high speed Layer 3 link (10Gb), The goal is to have duplicate servers available in site B in the event of partial server failure in site A or even complete failure of site A. Can I accomplished this with the CSM modules given that these servers will be in different networks and overall how would this configuration work, I really appreciate it.

    Are you planning to put CSMs in both data centers or a single data center?
    If CSM will be at one site (site A) only then
    You need to use source NAT on CSM (Assumption: its in Site A) to make sure that the return traffic from servers in "site B"
    can go back to the client through CSM at "Site A"
    If both Data centers will have their own CSM modules then the best approach is to use GSS or any any Geo redundant setup that can check the load/health/availability/proximity of the VIPs (virtual ips configured on each CSM) in each data center and direct the clients intelligently to the appropriate data center.
    Syed Iftekhar Ahmed

  • How to configure 2 CSM modules in 6500 ?

    hi,
    6500 supports multiple CSM modules in one chassis. I check the configuation about the CSM with 2 modes one is rp and another is csm. another mether is to enter the csm module. Does anyone know the current way to setup the 2 csm modules in one 6500 or give me a sample ?
    best regards.
    fred.

    If you are running muliple CSM's in the same chassis you need to run in csm mode, otherwise if you are running a single csm in a chassis you can run in rp mode.
    hope that helps
    I am running one csm in each chassis and fault-tolerant
    mark

  • ACE cookie-insert stickyness

    Hi, I am trying to understand the ACE`s cookie-insert method of stickiness. So the ACE will always insert a cookie into the http-header when sending a response to the client/browser. Based on that if it recieves the same cookie-id in the subsequent requests it knows to which end-server to send it as it does an internal hash based on the cookie-value.
    My question is, what happens if the server also sends a cookie? Does ACE dis-regards that cookie and inserts a new one on it`s own? How do the cookie-insertion from the server (which is done by default by the web-servers) co-exist with the cookie insertion by the ACE?
    thnx

    Hi,
    As long as they don't both use the Same Cookie name they won't influence each other.
    If you don't assign a cookie-name ACE will create a unique one per rserver.
    Or you can configure one e.g.
    rserver WebServer1 80
        cookie-string "ACEWS1Cookie"
    More details can be found here:
    http://www.cisco.com/en/US/customer/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/sticky.html

  • Can Firefox be fixed to block tracking cookies even it the web site refuses to cooperate?

    Too many web sites (e.g., New York Times, New Yorker, Google) do not honor the request to block tracking cookies. They add them back in within seconds after I delete them. Most of the added cookies are not, repeat not, from the owner of the website but are added via some agreement with the site owner. Most of these cookies are from sites having no connection with me or the site provider. Can or will Firefox provide an option to block all cookies inserted from the web site?

    Firefox only sends a DNT=1 response header to the server.<br />
    It is up to the server to decide what to do with that request.
    * http://blog.mozilla.com/blog/2011/06/21/mozilla-delivers-new-version-of-firefox-first-web-browser-to-support-do-not-track-on-multiple-platforms/
    * http://blog.mozilla.com/blog/2011/03/30/advertisers-and-publishers-adopt-and-implement-do-not-track/
    * http://browserspy.dk/donottrack.php

  • CSM Sticky Cookie Insert

    Hello,
    We have a Catalyst 6500 w/ CSM-S configuration that has 2 serverfarms with identical real servers using the same VIP. Each farm has 50 real servers (2 IPs with 25 consecutive ports each). One of the serverfarms is defined under a SLB policy with client NAT and the second one directly under the vserver. Both serverfarms are configured with the same sticky group for cookie insert. When I issue "show mod csm 13 sticky group 4" I only see 52 entries instead of 100. Also, some of the entries are duplicate. All the rest of the sticky groups are displaying the correct number of cookie entries, matching the number of real servers in the farms. Any ideas on why this is?

    You probably have encountered the following bug fixed only in version 4.2.2
    CSCsa74493
    CSM: sticky insert table not updated if adding new reals
    The workaround is to reboot the CSM or reconfigure reals, policy and vserver in the correct order.
    Gilles.

  • HTTPS Keepalive with the CSM & SSL Module

    Has anyone had any success getting a secured web page for a keepalive using the CSM with and SSL module. If so can post an example?
    Thank you,
    Dave

    Hi David,
    Here find some full config example for your perusal for CSM and SSL Services Module Initial Configuration Example
    http://www.cisco.com/en/US/products/hw/modules/ps2706/products_configuration_example09186a0080216c16.shtml
    2nd config example to Configuring CSM to Load Balance SSL to a Farm of SCAs for One-Armed Proxy Mode
    http://www.cisco.com/en/US/products/hw/modules/ps2706/products_configuration_example09186a00801aca55.shtml
    Sachin garg

  • Cookie Insert-Based Persistence

    Hi,
    I'm slightly confused by the relationship between the various timers with relation to cookies.
    For example, I want to use the "cookie insert" feature to provide persistence, but only across sessions. To do this I think I need to modify the COOKIE_INSERT_EXPIRATION_DATE variable to set it to null.
    So far so good.
    1) do I need to do anything more (like match cookie) to enable this persistence? or does it happen automatically?
    2) if I do this what effect does the timer values have on persistence? (i.e. there is a default timeout of 1440 minutes - does this get ignored?)
    thanks,
    Ray.

    setting COOKIE_INSERT_EXPIRATION_DATE to null makes "inserted cookie" session based cookie.
    You just need to
    1. Define a sticky group with insert cookie
    sticky 19 cookie APP1-cookie insert timeout 30
    (timeout defined here has no significance, CSM will insert cookie "APP1-cookie" in the server responses.Cookie values will be different for all the reals)
    2. And Assign it to a VServer/ policy
    vserver APP1-VS
    virtual 10.10.10.12 tcp www
    serverfarm APP1-SF
    sticky 30 group 19
    replicate csrp sticky
    replicate csrp connection
    persistent rebalance
    inservice
    Syed Iftekhar Ahmed

  • Problem releasing the application module after upgrade to 11.1.1.2

    We have recently upgraded from JDeveloper 11.1.1.1 to 11.1.1.2.
    In the "tearDown()" method in our Unit Tests, the Application Module is realeased using:
    private ApplicationModule am;
    Configuration.releaseRootApplicationModule(am, true);
    Alter the upgrade, this produces the following error:
    oracle.jbo.JboException: JBO-33025: Failed to release application module MapServiceGlobal. Cookie handle not found.
    Please Help.
    FYI - this is the code that is used to create the application module:
    Hashtable env = new Hashtable(2);
    env.put(JboContext.INITIAL_CONTEXT_FACTORY,JboContext.JBO_CONTEXT_FACTORY);
    env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);
    try
    InitialContext ic = new InitialContext(env);
    ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(rootAM);
    am = home.create();
    catch (NamingException nex)
    /* Handle the error here if you don't find it */
    throw new NamingException("Application Module naming exception " + rootAM + " : " + nex.getMessage());
    /* Connect the AM to a database connection */
    am.getTransaction().connect(jdbcConnectionURL);
    * Set the bundled exception mode so that exceptions are thrown in the
    * same way as when we're running in the web application.
    am.getTransaction().setBundledExceptionMode(true);
    Thanks,
    -Spiro

    Hi,
    I used OCEP 10.3.0.0 and upgraded the wlevs30 domain to PS6(11.1.1.7.0). and it worked without such error.
    My experience is:
    1) in OCEP 10.3.0.0 it needs not to add the security groups in atnstore.txt
    2) you need to add <scratch-directory/> for Jetty in server's config.xml otherwise you will see the visualizer takes a long time to get up on Windows
    Thanks
    Junger

  • Unable to load the kernel module 'nvidia.ko' [SOLVED]

    After my most recent kernel upgrade, I can't get my GUI to run. I've tried reinstalling the nvidia driver to no avail.
    Any insight would be greatly appreciated. I'm using a GeForce 8400 GS
    cat /var/log/nvidia-installer.log
    ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
    frequently when this kernel module was built against the wrong or
    improperly configured kernel sources, with a version of gcc that differs
    from the one used to build the target kernel, or if a driver such as
    rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
    obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU
    installed in this system is not supported by this NVIDIA Linux graphics
    driver release.
    Please see the log entries 'Kernel module load error' and 'Kernel
    messages' at the end of the file '/var/log/nvidia-installer.log' for
    more information.
    -> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
    -1 No such device
    -> Kernel messages:
    NVRM: This can occur when a driver such as nouveau, rivafb,
    NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
    NVRM: the NVIDIA device(s).
    NVRM: Try unloading the conflicting kernel module (and/or
    NVRM: reconfigure your kernel without the conflicting
    NVRM: driver(s)), then try loading the NVIDIA kernel module
    NVRM: again.
    NVRM: No NVIDIA graphics adapter probed!
    NVRM: The NVIDIA probe routine was not called for 1 device(s).
    NVRM: This can occur when a driver such as nouveau, rivafb,
    NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
    NVRM: the NVIDIA device(s).
    NVRM: Try unloading the conflicting kernel module (and/or
    NVRM: reconfigure your kernel without the conflicting
    NVRM: driver(s)), then try loading the NVIDIA kernel module
    NVRM: again.
    NVRM: No NVIDIA graphics adapter probed!
    NVRM: The NVIDIA probe routine was not called for 1 device(s).
    NVRM: This can occur when a driver such as rivafb, nvidiafb or
    NVRM: rivatv was loaded and obtained ownership of the NVIDIA
    NVRM: device(s).
    NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
    NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
    NVRM: support), then try loading the NVIDIA kernel module again.
    NVRM: No NVIDIA graphics adapter probed!
    ERROR: Installation has failed. Please see the file
    '/var/log/nvidia-installer.log' for details. You may find suggestions
    on fixing installation problems in the README available on the Linux
    driver download page at www.nvidia.com.
    Last edited by wsims (2010-06-22 15:06:04)

    if you used the packages from repos, the blacklist is done automatically in nvidia,
    $ pacman -Qo /etc/modprobe.d/nouveau_blacklist.conf
    /etc/modprobe.d/nouveau_blacklist.conf is owned by nvidia 195.36.31-1
    $ cat /etc/modprobe.d/nouveau_blacklist.conf
    blacklist nouveau
    but i guess you just want to mess your system by using unsupported and very bad ways and you are way smarter than the devs if you used that installer
    Last edited by wonder (2010-06-22 14:10:01)

  • How to use the text module in script

    hi,
            i script how to use the text modules and how to write the code  in layout of the script?

    Hi,
    You canr use text modules in script. You have to use standard texts .
    Standard text are maintained in SO10 transaction.
    you can create translation text for other languages also . So based on logon language it will print translation text.
    go to SO10
    give textname it say Ztextname  id as ST and language as EN
    say create, then you will get editor there maintain your text and save it . then come back . Now change language (say for german DE) say create and eneter translation text and save it.
    so now you have created a text called ztextname which you can use in your script.
    Inorder to insert the texts in your script do as below
    go to any window editor and   select path
    Insert->texts->symbols->standard symbols
    then you will get popup  in which you have to mention all the parameters that you have created earlier.
    after inserting just change language EN to sy-langu
    Reward points if useful
    About text elements Sravan already given some informatiomn
    Regards,
    Nageswar

  • Not able to use Commit after the function module STATUS_OBJECT_CREATE

    I am using function module   STATUS_OBJECT_CREATE
       CALL FUNCTION 'STATUS_OBJECT_CREATE'
              EXPORTING
               CHGKZ         = 'X'
               CLIENT        = SY-MANDT
                OBJNR         = LV_OBJNR3
                OBTYP         = 'IWE'
                STSMA         = 'ZS_RE_01'
              IMPORTING
                OBJNR         = LV_OBJNR3.
                STONR                        = LV_STONR.
            IF SY-SUBRC = 0.
                COMMIT WORK.
            ENDIF.
    i am getting error after the COMMIT WORK .
    I am not getting any issue in the function module .after the function module i am using the COMMIT WORK and i am getting the following error message
    Category               ABAP Programming Error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    ABAP Program           SAPLBSVU
    Application Component  CA-GTF-TS-SMT
    Date and Time          03/17/2014 07:01:29
    |Short text                                                                                        |
    |    The ABAP/4 Open SQL array insert results in duplicate database records.                       |
    |What happened?                                                                                    |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                                  |
    |    The current ABAP program "SAPLBSVU" had to be terminated because it has                       |
    |    come across a statement that unfortunately cannot be executed.                                |
    |What can you do?                                                                                  |
    |    Note down which actions and inputs caused the error.                                          |
    |                                                                                                  |
    |                                                                                                  |
    |    To process the problem further, contact you SAP system                                        |
    |    administrator.                                                                                |
    |                                                                                                  |
    |    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
    |    at and manage termination messages, and you can also                                          |
    |    keep them for a long time.                                                                    |
    |Error analysis                                                                                    |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                 |
    |     in                                                                                           |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", 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:                                                              |
    |    If you use an ABAP/4 Open SQL array insert to insert a record in                              |
    |    the database and that record already exists with the same key,                                |
    |    this results in a termination.                                                                |
    |                                                                                                  |
    |    (With an ABAP/4 Open SQL single record insert in the same error                               |
    |    situation, processing does not terminate, but SY-SUBRC is set to 4.)                          |
    |How to correct the error                                                                          |
    |    Use an ABAP/4 Open SQL array insert only if you are sure that none of                         |
    |    the records passed already exists in the database.                                            |
    |                                                                                                  |
    |    If the error occures in a non-modified SAP program, you may be able to                        |
    |    find an interim solution in an SAP Note.                                                      |
    |    If you have access to SAP Notes, carry out a search with the following                        |
    |    keywords:                                                                                     |
    |                                                                                                  |
    |    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"                                              |
    |    "SAPLBSVU" or "LBSVUU01"                                                                      |
    |    "STATUS_UPDATE"                                                                               |
    |                                                                                                  |
    |    If you cannot solve the problem yourself and want to send an error                            |
    |    notification to SAP, include the following information:                                       |
    |                                                                                                  |
    |    1. The description of the current problem (short dump)                                        |
    |                                                                                                  |
    |       To save the description, choose "System->List->Save->Local File                            |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    2. Corresponding system log                                                                   |
    |                                                                                                  |
    |       Display the system log by calling transaction SM21.                                        |
    |       Restrict the time interval to 10 minutes before and five minutes                           |
    |    after the short dump. Then choose "System->List->Save->Local File                             |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    3. If the problem occurs in a problem of your own or a modified SAP                           |
    |    program: The source code of the program                                                       |
    |       In the editor, choose "Utilities->More                                                     |
    |    Utilities->Upload/Download->Download".                                                        |
    |                                                                                                  |
    |    4. Details about the conditions under which the error occurred or which                       |
    |    actions and input led to the error.                                                           |
    |                                                                                                  |
    |    The exception must either be prevented, caught within proedure                                |
    |    "STATUS_UPDATE" "(FUNCTION)", or its possible occurrence must be declared in                  |
    |     the                                                                                          |
    |    RAISING clause of the procedure.                                                              |
    |    To prevent the exception, note the following:                                                 |
    |System environment                                                                                |
    |    SAP Release..... 702                                                                          |
    |    SAP Basis Level. 0010                                                                         |
    |                                                                                                  |
    |    Application server... "sds6ci"                                                                |
    |    Network address...... "11.224.101.53"                                                         |
    |    Operating system..... "Linux"                                                                 |
    |    Release.............. "2.6.18-194.el5"                                                        |
    |    Hardware type........ "x86_64"                                                                |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                 |
    |    Work process number.. 17                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "gctsdb01lds.hsi.hugh"                                                     |
    |    Database type..... "ORACLE"                                                                   |
    |    Database name..... "DS6"                                                                      |
    |    Database user ID.. "SAPDS4"                                                                   |
    |                                                                                                  |
    |    Terminal.......... "GCTEMP02VDI"                                                              |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                         |
    |    created (date)... "Sep 14 2013 05:28:14"                                                      |
    |    create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820"                              |
    |    Database version. "OCI_102, 10.2.0.5.0, V2, default"                                          |
    |                                                                                                  |
    |    Patch level. 500                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |
    |    SAP database version. 720                                                                     |
    |    Operating system..... "Linux 2.6, Linux 3"                                                    |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 1317248                                                                              |
    |    EM...... 0                                                                                    |
    |    Heap.... 0                                                                                    |
    |    Page.... 0                                                                                    |
    |    MM Used. 1242912                                                                              |
    |    MM Free. 53400                                                                                |
    |User and Transaction                                                                              |
    |    Client.............. 160                                                                      |
    |    User................ "DV018458"                                                               |
    |    Language key........ "E"                                                                      |
    |    Transaction......... "SE38 "                                                                  |
    |    Transaction ID...... "5323C30FC9364665E10000000BE06533"                                       |
    |                                                                                                  |
    |    EPP Whole Context ID.... "002655EE0F241ED3ABB7D81260A28C44"                                   |
    |    EPP Connection ID....... 00000000000000000000000000000000                                     |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "SAPLBSVU"                                                               |
    |    Screen.............. "RSM13000 3000"                                                          |
    |    Screen Line......... 2                                                                        |
    |    Debugger Active..... "none"                                                                   |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "SAPLBSVU" - in "STATUS_UPDATE".                     |
    |    The main program was "RSM13000 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 60                                  |
    |    of the (Include) program "LBSVUU01".                                                          |
    |    The program "SAPLBSVU" was started in the update system.                                      |
    |    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                   |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", but it was neither handled locally nor                |
    |     declared                                                                                     |
    |    in the RAISING clause of its signature.                                                       |
    |                                                                                                  |
    |    The procedure is in program "SAPLBSVU "; its source code begins in line                       |
    |    1 of the (Include program "LBSVUU01 ".                                                        |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |   30|  LOOP AT jsto_upd WHERE chgkz = 'X'.                                                       |
    |   31|    CHECK: jsto_upd-chgnr > '000',                                                          |
    |   32|           jsto_upd-stsma NE jsto_upd-stsma_old.                                            |
    |   33|    CLEAR jcdo_tab.                                                                         |
    |   34|    MOVE-CORRESPONDING jsto_upd TO jcdo_tab.                                                |
    |   35|    MOVE-CORRESPONDING chdat    TO jcdo_tab.                                                |
    |   36|    jcdo_tab-stsma_new = jsto_upd-stsma.                                                    |
    |   37|    APPEND jcdo_tab.                                                                        |
    |   38|  ENDLOOP.                                                                                  |
    |   39|* Änderungen zu Einzelstatus (Insert)                                                       |
    |   40|  LOOP AT jest_ins WHERE chgkz = 'X'.                                                       |
    |   41|    CHECK jest_ins-chgnr > '000'.                                                           |
    |   42|    CLEAR jcds_tab.                                                                         |
    |   43|    MOVE-CORRESPONDING jest_ins TO jcds_tab.                                                |
    |   44|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   45|    jcds_tab-chind = 'I'.                                                                   |
    |   46|    APPEND jcds_tab.                                                                        |
    |   47|  ENDLOOP.                                                                                  |
    |   48|* Änderungen zu Einzelstatus (Update)                                                       |
    |   49|  LOOP AT jest_upd WHERE chgkz = 'X'.                                                       |
    |   50|    CHECK jest_upd-chgnr > '000'.                                                           |
    |   51|    CLEAR jcds_tab.                                                                         |
    |   52|    MOVE-CORRESPONDING jest_upd TO jcds_tab.                                                |
    |   53|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   54|    jcds_tab-chind = 'U'.                                                                   |
    |   55|    APPEND jcds_tab.                                                                        |
    |   56|  ENDLOOP.                                                                                  |
    |   57|* Verbuchung Statusobjekte                                                                  |
    |   58|  DESCRIBE TABLE jsto_ins LINES sy-tabix.                                                   |
    |   59|  IF sy-tabix > 0.                                                                          |
    |>>>>>|    INSERT jsto CLIENT SPECIFIED                                                            |
    |   61|                FROM TABLE jsto_ins.                                                        |
    |   62|  ENDIF.                                                                                    |
    |   63|  DESCRIBE TABLE jsto_upd LINES sy-tabix.                                                   |
    |   64|  IF sy-tabix > 0.                                                                          |
    |   65|    field-symbols <fs_jsto_line> like jsto_upd.                                             |
    |   66|    loop at jsto_upd assigning <fs_jsto_line>.                                              |
    |   67|      IF <fs_jsto_line>-chgnr = '000'.                                                      |
    |   68|        <fs_jsto_line>-chgnr = '999'.                                                       |
    |   69|      ENDIF.                                                                                |
    |   70|* on change of status profile delete user status related to old profile                     |
    |   71|      IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD.                                  |
    |   72|        DELETE FROM JEST CLIENT SPECIFIED WHERE                                             |
    |   73|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   74|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   75|               STAT  LIKE 'E%'.                                                             |
    |   76|        DELETE FROM JCDS CLIENT SPECIFIED WHERE                                             |
    |   77|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   78|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   79|               STAT  LIKE 'E%'.                                                             |

    i tried with out using commmit but it is not creating Status.
    When i see the function module help and they are trying to COMMIT
    FU STATUS_OBJECT_CREATE
    Short Text
    Create Status Object
    Functionality
    The function module generates a status object.
    Take the object number from the object number management (function modules OBJECT_NUMNBER_GET_xx).
    If no object number is given, the module takes a temporary object number that must be replaced later (function module STATUS_OBJECT_SWITCH_NUMBER).
    Example
    Creating an internal order with number 100123 (object type "ORC") for status profile "STATSCHEM" with final object number
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        objnr = objektnummer
        obtyp = 'ORC'
        stsma = 'STATSCHEM'.
    commit work.
    Creating the same order with a temporary object number
    data: objectkey like ionra.
    * TBO00-REFSTRUCT for object type 'OR' is 'IONRA'
    objectkey-aufnr = '100123'.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        i_objectkey = objectkey
        obtyp       = 'ORC'
        stsma       = 'STATSCHEM'.
      importing
        objnr       = objektnummer.
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer_neu.
    call function 'STATUS_OBJECT_SWITCH_NUMBER'
      exporting
        objnr_old = objektnummer
        objnr_new = objektnummer_neu.
    commit work.
    Notes

  • No longer able to edit images inside the blog module? Has BC removed this function?

    When inserting images into a blog post I used to be able to resize images, add margins, etc. I tried to do this recently but those tools were no longer there. Is this no longer available? Below is a screenshot of what it used to look like.
    Since there is no featured image for blog posts I've been inserting images into the first paragraph as a work around. Not being able to edit those images directly in the blog module is going to make that more difficult.
    I've been able to resize the image through code, but this is not exactly user friendly for clients.

    Hi Beth, Liam answered this for me on another post.
    Go into site settings / beta features/ untick active beta feature untick "enable for everybody". That should do the trick.
    Check this link to see the conversation I am having with liam as I think we are on the same page....or maybe you can help with my questions...
    is it possible to truncate the blog so 2 paragraphs show up?
    cheers,
    d

  • How to use the Bluetooth module natively in Parallels Desktop

    link to the instructions on how to enable bluetooth natively in parallels:
    http://www.mattiouz.com/blog/2007/04/13/how-to-use-the-built-in-mac-bluetooth-in -windows-under-parallels/
    link to the .exe that installs the apple driver for the bluetooth module needed in parallels: http://www.mattiouz.com/download/AppleBluetoothInstaller.exe
    now my bluetooth is accessible under parallels 3.0.5158. i scanned with a bluetooth netowrk scanner and i had no problems connecting to my treo 650.
    i took my some time to find the info but @ last i found it;-)
    Message was edited by: smokeonit

    Hi,
    You canr use text modules in script. You have to use standard texts .
    Standard text are maintained in SO10 transaction.
    you can create translation text for other languages also . So based on logon language it will print translation text.
    go to SO10
    give textname it say Ztextname  id as ST and language as EN
    say create, then you will get editor there maintain your text and save it . then come back . Now change language (say for german DE) say create and eneter translation text and save it.
    so now you have created a text called ztextname which you can use in your script.
    Inorder to insert the texts in your script do as below
    go to any window editor and   select path
    Insert->texts->symbols->standard symbols
    then you will get popup  in which you have to mention all the parameters that you have created earlier.
    after inserting just change language EN to sy-langu
    Reward points if useful
    About text elements Sravan already given some informatiomn
    Regards,
    Nageswar

  • What is the current way of managing the CSM using a GUI?

    Hi, My customer is using CiscoView device manager 1.1 for the content switching module but it's a nightmare and full of bugs, it's also end of life.
    Does anyone know the current way of monitoring or configuring the Content Switching Module?
    Many Thanks in advance
    Dom

    Hi Dom,
    I believe what you are looking for is called the Cisco Application Networking Manager 3.0.  This is the GUI configuration, management, and monitoring tool for the Application Control Engine (ACE), but also supports the managment of CSS, CSM, CSM-S, and GSS.  See the link for more details.
    Also, it should be noted that both the CSM and CSM-S have recently been announced End-of-Life.  The ACE would be your path after the CSM.  See the link for more details on that too.
    Hope this helps,
    Sean

Maybe you are looking for

  • Aperture not working properly in iLife, iWork, and Mail

    I am placing this issue in Aperture as it occurred after the 3.1.3 update. We use Photo Browser to place a photo in a Mac Mail, iLife and iWork. With the update, 3.1.3, using Photo Browser we see only the first photo per project. In Aperture we do se

  • Dynamic Standard text - Appending text with variable

    Dear All, We have a dynamic standard text. The text is being created based on sales order (I don't know how this has been created). Now I want to add text inside the standard text. That text will also contain variable. Example: "This is a valid sales

  • Can I trade an older device for a newer device?

    I currently have an iPod 4th gen. and I was just curious if I could trade it in for maybe like a store credit towards a newer 5th gen. iPod?

  • Apple Remote Desktop 2.2 not able to do a storage report

    For some reason after updating to 10.4.7 i am unble to request a storage report to 1 or more computers. It comes back to me and says "Report database access not allowed" so im not sure where to begin. I can do a network test and i can chekc administr

  • Withdrawl posting and the GL account

    Hi all, My client has the particular requirement as follows--- When the order confirmation is done, the components are backflushed & inventory transction is carried out by 261 movement type as always. Then as per IMG settings proper GL accounts is pi