Delta Changed Records

Hi all
Here i am facing oneproblem with standerd data source 0ME_ISM_AM_INV_1
in this data source when i run the delta it is taking only new records but not canged records how to get the changerd records as a delta .
Dtasource name -
0ME_ISM_AM_INV_1
FM--ISM_BW_AM_INV_1
Regards
Anand

HI ,
see if you do init with data transfer then it will behave as full update and it will bring previous +new records from the system and set the init pointer ...
and if you do init without data transfer then it will only set the init pointer dont bring any records ..
and you have to run delta after that this will bring new records ..
new records and changed records are same and tehy are only delata records ..
regards,
shikha

Similar Messages

New status for changed records or Additive Delta

Hi Guys,
I have a design question for ODS and Extractor.
The requirement is as follows...
There is a table in CRM with service point as primary key. The fields in the table for example are bill account and Meter ID. Key figure is a XYZ value. In CRM for that Bill account Meter ID combination the XYZ value will change every year. In CRM the same record is being updated with changed value of XYZ. But in BW when the delta is being sent I do not want it to update the existing record but add it as a new record. This way the history can be tracked for previous years XYZ value.
What is required to make this happen?
When creating the extractor I think I should give the delta as new status or additive delta?
What should I indicate as delta specified field?
For the ODS ( I am on BI 7.0) should I create the normal ODS or should I create the write Optimized or something for this requirement ( I dont remember right now the 3 types of ODS we can create).
Your inputs will be greatly appreciated.
Thanks
Kumar.

Thanks Puneet!
Good Answer.
New and Changed records does help in getting the records as desired.
But the problem is while loading into BW I cannot create a new record. The primary key is only Service Point. So even if the key figures and dates associated with that record changes, BW will still update my existing record.
Is there a possibility of using the dates as a pointer that a new record should be created.
Let me explain it better. Following is the structure of table.
Service Point (primary key)
Product GUID (key in CRM)
Circuit ID
Installation date
Effective date
Termination date
CRC (some key figure)
Scenario is - This year Service Point A with CRC value as 50 with effective and termination date for example .. May1 2009 - Apr 31 2010.
Service Point   CRC   EffectiveDate   TerminationDate
A                     50      5/1/2009         4/31/2010
Next year the same service point will have different values and CRM system will update the record in CRM table.
Service Point   CRC   EffectiveDate   TerminationDate
A                     60      5/1/2010         4/31/2011
1) So I was wondering if there is a way or some code can be written to check if effective and termination dates are not same it should be added to ODS as a new record.
2) Another way is to make some sort of Time dependency. Like use Valid From and Valid To dates to track the changes to the record and display all the different values for every record when the CRC values were valid between what dates.
3) or some other way you can suggest

How can we get changed records in delta in case of numeric pointer

Deall All,
Thanks to all of you gurus i have been able to Get delta update for my query.
There is one last issue how can i include changes records in my delta update when i am using numeric pointer for data selection.
or
It can only be doen by time stamp.
can you explain me details of using time stamp.
Thanks & regards,
Gaurav Sood

Dear Gaurav,
Here we have three options for delta updation:
Time Stamp:   If we want to update change in the records with respect to the time interval then this option is selected.
Calend. Day:   If we want to update change in the records with respect to day to day basis then this option is selected.
Numeric Pointer: If we want to update in case of record which is completely new with respect to Field name then we use this option.
And we have got some settings like:
Safety Interval upper limit:
This field is used by Data Sources 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.
Data Source Is Real-Time Enabled
The 'real time enabled' indicator determines whether a delta-enabled Data Source can be used as a supplier of data for a real-time daemon.
And there are two options provided like
1)     New Status for changed records:
If you select this option each record to be loaded delivers the new status for the key figures          and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
2)     Additive Delta:
The key figures for extracted data are added up in BW. Data Sources with this delta type can supply data to ODS objects and Info Cubes.
Hope this helps u..
Best Regards,
VVenkat..

Question on SFSF Adapter : Delta sync to fetch only changed records.

