Delta in COPA

Can somebody explain me how Delta works in CO-PA? How is Delta behave in Account based and Cost based? What is meaning of Init load and Delta in this process? Documents and OSS notes (392635) say delta and init load works in Line item, Segment level and Summarization level differently. Its very confusing. Is it only time stamp - Delta can be implemented in CO-PA? How to change the safety time interval between deltas?
I know its lot of questions...Please share your knowledge, it will be helpful

Yeah Bhanu, But most of them are unanswered and not answering my questions. I have checked the OSS notes on this but not able to follow.
If you have explained it to someone in any forum than please paste that link and I will go trhough it.
Thanks
Rk..

Similar Messages

Working of deltas in copa and fisl

hi gurus
i am not able to understand the flow of data
from r/3 to bw in copa and fisl.
q1. when deltas data comes to rsa7 or not.
if so from where data comes in fisl
and copa
q2.when i am doing deltas in copa from which tables data is coming.
q2.when i am doing deltas in fisl from which tables data is coming.
please send me the answer to my mail
[email protected]
i will assign full points

Hi vishal,
The question u posted is very general and indeed u need an understanding of underlying table and their contents and how the table contents are related to the Business process.. The best think i wud suggest you to look for is SAP course material related to Exraction it should be TBW30, or BW350 i believe. You can get a very clear idea of COPA and FISL extraction.. Sorry i dont have the material, but this is where u can look in to for a clear conceptual explanation.
regards,
kishore

WHAT IS SAFETY DELTA IN COPA

Hi Gurus,
WHAT IS SAFETY DELTA IN COPA?
Help me.
Regards,RAMU.

Hi,
Safety Delta
The delta method relies on a time stamp which is contained in each line item, record in the
segment level and summarization level. This time stamp makes it possible for the system to
decide which line items are already contained in the summarization level. However, if you are
using more than one computer (database/application servers), these could show a slight
difference in their system times. The system can correct inaccuracies of up to half an hour by
ignoring any postings made in the last half hour.
Refer Page 375
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA.pdf
Hope this helps.
Thanks,
JituK

Realignment of delta in COPA ?

Hi Gurus,
What is Realignment of delta in COPA ? In which Scenario we will go for this kind of delta ?
I will assign points for your valuable answers.....

Hi,
Are you talking about changerun? If so, I could answer.
~Prem

How to set Delta for COPA Extraction

Hi all,
I want to do generic data source using Function Module for COPA can any one tell how to set the delta what fields i have to fill.
thanks
kavitha

Hi kavitha,
The easiest way to work out with Function Module is to copy the standard one and modify according to your reqirement.
The standard one is RSAX_BIW_GET_DATA_SIMPLE .
Dont forget to copy the Function grp RSAX into a custom defined Grp and Modify the Ranges options as per ur req.
and in Function module, in Sourcecode and Tables, Do modify the E_T_data with ur Generic datasource ,make sure u also modify the select statements within the sourcecode. If you have an idea on ABAP its really easy to work out.
And regarding the creation of Datasource.
this blog may help for the same.
Generic Extraction via Function Module
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.
Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
these are used to determining the delta in a datasource:
1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
Regards,
Anish

What are the delta mechanisms and tables used for Lo Extraction & COPA

Hi all
what are the delta mechanisms and tables used for Lo Extraction & COPA.
please explain clealry.
Thanks & Regards,
James

James,
Please go through Roberto's weblog :
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Anyways,
As you know LO cockpit consists of different modules(MM, PP, SD, etc)
They are called appl components. Each of them have a number (eg.MM=02) and for each appl comp they might be different Data sources and for each DS they might be different tables. So, unless you be specific we cant tell a specific table for a DS.
coming to the delta mechanisms, there are " direct delta, queqed delta and serialized delta".
Copa is based on the oepration concern. it can be created on " accouting based" or "costing based".
Assign points if helpful
Kalyan

Standard and generic COPA delta

Hello
I dont understand why many people say standard copa delta , generic copa delta.
COPA is a generated application and delta should be generic.
What do you mean when you are talking (many posts in this forum) about standard copa delta?
Thanks

