Deletion of request from init option for source system

Hello Experts,
Iam using 3 IP.
IP for init load with data transder, IP for init load without data transfer & Delta.
now with data transfer IP is not used.
i trigered "without data transfer IP", then accidentally "triggered with data transfer IP".
then manually made the request red & deleted data by right clicking datasource-->manage & deleted all the requests(2) available.
now before i load init without data transfer request exists in "init option for source system".
when trying to delete IP
"There are active init selections in source system for this data source. Therefore, only ALL init selections can be deleted at once. Do you want to delete all init selections (all channels)?"
when i choose yes....it takes a long time & gives run_time error status.
Guys, this issue is solved.
I deleted the without data transder first.
now when I load delta, I got error.
"Job terminated in source system --> Request set to red"
regards
KV
Edited by: K V on Apr 10, 2009 2:16 PM

Hi KV.........
U r doing init without data transfer..............it means it will not pick any records...........it will just set the init pointer and along with that Delta queue will get generated.........after that whenever any changes will be done.........or any new records will come.......it will get reflected in the Delta queue.......
So next time when u run the delta load..........data will be fetched from the Delta queue...........
So check the delta queue.......it may happen that there r no new or changed records..................
So check............may be delta queue is 0..............
Also check the update mode for the datasource in LBWE(if Logistic datasource)............if the update mode is Queued delta or unserialized V3 update........then data will first get accumulated in the Extract queue(LBWQ) or update table respectively.............so to fetch records in the Delta queue u hav to schedule the V3 jobs in LBWE............otherwise Delta queue will be empty and fetched records will be 0........
Regards,
Debjani......

Similar Messages

Initialization Flags deleted from Initialization options for Source System

Hi BW Experts,
We have loaded PCA data in Infocube last week with Fiscal Year/Period Selection Parameters like
001.2004 to 016.2004
001.2005 to 016.2005
001.2006 to 016.2006
001.2007 to 016.2050
So we got 4 Initialization flags in Initialization options for Source System in SCHEDULER.
After this we are running Deltas daily
Accidentally All Initialization Flags deleted from SCHEDULER yesterday that we did not know yesterday.
Deltas did not run today.
Please can anyone tell me the solution for this.
I have to run the Delta today. How can i get the yesterday records in my Data Target,
Thanks & Regards,
Anjali
Message was edited by:
Anjali

Hi Anjali,
Please delete the Init Request from your data target performed for Selection 001.2007 to 2050.
Also delete <b>only those deltas request</b> from your Data target <b>which were performed after the above mentioned Init.</b>
And then Re-Init with Selections on Fiscper - 001.2007 to 2050.
Thanks
CK
Highlighted
Chitrarth Kastwar

Can I delete 'Initialization Options for Source System' in Process Chain?

Hi All,
Can I automate the process of deleting the 'Initialization Options for Source System' for Delta Init package? I need to include this step in a process chain, rather than deleting the init request manually.
Thanks,
Naveen.

Naveen,
As far as I know, nope. And it's logical, considering the Initialization is a "one time" process and not a repetitive one (unless you have to reinitialize, of course...)
Regards,
Luis

Initialisation option for source system in schedular tab

What initialisation option for system in schedular tab signifies? Does it acts as pointer and points to the last record loaded in cube or ods?

Hi....
Welcome to SDN..........
Initialisation option for source system in schedular tab........
shows to you all the init you made for a specific datasource/sourcesystem...if you find a row here, it means that the init channel is active and you can load delta for that specific flow.....
Initialization may with data transfer or without Data Transfer.......If you do with data transfer it will set the init flag............as well as it will fetch the data from set up table...........if you do without data transfer it will only set the init flag.....it will not fetch any records.........As soon as this init flag get set.......delta queue will get generated in the source system........after that any changes or new records will go to the delta queue.............So initialization load will be followed by delta load......
When you have to reinit, first of all you have to delete this row and then request a new initial load, otherwise the system cannot allow to perform a new init (with overlapping condition) if you don't deete the previous one....
Hope this helps
Regards,
Debjani.......

Initialisation option for source system

Hi Gurus
Can anyone explain clearly about
Initialisation option for source system
Thanks in advance
Raj

