Hello,
I'm trying to turn on the reporting launchpad in MSS. I am trying to use the delivered scenario of RPT0 and I've added a new tcode function to it. When I run the IMG step "Convert MDT Data to MSS Reporting Launch Pad" I get the message that no MDT entries are found.
Why is it not finding the RPT0 entries? Is there an additional config step I'm missing? Also, I'm not sure if this relates to this issue, but the IMG step under MSS for setting up the launchpad does not exist in our system. I can't seem to find what activates it but I'd appreciate input on this if you've seen it before. I can get to tcode FPB_LP_MSS_REP_CUST if I enter it manually.
Thanks,
Eric
what is the scenario of your reports?
Please check the steps in
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=199820849
and also run test report in backend and see what error you get?
did you check this link
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=199820849
it has all the steps!
report category should be rpt0, ensure steps are followed in above wiki
you need to adjust iview properties if you use another report category
Therefore the best option would be to change the report category to
"RPT0" in the backend system for all your reports.
ie
2)Their is an Iview property called "Scenario" in the reporting iview.
By default this property is set as "RPT0" . When the reports are
accessed by the user the scenario type is forward to the backend along
with other selection parameters. The backend function modules use this
information to identify the report. There are times when customers
configure the report category type differently (Z***) for their function
codes in the table: T77MWBFCH "Table for function code hierarchies for
manager desktop". However with ERP2005 only scenario type: RPT0 is
delivered by default. If you observe this issue in your system than you
have two choices to get around this problem.
1)Change the Iview property "Scenario" of the Reporting iview from
"RPT0" to your own type"Z***", than this set of reports will work.
however, the standard reports will not work.
yes you are right. it shouldnt effect but i think i checks the resource on how it is maintained, You can debug and find out
can you check your customisation from the backend
check URL OF PCD PATH in table V_T7XSSSERRES, Please
check this resource
can you paste your configuratoin of the resource and test with the above FM in the backend what error you get?
can you please check directly in portal
ie in Please test the following go to portal >> content administration >>
its an issue with roles
Add a comment