Hi All ,
As per the SAP Document on SFSF Communication channel, one of the feature supported by SP00 release of the connectivity add-on 1.0 is :-
1. Delta sync to fetch only changed records
SFSF Adapter: Delta Sync
The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system.
This increases the efficiency of query operation.
So below are my question accross Successfull run date feature :
Is it SAP PI Connector internally maintains this last successful run date ?
what would be Time-Zone of Successful run date : Is it where SF DC is located or where PI Box is Located ?
what is it mean from successful run date ? - is it process successful run date or is it just communication channel successful run date ?
For Delta extraction - This Successful Run Date - Is it maintained internally for Interface wise or Communication Channel wise ?
eg. If i have 5 Delta Interface - will SAP PI maintain 5 Successfull run dates w.r.t to each connector or w.r.t each Process ?
for more information please open below URL.
http://help.sap.com/saphelp_nw-connectivity-addon100/helpdata/en/1e/22aaf0780d4b78b6f889157f6a8035/frameset.htm
Regards
Prabhat Sharma

Hello all,
I have the same question : in the "official" documentation (SuccessFactors (SFSF) Adapter for SAP NetWeaver Process Integration) is mentioned this :
Delta Sync - The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system. This increases the efficiency of the query operation.
Anyway I cant find any specification on how to use this feature. Do you have any suggestion on how to implement it or any reference to an existing documentation?
Do I need to write you an email to get the info?
Regards

*Query needs The Delta changeed records from Change log table*

Hello Friends,
I got an requirement where they want to see the current data and also the changes that happened last week. For e.g.
Sales Order 1       100 Qty      Nov 1 2009
sales Order 1         50 Qty      Oct 25 2009
as you can see, they want to see these both records in the query. I am running out of ideas , on how to establish this scenario. Can we some how report directly on the changelog table where it maintains all the delta changes.....
Appreciate your answers........ Thanks for your time......

Hi,
you can do the following:
to find last week
Create a Customer Variable for Calday
EXIT_SAPLRSOO_001 ---> Include ZXRSRUO1 write the code for the variable created above
DATA : date TYPE sy-datum.
date = sy-datum. "Today
date+6(2) = '01'. "First day of this month
date = date - 7. "Previous week before first day of this month = last week of last month
Current week take the system Date ( with give the current week)
                             OR (more options)
Some function modules you can use in exits are
DATE_GET_WEEK - Will return a week that the day is in. ( Current week)
DATE_GET_WEEK -1 will returne the previous week of the day is ( previous week)
Santosh

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

How to use the change log in ODS to track Delta change?

People say that historical data (like Delta change) in ODS can be tracked in the Change Log. How to use the change log to track historic data?
Thanks

Kevin
See if it helps
Every ODS object is represented on the database by three transparent tables:
Active data: A table containing the active data (A table)
Activation queue: For saving ODS data records that are to be updated but that have not yet been activated. The data is deleted after the records have been activated.
Change log: Contains the change history for delta updating from the ODS Object into other data targets, such as ODS Objects or InfoCubes for example.
An exception is the transactional ODS object, which is only made up of the active data table.
The tables containing active data are constructed according to the ODS object definition, meaning that key fields and data fields are specified when the ODS object is defined. Activation queue and change log are the same in the tables structure. They have the request ID, package ID and the record number as a key.
Data base structure changes
http://help.sap.com/saphelp_nw04/helpdata/en/d2/d53ec3efdc9b47a9502c3a4565320c/frameset.htm
Hope this helps
Thnaks
Sat

How to retrive delta changes in Infotype

Dear All
I am working on development of New Interface program from SAP to 3rd party application and this will run on daily.
I want to retrive delta changes record alone in 10 infotype tables.
I checked the Tech.setting of these 10 infotype table and came to know that log data changes & Maintain as transparent table check box is selected.
But i couldn't find any record in the table: DBTABLOG
Is there is any other table where the delta change in the Infotype get saved.
The infotype am checking is IT0000,IT0001,IT0002..etc
Could any one help me to solve this issue...
Definitely I will reward for best answer
Regards
Babu

