cancel
Showing results for 
Search instead for 
Did you mean: 

ESS for ECC5.0 and EP6.0 SP12

former_member689397
Active Participant
0 Kudos

Hi,

We are using ECC5.0 and EP6.0 SP12 for ESS Portal implementation.

Here,

1. What version we have to use for ESS?

2. What type of development has to use? ITS based or Webdynpro based method?

3. If it is Webdynpro method…Can any one give a step for this Development method and DEV...Tools also

Please any one help me out...Very urgent...

Thnx,

Suriya

Accepted Solutions (1)

Accepted Solutions (1)

suresh_datti
Active Contributor
0 Kudos

1. What version we have to use for ESS?

SAP Employee Self-Service is delivered through SAP Enterprise Portal, a component of the mySAP Enterprise Portal solution.

2. What type of development has to use? ITS based or Webdynpro based method?

ECC5.0 runs on WAS640 where you have the Integarted ITS.. so you can do both ie ITS based & WebDynpro.. I think, you will have to stick to WebDynpro for the std services & any new development. ITS can be use dof rnay of the HTML Templated based Custom services that have been migrated.

3.If it is Webdynpro method…Can any one give a step for this Development method and DEV...Tools also

You will ahve to use the NetWeaver Dev Studio or simply Dev Studio as it is being called now..

Go into the Solution Areas in service.sap.com & you can find all the info you need..

~Suresh

Answers (1)

Answers (1)

ChrisSolomon
Active Contributor
0 Kudos

@Suriya....

My current project (and a few prior to this) are on the same configuration...ie. ECC5.0 and EP6...so here goes from experience...

(1) This will largely depend on exactly which services of ESS you want to implement. With ECC5.0, the newer business package for ESS contains several services that are now WebDynpros...however, not all of the "classic" ESS services have been ported over yet. So, this means that you might have to implement a mix of both the newer and older ESS business packages.(yes, it is possible and no, it is not to difficult). In fact, some of the newer ESS services actually use the older ITS-services configuration in the ECC IMG! Funny eh?

(2) As mentioned....it might be both depending on which services you implement and of those, which ones you need to customize. Just in general, ITS services are way easier to customize and/or create from scratch. WebDynpro services are "nicer" but will be quite a change for folks use to "classic" ABAP development.

(3) I will answer both...for ITS development, just use good old transaction SE80 in ECC and work there....publish out to your ITS instance(s)...either internal or external. Also, another tip....if using internal ITS, make sure you have your services activated in transation SICF. Now....for WebDynpro, this will be some work....the "proper" way to do this is development in the NWDS(NetWeaver Developer Studio) and then deployment/versioning is handled via NWDI(use to be JDI). NWDI by itself will be a fairly large undertaking for your BASIS people to learn if they are not experienced with it....it is basically a transport/deployment system for your Webdynpro (largely Java) applications, but it is not so familiar as the normal transport system BASIS people are use too. Lastly, as I always point people too....SAP provides an online course for about $500 USD that covers this "new" way of development for ESS....more info here....

http://www50.sap.com/useducation/curriculum/course.asp?cid=60162715

The MSS/ESS section/track/map is a smaller part of the overall course.

Hope this helps....and also, if you will be asking about MSS too....well, all of the above are pretty much the same for MSS too. 😃