Kontakt

Ansicht
Dokumentation

HRAS_HRASR00FSCNPA - Process Form Scenario for Personnel Admin. Infotypes (Service SAP_PA)

HRAS_HRASR00FSCNPA - Process Form Scenario for Personnel Admin. Infotypes (Service SAP_PA)

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you configure the SAP_PA backend service for your form scenario. The SAP_PA backend service enables Personnel Administration infotypes to be created, changed, and deleted in a form scenario.

You have created a form scenario in the IMG activity Create Form Scenario and have assigned the SAP_PA service to it. You have assigned form fields to the service that you want to be processed by that service.

You carry out the following Customizing steps:

  • Define info objects
  • Define operations for info objects
  • Define assignment of form fields to info objects
  • Define default values for form fields
  • Activate value help for form fields

For detailed information about the individual steps, see the relevant sections.

The SAP_PA service is based on so-called info objects. An info object is generally understood as an infotype that can be restricted by the subtype. An additional restriction according to the object identification is also supported. An info object is therefore a combination of an infotype, subtype, and object identification, which can be displayed as follows: [infty, subty, objps]. Examples of valid info objects are:

Info object Name
[0002, space, space] Personal Data
[0006, space, space] Any Address
[0006, 1, space] Main Address
[0021, 1, space] Spouse
[0279, N001, 01] Individual values for product 01 (= "Retirement Scheme") of the pension fund N001

Activities

  1. Enter the name of the form scenario in the Determine Work Area: Entry dialog box.
  2. Select the version that you want to edit.
Note that the version 0 is output as initial here and therefore appears as a blank.
  1. Choose Operations in the dialog structure.
  2. Choose New Entries.
  3. Enter the info object you want to use, as a combination of the infotype, subtype, and object identification.
  4. Save your entries.

Note

When entering the infotype, use the value help to display a list of the available infotypes. Only the infotypes that are supported by the new infotype framework can be used. The new infotype framework requires the infotypes to be decoupled regarding business logic and UI. The majority of infotypes provided by SAP are already decoupled. If you want to use customer-specific infotypes, they also have to be decoupled. SAP provides a tool to support infotype decoupling. For more information, see the online documentation for HR Tools and choose Developing an Infotype in Personnel Administration. When you create new infotypes, you should create them using the new decoupled principle.

Also use the entry help to select the subtypes. Only the subtypes that are valid for the selected infotype are displayed.

If you also want to restrict the object identification, the valid values depend on the infotype and/or subtype. No value help can be provided as there is no uniform procedure for the object identification. For example, for infotype 0279, the valid values are stored in table T5NF1.

[0279, N001, 01]

Define the operations that you want to execute on the info objects. The SAP_PA service supports the following operations:

  • Create
  • Change
  • Change without delimiting
  • Delete

If you only want to use an info object to supply a form field with a value help or default value, do not enter an operation for the info object. This is the case, for example, if you use the Personal Data infotype (0002) to output the employee's name on the form. You always enter an operation if you want to modify the info object in the database.

The effect of the operation depends on the time constraint of the info object. The following time constraints are usually used:

  • Time constraint 1: Exactly one data record exists at all times.
  • Time constraint 2: Exactly one or no data record exists at all times.
  • Time constraint 3: Any number of data records exists at any point in time.

The time constraint is defined either for the infotype or the subtype.

Notes on determining the time constraint of an infotype

To determine the time constraint of an infotype, proceed as follows:

  • Select the infotypes in the IMG activity Infotypes or directly in the V_T582A view.
  • The Time Constraint field (ZEITB) contains either the time constraint of the infotype or the value "T". The value "T" means that the time constraint depends on the subtype.
  • You determine the time constraint of the subtype using the Time Constraint Table field (ZBTAB). It contains the name of a further table in which the time constraints of the subtypes are defined. You can read the time constraint of the subtype from this table.
  • If the infotype has subtypes but you do not restrict the subtype in the info object, the info object is treated as if it had time constraint 3. You then have to link a form field to the subtype field that contains the required infotype at runtime.

The operation may have different effects depending on the time constraint of the info object. For example, the Create operation always creates a new data record for an info object with time constraint 3, without modifying the existing records. By comparison, an existing data record is first delimited for an info object with time constraint 1 or 2.

Only the Create and Delete operations are supported for info objects with time constraint 3. Change and Change with delimiting are not possible.

You can only ever enter one operation for an info object. It is not possible to execute multiple operations on the same info object (for example, create and delete).

