Difference Between Update Queue and Delta Queue

Hi Experts ,
Could u brief out the difference between Extraction Queue , Update Queue and Delta Queue ?

Hi
a) Serialized V3 Update(If you set this as your delta mode then data will populated into extraction queue tables)
This is the conventional update method in which the document data is collected in the sequence of attachment and transferred to BW by batch job.The sequence of the transfer does not always match the sequence in which the data was created.
b) Queued Delta(If you set this as your delta mode then data will be populated into update queue tables)
In this mode, extraction data is collected from document postings in an extraction queue from which the data is transferred into the BW delta queue using a periodic collective run. The transfer sequence is the same as the sequence in which the data was created
Delta queue is a table which collects data from extraction queue/update queue tables based on the frequency you have set(daily/hourly etc)..from these tables we will get delta records to bw with infopackage delta run..
Hope it helps
Thanks
Teja

Similar Messages

Difference between Plannning Buffer and Delta Buffer in IP

Hi,
Can anyone please explain the difference between planning aand delta buffer in IP, with an example?
Regards,
Deepti

Hi,
Planning buffer is the data that is been retrived from the cube or the master data for the first time when you open the application for the first time.Now all the planning functions will read the data from this buffer and even writes back all the changes in the record to the same buffer.The planning function refers to the planning buffer data; it modifies the data and writes it back to the planning buffer.Every time a detail application is executed, the system first checks whether the requested data already exists in the planning buffer. If it does, the system accesses the version of data available in the planning buffer. If the data is not already in the buffer, the system reads it either from:infocube or master data.
Now with delta buffer ,once the data is available in the planning buffer and you made some changes to it only the delta part of the records will be written back to the planning buffer as well as it is reffered as delta buffer and the same delta buffer will be written back to the cube not the entire planning buffer.
For example:
If the query has to read the record as follows then for the first time :
PROJECT,WBS,COST ELEMENT,FISCPER,QTY,CPU,AMOUNT.
P1, WBS1, CE1, 010.2009, 50, 100, 5000
sO IN PLANNING BUFFER u 'll be having the above mentioned record and the above record will be called as planning buffer record.Now if you make some changes to the record through planning function or manually then :
P1, WBS1, CE1, 010.2009, 100, 100, 10000
So now the above new record will be posted as delta buffer as:
P1, WBS1, CE1, 010.2009, 50, 100, 5000
So now the planning buffer will have the original record as well as the delta buffer.So when we save the data the delta buffer is written to the cube but when we retrive again from the planning buffer the old record and the delta buffer will be aggregated and displayed.
Hope it is clear now.
Regards,
Indu

Diff between update queue and delta queue

hi all
can anyone tell me wats is the diff between update queue and delta queue? wats is delta queue and update queue?
wats are the possible system generated errors and custom generated errors?
Thanks,
Shreya

Hi Shreya,
Update queue(LBWQ) comes into the picture when you choose Queued Delta for the Datasource. the data first comes to the Update queue and than goes to the Delta queue, however if you have choosen Direct Delta than the posted record will directly go to the Delta queue(RSA7).
Here is the URLS for Roberto's weblog to understand the whole LO-Extraction process.
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Hope it helps you!!!!
Regards,
Amit
Pls do not forget to assign points, if helpful.

Hi I have the old photo shop elements 10 on my computer and want to update and was wondering what the differences between photoshop, lightroom and photoshop elements are? Also when I upgrade does it have to be with a monthly membership or can I just purch

Hi I have the old photo shop elements 10 on my computer and want to update and was wondering what the differences between photoshop, lightroom and photoshop elements are?
Also when I upgrade does it have to be with a monthly membership or can I just purchase the product out right like you use to be able?

You cannot "update" from what you have to any of the applications you mention. It will have to be a straight purchase or subscription at full price.
Photoshop is a professional level application that makes no apologies for its very long and steep learning curve.
Lightroom is all about volume, and very light editing.
The Photoshop Elements forum is at:
https://forums.adobe.com/community/photoshop_elements/content
Remember, you are not addressing Adobe here in the user forums. You are requesting help from volunteers users just like you who give their time free of charge. No one has any obligation to answer your questions.
I do not know where there is such a comparison table as you seek, but someone else might, or you can google.

AppID during application update and Difference between app id and product id

Hi
I understand once a app is in store it has a associated Appid. How does this differs from the product id?
During each app update does the product id's should be same?
or during the store certification process will the appid and the product ids be mapped?
How does the product id and App id differ if this is not the case?
Can you provide some article which actually explains what is the difference between XAP uploaded and xap after certification?
Regards
Varun
Varun Ravindranath Please 'Mark as Answer' if my post answers your question and 'Vote as Helpful' if it helps you.

