Delta in NW2004s

Hello
If I want to make an initial upload from data store object to cube should I select delta in extraction mode?
What is the purpose of "Only get delta once"?
Thanks

Dear,
Pls. see Andreas' reply in:
Re: Only get delta once- SPS 8
Deltas in DTP:
Re: Delta DTP
Delta DTP
Delta Processing using DataStore Object
Thanks,
Raj

Similar Messages

Writing to FI-GL records to Delta Queue using a Function Module

Has anyone of you tried to write FI-GL transactions to delta queue using BTE by configuring a function module. I am trying to achieve it for a datasource based on a view on FAGLFLEXA table (GL Line Items). For some reason I am not able to see records in Delta Queue. I am doing this to achieve RDA functionality. If you have done it please sends me step sequence and the name of FM.
Your help would be highly appreciable.
Regards,
Ram

Hello Ram,
See this SAP Network Blog: [Generic Extraction via Function Module|/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module]
Have a look at these docs,
[How to Create Generic Data Sources which use the Delta Queue (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]
[How to Create Generic DataSources Which Use the Delta Queue (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf]
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
Thanks
Chandran

Delta for Generic data source.

Hi,
I have created a generic data source for which I have taken the change data as generic delta in CRM4.0. But the problem is delta is not getting initiated. like we are not getting any records in delta. Kindly guide me what else i have to do to get this delta
Thanks
Naveen

Hello Naveen,
What is the delta method you have used, is it Time stamp or ALE Pointer?
See this SAP Note 539547 Generic delta with date does not work
Please see these docs as well
[How to Create Generic Delta|How to Create Generic Delta]
[How to Create Generic Data Sources which use the Delta Queue (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]How to Create [Generic DataSources Which Use the Delta Queue (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf]
Thanks
[Chandran|http://chandranonline.blogspot.com/]

Need for locking system for delta initialization (BW-R3-LO)

Hello all,
Could someone please help me with the following,
Please be kind, don't get impatient for the lengthy post
1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
             a). say, I do full load with end date and time (10pm 12-31-2007)
             b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
         If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
         If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
4. How this scenario differs to early delta initialization?
Your responses would be greatly appreciated
Thank you

Hello,
1
>
curious maven wrote:
> Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
No,you don't need to lock the Source System which is the advantage of Early Delta Init.
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
[Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
2
>
curious maven wrote:
> 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
Early delta is not supported by all the extractors. See Lo Extraction
3
>
curious maven wrote:
Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
>
>     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
>
>              a). say, I do full load with end date and time (10pm 12-31-2007)
>              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
>
>          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
>
>          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
4
>
curious maven wrote:
How this scenario differs to early delta initialization?
If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
[How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
[How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
Thanks
Chandran

Deltas not working in NW2004s

Hello All,
I am having issues while populating deltas in BI 7.0, we are extracting activity data from CRM and first populating all the deltas into ODS and then moving the data to Cubes. We defined a key figure for count which is always populated as a constant 1 at the DSO level. When we get a new transaction from CRM it gets populated with a count 1 in the Cube and when I get a change record, it has to trigger a record with negative key figure (-1) count to the cube and then add the change record with a new count 1, but its not triggering the negative record and at the same time triggering a new change record with count "0" which is really weird. Thereby throwing off all the key figure counts:
As an illustration:
Delta 1:
Transaction: 12345; Call Status: Open; Key Figure: 1
Delta 2:
Transaction: 12345; Call Status: Closed; Key Figure: 1
Ideally Data in Cube should be:
Transaction: 12345; Call Status: Open; Key Figure: 1
Transaction: 12345; Call Status: Open; Key Figure: -1
Transaction: 12345; Call Status: Closed; Key Figure: 1
But we have in cube:
Transaction: 12345; Call Status: Open; Key Figure: 1
Transaction: 12345; Call Status: Closed; Key Figure: 0
Deltas from ODS to Cube is extracted from the Change log tables. All the data movements are in delta mode. Don't know where and what we are missing or doing wrong. Any help is greatly appreciated.
Regards,
Vinay

Vinay,
It looks interesting to me. Can you please check the Changelog table and compare the entries? did you find before image entry with delta Load in Changelog? ODS should generate 2 entries with Delta record as we know. It's not generating entry with before image i guess.
I will try to put the same scenario in our system. Let us know what is the service pack you are on?
Note: I'm assuming you are working Standard DSO and In the Transformation Start or End routine youare not deleting Before Images.
Regards,
Nagesh Ganisetti.

Why editing iview id break the delta link in the portal page?

For some reason, everytime I edit the iview id, the delta link in the page will be broken.
After I changed the iview id, the iview id that I added as delta link in portal page remain same, and seems like become a separate copy , rather than the original delta link.
This frustracted me as I have to remove the old iview , and add the new edited iview into the page again.
Why is this happen? (I am very sure I didn't accidentally add the iview as copy, instead of delta link)
By the way, I am in NW04s SP9.
Thanks for help.
Kent

Hi Kent,
> (I am very sure I didn't accidentally
> add the iview as copy, instead of delta link)
The wording "I am very sure" points to the fact that you didn't really check and re-try it?!
I just checked it on NW04 / SPS18 (which corresponds to SP09 on NW2004s) - and it works like a charme. The delta-link on the test page points to the new ID (as the ID-Change-Wizard announces it).
As I have no 2004s installation at hand, I would suggest really to re-check if you are really talking of a delta-link. If it really doesn't work on SP09 while it works on SP18 in parallel, you would have to open an OSS message. Anyhow, this really should behave analogously...
Hope it helps
Detlev

BI Overview SAP course for NW2004s ? (BI 7.0)

Hi,
Does anyone know if there is a one day BI overview (introduction) course available at SAP education for release NW2004s (BI 7.0 ?)
I found the courses SAPBI and SAPNW but these seem to be for release 3.5 ?
If not, does anyone have a one day BI 7.0 overview course in PDF or PPT format ?
thx
Message was edited by:
Double U

Couple of months ago I took two courses at SAP on upgrade to BI 7.0, there was a 2 day course, DBW70E covering Enterprise Data Warehousing and a 3 day course, DBW70R, on Reporting, Query & Analysis.
These are delta courses, covering what has changed / added.

BI Statistics NW2004S Content - Virtual Info Provider 0TCT_VC01

Hi
We implemented BI NW2004S statistics for front end OLAP analysis which consists of info providers 0TCT_C01, 0TCT_C02. However, when we activated the queries, we are not seeing enough data in queries even though the info providers are loaded correctly. SAP has provided content for 0TCT_VC01 & 02 as virtual info providers which are used in multi providers -0TCT_M01 & M02 along with the base info providers mentioned above. All content queries are built on these multi providers and currently in our multi provider we have just base info providers but not virtual info providers.
Now my question is, on virtual info providers - These virtual info providers are based on DTP and am just wondering which data source I should use to maintain transformation as info provider based on DTP would require transformations to load the cube. I have used data sources 0TCT_DS01 & 02 to map transformations to base info providers 0TCT_C01 & C02 respectively.
Pls confirm on how I should use these virtual info providers as part of multi providers and which data source should I use to maintain transformation.
I am hoping that by including virtual info providers into the above multi providers, I would be able to see the data to analyze query performance during user navigations.
Appreciate your response.
Thanks

RSDDSTAT_OLAP->0TCT_DS01(data source)->InfoPackage->0TCT_C01(0TCT_MC01)->0TCT_MC01_Q*(queries)
The cube 0TCT_C01 gets filled from data source 0TCT_DS01 which is again gets data from the view RSDDSTAT_OLAP.
So whenever you run queries (3.x or 7.0) or templates (3.x or 7.0) or workbook (3.x or 7.0), this view gets filled.
So, you please schedule the releavant process chain or infopackage which will fill the cube 0TCT_DS01, then you will be able to use the queries built on this cube.These process chains are starting with 0TCT*.The installation steps and scheduling steps are very well explained in the note 934848.
P.S. SAP delivered queries are based on multicube 0TCT_MC01 (built on 0TCT_C01 and 0TCT_VC01) and not on 0TCT_C01
0TCT_VC01 Usage -
The purpose of virtual cube 0TCT_VC01 is to give delta data.
For ex, you would've scheduled the process chain for loading 0TCT_C01 every day in the mid-night. If you are running the query built on 0TCT_MC01 cube in the morning, you will miss the data from yesterday mid-night till today morning. To give this delta data, the virtul cube is used in the multi cube.
Hope it Helps
Chetan
@CP..

BW7.0 Delta question

Hi Everybody,
I am going to try to find an answer to my problem in this forum... the NW2004s one has few activity at the time...
It is possible to actualize from a PSA to a dataTarget in with a delta modus? or a need to implement (add) an ODS object for this purpose?
Thanks
FedeX

Thanks Sven,
when I am ceating the DTP I got a list to select the possible DataSources ... I get "Only" the DataSource on the Source System ( no DataSource PSA is there listed... no sure if they have diferent names) ....and selecting DELTA approach on DTP and then checking if the DTP is OK...I get:
Diagnosis
DataSource MyDataSource MySourceSystem uses delta processAIE, which is not suitable for direct updates into an InfoCube because the changed status of a record and not the change itself is transferred.
Procedure
Choose the Full Update update mode or write the request to a DataStore object first and then update it to the required InfoCube.
Note
A request in the update mode Initialization of Delta Process or Delta Update cannot be written directly to an InfoCube. When you try to save or update an InfoPackage that has this setting the following
error message appears:
DataSource cannot be uploaded to an InfoCube
I understnd the error if itis taking directly the information from the source system ...thing that I do not want to do...but I am not sure how can I adressfrom the PSA Datasource..
Thanks
FedeX

Now that we are on NW2004s...

We are just finishing up our upgrade from 4.6c to nw2004s and ecc 6.0. The issue is, we did a technical upgrade only. Will we still be able to use things like SCM, eWM, etc... all of the new, latest and greatest of toys, or will be have to do the functional upgrade first.
To be honest, i am unclear what the difference between the technical and functional upgrades are, and even what "version" we can consider ourselves to be at, having done only a technical upgrade (according to our basis team).
Any help, explanations, etc woul dbe appreciated and rewarded. I am kind of on a limb on this one. I have tried to read up and look at release notes, delta notes, etc, and can't get a firm handle on this.

Hello David,
If you need to use functions like SCM, you will need to insall a new SCM system. Based on my knowledge, you can't have SCM installed on the ECC system. But you can install CRM as an add-on in ECC system.
As for the new toys, you need to know if they can be running on ECC systems or not. If not, you will need a seperate system. Please be advised that some applications running on J2EE engine can be running on the ECC 60 JAVA stack too.
Regards,
Joe

K7N2 Delta lock ups

Hi there,
I've got a MSI k7N2 Delta sitting in my PC atm. But with a nasty problem. I have to keep the cpu sitting in it (AMD Barton 3000) underclocked for me to use my PC for more then 40 mins at a time. After that time, it just freezes, and the sound card (not system speaker) emits a nasty high pitched sound. Using a more intensive game, i.e. planetside speeds up the process, somethimes running for a mere 5 mins. To use the pc atm, the cpu is clocked at 1.4Ghz, instead of the over 2ghz it should be at.
Any suggestions anyone?
Specs:
K7N2 Delta
AMD Barton 3000+
512Mb Kingston DDR (on compatibilty list)
ATI Radeon 7500
SB! 128
Antec 400Watt PSU

ok, after some more testing (man i love CS ) it still locks up, but it took longer initially. It now just freezes, with no beeeep from the sound card. It may be temperature related though, as after the intial freeze, it will now only take a few minutes before it does it again. Straight after it freezes I'm getting temperature of around 50 on all monitors.
Ill whip out that TV card and give it a whirl now
p.s. case fans, i think one is in the wrong way, is the spinny side supposed to facing in the case, or out the case? cheers

Error while resetting the delta in ODS (BI 7.0)

Hi all,
I face a problem in delta resetting...need your help... Thanks..
I have an ODS-1 which has target cube1, cube2, cube3....One week back a new target has been added as ODS-2....All complete data from ODS1 has been piped into ODS 2..(Note.. ODS2 has many more inputs from other cubes/ODS too)
NO issues till now....
I found a data problem in ODS-1 which got loaded 15 days back..... I have removed all 15 requests from cube1, cube2 and cube3... Now I am trying to reset the delta in ODS1...
I am getting the following error....Infoprovide ODS2 still contains request... Delete this first....
Since ODS2 has many other data alongwith ODS1... If I try deleting request from ODS2,, I need to clean it totally and redo... I dont want to do this...
Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
Let me know your suggestions.... Thanks!
Regards
Ayyappan.V

Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
I dont think you can disconnect the link. just delete the requests originating from ODS1 in ODS2 and you can leave all other requests intact that are from other dataproviders and do a reinit.

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

Not getting delta master data after refresh

Hello,
We have just refreshed our QA (BW and R/3) environments from our production environments. It was a synchronized restore. We have done this multiple times in the past and have not run into this problem before.
Everything checks out fine - full master data loads fine, and delta transaction data loads fine, but our master data loads that are deltas retreive no data and produce the following message:
Selection conditions replaced by last init. selection conditions
Message no. RSM1036
Diagnosis
Selection conditions replaced by init. selection conditions.
No new selections can be made when requesting delta data from a 2.0 extractor.
Delta selections are composed of the total quantity of all the selections of all the sucessful init. requests for this DataSource.
I have looked this up here and in OSS. What I have found would indicate that we have multiple inits. However, when I look at the Initialization Options for Source System from within the infopkg, there is only one. Also, RSA7 appears to be fine on R/3.
Is there table or setting that may have been missed or some other place I need to check?
Any ideas or suggestions would be appreciated.
Thanks,
Kelley

Thanks, but I do not understand what exactly to look for in that table. What fields in that table should I check and for what?
I have compared rssdlinit on BW with roosprmsc on R/3 and they match. I have checked other tables too and they look fine.
There was a mistake made when the system was refreshed that may have caused this problem. That would at least explain why we are having this problem now and did not before.
I tested one of our delta master data objects (0material_text). I deleted the init from within the infopkg. Then I ran the infopkg to init with no data transfer. That appeared to work - resulting in 1 record which is normal for an init delta with no data. Then changed material text on R/3 and ran the infopkg with delta update. It still gave the same message that I listed in my first post, and it retrieved 0 records.
Any ideas?
Thanks,
Kelley

View data in Delta Queue (RSA7)

Hi,
We want to see data records available for extraction in delta queue.
Data source is 0CO_OM_NWA_2. In RSA7 it is showing 5 in total column for this datasource. When we select "Diaplay Data Entries (F2) , select update mode Delta and execute it is displaying "List contains no data"
How to view this data ?
Regards
SS

Hi,
Once you schedule the infopackage , it will pick up the data from RSA7 . Afterwards when you check the data in RSA7 by selecting update mode as delta - you won't find any records . but you can see the data in by selecting update mode - delta repetition - execute it. It will show the records which has been already transferred to BW side.
Update mode - repetition , will hold the data until the next delta is successful..
Hope i am clear..
Regards,
Siva.

Delta in NW2004s

Similar Messages

Maybe you are looking for