Loading through Process Chains 2 Delta Loads and 1 Full Load (ODS to Cube).

Dear All,
I am loading through Process chains with 2 Delta Loads and 1 Full load from ODS to Cube in 3.5. Am in the development process.
My loading process is:
Start - 2 Delta Loads - 1 Full Load - ODS Activation - Delete Index - Further Update - Delete overlapping requests from infocube - Creating Index.
My question is:
When am loading for the first am getting some data and for the next load i should get as Zero as there is no data for the next load but am getting same no of records for the next load. May be it is taking data from full upload, i guess. Please, guide me.
Krishna.

Hi,
The reason you are getting the same no. of records is as you said (Full load), after running the delta you got all the changed records but after those two delta's again you have a full load step which will pick whole of the data all over again.
The reason you are getting same no. of records is:
1> You are running the chain for the first time.
2> You ran this delta ip's for the first time, as such while initializing these deltas you might have choosen "Initialization without data transfer", as such now when you ran these deltas for the first time they picked whole of the data.Running a full load after that will also pick the same no. of records too.
If the two delats you are talking are one after another then is say u got the data because of some changes, since you are loading for a single ods to a cube both your delta and full will pick same "For the first time " during data marting, for they have the same data source(ODS).
Hope fully this will serve your purpose and will be expedite.
Thax & Regards
Vaibhave Sharma
Edited by: Vaibhave Sharma on Sep 3, 2008 10:28 PM

Similar Messages

How to stop the data loads through process chains

hi,
I want to stop all the data loads to BI through Process chains where load happens periodic.
kindly suggest how can I proceed.

Hi,
Goto RSPC find your PC and double click on START then change the timings, i.e. give starting date is 01.01.9999 like that Save and ACtivate the PC, it won't start till 01.01.9999.
Thanks
Reddy

Automate loads through Process Chains

Hi,
I have two Infocubes, one a delivered one and the other a custom one. The delivered one should be loaded everyday and it is a full load (we would delete its contents completely and reload every night). The custom cube is an exact replica of the delivered one and is also a full load from the delivered cube. But the custom cube stores monthly snapshots of the data and is hence loaded only on the last day of a month.
I want to automate the loads to both these cubes by creating Process Chains. How do I do it? The catch in this is if the load to standard cube fails on last day of month, then the load to snapshot cube should not be triggered at all.
Also note that we are using BW 3.5.
Thanks.

Another thought:
Make two chains - Daily and MOnthly...
In daliy chain: your deliverd cube will run...
In monthly : your daily and afer tht "On Success" - monthly load will happen..
Note that you need to keep start variant fro both chains accordingly and daily chain should not run on 1st day of month when monthly chain would run..
hope it helps
thnx for any pts

Data Load Requirement through Process Chain

Hello All,
I have implemented an area through a custom data source and following is my data load requirement through Process Chain. Request you to kindly help me for the same.
1. The design is an InfoCube and updated using a Transformation through the custom data source.
2. For the entire year 2008 I want a single request to be loaded. So it gets loaded into the PSA and then into the Infocube through a (Delta) DTP.
3. Now, I have created an InfoPackage (Full Update) with year as 2009 in the selection. Tht is I want tht hencforth the data load should be for the year 2009.
4. Hence, the Infopackage will run to bring the 2009 data into PSA and I run the (Delta) DTP to update the same in the Cube.
5. Now, what i require is everyday the InfoPackage (Full Update) with 2009 should run and bring data into PSA. and the same should be updated in the InfoCube after deleting the 2009 request already present keeping 2008 request loaded previously intact.
I hope the above is nt confusing.
Please let me know if i can elaborate the same.
Thank you.
Regards,
Kunal Gandhi

Hi,
Please go through the links.
http://help.sap.com/saphelp_nw04/Helpdata/EN/21/15843b74f7be0fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/Helpdata/EN/f8/e5603801be792de10000009b38f842/frameset.htm
http://help.sap.com/saphelp_nw04/Helpdata/EN/b0/078f3b0e8d4762e10000000a11402f/frameset.htm
These may help you in designing the process chain as required.
Regards,
Sunil
Edited by: sunil kumar on Apr 17, 2009 6:20 PM

Init load, delta load and full load

Hi BW,
Please when can I use init delta, delta and full load in a data load process.
Which of them is suppose to be in a process chain and which one is manual.
Regards.

Hi,
When you want to run delta, you have to initialize it first, thats when you run the init delta.Here you have 2 options with data transfer and without data transfer. If the data target is empty and there's no data, you can run the init with data transfer. This'll act as a full pull and also set up the initialization. If there's data already present, then you are better off running the init w/o data transfer. This dosen't pull over any data, but just sets up the initialization.
Then you can start using the delta pulls.That'll just bring over the changes and any new records rather than the whole data and is much more efficient.
You can use full pulls for say generic datasources that are not delta enabled or during a first time data load, or if there is a specific business requirement that needs you to pull over the full data everyday. Or in cases where the std datasource is not delta enabled.
Cheers,
Kedar

DTP Delta and Full Load...

