Is it possible to run BP ESS/ MSS 60.x on J2EE stack 7.0 (EP 7)?

Hi there,
is it possible to run BP ESS & MSS version 60.x on a J2EE server stack 7.0 (EP7.0) ?
In the contentportfolio area of SDN ([https://www.sdn.sap.com/irj/sdn/contentportfolio]) it is stated, that BP MSS 60.1.2 runs on
---> iView Runtime Technology:
Java / WebDynpro (WAS 6.40 and higher)
(Link: [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/70649942-a46d-2910-be9b-88db98b484f5 [original link is broken]])
Same for BP ESS 60.2.
([https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/d0dfa6ad-9b6d-2910-3d9a-f278ecc80c60 [original link is broken]])
What does "and higher" mean? Do you see any problems ?
I have studied a lot of notes already, but couldn't find a clear statement on this.
Many thanks and kind regards,
Jenny

From what I have "heard", it is possible. I say that because right now, I am on ECC6/EP7 at my current client. But my previous client was on ECC5/EP6 but are now moving to EP7...and have not had problems yet. I would suggest giving it a go in a sandbox system and checking it out...same as you would do for any upgrade. The fallback is that you can upgrade your portal to EP7 but then run a separate server for your XSS apps from ECC5 (that's kinda the point of the WAS anyways....you can run your apps on separate servers than your "main" server). Your JCO connections would point to the "middle" server and those apps would then "talk" back to your ECC5 box. Anyways, I "think" just having them on the EP7 box would work.

Similar Messages

ESS/MSS Component in CE 7.1

Hi,
We are trying to deploy the below Components. But We are facing issues Deployment.
SAPESS13_0-20000512.SCA
SAPMSS13_0-20000503.SCA
SAPPSS13_0-20001217.SCA
SAPPCUIGP13_0-20001215.SCA
SAPASR13_0-20001216.SCA
ISHERCSS13_0-20001218.SCA
Is it possible to deploy and run the ESS/MSS Application in CE 7.1
Regards,
Baskar.N

Hi Basker/ Siva Kumar
CE 7.1 was launched with the intention of using it as a platform for building composite apps and not as a full fledged portal and hence you wouldnu2019t be able to deploy / use ESS / MSS or any XSS applications on the CE portal. All ESS/MSS application are developed in NW04s and hence could not run in CE 7.1.
Please refer : http://help.sap.com/saphelp_erp2005/helpdata/en/5b/76a6d7fd3a4e91bfb422405bf3e04d/frameset.htm which says that the SAP ESS (ERP 2005) is based in SAP NetWeaver 2004s.
You can have another portal (2004s)set up where you can install/deploy ESS/MSS and use the federated concept to call this portal in your CE 7.1 (ajax portal). This might help.
Thanks,
Abdul Khadar Pathan

Debugging Workflow in ESS/MSS module .

Hi,
I know the stpes to debugging simple workflow and trouble shooting the same, but now
I want to know the debuggibg workflow steps for workflow running with ESS/MSS module Framework,
The scenario is
Its actually Approving Forms in ESS/MSS module, The Employee applying medical leave from his Id, then it will go to first level approver inbox once he approve it goes to second level approver inbox once he approves then it will go to third level approver inbox and he is the final level approvel once he approve the proces will be done.
The problem is, After the second level approver approves the form its updating wrong third level approver so its not comming to third level approver inbox. The workflow is designed under Z class but I dont have update cone in Z class methods.
The updation part is comming under standard ess/mss framework code.
So please tell me the steps how i can debugg or execute worklow in background for all the steps,
like from first step I like pass the container to second steps and goes on.
Help really appreciated.
Thanks & Regards
James.

Hi James
In ESS/MSS leave request the employee will apply the leave from portal and the workflow will triggered based on the spro which workflow template is used. Has you said that updation my custom cone. What is meant by that. Has as has i know we need to update the infotype 2001. This can be done by std FM.
To degbug.
In the put a external break point of the std FM which screen it call. I hope its called the webdypro java screen which nothing but a std FM. You need to find that FM. Then put a external breakpoint. change the user name from goto menu. Once you approve button is clicked in the portal. The debugger will open.
Regards
vijay

Help about ESS/MSS - Deploy error and landscape question

Hi.
I read a lot of post about this topic, but I continue something confuse about them.
I want to configure ESS and MSS.
My landscape is:
- J2EE 7.0 with Portal 7.0 (2004s) in a server A.
- ECC 5.0 ( with HR component SP05) in a server B.
Server B, has only stack Abap.
Server A is the latest version of Netweaver today. (stack j2ee and stack abap, BI, XI, Portal, etc)
I download and deploy in server A (J2EE 7.0), this components:
- BP ESS for erp2004
- BP MSS for erp2004
When I deploy the ESS BP, the deployment break raising this kind of error with the most of components, for example:

===========================================================================
Deployment started Tue Apr 10 12:01:57 ART 2007
===========================================================================
Starting Deployment of ess/au/addr
Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr.. Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of ess/au/addr finished with Error (Duration 5187 ms)
Starting Deployment of SAP_ESS
Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0' : aborted
Please, look at error logs above for more information!
Deployment of SAP_ESS finished with Error (Duration 4781 ms)

Obviously, for this reason the most of iviews raise errors. A few of these works ok.
I assign role, and others configuration steps, this part I thinks that is OK
I configured the Jco, the role in Portal, the profile in ERP for ESS, etc.
My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
Is necesary install J2ee stack in my server B ? or not?
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Why when I deploy have this problem and the most of components cant deploy it?
For my landscape, which is the recommended setup ?
thanks in advance.!
Leandro.

My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
You can use Portal 7.0 against ECC 5.0
Is necesary install J2ee stack in my server B ? or not?
You don't need to install J2EE stack on ECC system
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Deploy XSS on Portal server not on ECC.
Why when I deploy have this problem and the most of components cant deploy it?
There won't be any issue. Go for ERP 2005
For my landscape, which is the recommended setup ?
As per the landscape mentioned by you, I will suggest go for ERP 2005 & XSS 600.
If you have further queries, mail me at [email protected]

SAP Portal Custom Themes to change ESS/MSS UI Look and feel , possible ?

Hi,
I have a requirement where the look and feel of the UI controls of the ESS/MSS applications have to be different - Jazzy
I know XSS homepage framework is for the customisation of Areas, Sub Areas. What I am more interested is only the look and feel UI of ESS/MSS applications.
If I change the standard theme of portal using Theme Editor and create a new custom theme with different back ground colors, fonts, sizes for all the UI controls,.Will the customised Theme apply on the standard ESS / MSS screens ? Also my doubt is we are using EHP3 and I am not sure how many are Webdynpro java based or webdynpro Abap based.
Will the theme apply to both WDA and WDJ application UI controls?
Any inputs in this regard will be of great help. thanks in advance.
Regards,
Sreeram

Hello,
Check :
[Overview on changing the Portal look and feel.|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d077fa17-7fbf-2a10-d983-fb12decf63c7]
FYI :- Search for wiki on : Stylesheet for WDA without integrating in SAP Portal
Cheers,
Remi

NetWeaver Portal and ERP 6.0: BI, ESS/MSS and full Portal on one machine

Hello,
with ERP 6.0 you need a EP Core Portal for BI Java. An other EP Core Portal for HCM ECC/MSS. The iViews from this portal you integrate in the main portal via federated portal. But in this scenario i need to much portals and have a lot of maintenance costs (administration overhead for evry portal). For a small Customer i will build one Portal for all. It is possible e.g. to use the BI Portal with ESS/MSS and as full portal?
Best regards,
Patrick

Hi,
So you would like one BI installation with both the ABAP and the Java-stack with the full BI-functionallity and additionally the XSS-component and set it up to work against the ECC ABAP-only system ?
I think the scenario would actually work, but:
1) You might get future problems if you want to upgrade your BI-system and not the ECC-system.
Is it possible to run the old XSS-components in the new java-stack ?
2) You might get future problems if you want to upgrade your ECC-system and not the BI-system.
What if the new version of the XSS-component demands certain java-components which the BI-system do not have.
So my recommendation is still to run the java-stack on both systems.
ECC with the XSS-java-components and BI with the Bi-java-components.
This way you do not lock yourself into a corner and each system can be upgrade independent of the other.

Issue while accessing two web-dynpro application, ESS/MSS and Payroll

Hi All,
We are facing one Critical Server Issue in our systems. Following is the scenerio:-
Our Portal system was having one Application known as German Payroll application. Before last two week one more application of ESS/MSS i.e. Time Management has been deployed to our system.
Now the user has two application with two different roles in the portal.
When user try to navigate from Time Management Application to German Payroll application or German Payroll Application to Time Management Application then they are facing Critical Server Error issue.
But once the user try to refresh using CTRL+F5 then the problem got resolved.
========================================================================
German Payroll applications back end server details:P95.
Time Management Application back end server details: P23
Steps to reproduce the issue:
1-login to portalgot to Employee self service tab-wait for 3-5mins
& than navigate to german payroll applications----& faced crtical
server errors:
Log from deafult trace:-
=======================================================
1.#0021280FECEE0028000000A400005A4B0004A2FA644F345C#1305096215265#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdyn
pro.progmodel.generation.DelegatingComponent#km048893#2758##n/a##fa2a61757b9911e08e660021280fecee#SAPEngine_Application_Thread[impl:3]
_9##0#0#Fatal#1#/Applications/Xss#
Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
at
com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit
(ModelHandler.java:205)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit
(InternalModelHandler.java:428)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber
(FcXssMenu.java:570)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit
(FcXssMenu.java:292)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit
(InternalFcXssMenu.java:455)
at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit
(FcXssMenuInterface.java:165)
System 'P95' is not possible because RFC Metadata was retrieved using
System 'P23'. Please assure you have configured the RFC Connections
properly. A Server restart may
be necessary!#
==============================================================
here is the catch....When user is trying to navigate from ESS tab(using
custom jcos for Backend system P23) to German payroll(backend system
P95) after 3 mins ---getting crtical error...Still its using the
data/metadat jcos connection information of ESS applications from
cache...that you can see in default trace.
PS: Standards Jcos are configured for P23 systems:
====================================================
SAP_R3_HumanResources----created with P23
SAP_R3_HumanResources_MetaData----been created with P23
SAP_R3_SelfServiceGenerics----been created with P23
SAP_R3_SelfServiceGenerics_MetaData----been created with P23
=====================================================
P95----Germman payroll
P23---ESS/MSS
Name of Cutsomn Jcos created for bakcend P95 i.e. german payroll
A-P95
=======================================================
SAP_R3_HumanResources:D95
SAP_R3_HumanResources_MetaData:D95
SAP_R3_SelfServiceGenerics:D95
SAP_R3_SelfServiceGenerics_MetaData:D95 configured with sap-wd-arfc-
useSys.
Name of cutom jcos created for backend ESS/MSS P23
B-P23
=========================================================
SAP_R3_HumanResources_MetaData:X23
SAP_R3_HumanResources:X23
SAP_R3_SelfServiceGenerics:X23
SAP_R3_SelfServiceGenerics_MetaData:X23 configured with sap-wd-arfc-
useSys.
========================================================
Jcos parameter of P23 backend:
JCo Pool Configuration
Maximum Pool Size: 50
Maximum Connections: 100
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
Jcos parameter of P95 backend:
JCo Pool Configuration :
Maximum Pool Size: 5
Maximum Connections: 10
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
===================================================================
After more analyzing the situation we found that one web dynrpo component i.e. pcui_gp~xssutils is common to both the application and it is configured to standard JCO i.e.
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
My thinking is that this component is giving us the problem.
Please provide your comments and solution to rectify this issue.
Also, let me know in case you need more information.
Thanks in Advance
Kuldeep Verma

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

ESS MSS - Multiple Broken DCs in CBS

Hello All,
We are working on Netweaver Portal 2004s SP15.
We have deployed ess, mss and pcui_gp patches of SP12.
We have also installed the NWDI.
We have created new track, and added ess,mss and pcui_gp software
components to it. We have checked in and imported following components:
sap.com_EP_BUILDT 7.00 15
sap.com_SAP-JEE 7.00 15
sap.com_SAP_BUILDT 7.00 15
sap.com_SAP_ESS 600 12
sap.com_SAP_JTECHS 7.00 15
sap.com_SAP_MSS 600 12
sap.com_SAPPCUI_GP 600 12
But when we observed in CBS, there are many Broken DCs like
pcui_gp/xssutils, pcui_gp/xsscfg, ess/no/pdata, ess/no/bank, etc.
Because of this we are unable to build the projects in NWDS
successfully. NWDS log says:
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo
Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils
Warning: Source folder "META-INF" does not exist and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.09 seconds
Ant runtime 7.2 seconds
Ant build finished with ERRORS
[Error] Generation failed!
Error: Build stopped due to an error: [Error] Generation failed!
Build plugin finished at 2008-06-26 14:29:36 GMT05:30 (IST)+
Total build plugin runtime: 10.265 seconds
Build finished with ERROR
Please help us solve this problem as soon as possible.
Regards,
Vinod

Hi Alexander
Thanks for the reply.
We have imported the required SCAs into new track. That workd fine and these are visible in NWDS.
The problem is with our custom made SC which contains some DCs built on java1.4. When we import this SCA, it is shown as broken in CBS. that is also fine because the CE7.1 runs on java1.5. (There may be some build errors)
The problem is we are not able to see these broken DCs in to NWDS.
Regards
Arvind

Need help on ESS/MSS BP's impact due to Upgrade from ECC 5 to ECC 6 EHP5

Hi,
We are upgrading from ECC 5.0 to ECC 6.0 EHP5 and EP 6.0 SP23 to EP 7.0 EHP2 {7.02}.
Right now the ESS/MSS BP's used in the Existing system (ECC 5.0 and EP 6.0) are given below.
sap.com BP_ERP4ESS 60.2 SP0 (1000.60.2.0.0.20050419020715)
sap.com BP_ERP4MSS 60.1 SP1 (1000.60.1.1.0.20080618080447)
i.e.
sap.com SAP_ESS 100 SP16 (1000.100.0.16.0.20090316001300)
sap.com SAP_MSS 100 SP20 (1000.100.0.20.0.20081013052238)
sap.com SAPPCUI_GP 100 SP20 (1000.100.0.20.0.20081013052239)
We want to run the same BP's in the New environment (ECC 6.0 EHP5 and EP 7.0 EHP2 {7.02}).
If anyone has idea on this, Please let me know is it possible or any modifications to be done ?
Please send me some documentation to get clear idea.
Thanks & Regards,
Ashok M.
Edited by: Ashok Kumar Munugoti on Oct 20, 2011 8:22 AM

Well i would recommend to use lates BP cause lot has changed from ECC 500 to ECC 600
and they wont be supported and you ll definately get support mismatch here
read here for compatibilty issues
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES

Upgrade path for ESS/MSS business package while upgrading to ECC 6.0

Hi All,
We have a scenario where SAP Enterprise Portal 7.0 SP 18 is currently running with SAP ECC 4.6C. SAP ECC is being upgraded to SAP ECC 6.0 and consequently we have a requirement to upgrade to the latest ESS/MSS business package. In a scenario like this what is SAP recommended approach for ESS/MSS upgrade? My questions are
1) Is a direct upgrade of ESS/MSS possible? If this is possible, then how will it be done on a production system with reduced or no downtime?
2) Should ESS/MSS business package be deployed and configured afresh after removing/undeploying the existing version of ESS/MSS business package? If this is the case how would the earlier customizations be restored?
3) Is there any other approach?
Thanks in advance.

