I am getting an error in report shipping in CVD1 transaction. Details are mentioned below.

[devdatt_khedekar]

I am getting the below mentioned error in Report shipping.

"Report spec. 4***********8 gen. var. SDS_ES-PU lang. S: internal version not unique

System response:

System Response

A value file cannot be created for the final report. This means that the final report cannot be processed further and thus cannot be generated.

Procedure

Inform your system administrator that this error occurred and that the designated correction program RC1_REPORT_DOUBLE_INTVERSION has to be started. You can restart the final report generation process only once the correction program has ended successfully.

Not sure how to go ahead for the above mentioned error. Please guide.

[christoph_bergemann · Accepted solution]

Hello

never seen this error message in report shipment. But based on your information: this might be the reason

A report (of WWI type and other type and in this case) is handled in table "ESTDH". Here the "specification" is linked to status, version, generation variant etc. Under very rare circumstances there might be the case that the field "INTVER" is not populated properly

I have seen similar topics in our system (on very low level): I was not aware of report "RC1_REPORT_DOUBLE_INTVERSION". So I will check this report

Before you start the report. check the table content using specification number, generation variant, language etc. CHeck content of field "INTVER". This field must be populated and it is just a "counter". In the same table you have two additional fields, which are used for handling the "External" version (e.g. version 1.1 or 2 or 3.1).

C.B.

[devdatt_khedekar · Accepted solution]

Hi Christoph,

Thanks a lot for the answer, however I am unable to find entry for that particular specification in ESTDH. Is that the reason for this error?

[christoph_bergemann · Accepted solution]

Hello

mhh; strange.. If error as

""Report spec. 4***********8 gen. var. SDS_ES-PU lang. S: internal version not unique"

is generated I would assume the following

1.) the report distribution did the job (as assumed) and identified specification 4***********8 to check for a released report (I assume "*" has some "character" (but not "*" !!) but could not find "unique" report to use (and this is the issue in my opinion); for the process w eneed a "unique" report (and the "INTVAR" field is one of those to help to find a "unique" version)

2.) second: the process was able to detect that we need "SDS_ES-PU" in Language "s".. So I would assume we have some released version on the specification; but check deeper: is there really no report (e.g. iin status "ready" or whatsoever (please check only this spec; combine at least with "Gen Ver"..)

Dou you use "Change numbers" in your process.....?

Is this the only issue (of similar type)) you have identified since "years" in your system..? (I have never seen this error..)

If you dot suceed.. The error message does have some "number". IN the ideal world this "error message" is used only once in the process; Therefore: potentially: get in touch with some "ABAPer" and check by "debuging" at the place of the error). Try to check content of memory etc.

C.B.

[former_member272376]

Hello Devdatt,

you should run the Report RC1_REPORT_DOUBLE_INTVERSION to correct and eliminate duplicate internal version of the report as stated in the program documentation. I executed the report several times in our company. The error with duplicate internal versions in table ESTDH seem to occur when a report is generated several times on the same day.

Best regards,

Ute

[christoph_bergemann]

Hello Ute

"The error with duplicate internal versions in table ESTDH seem to occur when a report is generated several times on the same day." => in our system I have never seen similar behaviour (even the the repoer was generated often per day).

But ... we have "Change numbers" even on "report" level. I might imagine that then some issue might come up... but never seen. (and the errors which we can detect are because of "wrong" coding in some customer processes but not in SAP standard)

How do you check the result if report is used? Is the any "output" of the report (like. the following lines have bee adjusted in ESTDH...??) Never used the report

C.B.

[former_member272376]

Hello Christoph,

you can run the report RC1_REPORT_DOUBLE_INTVERSION in test modus to check the affected reports. It shows Subid, genvar., language, ESTDH-INTVERSION, version and ESTDH-RECN. INTVERSION is the same for several versions and that causes the error in report shipping process. The correction report changes the INTVERSION, means makes subsequent numbering and shows the result when executed in correction mode.

The Standard SAP Programm creating entries in ESTDH seems to have a problem when reports are generated several times in very short time (seconds, few minutes) for the same subid, genvar, language.

We don't use change numbers so maybe that the reason why it happens.

Best regards,

Ute