COnfiguring MSS Iviews ECC 5.0 and BP 60.1.2

HI All,
I am trying to configure reports on portal with ECC 5.0, BP for manager 60.1.2 and portal 7.0.
I am having trouble in locating the right Iview which I cna modify properties to pull the ABAP reports for SAP query.
Can any one tell me which Iview I need to configure. I know for ECC 6.0 it would be laund pad Iview.
The role in ecc 5.0 is com.sap.pct.mss.roles > MANAGER
DId any one work on this enviroment before does ECC 5.0 support Manager reports? if it does can you please give me which Iview I can set the application properties.
Right now, on my staff>reporting > selection criteria> Here, I see no data found. I am sure here for this iview some properties need to be set so data can be visible from sap query. Just want to know exactly what property to change.
Thanks and highly appreciate your help.
Raj

search for iview with ID.
com.sap.pct.hcm.rpt_reportselection
open it to edit properties.. open object... select parameter Scenario and enter Scenario name MDT or whatever is applicable.
Hope this helps,
Rgds

Similar Messages

CCMS Configuration Guide of ECC 5.0 and BW 3.5

Hi,
Can anyone send me the CCMS configuration Guide (Step by Step) for ECC 5.0 and BW 3.5.
Regards
Chandu

Hi,
Try this,
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/30237989-0901-0010-70a4-944691eb5e52 [original link is broken]
http://service.sap.com/monitoring
Thanks
DST
Message was edited by:
DST

Installing XSS (ESS and MSS) on EP 7 and ECC 5.0 (and ECC 6.0)

Hello,
I need to install XSS (ESS and MSS) on EP 7.0 SP9 and ECC 5.0 and also on ECC 6.0.
I do NOT know what steps I need to perform (installations & configurations).
Could anyone please help me ?
Is the procedure different between ECC 5.0 and ECC 6.0 ?
Please, help.
Kind regards,
Gil

Hello Gil,
1) As I wrote in my second posting, I think I installed the EP 7.0 correctly for XSS and the BP ERP for ERP2005.
Where can I find what configurations I need to undertake and what patches I should install so the XSS and the BP will work correctly ? (that is besides getting error messages when using an XSS iView)
You need to install the foloowing Web Dynpro Components in ur J2EE server.
PCI_GP
MSS
2) If the projects decides NOT to upgrade to ERP 2005 BUT to stay with ERP 2004, do I need to install the EP 7.0 ALL over AGAIN ?
If so, how do I install both the BP ERP 2004 and XSS on it in ONE installation (as I performed in for the BP ERP 2005) ?
If NOT, how do I uninstall the BP ERP and XSS of the ERP 2005 and install those for ERP 2004 ? OR does the BP ERP 2005 support ERP 2004 as well ?
The pre-requiste for BP ERP2005 is a backend ERP2005. So it will not function with backend ERP 2004.
You don't need to uninstall anything. Just download the Mysap ERP 2004 BP and do the necessary configuration to connect it to the BACKEND ERP 2004.This will solve the problem.
You can find the configuration guides and other information abt the BP here.
https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000687949& --> Click on Documents -> Manager Self service.
Hope this solves ur problem.
Regards
Deb
[Reward points for helpful answers]

Standard ESS and MSS Iviews that comes with business package

Hi all,
What are standard ESS and MSS Iviews that come along with business pacakage?
Does leave, appraisal and benefits come under standard?
Pls help.
Thanks
Dhiya.J

Hi Dhiya,
Yes, they all come standard.
Please go through the following links for full details on the applications delivered.
(Might vary depending on the versions you would like to use)
ESS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/5b/76a6d7fd3a4e91bfb422405bf3e04d/frameset.htm
MSS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/29/d7844205625551e10000000a1550b0/frameset.htm
Thanks,
Shanti

ESS implementation posibility with ECC 6.0 and EP 6.0

Hi ,
To implement ESS with ECC 6.0 and EP 6.0
Any body can suggest for this implementation feasibility and possibility.
What are the Business packages has to down load and where can we get those BPs.?
After importing into EP 6.0 , what are the configurations and settings required to get SAP HR screens/ivews (preview when we create after systems in EP),
What are the prerequisites and hardware and software requirements for 8000 users (apprx) ?
Any version upgradations are required for implementing this or
can we use this ECC 6.0 as backend and EP 6.0
and please help required for all those things.
Thanks
Kumar.

