SAP ABAP IMG Activity HRAS_HRASR00FSCNXI (Create Form Scenario for XI Message Type)
Hierarchy
☛ EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   ⤷ PA-AS (Application Component) HR Administrative Services
     ⤷ PAOC_ASR_PROCESS_MODELLING (Package) Modeling Processes
IMG Activity
ID HRAS_HRASR00FSCNXI Create Form Scenario for XI Message Type  
Transaction Code S_PEN_05000330   (empty) 
Created on 20050608    
Customizing Attributes HRAS_HRASR00FSCNXI   Create Form Scenario for XI Scenario 
Customizing Activity HRAS_HRASR00FSCNXI   Create Form Scenario for XI Scenario 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRAS_HRASR00FSCNXI    

Use

In this IMG activity, you create a form scenario for the XI message type.

Requirements

You used the Check Characteristics of XI Message Types IMG activity to determine which fields of the XI message type are available.

Standard settings

The SAP namespace comprises all form scenarios for which the key starts with an S. Therefore, the key for customer form scenarios must start with a different character.

Activities

  1. Create a form scenario.

    To do so, proceed as follows:

    1. Choose New Entries.
    2. Enter a four-digit alpha-numeric key and a name.
    3. Save your entries.
  2. Create a version for the form scenario.

    To do this, note the following information:

    • Form scenarios are version-dependent. This means that there is at least one version for each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated form scenarios. To be able to provide different forms for process variants, you create versions.
    • You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.
    • The ISR scenario that you link to the form scenario is also version-dependent. The form scenario and the ISR scenario must have the same version number. The system generates the version number of the ISR scenario. If you create a new version for a form scenario, you must therefore use this version number that the system generates.
    • If you have made extensive settings for a form scenario and want to create a new version based on these settings, we recommend that you use the Manage Form Scenarios IMG activity in HR Administrative Services Customizing by choosing Configuration of Forms/Processes -> Configuration of Forms.
  3. Define the form fields.

    In this step, you create all the fields that are relevant for the form scenario. To do this, note the following information:

    • You create both fields that appear on the form to display data and fields that do not appear on the interface but are used solely to transport data. If you no longer require a form field, delete it.
    • You must specify the type for each form field by entering a relevant data element. The form fields list data that is contained in the fields of an XI message. Therefore, the fields should have a compatible data type. To determine the data types of the fields of the XI message type, perform the Check Characteristics of XI Message Types IMG activity.
  4. Determine the attachment types that the form scenario supports.

    In this step, you assign the attachment types that you defined in the Form Scenario for XI Message Type: Define Attachment Types IMG activity to the form scenario.

  5. Create a form scenario step.

    You only need one form scenario step for a form scenario for an XI message type.

  6. Set the characteristics of the attachment types.

    In this step, you specify for the form scenario step you created that the user can view the attachments assigned. You perform this step for each attachment type that you assigned to the form scenario in step 4.

Example

You can use form scenario SXHR as an example. For more information, see Form Scenario for XI Message Type.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRAS_HRASR00FSCNXI 0 AEN0000011 HR Administrative Services 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
HRASR00FSCNXI C - View cluster SM34  
History
Last changed by/on SAP  20060905 
SAP Release Created in 600