cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Report Tree is not triggring once spec was approved

Former Member
0 Likes
461


Hi Experts.

Please advise since the spec was released completly and we are unable to connect the report tree for this spec.

Kindly find the attached issue details.

There are two error's as below.

1.Internal Program Error; (ESTDH-RECN 00000000000000079143)

2.specification<0000000013439> has not been Maintained for validity date 02.12.2013

  Diagnosis

The specification is not maintained for the validity date you specified

Procedure:

Change the specification validity in the specification master or enter  a  new  validity date

Message number:C$680

    

Please help me to solve this issue.

Thanks.

Kiran Math

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Likes

Hi Kiran,

This is internal program error. When the system tries to set up the report tree, it terminates with an internal error ("Internal program error") and it does not display any reports.

Click and apply this note

1093286 - You cannot call report management

After you implement this note, the system collects any error messages that occur when it is reading the report and displays them in a dialog box. If you close the dialog box, the system displays all reports that were read without errors.

Edward

Former Member
0 Likes

Thanks all experts for your valuable feed back here the problem what we are facing is we creating spec and we are sending it for approval in the mean time we are creating the draft report for the concerned spec without the complete release of the spec and once that spec got approved and complete released the validate date of the spec and draft report creation date (Earlier date of draft report creation) will be mismatching.And not  updating the spec approval date to the concerned report table ESTDH because of this  error .

And this draft report is customized report  we are sending it for the approval team to check the contents of the spec prior to complete approval of the spec as per business need.

Kindly advise.

Thanks.

Kiran

dhinsap
Active Participant
0 Likes

Dear Kiran,

Its the number range issue. Check if u have maintained the number ranges for specifications in IMG and if u have a change number.

In order to be able to define number ranges for the specification key, you need authorization for number range object "ESN_SUBID". This object is checked in authorization object "S_NUMBER".

Also Check the path as informed by Balajee.

Dhinesh

Former Member
0 Likes

Hi,

Internal Program error ESTDH-RECN is for internal sequence record number.

check '00000000000000079143'  in ESTRH and compare with ESTDH entries.

Thanks

Former Member
0 Likes

Hi !

Try changing the Key Date.

Regards

Subash Sankar

Former Member
0 Likes

Hi Subash.

Thanks for the response

we maintained validate date from 28.11.2013 to 31.12.2999 and Keydate we are using is 28.11.213 please advise Regarding internal program issue also.

Please help me to get the solution for the same.

Thanks.

Shiva Math

Former Member
0 Likes

Hi !

Can you post more of your problem..? what exactly you are trying to do & how do you do it..?

If possible post screen shots. IT will help the community to help fast.

Regards

Subash Sankar

Former Member
0 Likes

Dear Kiran

seems you are created change number for validity  period , but didn't mentioned number range for that.

Go to SPRO ... Environmental Health&safety...Basic Data & Tools .... Specification Management... Specification Master ........Specify Number range for specifications and maintain the data as mentioned below

NO       From No.                   To Number                    NR Status                    Ext

0E           A                           zzzzzzzzzzzz                       0                     Check Mark

0I      000000000001              899999999999                     931

And also ensure in change number is activated for all fields and Number range assignment for  Change number.

Balajee

Former Member
0 Likes

Hi,

As mentioned by the experts here, the issue seems to be with Number range object.

Go to Transaction, SNRO. Then enter the number range object, ESN_SUBID and maintain the values as mentioned by Balaji.

Regards

Subash Sankar