The next section describes how form fields are assigned to the info objects. The mandatory field EFFECTIVE_DATE has a special importance. If you assign form fields for the start and end date (BEGDA and ENDDA) to the info object, these values are used to process the data records. If you do not make the assignment, the value of the mandatory field EFFECTIVE_DATE is automatically used to process the data records. It is not necessary to explicitly assign EFFECTIVE_DATE to the info object, except for the Delete operation. For detailed information, see the online documentation for HR Administrative Services and choose Description of Operations.

Note about rules

If you want an operation to be executed only in particular circumstances, you assign a rule to it. You must have previously defined the rule in the form scenario. You must have assigned all form fields that you use in the rule to the SAP_PA service. The assigned operation is executed only if the rule - based on the values of the form fields used - has the value "true".

You are not permitted to use repeat fields (see below) in a rule as they can contain multiple values, whereas a rule can only ever be defined on one field value.

[0279, N001, 01]

If you want to execute the Create, Change, or Change Without Delimiting operations on the info objects, the data for the new data records has to be made available. This is achieved by assigning form fields to info objects. Access to the info objects is enabled by so-called screen structures. At least one screen structure exists for each infotype. There are usually multiple screen structures, in particular where the infotype is country-specific. In this case, there is a separate screen structure for each country version. Each screen structure contains all infotype fields that are relevant for the user interface. These can be input fields or output fields (for example, for corresponding texts or calculated fields).

When assigning the form fields to info objects, you have to decide on one of the possible country-specific screen structures of the infotype. This means that the entire form scenario is created for a particular country version. It is not possible to use screen structures for different country versions in the same form scenario at the same time. However, it is possible to use country-specific screen structures and international structures in one form scenario at the same time. If you do not use country-specific screen structures, only international ones, you define the entire form scenario as an international form scenario without any country-specific features. However, in this case, you lose the special country-specific functions, which is unacceptable in most cases.

Because each info object in a form scenario can be defined only once, you have to decide on one screen structure for each info object. You are not permitted to use the international screen structure and a country-specific screen structure simultaneously for the same info object.

Country versions and infotypes that do not have a screen structure cannot be used. The majority of infotypes and country versions provided by SAP have corresponding screen structures. To display the available screen structures, use the input help.

If you want to use customer-specific infotypes, they must also have screen structures, that is, the business logic and UI of the infotypes must be entirely decoupled, as in the SAP infotypes. SAP provides a tool to support infotype decoupling. For more information, see the online documentation for HR Tools and choose Developing an Infotype in Personnel Administration. When you create new infotypes, you should create them using the new decoupled principle.

There are two different types of screen structures: MAIN and LINE. You usually use screen structures of the MAIN type. You require LINE screen structures if you want to process repeat fields in the form scenario. To be output in the form, repeat fields have to be embedded in so-called "subforms".

In addition, you can display and edit infotype texts in the form. To do so, use the HCMT_BSP_PA_TEXT screen structure and link the form field to the TEXT field of the screen structure. Make sure when creating the form that you use a UI control that permits the display of texts of more than one line.

All screen structures contain the technical field OBJECT_KEY. This field is used for internal processing of the data records. Never use the OBJECT_KEY field in your form scenario.

Activities

  1. Choose Assignment of Fields in the dialog structure.
  2. Choose New Entries.
  3. Enter the name of the form field that you want to assign.
  4. Enter 1 as the index. If you want to assign the same form field more than once, enter successive increments of the value.
  5. Enter the info object as a combination of the infotype, subtype, and object identification to which you want to assign the form field.
  6. Specify the screen structure that you want to use.
  7. Enter the name of the field in the screen structure to which you want to assign the form field.
  8. Enter the data index (usually the value 1).
  9. Save your entries.

Note

If you only want to link a form field to an info object to fill it with a default value or assign it an input help, but do not want the value of the form field to be included in the operation, set the "Exclude from Operation" indicator (Op.Exclus.)

Note on the data index

You usually enter the value 1 as the data index. The following exceptions apply:

  • If you have set the Create operation for the info object and the info object has time constraint 3, it is possible to create more than one new data record. If you only want to create one new data record, use the value 1. If you want to create two data records, use the value 1 for the fields to be included in the first data record and 2for the fields that are to be included in the second data record. You cannot start with the value 2 or higher. If you want to create additional data records, raise the value of the data index by one for each new record.
If you have set the Delete operation for the info object and the info object has time constraint 3, it is possible to delete more than one data record. Use the value * (asterisk) as the data index for this purpose. The asterisk means that all data records in the relevant time interval are deleted. For detailed information, see the online documentation for HR Administrative Servicesand choose Description of Operations, in the section "Delete operation".
[0279, N001, 01]