Hi,
This option is used when you want to init / re-init delta loads from source system (R/3 or BW Datamart). You have to set-up your Initialization before you can run your deltas.If you have already deltas loaded or want to load deltas from source you have to do an init load. In case you have already loaded deltas you have to delete the existing Init Request from your data target and perform re-init.
You have two options Init with data transfer and without data transfer.
Init is just setting path for deltas to follow.
Steps for Re Init from R/3 to BW
1)Delete the contents of Application area 11 inRSA7 delta queue/LBWQ
2) Delete the setup table for the application 11 in LBWG
3) Delete the initialization information in BW , By deleting the 'initializing option for source system ' from infopackage(delta initialization).
4) Delete the PSA and data in Datatargets.
5) Fill the setup table for the application 11.
6) Execute the delta initialization infopackage for these Datasources.
Thanks,
JituK

Initialisation options for source system

If I am in an InfoPackage and seleet the option "Initialisation options for source system" and have more than one entries, is there any way that I can delete just one of the entries? Thanks

Hi there as a test scenario I am trying to delete one entry but it deletes both giving a message as below pre deletion, what am I doing wrong? Thanks
There are active init selections in source system for this data source
Therefore, only ALL init selections can be deleted at once
Do you want to delete all init selections (all channels)?

Initialization option for source system in schedular tab

SAP BW Gurus:
Please help me with this question.
This is a new system setup. I used initilization option doing the two years of data loads. I loaded eight loads with each load for a quarter's data.
Then I found there are some loading issues with one load. So, I need to delete that load and reload again.
To do that, i need to delete that particular load in the initialization request.
When I highlighted that request and delete, there is a window pop up saying:" There are active init selections in source system for this data source. Therefore, only ALL init selections can be deleted at once."
If I choose "no", I couldn't delete that particular package. Then, just for the sake of trying, I click on "yes", then all the 8 initization requests are gone!!!
Now, I got two questions:
1. If all the requests are gone, does it mean, I have reload everything again for initilization, ?? (it will take days to do it!!) Now i have two years of data already in my cube and DSO. This is version 7. But I do need to schedule Delta process later.
2. If I have eight requests, am I able to delete only one of them?? What does the question i listed above mean?
Thanks so much, guys!!

Hi,
System maintains only one delta queue for a datasource irrespective of ...number of inits... which is done from the source system to the target system and this you can see in RSA7.
You can do init with data for any number number of selections but the delta for all those selections will be combined and will present in one queue.
If you delete one init request it will delete the whole delta queue as all these request share the same delta queue and therefore all the init selections will go off.
You should be careful when you do this.
Now since all the delta is lost and if you can find a way to load the lost delta like doing a full repair on created on or changed on date... then you can just as suggested...but on the safer side I would suggest to the repeat the process or as mentioned in the OSS notes.
Thanks
Ajeet

Initialization options for source system (message_type_x)

Hi All
My R3 source system is just connected to my BI, after the upgrade of R3. Now i saw in RSA7, all entries in RED. So i have deleted them manually in RSA7.
Now, in RSA1, I wanted to run the Init delta IPAKs for all those deleted datasources, when i open the IPAK to run, its giving me MESSAGE_TYPE_X dump. So i cant go to the menu --> scheduler --> initialisation options for IPAK.
I think i should have deleted from here than in RSA7 in R3. But now i cant even open the IPAK. The module name in the dump is RSM1_CHECK_FOR_DELTAUPD.
How can i resolve this issue ? Do i have to replicate the datasource in RSA1 as Source system is upgraded ( we actually replicated all metadata by rt clicking the source system).
Any help pls ?
thx
venkat

hi,
check this link ..
Clicking on Delta Infopackage gives short dump MESSAGE_TYPE_X
Re: Short dump MESSAGE_TYPE_X while trying to open infopackage
reagrds,
shikha

HELP: 0 from 0 records: Initialization Option of source system