Dear All,
I'm working with SAP BW 7.3 and I have a standard data flow, starting with DataSource, DSO and InfoCube. My process chain faced an error and for last week or so I could not fetch deltas. To remove the error I had deleted all records from InfoCube, since I had all requests available into DSO. Then I manually loaded Full Load from DSO to InfuCube. But next day when my process chain executed it brought all precious and new records again into InfoCube, as the delta was properly fetched into DSO but it did not come into InfoCube, as it was coming before. When I checked Active and Change Log tables of DSO these two had same number of records.
1. What could be the reason that delta DTP between DSO and InfoCube is not fetching only delta records, it was fetching deltas records before full load?
2. Have I made a mistake or missed any setting in DTP while executing full Load DTP between DSO and InfoCube?
3. What are these options for in Extraction Tab of DTP and when we use following options and why:
    i.   Active Table (with Archive)
    ii. Acitve Table (Without)
    iii. Archive (Full Extraction only)
    iv. Change Log
I will appreciate your reply.
Many thanks!
Tariq Ashraf

Hi Tariq,
Please check the below:
Delta Init. Extraction from
Active Table (with Archive)
The data is read from the DSO active table and from the archived data.
Active Table (Without Archive)
The data is only read from the active table of a DSO. If there is data in the archive or in near-line storage at the time of extraction, this data is not extracted.
Archive (Full Extraction Only)
The data is only read from the archive data store. Data is not extracted from the active table.
Change Log
the data is read from the change log and not the active table of the DSO.
Hope this answers your question. Let me know if any required.
Regarsd
Ramesh V

BW Delta and Full load

Hi !
This is a simple question with BW 3.5 :
A standard extractor with Delta is extracting everyday delta to 1st level ODS -> 2nd level ODS -> Cube.
Now i want to add 2 ODSes in same flow and they should also catch all these delta. Along with that I want to load for remaining period of this month (ex. Full load from 1st to today of the month and then onwards delta)
So new structure would be
0CRM_SALES_ACT_1 -> Level 1 existing ODS delta -> Level 2 existing ODS Delta
-> New level 1 ODS with delta -> New Level 2 ODS with delta
Can you please let me know how to do that ?
Full , delta info package ?
(FYI - i loaded full load for history and then tried delta, but delta failed saying Full load is already there in system)
Please do not post duplicate threads
Edited by: Pravender on Apr 12, 2011 7:08 PM

Partik,
My suggestion is load data from exiting Level 1 DSO to 2 New DSO's instead of loading directly from source to New DSO's.
To do that... removed initialization from Level1 DSO to 2nd level DSO and Re-Initialize WITHOUT data transfer by considering new DSO's also and continue delta's.
Use full load infopackages to load historic data from Level 1 DSO to 2 new DSO's.
Flow now should be:
0CRM_SALES_ACT_1 -> Level 1 existing ODS delta -> Level 2 existing ODS Delta
Level 1 existing ODS delta -> New DSO's
If FULL loads already there in DSO's further delta's wont work. Convert FULL loads to repair full load using Program: RSSM_SET_REPAIR_FULL_FLAG.
Then continue delta's.
Hope it Helps
Srini

Delta Load and Full load

What is the difference between delta load and full load?when are they used?

Hi,
Delta loads - Brings only the changed or newly added data to the data target...
Full loads - Brings all the data whether it is old, new or changed data to the data target...
Full loads are usually used to load master data since it wont change in course of time and delta loads are used when there are large amount of data to be extracted from the source system. It entirely depends on the requirement...
Regards,
Kishore

Problem with loading in process chain

Hello all,
I've a problem with my process chain. There are few loading packages that are suppose to start together. Problem is, I guess, not enough processes to start them all together. What happens is that some start loading where others "wait". In SM50 I can see all processes are taken. When the loading of the first pacakages is finished (and I can see processes available in SM50)
I'm expecting the load of the waiting packages would start, but nothing happens and the process chains stucks!
The infopackage load gets a yellow color, and stays that way, no cahnges , and no start of process, can someone help? anyone encountered that before?
Thank you,
Yoav Ophek.

Hi,
Monitor the InfoPack Loads through the T-Code RSMO.
When u select a Job, go to EnvironMent ->tRFC -> In Source System / DataWarehouse, and check if there are any Stuck tRFC's due to which the loads are stuck.
I do not see any other reasons why the Loads would be stuck.
Also check ST22 for any Short Dumps occurred for that time.
SM21 for Job Overview.
And check what else could have been the problem for not loading the InfoPackages.
Hope it helps,
Pradip Parmar

Full Load" and "Full load with Repair full request"

Hello Experts,
Can any body share with me what is the difference between a "Full Load" and "Full load with Repair full request"?
Regards.

