How to increase the date of expiration

Hi,
I have 4.7 version installed at my home PC, it's license has been expired.How to increase its expiry date to future.And also it shows the system date 30-01-2005.
How can i change it to 30-01-2006.
Regards,
Veda Kumar.

Pick yourself up by your own bootstrap too?
Reinstall after restoring to HFS only then.
You want something that works, then spend the $20 on Paragon CampTune or WinClone 3.

Similar Messages

  • How to increase the number of data Business Object can pull for a report?

    Hi,
    I would like to ask around how to increase the number of data Business Object can pull for a report. I have a report which pulls data depending on the date range (ex. From 01/01/2007 - 01/10/2007). But, when the data that is pulled exceeds 5000, the report fails. Is there anyway to increase the number of data that BO can pull?
    Thanks

    Bobby,
       to my knowledge we can't change that. Let me explain this, we have setting in the source system for DS default Data Transfer. there we will assign the processes. if you want to assign 4 you need to change the setting in the source system. For flat files we can change in BW System. We can maintain the setting in the Infopackage level(wht we are assigned in the Source System), but we can't change the process.
    in order to check the setting in source system  SBIW--> General Settings --> Control Parameters for Data Transfer.
    we need to change here, this will effect to all the Data Sources. Before making changes check with your basis.
    All the best.
    Regards,
    Nagesh Ganisetti.

  • Server Admin - How current is the data?

    Good afternoon.
    When I view the DHCP data in Server Admin, how current is the data? When I close down workstations and logon others, the data displayed, even after multiple refreshes, does not change. A quit & relaunch doesn't update the data either.
    Can I rely on Server Admin to provide a current, accurate view?
    Brian Bowell
    Berkley Normal Middle School
    Hamilton New Zealand.

    I'm not sure of the frequency at which Server Admin re-polls the data, but nothing is cached so at the very least each time you connect to a server you're seeing data that's valid up until then.
    However, in the case of DHCP you need to consider lease duration.
    If your lease is set to something like 3 days then any given client will remain in the DHCP leases list for that long.
    In other words, assuming you have one DHCP client on your network and that machine boots on Monday Afternoon, then that machine will appear in the DHCP leases list until at least some time on Thursday afternoon. The number of leases will not decrease when the machine shuts down on Tuesday, nor increase if that machine comes back online before the original lease expiration (it will just be re-issued the same DHCP lease/IP address/etc.). Therefore your lease counter will remain at 1 even when the machine is offline.
    Is it possible that accounts for what you're experiencing? The number of leases does not reflect the number of active DHCP clients on your network, just the number that have been active within the last (lease duration) hours.

  • How to delete the data from partition table

    Hi all,
    Am very new to partition concepts in oracle..
    here my question is how to delete the data from partition table.
    is the below query will work ?
    delete from table1 partition (P_2008_1212)
    we have define range partition ...
    or help me how to delete the data from partition table.
    Thanks
    Sree

    874823 wrote:
    delete from table1 partition (P_2008_1212)This approach is wrong - as Andre pointed, this is not how partition tables should be used.
    Oracle supports different structures for data and indexes. A table can be a hash table or index organised table. It can have B+tree index. It can have bitmap indexes. It can be partitioned. Etc.
    How the table implements its structure is a physical design consideration.
    Application code should only deal with the logical data structure. How that data structure is physically implemented has no bearing on application. Does your application need to know what the indexes are and the names of the indexes,in order to use a table? Obviously not. So why then does your application need to know that the table is partitioned?
    When your application code starts referring directly to physical partitions, it needs to know HOW the table is partitioned. It needs to know WHAT partitions to use. It needs to know the names of the partitions. Etc.
    And why? All this means is increased complexity in application code as this code now needs to know and understand the physical data structure. This app code is now more complex, has more moving parts, will have more bugs, and will be more complex to maintain.
    Oracle can take an app SQL and it can determine (based on the predicates of the SQL), which partitions to use and not use for executing that SQL. All done totally transparently. The app does not need to know that the table is even partitioned.
    This is a crucial concept to understand and get right.

  • How to increase the number of rows to be displayed in BEx Web Analyzer

    hi,
    I am viewing reports using BEx Web analyzer option. It is displaying only 24 rows  of data at a time. How to increase the number of rows? do i need to any kind of settings?
    pls reply.

    Hi,
    I think the standard template in 2004s is named 0ANALYSIS_PATTERN. You can find it in Web Application Designer, open, and search for the technical name. If you want to change the number of rows or columns, you can find this setting near the bottom of the XHTML view of the template:
    <bi:BLOCK_COLUMNS_SIZE value="4" />
    <bi:BLOCK_ROWS_SIZE value="17" />
    Then just save, and ignore the error messages.
    Message was edited by:
            vind Reinsberg

  • How to increase the battery life of your N series ...

    What I am about to post here is valid for any 3G phone or device regardless of model but it is particularly focused towards the N series devices and their power hogging features.
    Your battery life is dependant on many many things. How often you take calls on the device, the condition of your battery, the features you use on the device and so on and on. Therefore it is impossible to say that by following the information in this post you will get x amount of days battery life, but it will get you more time out of the battery than you otherwise would have got.
    So with that out the way, if your looking to increase your battery life then follow these tips and your battery should start looking a lot healthier.
    First of all lets start with THE big one. The one that is going to save you the most juice. Switching 3G off.
    Yep, you heard me right. Just by switching the 3G capability of your phone off you will add hours and hours to your battery life. How is this so? Allow me to explain...
    Due to the rather poor delivery of 3G in the UK by the network operators, it is rare for any 3G phone to maintain a constant 3G signal. Instead you will find that the phone constantly flips between 3G and GSM mode (Keep an eye on your signal one day). Even those of you on Vodafone who probably have the best 3G network coverage will find this is the case.
    Unfortunately, this constant flipping between the two modes sucks power from the battery like a vampire as it alters its reception state for the different modes and the constant flipping is..well...causing it do this constantly! It can sometimes even make your phone unavailable for calls for very brief periods as it trips from GSM to 3G and vice versa.
    If you need to use 3G for video calls or whatever then I'm afraid your just going to have to live with this but if you don't (And lets face it few of us do) then you can switch 3G off and increase your battery life considerably.
    To do this, go into the "Settings" application (Found in the menu somewhere, by default Nokia normally stick it in "Tools"), and then to the "Phone" tab. In there you will see an option that says "Network mode" and you have a choice of "GSM" or "Dual Mode" (I.e. UMTS and GSM). Set it to GSM and your phone will restart. Once it restarts it will be working in GSM with GPRS speeds only but really for most purposes this is fine.
    You have now just extended your battery capability considerably. You can further extend it by going to the "Connection" tab, going into "Packet data" and changing it to "When needed" so it is not constantly checking for a data connection.
    The second big change you can make is to turn your phones wifi scanning capability off. The last time I looked not all Nokia's phones that have wifi capability can have their wifi cards switched off entirely but if you can, turn it off except for when you need to use it. Wifi is a power hog.
    The next big change you can make is to lower the screen brightness settings on your phone. The less bright your screen is the less power is being used to light it up. Nokia by default leave the screen brightness at something like 50%. Lowering this a bit more will conserve more juice. Before you do this though please consider the fact that lowering the brightness setting will have a big impact on your ability to see the screen clearly in sunny conditions although you will be fine in the dark as you can't lower the brightness that far.
    To lower the brightness, go to the settings tool in your phone and into the display option (Hidden in a subcategory called "Personalisation" on the N95). It won't hurt to set the power saving time out to 1 minute and the backlight time out to 10 seconds while your here (Although these are the Nokia default so they should already be set to this).
    Finally in regards to the screen, although they may look pretty, animated screensavers use more battery power than the standard blank screen with time and date so avoid them if you can.
    It also helps to keep Bluetooth switched off until you need it although the power savings are minimal in comparison to the other changes but every little milliamp counts!
    Using the above methods I generally get about 3 to 4 days with about 3 hours talktime on my N95 without using Bluetooth, GPS or anything like that (I might be able to get more but so far I have not paid attention to the battery state before I put it on charge). If I am on a long train journey I can get about 4 hours worth of full screen video and about 2 hours talktime over the period of about 24 hours before it needs a recharge. As I said at the start of the post your mileage will vary greatly depending on how you use your device.
    Hope this helps.
    Useful links: Phone firmware update | Nokia support site

    02-May-200701:14 PM
    bixby wrote:
    no keffa it is a cop out from nokia
    its not unfai as its a premium device with a premium price
    the n95 battery is atrocious
    dont change the post content as the title is 'How to increase the battery life of your N series device'
    your talking about nokia phones specifically
    the networks are not to blame
    they do not make the handsets : Nokia do !!!!!!!!!!
    I'm going to choose my words carefully here...
    I would never deny the battery on the N95 is not really up to the job of powering the N95 with its power hungry features. To put the same battery into a phone that has WiFi, GPS and a large 320x240 screen, the same one that goes into the E65 which has comparatively nothing compared to it is a bit pants.
    However at no point was I criticising them for the band hopping problem. I labelled the post as how to increase the battery life of your N series device because this is a board for the N series devices. It was a simple choice of wording and not intended to be cutting in any way and I did make a remark that the details would be true of any 3G device at the top of the post.
    What I was trying to point out in my second post is that the constant band hopping the phone is being forced to do that is draining its battery so much more quicker than it would if it had a constant signal of one kind or another isn't quite Nokia's fault.
    They build it to conform to a laid out specification for 3G. However if the network operators cannot be bothered to roll out their 3G infrastructure adequately enough that the phone can find and remain locked onto a 3G signal that is usable then what are Nokia to do other than offer you the capability to turn 3G off until you need it (Although note to Nokia: That **bleep** reboot the phone does when you do this is entirely unneeded and you know it).
    Blaming Nokia for this would be like blaming the manufacturer of your radio for failing to pick up radio because the radio station does not have any transmitters within range of your radio's receiver.
    Finally...this band hopping is exhibited by all 3G phones built by Samsung, Nokia, Sony Ericsson, etc, from their most budget 3G model to their priciest piece and is the reason that all phones with 3G capabilities have batteries that do not last for any respectable length of time because these phones are also having to band hop between 3G and GSM.
    Finally the proof is in the pudding. Turn 3G off for a few days. See your battery improve. Then (Although admittedly this will be harder to do...mcuh harder) find an area where you get a fairly decent 3G signal constantly. Again, see your battery improve. Try it with a different 3G phone...different manufacturer even. The same will be true.
    So I stand by my comment, the network operators and their woeful 3G rollout are the villains costing you a fair chunk of your battery and Nokia cannot be expected to mitigate this....but a better battery would be nice all the same...
    Useful links: Phone firmware update | Nokia support site

  • How to increase the waiting time for response in Adapter Engine not in IE

    Hi Experts,
                It is a SOAP to Proxy Synchronous interface. SOAP system is sending the request to PI, PI sending the same request to ECC system, After execution of some logic response back to PI in 7 minutes. In ABAP Stack(sxmb_moni) processing the response message also successfully with success flag after completion of these 7 minutes. But exactly 5 minutes later getting the error at Java Stack RWB- in communication channel monitoring i.e
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bd2bf8d0-b2c2-11e0-c383-001cc4fb5cb7(OUTBOUND) expired.  We have set the "runtime-HTTP_TIMEOUT" parameter as 3600. thats why in Integration engine it is processing successfully.
    kindly suggest me how to increase the waiting time for response in Adapter Engine. Exactly after 5 mins getting the above error in rwb, but in Integration Engine getting successful flag after 7 mins until then it is waiting for response with  status flag Log version.
    Thanks & Regards,
    Srihari.

    Hi,
    Please see
    How To... Investigate Timeouts In Synchronous XI/PI Scenarios
    It will answer all your queries
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true

  • How to increase the length of internal table dynamically

    How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
    The requirement code :
    types: begin of t_data,
             form          like zscr_data_hdr-form,
             werks         like zscr_data_hdr-werks,
             matnr         like zscr_data_hdr-matnr,
             verid         like zscr_data_hdr-verid,
             lot           like zscr_data_hdr-lot,
             lot_qty       like zscr_data_hdr-lot_qty,
             udate         like zscr_data_hdr-udate,
             utime         like zscr_data_hdr-utime,
             zuser         like zscr_data_hdr-zuser,
             processed     like zscr_data_hdr-processed,
             defect        like zscr_defect_data-defect,
             vornr         like zscr_route_data-vornr,
             fld1          like zscr_defect_data-defect_val,
             fld2          like zscr_defect_data-defect_val,
             fld3          like zscr_defect_data-defect_val,
             fld4          like zscr_defect_data-defect_val,
             fld5          like zscr_defect_data-defect_val,
             fld6          like zscr_defect_data-defect_val,
             fld7          like zscr_defect_data-defect_val,
             fld8          like zscr_defect_data-defect_val,
             fld9          like zscr_defect_data-defect_val,
             fld10         like zscr_defect_data-defect_val,
             fld11         like zscr_defect_data-defect_val,
             fld12         like zscr_defect_data-defect_val,
             fld13         like zscr_defect_data-defect_val,
             fld14         like zscr_defect_data-defect_val,
             fld15         like zscr_defect_data-defect_val,
             fld16         like zscr_defect_data-defect_val,
             fld17         like zscr_defect_data-defect_val,
             fld18         like zscr_defect_data-defect_val,
             fld19         like zscr_defect_data-defect_val,
             fld20         like zscr_defect_data-defect_val,
             fld21         like zscr_defect_data-defect_val,
             fld22         like zscr_defect_data-defect_val,
             fld23         like zscr_defect_data-defect_val,
             fld24         like zscr_defect_data-defect_val,
             fld25         like zscr_defect_data-defect_val,
             fld26         like zscr_defect_data-defect_val,
             fld27         like zscr_defect_data-defect_val,
             fld28         like zscr_defect_data-defect_val,
             fld29         like zscr_defect_data-defect_val,
             fld30         like zscr_defect_data-defect_val,
             fld31         like zscr_defect_data-defect_val,
             fld32         like zscr_defect_data-defect_val,
             fld33         like zscr_defect_data-defect_val,
             fld34         like zscr_defect_data-defect_val,
             fld35         like zscr_defect_data-defect_val,
             fld36         like zscr_defect_data-defect_val,
             fld37         like zscr_defect_data-defect_val,
             fld38         like zscr_defect_data-defect_val,
             fld39         like zscr_defect_data-defect_val,
             fld40         like zscr_defect_data-defect_val,
             fld41         like zscr_defect_data-defect_val,
             fld42         like zscr_defect_data-defect_val,
             fld43         like zscr_defect_data-defect_val,
             fld44         like zscr_defect_data-defect_val,
             fld45         like zscr_defect_data-defect_val,
             fld46         like zscr_defect_data-defect_val,
             fld47         like zscr_defect_data-defect_val,
             fld48         like zscr_defect_data-defect_val,
             fld49         like zscr_defect_data-defect_val,
             fld50         like zscr_defect_data-defect_val,
             fld51         like zscr_defect_data-defect_val,
             fld52         like zscr_defect_data-defect_val,
             fld53         like zscr_defect_data-defect_val,
             fld54         like zscr_defect_data-defect_val,
             fld55         like zscr_defect_data-defect_val,
             fld56         like zscr_defect_data-defect_val,
             fld57         like zscr_defect_data-defect_val,
             fld58         like zscr_defect_data-defect_val,
             fld59         like zscr_defect_data-defect_val,
             fld60         like zscr_defect_data-defect_val,
             fld61         like zscr_defect_data-defect_val,
             fld62         like zscr_defect_data-defect_val,
             fld63         like zscr_defect_data-defect_val,
             fld64         like zscr_defect_data-defect_val,
             fld65         like zscr_defect_data-defect_val,
             fld66         like zscr_defect_data-defect_val,
             fld67         like zscr_defect_data-defect_val,
             fld68         like zscr_defect_data-defect_val,
             fld69         like zscr_defect_data-defect_val,
             fld70         like zscr_defect_data-defect_val,
             fld71         like zscr_defect_data-defect_val,
             fld72         like zscr_defect_data-defect_val,
             fld73         like zscr_defect_data-defect_val,
             fld74         like zscr_defect_data-defect_val,
             fld75         like zscr_defect_data-defect_val,
             fld76         like zscr_defect_data-defect_val,
             fld77         like zscr_defect_data-defect_val,
             fld78         like zscr_defect_data-defect_val,
             fld79         like zscr_defect_data-defect_val,
             fld80         like zscr_defect_data-defect_val,
             fld81         like zscr_defect_data-defect_val,
             fld82         like zscr_defect_data-defect_val,
             fld83         like zscr_defect_data-defect_val,
             fld84         like zscr_defect_data-defect_val,
             fld85         like zscr_defect_data-defect_val,
             fld86         like zscr_defect_data-defect_val,
             fld87         like zscr_defect_data-defect_val,
             fld88         like zscr_defect_data-defect_val,
             fld89         like zscr_defect_data-defect_val,
             fld90         like zscr_defect_data-defect_val,
             fld91         like zscr_defect_data-defect_val,
             fld92         like zscr_defect_data-defect_val,
             fld93         like zscr_defect_data-defect_val,
             fld94         like zscr_defect_data-defect_val,
             fld95         like zscr_defect_data-defect_val,
             fld96         like zscr_defect_data-defect_val,
             fld97         like zscr_defect_data-defect_val,
             fld98         like zscr_defect_data-defect_val,
             fld99         like zscr_defect_data-defect_val,
             fld100         like zscr_defect_data-defect_val,
             fld101         like zscr_defect_data-defect_val,
             fld102         like zscr_defect_data-defect_val,
             fld103         like zscr_defect_data-defect_val,
             fld104         like zscr_defect_data-defect_val,
             fld105         like zscr_defect_data-defect_val,
             fld106         like zscr_defect_data-defect_val,
             fld107         like zscr_defect_data-defect_val,
             fld108         like zscr_defect_data-defect_val,
             fld109         like zscr_defect_data-defect_val,
             fld110         like zscr_defect_data-defect_val,
             fld111         like zscr_defect_data-defect_val,
             fld112         like zscr_defect_data-defect_val,
             fld113         like zscr_defect_data-defect_val,
             fld114         like zscr_defect_data-defect_val,
             fld115         like zscr_defect_data-defect_val,
             fld116         like zscr_defect_data-defect_val,
             fld117         like zscr_defect_data-defect_val,
             fld118         like zscr_defect_data-defect_val,
             fld119         like zscr_defect_data-defect_val,
             fld120         like zscr_defect_data-defect_val,
             fld121         like zscr_defect_data-defect_val,
             fld122         like zscr_defect_data-defect_val,
             fld123         like zscr_defect_data-defect_val,
             fld124         like zscr_defect_data-defect_val,
             fld125         like zscr_defect_data-defect_val,
             fld126         like zscr_defect_data-defect_val,
             fld127         like zscr_defect_data-defect_val,
             fld128         like zscr_defect_data-defect_val,
             fld129         like zscr_defect_data-defect_val,
             fld130         like zscr_defect_data-defect_val,
             fld131         like zscr_defect_data-defect_val,
             fld132         like zscr_defect_data-defect_val,
             fld133         like zscr_defect_data-defect_val,
             fld134         like zscr_defect_data-defect_val,
             fld135         like zscr_defect_data-defect_val,
             dayst         like zscr_data_hdr-dayst,
           end of t_data.
    In this fld1 to fld135 are defined in internal table.
    But if the number of fields are more than 135 then the program is going to short dump.
    Some times fld1 to fid170 or more fields will be there in my internal table.
    Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

    Hi
    You can try to use the type string:
    form like zscr_data_hdr-form,
    werks like zscr_data_hdr-werks,
    matnr like zscr_data_hdr-matnr,
    verid like zscr_data_hdr-verid,
    lot like zscr_data_hdr-lot,
    lot_qty like zscr_data_hdr-lot_qty,
    udate like zscr_data_hdr-udate,
    utime like zscr_data_hdr-utime,
    zuser like zscr_data_hdr-zuser,
    processed like zscr_data_hdr-processed,
    defect like zscr_defect_data-defect,
    vornr like zscr_route_data-vornr,
    fieldxx type string,
    dayst like zscr_data_hdr-dayst,
    end of t_data.
    So you can save you informations of every fld<n> concatenating their values into fieldxx.
    Max

  • How To Increase the Size of Memo Fields 4000 Char in WebCenter 11g?

    How To Increase the Size of Memo Fields greater than 4000 Char in WebCenter Content (UCM) 11g?
    I was able to increase the size of Memo field from 2000 Char to 4000 by setting parameter value MEMOFIELDSIZE=4000 . But the requirement is to increase the size more than 4000 around 7000 char but Database(Oracle 11G) is not supporting more than 4000 char.
    Is there any other way to increase the size of Memo field?
    Thanks in Advance!!
    Regards
    Ram

    Hello All,
    Thanks for your responses.
    Let me explain the scenario again in detail:
    1. we have three meta-data fileds xProductCategory,xProductFamily and xProducts
    2. These fields are related with DCL feature and corresponding values are being stored in corresponding custom Views
    3. xProducFamily is dependent of xProductCategory and xProduct is dependent on xProductFamily
    4. currently, there are around 250 Product values and average name of Product can be of 25 Char, so if we are selecting all product values for some Contents then Product Values are being stored in DocMeta table as comma separated values with one space, so total characters are being very high than 4K Char.
    5. Currently view that is storing the Product values, stores "Name" column instead of ID(like 1,2,3....)
    6. And our Content Server is integrated with Oracle WebSenter Portal, where logic has written to retrieve the contents based on "Product Name" instead of "Product ID" and already we are in UAT phase.Currently we are not in situation to revert the changes from Product Name to Product ID.
    7. Also if we are storing the values on the basis of Product ID, then again the issue may arise in Future, if the number of Products increased.
    Hoping the issue explanation is clear now and waiting for some possible solution for increasing the length of memo field.
    Thanks in Advance !!
    Regards
    Ram

  • How  to increase the database size

    Hi All ,
    Our Client is going to increase their customers from 3.5 million to 5 millions
    (12 millions in future ) and there is no increase in the existing licenses..
    At present we have very less space in Data base server. We are Going Live at the End of the Month.
    How to increase the database size to meet the Client requirements.
    we have to increase the No of Processerors etc...
    Below are the details of Servers:
    System Model: IBM,7040-681
    Machine Serial Number: 830D5BF
    Processor Type: PowerPC_POWER4
    Number Of Processors: 2
    Processor Clock Speed: 1904 MHz
    CPU Type: 64-bit
    Kernel Type: 64-bit
    LPAR Info: 4 bgl-svr-biap
    Memory Size: 4096 MB
    Good Memory Size: 4096 MB
    Note : Server is IBM P690.
    1)  System Lansdcape --> Two System Landsacpe ( Dev to Prod )
    2)  BW Version --> 3.5
    3)  SAP Basis --- > 6.4
    4)  No of Application servers currently having --> Only  One  Server
    Can any body suggest me how to solve this.....
    Thanks in Advance..
    Kasi Chukka

    Hi Kasi,
    Your question is not very clear, from the looks of it, the load on your client's system will be doubling soon.
    You need to look at the system stats on how the system is handling the current load, use transactions ST06, ST04 and ST02 to check if the DB hit ratios are as expected, the cpu idle time, the busy periods. Identify if there is large amounts of paging on the server(candidate for increase in real memory).
    On AIX level, you will need to look at CPU / Memory usage.
    On SAP Application server, you need to look at SAP Buffers.
    On Oracle end, look at SGA stats, if it need to increase, the data growth that is current and estimated growth (DB02).
    You will not get an exact answer to it, you will need to analyze the existing load and then estimate (guess). The hardware upgrade will also depend on what the client is willing to spend, its always a good practise to add 20% to what you have estimated as these figures are never accurate.
    All the best.
    Cheers,
    Nisch

  • How to increase the column size of Alv tbale

    Hi All,
    I created an Alv table to display the content of my database table. In one of the column the entire data from my database are not displayed the last few characters are missing. The data type for that column in the database is char. Can any one help me how to increase the column size in my Alv table or any suggestions to resolve this issue.

    Hi Vadiv,
    Try with this..
    DATA: LR_IF_CONTROLLER TYPE REF TO IWCI_SALV_WD_TABLE,
    LR_CMP_USAGE TYPE REF TO IF_WD_COMPONENT_USAGE,
    LR_CMDL TYPE REF TO CL_SALV_WD_CONFIG_TABLE,
    LR_TABLE_SETTING TYPE REF TO IF_SALV_WD_TABLE_SETTINGS.
    LR_CMP_USAGE = WD_THIS->WD_CPUSE_ALV( ).
    IF LR_CMP_USAGE->HAS_ACTIVE_COMPONENT( ) IS INITIAL.
    LR_CMP_USAGE->CREATE_COMPONENT( ).
    ENDIF.
    " get reference to the ALV model
    LR_IF_CONTROLLER = WD_THIS->WD_CPIFC_ALV( ).
    LR_CMDL = LR_IF_CONTROLLER->GET_MODEL( ).
    LR_TABLE_SETTING ?= LR_CMDL.
    " Set column width
    DATA LR_COL TYPE REF TO CL_SALV_WD_COLUMN.
    LR_COL = LR_CMDL->IF_SALV_WD_COLUMN_SETTINGS~GET_COLUMN( 'PERNR' ).
    LR_COL->SET_WIDTH( '70' ) .
    LR_COL = LR_CMDL->IF_SALV_WD_COLUMN_SETTINGS~GET_COLUMN( 'ENAME' ).
    LR_COL->SET_WIDTH( '100' ) .
    LR_TABLE_SETTING->SET_FIXED_TABLE_LAYOUT( ABAP_TRUE ).
    You can refer to webdynpro component SALV_WD_TEST_TABLE_PROPS. Go to the view TABLE and look inside the method SET_COLUMN_SETTINGS. I hope this will help you.
    Cheers,
    Kris.

  • How to Increase the # of Recently Opened Files in DW CS6 ???

    Can anyone please give a detailed instruction on how to increase the number of Recently Opened files in Dreamweaver CS6? I have read the forums everywhere and do not see a solution here that works. For me there is no: Menus/MM/File_RecentFiles.htm
    I mean I have a "Menus" directory but no "MM" directory inside that... also, if I create one... I still need a sample "File_RecentFiles.htm" to copy. Or maybe someone knows another solution?

    I don't have DWCS6, just DWCS4 and DWCC. When I go to Program Files(x86) > Adobe >  Adobe Dreamweaver CC (or Dreamweaver CS4) > configuration > Menus > MM > and then open the file named "File_RecentFiles.htm" at either location, this is the code...
    <!-- MENU-LOCATION=NONE -->
    <html xmlns:MMString="http://www.macromedia.com/schemes/data/string/">
    <HEAD>
    <!-- Copyright 2000, 2001, 2002, 2003, 2004, 2005 Macromedia, Inc. All rights reserved. -->
    <TITLE><MMString:loadString id="Menus/MM/File_RecentFiles/title" /></TITLE>
    <SCRIPT LANGUAGE="javascript" SRC="../../Shared/MM/Scripts/CMN/string.js"></SCRIPT>
    <SCRIPT LANGUAGE="javascript" SRC="File_RecentFiles.js"></SCRIPT>
    <SCRIPT LANGUAGE="javascript">
    <!--
    //--------------- LOCALIZEABLE GLOBALS---------------
    var MENU_RecentFile  = dw.loadString('Menus/MM/File_RecentFiles/MENU_RecentFile');
    //--------------- END LOCALIZEABLE   ---------------
    // -->  
    </SCRIPT>
    </HEAD>
    <BODY>
    </BODY>
    </HTML>
    EDIT: It appears you should definitely have this file, unless something is wrong with your installation, or perhaps you are in the wrong directory?

  • How to increase the line items against the std no of line items in MIGO

    hi,
    I have PO with more than 100 line items
    During GR system is showing the error message as
    Maximum number of items F1 reached
    What is the standard no of line items in MIGO
    And how to increase the line items
    Is there any notes to apply
    plz give sutable solution
    K.Raghuram

    Do you get message F5727 "Maximum number of items in FI reached"? reason is that in FI the posting line has a three-digit line item number (BSEG-BUZEI).
    SAP's note 117708 provides a modification. I am pasting solution below.
    Via the summarization you can post documents with more than 999 items in
    FI.
    The modification required for this is small, in addition you have to
    change 2 tables. The modification is carried out in FI not in invoice
    verification.
    To activate document summarization in FI proceed as follows:
    - The changes are described in Note 36353 and for the
    modification in Note 77161. You may also have to apply Note
    67640 so that the document summarization affects inventory
    management.
    An advice for the notes:
    36353: Solution point 3: Field name WERKS
    77161: Solution point 2: Maintain table TTYPV with Transaction
    SE16
    - this has the following effects; you can no longer clear the
    GR/IR clearing account on purchase order item level (but only
    on purchase order level) and you can only display the FI data
    summarized (also see Note 36353)

  • How to increase the font size of the report output in the printout.

    Hi Team,
    i have a requirement like to print the report output as a direct print from an internal table.I am using the below mentioned code, the output is printing fine but the Font size of the output text is so small so i need to increase the font size of the text of output data.
    call function 'GET_PRINT_PARAMETERS'
       exporting
         immediately                    = 'X'
         line_count                     = 65
         line_size                      = 320
         mode                           = 'CURRENT'
         no_dialog                      = ' '
         release                        = 'X'
         user                           = sy-uname
       importing
         out_parameters                 = st_param
       exceptions
         archive_info_not_found         = 1
         invalid_print_params           = 2
         invalid_archive_params         = 3
         others                         = 4.
      if sy-subrc eq 0.
        new-page print on parameters st_param no dialog.
    could you please suggest me how to increase the font size while printing the report output..
    Thanks in Advance.
    Puneet.

    hey,
    in our system when we click on print. on widow is coming.
    there is a properties button.
    we click on it.
    there FORMAT----AND then we select forat from there and then printing .
    not sure. but check on ur system. is there properites button.
    HI,
    READ THIS,
    You can specify attributes such as the character width and font size in the device type formatting yourself.
    contact ur basis team .
    in the report PRINT-CONTROL SIZE option is there. try to find more o this.

  • How to increase the decimals in RPD for some field?

    Hello gurus,
    We have 1 filed in DW name as "EXCHANGE_RATE" when i query it DW it's showing me values with 4 decimal points.
    and same column when i m using in OBIEE frontend, it's giving me values with 2 decimals.
    So how to increase the decimals for that field in RPD?
    we have 10.1.3.4.1 version.
    Thanking You.

    Hello Svee,
    Thanks for ur help, But I found one different way that will make change only to that particular filed.
    Bcz if I will change the database properties that will change the configuration globally to all the fields.
    So what I did is, I went to column properties and change the Data Format to 4 decimals and saved it as System-wide default for that field.
    So, the change that i want will be their only for that filed...
    Though I really appreciate ur help.
    Thanking you.

Maybe you are looking for

  • How do I fix my 3gs after 6.1.3 update? It will no longer send / receive group messages and won't send pic text messages either.

    Ever since I updated my 3gs (on ATT) to 6.1.3, it will no longer send or receive group texts, and it won't send picture messages (though I seem to be able to receive picture texts). I've looked around on the boards, and here's what I've tried so far

  • Zoom and Pan for Adobe Premiere Elements 12?

    I have Adobe Premiere Elements 12. I would like to zoom and pan into a video, but without that slow zoom in/out effect. Basically, I want it like a quick cut close up then back to the original size. I've been trying but nothing seems to work. There's

  • Adding a customer infotype in PPOME

    Hello experts, I'am trying to add a new customer infotype to PPOME, which should be displayed for all nodes of type "O" - so far, so good. I created the Structure HCI9600 and then I used PPCI without any problems. The new infotype is a part of PPOME,

  • DOS Window in Java Container

    If anybody knows how, I'd appreciate any suggestions on how to present an Interactive DOS window in a JAVA SWING container.

  • Why does the Input Source keep changing?

    I have two languages in my list of Input Sources - Maori and Australian.  I normally have it set on Maori, but in the last week it's been defaulting back to Australian.  Anyone have any ideas how to resolve the issue??