The SAP_PA service can be used to fill form fields with default values.

[0279, N001, 01]

In the IMG activity Create Form Scenario, you must have set Default Value of Specified Backend Service as the default value type for the form field and the sequence number of the SAP_PA service. If these prerequisites have been met, you define in this step how the SAP_PA service is to determine the default values. The following types are available:

  • Value for Effective Date
You should use this type if the form field is an input field and you want the value that "currently" exists on the database to be entered in the field as a default. The user can then retain the value or overwrite it. You will usually have linked the form field to an info object for which you have set the Change operation or Change without delimiting. That is, you assume that data already exists on the database that is to be changed through the editing of the form. The mandatory field Effective Date (EFFECTIVE_DATE) determines the date on which the change in data becomes effective. The existing value for this date is determined as a default value. If there is no data record on the database for the effective date, no default value is determined for the form field.
  • Value for Day Before Effective Date
You should use this type if the form field is a display-only field that is to display the previously existing value on the database. You will usually have defined another form field as an input field for users to enter the new or changed value. For example, in a process to change an employee's organizational data (including the position), there may be a display field that outputs the old position and an additional input field for entering the new position. The change is to take place as of the effective date. In this case, you would choose the Value for Day Before Effective Date type for the display field. For the field in which the new position is input, you would choose the Value for Effective Date type. This means that the existing position as at the effective date is specified in the field as the default value for the new position. In the case of both types, if there is no data record in the database on the day previous to the effective date (= EFFECTIVE_DATE - 1), no default value is determined for the form field.
  • Default Value of Business Logic
You should use this type if the form field is assigned to an info object for which you have set the Change operation. In this case, there is usually no data record in the database that could be used as a default value. If you use the Default Value of Business Logic type, the initial computation logic of the infotype is called and determines default values for the creation of a new data record. If the logic cannot determine a default value, none is entered in the form field.

Activities

  1. Choose Assignment of Fields in the dialog structure.
  2. Select the form field.
  3. Select the required type from the dropdown list for the default value.
  4. Save your entries.
[0279, N001, 01]

Form fields can be filled with value help. In many cases, the value help can be made available by the SAP_PA service.

[0279, N001, 01]

If you want to provide value helps through the SAP_PA service, you have to have set Value Help of Specified Backend Service as the value help type for the form field and the sequence number of the SAP_PA service. You do this in the IMG activity Create Form Scenario. Alternatively, you may have set Value Help for All Linked Backend Services as the value help type.

The SAP_PA service cannot provide value helps for all fields. To gain an overview of the fields for which value helps are available, you can use the tool for testing decoupled infotypes. To do so:

  • Start the transaction PUIT_UI.
  • Enter a personnel number.
  • Enter an infotype and, if required, a subtype.
  • Choose Execute.
An overview of all data records for the personnel number and the specified infotype appears.
  • To display the name of the screen structure, choose Technical Information. The following information about the available value help applies only to the displayed screen structure.
  • Choose Edit -> Create Data Record.
  • In the dialog box that appears, enter any values or leave the fields blank.
  • Choose Continue.
A dialog box appears that displays all fields of the screen structure. The Value Help column displays whether a value help is available for the field. In Customizing for the SAP_PA service, you can only activate the value help for fields that have a value help.

Activities

  1. Choose Assignment of Fields in the dialog structure.
  2. Select the form field.
  3. Select the value help from the dropdown list.
  4. Save your entries.

Note about mandatory form fields

The SAP_PA service has a range of mandatory fields, which are listed below. These fields must be created in each form scenario used by the SAP_PA service with the name exactly as specified and with the data element specified. (You do this in the IMG activity Create Form Scenario.) They also have to be assigned to the SAP_PA service in the same activity.

However, in this IMG activity for configuring the SAP_PA service, the fields do not necessarily have to be redefined or reassigned. The SAP_PA service assumes that the fields exist and knows how to handle them.

Mandatory fields:

Field Name Name Data Element
PERNR Personnel Number PERNR_D
EFFECTIVE_DATE Effective Date ASR_EFFECTIVE_DATE
MASSN Action MASSN
MASSG Reason for Action MASSG
CENTRAL_PERSON Central Person OBJEKTID

Central Person

Central Person

Central Person

Central Person






Addresses (Business Address Services)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 23709 Date: 20240523 Time: 191501     sap01-206 ( 412 ms )