Hi
In that case the dev account from which the update is done will have the unique id or appid and the appid or the product id mapping will be always done by the store certification process.
I'm not clear on this part whether the developer who does the update of the app should update the id or the process which does the certification of the app as an update will update automatically do it?.
Regards
varun
Varun Ravindranath Please 'Mark as Answer' if my post answers your question and 'Vote as Helpful' if it helps you.

Re: The difference between update() and doFinal() in ClassCipher

Hi Guys,
I found this topic,
The difference between update() and doFinal() in ClassCipher
during a Google Search. I need your help, because I'm working on a project for an university exam.
It's about a Client FTP that sends and received files with the content crypted.
I'm using DES Encryption with "DES/CBC/PKCS5Padding".
I have this doubt: when it's correct to uso the doFinal method? At the last block of the file, or after it? (for encryption)
And during the decryption, how can I use the result of the doFinal operation?

Reposting with {code} tags
capagira87 wrote:
Ok these are the functions:
public void CodificaInvia (String cd, String filename, SecretKey Key) // it opens, codes and sends to the server the content of the file 512 bytes per time
int returncode=0;
Socket DataSock = null;
FileInputStream fis = null;
byte [] text = null;
try {
DataSock = new Socket (servAddress,22);
ObjectInputStream cin = new ObjectInputStream (DataSock.getInputStream());
ObjectOutputStream out = new ObjectOutputStream (DataSock.getOutputStream());
byte[] iv = new byte[] { (byte) 0x8E, 0x12, 0x39, (byte) 0x9C, 0x07, 0x72, 0x6F, 0x5A };
AlgorithmParameterSpec paramSpec = new IvParameterSpec(iv);
Cipher cipher = Cipher.getInstance("DES/CBC/PKCS5Padding");
cipher.init(Cipher.ENCRYPT_MODE, Key, paramSpec);
fis = new FileInputStream (cd+File.separator+filename);
int size = fis.available();
if ((size%8)==0)
text = new byte [size];
} else {
do {
size++;
} while ((size%8)!=0);
text = new byte [size];
fis.read(text,0,fis.available());
byte [] ciphertext = cipher.doFinal(text);
out.writeInt(ciphertext.length);
int numblock = ciphertext.length/512;
int resto = ciphertext.length%512;
out.writeInt(numblock);
out.writeInt(resto);
byte [] tempblock = new byte [512];
for (int conta=0; conta<numblock; conta++)
for (int i=0; i<512; i++)
tempblock=ciphertext[(conta*512)+i];
out.write(tempblock);
out.flush();
if (resto > 0) // this block works if the file size is not multiple of 512
java.util.Arrays.fill (tempblock, (byte) 0);
int h= numblock*512;
for (int i=0; i<resto; i++)
tempblock[i]=ciphertext[h+i];
out.write (tempblock);
out.flush();
System.out.println ("OK!");
} catch (Exception e)
e.printStackTrace();
public void RicezioneDecodifica (String filename, SecretKey Key) // in this function I receive the file blocks, I decrpyt them and I save the decrypted text into a file
Socket DataSock = null;
byte [] buffer=null; // it saves the received data
String Plaintext = new String (); // it saves the deciphered text
try {
ServerSocket ss2 = new ServerSocket (TRANSMISSION_PORT);
DataSock = ss2.accept();
ObjectOutputStream out = new ObjectOutputStream (DataSock.getOutputStream());
ObjectInputStream cin = new ObjectInputStream (DataSock.getInputStream());
byte[] iv = new byte[] { (byte) 0x8E, 0x12, 0x39, (byte) 0x9C, 0x07, 0x72, 0x6F, 0x5A };
AlgorithmParameterSpec paramSpec = new IvParameterSpec(iv);
Cipher dcipher = Cipher.getInstance("DES/CBC/PKCS5Padding");
dcipher.init(Cipher.DECRYPT_MODE, Key, paramSpec);
int size = cin.readInt();
int numblock = cin.readInt();
int resto = cin.readInt();
if ((size%8)!=0)
do{
size++;
} while ((size%8)!=0);
int ByteLetti=0; // counter of read bytes
buffer = new byte [size];
for (int conta=0; conta<numblock; conta++)
int a=cin.available();
byte [] tempblock = new byte [a];
cin.read(tempblock, 0, a);
for (int i=0; i<a; i++)
buffer[ByteLetti+i]=tempblock[i];
ByteLetti=ByteLetti+a;
byte[] texttmp=dcipher.update(tempblock);
String tmp = new String (texttmp, "UTF8");
Plaintext=Plaintext+tmp;
if (resto>0)
int a = cin.available();
byte [] tempblock;
if ((a%8)>0)
do {
a++;
} while ((a%8)!=0);
tempblock = new byte [a];
cin.read(tempblock, 0, cin.available());
byte[] texttmp = dcipher.doFinal(tempblock);
String tmp = new String (texttmp, "UTF8");
Plaintext = Plaintext+tmp;
ObjectOutputStream oos = new ObjectOutputStream (new FileOutputStream (filename));
oos.writeChars(Plaintext);
oos.flush();
oos.close();
} catch (Exception e)
e.printStackTrace();

