SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

TE417 Cleared accidentally.

Former Member
0 Kudos

Table TE417(Sched. Recs: Portions) has been cleared accidentally. We use Dynamic scheduling, without budget billing amounts.

How can this be corrected/repopulated. Any help is appreciated.

Thank you

9 REPLIES 9

Former Member
0 Kudos

Did you look at E1DY?

0 Kudos

I tried E1DY but I get a short dump "The ABAP/4 Open SQL array insert results in duplicate database records"

I think this is because TE418 still has records.

Additional Details on Short Dump

"An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in procedure "ISU_DB_TE418_UPDATE" "(FUNCTION)", nor was it propagated by a

RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)"

0 Kudos

When you got the pop-up in this transaction with a long text, did you click Yes or No? You can create only entries you deleted by giving an input that is specific to what you deleted.

0 Kudos

Tried both. Was getting the same short dump.

Since this happened in our Development System I was able to clear all Open MR & Billing orders, Billing docs etc... with a date >05/01/2010 using EL37 and then Delete Schedule records using E3DY (Date 05/01/2010)

And then create schedule records using E1DY from 05/2010 onwards.

But still would like to know if there is a better way of fixing this.

Thank you.

0 Kudos

This is your only option. You can wipe out the entire table using E3DY and recreate it using E1DY, but in production system you should NOT use that option.

0 Kudos

Would clearing TE418 and then trying E1DY be a good option. As right now E1DY short dumps as TE418 has existing entries.

0 Kudos

Yes that is what you can do if you are talking about just your development system.

0 Kudos

So what do you suggest should be done. If this happens in a Production system??

0 Kudos

You still work with the same set of transactions but you will have to be very careful as to what you do. You can do that one portion or even one MRU at a time and may be one period at a time.