Convert Full datasource into delta

Hello,
We are facing a problem. We have a custom datasource that works as a full, because a delta is not possible on the sources tables in ECC (parked FI documents).
We need to convert this dataflow to a delta, because the dataflow will be crossed with other data (posted documents and more), and we don't want all our modell going full.
Is there a way in BI 7.0 to convert a full datasource into delta for further processing? I thought this functionality was available in BI 7.0, but could'nt find how to do it.
Thanks,
Philippe

Hi,
If the DS is not delta enabled try Fake delta or Pseudo delta.
Try to see if you can create a user exit at extractor level to select data based on some time stamp fields whcih will ensure that only changed or new records are coming into BW.
Refer
Fake Delta
Pseudo delta
Fake Delta
Data Recovery in delta loading
Hope this helps.
Thanks,
JituK

Similar Messages

Converting Full Load - Delta load

Hi Experts,
I am trying to convert ODS from Full Load to Delta Load.
The problem is already there are full req so its not allowing me to activate delta.
I have tried running the program "RSSM_SET_REPAIR_FULL_FLAG" which would convert full req into repair req and then I should be able to load Init/Delta.( see OSS Note 689964)
Problem is even after running the program succesfully I m getting same message and not able to activate Init.
I again tried running running the prog but now progr does nt show any req which could be converted to Repair req.
So how to proceed from here and Full load ODS -> Delta...???
All help would be appreciated and awarded by points...
Thanks in advance!!!
Sorabh

Hi Ajai,
I checked RSREQDONE; in tht Qm status of req is Green...I dont know what I shud check in this table..
Also as per my understandings loading thru reqs in PSA is another way (if the request still exist in PSA)apart from the program given.
Program shud work in any condition whether req is there in PSA or not.
Correct me if I am wrong..
but again struck ..on same issue...:)..
Thanks,
Sorabh

Full vs. Delta Load

Hi BI-Experts!
This is a rather general question.
Is there a recommendation when to use Full or Delta Load?
I know the functional differences but do SAP or some technical reasons say that each of them may only be used in special cases?
For example Delta Load can only be used with SAP source systems?
Best regards,
Philipp

Hi Philipp,
This is a pretty open-ended question. I will give you a few examples of when I use each ....
Delta's:
1.) If the record set is large and changes a lot daily. If you have a large initial load, let's say 2Million records and you get about 200k records per month, then you want to use a delta mechanism. There are just too many records to reload daily.
2.) If the record set is wide (many fields instead of a few), it will take less load time to run a delta than a full load.
3.) Datasource restrictions....some business content datasources don't have full loads and vice versa (some don't have deltas).
4.) Do my loads take too long? If so, I will convert full loads to delta's to shave off time here and there.
Full
1.) I gauge this mainly based on load time. If it takes 5 minutes to load 100k records, then it's going to take longer to figure out what delta's were missed (if there was a problem) than it would to just reload the dataset.
2.) Do my requirements dictate that I need to drop and reload the dataset? The best example of this would be the current year's forecast. Some companies revise the forecast and don't want to keep any previous revisions.
3.) Some data loads load a snapshot of a specific date. So, if I wanted to take a snapshot of inventory in a DSO/ODS on Monday, I would Datamart it into a Cube doing a full load for Monday's date.
Hope it helps!
Thanks,
Brian

Full load to Delta conversion of standard extractor

Hi Gurus,
Data have been loaded to Infocube from standard extractor( LO LIS) as a full load.Now I needs to convert full load to delta.Kindky throw your ideas, what are the points I have to be considered .
Thanks
Siva

HI,
For getting the Delta u have to first Initlize the Cube. the option is available at InfoPackage level.
After that only u can get the Delta.
that is only the Way.
Assign Point if it helps.
Regards,
sandeep

A Full DTP is converted into delta DTP and facing some data problem

Recently Full DTP(DSO to DSO) is converted into delta DTP , we are facing some data problem in first request.Some data in D2 are not updated properly after just converted in full to delta. Please let me know if you have any idea.
Example :
DSO : D1
DSO : D2
Previously FULL DTP D1->D2
Now Delta DTP D1->D2

