Difference between KT6 Delta and KT6V ?

What is the difference between the 2 boards ? I ordered a KT6V board from E-buyer in the UK and received a KT6 Delta one which is slightly more expensive. Am I right in saying that the KT6 Delta supports IDE Raid ?

KT6 delta has a different audio codec and NIC
KT6v has realtek audio codec and NIC
KT6 delta has Cmedia codec and broadcom NIC
As for RAID, They all have serial raid,
KT6V - SR = serial raid
KT6v - LSR = lan, serial raid
kt6 delta = LSR = lan, serial raid
kt6 delta = FISR = Firewire, lan, serial raid
kt6 delta = FIS2R = Firewire,lan, serial raid + promise serial raid

Similar Messages

What is difference between additive delta and new status for change record

Hi Experts
Can any one explain me about the difference between additive delta and new status for change record with example
if any one has a document please post it iam thank full to u
thanks
Ahmed
Please search the forum before posting a thread
Edited by: Pravender on Feb 12, 2012 1:54 PM

Hi
Additive delta --- We will get the changed quantity.
say suppose you have sales order and quantity like 1111 30 which is loaded to cube(BW).
now same record qty has changed from 30 to 40. As we have additive delta, we will get new record as 1111 10.
new status for change record: This is same as like After image delta type in standard SAP data sources. for every change in record you should have new record.
say if you have any number which will be generated by system for new/changed record, then you can use this.
You can use this option when delta option set to "numeric pointer"
Regards,
Venkatesh

Difference between RDA delta and normal Delta

Hi All
I have some doubts regarding the RDA [Real Time data Acquisition] process I am aware that RDA enables us to get the data every minute with help of Daemon process.What is the diffrence between th delta mechanism that is followed in RDa and normal dataflow.
Thanks & Regards
Santosh Varada

Hi Varda ,
RDA is Real Time Data Acquisition . In this We can retrieve Live data . While using Normal DTP We can t pull live data
For example :- Today We have Create a 50 orders . This 50 order information pulled after completion of sales order creation . we can t see live . But RDA process pulled the data at the point of sales order creation it self ,It support only Stranded DSO .It will use Some industries like FMCG.Retail,banking sector they want to know current data information from BI Side then RDA.
Please Find below link for Demonstration of Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00db64ee-82f0-2b10-01b0-fe9543dc227e?quicklink=index&overridelayout=true.
Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f704bd-b6e8-2c10-569e-d726784388ce?quicklink=index&overridelayout=true
Thanks & Regards,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://www.bluemarlinsys.com/
http://bluemarlinsys.com/bi

Difference between Direct delta and delta Queue

Hi,
1.ease explain me the concept of Direct delta and delta queue in LO extraction
2.Why set up tables are used and initially why the data is deleted for th setup tables.
3.Please explain me the LO extraction with an example.
Thanks
Alok

Dear Aloka,
1.
Direct delta:
transactional data or application posting will be directly available in the delta queue table with out any intermediate tables. then that data will be extracted from r/3 to bw.
Each document posting is directly transferred into the BW delta queue
each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Less monitoring overhead of update data or extraction queue
Cons:
Not suitable for environments with high number of document changes
Setup and delta initialization have to be executed successfully before document postings are resumed
V1 is more heavily burdened
Queued delta:
first the data posting will available in the extraction queue table. then there periodic job run take that data to queued delta table.
Extraction data is collected for the affected application in an extraction queue
Collective run as usual for transferring data into the BW delta queue
Transaction postings lead to:
1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Suitable for environments with high number of document changes
Writing to extraction queue is within V1-update: this ensures correct serialization
Downtime is reduced to running the setup
Cons:
V1 is more heavily burdened compared to V3
Administrative overhead of extraction queue
2.
Setup tables are used for Full/Initial Update.
Instead of pulling data from DB Tables directly, we r filling Setup tables and extracting data from the Setup tables, which dont have performance impact on DB Tables.
Setup tables are application specific.
It is cautious method to delete Setup tables before filling it for a specific DataSource.
3.
Re: LO-Cockpit V1 and V2 update
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Regards,
Ram.

