Caller 09 contains an error message

[former_member205400]

For this InfoSource the InfoPackage Data Selection tab did not contain an object from the source system. The Processing Tab has Only InfoObject checked. When I run this I get 0 records with a red status and then this message below in an email message.

Check Load from InfoSource 0TCTIOBJNM , Packet InfoObjects -Texts

Please execute the mail for additional information.

-

---

Error message from the source system

Diagnosis

An error occurred in the source system.

System Response

Caller 09 contains an error message.

Further analysis:

The error occurred in Service API .

Refer to the error message.

Procedure

How you remove the error depends on the error message

I am assuming that since I had no source in the Data Selection tab that I should expect no records, correct?

So, why do is there even an InfoPackage transferred as BI-Content?

Just trying to make sure I understand.

Your answers are appreciated.

BTW, sys is 7.0 sp14.

[former_member205400 · Accepted solution]

BTW, I just checked the extractor checker shows that there are records.

[former_member205400 · Accepted solution]

I r-clicked on the error message of the details "Request IDoc : Application document not posted" and selected "Idoc maint in OLTP" and then I saw the error message in the log.

I see that my systems are off a couple minutes.

Should I just reboot these sys's?

**************************************************************************************

DataSource 0TCTIOBJNM_TEXT has to be replicated (time stamp, see long text)

Message no. R3016

Diagnosis

DataSource 0TCTIOBJNM_TEXT does not have the same status as the source system in the Business Information Warehouse.

The time stamp in the source system is 10/31/2007 11:54:29.

The time stamp in the BW system is 10/31/2007 11:52:10.

System Response

The load process has been terminated.

Procedure

Copy the DataSource again and then activate the transfer rules that belong to it. You have to activate the transfer rules in every case, even if they are still active after the DataSource has been copied.

[Former Member · Accepted solution]

You just need to replicate your data source again and re-activate transfer rules.

to activate transfer rules in PRD you can use the program RS_TRANSTRU_ACTIVATE_ALL

- Go to SE 38

- RS_TRANSTRU_ACTIVATE_ALL > Hit execute

- Provide Source System & Info Source name

- Hit execute

- Now re-schedule the info package to laod the data.

[former_member205400 · Accepted solution]

I got exactly the same error. This error in the email talks about Service API not the extractor like some of the Caller 09 messages indicate on SDN.

And the iDoc talks about a timestamp problem.

This msg talks about a space problem in the source system.

Where would I see/fix that?

[Former Member · Accepted solution]

Caller 09 error is the common error message for many types of load failures.

For a detailed error msg you can go to details tab and navigate through the errored step and see the error msgs.

By looking at the error msg, I assume that your error is related to time stamp. So activate your TR's and reload the data.

[former_member205400 · Accepted solution]

Yes, it is a teimstamp error.

So. Ok I had run pgm RS_TRANSTRU_ACTIVATE_ALL as i said above and attempted the re-load but I got the same timestamp err.

So, after u were so sure I did the following:

ECC sys rsa5 reactivate the infoobjects

ECC sys rsa6 retransported the infoobjects

BW sys rsa1 rereplicate the datasources

BW sys rsa1 bi_content install the infoobjects over

BW sys rsa1 re-load ..... service api error

BW se38 run pgm RS_TRANSTRU_ACTIVATE_ALL on infoobject

SUCCESS !!!!

Thanks for being persistent. There must be something wrong with those structures that I have to run that pgm on all 3 infoobjects.

If you can explain it, go for it. I awarded you the points.

[Former Member · Accepted solution]

Time Stamp error will occur if there is an inconsistency between metadata of DS and Transfer Rules ( or ) if the Transfer Rules arer not activated.

If you have the same problem for many Data Sources, use the RS_TRANSTRU_ACTIVATE_ALL program to activate all IS's at a single go.

-Execute Program in SE38

-Provide Source System name & enter * in Info Source field

-Hit execute.

Cheers

Praveen

[Former Member]

I found that for me it was due to the Security team changing my authorizations.

I discovered this by drilling into the Error Message button on the Status tab of the Infopackage.

I was extracting from a BW system to the SCM BW system (not using a Flat file).