Hi Suresh,
In my openion, it will be good if you go for new implementation, reason being as you mentiond ECC versionyou are on is 4.6c all the ESS applications are ITS based now a days all the application/iView for ESS are Webdynpro for Java or WD for ABAP based.
Till the time the new portal ready you can continue with your currect one (No down time require).
Most of the people are using this way. (Check the SDN for more details).
Also chcek this migration guide, which will give you the basic steps required.
http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/5e1226c7-0601-0010-7d82-a8134e833150&overridelayout=true
Regards,

Customised Error Message for ESS-MSS Applications

Hello All,
Currently, if there are any errors in the ESS/MSS transactions, we get the 503 error with lot of irrelevant data to the users. We have a basic html page which says, "There is a issue-Please contact XXXX".
Is there a way to replace the standard error message with this html page ?
PS: I am not talkign about the "Dispatcher Running" or "Application Stopped" messages, Please do not point me again to SAP Help website which doesn't answer my query. THIS IS ABOUT REPLACING THE STANDARD ERROR MESSAGES FOR ESS/MSS APPLICATIONS.
Any help is much appreciated.
We are on EP 7.01 SP3 (ESS 1.41)
-Raj

Hi Raj
Let me clarify the difference between ESS and MSS errors and JAVA stack errors
A "503 Service not available" is not an ESS or MSS error - this is the thrown by the stack (possibly while navigating
in ESS or MSS)
The only information I have available in the case of java stack errors is to follow
http://help.sap.com/saphelp_nw70/helpdata/en/9a/e74d426332bd30e10000000a155106/frameset.htm
Whcih indicates how to customize stack errors like 404 or 500
Lastly you can also decide to hide the stack trace as per KBA 1596212
To modify an ESS or MSS message this may require modification to front and back-end HCM application - usually
ESS gets error information based on back-end errors example "fill in all required fields"
Hope this helps

