Report Assignment are getting dropped from report management

[Former Member]

Hi Gurs,

For the Real Group substance, nine real substances has been assigned in report management. when Iam trying to create a report of new version for real group some of the report assignement are being dropped from real group. any idea why the reports are getting dropped.

Thanks in Advance

Thanveer Ahmed.

[christoph_bergemann]

Hello Thanveer,

this is not the reaction which should happen.

Could you please indicate:

- eh&s version you are using

- Describe the process you have done. I assume you have created on REAL_GRP level a report and released that report (e.g. Version 1.0). Then you have entered the real_subs in the Report header of gthe report. Then you have generated a new version of the same genvariant/language combination. By standard normally now the nine real_subs you have assigned to report header (version 1.0) should be copied to the new report header as you have assumed.

May be check OSS but this functionality is "old" ( i believe was inside EH&S 2.5 latest) and therefore should work.

With best regads

C. Bergemann

[Former Member]

Hi Bergemann

Thanks for your reply. Currently we are in EH&S 2.00 version and I also checked for few SAP notes and found this note 456245 which is related to "Substance assignments of reports are missing". But it was already implemented in our system. Iam not sure exactly why the reports are getting dropped . Can you help me with all Functional scenario's for specification assignment on report management.

Thanks in advance.

Thanveer Ahmed.

[christoph_bergemann]

Hello Thanveer,

it seems to be that you are using SAP Enterprise Extension 2.0 (EH&S 2.00 version does not "exists" and has never been made available to SAP customers to my knowledge). This EH&S has been former known as EH&S 3.2. Actually EH&S does not get any version number any more.

Coming back to your question: the oss note you found seems to be the only one. I did the "same" research like you. So I have really no idea (may be place new OSS) because we are using an older EH&S version and there it works.

Coming back to your last remark:

Can you help me with all Functional scenario's for specification assignment on report management.

If you take a look in the actual help of sap you will find this page:

http://help.sap.com/erp2005_ehp_04/helpdata/en/a7/288aa30a6c11d28a220000e829fbbd/frameset.htm

(report Management (EHS-SAF-REP) => Report Managment Worklist => Specifiction Assignment

Here you will find a subchapter: Assigning specifications to reports)

In this chater this is explained:

Specification assignment can be defined differently for each report version. When creating new versions (or when replacing one version with another), the new report u201Cinheritsu201D the specification assignments of the previously valid report.

This reaction is what I would expact.

In my opinion the scenario which SAP describes there is clear enough. Again here is the story:

a.) you have a specification and you generate a report (first time). You release it (generation variant/Language combination) in version 1.0. Now in using cg50 you can enter on report header additionaly specifications regarding which the report is valid too.

Lets assume this: you have generated the report on specification A and added B and the report is "released". Now if you use cg54 and you use specification in an query A and B you will find total two released reports. The report on the level B is "inherited" from A (this is shown by using a different icon). Now if you generate version 1.1. on specification A (same geneartion variant etc.) the link to the specification B must be inherited to the new report header.

This functionality is in my opinion rarely used on SAP EH&S customer side. The reason is "simple".

a.) there is no mass update of specifications which should be added to the report header and the queriy which can be done there is "very" simple

b.) you need to take care about adding new specifications to the report header (becuase the version before does have a differnt number of specifications)

c.) the process to delete the link is not easy in daily work

In any case: please check the report distribution process. There are some pitfalls etc. inside so thet the report which is released on A can be used on B too in report distributon. Bit this is a different story.

To summerize: the process is in most cases to complex for normal EH&S users. Therefore other options should be analyzed.

With best regads

C. Bergemann

PS: you need to "save" the assignment in cg50; only an idea: may be you missed to do that

Edited by: Christoph Bergemann on Feb 13, 2010 9:41 AM

Edited by: Christoph Bergemann on Feb 13, 2010 10:00 AM

Edited by: Christoph Bergemann on Feb 13, 2010 10:00 AM