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

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

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

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......

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)?

Collection in source system ended-Process chain error

Hi friends,
I have got a PC which failed due to error : Collection in source system ended.
My flow of PC is .
start--
       --Load IP 1
      ---Load IP2
      _--load Ip 3
Load IP4
      ---Load Ip 5.
I got this error at IP2 and so my pc fail .
can i manually upload this IP2 and make the process chain OK?
what are the steps involved in rectifying this?
regards,
siddartha

First try to find out the reason for the load failure. Once you fix this, do a manual run of the infopackage and when successful you can continue with the rest of process chain.
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.

How to change source system in process chain

Hi All,
In our Bw quality system, process chain is pointing to the Production system ,
I want to keep the process variant name same as production but want to change the source system
For example.. let us say currently process chains(All DTPs) are pointing to the Production server (PD001) ip (200.12.23.22)
now i want to keep the Server name same but want to point it to the quality system..so after change Process chain will show same name but it should point out to quality system.(let us say bwq 200.12.23.232).
Can you please help me on this

Hi Pravender,
In our BW system , we have same process chain in all the system (Dev, Quality and production)..and naming convention is also same ..(all process chain points to Production system only)..
So when I want to load data from development i just need to change the source system ip adrress to the Development Server (So names in process chain will indicate production but it will point to the development server), .
I want to know how can i change the source system mapping.
Hope i am clear now

Need information-BW System administration-process chains

Hi gurus,
I need information about BW System administration-process chains
can anyone send me the docs related to
1)process chain modellin aspects
2)process chain monitoring &error handling
3)BW statistics and query tuning with aggregates
Thanks in advance..
regards
s ram

Hi,
Check these links:
http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ce/dc87c1d711f846b34e0e42ede5ebb7/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d5/e80d3dbd82f72ce10000000a114084/frameset.htm
Process Chain
process chain
BW STATISTICS
If you are asking abt the flags that you see in RSA1 -> Tools -> BW Stats...you can check BW Stats for each and every infoprovider. Whenever you create an infopprovider you should always decide whether you want to turn on the BW Stats for this infoprovider. This is a manual step and can be done in each and every box individually or can be transported across the systems. Coming to your question...BW Stats are of two kinds...
1) OLAP -
If you check this flag for an infoprovider...all the statistical data for the queries built on this infoprovider gets updated into the corresponding infocubes (0BWTC_C02 and 0BWTC_C03). An example would be like number of users that ran the report in a given time, the average run time of the query and so on. This data is of immense value in deciding the steps for performance tuning techniques like aggregates!
2) WHM (Warehouse Management) -
If you turn this flag on for an infoprovider, all the statistical data like how often the cubes are loaded, when are the requests deleted from the infocubes, data abt condensing of cubes and so on is loaded into the corresponding cubes like 0BWTC_C04, 0BWTC_C05, 0BWTC_C09 and 0BWTC_C11.
You have to activate the infopackages to load into these cubes and schedule them through process chain to run once in a while so that your statistical data is uptodate.
Production support for maintaining the process chains primarily involves monitoring activities of all the chains that are running in the background...
Errors in monitoring of process chains can be categorized into 4 different sections...
Master data - Full Update
Master data - Delta Update
Transaction data - Full Update
Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
Majority of the issues will be based on these things only..
****Assign Points If Helpful****
Regards,
Ravikanth
Message was edited by:
RK.PNV

HI,How can i set delta option for costumised Generic data source

Hi Sir/Madam,
How can i set delta option for costumised Generic data source.
Regards,
Vishali.R
Please search the forum before posting a thread
Edited by: Pravender on Aug 15, 2011 1:26 PM

Hi,
Go to RSO2 transaction and click on change then on the tool bar click on Generic Delta button. In the next popup you can set your delta.
Regards,
Durgesh.

Enabling Early Delta Initialization option for LO DataSource 2LIS_06_INV

Hi Guyz,
I want to enable Earlt Delta Initialization option for LO DataSource 2LIS_06_INV, as of now its greyed out.
please tell me if its possible or not, and if yes then please let me know the steps in detail.
cheerz,
raps.

hi,
Not all Data sources support Early Delta Initialization. Early delta initialization is done to capture the deltas when the initialization is being done between BW and source system (init with data transfer). As init with data transfer takes large time and during this time any records created will also be not captured so we do early delta initialization, also the same can be achieved by executing the init without data transfer and then loading a full repair request. The init without data transfer creats a time stamp and delta is generated for newly posted records.
regards,
Arvind.

Error in codepage mapping for source system. Error

Hi BW Experts,
I am facing following error:
Error message: Error in codepage mapping for source system. Error text:
Details: Inbound Processing ( 1000 Records ) : Errors occurred
Error in codepage mapping for source system. Error text:
Update PSA ( 0 Records posted ) : Missing messages
I repeated the delta working and everything fine.
Does anybody know why this error occurs?

Run rsa13 (for bi 7.0) find your source system which one you are using for data transfer and double click on it and find special options there select the optioned i mentioned already.
Please search SDN you can fin threads related to this thread
if not let me know.
Regards.

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

Similar Messages

Maybe you are looking for