ESS & MSS installation steps

hi,
can any one tell me the complete steps to install & configure business packages like ESS, MSS.....
i know that these packages comes in .epa or .sca format.....i tried the business packages in market place but i don't have any password or login id to download.. but i am unable to download these. if possible can any one send me the .sca format of business package files.... & steps to install....& requirements....to install these business packages.....
thanks & regards
vijaya

Hi Lakshmi
You are right.These packages are avaialable in .sca format.The extention of these packages will be SAPESSXX_0.sca where XX is the SP number.
You can deploy these packages using sdm :
1.\usr\sap\SID\JCXX\SDM\program and rum remote.gui
2.connect to the sdm and select deployment button.
3Select the packages you have downloaded from service market place or any other place.This packages should be physically located onto ur server where sap is installed.
4Choose next -next and start the deployment.
You can also deploy this packages using JSPM if ur using NW04S.
1.Put the packages under \usr\sap\trans\EPS\in
2.Login using sidadm and run go.bat from \usr\sap\SID\JCxx\j2ee\JSPM
3.Connect to the jspm
4.Choose the option deployment of sigle support package or bussiness packages
5.choose next and carry on deployment.
I cannot help ypu to download the package.You need to have access to http://service.sap.com/ .
In case after getting these packages you have some prob in deploying it feel free to ask.
Reward suiatble points