I executed an 'Initialization option for source system' on the scheduler and no data is coming from the source system.
Steps taken:
1. Delete data from target DSO
2. Picked InfoPackage and selected it returns back 'Initialization option for source system' on the scheduler
3. Deleted the initialization setting
4. Executed InfoPackage
Result: "0 from 0 records" found. How do I fill the queue table in the source system if not records are available? T
5. I go to delete the request in the PSA to retry: "No data in the PSA".
This is to resolve a HIGH status ticket because I stopped delta process of other Infoproviders until this situation is resolved.
Can you provide detail steps to properly create a trigger delta data from R/3 from a "Initialization Option of source system". We have cancelled delta undates until this is resolved.

Hi
Now that you have run the init once, there is no need to delete the init flag
The delta pointer is set now, you can run the delta Ip from now onwards.
But if there were already some previous deltas done for this, and the delta had failed, because of which you have to initialise the delta again, then you need to delete the previous initialisation.
To delete the init flag.
Open your delta IP in RSA1(or in the PC)
Goto the scheduler menu option
initialization option for source system
There you will see that a window will pop up which will show a succesful load, and you will see a tick mark in the first column.
If you see a cross mark that would mean that the initialization has failed.
this mark whihc you see is called the init flag.
If you need to reinitialize the delta, then you have to delete this .
Select the entire row and click the third button at the bottom.
This will delete the initialization for source system( i.e init flag)
now, before running the delta, you have to run the init IP again.
it depends on the scenario whether you hav to run with data transfer or without data transfer.
Hope this clarifies the query
Regards
Shilpa

Delete initialzation request from infopakage

hello ,
I want to delete , initilization request from infopackge , but when i m trying to open a infopak it is going to short dump.
can u please tell me , how can i delete the intitzation request from infpackhe scheduler with our open a infopak .
Regards,

Hi Jain,
Try by dumping Ur all data from the data target, if there is only one data source existing for that data target.
Process:
Rt click on the data target delete data.
Now go to Infopackage.
Select "Scheduler " option in menu.
Select "Initialization option for source system"
There U can find a request select it and delete.
Rgs,
I.R.K.

Process Type - Delete overlapping requests from an Info Cube

I have read many threads on this topic, still have some questions. To give you background, I will be doing delta load (delta process chain). But before delta, I want to do setup initialization (init process chain). I want to use this process type in my init process chain to delete all data in my cube loaded from a specific ods. I cannot use delete all contents process type because many odss feed the same cube.
1.     Do you put this process type after Load Data or before Load Data. I have seen both cases in SDN forums.
2.     Variant of this process type is an info package. Does this info package have to be same as in load data step or it can be different.
3.     I want to delete all data in cube which was loaded from my ods. Term overlapping is confusing to me. Will this process type delete all data or not.
Tanks in advance.

Yes, you can do that. Goto RSPC - under process types Load Process and Post Processing, you will see DELETE OVERLAP REQUESTS FROM INFOCUBE option is there.
Select the proper check boxes like same sourcesystem, same datasource etc...
If it is one time deletion, why not do that manually?
Also check: How to delete most recent request in a Cube by using process chain
Hope it helps..

Deleting failed request from DSO leading to delete of INIT of DSO to Cube

data flows from ds1, ds2 and ds3 to dso1 as delta. the data is then taken from dso1 to cube1 via delta
data flows from ds3 to dso2 as delta. the data is then taken from dso2 to cube 2 via delta.
when a data is loaded from ds1 or ds2 or ds3 to dso1.. or when data is loaded from ds3 to dso2.. now if we try to delete this un activiated request from lets say dso1. it gives and error that the init from dso1 to cube1 would be deleted as the data has already been data marted.
this happens even if the request in dso1 is inactive successful or inactive failed.
i did an init of ds1,ds2, ds3 to dso1. and also did an init from dso1 to cube1. but the problem persists.
though if all goes good. like no failures in the load, then all is well.
but if the load failed. say ds2 to dso1 failed. then when we attempt to delete this request from dso1, it says that it has already been uploaded to cube1 and the init will have to be deleted. here when we checked the datamart sign in dso1, it looks like the newly loaded n unactivated data is somehow assosiated with the dso1tocube1 init.
any thoughts?

Please give more info.
How have you connected DS01 and Cube 1? Transformation or update rules? How have you done the initialization?
What is the version SAP BW that you are using?
Have you checked any relevant SAP Notes?
Thanks,
Krishnan

