Hierarchy
DMIS_CNT (Software Component) DMIS_CNT 2011_1⤷
CA-EUR (Application Component) European Monetary Union: Euro⤷
CNV_TDMS_HCM_620_A (Package) TDMS4HMC - Release 620 and higher releases
IMG Activity
| ID | TDHC0_DEFINE_SELID1 | Assign Objects to a Selection ID |
| Transaction Code | S_SR9_69000017 | (empty) |
| Created on | 20120716 | |
| Customizing Attributes | TDHC0_DEFINE_SELID1 | Assign Objects to a Selection ID |
| Customizing Activity | TDHC0_DEFINE_SELID1 | Assign Objects to a Selection ID |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | TDHC0_DEFINE_SELID1 |
Short text
TDMS4HCM: UI for Object Selection
Purpose
You use this report to generate and view a list of SAP Human Capital Management (SAP HCM) objects based on business criteria you specify. When you choose the Create Selection pushbutton, the report automatically generates a selection ID, which is used to identify the list of HCM objects.
The primary purpose of the thus obtained list of objects is to transfer these objects to some receiver system from the system in which the selection was done.
You can also modify the generated list for purposes of data transfer by manually removing HCM objects from the list.
For more information about selecting objects for transfer, see Transfer Selection Criteria.
Integration
The selection ID is used in the activity Transfer Selection Criteria. Thus the user can transfer all objects stored under the specified selection ID from the sender system to the receiver system.
Prerequisites
You have sufficient authorizations for this report.
You have sufficent authorizations to select the SAP ERP HCM objects based on your specified criteria.
For more information on authorizations, see the Features section below.
Features
Authorizations
The TDMS4HCM: Control of Selection of HCM Objects for Transfer authorization object controls the authorization to display criteria, modify criteria, and execute the selection using selection criteria.
When executing the selection, the TDMS4HCM: Control of AUTHORITY-CHECK granularity authorization object verifies the Read attributes of objects. Depending on the level of authorization, the authorization object carries out the same checks as it carries out in the logical databases for Personnel Administration (PA) and Personnel Development (PD).
If time and payroll cluster data are used in the selection criteria, the Read authorization for this cluster data is verified.
Note
You can circumvent the authorization for accessing object attributes by assigning '*' to the TDMS4HCM01 authorization object . This feature may be useful for an HCM administrator who may have very general authorizations to read HCM data. Circumventing authorization checks to access object attributes increases performance.
Selection
You can perform the following actions to work on a selection ID:
- Create a new selection ID.
- Copy an existing selection ID.
- This action only copies the selection criteria and not the list of objects.
- Change the descriptive text of a selection ID.
- Define the selection criteria.
- Check the consistency of the selection criteria.
- Download the selection criteria to a .xml file.
- Upload selection criteria from a .xml file.
- Save changes to the selection criteria.
Note: Changing the selection criteria deletes any existing results.
- View references of the selection ID by other selections.
- Delete a selection ID.
This action deletes the selection criteria and the list of objects generated for the criteria if the selection ID is not referenced by any other selection ID.
- View administrative details for the selection ID.
The details include the user, time, and date information for the creation, modification, and execution of selection IDs. Details regarding any manual changes to the list of objects are also displayed.
You can perform the following actions to process a selection ID to obtain a list of objects:
- Execute the selection.
The result is a list of objects and the relationships between them.
- Execute the selection in the background.
The result is a list of object and the relationships between them.
- View the list of objects in form of a simple list.
- View the list of objects in form of a tree-structure.
- View the relationships from or to selected objects of these lists.
- View infotype-attributes of selected objects.
You can only view attributes of objects, if you are authorized to read the requested infotype data for the requested objects. The TDMS4HCM: Control o AUTHORITY-CHECK granularity authorization object is used to verify user authorizations.
- Delete selected objects from these lists.
- Save the deletion of selected objects from these lists.
- View the execution log for the selection.
You can perform the following locking and unlocking actions for a selection ID:
- Lock a selection ID to prevent further changes. This includes changes to the selection criteria, execution of the selection, and changes to the result. By thus locking a selection ID, the user can prevent accidental changes to a selection ID while its result list may be used by a user in some other application.
- Unlock a selection ID. This again allows changing the selection criteria, executing the selection and manually changing the result list.
When specifying selection criteria, enter the following information:
- Start date for selection. This field is mandatory. However, it is possible to specify system low-date (01.01.1800).
- Various steps for the selection
In the very first step, you must specify at least a selection ID or some object types and an explicitly-selected object IDs.
The selection criteria specified in a particular step is retained in the next step. You can then make further selection restrictions in the new step.
Hence, each step adds to the selection criteria in the previous steps.
The exception to the above rule is the case where you only specify restrictions in a particular step without specifying a selection ID, an object type, an object ID, an evaluation path, or a relationship ID.
Such a step is interpreted as a filter for the data of all previous steps.
For each step, you can enter the following criteria:
- A list of different selection IDs
The objects assigned to the selection IDs that you entered in this field are automatically included in the current selection ID. If you specify some restriction in this step, only those objects are included that fulfill the specified restrictions.
- Object types and explicitly selected object IDs
- If you do not specify a selection ID or an object type and object ID, the list of objects from the earlier steps are automatically used as input.
- A list of evaluation paths. These evaluation paths are applied to all the objects serving as input. This can be the objects of another selection ID or explicitly specified object types and IDs. If neither was specified, then automatically the list of objects of the earlier steps are used as input. A particular evaluation paths is only applied to those types of objects for which it makes sense based on its definition. Please note that specifying an evaluation path for a large number of objects or objects with many dependent objects can significantly reduce performance!
- A list of relationship IDs can be specified. These relationship IDs are applied to all the objects obtained so far, in order to obtain additional objects. This is then iterated until no further objects are found.
- Restrictions can be specified for particular object types. The user specifies infotypes to be used. The user can then specify attributes of fields of the tables of these infotypes. Objects of that type must then fulfill these conditions.
- For objects of type 'P', it is also possible to specify restrictions based on time cluster and/or payroll cluster content. For the time cluster, the existence of time types in time cluster table ZES can be searched, and the existence of wage types in time cluster table ZL can be searched. For the payroll cluster, the existence of wage types in payroll cluster table RT can be searched. Please note that specifying cluster restrictions can significantly reduce performance!
- Restrictions can be specified for particular object types also in the form of limits. Depending on the limit type, different limits apply. For details on the different types of limits, see the documentation of Limit Type
- Restrictions can also be specified for relationship IDs. This is only possible for relationship IDs for which additional data exists. The user can then specify attributes for the fields of the table containing additional data for the specified relationship ID. If two objects are connected via relationships of the specified relationship ID, and if none of these relationships fulfill the specified conditions, then the two objects are deleted from the Selection ID.
- The user can specify object types that should not be part of the final result. Only the objects added in the current step are adjusted accordingly. If the object type 'CP' is specified as an object to be removed, then a special logic applies. Ordinarily, for all 'P' objects, the corresponding 'CP' objects are obtained as well. And for the thus determined 'CP' objects all 'P' objects are obtained. This can result in an increase of the number of 'CP' objects. However, if object type 'CP' is specified a
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | TDHC0_DEFINE_SELID1 | 0 | HLB0009110 | Cross-Application Components |
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 |
| CNV_HCM_PRESEL_SUB_N | T - Individual transaction object | CNV_HCM_PRESEL_SUB_N |
History
| Last changed by/on | SURANA | 20121227 |
| SAP Release Created in | 2011_1_700 |
