To be able to use a
form scenario
in a process, you have to create one
ISR scenario
for each form scenario. You make this setting in Customizing for
HR Administrative Services
by choosing
Configuration of Forms/Processes
→
Configuration of Forms
→
Create ISR Scenario.
The ISR scenario is used for the following purposes in
HR Administrative Services
:
To define the input type (for the interactive form) used by users to enter the data
The default input type is
Input with Adobe PDF
and cannot be changed.
To define the interface for accessing the form
The interface is generated automatically from the features (form fields) once the form has been created, and is used to access the form.
To define an interactive form
You set up the form by selecting and positioning UI elements for displaying fields, and link the form fields to the UI elements.
For detailed information, see Creation and Editing of an Interactive Form .
The ISR has a 1:1 relationship with the form scenario. You establish the link between the ISR scenario and the form scenario in Customizing for
HR Administrative Services
by choosing
Configuration ofForms/Processes
→
Configuration of Forms
→
Link ISR Scenario with Form Scenario.
The version of the ISR scenario must be identical to the version of the form scenario to which it is linked. You have to check this manually.
To configure a ISR scenario, proceed as follows:
IMG Activity |
Description |
---|---|
Create ISR Scenario |
You create a rudimentary ISR scenario with a version. |
Create form scenario |
You create the form scenario with an identical version and define the basic set of form fields (display and input fields) that are displayed in the form. In the form scenario, you also define any fields that are not displayed in the form but processed in the background. |
Configure Backend Services: Process Form Scenario for Personnel Admin. Infotypes Process Form Scenario for Time Management Infotypes Process Form Scenario for Generic Services |
You assign the form fields to the backend services, where you configure the operations and field characteristics. |
Link ISR Scenario with Form Scenario |
You create the link between the ISR scenario and the form scenario so that the form scenario can be used in a process, the form fields can be compared, and so on. |
Create ISR Scenario View:
View:
|
You perform a comparison with the form fields of the form scenario. The system automatically creates the fields (features) in the ISR scenario. The features are displayed in the ISR scenario, but can be created and edited only in the IMG step for the form scenario. You generate the interactive form for the version of the ISR scenario. For more information, see Creation and Editing of an Interactive Form . |
If you have already created the ISR scenario and configured the form scenario, you can omit the above steps. Perform the IMG activity
Create ISR Scenario
, select the required version, and choose
Compare Form Fields
.
Name |
Example |
||
---|---|---|---|
|
SOC1 |
||
|
Transfer |
||
|
H (HR Administrative Services) |
||
|
0 |
||
|
Transfer |
||
|
Input with Adobe PDF |
||
|
ISR_HRASR_SOC1 |
||
|
ISR_IF_SOC1 |
||
|
|
|
|
1 |
BTRTL_NEW |
New personnel subarea |
|
2 |
BUKRS_NEW |
New company code |
|
3 |
BUKRS_NEW_TEXT |
New company code (text) |
|
4 |
CENTRAL_PERSON |
Central person |
|
5 |
EFFECTIVE_DATE |
Date of change |
|
6 |
EMPLOYEE_NAME |
Name of employee |
|
7 |
FORM_SCENARIO_STAGE |
Scenario step |
|
8 |
MASSG |
Reason for action |
|
9 |
MASSN |
Action |
|
10 |
PERNR |
Personnel number |
|
11 |
PERSONNEL_AREA_TEXT |
Personnel area (text) |
|
12 |
PLANS_NEW |
New position |
|
13 |
POSITION_TEXT |
Position (text) |
|
14 |
PROCESS_REFERENCE_NUMBER |
Reference number of process |
|
15 |
RCV_MGR_FORMATTED_NAME |
Formatted name of manager |
|
15 |
RCV_MGR_UNAME |
User name of manager |
|
17 |
SACHA_NEW |
Payroll administrator |
|
18 |
SACHP_NEW |
HR administrator |
|
19 |
SACHZ_NEW |
Time Recording administrator |
|
20 |
WERKS_NEW |
New personnel subarea |
|
21 |
HRASR_PREVIOUS_NOTES |
Previous comments |
|
22 |
HRASR_CURRENT_NOTE |
New comments |