Hi......
What is function of full repair?? what it does?
How to delete init from scheduler?? I dont see any option like that in infopackage
For both of you question there is a oss note 739863-Repairing data in BW ..........Read the following.....
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
Other terms
Restore data, repair data
Reason and Prerequisites
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets.
And also search in forum, will get discussions on this
Full repair loads
Regarding Repair Full Request
Instead of doing of all these all steps.. cant I reload that failed request again??
If some goes wrong with delta loads...it is always better to do re-init...I mean dlete init flag...full repair..all those steps....If it is an infocube you can go for full update also instead of full repair...
Full Upload:
In full upload all the data records are fetched....It is similar to full repair..Incase of infocube to recover missed delta records..we can run full upload.....but in case of ODS does'nt support full upload and delta upload parallely...so inthis case you have to go for full repair...otherwise delta mechanism will get corrupted...
Suppose your ODS activation is failing since there is a Full upload request in the target.......then you can convert full upload to full repair using the program : RSSM_SET_REPAIR _ FULL_FLAG
Hope this helps.......
Thanks==points as per SDN.
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Oct 23, 2008 8:32 PM

Need help in triggering the Data stream load using process chain

Hi Guru's
is it possible to trigger a data stream load using process chain?
Any help is highly appreciated.
Thanks
Indiran

Hi Indiran and welcome aboard!
Don't think this is possible. SAP BW & SAP SEM-BCS are rather independent systems. Though, BCS lives on top of BI-BW stack, it even may have master data different from those in BW.
Process chains, AFAIK, is completely the BW's feature. Certainly, you may use PCc on BW side, loading ODS/DSO and cubes involved in BCS data model.
The main con here is the lost transparency -- you don't control everything from the consolidation monitor.
The pro side is also rather obvious for me. Since, very often there is a huge difference between data quality at the data source and in the BCS totals cube, I need to make a lot of data transformation. Not only some data calculations or cleaning, but also transformation of data model: key figure model -> account model. It's much more easier to do in BW, for me.
I even call the ODS/cubes/routines involved in such transformation as intermediate layer, the layer between data source and SEM-BCS.
And this layer lives rather independently from BCS.
Hope this helps.

Diff b/n Repair full and Full load

Experts
Please explain diff b/n Repair full request and Full load.
If I do Repair full request instead of Full load ,is there any problem in the data ?
Many thanks
Manoj

Hi Manoj,
You can use a request that was selected as a repair request via Scheduler ® Repair Full Request to carry out a full update in any data target. This also applies to data requests that already contain data from an initialization run or deltas for this DataSource/source system combination, and that have overlapping selection criteria.
The difference between a Full Load and a Full Repair load is only evident in the case of loading to an ODS (to which you are also loading Init and Delta from the same datasource). If you ODS has the Init request active and you load a Full request, the data will not be activated. You should always use a Full Repair request when you want to load a full load to the ODS. For a cube it does not make a difference as the sequence of data loads is in important in a cube.
If you have accidentally not marked the request as a repair request, you can convert is using SE38 > RSSM_SET_REPAIR_FULL_FLAG
Hope this helps...

Diffrance between full repair and Full load .

hello ,
could you please let me know , what is the diffrance between full repair and Full load .
Regards

Hi,
Full Repair :
If you indicate a request in full update mode as a repair request, then it is able to update that request in data targets even if they already contain data from initial runs or deltas for this DataSource / source system combination and with overlapping selections.
Consequently, a repair request can be updated to ODS without checking the sequence of delta requests. The system supports loading in an ODS object by using the repair request without having to check the data for overlapping or request sequencing.
Full load :
Pulls the entire data from the source system to the BI system
Assign points if it helps
Thanks & Regards
santo

Delete and full load into ODS versus Full load into ODS

Can someone please advise, that in the context of DSO being populated with overwrite function, would the FULL LOAD in following two options (1 and 2) take the same amount of time to execute or one would take lesser than the other. Please also explain the rationale behind your answer
1. Delete of data target contents of ODS A, Followed by FULL LOAD into ODS A, followed by activation of ODS
2. Plain FULL LOAD into ODS A (i.e. without the preceeding delete data target contents step), Followed by activation of ODS
Repeating the question - whether FULL LOAD in 1 will take the same time as FULL LOAD in 2, if one takes lesser than the other then why so.
Context : Normal 3.5 ODS with seperate change log, new and active record tables.

Hi,
I think the main difference is that you with the process "Delete and full load" you will only get the full loaded data inside the dso. With full load you the system uses the modify logic (overwrite for all datasets already in the dso) and insert for all new datasets which are not inside yet inside the dso
Regards
Juergen

How to do a Delta after a Full load for an ODS

Hi all,
How to do set up a delta after a full load for an ODS ?
Thanks
S N

Dear SN,
When ever you already have some Init Requests and Full Requests , your Delta will not be activated for the ODS.
Now Just use RSSM_SET_REPAIR_FULL_FLAG to make all your Full requests in to Repair requests. then go to IP Delete your Init Req, Then load a Init Req without data transfer if you feel that all your history till date is available or else, you can always load Repair requests, by setting the same in the Infopackage -->Scheduler in the menu , for all your history data .
Hope this helps.
Thanks
Krish
*Assigning points is way of sayin Thanks in SDN

Loading through Process Chains 2 Delta Loads and 1 Full Load (ODS to Cube).

Similar Messages

Maybe you are looking for