For ESS/MSS based on ECC 6.0 (ERP 2005), you can download the XSS business packages from
service.sap.com/download --> Support patches and packages --> Entry By application Group --> SAP Application Components --> SAP ERP -->
SAP ERP 2005 --> Entry By Component --> SAP XSS --> (SAP ESS 600, SAP MSS 600 and SAP PCUI_GP 600).
You can use JSPM to apply these business packages on to the portal. To use JSPM, you have to login to the portal server using <SID>adm to be able to use the JSPM tool.
Business Packages and components in it: you BP consists of the 2 following parts
1) BP_ERP5ESS / BP_ERP5MSS is Portal Business package which consist of iview, pages and roles.. while SAP_ESS / SAP_MSS. is WebDynpro part of it.
These iviews will direct to some WD application which are part of SAP_ESS / SAP_MSS. and they are deployed on server.
2) you have to simple go to
service.sap.com/downloadSupport patches and packagesEntry By application GroupSAP Application ComponentsSAP ERPSAP ERP 2004/2005--Entry By ComponentSAP XSS
pick the correct version and download. You get full package not incremental. Old ones will be overwritten when you deploy them. try to download them again if it failed first time.
3) Refer note 761266 for package compatibility.

MSS Iview error - Any body help me - Very urgent

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
Any help will be highly appreciated.

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
Any help will be highly appreciated.

Configuring MSS 60.1.5

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
Any help will be highly appreciated.
Regards
Vaibhav Dua

Hello Vaibhav,
have you find a solution for your problem yet?
Im having the same problem. I recently installed MSS 6.1.5 into our EP 6.0 SP14 ontop of a already installed 6.1.2 (Web Dynpro, which is working great!). We did this, because the new 6.1.2 Web Dynpro version is lacking of scenarios.
Anyway, the Config Guide of 6.1.5 doesnt say anything about what System-Configurations you have to setup in order to connect to a backend System.
Does anyone know how to setup the Backend-Connection for the 6.1.5 MSS?
regards,
Markus

ESS/MSS in ECC 6.0 are Abap or Java WebDynpro ?

Hi ,
We are on ECC5.0 and have ESS/MSS on Java WebDynpro . For ECC6.0 are ESS/MSS in ECC 6.0 are Abap or Java WebDynpro compoment ?
Any watch out when updrading from ECC5.0 to ECC6.0 ?
Thank you .

in ECC 6.0, ESS/MSS are WebDynpro Java calling ABAP backend function modules. However, be careful, there is a switch that enables SOME ESS services as ABAP WebDynpro (Especially in the Travel management area). Unless you use that switch all services are WebDynpro Java.
when upgrading from ECC5.0 to ECC 6.0 you need to test again all ESS/MSS services. In ECC5.0, services are written as Portal iViews, so customizations you made to ESS in ECC5.0 may be lost.
let me know if you still have questions.
Tiberiu

MSS Iview error -Could not connect to the R/3 System

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
Any help will be highly appreciated.

Hi Mahesh,
Thanks for your repley, I am using the "SAP_R3_HumanResources" as a default alias, The same alias is working fine for my ESS Configuration.
I tried to test connection for the "Connection Test for Connectors" i am getting following error.But Connection test is success for the "ITS Connection"
com.sap.mw.jco.JCO$Exceptionoccured->Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=XXXX SYSNR=00 GWHOST=XXXX GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service '?' unknown TIME Wed Aug 30 16:42:35 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 11
my understand is , ESS is working fine for me because ,ESS iviews are IAC's based iviews which are running on ITS(ITS connection is working fine for me),
i think some problem with connectors(jco).....could you please suggest me.
Thanks
Aravinda

No preview button or option for all ESS MSS iViews under portal content

Hi All,
We are doing a green field implementation for one of our clients, we have installed ECC 6.0 with EHP5 in R/3 system and SAP Netweaver Portal 7.02 with SP8. We have also deployed suitable ESS MSS business components from service market place.
BP_ERP5ESS 1.41
BPERPESSWDA 1.50
BP_ERP5MSS 1.51
As it is EHP5 in ECC all the Homepage framework, Areas, Sub areas, services are preconfigured for standard ESS MSS business areas.
In Portal side under Portal content - Content Provided by SAP - End User Content - Employee Self Services -
we are not able to preview any of the iViews. can anyone suggest whether what may be wrong...?

Hi Sandeep,
1. Yes we are accessing portal through FQDN
2. IE 6.0
3. I mentioned above, its SAP Netweaver 7.02 with SP8
4. Yes, the user I am using has Super Administrator role
5. There are roles for ESS in ECC
This problem of preview is for other iViews also. I mean other than ESS MSS iViews.
Thanks,
Kalam.

MSS Iview Problem -Any Experts help please

I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
ITS - Standalone ( Not integrated)
when i test my System object for ITS ,it is working fine , but it is failed   for WAS Connection and Connector test
Any help will be highly appreciated.

