Internal error in cg02

[Former Member]

Hi all,

I am getting the below mentioned error in cg02 report management after creating the report. This error is coming for some particular material. Please guide me how to fix this.

Thanks and regards

Manasa

[christoph_bergemann]

Dear Manasa

is this error only related to one combination of specification, generation variant etc.only?

I would expecte to have this error in "CG02" and not in "CG50." If the system can not determine the "TEST" generation variant it should stop any further action..

If in CG02 you get the message "Report created sucessfully", then normally no "ad on" error shoud come up if youi navigate to CG50.

Which release do you use?

C.B.

[Former Member]

Hi Christ,

I am getting this error in quality system for some material specifications only.

In CG02 report is being created successfully, but when i am trying to open the report in report management or report information system in CG02< specification< Reports, I am getting the error. But when I continue(enter) to open the report tree, I could see all the reports.That means the report is being created but the error message is showing. I have tested for nearly 15 materials, in which i am getting the error for 4 materilas.

In CG50 also the same error message is showing. But when we continue (enter)  all the reports for all the specifications are getting opened.

We are using EHP7.

I hope we should delete the unwanted table entries. Could you please guide me how to delete the unwanted table entries. Unable to find the generation variant TEST. Hope the team used the TEST generation variant and deleted the same. But still it is showing.

But when we try to open the report from template no error message is showing.

Please guide me how to fix it.

Regards

Manasa

[christoph_bergemann]

Dear Manasa

we need to use some assumptions.

you use some spec id: then you create a report: then you switch to CG50. Now the system detects that a "curious" entry for the spec id is existing in ESTDH (report header).

The screen "explains" that the system tries to show a "report" (in my opinion) in CG50. This report seems to belong to generation variant "test" And the systems get in trouble as the generation variant is not existing any more (assumption based on error message)

Now if your assumption is correct: "Unable to find the generation variant TEST. Hope the team used the TEST generation variant and deleted the same. " then (I am sorry to say that) somebody has done something which she/he never should have done (never ever !!!). If you have a table entry in ESTDH (not deleted) referencing a generation variant "TEST" you should never ever delete "TEST" using debug/replace

Your system is now "corrupt" (if the assumptions are correct). PLease check ESTDH and look for entries (either deleted or not) with generation variant "TEST". Hope that the number is only low,...

The issue is that you should not only delete (using debug and replace) the entries in ESTDH (assuming that Gen Varian TEST is not existing) but you should as well deleted other entries in other tables; and if you have an ALE scenario in place: then you have now a "desaster" scenario to recover and there is "less" chance to get a "recovery".... (my good... nothing can as worse as this situation...)

Any ESTDH entry is refering to a further table (to handle the "status" net (sorry: i can not remember the name of this important SAP table; I was able only to find some "structure" (RCGRSTIOT EHS: IOTAB for status selection for reports - SAP Tables=(. And there is the table ESTDJ as well linked to ESTDH.

Regarding: I hope we should delete the unwanted table entries. Could you please guide me how to delete the unwanted table entries

I believe this is possible (with risks). But if you have an ALE in place then... ()

C.B.

[satya11719]

Hi Manasa,

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.

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

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

Thanks

Satya