A form scenario, together with the related ISR scenario, forms the basis of a form-based process and configures the interactive form.
In this sublesson you create form scenario ZTFS and make the following settings:
You define how the form data is processed in the back-end system (back-end service).
You define the basic quantity of the usable form fields and configure default values and input helps.
You define two scenario steps.
You assign the form fields to the back-end service.
Perform the
Create a Form Scenario
IMG activity.
Choose
New Entries
Create form scenario
ZTFS
that belongs to ISR scenario ZTFS, and enter
Relocation
as the description.
Save your entries.
Create the form scenario version that corresponds to the ISR scenario version.
Select form scenario ZTFS.
In the dialog structure choose
Version
and then
New Entries
.
Enter0as the version.
Save your entries.
You must define the back-end service before you create form fields that you want to fill with default values or input helps from the back-end service. If you subsequently create form fields, you can assign the appropriate sequence number to the back-end service.
Define the back-end service for processing the form fields:
Select form scenario ZTFS with version
0
In the dialog structure choose
Services
and then
New Entries
.
Enter the value
100
as the
Sequence Number
. The sequence number determines in what order the back-end services that are used are accessed.
We recommend that you create back-end services with a sequence number greater than 1. This enables you to create additional back-end services that are to be accessed before this back-end service with lower sequence numbers.
Use input help to select the SAP_PA service.
Save your entries.
Define the form fields for form scenario ZTFS version
0
. This includes the following fields:
Mandatory fields that you must always create
Display fields that give the user of the form information about the employee whose data the form changes. For example, data that is part of a form header row
Specific form scenario fields for changing data
In the dialog structure choose
Form Fields
and then
New Entries
.
Use the input values from the tables below.
The following tables schematically represent the input values and do not represent the complete Customizing table columns of
HCM Processes and Forms
Enter the mandatory form fields:
Field Name |
Description |
Default Value Type |
Input Help Type |
Data Element |
---|---|---|---|---|
PERNR |
Personnel Number |
No Default Value |
No Input Help |
PERNR_D |
EFFECTIVE_DATE |
Effective Date |
No Default Value |
No Input Help |
ASR_EFFECTIVE_DATE |
MASSN |
Actions |
No Default Value |
No Input Help |
MASSN |
MASSG |
Reason for Action |
No Default Value |
No Input Help |
MASSG |
CENTRAL_PERSON |
Central Person |
No Default Value |
No Input Help |
OBJID |
Enter the display fields.
Never choose
No Default Value
as the
Default Value Type
for these display fields, or no values will be displayed in these fields in the form.
Field Name |
Description |
Default Value Type |
Srv.No.Field Value |
Default Value |
Input Help Type |
---|---|---|---|---|---|
EMPLOYEE_NAME |
Employee |
Default Value for Specified Back-End Service |
100 |
<BLANK> |
No Input Help |
PERSA_TEXT |
Personnel Area |
Default Value for Specified Back-End Service |
100 |
<BLANK> |
No Input Help |
POSITION |
Position |
Default Value for Specified Back-End Service |
100 |
<BLANK> |
No Input Help |
Enter the specific form fields for changing data:
Field Name |
Description |
Default Value Type |
Srv.No.Field Value |
Default Value |
Input Help Type |
---|---|---|---|---|---|
STREET |
Street and House Number |
No Default Value |
<BLANK> |
No Input Help |
|
POST_CODE |
Postal Code |
No Default Value |
<BLANK> |
No Input Help |
|
CITY |
City |
No Default Value |
<BLANK> |
No Input Help |
|
COUNTRY |
Country |
Manual Default Value |
DE |
No Input Help |
Save your entries.
A form scenario must have at least one scenario step.
Scenario steps allow you to define specific Customizing for process steps. This Customizing affects the use of certain fields, the processing of attachments, and the availability of hyperlinks.
For these settings to come into effect when the process is run, in the appropriate workflow step you must also define which scenario step to use. When defining the process start under Creating a Process , you define which scenario step is used to start the process.
First create the following two form scenario steps for process ZTPR
Relocation
:
FSS_1Request
FSS_4Department Check
The scenario step description should be as clear as possible (not an abbreviation) since it is used as the text for the work item in the processor’s
Universal Worklist
.
In the dialog structure choose
Scenario Steps
and then
New Entries
.
Create the following scenario step:
Scenario step:
FSS_1
Description:
Request
Create another scenario step:
Scenario step:
FSS_4
Description:
Department Check
Save your entries.
You must assign the form fields to the back-end service used. A back-end service is accessed only if at least one field is assigned to it. Only the values of the fields that are assigned to the back-end service are transferred to it. You determine how the back-end service individually processes the form fields by configuring the back-end service in Processing Form Scenario for Infotypes (Service SAP_PA) .
In the dialog structure choose
Form Fields of Service
.
Define the
Work Area
:
Select version
0
Using the input help, select the back-end service with sequence number
100
The
Change Form Fields of Service
view appears.
Choose
New Entries
Using input help, select a form field under
Field Name
.
Repeat this step until all form fields are assigned.
Since you are only using one back-end service in this case, assign all form fields to the SAP_PA service.
Save your entries and exit processing.
You have created form scenario ZTFS version
0
with the mandatory fields, the display fields, and the form fields from the
Addresses
infotype (0006) that are required for making changes. You have created the scenario steps FSS_1
Request
and FSS_4
Department Check
, and assigned the form fields to the SAP_PA back-end service.