Hi Umair,
Thanks for your response, i am getting same error for all iviews.I pointed that there is some problem with my System object, i tried to test connection for the "Connection Test for Connectors" i am getting following error.But Connection test is success for the "ITS Connection"
com.sap.mw.jco.JCO$Exceptionoccured->Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=XXXX SYSNR=00 GWHOST=XXXX GWSERV=sapgw00 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service '?' unknown TIME        Wed Aug 30 16:42:35 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 COUNTER     11
my understand is , ESS is working fine for me because ,ESS iviews are IAC's based iviews which are running on ITS(ITS connection is working fine for me),
i think some problem with connectors(jco).....could you please   suggest me.
Thanks
Aravinda

MSS iview error

Hi
I have configure ESS/MSS on EP 6.0 and backhand is ERP2004
when i click personal information iview i get following error
no jcoMetadata found for RFC function &\#39;ISR_COMPLETE_NOTIFICATION
since i mantaioned all JCO accoring to help document.
how can i solve this error.
regards,
kinjal

Hi Kinjal
look at sap note 800288.
for further detail look at following forum.
MSS-mySAP ERP2004-Error in Personal Change Request
regards,
kaushal

MSS iview talent profile internals

hello experts,
in the MSS iView talent profile (See help link below)
http://help.sap.com/erp2005_ehp_04/helpdata/EN/9e/71dad0aba74a62a07bdee6edf8d91f/content.htm
information is presented in two visual areas (left and right):
1. the left side shows information for talent data, org assignment, successor etc
2. the right side is an FPM component with tabs for Overview, Resume, Talent Assessment, Mobility, Career Goal, Development Planths
where is the ABAP code that populates the left side of the iView (talent data, org assignment, successor for).
note: I found component configuration HRTMC_LP_OIF for component FPM_OIF_COMPONENT, which populates the FPM tabs, but what is the source code (abap component) reponsible for populating the left side of the iview (to the left of FPM)?
T.

Hi,
You mean write an Enhancement in the Web Dynpro ABAP application (which is not trivial - to me at least - since it relies on FPM) ?
Another idea I got is to set an handler on the ICF service for Web Dynpro ABAP application HRTMC_EMPLOYEE_PROFILE so that the ABAP Proxy is called first and a call to the super Handler (Web Dynpro) is done after.
Update 21-01-2010
Looks a lot like Chain-Of-Responsibility Design pattern to me !
Exploring OO Design Patterns: The Chain-of-Responsibility Pattern
Best regards,
Guillaume

NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
ECC5.0
Abap Stack
EP6 SP13
Java Stack
latest versions of MSS and ESS BPs
The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
Any help on this will be greatly appreciated.
Thanks in advance.
Regards, Neeta

Hi,
Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
The error message I get is (rather long....):
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
 com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
 ... 53 more
See full exception chain for details.
Correction Hints
Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
J2EE Engine 6.40 patchlevel 95420.313
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system SunOS, version: 5.10, architecture: sparcv9
Other
Session Locale en_US
Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
Web Dynpro Code Generation Infos
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
 at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
 at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
 at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
 at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
 at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
 at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
 at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
 at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
 at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
 ... 50 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
 ... 53 more
Thanks, Neeta

Configuring MSS on Portal 6.0

Hi,
Can anybody suggest me the steps to configure MSS business package on portal 6.0. R3 server is ECC 5.0.
Thanks
Shiraz

Hi Shiraz
Steps to configure MSS:
1 - Deploy MSS .sca to your J2EE Engine via SDM
2 - Deploy PCUI .sca to your J2EE Engine via SDM
3 - Make sure you have a SLD available, or you can enable the local SLD on your Portal J2EE instance via http://localhost:port/sld and login as Administrator or J2EE_ADMIN and run the auto import.
4 - Define your ECC server in the SLD as a new WAS ABAP instance and define all the settings via the wizard.
5 - Use the WebDynpro explorer to configure the Jco destinations to use the new WAS ABAP instance in your SLD
6 - Import the ESS business package into the Portal.
7 - Define the system definitions as per the MSS documentation for alias SAP_WebDynpro_XSS and others
8 - Assign Employee role from PCD to your Portal user and assign the relevant profile to your backend user in ECC
9 - Use transaction pa30 to add a communications infotype entry to map your username to an employee in the hierarchy.
MSS 60.1 configuration guide.:
https://www2.iviewstudio.com/support_content/_17011/BP_MSS_ERP04_601_EN.pdf
Hope this helps.
Regards
Yoga

COnfiguring MSS Iviews ECC 5.0 and BP 60.1.2

Similar Messages

Maybe you are looking for