Form Scenario

The form scenario provides the basis for a form-based process such as transfer.

This process includes several roles that are integrated using forms, and modifies the HR master data.

A form scenario comprises one form, and, for Adobe form, is assigned to one ISR scenario. You can use Adobe forms, which you create using Adobe LifeCycle Designer, or FPM or mass forms, which you create using the Floorplan Manager (FPM) Component Configuration Editor, or roadmap forms, which are reused form PA-PAO solution. All versions of a form scenario must have the same form type.

The form scenario is used to configure the interactive form as follows:

It determines the form type: Adobe, FPM, roadmap, or mass.
It determines the basic set of form fields that can be changed in a process.
It configures the default values and input help for the form fields.
It defines which HR master data fields are relevant for an assigned process step, and which changes to the data are to be performed on the database.
It defines the use of attachments and links for additional information.

Form scenarios are version-dependent. Since processes can vary, it is important that you are able to adjust the corresponding form scenarios. To be able to provide different forms for process variants, you create versions. Each form scenario has at least one version, which you link with the relevant process.

You can define scenario steps if the form configuration is not to be processed as a whole at the runtime of the process; in other words, when different parts of the form configuration are relevant depending on the process step involved.

You configure the form scenario in Customizing forHR Administrative Services under Start of the navigation path Configuration of Forms/Processes Next navigation step Design Time for Processes and Forms End of the navigation path .

For Adobe forms only: To use a form scenario in a process, you must also use the corresponding ISR scenario in parallel. The form scenario and the linked ISR scenario must have exactly the same version number. Form scenarios are synchronized with ISR scenarios. When you create a form scenario, you are asked to create the corresponding ISR scenario at the same time. When the form scenario is later saved, the ISR scenario is also updated and saved. You assign the ISR scenario to the form scenario in Customizing for HR Administrative Services by choosing Configuration of Start of the navigation path Forms/Processes Next navigation step Design Time for Processes and Forms. End of the navigation path .

Form scenarios are required for the start configuration of processes and must therefore be linked with a process. A process can be assigned several form scenarios. You make the assignment in Customizing for HR Administrative Services under Start of the navigation path Configuration of Forms/Processes Next navigation step Design Time for Processes and Forms End of the navigation path .

For roadmap forms only: A new country-specific section is available for the roadmap forms only. You can maintain the country-specific infotype version in this section. The anchor number and ISR scenario fields are disabled for roadmap forms.

Note Note

Only one roadmap form scenario can be assigned to a roadmap process.

End of the note.