# Active Employee, Department and Manager Data Feed to External Systems (LMS, Portal, Help Desk)

> An interface that regularly sends active employees with org unit, position, manager, cost center and email to external systems such as the learning management system, the employee portal and the help desk. Each target system gets its own field mapping; only changes are sent and a transfer report is produced.

- Type: Program, Custom development, Interface
- Module: HCM
- Estimated effort: M (8–12 working days)
- Last updated: 2026-11-18
- URL: https://nekuhub.com/en/programs/active-employee-department-and-manager-data-feed-to-external-systems/


## Why is the standard not enough?

The standard system offers the interface toolbox (PU12) and ALE distribution for employee data, but they are designed for payroll files or SAP-to-SAP distribution. There is no lightweight feed that sends active employees with manager and department names, with the field names the target system expects and only with changes; hires and leavers reach external systems manually or late.

### Closest standard alternatives

- PU12: The interface toolbox produces file-based exports; manager determination and per-target mapping need extra development.
- PA20: Displays employee data one by one; no bulk transfer.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| PA0000 | Employment status and actions | Read | - | ECC + S/4 |
| PA0001 | Org unit, position, cost center, company code | Read | PA0001-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0002 | First and last name | Read | PA0002-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0105 | Email and SAP user | Read | PA0105-PERNR = PA0000-PERNR | ECC + S/4 |
| HRP1000 | Org unit and position names | Read | HRP1000-OBJID = PA0001-ORGEH | ECC + S/4 |
| HRP1001 | Manager relationship and parent unit | Read | HRP1001-OBJID = PA0001-ORGEH | ECC + S/4 |
| T527X | Org unit text (fallback) | Read | T527X-ORGEH = PA0001-ORGEH | ECC + S/4 |

## BAPIs and functions used

- RH_GET_LEADER: Finds the manager of the org unit
- RH_STRUC_GET: Finds the parent unit when a unit has no manager
- HR_ENTRY_DATE: Finds the hire date
- HR_READ_INFOTYPE: Authorization-checked infotype read
- SO_NEW_DOCUMENT_ATT_SEND_API1: Sends the transfer report as an Excel attachment

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_TARGET | Target system (mapping key) | Single value | - | Yes |
| S_BUKRS | Company code | Range / multiple | PA0001-BUKRS | No |
| S_PERSG | Employee group | Range / multiple | PA0001-PERSG | No |
| P_FULL | Full transfer (all active employees) | Checkbox | - | No |
| P_TEST | Test run (do not send) | Checkbox | - | No |
| P_MAIL | Transfer report recipient | Single value | - | No |

## Result list columns

| Column | Source |
|---|---|
| Personnel no. | PA0001-PERNR |
| Name | PA0001-ENAME |
| Org unit | HRP1000-STEXT |
| Cost center | PA0001-KOSTL |
| Email | PA0105-USRID_LONG |
| Manager | Calculated: Result of RH_GET_LEADER, otherwise the parent unit's manager |
| Change | Calculated: New, changed or inactive |
| Status | Calculated: Sent, skipped (reason) or error |

## How does the program work?

1. Selection: employees with active employment status (PA0000-STAT2 = 3) are selected; a leaver is sent once as an 'inactive' record in the first run after the leaving date. The hire date is found with HR_ENTRY_DATE.
2. Organization: org unit, position and cost center are read from PA0001, and unit and position names from HRP1000. The manager is found with RH_GET_LEADER; for units without a manager the manager of the next higher unit is taken (RH_STRUC_GET).
3. Communication: email and SAP user come from PA0105 (subtypes 0010 and 0001), and the name from PA0002.
4. Change detection: records changed after the last successful transfer (AEDTM on the infotypes) and org changes are selected; the full transfer option resends all active employees.
5. Mapping: the field mapping and format (CSV, JSON) for each target system are kept in a settings table; e.g. the learning system needs the manager's email, the help desk needs cost center and location. Data is sent through a REST service or as a file to SFTP.
6. Transfer report: sent, skipped (missing email, no manager found) and failed records are listed and emailed to the HR owner as an Excel attachment with SO_NEW_DOCUMENT_ATT_SEND_API1. The solution works with the same tables in on-premise HCM on S/4HANA and in ECC.

## Authorization objects

- P_ORGIN: Read authorization for infotypes 0000, 0001, 0002 and 0105
- S_OC_SEND: Authorization to email the transfer report

## Frequently asked questions

### How much personal data is shared?

Each target system receives only the fields allowed in its mapping table; for example, no ID or salary data is sent to the learning system. The field list is agreed with the data controller during installation.

### When does a leaver become inactive in the external system?

An 'inactive' record is sent in the first transfer after the leaving action is saved; with the daily job this takes at most one day.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=hcm-employee-master-outbound-interface