Differences between FULL, DELTA and REPEAT DELTAs

Please distinguish Full, Delta and Repeat Delta loading from R/3 to BW/BI and give some example for their uses
Your answer would be appreciated.
Cheers,
Nari

please search in SDN before posting Novice questions

Diff between additive delt and delta

Hi all,
what is the difference between additive delta and delta?
sridevi

Hi,
the records which are generated after the last update is called delta.
In some datasources the changed records are stored with before and after images.
But some datasoures the changed records are stored with only new image we call it as additive delta.
regards,
haritha

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

What is the difference between qued delta update and serialized delta upda

what is the difference between qued delta update and serialized delta update?

Hi Ks Reddy,
Queued Delta:
In case of Queued delta LUW's are posted to Extractor Queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. Generally we prefer Queued Delta as it maintain the Extractor Log which us to handle the LUW's which are missed.
Direct Delta:
In case of Direct Delta LUW's are directly posted to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW's are directly posted to Delta Queue (RSA7) the application is kept waiting untill all the enhancement code is executed.
Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
https://websmp102.sap-ag.de/~sapdownload/011000358700007535452002E/HOWTOCREATEGENERICDELTA.PDF (need id)
http://help.sap.com/saphelp_bw33/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Business Intelligence Performance Tuning [original link is broken]
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
How to load data
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/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
Delta Types and methods;&#57245;
Hope this helps.
****Assign Points if Helpful*****
Regards,
Ravikanth

Gereral differences between 4.7 and ECC 6.0 from FI/CO view

Hi Guys
Can any one tell me key differences between 4.7 and ECC 6.0 from FI/CO view.
In interview what i must tell?
Thank you.

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/]
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, 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.
Regards,
Ajit

Difference between Queued Delta vs Unserialized V3 update

Dear Experts,
I am using 2LIS_02_ITM datasource.
PO is created using a program.
The next step in the program, it can change a field in the PO depending on logic, using a abap command 'update'.
Sometimes, this change is not captured in the delta queue, it seems.
why i say this is the PO shows the field value but BI delta load does not.
It is using Queued Delta now.
I am wondering would changing to Unserialised V3 update help solve the problem since when documents are posted it writes to update table and from there it is processed to delta queue using collection run.
What is the difference between writing to the Extraction Queue compared to writing to Update table? Will using the update table mean abap command 'update' changes to a PO document will be captured ?
regards
Pascal

Hi Pascal ,
The basic difference between these two is how the delta moves from R/3 to BW side .
When we do any transaction in R/3, first the data goes into a Temporary table called V1 Update and from here data moves to Final table (Application)say VBPA,VBRK etc. this is called V2 Update.
After this we have queued delta or Unserialized V3 update at between R/3 and BW side .
1. Queued Delta
At V1 update data goes to "Extraction Queue" (irrespective of V2 happen or not).Then when we run a "Extraction Run" program it pulls the data from Extraction Queue and sends it to DELTA Queue table (called V3 Update) from where it is transported to BW when a delta request is generated.
So if something is saved to application table, also get saved to Extraction Queue ( this is difference with direct delta) and you have to schedule a V3 job to move the data to the delta queue periodically .
2. Unserialized V3 Update
In this case when data is generated V1 update takes place and data moves to another table known "Update Table" but only after V2 takes palce. So it waits for V2 update to happen and does not miss any record.After that from "Update Table" data goes to Delta Queue when update collection Run is executed and then it goes to BW when Delta upload Request is generated.
The difference here is the sequence of document data in the BW delta queue that may be different from posting sequence of data so it is good when sequence of data does not matter due to the design of the data targets in BW.
ex: Inventory Management.
Hope this will throw some light on the concept you want to understand.
Regards,
Jaya

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 SRM 7 and SRM 5 Workflow

Hello all
what is the difference between SRM 7 and SRM 5 Workflow.
Reagrds
Marco