Creating NWDI track for ESS/MSS

Hi,
I am trying to implement ESS/MSS (600 SP7). For customization I need to import the package on the track in CMS. Import of JEE, JTECHS, BUILDT and PCUIG were successful. When i tried importing ESS and MSS, import is failing. Check-In of both the components are successful but while importing the component under Development tab, its failing. Import of MSS in DTR is successful but CMS is failing.
Below is the log for ESS:
Info:Starting Step Repository-import at 2007-04-10 12:46:13.0591 +5:00
Info:Component:sap.com/SAP_ESS
Info:Version :MAIN_ERP05PAT_C.20070314050106
Info:1. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
     at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:393)
     at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:335)
     at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:578)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
     at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
     at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1252)
     at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
     at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     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(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step Repository-import ended with result 'fatal error' ,stopping execution at 2007-04-10 12:47:49.0198 +5:00
Regards,
Piyush.
ps: points will be awarded to all helpful answers. )

Hi Bharath
How r u? Hope fine.
I have specified the version above. I am using (ESS 600 SP 7 [P11] & MSS 600 SP 7 [P4]).
Is there anything i can do to resolve the issue in JDBC etc? Whats this AFAIK?
Can u suggest something, a work around, to solve this issue?
Regards,
Piyush.
ps: u can directly mail to my ID, will grant u points for helpful answers. )

