RBDAPP01 issues?

Hi, All:
when we run RBDAPP01 to post sales order  IDOC. In the Parallel Proc. tab. If we check on the Parallel Proc. Active checkbox.  we can't catch sy-tcode or sy-batch in user exit USEREXIT_MOVE_FIELD_TO_VBKD.
How do I know this program run in parallel in the above user exit?
thanks in advance!

Have you looked for notes? See 399271.
Rob

Similar Messages

  • Performance issues in using RBDAPP01 for reprocessing iDocs with Status 64

    Hi All,
    I am using the Standard ABAP Program 'RBDAPP01' for reprocessing Inbound iDocs with Status 64 (Ready to be posted).
    When this is scheduled as a job in background, I find that it opens multiple sessions and occupies all available dialog sessions.
    This in turn slows down the entire system.
    Also, I find the addition 'Packet Size' on the selection screen for the program.
    Is it related in any way to the number of sessions the program creates?
    Any pointers in resolving this issue will be extremely helpful.
    Thanks in advance.
    Regards,
    Keerthi

    Hi,
    When you mention Parallel Processing, it becomes active only if I choose that particular option on the selection screen right?
    In my case, I haven't chosen parallel processing, but still the overall system performance seems to have fallen very badly.
    Now please correct me if my understanding is wrong.
    If I increase my Packet Size, it should improve the system performance, but will increase my runtime for the selected iDocs.
    But as I have not selected parallel processing in this current situatuon, it should not have any impact here.
    Have I summarized it rightly?
    Thanks in advance.
    Regards,
    Keerthi

  • RBDAPP01 DATA POSTING ISSUE

    Hi Guys,
    We are using RBDAPP01 program to post the IDOCS created  with message type PPCC2PRETEVENT (Status 64 to 53).The periodic Job meant for RBDAPP01 completes every time and Iam getting the status 64.
    In my case,RBDAPP01 submits the data to Function module CO_RS_CORUPROC1_START(which has CORUPROC1 program in it and the program is meant for transfer the data from AFRP0 to AFRU by using max 4 workprocesses and max 10 confirmations in each workproceses).
    Now the issue every time RBDAPP01 program completed,Iam getting SM58 error records as Object(in our case CORUPROC1) is currently Locked by user xxxx.   If I process 20 records,only 1 or 2 or 3 are transferring and for other records Iam getting SM58 error(But later automatically system transfering the records and hence no loss of data).
    I think this may be due to availablity of workprocesses and share me the way to avoid these SM58 errors an

    Hello Krishnan,
    would you tell me how this issue has been resolved?
    Thands and best regards
    Andreas

  • Idoc processing best practices - use of RBDAPP01 and RBDMANI2

    We are having performance problems in the processing of inbound idocs.  The message type is SHPCON, and transaction volume is very high.  I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
    1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
    2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
    We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time.  We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked.  Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing.  The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
    I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system.  I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses.  I have been told that setting the messages to trigger immediately in WE20 can result in poor performance.  So I am wondering if the best practice is to:
    1)     Set messages in WE20 to Trigger by background program
    2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
    3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
    I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable.  Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem.  I would welcome any comments.
    This appeared to be the correct area for this discussion based upon other discussions.  If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it.  Thank you for your help.

    Hi Bob,
    Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
    I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
    In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
    Also I believe we had a designated server for the background jobs, which helped with the resource availability.
    As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
    Hope this helps.

  • RBDAPP01 going into SLEEP Mode and Idocs still in 64 status

    Hey all,
          I have a Inbound Idoc interface which is being processed using RBDAPP01 Program. The Issue I am facing is that the job running the rbdapp01 program goes into sleep mode even though there are idocs present in 64 status. I tried to debug the work process using SM66 but it does not open any debugging window although it says debugging started. If I cancel the Job and run it again it processes those Idocs Any input on how one can resolve this issue?
    Thanks.

    Hi Aparna,
    Here is extract from SAP material on running RBDAPP01 transaction and possible reasons for delay in processing. HOpe this can help you.
    To automate the treatment of IDocs, you must run the ABAP program RBDAPP01 (transaction BD20) in job. This program has a very good option for parallel processing which can reduce a lot the time required for treatment. However use it carefully and make sure you set a packetsize high enough to avoid that your SAP system be overwhelm by demands for available dialog tasks (don't forget one dialog task is monopolized per IDocs packed to treat).
    Best Regards,
    Krishna

  • RBDAPP01 - First IDoc the CMOD works all subsequent ones don't..

    Hi All
    I have an interesting issue with RBDAPP01, I have developed a CMOD in Include ZXVEDU04 to block duplicate orders based on the cust PO number and to convert the quantity coming in if certain Units of measure are specified by the trading partners.
    When I test this with a single IDoc in WE19 everything works as expected.
    If however I process multiple IDocs using RBDAPP01- the first IDoc is processed successfully, but ALL of the subsequent IDocs do not work correctly...
    The user exit is being called for all IDocs as there is other code in the exit that is working for all of the IDocs and not just the first..
    Has anyone come across this problem before?
    Your views on this would be greatly appreciated..
    Many Thanks.

    The issue was with a static variable that was not being re-initialised when each Idoc was processed, hence the reason why it worked for one and not for multiple IDocs.
    Please note therefore that SAPLVEDA does not initialise its variables for each IDoc that is processed.

  • RBDAPP01 - Many arfc jobs tirggered - Why ?

    Hello all,
    we have an issue here on a solution being implemented. We want to process idoc DEBMAS in mass.
    > A program creates idocs ready to be processed (64 status), seems OK
    > in WE20 DEBMAS is set up to process in background (no immediate processing)
    > We call rbdapp01 to process these idocs (DEBMAS). We use parallel processing here when calling the program.
    > When job runs we see that parallel dialogs tasks are called to process the idocs
    > But when we check in SM37 after that wee see that there are lots of arfc jobs tirggered too.
    My question is,
    as here we set up WE20 to process incoming indoc via background program why do we have these arfc jobs triggered ??
    We thought that during RBDAPP01 dialogs tasks will be used to process in parallel mode but we do not understand whay we have also thes arfc* jobs created.
    Could someone help me on that point ?
    Thanks a lot for your help,
    A.W

    Thanks a lot Nabheet for your answer.
    But per my understanding the parallel tasks called in RBDAPP01 are dialog tasks (not background).
    So this is why i was not understanding we have addtionally these jobs too..
    I checked the kink you sent and I see that in the 1st link it said that for the unsuccesfull rfc call a job arfc will be created.
    It also shows how to disable that (in trfc options of the RFC destination).
    Is there a "functional" way to disable thes jobs scheduling ? (instead of modifiying the trfc options of the destination).
    I mean in logical processing of these idocs ?
    Again thx for your help,
    AW

  • RBDAPP01 is not processing Idoc's

    Hi,
    We are facing an issue that the RBDAPP01 program scheduled to process inbound Idoc's is not picking Idoc's for posting and running for ever with out processing Idoc's.
    Please let me know what could be the reason for this kind of behavior.
    Regards,
    Cheritha

    Hi ,
         Check your idoc is in 64 status ? If it in 64 process then process with RBDAPP01 in background or Put that idoc in BD87 and process in foreground.
    Thanks,
    Asit Purbey

  • RBDAPP01 - Delta

    Hi All,
    We use RBDAPP01 for processing of inbound IDOCs , with basic type DELVRY03 and message type SHPCON. We make changes to the actual PGI date. When we do WE19 and post a IDOC the delivery gets changed correctly and delta's seems to flow fine. When we use program RBDAPP01, the deliveries are posted correctly, but the delta for the PGI date is not captured. This is causing data inconsistency in our BI DSO.
    Has anyone come across this issue.
    Thanks,
    Krishna

    Hi Krishna,
                     We had a similar scenario and we created a wrapper FM and used the same to process both the idoc types, this is working for us just fine. I am not sure for RBDAPP01 program but try to debug the complete program once, Generally it seems that this should work as well.
    Best Regards,
    Tapodipta Khan.

  • Background ORDRSP posting via RBDAPP01

    Hello Everybody,
    running RBDAPP01 in background (w/O any parallel process and/or packetsize set) in order to post incoming ORDRSP pending in status 64, we noticed that the posting order doesn't respect the sequence of the selected IDOCs (for instance the first of the list are always the last one to be posted!) and this is a big problem in case of ORDRSP where the posting order is very important.
    Someone of your have already faced this problem? How can be solved?  txs RS

    Well, the question is 'flagged' as answered and obviously you were right, Harald, to assume that the field 'serialisation' was empty at the OP's site. I would never have guessed that ...
    Dear OP, can we please continue to derail your thread to discuss this issue further? I never got the chance to pester an expert like Harald, so please indulge me.
    @Harald
    >
    Harald Boeing wrote:
    > With release 6.40 (backported later to 6.20) SAP introduced also the option to use qRFC, which I'd say reflects probably best the strict serialization requirements by object type (though of course the queue name really drives the serialization).
    Would you agree, then that if you were to run a STO-scenario in one SID, one client, different company codes (so no middle-ware, no other interfaces etc.), that qRFC is the safest option to achieve serialisation (well, yes - by queue-name - but since you have to define that in your rule in WE20 ... you are still pretty safe) or are you of the opinion that I have been fooling myself here ... ? Could I have achieved the same goal with RBDAPP01 - but extending the serialisation to -say- milliseconds or something?
    >
    Harald Boeing wrote:
    > I'd say that depends, because to the best of my knowledge RBDAPP01 honors the serializations by object type and thus parallel processing (one RBDAPP01 instance) would still be safe...
    Where can I find out, whether that is precisely correct? Do you know of a note or a link or something where I can get exactly this statement (preferably out of SAP)?
    >
    Harald Boeing wrote:
    >As a side note - I still don't understand that SAP doesn't seem to properly lock IDocs when processing them. When I discovered it first I couldn't believe it and thought it's a nasty bug, but it seems SAP sees that different. If somebody knows the reason for this missing IDoc locking - please enlighten me...    (or did they implement it finally?)
    As far as I can see for now - but we only have on system landscape with NW 7.0 and that only for a couple of weeks - it is still not implemented. As for the reasons ... they elude me. Completely.

  • New DVR Issues (First Run, Channel Switching, etc.)

    I've spent the last 30 minutes trying to find answers through the search with no luck, so sorry if I missed something.
    I recently switched to FIOS from RCN cable in New York.  I've gone through trying to setup my DVR and am running into issues and was hoping for some answers.
    1.  I setup two programs to record at 8PM, I was watching another channel at the time and only half paying attention.  Around 8:02 I noticed a message had popped up asking if I would like to switch channels to start recording.  I was expecting it to force it to switch like my old DVR, but in this case it didn't switch and I missed the first two minutes of one of the shows.  I typically leave my DVR on all day and just turn off the TV, this dual show handling will cause issues with that if I forget to turn off the DVR.  Is there a setting I can change that will force the DVR to choose one of the recording channels?
    2.  I setup all my recordings for "First Run" because I only want to see the new episodes.  One show I setup was The Daily Show on comedy central, which is shown weeknights at 11pm and repeated 3-4 times throughout the day.  My scheduled recordings is showing all these as planned recordings even though only the 11pm show is really "new".  Most of the shows I've setup are once a week so they aren't a problem, but this seems like it will quickly fill my DVR.  Any fixes?
    Thanks for the help.
    Solved!
    Go to Solution.

    I came from RCN about a year ago.  Fios is different in several ways, not all of them desirable.  Here are several ways to get--and fix--unwanted recordings from a series recording setup.
    Some general principles. 
    Saving changes.  When you originally create a series with options, or if you go back to edit the options for an existing series, You MUST save the Series Options changes.  Pretty much everywhere else in the user interface, when you change an option, the change takes effect immediately--but not in Series Options.  Look at the Series Options window.  Look at the far right side.  There is a vertical "Save" bar, which you must navigate to and click OK on to actually save your changes.  Exiting the Series Options window without having first saved your changes loses all your attempted changes--immediately.
    Default Series Options.  This is accessed  from [Menu]--DVR--Settings--Default Series Options.  This will bring up the series options that will automatically be applied to the creation of a NEW series. The options for every previously created series will not be affected by a subsequent modification of the Default Series Options.  You should set these options to the way you would like them to be for the majority of series recordings that you are likely to create.  Be sure to SAVE your changes.  This is what you will get when you select "Create Series Recording" from the Guide.  When creating a new series recording where you think that you may want options different from the default, select "Create Series with Options" instead.  Series Options can always be changed for any individual series set up later--but not for all series at once.
    Non-series recordings.  With Fios you have no directly available options for these.  With RCN and most other DVRs, you can change the start and end times for individual episodes, including individual episodes that are also in a series.  With Fios, your workarounds are to create a series with options for a single program, then delete the series later;  change the series options if the program is already in a series, then undo the changes you made to the series options later; or schedule recordings of the preceding and/or following shows as needed.
    And now, to the unwanted repeats. 
    First, make sure your series options for the specific series in question--and not just the series default options--include "First Run Only".  If not, fix that and SAVE.  Then check you results by viewing the current options using the Series Manager app under the DVR menu.
    Second, and most annoying, the Guide can have repeat programs on your channel tagged as "New".  It happens.  Set the series option "Air Time" to "Selected Time".  To make this work correctly, you must have set up the original series recording after selecting the program in the Guide at the exact time of a first run showing (11pm, in your case), and not on a repeat entry in the Guide.  Then, even it The Daily Show is tagged as New for repeat showings, these will be ignored. 
    Third, another channel may air reruns of the program in your series recording, and the first showing of a rerun episode on the other channel may be tagged as "New".  These can be ignored in your series if you set the series option "Channel" to "Selected Channel".  Related to this, if there is both an SD and HD channel broadcasting you series program, you will record them both if the series option "Duplicates" is set to "Yes".  However, when the Channel option is set to "Selected Channel", the Duplicates Option is always effectively "No", regardless of what shows up on the options screen.  
    As for you missing two minutes,  I have sereral instances in which two programs start recording at the same time.  To the best of my recollection, whenever the warning message has appeared, ignoring it has not caused a loss of recording time.  You might have an older software version.  Newest is v.1.8.  Look at Menu--Settings--System Info.  Or, I might not have noticed the loss of minutes.  I regularly see up to a minute of previous programming at the start of a recording, or a few missing seconds at the beginning or end of a recording.  There are a lot of possibilities for that, but the DVR clock being incorrect is not one of them.  With RCN, the DVR clocks occasionally drifted off by as much as a minute and a half.

  • Pension issue Mid Month Leaving

    Dear All,
    As per rule sustem should deduct mid month joining/leaving/absences or transfer scenarios, the Pension/PF Basis will be correspondingly prorated. But our system is not doing this. In RT table i have found 3FC Pension Basis for Er c 01/2010                    0.00           6,500.00.
    Employee leaving date is 14.04.2010. system is picking pension amout as 541. Last year it was coming right.
    Please suggest.
    Ashwani

    Dear Jayanti,
    We required prorata basis pension in case of left employees and system is not doing this. This is the issue. As per our PF experts Pension amount should come on prorata basis for left employees in case they left mid of month.System is doing prorata basis last year but from this year it is deducting 541. I am giving two RT cases of different years.
    RT table for year 2010. DOL 26.04.2010
    /111 EPF Basis              01/2010                    0.00           8,750.00 
    /139 VPF Basis              01/2010                    0.00           8,750.00 
    /3F1 Ee PF contribution     01/2010                    0.00           1,050.00 
    /3F3 Er PF contribution     01/2010                    0.00             509.00 
    /3F5 Ee Mon PF contribution 01/2010                    0.00           1,050.00 
    /3F6 Ee Ann PF contribution 01/2010                    0.00          12,600.00 
    /3F9 PF adm chrgs * 1,00,00 01/2010                    0.00              96.25 
    /3FA PF basis for Ee contri 01/2010                    0.00           8,750.00 
    /3FB PF Basis for Er Contri 01/2010                    0.00           8,750.00 
    /3FJ VPF basis for Ee contr 01/2010                    0.00           8,750.00 
    /3FL PF Basis for Er Contri 01/2010                    0.00           6,500.00 
    /3F4 Er Pension contributio 01/2010                    0.00             541.00
    /3FC Pension Basis for Er c 01/2010                    0.00           6,500.00
    /3FB PF Basis for Er Contri 01/2010                    0.00           8,750.00
    /3FC Pension Basis for Er c 01/2010                    0.00           6,500.00
    /3FJ VPF basis for Ee contr 01/2010                    0.00           8,750.00
    /3FL PF Basis for Er Contri 01/2010                    0.00           6,500.00
    /3R3 Metro HRA Basis Amount 01/2010                    0.00           8,750.00
    1BAS Basic Salary           01/2010                    0.00           8,750.00
    RT table for year 2009. DOL 27.10.2009
                                                                                    /111 EPF Basis              07/2009                    0.00           9,016.13
    /139 VPF Basis              07/2009                    0.00           9,016.13
    /3F1 Ee PF contribution     07/2009                    0.00           1,082.00
    /3F3 Er PF contribution     07/2009                    0.00             628.00
    /3F5 Ee Mon PF contribution 07/2009                    0.00           1,082.00
    /3F6 Ee Ann PF contribution 07/2009                    0.00           8,822.00
    /3F9 PF adm chrgs * 1,00,00 07/2009                    0.00              99.18
    /3FA PF basis for Ee contri 07/2009                    0.00           9,016.00
    /3FB PF Basis for Er Contri 07/2009                    0.00           9,016.00
    /3FJ VPF basis for Ee contr 07/2009                    0.00           9,016.00
    /3FL PF Basis for Er Contri 07/2009                    0.00           5,452.00
    /3FB PF Basis for Er Contri 07/2009                    0.00           9,016.00 
    /3FC Pension Basis for Er c 07/2009                    0.00           5,452.00 
    /3FJ VPF basis for Ee contr 07/2009                    0.00           9,016.00 
    /3FL PF Basis for Er Contri 07/2009                    0.00           5,452.00 
    /3R4 Non-metro HRA Basis Am 07/2009                    0.00           9,016.13 
    1BAS Basic Salary           07/2009                    0.00           9,016.13 
    Now please suggest what to do. where is the problem  ? If have also checked EXIT_HINCALC0_002 but nothing written in it.
    With Regards
    Ashwani

  • Open PO Analysis - BW report issue

    Hello Friends
    I constructed a query in BW in order to show Open Purchase Orders. We have custom DSO populated with standard
    datasource 2lis_02_itm (Purcahse Order Item). In this DSO we mapped the field ELIKZ to the infoobject 0COMP_DEL
    (Delivery completed).
    We loaded the data from ECC system for all POs and found the following issue for Stock Transport Purchase orders (DocType = UB).
    We have a PO with 4 line items. For line items 10 and 20, Goods issued, Goods received and both the flags "Delivery
    complete" and "Final delivery" checked. For line items 30 and 40, only delivery indicator note is issued for zero
    quantity and Delivery complete flag is checked (Final delivery flag is not checked) in ECC system. For this PO, the
    delivery completion indicator is not properly updated in the DSO for line items 30 and 40. The data looks like the
    following:
    DOC_NUM     DOC_ITEM       DOCTYPE     COMP_DEL
    650000001       10     UB        X
    650000001       20     UB        X
    650000001       30     UB
    650000001       40     UB      
    When we run the Open PO analysis report on BW side this PO is appearing in the report but the same is closed in ECC
    system.
    Any help is appreciated in this regard.
    Thanks and Regards
    sampath

    Hi Priya and Reddy
       Thanks for your response.
                         Yes the indicator is checked in EKPO table for items 30 and 40 and delta is running regularly for more than 1 year and no issues with other POs. This is happening only for few POs of type Stock Transport (UB).
                        I already checked the changes in ME23N and the Delivery completed indicator was changed and it reflected in EKPO table. Further, i checked the PSA records for this PO and i am getting the records with the Delivery completed flag but when i update from PSA to DSO the delivery completed indicator is not updating properly.
                       In PSA, for item 30 i have the following entries. Record number 42 is capturing the value X for ELIKZ but after that i am getting two more records 43 and 44 with process key 10 and without X for ELIKZ. I think this is causing the problem.
    Record No.    Doc.No.                    Item              Processkey         Rocancel     Elikz
        41               6500000001            30                    11                            X           ---    
        42               6500000001            30                    11                            ---           X
        43               6500000001            30                    10                            X           ---
        44               6500000001            30                    10                            ---         ---
    (Here --- means blank)        
    Thanks and Regards
    sampath

  • HP LaserJet Enterprise 600 M602 driver issue

    Hello,
    I've got issue with 600-series printers. We use the latest UPD drivrer ver. 61.175.1.18849 and print from XenApp 6.5. The error occurs every time when users try to print jpg files from XenApp session. It only happens with 600 series printers and UPD.
    Also I've tried to assign native 600-series driver ver. 6.3.9600.16384 and it works good. But with that driver system says that it's color printer and it brokes our printing reports. These reports are very important for us. So we can't use printer and that driver as well.
    Printer installed on Windows Server 2012 R2. All clients are Windows 7 x64. XenApp Servers are Server 2008R2.
    Is it possible to get fixed UPD driver or correct native driver for Server 2012 R2?
    Regards,
    Anatoly

    I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial printer. You can do this at Printers - LaserJet.
    Click on New Post.
    I hope this helps.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Gemini02
    I work on behalf of HP

  • Windows 7 displays error message when exiting +cursor issue

    Two issues here. CS5 Phoshop on Wind 7 64 bit.
    Physical processor count: 8
    Processor speed: 3073 MHz
    Built-in memory: 12279 MB
    Free memory: 9577 MB
    Memory available to Photoshop: 10934 MB
    Memory used by Photoshop: 80 %
    Image tile size: 128K
    First issue is since the latest automatic Adobe update (why fix what isn't broken?) Every time I now exit Photoshop I get the message "Adobe QT Server has stoped working" and occasionally it happens when I exit bridge. Indesign is also behaving badly. I can no longer start a previous document from file manager without ID crashing out.
    The other is the cursors in Clone and erase lose their edge (become invisable) for no reason - well not quite. Noise Ninja crashed Photoshop when I tried to use it. I reinstalled it and all is well. The cursor issue seems to be intermittant but came back (for no reason) after I reinstalled NN. I can't seem to change the cursor, no matter what I do. The problem is now seriously affecting how I work. Almost enough to go back to Win XP which ran CS5 Photoshop flawlessly.
    Any help will be gratefully accepted.
    Doug

    function(){return A.apply(null,[this].concat($A(arguments)))}
    doug87510 wrote:
    The recent problem is the entire outline of the cursor (including the crosshair in the middle) was missing at any size of cursor. All I had was exactly what I'd get if I used a real spraygun.
    Well, that issue is simply a matter of hitting the Caps Lock key.  When Caps Lock is on, you'll see the cursor outline, and when it is off you'll see a crosshair.  That's a feature, not a bug.
    Glad to hear the 11.1 drivers are out.  I will download them and try them now myself.
    Regarding "Adobe QT" crashing...  QT brings to mind QuickTime, though that is Apple, not Adobe.  Do you have Apple QuickTime installed?
    Regarding memory usage, with 12 GB of installed RAM, you should be able to set Photoshop to use 90% or more in Edit - Preferences - Performance.
    -Noel

Maybe you are looking for

  • Ipod classic cannot seem to work with itunes

    I have been having problems with the new itunes epscially with syncing my iPod classic(6th gen), once I started using itunes 11 whever I plugged in my iPod the whole system would jam, furthermore once I'd plug out the ipod I would get the message "iT

  • Acrobat 9.4.2 Portfolio Welcome Page, Headers, Footers

    I recently upgraded to Acrobat 9.4.2 and now cannot save welcome page, headers, footers in portfolios I create. Portfolios created in previous verious 9.X.X. properly display welcome page, headers, footers. Anyone with ideas. Is there some setting I

  • Excluding condition type for a Purchasing document type

    Dear all, I want to excude a particular condition type from pricing in a Purchase order. How to do this and where actually it is assigned to a dcoument type? Please give steps in both spro and easy access? thanks and regards, Prashanth

  • In safari my keypad disappears after one key stroke

    in afari my keypad disappears if i hit a letter or number key.  the ipad was purchased new 9/13 with wifi access. the iso 8 is current but the problem began with iso 7..i have reset system.  i don't want to wipe it yet...

  • Advice Needed Before Purchase

    Hi, I am looking at buying one of the new intel iMacs and will make sure I upgrade the harddrive and have plenty ram in there. Want this to last me a couple of years at least. I'm not sure if I should upgrade the graphics memory as well though from t