cancel
Showing results for 
Search instead for 
Did you mean: 

Actual cost is not showing in refurbishment order.

0 Kudos

Hi experts,

Actual cost is not showing in refurbishment order,so I am not able to teco the refurbishment order. I get the error message: "Teco is not possible as order has no actual cost".

I have added a PM03(External service) operation and PR,PO,SES and GR is done. Also I have done the material GR.

System status is REL CNF DLV GMPS MANC PRC SETC and user status is RCVD SETF.

Could you please suggest me how to display the actual cost in order?

Regards

Vivek

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member185450
Active Contributor
0 Kudos

Dear Vivek,

The actual cost will get update once you do the consumption against the maintenance order, simultaneously if you maintained the MHR for your activity hours

once you confirm the maintenance order through IW41 with reference to actual duration system will calculate the Actual cost

the message which you are getting is a custom message developed with our own logic

so please coordinate with ABAPer for removing the validation

Regards,

Venkatesh..

0 Kudos

Hi Venkatesh,

Thanks for your reply. But I am getting this error only for a particular order. For other order, it works fine.

My question is "If I have done the service GR then why actual cost is not showing in order"?

Regards

Vivek

peter_atkin
Active Contributor
0 Kudos

Vivek

Can you please send the full message text including message number.

PeteA

0 Kudos

Hi Peter,

I have done all GR related to order but actual cost is not reflecting. Hence Teco of order is not possible. Although plan cost is showing.

I have the issue that "Why actual cost is not showing" ?

Regards

Vivek

0 Kudos

Hi Peter,

Error message is - TECO not possible, no actual costs on order. Check the costs or use cancel instead.

Message no. DB000

Regards

Vivek

peter_atkin
Active Contributor
0 Kudos

Message DB000 is a generic message (see SE91).

This message is odd because TECO is not affected by settlement in the standard system.

So I suspect its one of your own developments causing the issue (possibly user-exit IWO10004 0 see SMOD)

PeteA