SSO not working in ESS/MSS in ERP 2004

I have installed the Business Packages ESS 60.2 and MSS 60.1.2 on EP6 SP9. Another server has the Web AS ABAP 6.40 system and J2EE running the ESS and MSS Web Dynpro apps. It all works fine without SSO. When I change the JCO Destinations for the application data to ticket instead of username/password I get the following error on testing:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: The system is unable to interpret the SSO ticket received
This error also occurs when accessing the webdynpro app directly or through the portal. NB. The portal SSO does work in the case of calling an R/3 transaction or calling webdynpro app iview that does not in turn make an RFC call to the ABAP system. I have followed the SAP help on "Scenario: SSO Between Portal, Web Dynpro, and ABAP Systems".
Any ideas appreciated
Fergus

Hi Prakash
This is the end of the dev_jrfc.trc from the abap/j2ee webdynpro server:
Error file opened at 20050608 101523 British Summer Time Rel 6.40
Error> occured >Wed Jun 08 10:15:23,406< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
Error> occured >Wed Jun 08 10:17:28,544< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
The portal dev_jrfc.trc does not report any errors.
Other information I should have mentioned: EP uses LDAP for user directory, the ABAP system uses its own user management, the J2EE on the ABAP server uses its own user management. The user I am testing with is the same name in all 3 systems and has full admin permissions in each.
Thanks, Fergus

ESS & MSS Team Calendar Customization

Hi Team,
We are implemented ESS & MSS & configured Team Calendar but in that we are facing bellow issues
Can we do customization Team calendar? If it is possible how?
Reporting structure showing wrongly displaying.
    please help me
Regards,
Ajay

Hi Mithun & Jwala,
Thanks for reply, here i am sharing my screen shots please check
We required direct report employees list only should display MSS Team workset
    Emp: Direct report employees only 44 to that manager but in MSS team workset nearly 90 employees
            are displying
I am client side functional consultant, my ESS & MSS project done by other company
Now they left the company I had no much knowledge on the ESS& MSS Team calendar just I had knowledge functional side so please guide me to close my issue
Thanks,
Ajay

Is it possible to run BP ESS/ MSS 60.x on J2EE stack 7.0 (EP 7)?

Similar Messages

Maybe you are looking for