Dear Prakash,
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/
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, 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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Getting difference between GMT time and Local time

Folks,
I am trying to get difference between gmt time and local time for Korea time zone.
which should be 9 hours.
Instead of 9, I am getting 15 hours diff.
What am I doing wrong?
Here's what I did to test it:
First I set the system (Windows XP) time zone to Soul (Korea GMT+9hours) time zone.
Then I ran the following program, and I got 15 hour diff, not 9.
Thank you in advance!
import java.util.*;
public class Using_GregorianCalendar
     public static void main(String args[])
          Using_GregorianCalendar ugc = new Using_GregorianCalendar();
          ugc.getTimeDiff();
     public void getTimeDiff()
          Calendar cal = new GregorianCalendar(TimeZone.getTimeZone("GMT"));
          Calendar cal1 = new GregorianCalendar(cal.get(Calendar.YEAR),
                                       cal.get(Calendar.MONTH),
                                       cal.get(Calendar.DATE),
                                       cal.get(Calendar.HOUR_OF_DAY),
                                       cal.get(Calendar.MINUTE),
                                                  cal.get(Calendar.SECOND));
        int gmtHour          = cal.get(Calendar.HOUR); //(Calendar.HOUR_OF_DAY);
        int gmtHourOfDay = cal.get(Calendar.HOUR_OF_DAY);
        int gmtMonth        = cal.get(Calendar.MONTH);
        int gmtYear          = cal.get(Calendar.YEAR);
        int gmtMinute       = cal.get(Calendar.MINUTE);
        int gmtSecond     =   cal.get(Calendar.SECOND);
        int gmtDate         = cal.get(Calendar.DATE);
        Calendar localCal = Calendar.getInstance();
        int localHourOfDay = localCal.get(Calendar.HOUR_OF_DAY);
        int timeDiff = (localHourOfDay - gmtHourOfDay);
          //Korea time is GMT + 9 hours so I should get a difference of 9
          //why am I getting difference of 15?
             System.out.println("************** in getTimeDiff() **********************");
          System.out.println("gmtDate: "+gmtDate);
          System.out.println("gmtHour: "+gmtHour);
          System.out.println("gmtHourOfDay: "+gmtHourOfDay);
          System.out.println("localHourOfDay: "+localHourOfDay);
          System.out.println("timeDiff: "+timeDiff);
          System.out.println("**********************************************************");
     }//getTimeDiff()
}//class Using_GregorianCalendar
/*              here's the output of this program:
     ************** in getTimeInGMT() **********************
     gmtDate: 14
     gmtHour: 6
     gmtHourOfDay: 18
     localHourOfDay: 3
     timeDiff: -15
*/

DrClap wrote:
sabre150 wrote:
Nearly correct since the Daylight saving may or may not be in effect which does depend on the date...I would simplify that to this:
TimeZone korea = TimeZone.getTimeZone("Asia/Seoul");
long delta = korea.getOffset(new Date().getTime());
System.out.println(delta / (1000.0 * 60 * 60));That's assuming that the OP really meant UTC when he/she said "GMT". Most people don't realize there's a distinction and that Java's timezones are all based relative to UTC.I suspect you are right in assuming that the OP want UTC and not GMT. I figured it was better to illustrate that the method can be used for getting the time difference between any two TimeZones.

Difference between 4.7 and ECC 5/6

Hi Friends,
I am ABAP developer and would like to know the differences between 4.7 and ECC 5.0 and ECC 6.0 from a techincal perspective. I appreciate if you differentiate between each of them or 4.7 and ECC 5.0.
Regards
Prakash

Dear Prakash,
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/
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, 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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Difference between 4.7 and ECC6

Hi
Could any one explain me the difference between 4.7 and ECC6
Regards
Uday

Hi,
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/
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, 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.
Hope this helps you.
Regards,
Rakesh

Difference between KT6 Delta and KT6V ?

Similar Messages

Maybe you are looking for