Hierarchy
⤷ PY-BE (Application Component) Belgium
⤷ P12C (Package) HR customizing: Belgium
IMG Activity
ID | OHABE_SB_010 | Select Employees for Social Balance Reporting |
Transaction Code | S_L7D_24002424 | (empty) |
Created on | 20100215 | |
Customizing Attributes | OHABE_SB_010 | Select Employees for Social Balance Reporting |
Customizing Activity | OHABE_SB_010 | Select Employees for Social Balance Reporting |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHABE_SB_010 |
Use
In this Customizing activity, you define the persons that are included in Social Balance Declaration reporting. You can define these persons by customizing the Employee selection for Social Balance (BSOBA) feature. The selection is based on whether a person has an employment contract, and the employee specification defined in the employee's Social Insurance B (0100) infotype record.
Requirements
Standard settings
Employees are selected for the Social Balance Declaration according to their BSOBA feature value. The following table illustrates how an employee's BSOBA feature value determines in what section of the declaration the corresponding data is reported:
BSOBA Sect 1 Sect 2 Sect 3 Sect 4 Sect 5 Sect 6
Directors - Staffing M yes yes - yes yes yes
White Collar Workers - Staffing B yes yes - yes yes yes
Blue Collar Workers - Staffing W yes yes - yes yes yes
Others - Staffing O yes yes - yes yes yes
Interim Workers - Externals E yes
Persons at Disposal - Externals D yes
Activities
You adapt the Employee Selection for Social Balance (BSOBA) feature to meet your company requirements. If you have defined company-specific codes for the employee specification, you must ensure that the feature uses these codes.
Example
If an employee has the value M, B, W, or O (BSOBA returned value), then the employee's data is collated in all declaration sections except section 3. If an employee has the value E or D, then the employee's data is collated in section 3. There is a further filtering of data within section 3 depending on the code. For example, for an employee with value E, the codes 150A, 151A, 152A, and so on are used. For an employee with value D, the codes 50B, 151B, 152B, and so on are used.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHABE_SB_010 | BE | Belgium |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHABE_SB_010 | 0 | HLA0008903 | Subsequent Activities |
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 | BSOBA | HR: Transport Customer Features |
History
Last changed by/on | SAP | 20100219 |
SAP Release Created in | 600 |