Is this an optimization ?

env : jdk 5 or 6
import java.util.ArrayList;
import java.util.List;
public class Test {
     public void method(){
               List<Object> list = dao.getSomeData();
               for(Object obj: list){
                    doSomething(obj);
                    obj = null;//Here optimization
          public void doSomething(Object obj){
               //do something with computation based on object 'obj'
}thanks

jwenting wrote:
which makes it the reverse of an optimisation as you're now using a few more CPU cycles for every iteration through the List (unless of course the compiler is smart enough to remove the entire null assignment because it has no effect whatsoever).Wouldn't an optimizing compiler remove the unnecessary assignment?
¦ {Þ                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • In-Place Element Structures, References and Pointers, Compiler Optimization, and General Stupidity

    [The title of this forum is "Labview Ideas". Although this is NOT a direct suggestion for a change or addition to Labview, it seems appropriate to me to post it in this forum.]
    In-Place Element Structures, References and Pointers, Compiler Optimization, and General Stupidity
    I'd like to see NI actually start a round-table discussion about VI references, Data Value references, local variables, compiler optimizations, etc. I'm a C programmer; I'm used to pointers. They are simple, functional, and well defined. If you know the data type of an object and have a pointer to it, you have the object. I am used to compilers that optimize without the user having to go to weird lengths to arrange it. 
    The 'reference' you get when you right click and "Create Reference" on a control or indicator seems to be merely a shorthand read/write version of the Value property that can't be wired into a flow-of-control (like the error wire) and so causes synchronization issues and race conditions. I try not to use local variables.
    I use references a lot like C pointers; I pass items to SubVIs using references. But the use of references (as compared to C pointers) is really limited, and the implementation is insconsistent, not factorial in capabilites, and buggy. For instance, why can you pass an array by reference and NOT be able to determine the size of the array EXCEPT by dereferencing it and using the "Size Array" VI? I can even get references for all array elements; but I don't know how many there are...! Since arrays are represented internally in Labview as handles, and consist of basically a C-style pointer to the data, and array sizing information, why is the array handle opaque? Why doesn't the reference include operators to look at the referenced handle without instantiating a copy of the array? Why isn't there a "Size Array From Reference" VI in the library that doesn't instantiate a copy of the array locally, but just looks at the array handle?
    Data Value references seem to have been invented solely for the "In-Place Element Structure". Having to write the code to obtain the Data Value Reference before using the In-Place Element Structure simply points out how different a Labview reference is from a C pointer. The Labview help page for Data Value References simply says "Creates a reference to data that you can use to transfer and access the data in a serialized way.".  I've had programmers ask me if this means that the data must be accessed sequentially (serially)...!!!  What exactly does that mean? For those of use who can read between the lines, it means that Labview obtains a semaphore protecting the data references so that only one thread can modify it at a time. Is that the only reason for Data Value References? To provide something that implements the semaphore???
    The In-Place Element Structure talks about minimizing copying of data and compiler optimization. Those kind of optimizations are built in to the compiler in virtually every other language... with no special 'construct' needing to be placed around the code to identify that it can be performed without a local copy. Are you telling me that the Labview compiler is so stupid that it can't identify certain code threads as needing to be single-threaded when optimizing? That the USER has to wrap the code in semaphores before the compiler can figure out it should optimize??? That the compiler cannot implement single threading of parts of the user's code to improve execution efficiency?
    Instead of depending on the user base to send in suggestions one-at-a-time it would be nice if NI would actually host discussions aimed at coming up with a coherent and comprehensive way to handle pointers/references/optimization etc. One of the reasons Labview is so scattered is because individual ideas are evaluated and included without any group discussion about the total environment. How about a MODERATED group, available by invitation only (based on NI interactions with users in person, via support, and on the web) to try and get discussions about Labview evolution going?
    Based solely on the number of Labview bugs I've encountered and reported, I'd guess this has never been done, with the user community, or within NI itself.....

    Here are some articles that can help provide some insights into LabVIEW programming and the LabVIEW compiler. They are both interesting and recommended reading for all intermediate-to-advanced LabVIEW programmers.
    NI LabVIEW Compiler: Under the Hood
    VI Memory Usage
    The second article is a little out-of-date, as it doesn't discuss some of the newer technologies available such as the In-Place Element Structure you were referring to. However, many of the general concepts still apply. Some general notes from your post:
    1. I think part of your confusion is that you are trying to use control references and local variables like you would use variables in a C program. This is not a good analogy. Control references are references to user interface controls, and should almost always be used to control the behavior and appearance of those controls, not to store or transmit data like a pointer. LabVIEW is a dataflow language. Data is intended to be stored or transmitted through wires in most cases, not in references. It is admittedly difficult to make this transition for some text-based programmers. Programming efficiently in LabVIEW sometimes requires a different mindset.
    2. The LabVIEW compiler, while by no means perfect, is a complicated, feature-rich set of machinery that includes a large and growing set of optimizations. Many of these are described in the first link I posted. This includes optimizations you'd find in many programming environments, such as dead code elimination, inlining, and constant folding. One optimization in particular is called inplaceness, which is where LabVIEW determines when buffers can be reused. Contrary to your statement, the In-Place Element Structure is not always required for this optimization to take place. There are many circumstances (dating back years before the IPE structure) where LabVIEW can determine inplaceness and reuse buffers. The IPE structure simply helps users enforce inplaceness in some situations where it's not clear enough on the diagram for the LabVIEW compiler to make that determination.
    The more you learn about programming in LabVIEW, the more you realize that inplaceness itself is the closest analogy to pointers in C, not control references or data references or other such things. Those features have their place, but core, fundamental LabVIEW programming does not require them.
    Jarrod S.
    National Instruments

  • Verizon's "Network Optimization" on 3G Unlimited Plans

    I'm sure that this has probably been discussed here before, maybe numerous times since I don't frequent these boards, but since it is something that is now impacting me and since I've noticed others posting threads here and other forums about sporadically slow speeds with Verizon 3G during certain times of the day without any mention of this being the cause I thought I would share my experience with it first hand.
    I just found out about it yesterday when I called Verizon to complain about the performance I've been having off and on the last few weeks during peak times of the day (Download speeds in the 100-200Kbps range) for my 3G service and what I soon found out from the rep was that in December there was a "feature" added to my account called Network Optimization which basically is a means to throttle users who have 3G Unlimited plans and use the internet in areas which they deem as being congested. Any time you go over 2GB in a past billing cycle even though your on an Unlimited plan your up for it to be added to your account.
    And in a way I could understand them needing to crack down on really high users which I myself no doubt fall into on certain months since I have a Business Unlimited plan and I'm on the computer for hours every day using it with constantly refreshing websites, checking e-mails, and then downloading Windows and Mac updates and at times large files that I need. So it's nothing for me to hit 10-20GB in a month's time, especially around the holidays.
    But the biggest problem that I have with it is the fact they're free to add it to your account every time you go over 2GB in a month and reside in what they consider a congested area. Because someone that is on an Unlimited plan, and especially a Business Unlimited plan, should at least be given a cap of 10-12GB before they add on this "Network Optimization" feature to throttle your speeds because they are offering 10-12GB packages to Smartphone users without adding any Network Optimization to their accounts if they reside in a congested area and those types of users are in far greater number than those of us using laptop connect plans.
    But it all boils down to Verizon wanting to force the grandfathered Unlimited users into giving up their plans and signing new 2 year agreements on a more expensive tiered plan than it has anything to do with improving the network in congested areas. If they wanted to improve the network in congested areas they would be cracking down on the Smartphone users who are using mega amounts of data to constantly stream Youtube and Netflix all day but they don't. Or better yet how about spending money to upgrade the 3G towers that are congested instead of throttling your users and continually taking on more new users? Yeah like Verizon is actually going to do something like that right.
    Anyways I'm a little ****** off at Verizon at the moment since this is the only internet option I have available to me out here in my rural area and I have to have it for my home business so I can't just drop them yet as much as I would like to until they absolutely force me to.
    Is anyone else here facing these same troubles at the moment with your supposedly Unlimited plans and care to share your experience so far?
    If you want to read more about Verizon's Network Optimization feature and who they're targeting you can do so here:
    http://support.verizonwireless.com/information/data_disclosure.html

    Tidbits wrote:
    Twohothardware wrote:
    You missed the point of what I just said. I didn't imply that there isn't a clause there for them to be able to legally enforce bandwidth caps on the unlimited plans if they wanted to, what I said is that there is nothing fair about having a "Network Optimization" throttle added to your account each month you go past 2GB when there is no Network throttling being done to the largest percentage of users who are on Smartphones.
    If Verizon is capable of offering 10-12GB packages to Smartphone users with NO throttling then why are 3G Unlimited laptop connect users including those with Business accounts that require the most bandwidth being hit at only 2GB? Why isn't the excessive usage cap at something more "fair" like 10-12GB? And why are you even needing to throttle the laptop connect users who only make up a small percentage of your customer base in terms of bandwidth used compared to the iPhone and Nexus users?
    Huge difference in price paid.  Simply put the people who are paying more money are paying for their bandwidth.  Bandwidth isn't free for Verizon.  All carriers when they offered their unlimited plans they were overselling their network then realized they can't handle the capacity when devices started to get more sophisticated too quickly.
    For the people that come on here and say there is no difference in computer data and phone data...  YES there is a difference.  I have personally tested it out multiple times and on a laptop I can use 5times the amount of data in the same 1 hour period than I do on my cell phone going to the same sites.  The difference is background data, and the speed(jumping between sites, tabs, and bookmarks) you can surf the web is different between the two which people ALWAYS overlook.
    $60 vs $80 is not that huge of difference in price paid, what is a huge difference is 2GB and 10GB. And yes you can use far more data on a computer or laptop than a smartphone, even though laptop connect users only make up a fraction of Verizon's customer base compared to Smartphone users, but that is exactly why it is ridiculous that you try and cap Unlimited 3G desktop/laptop users at 2GB but then offer 10-12GB tiered plans to Smartphone users who aren't the ones that need it. And that is something that obviously you and Verizon are both overlooking.
    Let me ask you this, do you personally have a DSL or Cable connection at home outside of your Verizon 3G/4G service? What about at work?

  • Reg Query Optimization - doubts..

    Hi Experts,
    This is related to Blog by Mr Prakash Darji regarding "Query Optimization" posted on Jan 26 2006.In this to optimize query Generation of Report is suggested.
    I tried this, but I am not sure I am analyzing this correctly.
    I collected Stats data before and after Generation of Report.But how to be sure that this is helping me? Did any one has tried this?
    What to look for in Stats Data - duration?
    But duration would not be absolute parameter as there is factor of "Wait Time, User", so duration may depend on this.
    Please help me in this.
    Thanks
    Gaurav
    Message was edited by: Gaurav

    Any ideas Experts?

  • Full optimize Failed when scheduled

    Hi everyone,
    I got an issue with a full optimize package in SAP BPC 7.0 MS when scheduled.
    The package admin_Optimize i use is the standard one. They are no overlapping package scheduled at the same time.
    When i manually run the package for a Full optimize on one application it works.
    When i manually run the package for a Lite optimize on one application it works.
    When i schedule the package for a Lite optimize on one application it works.
    When i schedule the package for a Full optimize on one application the package failed and stay stuck. Then the application stay unavailable.
    This issue takes place in the production environment so i can't make a test during the day. and some people are using the application very early in the morning so they stay stuck in the morning.
    Have you ever meet this issue ? What can i do ? What could be the test ?
    Best regards,
    Paul

    When i start the full optimize by hand it's working fine (But we are supposed  to launch it at 4h15 in the morning so i would prefer to schedule it !)
    Are you receiving any error message or actually the statusof package show that was not completed and no erro mesage is provided?
    The package stay stuck, it never ends even after 4 hours. We are obliged to kill it.
    Did you check tbllogs durin the time when the package is running ? It can provide very usefull information.
    Yes we did, nothings appears in this table ... all the other package are correclty recorded even the LiteOptimize that is run 30 minutes after ... byt the way this Lite optimize doesn't failed.
    Also please check the event viewer from BPC servers during the period when the full optimize was running.
    No error  related to bpc. But i had an error 45 minutes before related to Osoft data manager

  • Zend optimizer and PHP startup: unable to load errors

    I am finding some errors in the log for my site about zend
    optimizer and PHP startup: unable to load dynamic library.
    as far as I know, I have never used PHP and i have never done
    anything with this zend optimizer. i need some help!
    there are some references in there to some pretty strange
    websites. my site is a wedding photography site!
    thanks for any help.
    here is the log:
    [Fri Jun 06 13:33:44 2008] [error] [client 82.18.149.126] PHP
    Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0, referer:
    http://www.justiceandcompassion.com/
    [Fri Jun 06 13:33:44 2008] [error] [client 82.18.149.126] PHP
    Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0, referer:
    http://www.justiceandcompassion.com/
    [Fri Jun 06 13:33:45 2008] [error] [client 75.8.116.97]
    Failed loading /home/vanity1/ioncube/ioncube_loader_lin_5.2.so:
    /home/vanity1/ioncube/ioncube_loader_lin_5.2.so: cannot open shared
    object file: No such file or directory, referer:
    http://vanitytransformations.com/diamondt/index.php?option=com_fireboard&Itemid=57&func=sh owcat&catid=2&page=2
    [Fri Jun 06 13:33:50 2008] [error] [client 80.82.139.143] PHP
    Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0
    [Fri Jun 06 13:33:50 2008] [error] [client 80.82.139.143] PHP
    Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0
    [Fri Jun 06 13:33:53 2008] [error] [client 62.50.73.8]
    Request exceeded the limit of 10 internal redirects due to probable
    configuration error. Use 'LimitInternalRecursion' to increase the
    limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Jun 06 13:33:53 2008] [error] [client 62.50.73.8]
    Request exceeded the limit of 10 internal redirects due to probable
    configuration error. Use 'LimitInternalRecursion' to increase the
    limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Fri Jun 06 13:33:59 2008] [error] [client 200.30.148.234]
    Failed loading /home/estudio5/ioncube/ioncube_loader_lin.so:
    /home/estudio5/ioncube/ioncube_loader_lin.so: cannot open shared
    object file: No such file or directory
    [Fri Jun 06 13:33:59 2008] [error] [client 200.30.148.234]
    Failed loading /home/estudio5/ioncube/ioncube_loader_lin_ts.so:
    /home/estudio5/ioncube/ioncube_loader_lin_ts.so: cannot open shared
    object file: No such file or directory
    [Fri Jun 06 13:34:09 2008] [error] [client 82.18.149.126] PHP
    Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0, referer:
    http://www.otmatheist.com/
    [Fri Jun 06 13:34:09 2008] [error] [client 82.18.149.126] PHP
    Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0, referer:
    http://www.otmatheist.com/
    [Fri Jun 06 13:34:14 2008] [error] [client 82.18.149.126] PHP
    Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0, referer:
    http://www.otmatheist.com/2008/06/05/i-dont-want-my-kids-to-be-atheists/
    [Fri Jun 06 13:34:14 2008] [error] [client 82.18.149.126] PHP
    Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0, referer:
    http://www.otmatheist.com/2008/06/05/i-dont-want-my-kids-to-be-atheists/
    [Fri Jun 06 13:34:21 2008] [error] [client 75.8.116.97]
    Failed loading /home/vanity1/ioncube/ioncube_loader_lin_5.2.so:
    /home/vanity1/ioncube/ioncube_loader_lin_5.2.so: cannot open shared
    object file: No such file or directory, referer:
    http://vanitytransformations.com/diamondt/index.php?option=com_events&Itemid=37
    [Fri Jun 06 13:34:21 2008] [error] [client 75.8.116.97]
    Failed loading /home/vanity1/ioncube/ioncube_loader_lin_5.2.so:
    /home/vanity1/ioncube/ioncube_loader_lin_5.2.so: cannot open shared
    object file: No such file or directory, referer:
    http://vanitytransformations.com/diamondt/index.php?option=com_events&Itemid=37
    [Fri Jun 06 13:34:25 2008] [error] [client 38.100.8.10] PHP
    Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0, referer:
    http://www.google.com/search?sourceid=navclient&ie=UTF-8&rlz=1T4DMUS_enUS204US205&q=gideon +bible+ebay
    [Fri Jun 06 13:34:25 2008] [error] [client 38.100.8.10] PHP
    Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0, referer:
    http://www.google.com/search?sourceid=navclient&ie=UTF-8&rlz=1T4DMUS_enUS204US205&q=gideon +bible+ebay
    [Fri Jun 06 13:34:26 2008] [error] [client 70.241.173.162]
    PHP Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0
    [Fri Jun 06 13:34:26 2008] [error] [client 70.241.173.162]
    PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected
    at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0
    [Fri Jun 06 13:34:31 2008] [error] [client 70.241.173.162]
    PHP Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0, referer:
    http://doableevangelism.com/2008/04/16/dali-desi-and-doug-in-seattle/
    [Fri Jun 06 13:34:31 2008] [error] [client 70.241.173.162]
    PHP Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected
    at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0, referer:
    http://doableevangelism.com/2008/04/16/dali-desi-and-doug-in-seattle/
    [Fri Jun 06 13:34:32 2008] [error] [client 65.214.44.28] PHP
    Warning: PHP Startup: Unable to load dynamic library
    '//home/offthema/sourceguardian/ixed.lin' -
    //home/offthema/sourceguardian/ixed.lin: cannot open shared object
    file: Permission denied in Unknown on line 0
    [Fri Jun 06 13:34:32 2008] [error] [client 65.214.44.28] PHP
    Warning: Zend Optimizer for PHP 5.2.x cannot be found (expected at
    '/usr/local/Zend/lib/Optimizer-3.2.2/php-5.2.x/ZendOptimizer.so') -
    try reinstalling the Zend Optimizer in Unknown on line 0

    ..... What???

  • Optimizer not giving PR's in time even below the safetystock level

    Hi
    Optimizer not giving PR's in time even below the safety stock
    I maintianed safety stock penalty and supplier lead time also but still am missing something and i am unable to find the problem why
    PR not creating.the product is external procurement .is their any inforecord problem (or) because of cost it is not creating PR's
    please give me some inputs it wil help for me
    Regards
    jungili

    Hi Senthil/nitin
    thankyou for response
    actually the product is raw material so i checked the finished product whether the demand is there or not but there is no suficient demand but safety stock is there for finished product.it can give supply upto 4 months .
    so at the time of completing the finished product safety stock, then optimizer giving PR for raw material from that day onwards
    because here we maintained safety stock penalty is more,for this reason optimizer giving results as per ........this is am thinking
    correct me if am wrong
    regards
    jungili

  • How to figure out which tables are using Extensible Optimizer?

    Hi guys,
    I'm sure that there're several tables those are associated with Extensible Optimizer in my database, I can also find the Extensible Optimizer relevant type and the implementation of interface functions ODCIGetInterfaces, ODCIStatsTableFunction.
    I'm curious to know is there a way to figure out which tables are associated with this Extensible Optimizer, does anyone have any clues?
    Database: oracle 11.2
    Thank you in advance.

    Hi,
    Can you please check the below link.It may help you:
    http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28425/ext_optimizer.htm
    Best regards,
    Rafi.
    http://rafioracledba.blogspot.com

  • Perform implementation step failed in Maint optimizer!!!

    Hi,
    I  have performed upto step 3 in maint optimizer , which is the files got downloaded successfully.Now, when i click on Step 4 "Perform implementation"
    which should go apply the downloaded patches,this step failed with warning
    "The product maint is not completed in all systems of the procedure".
    But i have only one system defined in this solution.
    Did i miss anything in the configuration?
    Thanks,
    Ram

    Hello Ram,
    Please get for service.sap.com/instguides--NW2007->Maintenance the guide
    Support Package Stack Guide - SPS12
    In this guide you will see the different tools to use for the different patches that you want to install.
    This Maintenance Optimizer tool is for the moment only for being able to get the patches for NW2004s products released after 2nd April 2007, for the moment this scenario in not adding any extra functionallity only documentation funtion in solman system, this is correct.
    Best regards,
    Dolores

  • Enable to optimize my files

    Cannot optimize my file.
    Neither those ways :
    FIRST TEST
    In my FCPX prefs transcoding OFF
    In import window transcoding OFF
    Transcoding the event to 422
    SECOND TEST
    In my FCPX prefs transcoding ON
    In import window transcoding OFF
    THIRD TEST
    In my FCPX prefs transcoding OFF
    In import window transcoding ON
    Was working fine, but not now.
    Do you think that I have to reinstall FCPX
    And if what about all my third party plugins.
    Thanks
    Michel

    Exactlly what media are you trying to optimize. (Transcode is a post import function.)
    FIRST TEST
    Nothing should optimize in these settings
    SECOND TEST
    Nothing should optimize in these settings either. The import setting will override the preference.
    THIRD TEST
    This should optimize if the media is suitable.

  • Any way to identify causes of Optimization failures ???

    Hi guys
    We have recently been seeing regular optimization failures (06:45 every morning - Lite optimization).
    Unfortunately, the BPC logs only tell me that the job has failed, with no reason as to why it has failed.
    This job runs every 2 hours on our system and the 06:45 job is the only one that fails with any regularity.
    Is there any way that I can track what has actually gone on with the job, or am I stuck with only the job logs and EventViewer for information?
    BTW - This is BPC 5.1 SP5
    Thanks
    Craig

    There are definitely no scheduled jobs that clash with this one.
    How do I check the "Master data"? (And indeed, what is the master data?)
    I am not aware of any other jobs that run overnight on the server, other than this lite optimization every 2 hours and a full optimize.
    The results (every day) are as follows:
    00:45 - Lite Optimize - Success
    02:45 - Lite Optimize - Success
    03:30 - Full Optimize (no compression) - Success
    04:45 - Lite Optimize - Success
    06:45 - Lite Optimize - Failure
    08:45 - Lite Optimize - Success
    10:45 - Lite Optimize - Success
    ..... and so on throughout the day
    The job succeeds almost every time it is run (with the odd exception of a dimension update which can clash with the 08:45 job if we are changing it at the time).
    The only thing that changes before the 06:45 lite optimize is that the dependencies are dropped and recreated on each of the Fact tables:
    INS1..., INS2..., INS3..., INS11..., INS21..., INS31..., DMU... for each Application
    This is done because of a known issue in v5.1 which drops the dependencies of each application after a full optimize.
    As for running the job again 30 minutes later - That works perfectly as well.
    I just really need to know whether I have any way of finding out what other job(s) is/are running at the same time that could block the optimization, or whether the rebuilding of the dependencies could cause the issue (although that has been done for months on end without issue until now).

  • Sharepoint 2013 search component best practice

    hi
    With a big SharePoint 2013 farm:
    2 WFE
    2 App server
    2 Search App server (havent set up these servers yet)
    What would the best way to divide the search componment between the two serarch app servers?
    Crawl component
    Crawls content sources to collect crawled properties and metadata from crawled items and sends this information to the content processing component.
    Content processing component
    Transforms the crawled items and sends them to the index component. This component also maps crawled properties to managed properties.
    Analytics processing component
    Carries out search analytics and usage analytics.
    Index component
    Receives the processed items from the content processing component and writes them to the search index. This component also handles incoming queries, retrieves information from the search index and sends back the
    result set to the query processing component.
    Query processing component
    Analyzes incoming queries. This helps optimize precision, recall and relevance. The queries are sent to the index component, which returns a set of search results for the query.
    Search administration component
    Runs the system processes for search, and adds and initializes new instances of search components.
    If you ignore the need for redunancy (we may add another 2 search app servers for that later).
    brgs
    Bjorn

    Hi Bjorn,
    According to your description, my understanding is that you want to deploy the search components in two search app servers.
    It depends on how many search service applications you need and the size of your environment.
    Here is a link about how to configure topology for one search service application with multiple search components across 2 servers for redundancy and performance:
    http://blogs.msdn.com/b/chandru/archive/2013/02/19/sharepoint-2013-configuring-search-service-application-and-topology-using-powershell.aspx
    You can also run the Query Processing component in web front server and run the other components in the search servers or application servers.
    Please refer to the link below:
    http://blogs.technet.com/b/meamcs/archive/2013/04/09/configuring-sharepoint-2013-search-topology.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+yahoo%2FZfiM+(Team+blog+of+MCS+%40+Middle+East+and+Africa)
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Suggestions to improve the INSERT performance

    Hi All,
    I have a table which has 170 columns .
    I am inserting huge data 50K and more records into this table.
    my insert would be look like this.
    INSERT INTO /*+ append */ REPORT_DATA(COL1,COL2,COL3,COL4,COL5,COL6)
    SELECT  DATA1,DATA2,DATA3,DATA4,DATA5,DATA5 FROM TXN_DETAILS
    WHERE COL1='CA';
    Here i want to insert values for only few columns.Hence i specifies only those column names in insert statement.
    But when huge data(50k+) returned by select query then this statement taking   very long time to execute(approximately 10 to 15 mins).
    Please  suggest me to improve this insert statement performance.I am also using 'append' hint.
    Thanks in advance.

    a - Disable/drop indexes and constraints - It's far faster to rebuild indexes after the data load, all at-once. Also indexes will rebuild cleaner, and with less I/O if they reside in a tablespace with a large block size.
    b - Manage segment header contention for parallel inserts - Make sure to define multiple freelist (or freelist groups) to remove contention for the table header. Multiple freelists add additional segment header blocks, removing the bottleneck.  You can also use Automatic Segment Space Managementhttp://www.dba-oracle.com/art_dbazine_ts_mgt.htm (bitmap freelists) to support parallel DML, but ASSM has some limitations
    c - Parallelize the load - You can invoke parallel DML (i.e. using the PARALLEL and APPEND hint) to have multiple inserts into the same table. For this INSERT optimization, make sure to define multiple freelists and use the SQL "APPEND" option. If you submit parallel jobs to insert against the table at the same time, using the APPEND hint may cause serialization, removing the benefit of parallel jobstreams.
    d - APPEND into tables - By using the APPEND hint, you ensure that Oracle always grabs "fresh" data blocks by raising the high-water-mark for the table. If you are doing parallel insert DML, the Append mode is the default and you don't need to specify an APPEND hint. Also, if you're going w/ APPEND, consider putting the table into NOLOGGING mode, which will allow Oracle to avoid almost all redo logging."
    insert /*+ append */ into customer values ('hello',';there');
    e - Use a large blocksize - By defining large (i.e. 32k) blocksizes for the target table, you reduce I/O because more rows fit onto a block before a "block full" condition (as set by PCTFREE) unlinks the block from the freelist.
    f - Use  NOLOGGING
    f - RAM disk - You can use high-speed solid state disk (RAM-SAN) to make Oracle inserts run up to 300x faster than platter disk.

  • Field Catalogs in ALV

    Hi Friends,
    Please help me out, I am new to ABAP.
    Please anybody explain me the functionality of Field catalogs in ALVs?
    How many methods are there to pass data to ALVs, i.e., in how many ways?
    Hope u will help me.

    hi,
    this will be very helpful for ALV REPORTING.....
    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.  In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain upto 90 columns in the display with the wide array of display options.
    The commonly used ALV functions used for this purpose are;
    1.     REUSE_ALV_VARIANT_DEFAULT_GET
    2.     REUSE_ALV_VARIANT_F4
    3.     REUSE_ALV_VARIANT_EXISTENCE
    4.     REUSE_ALV_EVENTS_GET
    5.     REUSE_ALV_COMMENTARY_WRITE
    6.   REUSE_ALV_FIELDCATALOG_MERGE
    7.   REUSE_ALV_LIST_DISPLAY
    8.     REUSE_ALV_GRID_DISPLAY
    9.     REUSE_ALV_POPUP_TO_SELECT
    The different steps used for getting the above function modules into use are:
    Step 1
    DATA DECLARATION
    Sap standard type pools:  SLIS , KKBLO .
    Sap standard tables types taken from the type pools are:  SLIS_LAYOUT_ALV ,
                                             SLIS_T_FIELDCAT_ALV,
    SLIS_T_LISTHEADER,
    SLIS_T_EVENT,
    SLIS_SELFIELD.
    Internal tables to used in the program declared based on the above table types
    DATA:  I_LAYOUT TYPE SLIS_LAYOUT_ALV,
                I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
               I_HEADING TYPE SLIS_T_LISTHEADER,
    I_EVENTS TYPE SLIS_T_EVENT.
    TYPES:  KKBLO_SELFIELD TYPE SLIS_SELFIELD.
    Step 2 (Optional)
    SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)
    The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.
    The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.
    Sample code:
    CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
           EXPORTING
                i_save     = variant save condition ( A=all, U = user-specific )
           CHANGING
                cs_variant = internal table containing the program name (and the default variant---optional )
           EXCEPTIONS
                not_found  = 2.
    The user can also choose from the list of existing variants using the function module ‘REUSE_ALV_VARIANT_F4’.
    Step 3
    DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG
    A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields).
    A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.
    The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.
    The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.
    A field catalog need not be built-up and passed explicitly only under the following conditions:
    1.     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.
    2.     all fields in this structure are to be output
    3.     The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.
    All the values entered in the catalog is specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.
    The different possible attributes are:
    •     Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.
                         Value set: 0, 1 – 3
    •     Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display.       The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.
    Value set: 0, 1 – 60
    •     Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.
    Value set: internal output table field name (required parameter)
    •     Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.
                         Value set: SPACE, internal output table name.
    •     Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the        Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
        Value set: SPACE, Data Dictionary field name.
    •     Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field.        This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
    Value set: SPACE, name of a Data Dictionary structure or table
    Link to currency unit
    •     Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
    Value set: SPACE, output table field name
    •     Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
    Value set: SPACE, output table field name.
            Link to measurement unit
    •     Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
    Value set: SPACE, output table field name.
    •     Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
    Value set: SPACE, output table field name.
    •     Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
    Initial = column width is the output length of the referred Data Dictionary field (domain).
    N = column width is n characters.
          Value set: 0 (initial), n.
    •     Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.
    If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.
    'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
          Value set: SPACE, 'X'.
    •     Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.
    The key column sequence cannot be changed interactively by the user. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
    Value set: SPACE, 'X'.
    •     No_out (field in field list): This parameter is used to remove certain fields from the output during initial display.  The user can however interactively choose the field for output from the field list in the display variant.
                'X' = field is not displayed in the current list.
            Value set: SPACE, 'X'.
    •     Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.
                        'X' = technical field.
           Value set: SPACE, 'X'.
    •     Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.
    Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).
    'X' = column is colored with the default column highlight color.
                        'Cxyz' = column is colored with a coded color:
                      -  C: Color (coding must begin with C)
                     -  X: color number
                      -  Y: bold
                       -  Z: inverse
    •     Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.
             Value set: SPACE, 'X'.
                        'X' = column cells are output as hotspots.
    •     Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.
                         Value set: SPACE, 'X'.
            'X' = column fixed (does not scroll horizontally).
    •     Do_sum (sum over column): the user can also call this function interactively.
                      Value set: SPACE, 'X'.
    'X' = a sum is calculated over this internal output table field.
    •     No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.
             Value set: SPACE, 'X'.
    •     Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.
                        Value set: SPACE, 'X'.
                         'X' = column contents to be output as an icon.
    •     Symbol: The internal output table column must be a valid symbol character.
    Value set: SPACE, 'X'
                        'X' = column contents are to be output as a symbol.
    •     Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.
    Value set: SPACE, 'R', 'L', and ‘C’.
           ' ' = Default justification for this data type
           'R' = right-justified output
           'L' = left-justified output
           'C' = centered output.
    •     Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.
                       Value set: SPACE, 'X'.
                        'X' = output with leading zeros.
    •     No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.
        Value set: SPACE, 'X'.
               'X' = value output without +/ sign.
    •     No_zero (suppress zeros): Only relevant for value fields.
                 Value set: SPACE, 'X'.
                        'X' = suppress zeros.
    •     Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.
               Value set: SPACE, template.
    The following parameters are used for customizing the texts in the heading of the output of the columns. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored.
    If the user changes the column width interactively, the column header text with the appropriate length is always used.
    The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
         The 'long field label' is also used in display variant definition,
            Sort, etc.  Popup.
    •     seltext_l (long field label)
    •     seltext_m (medium field label)
    •     seltext_s (short field label)
    •     reptext_ddic(header) Analogous to the Data element main header
    •     Ddictxt (specify text) : You can specify with values 'L', 'M',  and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
    Value set: SPACE, 'L', 'M', and ‘S’.
    Sample code:
    Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).
    DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV.     “Local variable to hold the parameters                                                                               
    for a particular field of the field catalog
      CLEAR L_FIELDCAT.
      L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
      L_FIELDCAT-FIELDNAME = 'EBELN'.
      L_FIELDCAT-KEY = 'X'.         “The PO no is made the key field,
                          “Colored and non scrollable
      L_FIELDCAT-HOTSPOT = 'X'.     “The po no becomes a hotspot
      L_FIELDCAT-SELTEXT_S = ‘P.O No’.
      L_FIELDCAT-SELTEXT_M = 'P order No'.
      L_FIELDCAT-SELTEXT_L = 'Purchase order No'.
      APPEND L_FIELDCAT TO I_FIELDTAB.
      CLEAR L_FIELDCAT
      L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
      L_FIELDCAT-FIELDNAME = 'EBELN'.
      L_FIELDCAT-KEY = 'X'.         “The po item no is made the key field,
                               “Colored and non scrollable
      L_FIELDCAT-SELTEXT_S = 'Item No'.
      L_FIELDCAT-SELTEXT_M = 'Item No`.
      L_FIELDCAT-SELTEXT_L = 'PO Item No'.
      APPEND L_FIELDCAT TO I_FIELDTAB.
      CLEAR L_FIELDCAT
    Thus the catalog for the report output is prepared.
    Step 4
    The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.
    A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.
    The function module contains following import and export parameters.
    IMPORTING PARAMETERS: I_LIST_TYPE
    This parameter has possible values from 0-4.
    The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0 .
    EXPORTING PARAMETERS:  I_EVENTS table.
    This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.
    The table structure contains the fields:
         I_EVENTS-NAME: Name of the Callback event.
    I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.
    Only events with a form routine name are processed.
    The I_EVENTS table returns with the following possible constants:
    1.     Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.     
    Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.
    2.     Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
    RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to       be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.
    RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that    entries are not repeated in the item table.
        RS_SELFIELD is initial in this case.         
    3.     Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
    Is called at the beginning of the function module to make special settings. It is not usually used.          
    4.     Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
    As this is a frequently-used Callback event, the form routine can also be passed        directly in the interface by passing the user command in the IMPORTING parameter           I_CALLBACK_USER_COMMAND.
    5.     Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
       Equivalent to the list processing TOP-OF-PAGE event.           
    6.     Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.       
    The selection information and list status are output together (if they exist) on a separate page by default
    7.     Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.       
    Analogously to TOP_OF_COVERPAGE the user can add other information
    to the information output by ALV (selection information, list status) at this event.
    8.     Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.
    The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
    In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
    9.     Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.  
    The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
    In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.                             
    10.     Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
    If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
    The STANDARD status of the function group SALV should be used as a          template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
    11.     Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.     
    LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
                                             R_INDEX LIKE SY-TABIX
                                             R_INDEX_ITEM LIKE SY-TABIX
                                             R_INDEX_SUM LIKE SY-TABIX.
    12.     Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.  
    Information output at the start of the list     
    13.     Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
    Information output at the end of a page. This is only called for printing.
    14.     Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.     
    Information output at the end of the list
    15.     Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
    Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
    16.     Slis_ev_before_line_output TYPE slis_formname VALUE   'BEFORE_LINE_OUTPUT'.       
    Output information before each output line. Should only be used in justified cases because it costs a lot of performance.         
    17.     Slis_ev_subtotal_text TYPE slis_formname VALUE  'SUBTOTAL_TEXT'.                        
    This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.
    Sample code :
    FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
    FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.
    DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
           EXPORTING
               I_LIST_TYPE = 0
           IMPORTING
                ET_EVENTS   = I_EVENTS.
      READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                               INTO L_I_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.
        APPEND L_I_EVENT TO I_EVENTS.
      ENDIF.
      READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
                               INTO L_I_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.
        APPEND L_I_EVENT TO I_EVENTS.
      ENDIF.
      CLEAR L_I_EVENT.
      READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND
                               INTO L_I_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.
        APPEND L_I_EVENT TO I_EVENTS.
      ENDIF.
    This will prepare the events table for the report.
    The report will contain three forms for the above events:
    1.     FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc
    Using the function module ‘REUSE_ALV_COMMENTARY_WRITE’, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.
    2.     FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc
    3.     FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection
    Step 5
    A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).
    Output list description structure.
         The parameters are described under the following heads:
    •     Display options
    •     Exceptions
    •     Totals
    •     Interaction
    •     Detail screen
    •     Display variants (only for hierarchical-sequential lists)
    •     Color
    •     Other
    The layout table is of type slis_layout_alv_spec and has the following fields:
    Display options                                                
    1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.
    Value set: SPACE, 'X'
    'X' = optimizes the column width so that all contents are displayed completely.                   
    2. No_colhead(1) TYPE c : This parameter suppresses the column headings                    
    Value set: SPACE, 'X'.
    'X' = column headers are not output
    3. No_hotspot(1) TYPE c :  The heading of the report output are not output as hotspot.       
    Value set: SPACE, 'X'.
    'X' = column headers are not output as hotspot
    4. Zebra(1) TYPE c : The report is output in the striped pattern.             
    Value set: SPACE, 'X'.
    'X' = striped pattern (e.g. for wide lists)
    5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines.  It is not relevant for: hierarchical-sequential lists and multiple-line lists.
    Value set: SPACE, 'X'.
    'X' = columns separated by SPACE
    6. No_min_linesize(1) TYPE c : The report  line size is equal to the width of the list. It is not relevant for block lists.
    Value set: SPACE, 'X’.
    'X' = line size depends on list width
    '  ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .
    7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.
    Value set: 0, 10 - 250
    If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).
    8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.
    Value set: 0, 80 - 1020
    9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.                            
               10. No_uline_hs(1) TYPE c.
    Exceptions                                                 
    11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.
                      Output table field code:  '1' = red traffic light
                                    '2' = yellow traffic light
                                         '3' = green traffic light Fieldname for exception 
         Value set: SPACE, internal output table field name.
    12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.
    .     Value set: SPACE, internal output table name.
    13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.
    Value set: SPACE, data element name.
               14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each
               Subtotal that includes this record is also output with 'red traffic light'.
               Value set: SPACE, 'X'
               'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.
    Sums                                                       
    15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up
    Only by fieldcatalog.
    Value set: SPACE, 'X'
    'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.
    16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.
    Value set: SPACE, 'X'
    'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.
    17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.
    Value set: SPACE, 'X'
    'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.
    18. No_subtotals(1) TYPE c : No subtotals possible          
    Value set: SPACE, 'X'
    'X' = no subtotals.
    19. Numc_sum(1)  TYPE c : Totals only possible for NUMC-Fields.
    20. No_unit_splitting TYPE c: No separate total lines by inh.units   
    21.totals_before_items TYPE c: Display totals before the items   
    22. Totals_only(1) TYPE c :  Show only totals      
    Value set: SPACE, 'X'
    'X' = only total records are output.
    23. Totals_text(60) TYPE c : Text for 1st col. in totals   
    Value set: SPACE, string (max.60)
    ' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.
    'String’ = The string passed is output after the total indicated by '*', if the column is wide enough.
    24. Subtotals_text(60) TYPE c : Texts for subtotals
    Value set: SPACE, string (max.60)
    ' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.
    'String’ = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.
    Interaction                                                      
    25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.
    Value set: SPACE, internal output table field name
    26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.
    Value set: SPACE, internal output table name.
    27. Box_rollname LIKE dd03p-rollname: rollname for checkbox          
    28. Expand_fieldname TYPE slis_fieldname: fieldname flag ‘expand’. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event        'ITEM_DATA_EXPAND'.
    29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.
    30. No_input(1) TYPE c : The fields are only display fields.
            Value set: SPACE, 'X'
    'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')
    31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.
                      => LAYOUT-F2CODE = '&ETA'.
    Value set: SPACE, function code
    32. Confirmation_prompt: confirm. Prompt when leaving       
    Value set: SPACE, 'X'
    'X' = if one of the functions ‘Back (F03)', ‘Exit (F15)' or ‘Cancel (F12)' occurs, a confirmation prompt appears.
    33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.
    Value set: SPACE, 'X'.
    34. Reprep(1) TYPE c :  report report interface active.     
    35. Group_buttons(1) TYPE c :  group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.           
    Value set: SPACE, 'X'.
    36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.
    Value set: SPACE, 'X'.
    ' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.
    'X' = key columns not fixed
    37. Get_selinfos(1) TYPE c : To read selection screen.
    Value set: SPACE, 'X'.
    If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.
    38.     group_change_edit(1) TYPE c :  Settings by user for new group     
    Value set: SPACE, 'X'
    'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).
    39.     No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.
    Value set: SPACE, 'X'.
    40. Expand_all(1) TYPE c : Expand all positions                   
    Detailed screen                                                    
    40.     Detail_popup(1) TYPE c : show detail in popup.
    Value set: SPACE, 'X'
    '  '  = List record detail display in full-screen mode, with top-of-page.
    'X'  = list record detail display in popup (without top-of-page).
    41. Detail_initial_lines(1) TYPE c : show also initial lines   
    Value set: SPACE, 'X'
    '  ' = Only fields whose contents are not initial are output in the detail view.
    'X' = initial field contents are also output in detail.
    41.     detail_titlebar(30) type c : Titlebar for detail screen
    Value set: SPACE, string (max.30)
    ` ' = ' Detail: Display' is output as the title of the detail window.
                  'String’ = the string passed is output as the title of the detail window. 
    Display variants                                                   
    42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.   
    Value set: SPACE, CHAR (20)
    ' ' = The header table field pushbutton text is 'Header' by default.
    CHAR (20) = header table field pushbutton text.
    43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.        
    Value set: SPACE, CHAR (20)
    ' ' = The pushbutton text for the item table fields is 'Item' by default.
    CHAR (20) = item table field pushbutton text.
    44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.
         Value set: SPACE, 'X'
    ' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.
    'X' = the item table fields are displayed by default in the display variant Definition Popup.    The user can switch to the header table fields interactively.
    Colour                                                       
    45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.
    Value set: SPACE, internal output table field name
    The internal output table field must be of type CHAR(3).
    The code must have the following syntax:  'Cxy':
            C = color (all codes must start with 'C')
            X = color number ('1'-'9')
            Y = bold ('0' = off, '1' = on)
    46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.       
    Others                                                
    47. List_append(1) TYPE c :  no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.
    Example code :
           I_LAYOUT-f2code       = ws_fcode.
           I_LAYOUT-zebra        = 'X'.
    I_LAYOUT-colwidth_optimize = 'X'.
    I_LAYOUT-no_keyfix = 'X'.
    I_LAYOUT-get_selinfos = 'X'.
    I_LAYOUT-no_hotspot = 'X'.
           I_LAYOUT-no_input = 'X'.
    I_LAYOUT-hotspot_fieldname = FIELDNAME.
    I_LAYOUT-no_input          = ‘X’.
    I_LAYOUT-no_vline          = `X’.
    I_LAYOUT-no_colhead        = ‘ ‘.
    I_LAYOUT-lights_condense   = ` `.
    I_LAYOUT-totals_text       = ` `.
    I_LAYOUT-subtotals_text    = ` `.
    I_LAYOUT-totals_only       = ` `.
    I_LAYOUT-key_hotspot       = ‘X’.
    I_LAYOUT-detail_popup      = ‘X’.
    I_LAYOUT-group_change_edit = ‘X’.
    I_LAYOUT-GROUP_BUTTONS     = ‘X’.
    Step 6
    This step is required to get the selection screen information in the report output.
    The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.
    The parameters to be passed in the IS_SEL_HIDE table are:
    o mode:              'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES       
    Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.
    'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.
    o t_entries:         Selection info table
    o t_entries-mode:   'A' = output the selection info for the current table record in the info popup.
    'D' = do not output select option or SELNAME parameter selection info in   the popup.
    o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.
    The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.
    •     t_entries-field:  DDIC field name of the field for which selection information is to be output.
    •     t_entries-table:  DDIC table names of t_entries-field.
    •     t_entries-stext:  Field name in info popup.
    •     If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.
    •     t_entries-valuf:  Selection condition 'from' value (external format)
    •     t_entries-valut:  Selection condition 'to' value (external format)
    •     t_entries-sign0:  (I)nclusive (E)xclusive
    •     t_entries-option:  All values of the select options Option field allowed.
    Step 6
    The Table IT_SORT is populated with the sort criteria for the different fields.
    The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.
    This internal table has the following fields:
         o spos :  Sort sequence
         o fieldname :  Internal output table field name
         o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.
         o up : 'X' = sort in ascending order
         o down : 'X' = sort in descending order
         o subtot : 'X' = subtotal at group value change
         o group : '* ' = new page at group value change ,'UL' = underline at group value change
                             Step 7
    The final step in the output of the report is the use of two ALV functions modules.
    1.     REUSE_ALV_FIELDCATALOG_MERGE
    2.     REUSE_ALV_LIST_DISPLAY
    The first function module is used to pass the field catalog to the report output and merge it with the internal output table.
    FUNCTION reuse_alv_fieldcatalog_merge.                                
    ""Lokale Schnittstelle:                                             
    *” IMPORTING                                                    
    *"             VALUE(I_PROGRAM_NAME) LIKE  SY-REPID OPTIONAL          
    *"             VALUE(I_INTERNAL_TABNAME) TYPE  SLIS_TABNAME OPTIONAL  
    *"             VALUE(I_STRUCTURE_NAME) LIKE  DD02L-TABNAME OPTIONAL   
    *"             VALUE(I_CLIENT_NEVER_DISPLAY) TYPE  SLIS_CHAR_1        
    *"                             DEFAULT 'X'                            
    *"             VALUE(I_INCLNAME) LIKE  TRDIR-NAME OPTIONAL            
    *"       CHANGING                                                     
    *"             VALUE(CT_FIELDCAT) TYPE  SLIS_T_FIELDCAT_ALV           
    *"       EXCEPTIONS                                                   
    *"              INCONSISTENT_INTERFACE                                
    *"              PROGRAM_ERROR                                         
    Import parameters 
    I_PROGRAM_NAME: Program in which the internal output table is declared and populated   
    I_INTERNAL_TABNAME: Internal output table name
    I_STRUCTURE_NAME: Structure name (structure, table, and view)
    I_CLIENT_NEVER_DISPL: Hide client fields default ‘X’
    I_INCLNAME: Data declarations include name
    CHANGING parameter
    CT_FIELDCAT: Field catalog with field descriptions
    The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:                                                                               
    1.   Performance is affected since the code of the table definition must always be read and interpreted at runtime.                                                                               
    2.   Dictionary reference are only considered if the keywords LIKE or  INCLUDE STRUCTURE (not TYPE) are used.
    Step 8
    The other function module is used to display the internal output table with the contents
    FUNCTION reuse_alv_list_display.                                          
    ""Lokale Schnittstelle:                                                 
    *” IMPORTING                                                        
    *"             VALUE(I_INTERFACE_CHECK) DEFAULT SPACE                     
    *"             VALUE(I_CALLBACK_PROGRAM) LIKE  SY-REPID DEFAULT SPACE     
    *"             VALUE(I_CALLBACK_PF_STATUS_SET) TYPE  SLIS_FORMNAME        
    *"                             DEFAULT SPACE                              
    *"             VALUE(I_CALLBACK_USER_COMMAND) TYPE  SLIS_FORMNAME         
    *"                             DEFAULT SPACE                              
    *"             VALUE(I_STRUCTURE_NAME) LIKE  DD02L-TABNAME OPTIONAL       
    *"             VALUE(IS_LAYOUT) TYPE  SLIS_LAYOUT_ALV OPTIONAL            
    *"             VALUE(IT_FIELDCAT) TYPE  SLIS_T_FIELDCAT_ALV OPTIONAL      
    *"             VALUE(IT_EXCLUDING) TYPE  SLIS_T_EXTAB OPTIONAL            
    *"             VALUE(IT_SPECIAL_GROUPS) TYPE  SLIS_T_SP_GROUP_ALV         
    *"                             OPTIONAL                                   
    *"             VALUE(IT_SORT) TYPE  SLIS_T_SORTINFO_ALV OPTIONAL          
    *"             VALUE(IT_FILTER) TYPE  SLIS_T_FILTER_ALV OPTIONAL          
    *"             VALUE(IS_SEL_HIDE) TYPE  SLIS_SEL_HIDE_ALV OPTIONAL        
    *"           VALUE(I_DEFAULT) DEFAULT 'X'
    "             VALUE(I_SAVE) DEFAULT SPACE                             
    "             VALUE(IS_VARIANT) LIKE  DISVARIANT                      
    "                             STRUCTURE  DISVARIANT DEFAULT SPACE     
    "             VALUE(IT_EVENTS) TYPE  SLIS_T_EVENT OPTIONAL            
    "             VALUE(IT_EVENT_EXIT) TYPE  SLIS_T_EVENT_EXIT OPTIONAL   
    "             VALUE(IS_PRINT) TYPE  SLIS_PRINT_ALV OPTIONAL           
    "             VALUE(IS_REPREP_ID) TYPE  SLIS_REPREP_ID OPTIONAL       
    "             VALUE(I_SCREEN_START_COLUMN) DEFAULT 0                  
    "             VALUE(I_SCREEN_START_LINE) DEFAULT 0                    
    "             VALUE(I_SCREEN_END_COLUMN) DEFAULT 0                    
    "             VALUE(I_SCREEN_END_LINE) DEFAULT 0                      
    "       EXPORTING                                                     
    "             VALUE(E_EXIT_CAUSED_BY_CALLER)                          
    "             VALUE(ES_EXIT_CAUSED_BY_USER) TYPE  SLIS_EXIT_BY_USER   
    "       TABLES                                                        
    "              T_OUTTAB                                               
    "       EXCEPTIONS                                                    
    "              PROGRAM_ERROR
    Import parameters
    I_INTERFACE_CHECK: Interface consistency check log output.
    I_CALLBACK_PROGRAM: Name of the calling program
    I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.   
    I_CALLBACK_USER_COMMAND: EXIT routine for command handling
    I_STRUCTURE_NAME: Internal output table structure name     
    IS_LAYOUT: List layout specifications 
    IT_FIELDCAT: Field catalog with field descriptions
    IT_EXCLUDING: Table of inactive function codes   
    IT_SPECIAL_GROUPS: Grouping fields for column selection
    IT_SORT: Sort criteria for first list display
    IT_FILTER: Filter criteria for first list output
    IS_SEL_HIDE     : Selection information modification
    I_DEFAULT:      Initial variant active/inactive logic
    I_SAVE: Variants can be saved
    IS_VARIANT     : Variant information
    IT_EVENTS: Table of events to perform  IT_EVENT_EXIT :  Standard fcode exit requests table 
    IS_PRINT: Print information
    IS_REPREP_ID: Initialization keys for Re/Re interface
    I_SCREEN_START_COLUMN: Coordinates for list in dialog box
    I_SCREEN_START_LINE: Coordinates for list in dialog box
    I_SCREEN_END_COLUMN: Coordinates for list in dialog box        
    I_SCREEN_END_LINE: Coordinates f

  • Conditional Select  - How to retrieve data based on different cond.

    Hi
    I have a requirement to retrieve Equipments for Sales orders. But the selection criteria includes that if an Equipment with a EQTYp = 0 exists, only that record needs to be retrieved. And if no such equipment (Eqtyp = 0) exists, then retrieve any equipment from the Sales Order.
    I have for this reason selected a process as follows:
    First collect all sales orders, collect Equipments for them from SER02 and OBJK. And then look for a EQtyp = 0 equipment for each sales order line item. If no such one is found, then one of the other equipments is selected.
    As the report needs to be run open (without specifying any sales orders) at times, the amount of sales orders that are to be checked becomes huge and so retrieving the equipmets also becomes hectic in my current process.
    So, is there any other way to retrieve this information? or can a select be formulated in such a way that it can decide to pick a EQTYP <> 0  equipment when a EQTYP = 0 equipment is not found.
    Thanks in advance.
    Jr.
    Message was edited by:
            Jr Abaper

    Hi
      Is Equipment is an selection-screen field?
    If so give Equipment value = o and # in the selection-screen while executing?
    If that is not an selection-screen field in the select query in the where condition you can mention Equipment = 0 or
                             equipment # 0.
    This can optimize the code some what.
    Regards,
    Sreeram

