SAP ABAP IMG Activity HRAS_HRASR00FSCNPT (Process Form Scenario for Time Management Infotypes (Service SAP_PT))

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_HRASR00FSCNPT	Process Form Scenario for Time Management Infotypes (Service SAP_PT)
Transaction Code	S_AEN_10000684	(empty)
Created on	20050317
Customizing Attributes	HRAS_HRASR00FSCNPT	Process Form Scenario for Time Management Infotypes (Service SAP_PT)
Customizing Activity	HRAS_HRASR00FSCNPT	Process Form Scenario for Time Management Infotypes (Service SAP_PT)

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	HRAS_HRASR00FSCNPT

Use

In this IMG activity, you configure the SAP_PT backend service for your form scenario. The SAP_PT backend service enables Time Management infotypes to be created, changed, and deleted.

Requirements

You have created a form scenario in the IMG activity Create Form Scenario and have assigned the SAP_PT 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

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

Define info objects

The SAP_PT 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 on the object identification level is supported, but is not usually required. 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:

[2001, space, space]    Any Absence

[2001, 0190, space]    Educational Leave

[2007, 01, space]    Approved Overtime

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.

3. Choose Operations in the dialog structure.
4. Choose New Entries.
5. Enter the info objects you want to use as a combination of the infotype, subtype, and object identification.
6. 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 Time Management infotype framework (BLP) can be used. It is not possible (and usually not necessary) to develop customer-specific infotypes in this framework.

Also use the entry help to select the subtypes.

Define operations for info objects

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

• Create
• Change (restricted)
• Delete

If you only want to use an info object to supply a form field with a default value, do not enter an operation for the info object. You enter an operation if you want to modify the info object on the database (this is usually the case).

Whereas Personnel Administration infotypes can have a time constraint of 1, 2, or 3, Time Management infotypes have a separate, complex time constraint logic. The Time Management infotype framework ensures that this is taken into account when infotypes are created and changed. Put simply, the complex time constraint logic is most comparable to time constraint 3. However, there are also situations in which an infotype's behavior is similar to time constraint 2.

Create operation

You use the Create operation when you want to create a new data record.

If you explicitly link the start and end date (BEGDA and ENDDA) of the info object to form fields, the new data record is created with the same validity. If you do not link the start and end date, the data record is created with the validity of the mandatory fields EFFECTIVE_BEGDA and EFFECTIVE_ENDDA. In this case, EFFECTIVE_BEGDA and EFFECTIVE_ENDDA should be form fields and entered explicitly by the user, for example. If EFFECTIVE_BEGDA or EFFECTIVE_ENDDA is initial, the value from EFFECTIVE_DATE is used instead.

Change operation

You should use the Change operation only with the utmost caution. For Personnel Administration infotypes (SAP_PA service), it is not intended for use with infotypes with time constraint 3. Because Time Management infotypes usually also have the nature of time constraint 3, you should not use the operation for them either. You should use the Change operation only if you are certain that the Time Management infotype behaves in a similar manner to time constraint 1 or 2.

Delete operation

You use the Delete operation to delete data records. It deletes all data records that are in the interval [EFFECTIVE_BEGDA - EFFECTIVE_ENDDA] or are valid on at least one day in the interval. If EFFECTIVE_BEGDA or EFFECTIVE_ENDDA is initial, the date specified in EFFECTIVE_DATE is used instead. If you want to delete data records in another period, you specify the period explicitly by linking form fields to the start and end date of the info object.

Note that you always have to link at least one field to the info object for the operation to be executed on the info object. You are advised to link the PERNR field for the Delete operation.

As a result of the complex time constraint logic of Time Management infotypes, it can be assumed that more than one data record exists in the specified deletion interval. The Delete operation is therefore usually applied to a set of data records. For this reason, you must enter an asterisk (*) for the data index when linking the form fields. This indicates that there are multiple data records, as opposed to just one.

Note about assignment of 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_PT service. The assigned operation is executed only if the rule - based on the values of the form fields used - has the value "true."

Define assignment of form fields to info objects

If you want to execute the Create or Change 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. The info objects are then accessed via the Pnnnn infotype structures, where nnnn stands for the four-digit number of the infotype. To display the available infotype structures, use the input help.

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. Enter the infotype structure.
7. Enter the name of the field in the infotype 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, 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, 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 2 for 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, 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 more information, see the "Delete operation" section of the documentation.

Define default values for form fields

The SAP_PT service can be used to fill form fields with default values. However, you should restrict your use of this option. As Time Management infotypes usually have the character of time constraint 3, several data records can exist simultaneously in the database for a key date or effective date. It is then unclear from which data record the default value is read. You should only use default values using the service SAP_PT if you are sure that only one data record exists for the point in time i

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_HRASR00FSCNPT	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
HRASR00FSCNPT	C - View cluster	SM34		☐	☐

History

Last changed by/on	SAP	20050616
SAP Release Created in	600