Hi,
Copa extraction is generated application based on the operating concren configured in R/3 system. and same applied to delta process.
R/3 table TKEBWTS contains information about the COPA load requests that have been posted into BW. time stamp entries in this table can be maintained to reintialize the delta. this may be the reason some may call in generic or standard delta.
Dev

COPA Delta

Hi,
I am using delta enabled COPA datasource to extract copa data into BW. In our delta que(RSA7), COPA datasource is not accumulating any new or changed delta records. After a full load, I have successfully initialised delta and I can see the COPA datasource in RSA7. Can someone tell me what are the steps for a successfull delta method.
Thanks,
Rao.

Simulate Initialization of Delta Process using KEB5 transaction and read <u>following SAP provided information thoroughly before you start doing this:</u>
You can use this function to simulate the initialization of the delta procedure for a DataSource and to set the time stamp of the DataSource to a desired value. You can then plan an InfoPackages for delta updates.
Note: Only use this function in the cases described below. Inappropriate use can cause irreparable inconsistencies in your data in the SAP BW.
The simulation occurs as follows: the system sets the DataSource status to "Update successful" and gives it the time stamp you entered. A data package is also logged with the interval 0 to that time stamp. This data package sends 0 records to the SAP BW.
It makes sense to simulate the initialization of the delta procedure under the following circumstances:
You want to perform an initial test in the SAP BW using just a reduced amount of transaction data so that you can view reports with data from your CO-PA DataCube, for example, without having to replicate several million data records in the SAP BW.
In this case, set the DataSource time stamp in the Date and Time field to a date a few weeks ago.
Apart from executing this function, you also need to make the following settings in the SAP BW to simulate the initialization of the delta procedure.
a) In transaction RSADMIN in the SAP BW, enter your name in the field User for whom the debugging mode is active.
Consequently, the indicator Update data in the source system immediately in the tab page Update parameters in the InfoPackage Scheduler is then unlocked for entries.
b) Create an initialization InfoPackage and deactivate the indicator Update data in the source system immediately for this InfoPackage. In this way, you stop the system from immediately processing the request IDoc in the source system.
c) Start the initialization InfoPackage.
d) In the monitor, set the overall status for this InfoPackage to "OK" (green light).
You want to continue a delta replication from a different DataSource. This is sometimes necessary (for example, after an upgrade from R/3-Release 3.x to 4.5) if you wish to use the new option for updating multiple valuations (transfer prices). You then need a DataSource containing the valuation category (VALUTYP) as well as the currency type (CURTYPE).
In this case, simply copy the time stamp from the old DataSource by entering the name of that DataSource in the field from a different DataSource. Then continue the delta replication from the new DataSource.
Note: The initialization of the delta procedure must also be simulated in the SAP BW for the new DataSource. To do this, follow the points a) thru. d) described above.
Hope this is helps; please assign points if it does...thanks
A.Ramasubban

Difference between COPA and Logistic Delta Mechanisam

Dear All,
May i knw the difference between the COPA and Logistic Delta Mechanisam h it works.
In our Production system, when ever a logistic delta fails we take action and repeat it then it will featch the delta on the same day,
where as in COPA delta, when it fails we take action and when we repeat it will fetch zero records and in the next day the delta will come.
What is the difference in both
What exactly is happeing in R/3 for these both delta mechanisam.
Thanks in advance,
K Janardhan Kumar

