Online Tutorials & Training Materials | STechies.com
Register Login

ESS Based on Web Dynpro ABAP

|| || 0

ESS Based on Web Dynpro ABAP
Stechies

SAP has provided the Employee Self-Service (ESS) component based completely on Web Dynpro ABAP technology. The WD ABAP-based ESS services are available with software component EA-HR 605.

You can find a complete list of the services and features available with ESS (WDA) in SAP Library for SAP ERP for SAP Enhancement Package 5 on SAP Help Portal at http://help.sap.com/erp -> SAP ERP Central Componenhttps://www.stechies.com/what-is-mysap-erp/t -> Human Resources -> Shared Services -> Employee Self-Service -> Employee Self-Service (WDA).
This means the customer has the option of not installing the Java parts of the self-services (SAP ESS 603 and other related pre-requisite Java parts, such as SAP PCUI GP 603 components).
An additional deployment option using SAP NetWeaver Business Client for HTML without using the SAP NetWeaver Portal is also available for Employee Self-Service (WDA).
Customers who want to use the new WD ABAP services on SAP NetWeaver Portal must deploy the business package content BPERPESSWDA1.50.
           Note: Some of the services (including some country-specific scenarios) that are available in WD Java based on SAP ESS 603 and EA-HR 603 are not yet available in SAP Business Suite 7 Innovations 2010 and are planned for later release.

For using new WD ABAP-based ESS you need to install SAP Business Suite 7 Innovations 2010 (EA-HR 605) and activate business function HCM_ESS_WDA_1. You can find a description of the business function in SAP Library for SAP ERP for SAP enhancement package 5 on SAP Help Portal at http://help.sap.com/erp -> Business Functions (SAP Enhancement Package 5 for SAP ERP 6.0) -> Enterprise Business Functions -> Human Capital Management -> HCM, ESS on Web Dynpro ABAP.

Strategy for WD ABAP-based ESS:

  • SAP supports both WD ABAP-based and WD Java-based ESS applications, as per the existing maintenance strategy.
     
  • SAP supports the standard deployment options, based on SAP NetWeaver Portal and NWBC.
     
  • New innovations and features provided in future enhancement packages will be delivered in WD ABAP-based ESS only.
     
  • As of SAP enhancement package 5 for SAP ERP 6.0, the Homepage  Framework is discontinued for the WD ABAP-based Employee role and is replaced by service map capabilities based on NWBC client (PFCG role) or as a WD ABAP application based on launchpad Customizing (transaction LPD_CUST).

As of SAP enhancement package 5 for SAP ERP 6.0 you can choose from the following deployment options for ESS:

1. Deployment Option 1: WD ABAP-Based ESS on NWBC

This deployment option is recommended for customers who do not use SAP NetWeaver Portal for the Employee role and would like to use WD ABAP-based ESS. This deployment option is suitable for customers who are implementing ESS for the first time, or who are migrating ESS from older releases prior to ERP 2004 (based on ITS technology).

NWBC for HTML is recommended as a client based on a zero-footprint browser, and can be used by employees without any installation.

Role Delivery:  The composite PFCG role that is delivered is SAP_EMPLOYEE_ESS_WDA_1, and contains all applications.

Homepage or Service Map: The homepage or service map is generated by NWBC HTML, based on the role structure defined in transaction PFCG.

2. Deployment Option 2: WD ABAP-Based ESS on SAP NetWeaver Portal

This deployment option is recommended for customers who use SAP NetWeaver Portal for the Employee role and would like to use WD ABAP-based ESS. This option is suitable for customers who are implementing ESS for the first time, or who are migrating ESS from older releases prior to ERP 2004 (based on ITS technology).

Role Delivery:  The Employee role is delivered with business package BPERPESSWDA1.50. The WD ABAP-based Portal role is a "lightweight" role, which contains a WD ABAP launchpad application iView: This WD ABAP launchpad application acts as a homepage or service map that launches the individual WD ABAP applications, which are not shipped as iViews themselves.

Homepage or Service Map: The homepage or service map is generated by a WD ABAP launchpad-based application. The structure of the homepage is defined in launchpad Customizing (using transaction code LPD_CUST) in the back-end system. The standard launchpad Customizing uses the ESS role and the MENU instance.

3. Deployment Option 3: WD Java-Based ESS on SAP NetWeaver Portal

This deployment option is recommended for customers who have implemented ESS, based on SAP NetWeaver Portal and want to continue using WD Java-based ESS for most of the services.

WD ABAP-based services offer enhanced features and easier usage, and it is possible to replace individual WD Java applications with new WD ABAP applications. However, this requires implementation efforts to build the Portal content (iViews, role) and the appropriate homepage Customizing.

Role Delivery: No new business package content or Portal role is shipped with mixed UI technology. Customers who want to use new WD ABAP-based applications need to adapt the existing business package content and role with additional WD ABAP-based applications delivered with SAP enhancement package 5 and above.

Homepage or Service Map: For WD Java-based services, customers can continue to use the Homepage Framework and additional WD ABAP-based applications can be added to existing Home and Area Page Customizing.

Migration from Existing WD Java-Based ESS to WD ABAP-Based ESS
Customers who wish to migrate a substantial part of the existing WD Java-based services to new WD ABAP-based services can use Deployment Option 2, described above. This option uses the new lightweight Portal role with a WD ABAP-based launchpad application as homepage instead of the Homepage framework.

Additional custom-built or standard applications, which are based on WD Java, can be added to the launchpad Customizing (using transaction code LPD_CUST) in the back-end system as the "Portal Pages" application category. Standard launchpad Customizing uses the ESS role and the MENU instance.

Role Delivery: New business package content and a new Portal role is not shipped with mixed UI technology. It is necessary that customers adopt the existing business package content and role if they want to use this migration option.

Homepage or Service Map: The homepage or service map is generated by a WD ABAP launchpad-based application. The structure of the homepage is defined in launchpad Customizing (using transaction code LPD_CUST) in the backend system. Launchpad Customizing of the standard delivery uses the ESS role and the MENU instance.
           Note: If you continue to partially use WD Java applications it is necessary to deploy the Java parts of SAP ESS on SAP NW Java (EP Core system).


Related Articles

0.0136 seconds.