DELTA Load gives wrogn values Where as FULL load gives right for FI Report.

Pls help!
I am trying to calculate Opening Balance for FI AR postings for which i have coded in end routine in Transformations.
The new fields OPENING BALANCE CREDIT/DEBIT get values from my routine.
However the problem I am facing is,
I only Get Correct VALUES for the OPENING BALANCE only when I DO FULL LOAD.
If i do delta load ,i get wrong values.
Thank you for reading.

Hi,
When you make delta load, you are just getting unexisting FI data. But I think that you need all the data in the cube to calculate the opening balance for the day.
Therefore, I don't think that delta load is a good way if you calculate Opening balances.
If you want to use delta load , fill the cube and then create another cube being filled from that cube(which is loaded with delta) and implement your routine between this two cubes.
Hope this helps.
Thanks

Similar Messages

Generic Delta based off TimeStamp field is extracting full load

I have a generic delta in place which is extracting a full load every time instead of only extracting the changes.
I have created a generic delta based off a timestamp using a "Last Changed by" field of type Dec15, format YYYYMMDDHHMMSS.
This datasource is populated via a FM which is only used to update two fields, all other fields (including last changed by field) are taken straight from the source table. Entries to the last changed by field are entered like this:
20080310021530, then show up like this: 20,080,310,021,530.
All relevent entries are showing in the tables ROOSOURCE, ROOSGENDLM, and ROOSPRMSC. There is also an entry in RSA7, status Green, Total = 1, and Status is showing the correct Delta relevent field as well as the correct timestamp of the last extraction.
The entry in ROOSGENDLM contains:
Current Pointer Repeat Pointer
20080320091503 20080320091653
Yet every time I extract a "delta" from BI, it pulls a full load.
Does anyone have an idea of how I can get the generic delta to work properly? I'm using 7.0 transformation/DTP. This field in BI uses a routine to convert the timestamp to a date field. Any help is greatly appreciated.
Thanks!

I think I found the issue. This timestamp is UTC timestamp, and until we implement SP13 (which is being onboarded in a week), this type of timestamp is not delta-relevent. Only timestamps on the local application server are delta-relevent pre-SP13, which can cause issues if the time is updated in a different timesone (to the east) of the application server.
The following note corrects this issue:
1073871
Edited by: Cote Adams on Mar 20, 2008 4:59 PM

OUTGOING PAYMENT ROW INFORMATION WHERE IS IT STORED. NEED FOR A REPORT

OUTGOING PAYMENT ROW INFORMATION WHERE IS IT STORED. NEED FOR A REPORT

Try this thread:
Query for outgoing payment
Thanks,
Gordon

Value of Infocube and ODS Line Item for a Reporting User.

Hi,
I want to give authorizatoin to a reporting user for InfoCube as well as ODS Line Item . I tried give values of InfoCube as well as value of ODS Line Item in Auth. Object "S_RS_COMP" in the field of Infocube. But it only accepts the value of Infocube. Then where shall I specify the value of ODS Object.
Please guide
Sam

Hi Suneel,
Thanks for your reply.
Do you mean to say the check box in RSA1->EDit ODS Object->Settings->BEx Reporting ?
If you mean the same one, then it is already checked. But still am not getting the ODS Names in Infocube field of S_RS_COMP.
Regards,
Sam

Give difference between full load, delta load, repair full load

Can i run full update after delta load?? if yes tell me a scenario??Can anyone tell me the difference between all three & when to use these??
Regards,
Asish

Hi,
For Repair full load please check OSS note 689964 which is about repairing the full load by executing the program RSSM_SET_REPAIR_FULL_FLAG.
Basically in this you provide your ODS, Data Source and Source System name and execute the program RSSM_SET_REPAIR_FULL_FLAG and hit Repair full load.
It will repair the full load.
But after this you cannot go directly for delta load which is for new added records or changed records. Before delta load do initialization without data loading and then go for delta load.
So delta load will run after init run (without data transfer) and add new added record or changed records to exisitng full upload records.
Technically you cannot go for delta load with out init load.
So, If you have already done full load, you can go for delta load after doing initializing (init load) without data loading.
Hope it helps.
Regards,
Mona

