Professional Documents
Culture Documents
(Ess-Mss)
Detailed Steps
1.
2.
3.
4.
5.
Avik Poddar
Roshan Nepal
Wipro Technologies
Contents
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
PREFACE
~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~
ESS - Employee Self Service is an web enabled tool used to update their
own data by the employee itself.
MSS - Manager Self Service is an web enabled tool used for Managers to
take report or update the datas of subordinate.
1.1 ESS :
Allows employees to create, display, and change their own data
in the company's intranet. In Personnel Administration, for example, employees
can use the Personal Data service to create and edit their own personal data. In
this way, employees can keep their own data up-to-date, while simultaneously
reducing the number of time-consuming and expensive activities performed by
the Human Resources Department.
1.2 MSS :
This Manager Self Service is designed for all employees
who perform management tasks at an operational level, for example:
i. Line managers
ii. Team leaders with project management tasks
iii. Department heads
In particular, the business package supports managers perform the following:
-
3. ADOBE FORMS
What is an Interactive Adobe Form?
SAP and Adobe partnered with the goal of automating and streamlining formsbased communication to support customers who create reusable forms for their
business processes. The result of this partnership is SAP Interactive Forms by
Adobe. SAP Interactive Forms by Adobe is integrated into no less than six SAP
development and run-time environments, which cover both stacks of SAP
NetWeaver as well as the SAP Business Suite. These forms are used to display
information from the backend as well as take input from the user and update it in
system.
In the context, you define which part of the interface you actually
want to use in a particular form. You can also add elements like
text modules.
The Scripting for Validations and other Form Level Activities etc. is
done in the Script Editor.
Provide Scenario Name, Description of the Scenario and Application to which the
Scenario relates.
Click on Yes
10
11
12
Create the Form Layout according to the Given Specification, Maintain the
Layout Standards
Check Data Binding for the fields , go to Objects and then Binding
13
Do the Necessary Scripting in the Script Editor under the appropriate Events.
= "readOnly";
14
Double Click on Default Values & Change Default Value for fields
15
Now, after this much configuration if you want to check whether things are
going fine you have to create a process for the form through which you can
check whether the functionality is going on just as expected.
16
9. CREATION OF PROCESS
Click on Process.
Click on Yes.
17
18
10.
DEFINITION OF BADI
Once the BADI is defined , it needs to be implemented for the form scenario as a
backend service and coding needs to be done in the methods already generated, if
there is need of custom methods they can as well be defined and used, appropriate
parameters should be defined for them. Also Attributes need to be defined in the
Class of the BAdi and everything needs to be Active.
19
11.
IMPLEMENTATION OF BADI
Now write the BADI code in the Methods and do the needful
20
21
22
After this you can start on with the coding part. Below a set of code is given that is
applicable to the test scenario that has been developed.
23
12.
Method : if_hrasr00gen_service~get_specials_fields
method if_hrasr00gen_service~get_special_fields.
data init_fields_wa type line of hrbas_fieldlist_tab.
init_fields_wa = c_fieldname_plans. append init_fields_wa to special_fields.
endmethod.
Method : if_hrasr00gen_service~get_field_info
method if_hrasr00gen_service~get_field_info.
data field_info type hrasr00gs_field_info.
data service_field type fieldname.
clear field_infos.
loop at service_fields into service_field.
clear field_info.
case service_field.
when c_fieldname_plans.
field_info-fieldname = c_fieldname_plans.
field_info-field_data_element_name = c_dtel_plans.
field_info-supports_value_help = false.
field_info-supports_default_value = true.
append field_info to field_infos.
when c_fieldname_bukrs.
field_info-fieldname = c_fieldname_bukrs.
field_info-field_data_element_name = c_dtel_bukrs.
field_info-supports_value_help = false.
field_info-supports_default_value = true.
append field_info to field_infos.
24
when c_fieldname_btrtl.
field_info-fieldname = c_fieldname_btrtl.
field_info-field_data_element_name = c_dtel_btrtl.
field_info-supports_value_help = false.
field_info-supports_default_value = true.
append field_info to field_infos.
when c_fieldname_werks.
field_info-fieldname = c_fieldname_werks.
field_info-field_data_element_name = c_dtel_werks.
field_info-supports_value_help = false.
field_info-supports_default_value = true.
append field_info to field_infos.
endcase.
endloop.
endmethod.
Method : if_hrasr00gen_service~get_operations
method if_hrasr00gen_service~get_operations.
data operation type hrasr00gs_operation.
clear operations.
* operation GET_Position Data
clear operation.
operation-operation = c_oper.
operation-fieldnames = get_fields_of_operation( operation-operation ).
append operation to operations.
endmethod.
Method : if_hrasr00gen_service~initialize
25
method if_hrasr00gen_service~initialize.
data special_field type hrasr00value_of_field.
data plans type plans.
* Get position number
loop at special_fields into special_field where fieldname = c_fieldname_plans.
if special_field-fieldvalue is initial.
return.
else.
plans = special_field-fieldvalue.
endif.
endloop.
endmethod.
Method : if_hrasr00gen_service~do_operations
method if_hrasr00gen_service~do_operations.
data service_operation_wa type hrasr00genserv_operation.
data relevant_help_datasets type hrasr00gs_help_dataset_tab.
data relevant_service_datasets type hrasr00gensrv_dataset_tab.
case service_operation_wa-operation.
when c_oper.
*
26
endmethod.
The method if_hrasr00gen_service~get_help_values contains.
method if_hrasr00gen_service~get_help_values.
endmethod.
method get_fields_of_operation.
clear fieldnames.
case operation.
when c_oper.
*
append c_fieldname_pernr to fieldnames.
append c_fieldname_plans to fieldnames.
append c_fieldname_werks to fieldnames.
append c_fieldname_bukrs to fieldnames.
append c_fieldname_btrtl to fieldnames.
when others.
assert 1 = 0. "called for an operation, that is not supported
endcase.
endmethod.
27
method do_opera_get_position_data.
data service_dataset_wa
type hrasr00gensrv_dataset.
data special_field_wa
type hrasr00value_of_field.
* data pernr_id type pernr_d.
data lv_plans type plans.
data lv_werks type werks.
data lv_btrtl type btrtl.
data lv_bukrs type bukrs.
field-symbols <service_field_value> type hrasr00gensrv_dataset.
* get position
loop at special_fields into special_field_wa
where fieldname = c_fieldname_plans.
lv_plans = special_field_wa-fieldvalue.
endloop.
select single werks from pa0001 into lv_werks where plans = lv_plans.
select single bukrs from pa0001 into lv_bukrs where plans = lv_plans.
select single btrtl from pa0001 into lv_btrtl where plans = lv_plans.
loop at service_datasets assigning <service_field_value> where fieldname = c_fieldname_btrtl.
if <service_field_value> is assigned.
<service_field_value>-fieldvalue = lv_btrtl.
endif.
endloop.
loop at service_datasets assigning <service_field_value> where fieldname = c_fieldname_werks.
if <service_field_value> is assigned.
<service_field_value>-fieldvalue = lv_werks.
endif.
endloop.
loop at service_datasets assigning <service_field_value> where fieldname = c_fieldname_bukrs.
if <service_field_value> is assigned.
<service_field_value>-fieldvalue = lv_bukrs.
endif.
endloop.
endmethod.
28
29
30
Assign the required Fields to the Field Group that has just been created,
31
Save the Form Scenario , Check whether Interface, Layout and BADI are Activated.
32
13.
Toggle to Process and Enter the Process Name that you created , click Enter.
Check for a value for which all the concerned data are maintained in SAP and
Execute.
33
34
So, Now once you are sure that the Back-End Services are working just as
desired you can move on with integrating the form in the portal.
In absence of the actual ESS MSS Portal you can always simulate it in
WebDynPro component that can be generated through Object Navigator
35
36
15.
37
38
A List of all the available Process for that Employee appears, select the process that
has just been created.
39
40
The form comes with current details autopopulated based on the Employee ID
provided.
41
42
The Details according to the Position No. gets populated in respective fields.
43
44
Finally click on Send and if everything went fine the Process gets completed and a
Process Reference No. is generated
END
45