Delta in LO Extraction

Dear all,'
Whenever we are running the init info package first time.
1.with data transfer .
2.without data transfer.
My doubt is how many records will come in RSA7 with.
1.with data transfer .
2.without data tarnsfer.
Let us assume there are 100 records in setup table.
I want to know about the delta pointer it set in Delta queue.
Please help me
Thanks,
Saveen Kumar
Edited by: saveen kumar on Feb 19, 2010 3:07 PM

Hi Saveen,
If you do an Init without data transfer then no records are loaded, only the delta
queue entry is created in RSA7. The time stamp will be created from the time at
which this entry is created in RSA7 , its depends on a successful load in the
BW monitor (Green traffic light) and then all new records or changed records
will be extracted from this point forward in your delta loads.
With Init with data transfer then all the records are extracted from the setup
table.
You will find more detailed information on the logistics extraction in the SAP
note 602260.
Best Regards,
Des

Similar Messages

Delta for Generic Extraction

Hi all,
Can anyone tell about delta for generic extraction i.e 3 options in detail and when do we use it.
thanks in advance,
chandra sekhar

When you want to customize existing datasources at R/3 sides then you can do that with customer exits.
Suppose if you want to add a column to the existing datasource then you will use append structures (Transaction SBIW-> Edit Data sources - Enhance Datasource) then to fill the column you will write the code in these Exits.
There are 4 types of Exits available.Function Group (XRSA)
EXIT_SAPLRSAP_001 Customer Function Call for Supplying Transaction Data
EXIT_SAPLRSAP_002 Customer Function Call for Supplying Master Data (Attributes)
EXIT_SAPLRSAP_003 Customer Function Call for Supplying Text
EXIT_SAPLRSAP_004 Customer Function Call for Supplying Hierarchies
As you are aware there 4 types since the datasources in R/3 are predefined to fill the data of BW viz, attributes,Text,Hierarchy and Transaction.
Check the below forum discussion for more information..
DataSource Enhancement
Regs
Gopi
Assign point if it helps ...

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

Deltas in generic extraction

how can we set delta updates in generic extraction?can any one help in this

Hi Praveen,
Please do check the link for step by step for generic extraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
check the following
http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
business content
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
https://websmp203.sap-ag.de/co
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
(navigate with expand left nodes)
Check these links:
/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
/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
For Generic:
>Go to Tcode : RSO2,
>There give the name of data source which you want to create like transaction data source or master data attribue or Text data source.
>enter
>again in the next screen you need to give application like SD or MM etc
>in the same screen need to select table/view or infosetquery or function module. these are different ways of creating data sources.
>Give the name for the same like if u r creating data source on table give the name of table.
>click on Generic delta which will there in application tool bar and fill the required columns in that screen like type of delta and all
>continue and save
>it will give all the fieds
>enable the check boxes based on your requirement like selection or hide or field only..
>save
Hope This Helps.
Regards,
Ravikanth

Where to find deltas in generic extraction

hi experts,
could you please explain me tcodes which are used to find the delta data while we go for generic extraction. Also can anyone explain me the full process of extracting the data using
infoset query and function module.
Cheers,
Pragya.

Hi
You can define delta's in generic using " calendr day, numeric pointer, time stamp."
Generic Delta
If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system. Only the data that has newly arrived is transferred.
To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                            b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
Example for Determining the Selection Interval for a Generic Delta
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
source: help.sap.com
Hope it helps
kalyan

Deltas for generic extraction.

Hi,
if i want use time stamp & calday for my generic extraction , i can use uppercase and lower case, wher can i give timings suppose want run deltas for 10am-10.30am.
regards
anitha

Hi,
Security interval upper limit The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The security interval for the upper limit is 120 seconds. The selection interval for the delta request is: 12:00:00 to 12:28:00. When the extraction is finished, the pointer is set to 12:28:00. Security interval lower limit The delta-relevant field is a timestamp. After images are transferred. In BI the record is overwritten with the post-change status, for example, for master data. Any duplicate data records do not affect BI. The last read timestamp is 12:28:00. Delta extraction begins at 13:00. The security interval for the lower limit is 180 seconds. The selection interval for the delta request is: 12:25:00 to 13:00:00. When the extraction is finished, the pointer is set to 13:00:00.