Hi,
First time run of delta DTP will extract all the records from the source...
As u have already run the Full load and followed by delta,i guess u can use direct change log option...
rgds,

Problem with subsequent deltas after converting Full requests to Repair.

Hi All,
We are working on changing an existing system from loading from multiple extractors directly to a cube to loading each extractor to its own DSO and then combining the data in a 'consolidated' DSO and then on the the cube.
To avoid downtime in the production system when we do the cut-over we have decided to do full loads of historical data up to Sept 2007 and then do delta loading from then on.
So the steps so far have been:
1) Full load of data to low-level DSO's. to 09 2007.
2) Full load of data to 'consolidated' DSO.
3) Convert Full requests in consolidated DSO to Repair Full Requests (see SAP Note 689964).
4) Initialise Without Data Transfer to the 'consolidated' DSO.
5) Delta Initialise from 10 2007 from the source system to the low-level DSO's.
6) Delta from low-level DSO to consolidated DSO.
My problem is with step 6 - no records are loaded into the consolidated DSO after delta load of data to the low-level DSO - the load process runs correctly but tells me that there was no data available.
Can anybody see if there is a problem with my approach - I thought this was the correct way to convert from full loading to delta loading ?
A Merry Christmas and a Happy New Year to you all
Graham

Hi Siva,
Thanks for the reply.
I understand that there is only an active table with a write-optimised DSO - but delta processing should still be possible at the request level
(SAP Help on Write-Optimized DataStore Objects http://help.sap.com/saphelp_nw2004s/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm)
Since write-optimized DataStore objects do not have a change log, the system does not create delta (in the sense of a before image and an after image). When you update data into the connected InfoProviders, the system only updates the requests that have not yet been posted.
In my case the 'new' request loaded into the DSO have not been loaded into the connected InfoProvider, so it should be processed.
Regards
Graham

Generic Delta: Init, Full Upload and Deltas...

Dear All,
Last week on 10.04.2014 I've created "Generic DataSource with Generic Delta" and used CalDay as Delta-Specific Field and lower limit kept to blank and upper limit to 1. On 11.04.2014 I've initialized the Delta with Data Transfer using Process Chain: Time 1:15 p.m (Note: Posting was on)
see below screen shot:
Result: Process Chain was scheduled to immediate and it executed and initialized the delta and brought records as well. See below screen shot of RSA7:
Q: 1: Why generic delta current status is 10.04.2014, as I'v scheduled delta through process chain on 11.04.2014 @ 20:50: and why Total column is showing 0 records? Even I've checked Display Data Entries with Delta Repetition, but could not find any records?
Following is the InfoPackages which I created for Delta Loads and used in another Process Chain for Delta scheduled (daily @ 20: 50).
Following is the DTP used into Delta Process Chain:
On 12/04/2014 when I checked my InfoCube, and found that same number of records being loaded again despite InfoPackage and DTP were created as Delta, see screen shot:
On 12/04/2014 See below PSA table:
On 14/04/2014 when I checked InfoCube and I saw deltas being loaded successfully: see below screen shot:
On 14/04/2014 see below PSA table:
On 14/04/2014 see below RSA7 BW Delta Queue Maintenance screen shot:
Q: 2: Why am I unable to load the Delta records on the day(11/04/2014) when I initialized it with Data and why same number of records being loaded again on 11/04/2014?
Q: 3: On 11/04/2014, around 1:15 p.m I've initialized Delta with Data successfully and the same day (11/04/2014) was my first load of delta records (Time: 20: 50), could this be a problem? as the posting period was on when I initialized and I tried to load the delta on the same day?
Q: 4: Why the pointer is showing me Current Status: 12/04/2014 today and this time around I can find last delta records from "Display Data" option with Delta Repetition?
Q: 5: Have I missed something in the design or data flow?
Q: 6: How can I verify deltas records accuracy on daily basis; is it from RSA3?
or How can I verify daily deltas with ECC delta records?
Q: 7: What is the best practice when you load full data and initialized delta and schedule deltas for Generic DataSources with CalDay as delta specific field?
I will appreciate your replies.
Many Thanks!!!
Tariq Ashraf

I clearly got ur point.....But
If i have situation like ....." I loaded the LO data from R/3 with Init delta......then i loaded 5 loads of delta too.......due to some error in data now i am trying to load all th data......In this case if i do Full upload it is going to bring all the data till 5 th delta load .......If i do Init delta again it is going to bring the same data as full upload..........In LO while loading both Full load or delta init load we need to lock R/3 users....I believe we can load delta even after full upload by using "Init delta without data transfer"............So that wont be the barrier....then what is the difference or how should i figure out which load should i do.............If i am wrong please correct me.......
Thanks

Full Repair/Init/Delta & LO Cockpit Information required

Hello
I'm pretty new to BW and I'm starting to dig a bit more now into the deeper stuff now. I've created Cubes with Extractor from R/3 and now I'm interested to understand more the LO Cockpit various specificities.
For a better understanding, let's establish a scenario as --> Activation of R/3 SD Billing --> BW --> DSO --> Info Cube
Ok, first, let me start by explaining what my understanding is.
First, I need to go into R/3, t-code LBWE, and under the "13: SD Billing BW", activate the extractors I'm interested in (Header & Item as an example in my scenario). I'm also assuming that the default fields within the extractors are suiting my needs so no adjustments needed for now. I should also schedule a job here that will create records in the Waiting Queue on a daily basis.
Next, I need to fill the setup tables from the t-code SBIW; I enter a date in the future, it runs for a while, then I get my data prepared. In the setup table, it included all the existing R/3 invoices as of now right? (1) Let's say there are new invoices created minutes after I've created the setup table, they will be sent to the Waiting Queue as soon as the document are created or will the schedule job created earlier will post them to that Queue? (2) If the job send them to the Waiting Queue, where are sitting the pending documents before being sent then? (3)
Now, on my BW system, once the Data Source have been replicated, what do I need to create and execute to be able to proceed with a Delta process? (4) I know I have to create a u201CInitu201D package 1st but have no clue why except that itu2019s needed for me to be able to create a u201CDeltau201D package afterwards. Technically, what does the u201CInitu201D package really does? (5) What is the reason to have a u201CInit without datau201D and u201CInit with datau201D, I mean, I know literally what it means but again, why would I choose one over the other? (6)
Iu2019d also like to understand the concept behind a "Full Repair" request, which I have no clue what the purpose is. I guess there some of these properties (Full Repair, Init) determines where to get the data on the R/3 side; Setup Tables or Waiting Queue? (7)
Please, provide clear respond (Donu2019t assume I know what youu2019re think of ) on my questions (identified by a bold number) and don't hesitate to provide a long one if needed to; it's better to provide more information than not enough
Thank you in advance for all of your help!
P.s. I'm working with BI 7.0.

Hi.....
So if I understand properly, whenever I run the init, it toggle a flag on my source system (R/3) which means that all changes performed in the invoices are going to be sent in the Delta Queue? Until I run an Init, changes are not written anywhere (Other than internal SAP tables/structures required by R/3 Invoices processes).
If so, does this means that I could loose some transactions from the time I run the creation of the setup tables and the time I execute the Init on my BW system? Let's say I create the setup table today and execute the init only tomorrow; all invoices that have been created by this time won't be tranferred to BW?
yes,suppose you create a set up table today....and ron the init tomorrow........in between many new recordsmay come.......but those new records will not be in the set up table.......since those transaction happenned after the filling of the set up table........and new records only goes to Delta queue after you run the init.......
I have to admit that it's hard for me to "Suppose" i did not want to do an init; what would be a good reason not to? I understand that both Init types will toggle the "Init" flag on but still can't figure appropriate business scenarios for both types
Suppose your Delta mechanism is corrupted.......for which you need to do a full repair......I mean first ,you have to delete the existing init flag.........second, you will fill the set up table .......third,you will load the records by Full repair......then 4th step will be running init without data transfer..only to set the init flag..........it will not pick any records.............then delta.......
Init with data transfer picks all the previous records......we cannot give any selection..............for selection we have to use Full repair.........then init without data transfer..............generally for Transaction data we will go for Full repair..........bcoz otherwise number of recordswill be very huge........and there may be duplicate records..................
Another thing we want to say........we do full repair we mainly use for ODS.........it is just like Full upload.........in case of infocube we can use full upload instead of full repair.........but in case of ODS full repair is must............since ODS does'nt support Full upload and Delta upload parallely........otehrwise ODS activation will fail........
Then again you hav to use the Program : RSSM_SET_REPAIR_FULL_FLAG to convert full upload request to full repair request.....
Hope this helps....
Regards,
Debjani.......
Edited by: Debjani Mukherjee on Nov 7, 2008 10:45 PM

Can one datasource supply delta to more than one data targets?

Can one datasource supply delta to more than one data targets?

Hi Alok,
You can assign only one infosource to one datasource but you can feed any number of data targets based on the requirement from that Infosource. It can be either Delta or Full load. But to do Delta, initially you need to do INIT and then go for Delta. If you have already done full load into a data target, you can go for INIT w/o data transfer there after continue with Delta.
Hope this helps u...
Regards,
KK.

Change load full data to Delta

Hi!!
In the past, we load Full data for a customized DataSourece. Now I changed the DataSource to load delta datas.
This data source was connected a ODS and when I tried to initialize delta process I received the error message. "Full updates already available in ODS 0SAL_DS01 ; Cannot update init./delta".
Someone know, How can I Initialize Delta Process?
Regards,
Cesar G. Batista

Hi.............
ODS does'nt support Full upload and delta upload parallely..........suppose a ODS is getting loaded with delta upload...........then if u do a full upload.........then ODS activation will with this error...........then u have to convert full upload to full repair...........
Go to SE38 >> Program : RSSM_SET_REPAIR_FULL_FLAG...................this program also exists in 3.5.............check it properly............
Check SAP note 689964 ........
Hope this helps........
Regards,
Debjani.........

BI7 : Change full load to delta load - things to do?

http://wiki.sdn.sap.com/wiki/display/profile/2007/04/30/Differencebetweenfull,intialanddeltaupdatemodes
Difference: Full load, Delta Load & INIT load in BW
Hi.
Since am not familiar with BW request clarity as to how to achieve the following :
We are on BI 7.
On our BW server, One of the Existing process chain loads data as full load daily Till date.
This schedule runs for about 4 to 6 hours during the nights. And the data seems to be growing.
And doing full load, now seems, not that meaningful for data analysis.
So we now feel we need not do a full load every day. But do only the incremental load.
How to make this effective in our existing process chains.
I went thro the 2 links above, but a few things am not clear.
What exactly needs to be done to change a full load into a delta load.
Also do not wish to have any data loss happening.
We run the schedules on a particular process chain for BW around 1 am.
Say from tomorrow I want to have the data loading as delta.
What exactly are the steps to be followed.
Precautions to be taken
So that we have the correct data load and no data is lost - while doing this.
Things to do am not clear :
do initialization with data transfer / or without data tranfer ?
The make it delta?
So that from tomorrow all data loading becomes delta ?
Or
since in our scenario,
daily basis it is full load.
Just make it delta load,
so that whatever changes will run in the next days schedule.
What all things are to be done stepwise.
if anyone could advise.
That would be very helpful.
Also any documentation which explains all these if someone could share the link please ?
Many thanks
indu
Edited by: Indumathy Narayanan on Aug 26, 2011 5:50 PM

Hi,
Kindly look at following links as well
http://help.sap.com/saphelp_nw04s/helpdata/en/44/9821620553053de10000000a1553f6/content.htm
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.
Thanks and regards

Trick BW into delta

Hi all,
I have loaded in full from one ODS into another instead of running an initialization.
As this full (initial) load takes a whole weekend to run, I would like to trick the BW system into accepting delta's from now on. Is this possible?
Update: I think there are two options:
- initialize without data transfer (what does this do?)
- create a new init (based on changed on and created on date --> both fields available) Is it possible to make an or selection in the infopackage?
thanks for the answers,
Tom
Message was edited by: Tom Francis

tom,
let me explain the options you have presented:
- if you initialise without data transfer at this point, the system sends a delta marker (of sorts) telling the target ODS that you want to collect the deltas, but have no need for the actual init delta loading. you'll have to do something about the full upload you've done though, since a full upload won't co-exist with an init delta (and vice versa). run program RSSM_SET_REPAIR_FULL_FLAG (via SE38, as described in SAP Note 689964) to convert your full update into a repair full request. after you init delta, you should be able to capture any change to any data that you have loaded in already.
- if you trigger an init delta update with a date range, that's fine, but any changes to the full update won't be tracked by the delta anymore. you will have to contend with the problem with co-existence anyway though.
i don't quite understand the exact nature of your problem, but i think you'd be better off doing option 1. make sure that there are no transactions in your 1st ODS between the init w/o data transfer and the full update okay?
you could check the thread i had on a similar problem here:
data extraction via combination of full + init updates
ryan.

Converting oracle forms into java forms

Hi all,,
would help me plz on how to convert oracle forms into java using any tool;
Is Jheadstart is the tool,, im having jeveloper version 10.1.2.1.0

There are at least two companies that are marketing Forms to Java conversion tools. I'm sure that a good Google search will locate them, and they are frequent exhibitors at Oracle-oriented conferences like Collaborate and ODTUG Kaleidoscope. But there are problems associated with doing this. I urge anyone who is considering such a project to read this article by Grant Ronald: http://www.oracle.com/technology/products/forms/pdf/10gR2/formsmigration.pdf
You should carefully ask yourself and your clients and management, "Why do you want to do this?", "What benefits are you trying to realize?", "Does this make sense, and are there other options that we should be exploring?"
For instance, many people are trying to protect themselves because "Forms is going away". Oracle has stated again and again that Forms is NOT going away. In fact the recent Fusion Middleware 11g release included a new version of Forms with some significant enhancements. You may do very well just by upgrading to the latest version of Forms.
If you do decide that it still makes sense to convert, I suggest that rather that converting, you may want to redevelop from scratch. Keep the database if it is well designed - a well designed, stable database will outlast any front end that you may use against it. Then take full advantage of the capabilities of your new toolset, and leave behind the limitations and inapplicable methodologies of your old one. Oh, by the way, don't use JDeveloper 10.1.2. Use 11g if you can, or 10.1.3.5 if you must.

Convert abap reports into crystal reports

Hi,
We are trying to convert abap reports into crystal reports.We could convert these reports into XML files
Now we want to create utility which will automate the conversion of XML files into RPT files of crystal reports.Later on we can refresh the data in reports by changing the datasource location.
Can you please guide us whether it is possible and if yes how should we go about it?
regards,
shital

Hi, i suggest, 2 technies to do this, the first one, you can use,
CALL METHOD CL_GUI_FRONTEND_SERVICES=>EXECUTE
EXPORTING
    APPLICATION            = 'C:\Program Files\crystalreports.exe'
EXCEPTIONS
    CNTL_ERROR             = 1
    ERROR_NO_GUI           = 2
    BAD_PARAMETER          = 3
    FILE_NOT_FOUND         = 4
    PATH_NOT_FOUND         = 5
    FILE_EXTENSION_UNKNOWN = 6
    ERROR_EXECUTE_FAILED   = 7
    SYNCHRONOUS_FAILED     = 8
    NOT_SUPPORTED_BY_GUI   = 9
    OTHERS                 = 10.
where, exe file could be, a crviewer.exe, and, use a parameters ( on exe ) to indicate rpt file, or, define of standar mode, a generic name and put, xml file generated via abap, on a repository, this way, rpt file, when launched, displaying file.
the second choice, could be, go SM69, click create. enter a command name 'ZCREXE', enter the path and the exe file name in operating system command field. You can call this exe from ABAP using SXPG_COMMAND_EXECUTE.
i hope so that my answers help you.
greetings.

How do I convert a JPG into PDF, Adobe converter not available in India yet ?!!!!!

How do I convert a JPG into PDF, Adobe converter not available in India yet ?!!!!!

Hi supersude,
You can use Acrobat XI Pro software for converting jpg into pdf, Here's the download Link (Free 30 Days trial ) : https://helpx.adobe.com/acrobat/kb/acrobat-downloads.html
You can buy the full version here : Adobe Store - Adobe Acrobat Professional XI
Regards,
Rahul

Convert Full datasource into delta

Similar Messages

Maybe you are looking for