Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-PS (Application Component) Public Sector⤷
P01O (Package) HR Germany: Public Sector
IMG Activity
| ID | PAY_DE_PS_FZ06 | Create Model Action (Child) for Public Sector |
| Transaction Code | S_PH0_48000313 | (empty) |
| Created on | 20000122 | |
| Customizing Attributes | PAY_DE_PS_2_2_204 | Attributes Public Sector DE: Optional Activity, Uncritical, ProcMod. No.204 |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PAY_DE_PS_FZ06 |
You can take advantage of the similarity of the data for the child, the child allowance, the family-related bonus, and the cost-of-living allowance and reduce your maintenance effort significantly by using an action that you adjust to your requirements.
Example
An employee has had a child. You want to create the data for this child in the system with all information about the child allowance and the child-dependent elements in the family-related bonus and the cost-of-living allowance. To do this, you have to create data records in the following infotypes.
- Family/related person (0021), subtype child
- Child allowance (0118)
- Family-related bonuses (0595), subtype Child element and child bonuses
Possible process of the example action
If the example measure is called Create child (child child allowance and cost-of-living allowance), the process would be carried out in the system as follows:
- You call transaction PA40 (personnel actions) and select the action Create child child, child allowance and cost-of-living allowance.
As the start date, you select the child's date of birth.
- Once you have saved the infotype Actions (0000), the system automatically navigates to the infotype Child of the infotype Family/related person (0021).
You enter the name of the child, his or her date of birth, and the other data.
- Once you have saved the infotype Family/related person, the system automatically navigates to the infotype Child allowance (0118).
- Here, the system adopts the child number and the validity period.
- If the automatic default it active, the system proposes the period, entitlement and reason.
- You can adopt the values without carrying out any further maintenance or adjust them if required.
- Once you have saved the infotype Child allowance, the system automatically navigates to the subtype Child element and child bonuses of the infotype Family-related bonuses (0595).
- Again, the system adopts the child number and the validity period.
- If the automatic default it active, the system proposes the period, the entitlement to the child element, the reason for the entitlement, and the entitlement to the child increase amount.
- You can adopt the values without carrying out any further maintenance or adjust them if required.
- Once you have saved the infotype Family-related bonuses, this action is complete.
Requirements
In the previous process steps, you activated the automatic default for the infotypes Child allowance (0118) and Family-related bonuses (0595), and you have correspondingly adjusted them to your requirements. If necessary, in the process step Store Default Values, you also maintained the default values for the infotype Family-related bonuses (0595) that are not covered by the automatic default.
Further notes
You can use transaction PA40 (personnel actions) to select an action similar to the above action. Only the subtype Child of the infotype Family/related person (0021) belongs to the infogroup of this action. The two dynamic actions that make it possible to navigate from the infotype Family/related person to the infotype Child allowance (0118), and from the infotype Child allowance to the infotype Family-related bonuses (0595), are only active in the example action. If, for example, you maintain these infotypes by calling them directly, the system does not navigate to the dynamic actions after you save.
Activities
The Implementation Guide for personnel administration contains a description of the set up procedure for actions under Adjust Workflows -> Actions. There, you set up the dynamic actions in the process step Dynamic Actions. To ensure that the system only executes the dynamic actions when the person responsible is in the example action, you have to insert a corresponding condition into the dynamic action (for example, action = P and the variable function part = PSPAR-MASSN=ZZ, if the key of the example action is ZZ.)
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20000122 |
| SAP Release Created in | 46C |