Is difference between update routine,start routine and transfer routine

Hi All,
What is difference between transfer routine and update routine.

Hi Venkat,
Routine is a set of ABAP code which is used to select a record or transform the field value at the time of loading the data.
Types of routines:
Tranfer Routines in Transfer Rules:
Start Routines in Transfer Rules:
Update Routines in Update Rules:
Start Routines in Update Rules:
Transfer/Update routine:
It's the set of ABAP code used in Transfer/Update rules. Transfer/Update routine is used to change the value of a particular field/object at the time of loading data.
Ex: Populate the amount/discount field by using Price and Quantity based on the given conditions.
Start Routine:
Start routine can be used in both Transfer Rules and Update Rules. Start routine is used to determine whether to load a particular record or not.
Ex: From the data related to the year 2005, we can select only the records which belong to a particular month or fiscal period.
Ultimately Transfer/Update routines are to update the value of a particular field. Start routines are used to select entire record.
You can get more details about routines at :
Routines
ROUTINES
Routines and Examples
Start Routines
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/60cecb1d-0a01-0010-8289-b14fd99062fa
take a look this doc for abap used in bw
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4493c4a6-0301-0010-62a2-efd6ded61e04
ABAP book that always mentioned :
http://cma.zdnet.com/book/abap/
assign points if useful ***
Regards
CSM Reddy

Difference between Generic extraction and Generic Delta

Hi Experts,
Pleasee give of some information below query:
1) Difference between Generic extraction and Generic Delta.
2) How to achieve Generic delta.
3) When we go for Generic delta instead of generic extraction.
Advance ThankU. Points vl be assigned.
Thanks,
Ragu.R

Hi,
Generic delta is the delta load done using Generic DS.
Generic extraction
Usage:
1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
How:
You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
Refer:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Generic Extraction via Function Module
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
thanks,
JituK

Difference between system debugging and update debugging

hai guru's can any one tell the difference between system debugging and update debugging
thanx in advance
afzal

hi,
System Debugging
If you set this option, the Debugger is also activated for system programs
(programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.
Update Debugging
Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger.
These function modules are therefore not included in debugging.
Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
For debugging tutorial:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://www.sapdevelopment.co.uk/tips/debug/debughome.htm
http://www.sap-basis-abap.com/sapab002.htm
<b>Reward points</b>
Regards

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Difference between 4.6 and ECC 6.0

Can anybody tell me what is the difference between 4.6 and ECC 6.0 related to SD Module.

Hi Sunil,
. Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, and QM.....
Click on Search
then it displays the Release Version and the Delta Functionality. Which can be downloaded to a word document if required.
And also check the release notes of ECC 6.0 in service.sap.com.
A2. When you are upgrading from 4.6C to ECC6
Nothing major, follow the same process you'd follow if you were updating PI service packs in R/3 or enhancing data sources. Empty queues in RSA7 and lbwq. Also empty setup tables through lbwg as the upgrade doesn't like it if these tables contain data. This is all on the R/3 side (although you empty RSA7 by running each delta TWICE in BW).
To transfer queues from lbwq to rsa7, execute jobs through LO cockpit (lbwe).
Some of your data sources could also be using sm13 instead of lbwq, so do check it out as well.
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't require solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Major difference is ECC6 is netwear product having WASJAVA+ABAP
secondly support unicode apart from this we have other diff. you can get form master guide from service.sap.com/instguides.
Please go through the link that is shown here and if there is any doubts then feel free to ask.
A3. Major difference is ECC6 is net weaver product having WASJAVA+ABAP
secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't required solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
A4. Refer sdn thread and make a small search where u can find lot of information Reg this
olution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Refer below and search for posts on this topic on sdn
There are so many differences between the version in different objects
I
These are the some of the settings that are differed in the two versions and in that two objects
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
Upgrade from 4.6c to 6.0 ECC
upgrade from 4.7 to ecc 6.0
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Difference between BW3.5 and BI 7.0 version

difference between BW3.5 and BI 7.0 version

Hi ,
Differences between BW 3.5 and BI 7.0
Major Differences between Sap Bw 3.5 & sapBI 7.0 version:
1. In Infosets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal !
5. Search functionality hass improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
7. The Data Warehousing Workbench replaces the Administrator Workbench.
8. Functional enhancements have been made for the DataStore object:
New type of DataStore object
Enhanced settings for performance optimization of DataStore objects.
9. The transformation replaces the transfer and update rules.
10. New authorization objects have been added
11. Remodeling of InfoProviders supports you in Information
Lifecycle Management.
12 The Data Source:
There is a new object concept for the Data Source.
Options for direct access to data have been enhanced.
From BI, remote activation of Data Sources is possible in SAP source systems.
13.There are functional changes to the Persistent Staging Area (PSA).
14.BI supports real-time data acquisition.
15 SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
a) Renamed ODS as DataStore.
b) Inclusion of Write-optmized DataStore which does not have any change log and the requests do need any activation
c) Unification of Transfer and Update rules
d) Introduction of "end routine" and "Expert Routine"
e) Push of XML data into BI system (into PSA) without Service API or Delta Queue
f) Intoduction of BI accelerator that significantly improves the performance.
g) Load through PSA has become a must. I am not too sure about this. It looks like we would not have the option to bypass the PSA Yes,
16. Load through PSA has become a mandatory. You can't skip this, and also there is no IDoc transfer method in BI 7.0. DTP (Data Transfer Process) replaced the Transfer and Update rules. Also in the Transformation now we can do "Start Routine, Expert Routine and End Routine". during data load.
New features in BI 7 compared to earlier versions:
i. New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition (RDA).
ii. Enhanced and Graphical transformation capabilities such as Drag and Relate options.
iii. One level of Transformation. This replaces the Transfer Rules and Update Rules
iv. Performance optimization includes new BI Accelerator feature.
v. User management (includes new concept for analysis authorizations) for more flexible BI end user authorizations.
Regards
KP

