SAP ABAP Data Element P01P_MJMAB (Is Annual Report Required Despite Existing Deregistration?)
Hierarchy
☛
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR
⤷ PY-DE-PS (Application Component) Public Sector
⤷ P01O_ZV (Package) SP Notification Program for Public Sector Germany
⤷ PY-DE-PS (Application Component) Public Sector
⤷ P01O_ZV (Package) SP Notification Program for Public Sector Germany
Basic Data
Data Element | P01P_MJMAB |
Short Description | Is Annual Report Required Despite Existing Deregistration? |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | AnNotDereg |
Medium | 15 | An.Not., Dereg. |
Long | 20 | An.Not.Despite Dereg |
Heading | 55 | Annual Notif. Required Despite Existing Deregistration? |
Documentation
Definition
Employees who leave during the year are deregistered from their SPI. In addition to this deregistration, the remunerations liable to SP contributions for which payroll has already been run are reported for the employee in the form of periods (record type 60).
Although they already have the periods, some SPIs want to again receive the periods for the cases that have already been deregistered when the general annual notification is created for all employees who are still active.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20060208 |
SAP Release Created in | 600 |