Personnel Change Requests: Direct Launch

Technical Data

Runtime Technology

Java/Web Dynpro

Technical Names of iViews

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_speg

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sppa

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spwt

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spsp

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sppm

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spps

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sptr

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spse

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sppd

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sptd

com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spsd

com.sap.pct.erp.mss.pcrdirectlaunch

Technical Name of Web Dynpro Application

sap.com/mss~pcr/PcrDirectLaunchApplication

Available From

SAP NetWeaver 2004s

Data Source

SAP ECC 6.0 or above

RFC modules called: see RFC-Function Modules for Personnel Change Requests

Software Component

SAP_HR

Support

EP-PCT-MGR-HR

Features

Managers use these iViews to create a request for the data of their employees to be changed in the ERP system. In contrast to the Personnel Change Request iView, managers use these iViews after they have selected an employee on one of the Employee Information pages. In this case, managers simply have to select the change request they require.

Managers can access these change requests using links displayed in the Additional Activities iView. When a manager selects one of these links, the Process Form step of the relevant change request is displayed automatically.

Each of the links for calling a change request in the Additional Activities iView corresponds to a separate iView. Managers can access the following iViews:

  • Personnel Change Requests: Change Employee Group and Subgroup – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_speg)

  • Personnel Change Requests: Change Personnel Area and Subarea - Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sppa)

  • Personnel Change Requests: Change Working Time – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spwt)

  • Personnel Change Requests: Request Special Payment – Direct Launch (com. sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spsp)

  • Personnel Change Requests: Request Promotion – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sppm)

  • Personnel Change Requests: Change Position - Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spps)

  • Personnel Change Requests: Request Transfer – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sptr)

  • Personnel Change Requests: Request Separation – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spse)

  • Personnel Change Request: Change Position (Enhanced) - Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sppd)

  • Personnel Change Requests: Request Transfer (Enhanced) – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_sptd)

  • Personnel Change Requests: Request Separation (Enhanced) – Direct Launch (com.sap.pct.erp.mss.relatedactivity_pcrdirectlaunch_spsd)

For more information about the functions of the individual change requests, see Delivered Request Scenarios .

Note Note

You cannot use the generic iView Personnel Change Requests – Direct Launch (com.sap.pct.erp.mss.pcrdirectlaunch) to execute change requests. It is intended as a template if you have created customer-defined request scenarios and you want managers to be able to launch these scenarios directly from the Additional Activities iView.

End of the note.

Integration

Prerequisites

See Personnel Change Requests .

In the standard SAP system, the following settings have also been defined in Customizing for Cross-Application Components, under Homepage Framework.

  • Under Start of the navigation path Services Next navigation step Define Services, End of the navigation path a service key is defined for each request scenario in the format MSS_HCM_SRV_RELACTIVITY_PCR_<Scenario Abbreviation>.

    Example: MSS_HCM_SRV_RELACTIVITY_PCR_SPEG

  • Under Start of the navigation path Resources Next navigation step Define Resources, End of the navigation path a resource object key is defined for each request scenario in the format MSS_HCM_SERV_RELACTIVITY_PCR_<Scenario Abbreviation>.

    Example: MSS_HCM_SERV_RELACTIVITY_PCR_SPEG

If you have created customer-specific request scenarios that you want to enable to be launched directly, you must enter an appropriate service key and resource object key in the mentioned IMG activities.

Settings

The request scenario is entered in the properties of the appropriate iView as a Web Dynpro application parameter in the format SCENARIO=<Scenario Abbreviation>.

Example Example

In the Personnel Change Requests: Change Employee Group and Subgroup – Direct Launch iView, SCENARIO=SPEG is entered as the application parameter .

End of the example.