HCM Program Custom development Interface

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

Short answer: 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.

Estimated effort
M · 8–12 working days
System
ECC and S/4HANA
Tables
7
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

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.

Who uses it? HR information systems, learning and development teams, IT help desk and integration teams.

Closest standard alternatives

  • PU12 Connection to Third-Party Payroll (Interface Toolbox). The interface toolbox produces file-based exports; manager determination and per-target mapping need extra development.
  • PA20 Display HR Master Data. Displays employee data one by one; no bulk transfer.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
PA0000HR Master Record: Infotype 0000 (Actions)Employment status and actionsReadECC + S/4
PA0001HR Master Record: Infotype 0001 (Organizational Assignment)Org unit, position, cost center, company codeReadECC + S/4
PA0002HR Master Record: Infotype 0002 (Personal Data)First and last nameReadECC + S/4
PA0105HR Master Record: Infotype 0105 (Communications)Email and SAP userReadECC + S/4
HRP1000Infotype 1000 (Object) Database TableOrg unit and position namesReadECC + S/4
HRP1001Infotype 1001 (Relationships) Database TableManager relationship and parent unitReadECC + S/4
T527XOrganizational UnitsOrg unit text (fallback)ReadECC + S/4

BAPIs and functions used

  • RH_GET_LEADERGet Manager of an Organizational Object. Finds the manager of the org unit
  • RH_STRUC_GETRead Organizational Structure for a Root Object. Finds the parent unit when a unit has no manager
  • HR_ENTRY_DATEDetermine Employee Entry Date. Finds the hire date
  • HR_READ_INFOTYPERead HR Infotype Records. Authorization-checked infotype read
  • SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends the transfer report as an Excel attachment

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_TARGETTarget system (mapping key)Single value—YesLMS
S_BUKRSCompany codeRange / multiplePA0001-BUKRSNo1000
S_PERSGEmployee groupRange / multiplePA0001-PERSGNo1
P_FULLFull transfer (all active employees)Checkbox—No—
P_TESTTest run (do not send)Checkbox—NoX
P_MAILTransfer report recipientSingle value—No[email protected]

Result list columns

#ColumnSource
1Personnel no.PA0001-PERNR
2NamePA0001-ENAME
3Org unitHRP1000-STEXT
4Cost centerPA0001-KOSTL
5EmailPA0105-USRID_LONG
6ManagerCalculated Result of RH_GET_LEADER, otherwise the parent unit's manager
7ChangeCalculated New, changed or inactive
8StatusCalculated Sent, skipped (reason) or error

Sample result list

Personnel no.NameOrg unitCost centerEmailManagerChangeStatus
00012045Ayşe ÖrnekQuality Assurance4110[email protected]Mert DemoChangedSent
00012102Deniz TestProduction Planning4200Ece ÖrnekNewSkipped: email missing
00011877Bora DemoSales5100[email protected]InactiveSent
00012110Selin ÖrnekMaintenance4310[email protected]Kaan TestNewSent
A view built with fictional sample data; not real system data.

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.

Performance notes

Read PA0000, PA0001, PA0002 and PA0105 with bulk SELECTs for the employee list; find the manager once per org unit and keep it in memory. Send only changes in the daily job; run the full transfer weekly or on demand.

Features

  • Runs as a background job The daily change transfer is scheduled as a background job.
  • Test mode (check without posting) Lists which records would be sent before sending.
  • Send the result by email The transfer report is emailed to the HR owner as an Excel attachment.
  • Line-by-line result and error log
  • Export to Excel

Authorization objects

  • P_ORGINRead authorization for infotypes 0000, 0001, 0002 and 0105
  • S_OC_SENDAuthorization 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.

Related reports

Let us build this program for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

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