cancel
Showing results for 
Search instead for 
Did you mean: 

TM - Optimizer Dump - FM /SAPAPO/CRES_TIMESTREAM_CREATE

former_member205075
Participant
0 Kudos

Dear Experts,

we are facing an issue when running the optimizer in TM. After selecting a FU and a vehicle resource and running optimizing planning (selected entries only), there are short dumps created under category MESSAGE_TYPE_X.

In a deeper analysis we find out that the system is failing during the call of function /SAPAPO/CRES_TIMESTREAM_CREATE and there is a missing parameter IS_RES_HEAD

The values that are being passed onto the function module are the following, including the missing is_res_head according to the dump:

In debug mode we find that ls_resheadpl is properly populated also by the previous method.

Nevertheless is_res_header is a structure that is actually not present in the function module /SAPAPO/CRES_TIMESTREAM_CREATE itself and therefore not supported when fed. The dump is then occurring.

We are using SAP TM 110 with SP 8. There is probably a mismatch between the Function module and the method that is calling it.

Has someone experienced the same already?

Thanks for support

Accepted Solutions (1)

Accepted Solutions (1)

former_member205075
Participant
0 Kudos

Issue solved with note 1956598 - Resource Availability: Prerequisite for Performance Improvement .

Answers (1)

Answers (1)

bharath_k6
Active Participant
0 Kudos

Dear Salvador,

It seems to be a standard issue.

Once the dump is replicated, go to ST22 transaction and there you can see the dump that recently you encountered. Open the Runtime error -> select 'How to correct the error' left side -> There you will find some keywords to search for SAP Note.

Search in SAP service Marketplace. Hope you will find some notes to solve the issue.

Thanks,

Bharath.K

former_member205075
Participant
0 Kudos

Bharath,

I already went to ST22 and searched all possible combinations that I could think of in OSS notes but still no success. I even checked the differences between support package 8 and support package 9 stacks to see if it had been corrected in the later relase of SP 9 (April 2014), and still nothing.

My point was actually to find if someone had this same experience since it´s weird for me that nobody has mentioned this in the past. For me there were 2 options, either I am missing something in my customizing/configuration, or this is a message to be reported to SAP.

Thanks for your reply

Salvador