Delete overlapping requests from infocube

Hi ALL,
I have loads to infocube from 5 diffrent infopackages loading adhocly or randomly from same source sytem and same infosource.
Note:infopackages have dynamic selections.(ex calweek,product)
My requirement: If i load infopackage-1 today,and when i load the same infopackage next time the prevoius load should be deleted .
I need the same functionality for other 4 infopackages.
So at given point of time i should have only 5 requests in the infocube.
These are the settings i have done.
1)At infopackage level i have selected option Delete existing requests : overlapping
   Without selecting any conditions like infosources,source sytem are same.
2)Added process type in the process chain delete overlapping requests from infocube
   selected option: Delete existing requests : overlapping.
   Without selecting any conditions like infosources,source sytem are same.
Are these settings are enough or is there in best way to do this .
Please suggest me ...

Kishore,
Delete overlapping requests means, delete request with same selection only. If data selection not same, i dont think it will delete any previous request.
You can select infosource, source system. No issues. System only deletes request if data coming from same infosource or from same source system for same selection.
But in your case selection changing every day or for every load. I dont think it works.... Try once in DEV.
If i understand correctly, as you only needed latest 5 requests only, why cant you delete data completely before loading / starting new set of requests...?? This is easy, quicker and better approach.
But only problem is data will not be available during loading of new set of requests.
Srini

HOW TO USE FUNCTION Deletion of Requests from the Change Log IN PRCSES CHAN

Respected all
i used Deletion of Requests from PSA from the prcess chain and found good results, now i have only one request at the psa and thus i am doing good space utililisation. but when i am using Deletion of Requests from the Change Log i am not getting any changes in the request of dso. kindly let me know how to use this 2nd function.
thanks
abhay

Hi Mahodaya,
As per SAp standards its good to delete the requestes that are no longer needed for the delta update and no longer used ffor inti from the change log table and the data is loaded already in to DSO.
Goto RSPC
Click on create New PC -> enter the PC name n long descp
Next we need to define the start process for the PC.Maintain the start variant process.save n come back.
for deletion of change log we have option in the Other BW Processes -> deletion of requestes from change log
Once u select the option we get a dialoge box here we need to create the variant for the process enter the process variant n long descp. cick ok.
Next in the maintenance screen for the deleting the request from change log table will appear.
Enter the selection patterns to which the requestes should be deleted from the change log.
In the maintenance screen, select one or more Data Store objects for which requests are to be deleted from the relevant change log tables under Data Store Object column and select theInfo Area of the corresponding Data Store Objects under Info Area
If you select the first check box exclude selction pattern, this means that del of requests from change log table will be ignored.
or
We can delete the requests which are Older than N-number of days (or) date in the above screen. For this one, enter the number of days (or) date in the filed Older than .
OR
If we want to select the requests with a certain status then we can also do in the above screen. We can select the following status indicators from the above screen.
Delete Successfully Updated Requests Only -This status will delete only requests which
are successfully updated into corresponding Data Store objects.
Delete Incorrect Requests that were not Updated - This status will delete only incorrect requests which are not successfully updated into the corresponding Data Store Objects.
Delete Activation Requests only, No Load requests- This status will delete only the activation requests (requests that begin with ODSR_... ). No load requests are deleted.

Problem in deleting the request from ODS......

Hi,
I am not able to delete one INIT request from the ODS. This request was taking long time and eventually it turned to RED. Data was there in PSA but I deleted the request and thought of doing the fresh load .
Problem is that although I have deleted the request from the ODS , it is again coming back to ODS . I have started the fresh load. AS the previous also coming to this ODS its taking long time to load the data.
Can some body let me know how to STOP/DELETE the old request?? I have already turned everything to RED QM status , overall status etc. but still its not getting stoped.
Thanks Jeetu

Hi Jeetu,
Even though u find the job and cancel it or delete it the data load will not stop untill it loads the entire data!
Hope there will be large volume of data !
Until the data load is complete wait and then delete the request and then delete the init and start the fresh load!
I too faced the same issue but i am helpless i could not stop the data load inthe middle!
If you found any solution for this let me also know
Thanks
Ram

Deletion of request from init option for source system

Similar Messages

Maybe you are looking for