Empty iviews in MSS ERP 2005

Question

Hi,
We've installed the above business package.  When we click through the iviews, a lot of them are coming up empty. 
For example the following iviews under Overview -> Team -> Employee Information are empty:
1) General Information
2) Compensation Information
3) Personnel Development
The "Create New Personnel Change Request" iview works though.
I've already applied OSS Note 903370.
Any other ideas ??
Thanks,

Answer 1

hi
This may be possible if System properties are not configured properly or backend authorisation SAP_ALl is not given to role .Basically some iviews are BSp iviews others are webdynpro and java .so can you check whether you have configured following
You set up the JCo connections on the Web Dynpro J2EE server on which the self-service components have been implemented.
                            a.      For ESS, set up the following JCo connections:
         SAP_R3_HumanResources
         SAP_R3_HumanResources_MetaData
         SAP_R3_Financials
         SAP_R3_Financials_MetaData
                            b.      For the Self-Services Homepage used by all self-service applications, set up the following JCo connections:
         SAP_R3_SelfServiceGenerics
         SAP_R3_SelfServiceGenerics_MetaData
                            c.      For the self-service applications in the Travel Management area, set up the following JCo connections in addition to those connections previously mentioned:
         SAP_R3_Travel
         SAP_R3_TravelMetaData
       3.      You make the settings required for the area group page (ESS homepage) and the area pages of the individual business areas (Working Time, Career and Job, Travel, and so on).        4.      You set up the ESS users and maintain the required data.
5.     You assign employees the authorizations for ESS.
       1.      Access the Web Dynpro Content Administrator.
The URL is http://<host>:<port>/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
       2.      Log on using the administration user for the J2EE server.
       3.      Create the required JCo connections or edit the existing ones. To do so, choose Maintain JCo Destinations.
A list of the JCo connetions for the metadata and those for the application data is displayed. Connections for various areas exist. The names of the connections start with SAP_R3_*.
JCo connection for metadata: SAP_R3_HumanResources_MetaData.
JCo connection for application data: SAP_R3_HumanResources.
If the software is already installed on the J2EE server, the Web Dynpro Content Administrator automatically recognizes which JCo connections are required.
                            a.      Configure the JCo connection for the metadata:
1.                                                       i.       In the Connection Type step, choose the Dictionary Meta Data option.
2.                                                     ii.       Choose Security.
3.                                                    iii.       In the Used Method field, enter the User/Password.
4.                                                    iv.       Enter a user in the SAP ECC system that you have created for the authorization check of the JCo connection.
5.                                                      v.       Enter the password for the user.
6.                                                    vi.       Check the connection.
If the user only has the authorizations from the S_DDIC_MDI profile, the system issues the following error message when you check the connection:
com.sap.mw.jco.JCO$Exception:(104) RFC_ERROR_SYSTEM_FAILURE: No RFC authorization for function group SSCV for user <your metadata user>.
This message does not mean that the specified user does not have the required authorizations for the metadata. It means that the user’s authorizations are not sufficient to test the connection.
                            b.      Configure the JCo connection for the application data:
7.                                                       i.       In the Connection Type step, choose the Application Data option.
8.                                                     ii.       Choose Security.
9.                                                    iii.       In the Used Method field, enter Ticket.
10.                                                    iv.       Check the connection.
The system uses the administration user for the J2EE server with which you are logged on to check the authorizations. If this user does not exist in the SAP ECC
<b>hope this helps you please do not forget to give points</b>
with regards
subrato kundu