Maybe you are looking for

  • Excel .xls 'read only' after downloading security update

    Today all my data .xls files won't open - the message reads: I am able to open one .xlsx file but all the .xls will only open as 'quick view' I've recently downloaded Security Update 2015 version 1 and also updated Remote Desktop client. I restarted

  • Quicktime error -9459

    This morning it worked fine, tonight not so good. I am compressing to ProRes Progressive. The batches all fail with that error - quicktime error -9459. Also, applying settings to the jobs in Compressor is very slow. Each setting takes about 5 seconds

  • Batch return problem

    Suppose for production order no. 123 of qty 1000 EA i had issued material for 800 EA but when production had started i had used only 500 EA & now i wish to transfer 300 EA again in unrestected stock .From where i will come to know about records again

  • Let Auto-Map in Transform work with COLLAPSED nodes/tags ?

    When I open for a "Transform" activity the mapping editor and drag one complextype from one side to another on the other side then Auto-Mapping only works if the node/tag trees on both elements/sides are full expanded. If they are collapsed then auto

  • T42 hangs, extremely slow performance

    Hello, I can boot up my T42, but it works very slowly.  In safe mode with networking, it works great.  I have automatic updates turned on, but it cannot successfully download updates.  It still has service pack 2.  Not sure if that's related to slow