Generic Data Source delta is not extracted

Hi,
There is a problem in extracting the delta records using Generic Data Source. Delta records ( New / Modified records ) are not posted in the RSA7.
I'll Explain you the Scenario I have done. Created a generic data source in R/3 using view. In the view there is a field Sales Order No. I have enabled the delta update for this field. In the generic delta i have chosen delta type as Numeric pointer.
Extracted the entire record using full update and after initializing the Delta, it extracts the delta record well ie. it only extracts the sequence of Sale Order No. First I extracted nine records(i.e 10001 to 10009) using full update. again I entered a record in underlying table with sale order no as 10011-10013. It extracts those records into BW system. Then again I made an entry in the table with sales order no 10010. But the record is not extracted. Even though I tried of specifying safety lower limit as -3. Still it not extracting the record(10010).
And what if I posted a value of sale order 10014 with the same. what should I do?? Help on this plz.
--Durai.S

Hi SVS,
Thanks for your reply.
I followed this in my scenario. But I don't understand why it is not extracting? even I specified the safety limit of upper and lower values in the generic delta.
Here the below explanation shows that the delta record can be extracted even if the pointer value is greater than the posted value.
Numeric pointer (last extracted value 10011; Data in underlying table (Max value = 10025) )
Data would be extracted from a min-value of 10010 (lower limit adjusts the last counter 10011 by specified value u2013 1)
max-value of 10020 (after adjustment for upper safety limit u2013 by 5). The current pointer would now indicate 10020 in
RSA7.
--Durai.S

Delta in Generic extraction

Dear All,
When we should go for which delta method and is there any specific reason for this.
What we use in real time scenerio.
Thanks,
Saveen Kumar

Please read this and let me know if still you are not clear.
It all depends upon your reporting requirements.
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
@AK
Edited by: Ashok KUMAR on Apr 1, 2010 3:39 PM

Delta in FI extraction

Hi,
During the delta of an FI extraction, do the delta records first come to RSA7 or does it directly enter BW?
Thanks.
Sankar. M

Hi,
Once the Initilization has done, the delta records comes into delta queue(RSA7)
Thanks

Configuration of delta in Lo extraction

Hi gurus,
please explain about LO extraction in detail.
how to implement delta.
what is the need of setuptables.
what is the need different update modes & difference between
when exactly these update modes are used.
if possible I want enhance datasource like 2lis_11_VAHDR.what are the steps to be taken.
Please do not give any links.
Thanks,
Madhu.

Hi,
Setup tables
The Data in setup table is used in Delta initialization and full upload. Actually data comes from OLTP tables to Setup table in filling of setup table
http://www.sap-img.com/business/questions-answers-on-sap-bw.htm
Different update types
Chk this document(exp the diagrams explain ur doubts)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7312ec94-0501-0010-0da3-a49815566423
and also chk this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7312ec94-0501-0010-0da3-a49815566423
For LO datasources:
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
SD Sales BW
Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
Select the fields of your choice and continue
Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders Perform Setup (T-Code OLI7BW)
Specify a Run Name and time and Date (put future date)
Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
How to do basic LO extraction for SAP-R3-BW
StepsEdit section
Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
Go to transaction RSA3 and check the data.
Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
Now you can go to your data target and see the delta record.
Regards,
B

Delta Problems in Extraction of CRM data to BW

Dear Gurus, Arun,
We are using CRM 4.0 and BW 3.5 version
Process Chains are scheduled to extract
delta records every day from CRM to BW production server.
For the Opportunities report, we are facing a problem.
For a Customer "XYZ Corporation"
A correct Opportunity is displayed
with expected sales volume = 50,000 USD
and status = "WON"
and number of opportunities = 1.
But the same Opportunity report shows
Customer "XYZ Corporation"
also displays a record with
status "ACTIVE" and expected sales volume Amount 0 USD
and number of opportunities = 0
There is only 1 current transaction existing in CRM server
relevant to these 2 records displayed in BW .

This Error happens for 10 to 20% of total Opportunities displayed
Any Help is Appreciated / Rewards also : -))
Thanks,
Aby Jacob
=========