Full load works, but delta fails - "Error in the Extractor"

Good morning,
We are using datasource 3FI_SL_ZZ_SI (Special Ledger line items) to load a cube, and are having trouble with the delta loads. If I run a full load, everything runs fine. If I run a delta load, it will initially fail with an error that simply states "Error in the Extractor" (no long text). If I repeat the delta load, it completes successfully with 0 records returned. If I then rerun the delta, I get the error again.
I've run extractions using RSA3, but they work fine - as I would expect since the full loads work. Unfortunately, I have not been able to find why the deltas aren't working. After searching the Forums, I've tried replicating the datasource, checked the job log in R/3 (nothing), and run the program RS_TRANSTRU_ACTIVATE_ALL, all to no avail.
Any ideas?
Thanks
We're running BW 3.5, R/3 4.71

And it's just that easy....
Yes, it appears this is what the problem was. I'd been running the delta init without data transfer, and it was failing during the first true delta run. Once I changed the delta init so that it transferred data, the deltas worked fine. This was in our development system. I took a look in our production system where deltas have been running for quite some time, and it turns out the delta initialization there was done with data transfer.
Thank you very much!

Differentiating factor between delta and full load

Hi All,
I have a requirement where i need to abort the load if it is a delta. Currently we are doing a full load . I need to write an ABAP code for this, but what is the factor(field) to decide whether the load is full or delta ?

If it is an update rule, field g_s_minfo-updmode should have what you look for.
I am not sure of your requirements but this seems inefficient.

Change from Full load to delta load.

Hi Gurus,
I have one ODS object which is extracting data from r/3 system.this ODS object is getting loaded on a daily basis,& it's having heavy volume data (takes almost 8 hours to load).
Now I want to change the load mode of that ODS from FULL load to Delta Load
How can I do that ?
I tried to do* Init without data transfer* from source to this ODS obejct , but while activation it's saying Full load is already loaded so no init
I want to change the load mode of that ODS object without deleting the data,as it takes lot of time to load the total data.
Is there any way to that??
Plz help.Thanks in advance.
Regards,
Kironmoy Banerjee.

RSSM_SET_REPAIR_FULL_FLAG.
1 more question,if run that function module,will it change the existing loads in Repair full mode?
or it will load the total data again.
If you run RSSM_SET_REPAIR_FULL_FLAG Program and give ODS name etc.. it will turn all Full loads to Repair full mode.
Steps:
1. Run that function module.
Run Program RSSM_SET_REPAIR_FULL_FLAG
2. give ODS,data source name.
Yes
3 it will change the existing load to repair full load,
Yes
4.Init without data transfer. (i am not sure if this step is required or not.)
Yes
5.delta load.
Yes
Thanks
Reddy

Init & Delta After Full Load

hii Experts
I have one doubt please clarify that.
If i have a Cube and i m pulling data on basis of Full Load . Then i switch to delta load, before that i took the INIT load without data transfer.
But after a couple of days i need to pull the full load again for that particular period, for that i delete the INIT request & also the Delta request from Cube & PSA. & after full load i want to pull the delta load.
Now my doubt is how does this process impact on loading process?Is the previous init & delta also have some impact on the current delta loading???
Thanks in Advance
Neha

