ESS Role Doubts

[Former Member]

Hi,

Our System component is ECC 6.0 EHP6.I am using portal but I need WD ABAP – ESS &MSS application to be displayed in ESS & MSS portal and need to control the authorization through PFCG Role

Please let me know the which Role I have to use and how to control the authorization through PFCG Role

[Former Member]

Hi Rajendra

Below Link navigates to MSS / ESS WDA  role's

http://help.sap.com/erp2005_ehp_06/helpdata/en/1e/8a70389fa8f63fe10000009b38f842/content.htm?framese...

http://help.sap.com/erp2005_ehp_06/helpdata/en/0f/ad4e45d0fc45f4a315927b53bcc159/content.htm?framese...

To restrict the Authorization

T-code : PFCG

Select the standard role and copy  to " Z " .

Click on Authorization tab and generate profile name

click on maintain authorization next Maintain or remove authorization object

at last maintain USER details for the custom "Z" role

Regards

Sanjay

[Former Member]

Hi Rajendra Prasad,

As seen your System component is ECC 6.0 EHP6.

What is the version of the current  portal ?

There are many alternative option to look the portal for wdABAP,like using the NWBC or going for the upgrade version of portal NW 7.3.

For the PFCG related controls you can take the NWBC option which can be suitable but have its own repercussion check the below helpful nwbc content.

Hope you can have adequate information .

http://scn.sap.com/thread/3245130

http://help.sap.com/bp_ekit604/documentation/NWBC30_EN.PDF

Regards,

Aswin Chandra Girmaji

[Former Member]

Hi,

We are using NW 7.3 and moreover client does not want NWBC which we already discussed with our client .

They want Portal because they already using portal for some other purpose.We need to implement ESS & MSS using WD ABAP

Which is the best option and how to do it

Regards

[Former Member]

HI

For NWBC cost will be high so your client is going for for portal.

since portal user licensing cost is less when compare to NWBC cost.

All the  standard /custom ESS / MSS WDA r/3 application can be maintained in launchpad .

In portal, ESS/MSS roles are assigned to user's.

Regards

Sanjay

[siddharthrajora]

NWBC is cheaper compared to portal.

You can refer these blogs and this important note 0001685257

http://scn.sap.com/community/erp/hcm/employee-self-service/blog/2012/05/31/tips-recommendations-for-...

[Former Member]

Hi Siddharth

Thanks a lot for sharing this information.

I got to know that portal platform uses lot of component separately and delivery process will be different , business package will be shipped. where as for NWBC delivery process remain unchanged and NWBC roles will be shipped .

But my question is does NWBC ESS/MSS user and Portal ESS/MSS user licensing will have same  cost ?

Regards

Sanjay

[Former Member]

Hi,

I am checking in the portal ,The below portal role which is not there

SAP_EMPLOYEE_ESS_WDA_1 and it says it is obsolete so i have to use SAP_EMPLOYEE_ESS_WDA_2 in back end system.

When i check in the portal SAP_EMPLOYEE_ESS_WDA_2 role is also not there.

Please let me know what should i do

[Lukas_Weigelt]

Hi Rajendra,

SAP_EMPLOYEE_ESS_WDA_1 and SAP_EMPLOYEE_ESS_WDA_2 are R/3-Roles, not Portal Roles. The Standard Portal role for the Launchpad-based Navigation used since BF HCM_ESS_WDA_1 is:

pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.pct.erp.ess.wda.roles/com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA

Use SAP_EMPLOYEE_ESS_WDA_2 as a foundation for the authorizations, copy it into Z-Namespace, do your changes in the authority objects and Map that Z-R/3-Roles to the standard Portal role in the portal identity management. For service visibility configure the Launchpad Role ESS Instance MENU

That would be the most straight-foward approach.

Cheers, Lukas

[Former Member]

Yes Dude I understood sorry Still I am not clear

I am very clear about NWBC concepts it is fully ABAP system .Portal is not required.

but I am using portal 7.3 and i would like to use WD - ESS and MSS application through portal (Java)

Please let me know which role i have to use and it should be any impact for future maintenance

Regards,

[Former Member]

Yes Dude I understood sorry Still I am not clear

I am very clear about NWBC concepts it is fully ABAP system .Portal is not required.

but I am using portal 7.3 and i would like to use WD - ESS and MSS application through portal (Java)

Please let me know which role i have to use and it should not be any impact for future maintenance

Regards

[Lukas_Weigelt]

I already answered these question in my prior post.... I don't understand why you bring up NWBC now...

You say you want to use WD ABAP in ESS/MSS portofolion on EP 7.3, fair enough. In my prior post I stated which Portal Role you need (the one starting with pcd:portal_conten/...), which R-3 Roles you need for the authorizational basis (SAP_ESS_* and so on)... and what LPD-Role/Instance you need to configure the navigation (ESS MENU) I don't see what's not to understand, please elaborate precisely what confuses you.

Cheers, Lukas

[hitesh_arora_erp]

Hi Lukas,

I have a similar issue ,we have activated E Separation services ,now these services are only visible in ESS ABAP role,Is there any way we can use these links in standard ESS role??

Or we have to use both roles for ABAP services??

 

[Lukas_Weigelt]

What you describe as "standard ESS Role" seems to be based on Homepage Framework Navigation and since E-Separation is released from EHP5 onwards I doubt SAP bothered to deliver entries for the old Homepage Framework for the E-Separation Services, i.e. you'll have to create the Ressources (V_T7XSSSERRES), Services (V_T7XSSSERSRV) , and the Linkings between Services and Sub Areas (V_T7XSSSERSAR) yourself.

Cheers, Lukas

[hitesh_arora_erp]

hi Lukas,

Thanx for ur valuable info,If I go other way round by using ABAP role for all ess user ,will all services under old role will be available in ABAP role??

regards,

Hitesh

[Lukas_Weigelt]

No, because some services simply are obsolete and are partially replaced by new WDA based scenarios. If you want to to explore options in terms of scalability, usability (from the developer's point of view) etc concidering the navigation approach for ESS, I'd recommend you to use the Launchpad Navigation instead of HPF. It's (In my opinion) simpler to handle and provides an overall better clarity and, what probably will interest you most, new services shipped via upgrades will be considered here, in HPF they will not.

wrote a pretty good blog with customization approaches for Launchpad, Siddharth also posted it already in his reply, oh well, better safe than sorry:   

Cheers, Lukas

[hitesh_arora_erp]

Thanx for the insight .really cleared my mind.