cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Process chain issue: Delta load failed

Former Member
0 Likes
1,020

Hello Friends,

We have scheduled a process chain in BI 7.0 Production. This is for a 3.x flow where in the data moves from R/3 to DSO. The extraction of data was fine till 14 Nov. However, on 15th Nov the InfoPackage failed. In the Manage option for DataSource I can see green requests till 14, but there is a red request for 15 and for 16th there is a green request (with a yellow lighting bolt beside it) but it is bringing 0 records.

Friends, I am not very confident with the delta process and how to rectify things when there is such a condition.

1) Can anyone please tell me what are my options now? Should I delete the red request from Manage option of DataSource and hope that the next delta run will bring those records?

2) Also can someone please explain or re-direct me to a source which explians, the working of delta mechanism so that this poor soul will not be intimidated in future with delta loads

Thanks in advance for your timely assistance!

Regards,

Prem.

View Entire Topic
Former Member
0 Likes

Since you said that your dataflow is 3.x, you dont need to do anything in PSA. As per described by you, I assume your target must have 2 red requests. Latest red request must be 0 records which is also failed delta.

To correct this -

You can simply make RSMO (monitor) status for both requests red. Also make QM status for both request in target red and then delete those 2 requests from target. And finally just run delta load manually. Most of the times, transactional datasources support repeat of delta..

But before taking above steps, please tell us -

1. What is the datasource name?

2. In manage tab of target, you see red request for 15 & 16.. correct?

3. Also, do you want to correct this load only or correct process chain too and make it run further?

Abhijit

Edited by: ABHIJIT TEMBHEKAR on Nov 16, 2008 12:44 AM

Former Member
0 Likes

Thanks for your prompt reply Abhijit!

1) The DataSource is 0CO_OM_CCA_9.

2) In the manage tab of the DSO I see a red request for 15 but surprisingly there is a green request for 16. However this request has brought no records

3) I wanted to correct this load as well as the Process chain also.

In the Monitor for the InfoPack, if you try to turn the red request into green, you are prompted with a message saying that with the next request a delta request will be sent to the source system. And the data from the Red delta load will no longer be available and will be lost forever. I am getting a bit confused with this.

If possible clarify this. Once again thanks for your prompt reply!!!

Regards,

Prem.

Former Member
0 Likes

Ok.. so this datasource should support repeat of delta. And since it ran through process chain again on 16th.. 16th load should be repeat of last delta. And since you saying green request bought 0, even the red request on 15th must be 0. If this is true, you can just delete request loaded on 15th and continue process chain further (You can delete 15th request only if 16th is not activated and in this case I believe 16th request is not activated)

So from above scenario, I am using that on 15th load failed and created red request in target. On 16th, load was successful as repeat of last delta but activation failed since target has red request from 15th. So simply delete 15th red request making it red in RSMO and and in target and then do repeat on activation step in 16th process chain log. This should continue process chain further.

Also to push process chain further manually, if your chain is stuck in yellow or if you carried out red step (failed) manually from RSA1 and now want to continue chain, - follow these steps -

Execute in SE38 -> RSPC_PROCESS_FINISH

Fill the following parameters on screen and rest all can be left blank.

1. LOGID - you will find this when you do monitor of your process chain. Every time you run process chain, unique LOGID is created.

2. TYPE - If step 4 is ODS activation then TYPE wud be ODSACTIVAT and if it is infopak loading TYPE wud be LOADING and if it is DTP Load TYPE wud be LOAD.

3. VARIANT - In the process chain monitor mode, right click on step 4 -> Display Messages. Go to chain tab and there you will find VARIANT

4. INSTANCE - In the process chain monitor mode, right click on step 4 -> Display Messages. Go to chain tab and there you will find INSTANCE

5. STATE - Value wud be G

After entering above parameters, click execute. It will be done in fraction of second and wont give any popup. Now when you will check process chain monitor, you will see that step 4 is green and next step has started executing. Do this steps for all yellow processes.

Abhijit

Edited by: ABHIJIT TEMBHEKAR on Nov 16, 2008 1:53 AM

Former Member
0 Likes

Hi....

I am scared ....ur delta mechanism is corrupted......is every day that load picks 0 records.......if no.......then check the delta queue(RSA7).......in the source system........is that datasource is suppose to pick any records......if there are some records in the delta queue........but still that successful load has picked 0 records........that means delta mechanism is corrupted...........the only option is re-init......

First delete both the request after manking the QM status red..........

1) Delete the set up table(tcode >> LBWQ)

2) Re fill the set up table with selection..........for 15th and 16th..........(tcode >> OLIBW..... for application component or SBIW -> Business Content DataSources -> Settings for Application-Specific DataSources (PI) -> Logistics -> Managing Transfer Information Structures -> Setup of Statistical Data -> Application-Specific Setup of Statistical Data -> Perform Setup (here you can find a list...)

3) Delete the init flag...........to do this go to IP scheduler >> in the Top Scheduler tab >> Initialization option for source system.....

4)Then do full repair

5)then init without data transfer

6) And then Delta load.......

Hope this helps.....

Regards,

Debjani.......