Direct X 10 and creative soundca
fairly soon direct x 0 will be released...and I'm wondering about creative sound cards...will there be a direct x 0 release of cards? will my sound card still work with a direct x 0 compatible video card? what, in general, is going to happen? anyone with any information is encouraged to post...
Yes they will work. Even the x-fi isnt direct x 9 card. Its directx 8. Soundcards arent that dependant of directx as gpu?s are.
Similar Messages
-
Strobe and Creative Suite? and HTML5 Video?
The most recent Strobe release (StrobeMediaPlayback_1.5.Sprint4-full.zip), included an html5demo.html
The Dreamweaver team just announced a Kaltura.com-based HTML5 Video Player widget.
Is the Strobe html5demo.html any indication of HTML5 Video support by Strobe?
Also, regarding the core SWF-based Strobe, are there any plans to provide any direct SMP integration with Creative Suite applications?
Thanks again for your great work.
Warmest regards,
gWhat had me very concerned is system requirements on the box state that a "multicore" processor is required. The smaller iMac (best suited to my budget) comes with an optional dual-core i5 processor, and the larger iMac can be equipped with quad-core i7 processors. I wasn't sure if "dual-core" qualified as "multicore" in Adobe's specification.
Thanks. -
Hello, we have both Creative Cloud membership and Creative Cloud for team. Can you help me with the difference and if i need to have both? We have 9 employees that are using it. Just not sure if i'm paying for something i don't need.
Thank youPlease refer to Creative Cloud Help | Creative Cloud / Common Questions
CC is for retail use with 20 GB of storage space, CCT is where number of seats are purchased & assigned by one program admin where each seat gets 100GB of storage space.
You can not have both the CC & team in one account as it will only provide you added storage space of 120 GB but you can activate the CC any of them or either of them twice as CC is based on Adobe ID.
Regards
Rajshree -
I recently purchased season 7 of entourage from Itunes and downloaded directly to IPad2. When I selected to play the tv shows the screen would go black and become disabled. I have to hit the home page to exit and then search for another movie in my ipad to get access to the library again. I have tried downloading directly to PC and then transferring to IPad without success. I don't think it is the download itself because I can play the tv shows on the pc and my iphone. Am I missing a setting? also, I can watch other tv shows or movies so my video app is not completely fouled up.
Sometimes simply restarting your iTunes, the computer and the iPad is all that it takes to correct an issue like this so try that. Quit iTunes, reboot your computer, and restart the iPad. Then try the sync again.
Restart the iPad by holding down on the sleep button until the red slider appears and then slide to shut off. To power up hold the sleep button until the Apple logo appears and let go of the button. -
Business Catalyst and Creative Cloud not Working
I have a $2000 Premiere Business Catalyst Partner account. I set up my BC account and my Adobe ID years ago under different e-mails. When I tried to integrate my BC and Adobe Creative Cloud e-mails I got an error saying that I have to create a new Adobe ID.
I created a new ID. Now with Dreamweaver I'm getting the following error that I don't have a Partner Account!!! I do have a partner account, it's just under a different e-mail. Am I to stomach the fact that I will not be ablt to use my BC account on Creative Cloud simply because they are under 2 different e-mails? I've been waiting to use BC and Creative Cloud for months, what a dissapointment. This takes all the appeal out of Dreamweaver, Muse, and more, if I can't use Business Catalyst with Creative Cloud. Please help....
IPlease refer to a couple of similar threads below.
Can't access my BC Premium Partner site in Dreamweaver CS6 - http://forums.adobe.com/message/4399268#4399268
BC and DW CS6 Issues - http://forums.adobe.com/message/4399267#4399267
Also, please reference the last FAQ note within the page below.
http://forums.adobe.com/docs/DOC-2153 -
I have just upgraded from Lightroom 5 standalone to Lightroom 6 standalone. I appear to have been automatically enrolled for a 30 day free trial of Lightroom Mobile and Creative Cloud. Reading the FAQ, it appears that after the expiry of the free trial, if I do not sign up and pay, I will only be able to view my pictures on the desktop but not edit them - surely this cannot be true. How do I un-enroll for the 30 day free trial of Lightroom Mobile and CC?
When I was signed into Adobe (which was a requirement for installing the upgrade), Lightroom 6 told my at the top right corner that I had 30 days left of my free trial of Lightroom Mobile and Creative Cloud. In parallel with this forum posting, I am chatting with Adobe support. he is away to find out how to prevent any synching with Creative Cloud during the 30 day free trial. I do not think that Creative Cloud is an application that gets installed on your PC. I think Lightroom 6 has it built in, and can use it if if you are signed up to the Creative Cloud and Lightroom Mobile (which I am for 30 days)
-
Questions about the future directions of InfoPath and Microsoft Access
Because I have been confused about the future directions of InfoPath and Access, I wrote a short blog post, which I have pasted below. My question is, can Microsoft provide some more guidance on Access vs InfoPath? If Access is indeed the
the future direction, can you please provide some pointers to resources that can help us transition.
A Short Review of MS Access, SharePoint ,InfoPath (2013)
After the November 2012 SharePoint Conference in Las Vegas (#spc12) there were a number of blog posts and people saying that Access 2013 was great and would be replacing InfoPath.
Marc Anderson and
Ruven
Gotz have short posts summarizing #SPC12 and touch on the subject of InfoPath and Access. I also spoke with several individuals shortly after #SPC12 and they were excited about Access 2013.
Since I rely heavily on InfoPath for much of what I do, I wanted to kick the tires and see what everyone was talking about. First, a few notes about SharePoint 2013 and Office 2013.
Microsoft should rename Access: If you have tried to
bing the word Access, then you know that the search results are overwhelming, because the word "access" is used for so many other purposes.
Use the RTM version of Office 2013! I was performing my investigations by leveraging the Office 365 Beta and the Office Applications that come with it. Not much was working! After I uninstalled the Beta
version of Office 2013 and Installed the RTM version everything seemed to work.
Windows 7 and IE 9.0: The drag & drop that is being touted as
"manna from heaven" seems to work well with Firefox, Safari, Chrome, and IE 10, but it does
not work with IE 9!
Non Microsoft browsers are still second class citizens (except for the drag & drop): Microsoft has finally done away with the Active X's for datasheet view (that is brilliant!) One can now see the newly
minted datasheet view in many browsers. But I still find that one needs to be in IE to do a number of key manual opeartions. For example pasting numerous rows of data from a spreadsheet into the new sheet view works only in IE.
Access 2013
Microsoft Access is touted as a non developer tool. I know a number of people who are on the business side and love Access. These people will like the renewed energy that Microsoft has applied to Access. One should note that conceptually
this functionality existed in SharePoint 2010. Here is what I see that is new:
+The new version works better:Although I haven't tested it fully, it seems that many more features that work on the Desktop version of Access, now work in the published Web Application which is hosted by SharePoint 2013.
+The new version has fairly robust browser based forms: End users can now fill in data using forms that are rendered in the browser.
+The published version that resides in SharePoint now uses its own SQL server tables. So the engine appears to be SQL Server, not a modified version of Access built for a server. This stands to be quite robust, but I imagine
that some quirks will surface due to new model.
The limitations are:
- Access is pretty much its own application and does not integrate with SharePoint building blocks. For example, an Access table is not easy to integrate with a SharePoint workflow. Further, although Access forms now are visible
in a browser, they are not nearly as rich as InfoPath forms. InfoPath forms cannot easily integrate with the Access tables. In order to integrate SharePoint features and Access, one needs to tie SharePoint list(s) to Access as data sources.
This overcomplicates the model and one may very well run into synchronization issues.
In short, although I believe there will be some people who will be happy with newly minted Access, I do not think that Access will be able to replace InfoPath and Workflow technologies. I do agree that Microsoft does not seem to have put much energy into
InfoPath. If they leave a vacuum in this space, then others may very well take over, for instance Nintex Forms.Although I agree with the comments made by Ruven and Marc after the conference please note that those blog posts are their own personal opinions and that they don't work for Microsoft. A lot of people have asked Microsoft to clarify the future of InfoPath
and the response up until now has been a deafening silence. In my opinion speculations about Access replacing InfoPath are premature.
I should also point out that most of your comments about Access 2013 above are actually about Access Services in SharePoint Server 2013. Access Services are NOT Access they are a shared service offering in SharePoint that convert and publish Access
databases and forms. As you point out once an Access database is published through Access services it is converted to SQL Server and no longer resides in Access. Of course I don't work for Microsoft either so these are all just my personal opinion.
Having said that I doubt you will get the confirmation/response that you are hoping for from any official Microsoft channel.
Paul Stork SharePoint Server
MVP Principal Solutions Architect: BlueChip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem. -
I have an Epson Perfection V100 scanner and can no longer scan after upgrading to Mountain Lion and Creative Suite 5.5. Any suggestions?
Check the Epson web site for updates to drivers and Epson scan software.
-
How do I reinstall PSCS6 and creative cloud? Download center gives me (amm) protocol error message.
My computer crashed, had to restore to a pre-photoshop and creative cloud backup. When I sign in online, every link seems to take me to the download center. However, when I try to download anything from there, I get a message that says
Firefox doesn't know how to open this address, because the protocol (aam) isn't associated with any program.
It recommends thats the problem may be resolved by downloading software, however, like I said, I can't seem to find a way to download the programs from anywhere else.
Suggestions??EReinstall the Creative Cloud app.
Mylenium -
Wait events 'direct path write' and 'direct path read'
Hi,
We have a query which is taking more that 2 min. It's a 9.2.0.7 database. We took the trace/tkprof of the query,and identified that there are so manay 'direct path write' and 'direct path read' wait events in the trace file.
WAIT #3: nam='direct path write' ela= 5 p1=201 p2=70710 p3=15
WAIT #3: nam='direct path read' ela= 170 p1=201 p2=71719 p3=15
In the above, "p1=201" is a file_id, but we could not find any data file, temp file, control file with that id# 201.
Can you please let us know what's "p1=201" here, how to identify the file which is causing the issue.
Thanks
SravanWhat does:
show parameter db_filesreturn? My guess, is that it returns 200.
The direct file read and direct file write events are reads and writes to TEMP tablespace. In those wait events, the file# is reported as db_files+temp file id. So, 201 means temp file #1.
Now, as to your actual performance problem.
Without seeing the SQL and the corresponding execution plan, it's impossible to be sure. However, the most common causes of temp writes are sort operations and group by operations.
If you decide to post your SQL and execution plan, please be sure to make it readable by formatting it. Information on how to do so can be found here.
Hope that helps,
-Mark
Edited by: mbobak on May 1, 2011 1:50 AM -
How do I get rid of behance and creative cloud?
how do i get rid of behance and creative cloud?
To delete your Behance account, login at Behance.net please go into your 'Me' tab, visit account settings and hit the privacy tab. There, you'll have the option to delete. Before you do so, please note that:
Deleting your account is PERMANENT.
All of your content will be deleted.
All of your information, including comments, messages, discussion posts, etc will be deleted.
You will not have access to your profile, your projects, or your frame view. -
E payment should be enabled so that the user could make payment directly from SAP and after the payment is verified ,approved and authorized by the concerned users responsible the payment should be electronically transferred to the payee’s bank account through our bank.
Thanks,
I usually use the OS connection option. So as you suggest, connect without the ISP connection software. Doing so does not by-pass the sudo command being active in Activity Monitor however.
On reading my post I see my failure to link the concerns of the laptop purchase with the sudo and modem. My thought here is of an intersection of known vulnerability with this widely used modem/software (via permanent sudo process activated) and that vulnerability then being known and utilised by another party(s).
I am pursuing the issue in part with consideration to a broader possible issue of vulnerability.
Thanks again for your thoughts and suggestions. Valued. -
Direct Delta, Queued and Unseralized V3
HI
FOR IM datasources, BF and UM, the guide mentions Direct Delta as the preferred selection. How do we decide this?
Also for LO cockpit DS in SD, what selection is chosen?
Thanks
Hariehi Harie,
take a look oss note 505700 -LBWE: New update methods as of PI 2002.1 and 500426 - BW extraction SD: alternatives to V3 updating
hope this helps.
505700
Symptom
Up to and including PI 2001.2 or PI-A 2001.2, only the "Serialized V3 update" update method was used for all applications of the logistics extract structures Customizing Cockpit. As a result of the new plug-in, three new update methods are now also available for each application.
The "Serialized V3 update" update method is no longer offered as of PI 2003.1 or PI-A 2003.1. Between installing PI 2002.1 or PI-A 2002.1 and installing PI 2003.1 or PI-A 2003.1, you should therefore switch to one of these new methods in all applications offering alternative update methods.
Rather than describing an error, this note helps you make the right selection of update methods for the applications relating to the logistics extract structures Customizing Cockpit.
Read this note carefully and in particular, refer to the essential notes required for some applications when using the new update methods.
You will also find more detailed information on the SAP Service Marketplace at: http://service.sap.com/~sapidb/011000358700005772172002
Or:
http://service.sap.com/BW > SAP BW InfoIndex > Delta Handling > New Update Methods in Logistics Extraction with PI2002.1 2.0x/3.0x (ppt)
Other terms
V3 update, V3, serialization, TMCEXUPD
Reason and Prerequisites
New design
Solution
1. Why should I no longer use the "Serialized V3 update" as of PI 2002.1 or PI-A 2002.1?
The following restrictions and problems with the "serialized V3 update" resulted in alternative update methods being provided with the new plug-in and the "serialized V3 update" update method no longer being provided with an offset of 2 plug-in releases.
a) If, in an R/3 System, several users who are logged on in different languages enter documents in an application, the V3 collective run only ever processes the update entries for one language during a process call. Subsequently, a process call is automatically started for the update entries from the documents that were entered in the next language. During the serialized V3 update, only update entries that were generated in direct chronological order and with the same logon language can therefore be processed. If the language in the sequence of the update entries changes, the V3 collective update process is terminated and then restarted with the new language.
For every restart, the VBHDR update table is read sequentially on the database. If the update tables contain a very high number of entries, it may require so much time to process the update data that more new update records are simultaneously generated than the number of records being processed.
b) The serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document has not been changed twice in one second.
c) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
d) In addition, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if an error did not occur beforehand in the U2 update, since the V3 update only processes update data, for which the U2 update is successfully processed.
2. New "direct delta" update method:
With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues.
If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
3. The new "queued delta" update method:
With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP, provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
In the following cases, the extraction queues should never contain any data:
- Importing an R/3 Support Package
- Performing an R/3 upgrade
- Importing a plug-in Support Packages
- Executing a plug-in upgrade
For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.
b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
4. The new "unserialized V3 update" update method:
With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
However, unlike the current default values (serialized V3 update), the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
5. Other essential points to consider:
a) If you want to select a new update method in application 02 (Purchasing), it is IMPERATIVE that you implement note 500736. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBV302 report.
b) If you want to select a new update method in application 03 (Inventory Management), it is IMPERATIVE that you implement note 486784. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV303 report.
c) If you want to select a new update method in application 04 (Production Planning and Control), it is IMPERATIVE that you implement note 491382. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV304 report.
d) If you want to select a new update method in application 45 (Agency Business), it is IMPERATIVE that you implement note 507357. Otherwise, even if you have selected another update method, the data will still be written to the V3 update. The update data can then no longer be processed using the RMBWV345 report.
e) If you want to change the update method of an application to "queued delta", we urgently recommended that you install the latest qRFC version. In this case, you must refer to note 438015.
f) If you use the new selection function in the logistics extract structures Customizing Cockpit in an application to change from the "Serialized V3" update method to the "direct delta" or "queued delta", you must make sure that there are no pending V3 updates for the applications concerned before importing the relevant correction in all affected systems. To check this, use transaction SA38 to run the RMCSBWCC report with one of the following extract structures in the relevant systems:
Application 02: MC02M_0HDR
Application 03: MC03BF0
Application 04: MC04PE0ARB
Application 05: MC05Q00ACT
Application 08: MC08TR0FKP
Application 11: MC11VA0HDR
Application 12: MC12VC0HDR
Application 13: MC13VD0HDR
Application 17: MC17I00ACT
Application 18: MC18I00ACT
Application 40: MC40RP0REV
Application 43: MC43RK0CAS
Application 44: MC44RB0REC
Application 45: MC45W_0HDR.
You can switch the update method if this report does return any information on open V3 updates. Of course, you must not post any documents in the affected application after checking with the report and until you import the relevant Customizing request. This procedure applies in particular to importing the relevant Customizing request into a production system.
Otherwise, the pending V3 updates are no longer processed. This processing is still feasible even after you import the Customizing request using the RSM13005 report. However, in this case, you can be sure that the serialization of data in the BW delta queues has not been preserved.
g) Early delta initialization in the logistics extraction:
As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
Regardless of the initialization procedure or update method selected, it is nevertheless necessary to stop any document postings for the affected application during a recompilation run in the OLTP (filling the setup tables).
500426
Symptom
With the BW extraction with the structures of the logistics extract structures customizing cockpit there is only V3 updating as an update method up to plug-in release PI-2001.2.
To make every possible effort to ensure the transfer of document postings to BW in the correct sequence the parameter "SERIAL" was added to the V3 collective update (refer also to note 385099). If this parameter is set at the start of the V3 collective update, the update data is read and processed by the database in the sequence of its creation time.
However, this procedure gives rise to the following major performance problem:
If documents are entered in an application in an R/3 System by several users that are logged on in different languages, the V3 collective run will only ever process the update entries for one language in a process call. A process call is then started automatically for the update entries of the documents which were entered in the next language. Accordingly, during the serialized V3 update only update entries which were generated in direct chronological sequence and with the same logon language can ever be processed. If the language changes in the sequence of the update entries, the V3 collective update process is terminated and restarted with the new language.
During every restart, the update table VBHDR is read sequentially on the database. If there are very many entries in the update tables, this can cause the processing of the update data taking so much time that more new update records are generated simultaneously than are processed.
Furthermore, the serialization is not 100% guaranteed in all scenarios when the V3 update is used, as described also in note 384211.
From plug-in PI 2002.1 the option is offered for the most important applications of the logistics extract structures customizing cockpit of selecting between several alternative update methods.
The serialized V3 update is no longer provided from plug-in PI-2003.1.
The modification provided here enables you to use the new update methods for the applications 11, 12 and 13 as early as from patch 5 of PI 2001.2 or PI-A 2001.2.
The following update methods are offered:
direct delta (update mode A):
With this update mode the extraction data is transferred directly into the BW delta queues with every document posting. Every document posting with delta extraction becomes exactly one LUW in the corresponding BW delta queues.
If you use this method it is therefore no longer necessary to regularly schedule a job to transfer the data to the BW delta queues. Otherwise there will be a substantial increase in the number of LUWs per DataSource in the BW delta queues since, unlike previously, with V3 updating the deltas of many documents are grouped together to form an LUW in the BW delta queues.
Furthermore you should note when using this update mode that during delta initialization in an application, from the start of the recompilation run in the OLTP no document postings may be made until all delta Init requests have been updated successfully in BW. Otherwise data in documents posted in the interim will be irretrievably lost.
queued delta (Update mode B):
With this update mode the extraction data of the affected application is collected in an 'extraction queue' instead of in the update dataand can be transferred via an update collective run into the BW delta queues, as is already the case during V3 updating.
For each DataSource,1000 delta extractions are summarized by documents of the application to form an LUW in the BW delta queues.
If you are using this method it is thus also necessary to regularly schedule a job for transferring the data to the BW delta queues. This scheduling is carried out with the same report which is used when you use the V3 updating (RMBWV311, RMBWV312 or RMBWV313). You are recommended to schedule the job on an hourly basis in normal operation - that is following the successful delta initialization.
In the case of a delta initialization the document postings of the affected application can be included again after the successful execution of the recompilation run in the OLTP (OLI7BW, OLI8BW or OLI9BW) if you ensure that the update collective run is not started before all delta Init requests are updated successfully in BW.
In the posting-free phase during the recompilation run in the OLTP - as previously - the update collective run should be be run once successfully to ensure that there is no old delta extraction data in the extraction queues during the reinsertion of the document posting.
Using transaction SMQ1 and the queue names MCEX11, MCEX12 or MCEX13 you can get an overview of the data in the extraction queues.
unserialized V3 update (update mode C):
With this update mode the extraction data of the affected application is written to the update tables as before with the aid of a V3 update module and kept there until the data is read and processed by an update collective run.
However, unlike the current default values (serialized V3 update), in the update collective run the data is read and transferred to the BW delta queues without taking into account the sequence from the update tables. This is why the performance problem described above does not arise in this case.
This method should only be used if, due to the design of the cubes or ODS objects in the BW system, it does not matter whether the data is transferred to BW in exactly the same sequence in which it was generated in the OLTP System.
Other terms
V3 update
Reason and Prerequisites
Additional desired functions.
Solution
If you already want to use one of the above-described new update methods in the applications 11, 12 or 13 with PI 2001.2 or PI-A 2001.2, you can do this with the corrections given here. However, it is vital that you bear in mind the following points:
1. The corrections described here consist ofa modification which is not included in any PI Support Package. Check whether the described corrections are necessary. When you import a PI Support Package, parts of these corrections may be overwritten. When importing the PI Support Package ensure that you have got all of these corrections (SPAM/SPAU).
2. Only copy these modifications in consultation with SAP logistics extraction development.
3. The corrections presented here should only ever be regarded as an interim solution. The functions are only fully available with PI 2002.1 and PI-A 2002.1. You should also consider the option of upgrading soon to PI 2002.1 or PI-A 2002.1.
Note also that if the update methods of the applications 11, 12 and 13 are changed prematurely, other applications can still only offer the serialized V3 update. The performance problem described above continues to apply to these applications. It should, however, be significantly reduced by the absence of the modules of applications 11, 12 and 13.
4. The corrections described here necessitate the importing of Support Package 5 of PI 2001.2 or PI-A 2001.2. The corrections described here are not possible in a lower plug-in release or Support Package status since the functions of the new update methods are not available.
5. If you want to change the update method of an application to "queued delta", you are strongly recommended to first install the most current qRFC version. Refer to note 438015.
6. If you use the corrections below to change from the update method "Serialized V3" to "Direct delta" or "queued delta" in an application, you must ensure that before the corresponding corrections are imported there are no more open V3 updates for the corresponding applications in all affected systems. To check this, you can execute the report RMCSBWCC in the corresponding systems with transaction SA38 with one of the following extract structures:
Application 11: MC11VA0HDR
Application 12: MC12VC0HDR
Application 13: MC13VD0HDR.
The change is possible if you are not referred to open V3 updates. Of course, no document postings should be made in the affected application after the check with the report until the transfer of the corrections. This procedure applies in particular to the importing of the corrections into a production system.
7. If you are already using the update mode "queued delta" with one of the applications 11, 12 or 13 with the corrections stored here before PI 2002.1 and if you want to make changes to the extract structures in this phase via the cockpit, you should ensure that there is no data in the extraction queues before you execute these changes in the affected systems. In particular this applies to the transportation of changes into a production system. In this case it is not sufficient to execute the check report RMCSBWCC recommended in the cockpit and to eliminate the problem areas specified there.
Below we describe how you can check and ensure this condition.
8. When you import PI 2002.1 the changes made here will always be ineffective and you will get the update method "serialized V3" again as the preset update method.
If you have already changed to a different update method in advance in one of the applications 11, 12 or 13 via the corrections stored here, you must consider the following points during the plug-in upgrade to PI 2002.1 or PI-A 2002.1:
a) Before the upgrade you must ensure that there is no more data in the extraction queues MCEX11, MCEX12 and MCEX13. Otherwise it may no longer be possible to process the data, which may have to be deleted from the queues, due to an extract structure enhancement with the new plug-in. You can do this by starting the collective update report (RMBWV311, RMBWV312 or RMBWV313) and by subsequently checking the extraction queues using transaction SMQ1.
b) After the upgrade you must ensure that before the inclusion of new document postings, the update method of the corresponding application used in advance by the corrections specified here is also set in the cockpit of the logistics extraction (LBWE), and that this setting is transported into all clients of the affected systems.
Note in this context that the corrections specified here change the update method so that it is client-independent. The new functions in the cockpit of the logistics extraction from PI 2002.1 or PI-A 2002.1 then allow the client-specific selection of the update methods.
9. If you want to use the update method "direct delta" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
10. If you want to use the update method "direct delta" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
11. If you want to use the update method "direct delta" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000373868" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
12. If you want to use the update method "queued delta" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
13. If you want to use the update method "queued delta" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
14. If you want to use the update method "queued delta" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380083" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
15. If you want to use the update method "unserialized V3 update" in application 11 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX11TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
16. If you want to use the update method "unserialized V3 update" in application 12 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX12TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2).
17. If you want to use the update method "unserialized V3 update" in application 13 instead of the serialized V3 update, copy the changes specified in the correction instructions "0120061532 0000380084" given below for the include MCEX13TOP using the ABAP editor (transaction SE38) (these guidelines can be used both for PI 2001.2 and PI-A 2001.2). -
Installing FLash player (and Creative cloud)
I am having trouble with Flash player and creative cloud. Most recently I have tried umpteen times to install Flash player and it wont work. I have run through uninstalling it. re installing it. ensuring it is enabled. and nothing. i have established that i DO have the current version on my computer through the \app\ through your website...its the 11.9 version. but when I try to use FB to upload photos, it says i have to install the latest version of flash.
I have also had the same issue with CC. I have a subscription and i have downloaded the desk top app, but I cannot see or access it. I have it listed in my control panel, under programs...but cannot see it anywhere else.
What else can I do? I am so frustrrated. mostly with these adobe products - they just dont seem to 'stay' on my comp. LR and PS both work - downnloaded from CC...but nothing else really!?
Thanks so much
JenJendie wrote:
I am having trouble with Flash player and creative cloud. Most recently I have tried umpteen times to install Flash player and it wont work. I have run through uninstalling it. re installing it. ensuring it is enabled. and nothing. i have established that i DO have the current version on my computer through the \app\ through your website...its the 11.9 version. but when I try to use FB to upload photos, it says i have to install the latest version of flash.
This is a known problem with Internet Explorer 11 (which I can only assume you're using because this is where the FB problems occur), which Microsoft has been aware of since October 18 when they released their latest "untested" browser. The pages can't recognize the browser, so they don't recognize any of the plugins, like Flash Player. So far, Microsoft has made NO indication that they have any plan to fix it soon.
Microsoft's recommendation is to use Compatibility View for affected pages, and "pretend" you're using an different browser. Trouble with that is it has seen limited success at best, and you have to individually enable it for EVERY page that has problems.
I'm not big on "pretending" so I recommend actually using another browser.
Firefox (from Mozilla)
Opera (from Opera)
Safari (from Apple)
Chrome (from Google)
ANY of those will work where IE11 won't, with the Flash Player Plug-in (For all other browsers), and Chrome doesn't even need that because it has its own Flash Player plugin built in. -
How do I remove the DRM-Protection from tracks so that I can play them on my DJay 2 app. I've followed the directions for removal and it's not working...
Will I have to purchase these tracks again?Apple's official advice is here... HT2905 - How to find and remove duplicate items in your iTunes library. It is a manual process and the article fails to explain some of the potential pitfalls.
Use Shift > View > Show Exact Duplicate Items to display duplicates as this is normally a more useful selection. You need to manually select all but one of each group of identical tracks to remove. Sorting the list by Date Added may make it easier to select the appropriate tracks, however this works best when performed immediately after the dupes have been created. If you have multiple entries in iTunes connected to the same file on the hard drive then don't send to the recycle bin. This can happen, for example, if you start iTunes with a disconnected external drive, then connect it, reimport from your media folder, then restart iTunes.
Use my DeDuper script if you're not sure, don't want to do it by hand, or want to preserve ratings, play counts and playlist membership. See this thread for background. Please take note of the warning to backup your library before deduping, whether you do so by hand or using my script, in case something goes wrong.
(If you don't see the menu bar press ALT to show it temporarily or CTRL+B to keep it displayed)
tt2
Maybe you are looking for
-
Delivery Schedule for Service Item
Hi folks! Can anyone guide me, how to create delivery schedule for Service item in Purchase Order. Regards.
-
Yesterday I decided to finally update my iphone 4S to the latest operating system 7. It asked me for a password when upgrading but now does not recognize the password and will not let me in. FRUSTRATED. What do i do????
-
IOS installed apps showing as not installed in App Store
This problem seemed to start when I was unable to pay my Apple bill. As is usual, the App Store wouldn't allow me to download apps and updates but I signed out my account and then back in and all of my pending app updates disappeared and in the Purch
-
Drives mapped via GPO, NET USE shows mapping but doesn't show up in Explorer - Win 8.1
Fresh install of Windows Enterprise 8.1 Connected PC to domain, logged in, drive mapping worked as it should. Rebooted a few times after installing software that I normally install on my computers (from the same sources/locally from my file server, e
-
Sqlpackage.exe Azure export error started few days ago
I was using this for a couple of months and suddenly since few days, I can't do it anymore sqlpackage.exe /a:Export /ssn:xxxxxxx.database.windows.net /sdn:"xxx" /su:"xxx" /sp:"xxxxxxxxxxxxxx" /tf:"xxxxxx.bacpac" Connecting to database 'xxxxx' on serv