on 06-08-2011 5:12 PM
Hi All,
Following JCo are not available in Portal 7.0 for MSS configuration.
Already MSS Buss Pkg has been deployed in Portal.
u2022 SAP_R3_SelfServiceGenericsFIN
u2022 SAP_R3_SelfServiceGenerics_MetaDataFIN
u2022 SAP_cProjects
u2022 SAP_cProjects_MetaData
Getting mention error for MSS application:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaDataFIN' in the SLD. No such JCO destination is defined in the SLD.
Please suggest for resolution.
Regards,
SK
You have to get this fixed through BASIS / Web Dynpro Content Administrator.
Check under Content administrator -> Webdynpro whether all the JCO connections are working fine.
Setting Up JCo Connections for MSS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/15d2060e344c2fbf22e526104c24bb/frameset.htm
Once the ESS / MSS Business Packages are deployed, as a part of the post deployment steps JCO set up is to be completed
Below JCO are to be set up for MSS -
● General connections:
○ SAP_R3_SelfServiceGenerics
○ SAP_R3_SelfServiceGenerics_MetaData
● Connections for the Team area:
○ SAP_R3_HumanResources
○ SAP_R3_HumanResources_MetaData
● Connections for the Budget area:
○ SAP_R3_Financials
○ SAP_R3_Financials_MetaData
○ SAP_R3_SelfServiceGenericsFIN
○ SAP_R3_SelfServiceGenerics_MetaDataFIN
Set up the following for branching to the details screen from Travel work items in the universal worklist:
○ SAP_R3_Travel
○ SAP_R3_Travel_MetaData
● Connections for the Projects area:
○ SAP_cProjects
○ SAP_cProjects_MetaData
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear SK,
Please check in the Content Administrator->Webdynpro->Content Administrator which JCO are listed over there when you click the Maintain JCO Destinations button. Do let us know what all JCO are there. The JCO names are case sensitive and it might cause the error which you are getting for JCO Connection SAP_R3_SelfServiceGenerics_MetaDataFIN.
It might happen that the JCO connection available currently is 'SAP_R3_SelfServiceGenerics_MetadataFIN' with small 'd' in the MetadataFIN.
You can create the JCO SAP_R3_SelfServiceGenerics_MetaDataFIN and maintain the properties General,Security and Connection details for your respective system. It should solve your issue.
Regards,
Samir
In order to keep your accounts, it is imperative that you respond to the email I sent you earlier this week. Otherwise, both may be deleted. This is your last warning.
matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.