Definition of Form Scenarios

You use this function to create the basic data for a form scenario. Form scenarios are version-dependent, which means that there is at least one version of each form scenario. You require this version when you want to assign a form scenario to a process.

Since processes can vary, you must also be able to adjust the associated form scenarios. In this case, you can create a new version of the assigned form scenarios to which you can also assign new forms.

Recommendation

As soon as a version is used for running a process, you should no longer change this version under any circumstances. Create a new version instead.

End of the recommendation.

ISR Scenario

For form scenarios of type Adobe Form only, it is necessary to create an ISR scenario that corresponds to the form scenario, so that there is always a 1:1 relationship between a form scenario and an ISR scenario. The ISR scenario is used to integrate the interactive form and create the form layout.

An ISR scenario is not required for an FPM form type scenario. On the Form Scenario screen, the ISR Scenario button is disabled and the ISR Scenario field is cleared and disabled. In the Create Form Scenario dialog box, the ISR Scenario field is disabled.

Digital Personnel File (DPF)

In Customizing for Digital Personnel Files (DPF), you specify if the forms and attachments of a process are transferred to the DPF. When using multiple forms and/or attachment types, a partial transfer is also possible.

An anchor number is assigned to each form scenario. This ensures that the forms from the process documents are inserted under the correct DPF of the corresponding employee. DPF is available for Adobe and FPM form types.

Activities

Note Note

When you create a completely new form scenario, the system first creates version 0. If you want to revise the form scenario later, you can either make these changes in the existing version or create a new version. The system automatically creates the new version with the next free number.

If you have already made extensive Customizing settings for the form scenario and want to create a new version based on these settings, you should copy this form scenario version.

End of the note.

To define a form scenario of type Adobe or FPM forms, perform the following activities:

Create the form scenario with a name and a description.
Enter a name for the package.
Select the form type Adobe Form or FPM Form.
For Adobe forms only: Enter a name for the ISR scenario.
For Adobe forms only: Enter a name for the form. If you select Suggest Names, the system generates the name using the format Z_ISR_HRARS_<Form scenario>. If you assign the name yourself, make sure that it is within the customer namespace. If you have entered both the ISR scenario name and the form name, the system opens a dialog box where you confirm the creation of the form scenario. You can confirm whether to create the form and the interface with the interface name Z_ISR_IF_<Form Scenario>.
Specify the backend service.
On the Change Form Scenario screen, make the following entries:
1. Enter a form scenario group for the authorization check.
2. Enter an anchor number for storing the form in the digital personnel file after running the process.
The system displays the administration information for the form scenario.
For Adobe forms only: When you save the form scenario, the system automatically generates the ISR scenario.

To define a form scenario based on roadmap forms, perform the following steps:

Create the form scenario with a name and a description.
Enter a name for the package.
Select the form type Roadmap Form.

Note
The other fields like such as ISR Scenario, Form, and Back-End Services are disabled.

End of the note.
On the Change Form Scenario screen, make the following entries:
1. Enter an infotype version to determine the country relevance of the process.
2. Enter a form scenario group for the authorization check.
The system displays the administration information for the form scenario.
Save the form scenario.