cancel
Showing results for 
Search instead for 
Did you mean: 

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

devdatt_khedekar
Participant
0 Kudos

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.

View Entire Topic
christoph_bergemann
Active Contributor
0 Kudos

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
Participant
0 Kudos

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
Active Contributor
0 Kudos

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.