Hi Babu,
please use RPUAUD00 program.
you can do assign above program in your interface by using SUBMIT.
another way. you create one Z function module, here you do submit RPUAUD00 program.
Please find sample code as below.
RP_PROVIDE_FROM_LAST p0167 space pn-begda pn-endda.
IF p0167-aedtm GT wa_last_create_date.
l_search_text = '.Benefit Plan.'.
l_infotype = '0167'.
PERFORM check_for_change USING l_search_text l_infotype
CHANGING wa_changes.
IF wa_changes EQ c_checked.
RETURN.
ENDIF.
*& Form CHECK_FOR_CHANGE
text
FORM check_for_change USING p_search_text TYPE zdesc_15
p_infotype TYPE choic
CHANGING p_changes.
CALL FUNCTION 'ZHR_GET_INFOTYPE_FIELD_CHANGES'
EXPORTING
search_text = p_search_text
infotype = p_infotype
pernr = p0000-pernr
bypass_type_check = 'X'
IMPORTING
old_value = wa_old
new_value = wa_new
TABLES
date_range = s_datum
EXCEPTIONS
no_change_found = 1
OTHERS = 2.
IF sy-subrc EQ 0.
p_changes = c_checked.
ENDIF.
ENDFORM. " CHECK_FOR_CHANGE
I assigned RPUAUD00 program in Z function module.
Cheers,
Guru.

R/3 Delta changes in BW

Hello Everyone,
When we do an Init or Full data extraction from R/3 to BW for the first time for any extractor, the data gets loaded in BW. When we load delta changes from R/3 by doing a delta load into BW, how does BW know to extract only the changed R/3 records and not all records.
How are R/3 changes tracked in BW? where is the previous request information stored in BW?
Thanks in advance

Hi,
After initial full upload if there is any change in the records or any new records found then only the delta will work, if there is no new records then even u do the delta there is no updation..
One morething in RSA7 of detail view u will get the previous posted records and next delta records..the old records will me maintained untill the old request is successful and a new request was reached in r\3 from BW.
Regards-
Siddhu

Delta image records included in Purchasing initialisation

