Hierarchy
SAP_HRCMX (Software Component) Sub component SAP_HRCMX of SAP_HR⤷
PY-MX-PS (Application Component) Public Sector⤷
P32P1 (Package) Public Sector ISSSTE development for Mexico
IMG Activity
| ID | OHPSMXISSSTE17 | Maintain designation type |
| Transaction Code | S_L6B_69000599 | (empty) |
| Created on | 20030610 | |
| Customizing Attributes | OHPSMXISSSTE | ISSSTE contributions |
| Customizing Activity | OHPSMXISSSTE17 | Maintain designation type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHPSMXISSSTE17 |
Use
The system checks the values set in feature MXAPP to determine the naming type for each value in the 'work relationship' field of infotype 0001, Organisational Assignment.
This activity allows your company to use a field other than the 'work relationship' field, and assign the naming type to the new field to allow the system to identify the naming type.
You can use the following fields for the naming type: employee group, employee subgoup, personnel area, personnel subarea, payroll area, infotype 0001 work relationship (Organizational Assignment) and infotype 0016 contract type (contract elements).
You can use feature MXAPP to determine which of the fields listed above will be used to identify the naming type for ISSSTE. All results obtained by this characteristics are made up of two values, which correspond to a single field in the infotype.
The values of the feature should be in the form xx/yy, where 'xx' is the naming type used in the ISSSTE affiliation transactions file generated by report HMXUACTPBS, and 'yy' is the naming type used in the payroll data file generated by report HMXCIPDPBS.
In the value format of the feaure, 'yy' may be null, but 'xx' must contain a value. The symbol '/' must also always be present, even if 'yy' is null. For example, '30/' and '30/3' are valid values, while '30' and '/30' are not. All values are user-defined.
Requirements
Standard settings
Activities
- Execute this IMG activity.
- In the screen that appears, check the existing structure for feature MXAPP. The structure that appears is formed as follows:
Line Variable key C D Operations
000010 D ANSVH
000020 BA &MXAPP=10/1,
000030 CO &MXAPP=20/2,
000090 EV &MXAPP=30/3,
000090 ** &MXAPP=,
- Add more nodes to this feature if you need to include more employment contracts.
- Choose Feature -> Save to save any changes you have made to the feature.
- Generate the feature and contiune with the configuration.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
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 |
| PMKC | L - Logical transport object | PE00 | MXAPP 32 |
History
| Last changed by/on | SAP | 20030610 |
| SAP Release Created in | 470 |
