cancel
Showing results for 
Search instead for 
Did you mean: 

Initialization issue for 2LIS_11_VAITM,2LIS_11_VAKON datasources

Former Member
0 Kudos

Hi New Year Greetings to all SCNers,

                                                         I have taken downtime recently and initialized all the sales orders,deliveries,billing.I got an issue for 2LIS_11_VAITM,2LIS_11_VAKON datasources,they are successfully loaded data to BI data targets with the status GREEN but not successfully initialized in ECC system.For these datasources it is showing YELLOW color in ECC.I have been looking again to take downtime for the SALES ORDERS in ECC and i am worrying what if they are not Initialized again after loading data..


In the below screen shots clearly you can see NO RECORDS for 2LIS_11_VAITM,2LIS_11_VAKON  in SMQ1 that means changes are not coming to SMQ1 and then to RSA7 because the initialization is not successful.

If anybody has encountered this type of problem please advice me what to do so that it won't happen again

SMQ1:

RSA7:

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi,

      thanks to all for helping me to resolve this issue.I have successfully initialized for 2LIS_11_VAITM.Because the data volume is so high last time it has taken so much time and a deadlock might have occurred in BW system so this time i have loaded data first till PSA and from there i have updated data targets.I have done some search on CALLER 70 MISSING which is the main issue and i understand it is deadlock error in database.

Prasanth and Ram,your comments have helped me to find the cause.

Shilpa i have tested the RSRV check for PSA partition problem,as it turns out check was successful i looked in different ways to solve the issue,but any how thank you for helping me out.

Thanks to venkateswarlu and kalpana too

Former Member
0 Kudos

Hi ram im doing my research about caller 70 missing and trying to find where exactly is the problem, whether it is there in source system or BW system.i will get back asap.

Hi shilpa thank you for your reply.earlier i was thinking that problem might be there in PSA itself but i cant see any errors in PSA so PSA seems good.but anyhow i want to check in RSRV..could you please tell me which section i should go in RSRV i mean where i can find the option to check PSA partition?

Former Member
0 Kudos

Hi,

It once happened in project as well.

Caller 70 missing, the cause was incorrect PSA partition.

Try to run RSRV tests and if there is an error, that may be corrected there.

Shilpa

former_member182516
Active Contributor
0 Kudos

Hi Sy,

Before performing your INIT again, could you please check if the earlier INIT load got completed successfully?

is the source system job completed ?

If above is not the issue try to change the status of the loaded requests in info providers to RED and also the IP data load status to red and delete the request.

Delete the previous init selections and perform a re-init with out data transfer and perform a full load . once this is done you can set the IP to delta.

Check the data source init status in RSA7 now.

regards

KP

Former Member
0 Kudos

Hi prasanth,

                      the request was loaded to targets with GREEN status but just now i have seen at IP level it is showing RED and i have checked in the status it is showing CALLER 70 MISSING,tried to see the short dump from ST22 but it is showing NON OF THE SELECTED SHORT DUMPS EXIST and in the details page all the packets are showing errors occurred at update rules but it is not showing exactly where those errors occurred,i mean at which infoobject or routine or rules it is happened.Provided screen shots from DETAILS tab.I tried to UPDATE MANUALLY but not working

RamanKorrapati
Active Contributor
0 Kudos

hi sy,

can you check ecc job which was related to your info pack.

Go to your info pack Monitor --> menu Environment--> job overview--> job in the source system. its will ask ecc user id and password, enter those and see your job, select your job and click on job log details. observe the logs and find the cause where its causing.

Mean while check at ECC Tx - SM58. if you see any red queues. need to clear.

you can find queues which are related to your data source by using TID(transaction id from your SM37 job log details).

From google you can search for " Caller 70 missing in SAP BW". Might be helpful.

Thanks

former_member182516
Active Contributor
0 Kudos

have you verified the TRFCs which might got stuck from source to PSA?

You can find if there are any fialed TRFC that did not processed from source to BW from the source job log.

data load monitor --> environment --> job overview --> source system (prompts fro user details).

open the job log --> Find (CTRL+F) --> enter the works "sysfail" --> if at all any TRFCs which are not processed with respect to this load will be displayed in separate window.

If you found any hung TRFC from the log next goto SM58 and process the hung TRFCs manually.

Check and let me know if you need more info.

Regards

KP

Former Member
0 Kudos

Hi prasanth,

                    I have checked in source system with SM58 and i have seen some LUW's struck and i processed them and after that in BW system i have tried to manul update all the data packages but still error is not resolved.i hav been searching about CALLER 70 MISSING as you can clearly see the issue is there in update rules in the processing tab.somebody is explaining there might be problem with indexes for the cube when you are loading from multiple datasources or infosources so drop them and load the data.can i delete the request at cube level for 2LIS_11_VAITM and schedule it from PSA again to cube.but i have a doubt how it is going to put the initialization in source system because its been days since i have run this init?i hope you can understand all of my queries expressed above,

Thanking you,

SY

Former Member
0 Kudos

Try to kill the job  and in infopackage select  init without data transfer next run full repair in bi side

Former Member
0 Kudos

Hi S Y,

Happy new year!.

As Raman said, do a re-init again by deleting all the data and of course the pointer also. IP-->Scheduler from Menu --->Initialization Options for Source Syastem---->Active Init selection.

Regards

Venkat...

RamanKorrapati
Active Contributor
0 Kudos

Hi Sy,

Init may not happens properly. so better delete your existing init and do the reinit again.

take all necessary  steps to have all data into bw without duplciation or missing.

delete your init at your info pack --> Menu scheduler --> init options for source system.

Thanks

Former Member
0 Kudos

Hi Ram,

               Very happy to see prompt reply from you.I knew i have to re-init that's what i have mentioned in my query. I have been followed all the steps in the previous Initialization and i will do the same next time also.If i do re-init WHAT IF IT IS NOT SUCCESSFUL AGAIN?

RamanKorrapati
Active Contributor
0 Kudos

Hi,

Thank you wish you the same.

As i know by doing reinit it will be green.  if not happens then reactivate your data source again and replicate into bw again. alter check it once data flow was active.

Even thought not active then there might some issue at backend program. need look for oss note or SAP help.

Mean while try reinit and let us know.

Thanks