Dear Experts,
I am thinking of a Solution like this....
Since the data in Info Cube is looking Good,
and only some of the BW reports are having error records.
=====================================

In the BEx Query
I can filter the records having
"Opportunities = 0 "
Only records with Opportunity >= 1 will be displayed
Kindly advice if this is a Good solution ?
Any inherent defects in this Workaround plan ?
Thanks again,
Aby Jacob
=======

Delta Problem while extracting the data by using function module

Hi Experts,
I have extracted the data by using Function module, for delta loads I have given Calday and additive delta in Generic delta settings, in BW side I have initialized the data after that I have given delta update option in infopackage and I made process chain also, every day process chain is running successfully but it is showing zero records, but there is a data in Data source (RSA3), means delta is not working.
What is the problem,
Is there any another settings for delta loads,
Please help me to do this,
Helpful answer will be appreciated with points,
Regards,
Venkat

Hi,
Try this delta type :NEW STATUS FOR CHANGED RECORDS.
More information from Nagesh, this information may help
1. New status for changed Records.
2. Additive delta.
New status for changed records means
New Order
order no quantity
1000 10
order changed to quntity 8. then 2 records will posted 2 BW in first case.
1000 -10
1000 8
if you come to Additve delta.
for the same case it will send the same record as
1000 10
changed records
1000 -2
this is the difference. New status with changed records should be used only in association with ODS not cube becoz we don't have overwrite option.
Additive delta we can use for ODS and Cubes with update mode Addition.
Regards,
Satya

Delta aren't extract thru XI

Hi all,
I'm trying to extract delta from flat files thru XI Process.
Every once in a while the data aren't extract and I can't see the data at the RSA7 & SMQ1.
When I monitor the data transfer with Trans' SXMB_MONI the transfer status is green flag, when I transfer the same file again the status changed into black & white flag and the data transferred into the RSA7 queue.
When i check SMQ2 i can see the entries with SYSFAIL status.
Can someone know to tell what happened and how to resolve this problem?
Thanks,
Ehud Bar

Hi,
Thanks for your answer, I'm familiar with this "How to"
Our BW is integrated with the XI, the issue is that sometimes for unknown reason the data aren't got into the RSA7 queue.
When I checked the transmission in SXMB_MONI (BW environment), I found out that the transmission status is green and not black & white like it suppose to be.
Most of the times when I send the data again I get black & white status.
Do you have any idea what can be the cause to the problem?
Thanks,
Ehud Bar

Delta for generic extraction using FM

Hi All,
I am trying to create generic datasource using function module. I need to set delta functionality for this DS but I don't know how to set delta for FM.
Do I need to give delta specific field in RSO2? My delta specific field is either AEDAT or ERDAT? Is it possible? how to write code for this?
I have around 13 tables & there is no stadard DS for these table so is it correct way to use generic using FM or is there any other way?
plz suggest & if u have any step by step document for FM plz provide.

Hi Manesh,
Yes you need to set up your delta enabled field in RSO2 when you click the delta button for the datasource.
Usually for generic datasources we use any date field to genarete deltas and looks like you have the same (AEDAT and ERDAT a re date fields).
You dont need to write any code for this. Just provide any field for executing delta and initialize. It will get you the delta based on the date.
In some scenarios, we get postings happening on an older date and hence dates cannot be used, in those scenarios we can go by numeric pointer.
Creating a datasource on 13 tables, i ma not sure how efficient it would be (mainly depends on the data volume on these tables) but yah writing a function module will be fine.
Let me know in case of any clarification
Thanks
Sachin

How to create delta extraction through function module?

Hi all,
So far i have created the data source through full load. But currently i would like to convert the couple of function module generic extraction converted through delta.
Can anyone let me know how to convert from full load to delta using generic extraction
thanks

Hi,
Try these Links, helps u in getting an idea.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aefb04-7043-2c10-8e92-941536eebc79?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30f1a423-02ae-2e10-bd85-bde64e61fe7b?QuickLink=index&overridelayout=true&51947629650864
Regards,
Aravind.

Delta in LO Extraction

Similar Messages

Maybe you are looking for