Hi all,
Is it valid for delta image records to be included in an initialisation of Purchasing (02)?
We have active 2LIS_02 DataSources and whenever they are initialised we get multiple records that are obviously all of the changes ever made to every purchase order. I have followed SAP's Best Practice document for initialisation and all the steps (LBWG, LBWQ, RSA7, OLI3BW). The industry sector is set to Standard and all the transaction keys seem to be in order.
As an example, there are only 4 POs in the R/3 Dev system but when I run the initialisation I get 12 header records (before and after images when the PO was GI'd). The setup table is DEFINITELY empty before I run OLI3BW and ROCANCEL is mapped to 0RECORDMODE and 0STORNO for all DataSources in BW, as recommended on a previous thread.
The only OSS Note relating to this seems to be 712898, as some of the FM's have different parameters. OLI3BW seems to look for InfoStructures before reading the transparent tables, so I don't know whether this affects the initialisation set up.
The load is too large and taking too much time to load from each initialisation that we do so we need to optimise it if possible. Can anyone shed any light on this?
Thanks,
Stuart

Yes, is valid and it is the way in which it works.

How we can load change record in cube.

Hi,
How we can load change record in cube, (delta)
i need step by step in sap BI 7.0.

Hi Nitin
I hope you are asking about delta loads, if your datasource supports deltas then you can do only changed records from source to cube. To see the details goto ROOSOURCE table in ECC and find.
For further help search in SDN and help.sap.com, you can find n number of postiings about the same.
Thanks
Reddy

Tracking of changed records:sem6 -bps

Hi friends,
i want to track changes made to particular field cell, when it was changed and by whom..simply tracking history of changes made to records..
i have how-to documents that is for tracking of changed records in Integrated planning as well as for SEM3.5(on BW3.5).
Ours is SEM6.0 with BPS ( BI7 system). If anyone of you have, pls share.
thanks,
kumar

HI Kumar,
Even in BPS you will follow same methodolgy, create infoobjects for Uname, Timestamp and GUID (if needed). Then use a char derivation to derive those objects.
Note : If you use time, each delta will create a new reord with new timestamp and delta value.

Delta changes in R/3 sales document are not coming into CRM

Hi Middleware experts,
We are on CRM 5.0 SP 005 with ECC 5.0 SP 007 and using the scenario X for sales documents replication.
Now the order is created in CRM and successfully transfered to R/3. I can see 3 Bdocs in SMW01 with green lights. First Bdoc says 'R/3 adapter is called', second Bdoc says 'the order is successfully saved' and displays a warning 'The sales document is not yet complete: Edit data' and third Bdoc has no messages. Also I do not see any struck queues in CRM and in R/3
I am able to edit the sales document in both the systems as per the scenario X. Now I have completed and saved the document in R/3. Surprisingly these changes are not coming into CRM and no new entries in SMW01. Also R/3 SMQ1 and CRM SmQ2 doesn't show any entries. I am also not able to debug, since I do not see any Bdocs in SMW01.
Now, if I changes the document in CRM and these changes are coming into R/3.
Also all documents created in R/3 are successfully going into CRM including delta changes in R/3.
I do not have any clue on what is happening? Highly appreciated, if you can help me.
Thanks,
PK

Hi PK,
In R3AC1 only we put the filter. So if you do not have any other filter then make sure that you are changing the order which was created not before the date mentioned.
I would recommend you to just deregister the CRM system in R/3 Transaction SMQS and do some changes in the orders and check any queues are getting created corresponding to that order, If yes that means filter is not an issue. Then debug the queue and find the exact problem. Also make sure that the order you are changing in R/3 is of the same order type what you have mentioned in the filter.
Make sure to registor back the CRM other wise all the queues will get stuck in R/3 outbound.
Reward points if it helps!!
Best regards,
Vikash.
Message was edited by: Vikash Krishna

Delta Changes in ECC 6.0 compared to R/3 4.7 - SAP MM

Hi Guys,
Please list me some 4-5 Delta changes made in SAP Materials Management - ECC 6.0 compared to SAP R/3 4.7 version.
Thanks,
Pallu
Edited by: Pallu Tillu on Sep 15, 2009 3:11 PM

Hi
see these links
Refer this link for ECC 5.0 & 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
A similar post
/message/1783778#1783778 [original link is broken]
You can go through the Release Notes for each of the versions after 4.6B (4.6C, 4.7 , ECC 5.0 & ECC 6.0)
http://help.sap.com/saphelp_erp2005/helpdata/en/43/688055b88f297ee10000000a422035/content.htm
For 4.7 SAP R/3 http://help.sap.com/saphelp_47x200/helpdata/en/12/9d78d6d8f74043a32e82be87e433b7/content.htm
Release Notes on SAP Web Application Server 6.30
http://help.sap.com/saphelp_47x200/helpdata/en/2b/64fc3e9d3b6927e10000000a114084/content.htm
http://solutionbrowser.erp.sap.fmpmedia.com/
Reward points if useful
Regards
Anji

Queue is getting struck for every delta change in CRM 5.0

Hi Middleware gurus,
The queues are getting struck with status 'READY' for each of these following scenarios:
1. Individual new sales order upload from CRM to R/3 (CRM - SMQ1)
2. Individual sales order delta changes upload from CRM to R/3 (CRM - SMQ1)
3. Individual new materials donloaded into CRM from R/3 (CRM - SMQ1)
4. Material delta change download from R/3 to CRM (CRM - SMQ2)
5. Knowledgebase delta changes download from R/3 to CRM (CRM - SMQ2)
I have to manually release the queue everytime, so that the changes can be uploaded. Am I missing something?
By the way individual new sales order created in R/3 and delta changes on R/3 orders are getting replicated into CRM without any problem.
Thanks,
Kishore

Hi Kishore,
We had similar issue before. Do not use the replication scenarios X,Y or Z. You have use the scenario A which will solve your problem for sales order replication issues. Please refer to the note 705200. For rest of issues make sure in both the systems the queue scheduler is running. If not running actively then register the each queue in both the systems using SMQS and SMQR. If still the issue is not solved then let me know.
Award points, if the issue is solved
Cheers,
Paul Kondaveeti

Delta Changed Records

Similar Messages

Maybe you are looking for