Error Message form the Source System

[former_member267533]

hi all,

I'm facing problem with Caller 09 error every day when info package is executed in process chain. I just use repeat option in process chain for executing the info package step, I'm doing this for step every day. Please suggest me how to resolve these error permanently. Error massage is follows:

And also I tried :

But same problem for next day. Please give some solutions to resolve this error permanently

[RamanKorrapati · Accepted solution]

Hi,

please try to replicate your data source from source to bw at prod system.

later activate data source thru program.

Even try to activate next data flow steps as well.

Thanks

[former_member267533 · Accepted solution]

Hi Raman,

I followed your steps on FEB 3rd, next day process chain started : Info Package triggered successfully. but next day (Today FEB 5th), process was not started, it canceled today's loading and shows next chain start day is FEB 6th.

I've checked SM37 --> FEB 5th BI_PROCESS_TRIGGER was Canceled. I started process chain through function module.

please help me on how to know why BI_PROCESS_TRIGGER was cancelled.

thanks&regards

Kumar.

[RamanKorrapati · Accepted solution]

Hi,

please check your Feb 5th logs and see why its failed.

Without logs/error information we are unable to suggest you.

please share your feb 5th failed logs or error or long text details.

Thanks

[former_member267533 · Accepted solution]

Hi Raman,

Job log in SM37

• But when I’m trying to see job log, it is giving “No job log found”.

--> Is there any other option to check error log.

[RamanKorrapati · Accepted solution]

please try to go SM37 from your failed process chain.

You will find related your chain job.

if there is no logs then just remove your chain from schedule.

activate your process chain and again keep it back to schedule.

monitor your chain coming days and see.

in above screen, select job and later click on job logs.

[Former Member]

Hi Bellala,

Kindly activate the datasource and related transfer structure if any, in BW system through program and check.

Thanks,

Shailesh.

[former_member223861]

Hi Kumar,

When You trigger any infopackage one request will be generated in ECC System with prefix BI*. Check that request in ECC. definetly the job will be in failure. And also check on which application server the request has been running in ECC. if you get like this errors means the job has been cancelled.

                                                                          I have faced like this error. my client is having two application servers if request has been running on application server one my job is getting Success if my job runs on Second application server the job is getting failed. throwing message error in the source system. raise this issue to Basis people they will resolve it.

Thanks,

Naveen

[KodandaPani_KV]

HI,

check the TRFC issues in SM59. push to manually using execute button.

after running the info package check the jobs is generated or not in ECC system.

check the SM37 job logs in ECC with BIREQU.

if not job generated in ECC check with the basis team have table space issue.

Thanks,

Phani.

[Former Member]

Hi,

did you further check, was it because source system job got cancelled which is causing info package failure? or idoc issue?

[former_member267533]

Hi jyothi,

where we can find whether source system job cancelled are not.

[Former Member]

from infopackage menu -->Environment-->job overview-->source system

(or) from infopackage header status -->copy the request requ_****

goto source sytem -->sm37--> and prefix BI (ex : BIREQU_***) in job name and execute.

is this happening with only one info package? or all?

[former_member267533]

hi jyothi,

thank you for quick replay, I tried what you said, but I don't access to check source system. Is there any another way to resolve this error.

thanks & regards

Kumar

[Former Member]

Kumar,

if you don't have access to source system, you can reach out basis to help checking the job status.

if source job is failed, then you need to check what was the reason behind.

if source job is successful, then you have to check if there are any trfc's which got stuck (this is also in source system) .

between, is this is only info package which is failing? and since when? was there any recent changes done at data source level?