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_HRASR00FSCNPA | Process Form Scenario for Personnel Admin. Infotypes (Service SAP_PA) |
| Transaction Code | S_AEN_10000683 | (empty) |
| Created on | 20050317 | |
| Customizing Attributes | HRAS_HRASR00FSCNPA | Process Form Scenario for Personnel Admin. Infotypes (Service SAP_PA) |
| Customizing Activity | HRAS_HRASR00FSCNPA | Process Form Scenario for Personnel Admin. Infotypes (Service SAP_PA) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRAS_HRASR00FSCNPA |
Use
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.
Requirements
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.
Activities
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.
Define info objects
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
- Enter the name of the form scenario in the Determine Work Area: Entry dialog box.
- Select the version that you want to edit.
Note that the version 0 is output as initial here and therefore appears as a blank.
- Choose Operations in the dialog structure.
- Choose New Entries.
- Enter the info object you want to use, as a combination of the infotype, subtype, and object identification.
- 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.
Define operations for info objects
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.
Define assignment of form fields to info objects
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 scre
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory 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_HRASR00FSCNPA | 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 |
| HRASR00FSCNPA | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20050616 |
| SAP Release Created in | 600 |
