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.

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

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

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

Different between initial replication and delta replication

Hi,
What is different between initial replication and delta replication of the catalog to B2B?
Denis Khveshchenik

Initial replication will replicate the full catalog
Delta replication - The replication will be based on teh change pointer that have been updated, so only the items that have been changed since the last initial replication will be replicated. This should result in a quicker replication time.

Difference between standard dtp and direct access dtp

Hi,
Can anybody tell me the difference between standard DTP and Direct access DTP other than Help.sap.com.
Regards,
Devi

simple words.. Standard DTP needs to use for Physical data targets loading.
Direct Access DTP needs to use for virtual providers. you won't pull data into BI. it will directly retrive from DS while reporting .
Nagesh Ganisetti.
Assign points if it helps.

Difference between Direct activity allocation and internal activity allocat

Hello
I am pursuing SAP Management Accounting certification
Can somebody tell me what's the difference between direct activity allocation and internal activity allocation. Please give some example and also specifications as to cost element categorry, activity type, etc.
Asif
Moderator: Please, do not post certification queries. Regarding your issue, please, refer to help.sap.com

Hi,
Activity means e.g.. sales call, customer visit etc.
But service process means after you sale your product if some service related issue arrives then that is taken care by this transaction.
Inspire by rewarding.
Regards,
Nikhil

Difference between Batch input and Direct Input

Hi please tell me the difference between Batch Input and Direct Input in BDC?

hi aparna,
DIRECT INPUT
TO ENTER THE DATA INTO THE CORRESPONDING DATABASE TABLES DIRECTLY, THE SYSTEM CALLS A NUMBER OF FUNCTION MODULES THAT EXECUTE ANY NECESSARY CHECKS. IN CASE OF ERRORS, THE DIRECT INPUT TECHNIQUE PROVIDES A RESTART MECHANISM. HOWEVER, TO BE ABLE TO ACTIVATE THE RESTART MECHANISM, DIRECT INPUT PROGRAMS MUST BE EXECUTED IN THE BACKGROUND ONLY. DIRECT INPUT CHECKS THE DATA THOROUGHLY AND THEN UPDATES THE DATABASE DIRECTLY.
TO MAINTAIN AND STRAT THESE PROGRAMS, USE PGM RBMVSHOW OR THE TRANSACTION BMVO.
BATCH INPUT
TYPES SESSION METHOD, CALL TRANSACTION, DIRECT INPUT.
TO SAVE DATA IN THE BDCTAB, USE THE FIELDNAME BDC_OKCODE AND FIELD VALUE OF /11.
BDCDATA
THIS IS A STRUCTURE WHICH CONTAINS THE FOLLOWING FIELDS.
PROGRAM NAME OF TH MOD PROG ASSOCIATED WITH THE SCREEN. SET ONLY FOR THE FIRST RECORD OF THE SCREEN.
DYNPRO SCREEN NUMBER. ALSO SET ONLY FOR FIRST RECORD.
DYNBEGIN INDICATES THE FIRST RECORD OF THE SCREEN. SET X FOR FIRST RECORD OTHERWISE .
FNAM FIELD NAME.
FVAL VALUE FOR THE FIELD NAMED IN FNAM.
THE FIRST STEP IN BDC IS TO UPLOAD DATA FROM THE FLAT FILE OR SEQUENTIAL FILE TO THIS BDCTABLE.
SESSION METHOD
WE USE 3 FUNCTION MODULES IN THIS SESSION METHOD.
1) BDC_OPEN_GROUP
 USER NAME: USER NAME
 GROUP: NAME OF THE SESSION
 LOCK DATE: THE DATE ON WHICH YOU WANT TO PROCESS THE SESSION.
 KEEP: THIS PARAMETER IS PASSED AS X WHEN YOU WANT TO RETAIN SESSION AFTER PROCESSING IT OR TO DELETE IT AFTER PROCESSING.
THIS CREATES A SESSION
2) BDC_INSERT
 TCODE: TRANSACTION NAME
 DYNPROTAB: BDC DATA