What is the Difference between AQ adpater and JMS adapter??

What is the Difference between AQ adpater and JMS adapter in BPEL11g??
In what scenarios we go for AQ and for what scenarios we go for JMS adapter???

Go for AQ when using Oracle Advanced Queueing (the database stuff).
Use JMS when using JMS (in memory of file queues)
hth,
Peter Paul

What is the difference between full checkpoint and incremental checkpoint?

What is the difference between full checkpoint and incremental checkpoint?
And what is checkpoint queue?
Can someone clarify these concepts?
Thanks!

Hi,
there are different types of checkpoints:
- Full checkpoint:
=> DBWR writes all dirty buffers from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- can be triggered by different events, like a logswitch, a manual checkpoint (alter system ..), a shutdown and so on
This is the setup point for SMON for a crash recovery.
- Partial checkpoint:
=> DBWR writes all dirty buffers of a singel tablespace from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- can e triggered by an ALTER TABLESPACE OFFLINE, ALTER TABLESPACE READ ONLY, ALTER TABLESPACE BEGIN BACKUP statement.
Incremental checkpoint:
number to all file headers and the controlfile.
-- can be triggered by different events, like a logswitch, a manual checkpoint (alter system ..), a shutdown and so on
- Partial checkpoint:
=> DBWR writes all dirty buffers of a single tablespace from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- frequency is determined by FAST_START_MTTR_TARGET parameter (new feature to Oracle 9i), with wich you can specify a time in seconds which SMON is allowed to take maximal for a Crash Recovery until the database must be open again.
Dapending on the system you have SMON must calculate the maximum number of Redolog-blocks which it can manage to recover in the specified number of seconds. It will then create so called incremental checkpoints which will be tracked in the so called checkpoint queue in memory.
FAST_START_MTTR_TARGET is auto-tuned in Oracle 10g and Oracle tries to manage (incremental) checkpoint in a fashion that a minimum of I/Os are caused and a minimum time for crash recovery is needed.
If you set LOG_CHECKPOINTS_TO_ALERT to TRUE you will find checkpoint information in the alertSID.log file. You will see FULL and INCREMENTAL checkpoints then.
Hope this clarifies your question,
Lutz Hartmann

Difference between ncConfigCANNet.vi and ncConfigCANObj.vi

What is the difference between ncConfigCANNet.vi and ncConfigCANObj.vi? What is a CAN Network Interface Object and a CAN Object? Can you give examples.
Thanks,
Peter

Hi,
    I am getting -1074388736 error code with ncConfigCANObj.vi for message ID 1155 i.e 0x483. But for ID1156 there is no error.
After this message I get the error code for all the other message(decreasing order)in the dbc file. Can somebody please help me.
It is very urgent.
The CAN Object Config Values are
Period                                                  100
Read Queue length                              0
Write Queue Length                             0
Receive Changes Only                       FALSE
Communication Type                        Transmit Data By Call
Transmit By Response                      FALSE
Data Length                                         8
Thanks,
Siva

Difference Between Update Queue and Delta Queue

Similar Messages

Maybe you are looking for