Hi Guru,
I will explain about delta extraction with timestamp in general with an example:
timestamp is generally in yyyymmddhhmmss format
let's assume delta runs daily at 09:00 morning.Last delta ran at 09.00 yestreday.And today when delta runs it picks the data ranges between
09:01 (yesterday's) to 09:00(today).
if one record is posted at 09:10 today,then it will not be picked by today's delta(coz' it is posted after 09:00)
Hope now you are clear about timestamp.........
In case of COPA ,we are using timestamp as a tool to identify delta
now COPA delta mechanism has one more concept "saftey delta ":let's put a question to ourselves ,why we should use this;
SAP answer is "The reason for the selection of the safety delta is that there are possible level differences of the clocks on different application servers. If the delta is selected on a level that is too low, it is possible that records
are not taken into account when uploading into the BW."
'Safety delta' usually will be set to 30 mins during the initialization /delta upload(default).
This means that only records that are already half an hour old at the starting point of the upload are loaded into BW
Ex:
we have made following settings for copa
timestamp=09:00
safety delta=30 mins
now when you run daily delta,it picks data ranges between (current timestamp-safety delta) i.e 08:30 instead of 09:00(yesterday's)
to 09:00 today
check this oss notes 502380 for better understanding on COPA delta mechanism
Symptom
There is some confusion about how the delta process works with CO-PA DataSources and the old logic (time stamp administration in the Profitability Analysis) or there are data inconsistencies between the BW and OLTP systems.
As of PlugIn Release PI2004.1 (Release 4.0 and higher), a new logic (generic delta) is used during the delta process. Old DataSources can be converted to the new logic. New DataSources automatically use the new logic. With the new logic, the time stamp administration is located in the Service-API and no longer in the Profitability Analysis.
This note refers only to DataSources with the old logic.
Reason and Prerequisites
Administration of the delta process for CO-PA DataSources partly occurs in the OLTP system. In particular, the time up to which the data was already extracted is stored in the DataSource control tables (old logic).
Solution
Since the control tables for the delta process for the extractor are managed in the OLTP, the following restrictions apply:
1. There should only ever be one valid initialization package for a DataSource. Data inconsistencies may occur between BW and OLTP if, for example, you schedule an Init for various selections for the same DataSource and data is posted between the individual initializations to the Profitability Analysis. The reason for this is that each time the time stamp for the DataSource is initialized in the OLTP, the current value (minus the safety delta, see note 392876) is reset. Records from a previous selection are therefore no longer selected with the next delta upload if they were posted before the last initialization run with another selection.
2. Initialization can always only be carried out from one system. Inconsistencies may occur if the same DataSource is used from several BW systems and if data is posted between the initialization runs. This is because the time stamp for the replication status is reset for every initialization or delta upload in the OLTP. Records may therefore be missing in the system that was first updated if updates were made in the result area before the Init or delta run. In the system that was the second one to be updated, the records that were loaded into the first system are missing for a delta upload.
In the case of large datasets, you should therefore perform initialization either using several DataSources or with a combination of one or more full uploads and an init upload. Full uploads without errors are possible for closed periods/fiscal years because no additional changes are made to this data. Initialization should be performed, for example, from the current fiscal year. The full updates for the closed periods can also be split in time. If required, more characteristics, for example, the action type, can also be used for the selection. For information on the period selection, see note 425844
Hope you are clear now!!!!!!!!!
Cheers
Swapna.G
Message was edited by:
swapna gollakota

Unexpected value in COPA

Hi experts,
We are getting a record from COPA datasource in BW which never occured in that fiscal period. Even the company code, cost element (not matching in R3) and amount are coming from a different world. Where should I investigate to check for the problem.

Here is a good "How to..." to have when you are dealing with CO-PA:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
If you don't turn on the PSA for COPA, then check RSA3 in your datasource. Also, there are a few copa transactions you can use to look at the datasources:
KEB0 -- COPA Datasource display or create
KEB2 -- Detailed display of COPA datasource
KEB3 -- COPA DS debugging
KEB4 -- ??
KEB5 -- Simulate delta on COPA datasource
These can all be found in SBIW in your R/3 system.
Additionally, you can use KE24 to Display Actual Line Items for COPA. This is the best way to validate your date because these are the actual line items sent from R/3 COPA to BW (or at least they should be). Look at your errant line item and document numer and see if they are in KE24. If they are, you're good!
Brian

Delta links

I followed SAP's recommendation to make copies of the original ESS Portal objects (iViews, Pages, Worksets) so that customer modifications do not happen on the original SAP objects. I have therefore created delta-link copies for all the original SAP objects. However, the "delta-link copy" pages I created use original SAP iViews, not my "delta-link copy" iViews. So customer modifications to the copied iviews will have no effect. One option I have is to re-attach the delta-link-copy iviews to delta-link-copy pages, but in the future SAP may change the relationship page-iView and then my system won't work (or won't take advantage of the SAP enhancement). Any other ideas?

I think re-attaching the delta linked iViews is the only option. When SAP privdes any update we need to do this excersize again.

Delta links on applying patches/upgrade.

Hi,
I have a basic question. What happens on applying patch/upgrade to the delta linked copies, when the source objects have been updated/upgraded with new SAP changes.
Will the delta linked object properties get over written by new upgraded (or SAP patches) source objects.
I have made delta links of the SAP delivered WPC IView container objects and using them in the custom pages. Lets say on applying a patch or upgrade, the orginal source objects are changed. Will those changes undo my changes on target delta linked objects.

Hi,
Copying to your namespace is possible but by that you loose all the advantages in the delta-link.
What exactly are you copying Roles, iView, Pages everything?
Adding additional delta link layer between the roles and SAP content is a wise step but copying everything will only dupplicate content and will not allow you upgrade safty with SAP features.
Regards, Elisha
PCD Team Leader
SAP

How to get sales order information in COPA datasource

Hi All,
I wish to get sales order information like Customer, Sales office, Sales group etc in COPA datasource. Presently all this information is not available and the fields display blank value. Can you please guide me through the steps to achieve this.
Thanks in advance,
Sananda

Hi
They actually create Generic extraction for COPA modules..especially all finance modules. Hope you are aware of it and do you know the steps for COPA?
Any check all the below links as well lot many threads for COPA available. pls chek that as well
http://sap.seo-gym.com/copa.pdf
http://searchsap.techtarget.com/answer/Steps-for-a-generic-extraction-of-FI-CO-COPA-and-LO-in-SAP-BW
Problem with COPA extractor 1_CO_PA<...>
Delta Mechanism : COPA extractor
steps for FI-SL and CO-PA Extraction
COPA extraction steps for BI 7.0
This link would be help ful:
http://www.sap-img.com/business/copa-extraction-steps.htm

FI & CO deltas

Can any body tell me , how to set up deltas in FI extraction & co-PA extraction.
Please.
Thanks.

Hi,
CO-PA Delta:
Generally COPA data sources are delta capable ( Directly data can be loaded into Info cube ). They provide additive image.You can check this by putting ur COPA data source name in RSA2 in R/3 system, and check the delta capability in "Delta Process" field. It should be "CUBE". You need not need to manually define delta.Just do a "init" with data transfer and set a just "delta" in your process chain.
when you first time load the data through infopackage u will get these two options,After Initialization package gets uploaded in the Infoprovider, you can create the infopackage for Delta schedulling, and COPA is Delta enabled only.
Pls chk this link for FI delta extraction
http://help.sap.com/saphelp_nw04/helpdata/en/af/16533bbb15b762e10000000a114084/content.htm
Regards
CSM Reddy

Regarding COPA DATA

We have loaded the DSO you have created in GWD. However there is some issue, so wondering
Issue : When we do a full load to DSO, many of the fields are not getting populated whereas if I do a delta init load with data , it brings data. Please note we need to give the number range in the infopackage for BELNR always. You can check this issue in the PSA itself. Do not need to run DTP and send it to ODS.
Can you search and investiage the COPA extractor ( 1_CO_PA_*) we are using and see any suggestions or understand bewteen FULL and DELTA from COPA extractor
Guys can u help me in this one
Cheers
vijju

Hi
CO-PA DataSources cannot be enhanced using the standard SAP BW tools. If you adjust the operating concern (by adding or deleting characteristics or value fields), it is then no longer possible to simply edit the DataSource. You have to delete the DataSource and then create it again.
Try the following Note:
0408366 Simulation of the delta method initialization
0502380 Information: Delta method for CO-PA extraction
0546238 Change of the mandatory field PERIO in the selection
0571853 Incorrect data during delta upload for account-based CO-PA
Delta / Init is not possible with all Fields with CO-PA try to see the SAP Note 546238 for the delta enabled fields.
Hope it helps and clear

Delta in COPA

Similar Messages

Maybe you are looking for