THIS CREATES A SEESION AND DATA IS TRANSFERRED O SESSION.
3) BDC_CLOSE_GROUP THIS CLOSES THE BDC GROUP.
ONLY ONE SESSION CAN BE CREATED USING BDC_OPEN_GROUP. BUT MULTIPLE TRANSACTIONS CAN BE PROCESSED USING BDC_INSERT.
CALL TRANSACTION
CALL TRANSACTION <TCODE> USING <BDCTAB>
 MODE <A/N/E>
 UPDATE <S/A>
 MESSAGES INTO <MSGTAB>.
A ALL SCREEN MODE. ALL THE SCREEN OF THE TRANSACTION ARE DISPLAYED.
N NO SCREEN MODE. NO SCREEN IS DISPLAYED WHEN YOU EXECUTE THE TRANSACTION.
E ERROR SCREEN. IF THE SCREEN HAS ERROR RECORD, THEN THAT SCREEN WILL BE DISPLAYED.
S - IF YOU CHANGE DATA OF ONE TABLE THEN ALL THE RELATED TABLES GETS UPDATED. AND SY-SUBRC IS RETURNED I.E., SY-SUBRC IS RETURNED FOR ONCE AND ALL.
A - WHEN YOU CHANGE DATA OF ONE TABLE, THE SY-SUBRC IS RETURNED. AND THEN UPDATING OF OTHER AFFECTED TABLES TAKES PLACE. SO IF SYSTEM FAILS TO UPDATE OTHER TABLES, STILL SY-SUBRC RETURNED IS 0 (I.E., WHEN FIRST TABLE GETS UPDATED
WHEN YOU UPDATE DATABASE TABLE, OPERATION IS EITHER SUCCESSFUL OR UNSUCCESSFUL OR OPERATION IS SUCCESSFUL WITH SOME WARNING. THESE MESSAGES ARE STORED IN INTERNAL TABLE, WHICH YOU SPECIFY ALONG WITH MESSAGE STATEMENT. THIS INTERNAL TABLE SHOULD BE DECLARED LIKE BDCMSGCOLL, A STRUCTURE AVAILABLE IN ABAP/4. IT CONTAINS THE FOLLOWING FIELDS: TCODE, DYNAME, DYNUMB, MSGTYP, MSGID.
DIFFERENCE BETWEEN SESSION AND CALL TRANSACTION
 SESSION METHOD CALL TRANSACTION
1. DATA IS NOT UPDATED IN DATABASE TABLE UNLESS SESSION IS PROCESSED. IMMEDIATE UPDATION IN DATABASE TABLE.
2. NO SY-SUBRC IS RETURNED. SY-SUBRC IS RETURNED.
3. ERROR LOG IS CREATED FOR ERROR RECORDS. ERRORS NEED TO BE HANDLED EXPLICITLY
4. UPDATION IN DATABASE TABLE IS ALWAYS SYNCHRONOUS
 UPDATION IN DATABASE TABLE CAN BE SYNCHRONOUS OR ASYNCHRONOUS.
5. ASYNCHRONOUS PROCESSING SYNCHRONOUS PROCESSING
6. TRANSFERS DATA FOR SINGLE TRANSACTIONS TRANSFERS DATA FOR MULTIPLE TRANSACTIONS
ERROR HANDLING IN CALL TRANSACTION
1) CREATE AN INTERNAL TABLE SIMILAR TO THE STRUCTURE OF YOUR LOCAL FILE.
2) CREATE BDCTAB LIKE BDCDATA.
3) CREATE BDCMSG LIKE BDCMSGCOLL.
4) CREATE AN INTERNAL TABLE SIMILAR TO THE 1ST INTERNAL TABLE.
5) UPLOAD FN UPLOADS DATA FROM THE LOCAL FILE TO THE ITAB.
6) LOOP AT ITAB.
POPULATE BDCTAB TABLE.
CALL TRANSACTION STATEMENT.
PERFORM CHECK.
REFRESH BDCTAB.
ENDLOOP.
7) FORM CHECK.
IF SY_SUBRC <> 0.
CALL FUNCTION FORMAT_MESSAGE.
APPEND ITAB2.
ENDFORM.
TRANSACTION FOR RECORDING SHDB.
MAX TIME ALLOWED FOR ONLINE EXECUTION 300 SECONDS.

Pls reward if helpful.

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

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

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 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 Direct delta and delta Queue

Similar Messages

Maybe you are looking for