Hi,
There is absolutely no problem in doing a full loaf after init delta.
doing full load doesnt disturb the delta status.
Here i explain how an init and delta works
Init and Delta :
Once you are done with fetching all data from source using fullload, you have to run init.
all the new records that appear in the source system after init will sit in the delta queue.
when ever you run delta after the init, all the new records will coime to Bi and once this delta runs succesfully, these records will be cleared from the queue in source system and the new records from then comes to the queue.
this way, we can be sure that there is no loss of data.
Full load after delta :
now comming to your answer, if you run a full load, the data is not fetched from the delta queue and it doesnt disturb the queue in any way. it only brings all the data from soure(according to selection condition). so the delta is not disturbed in any way.
Repair Full Request :
The repair full request acts in the same way as full load in fetching data from source.
the only difference is in updating the target.
Rather than updating the data in the request, it checks out for the changes in already loaded data and update if there are any changes (Repairing the data already loaded.
That means there is no impact of previous init without data transfer in the current delta loading?
If you go thru the above explanation you can get this answer easily.
Init is used to set the delta pointer due to which the present delta is working fine.
Hope this answer helps you,
Thanks and Regards,
Srinath.

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

Process chain for a full load failed

Hi,
I have a process chain where load data from an InfoCube to a DSO with the following steps:
Begin
Load data: Execute an Infopackage with full load.
Update from PSA
Activate Data: Activate data of DSO.
When I execute the process chain, the step of execute InfoPackage succes, but the step of Update from PSA failed. If I saw the errors, I can see that when the infopackage finished need to Activate the data of DSO, and the status of the request is yellow and to Update from PSA need the QM status was green. What can I do? The data transfer correctly to the DSO but not is active.
Thank you very much.
PD: May be, some steps and options are not exactly like I wrote them but I'm working in Spanish and the meaning is the same

Hi....
Look if Update from PSA has failed......then go the details tab in the IP monitor.........expand the failed data packet and see the error message........there may be several reasons .......try to solve that issue............ then delete the request from the target without making the QM status red.......the reconstruct the request................
Actually I am not getting you clearly....I think your process chain is fine......Are you trying to say your ODS activation also failed...........but how ODS activation will start..........the load itself failed.........Is the link is on success or failure....
Regards,
Debjani....
Edited by: Debjani Mukherjee on Oct 16, 2008 2:02 PM

Initial Load/ Full Load

Is there a Diffference Between Initial Load and a Full Load?

Hello Xcaliber,
There is a difference if you put it in the context of delta loads.
The initial load will do a "full load" on some selection and after that, delta loads can take place.
A full load will do a full load but you can not perform delta load (except if you are doing a pseudo-delta) after that.
Hope this helps.

Each time master data full load removes previous data and load with new ?

We load company code (0COMP_CODE) master data (full load).
1st day, we check company code master data, the record count is 150, 2nd day, the record count is 90. It sounds like the master data full load each time would clean the previous data and load with new data, am I right? If what I guess is right, then what setup is controlling this?
Thanks

I dont think it does cleanup.
MD records in the new load simply overwrite the records already present in the master data.
I mean if same record comes again its overwritten.If new record it gets added.
I wouldnt expect number of records to reduce drastically from 150 to 90.
Maybe before MD activation records could be more(as there will be both M(modified) and A(active) records).
cheers,
Vishvesh

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

Problem with Data source- full load is not extracting where as delta can.

Hi All,
I have a problem in loading of the region values into BW.
Data Source 0CRM_OPPT_I is used to fetch opportunities ( same as Sales Orders in ECC) from CRM system.Data source has a field 0CRM_TR which gives the values of region values pof the employee responsible. problem here is that CRM_TR value is not being fetched when the record was first created, but the value is being flown to BW in the delta run i.e. when a change happened in record.
Please anyone help us out in resolving this issue.
Regards,
Haaris.

Hi Hari.......
Hav u done init........if yes........What u hav done....I mean.....init with or w/o data transfer.....?
It has picked records or not? if yes...........after init.........hav u checked the Delta queue(RSA7) in the source system...........is the Total field is 0 or not.........if 0..then....
Look if u r using Direct delta.then after init.any changes or new records will get recorded in the Delta queue(RSA7) directly..........but if the Update mode is Unserialized V3 update or Qued delta.then data will accumulated in the Update table and the Extraction Queue respectively...........in that case u hav to schedule V3 jobs to pull them in RSA7............otherwise delta load will pick 0 records only........
Check the update mode of the Datasource in LBWE.......
Check this..........it may help u........
Steps to do init load from CRM
Regards,
Debjani.......

DELTA Load gives wrogn values Where as FULL load gives right for FI Report.

Similar Messages

Maybe you are looking for