Modern enterprises rarely run on a single monolithic system. Instead, they carry decades of legacy—from proprietary attendance systems to mainframe payroll sub-engines, and custom-built SAP add-ons tailored for industry-specific processes.
Many organizations running SAP ECC or S/4HANA today still depend on:
The challenge? These systems weren’t designed to talk to SAP. But now, they must.
And when SAP-to-SAP or SAP-to-legacy integration is required—with minimal middleware, full control, and compliance—point-to-point becomes the smartest approach.
Legacy Time
Old HRMS
SAP ECC FI
External HR Portal
Oracle DB
CSV
Excel
RFC
JSON
Flat File / DB View
File → Infotype 2011
Excel → Z-table → Infotypes
Z report → BAPI_ACC_DOCUMENT_POST
RESTful → SAP Gateway
Shared staging → SAP Job
Z Parser
ALSM_EXCEL_TO_INTERNAL_TABLE
Remote-enabled FM
JSON Handler Class
JDBC or File Ingestion
Payroll is the single most critical and risk-sensitive area in any SAP deployment. Integrating third-party systems into your payroll processes—without losing control of retroactivity, wage type generation, and deduction accuracy—requires a level of precision that only SAP-native point-to-point integrations can offer.
We dive into Infotype structures, ABAP interface designs, compliance considerations, and how to build integrations aligned with your payroll control record lifecycle.
At its core, point-to-point integration is the direct, tightly coupled connection between SAP and a third-party system, bypassing generic middleware tools. This method:
1. Reduces latency
2. Improves customization
3. Simplifies error handling
4. Aligns closely with payroll and compliance needs
Rather than sending data into a black box middleware, you're in full control—writing ABAP logic that knows exactly which Info type, PA subtype, or Wage Type to manipulate.
1. Data Extraction: Use ABAP programs or LSMW tools to pull employee master data, time punches, deduction records, etc. Accessed from Infotypes like 0002, 0167, 0378, 2010, 2011
2. Transformation: ABAP logic maps SAP internal formats to the vendor’s schema (e.g., Fidelity fixed-width layout, Alight’s ANSI X12)
3. File Generation & Encryption: Generated file stored on the SAP application server or NFS path PGP encryption applied if needed
4. Secure Transmission: Transferred via SFTP using command-line tools or SAP’s own connectivity add-ons
5. Audit Logging: All activity logged via custom Z-tables or application logs (SLG1)
1. Data Extraction: Use ABAP programs or LSMW tools to pull employee master data, time punches, deduction records, etc. Accessed from Infotypes like 0002, 0167, 0378, 2010, 2011
2. TransformField Mapping Tables (V_T77SFEC_BIBF): Defines EC → Infotype field relationships
Transformation Templates: Handle conversion logic (e.g., map EC ‘grade’ to SAP ‘job group’)
Filters: Set by country, employment type, event reason
Switches: To allow client-specific logic branching ation: ABAP logic maps SAP internal formats to the vendor’s schema (e.g., Fidelity fixed-width layout, Alight’s ANSI X12)
3. File Generation & Encryption: Generated file stored on the SAP application server or NFS path PGP encryption applied if needed
4. Secure Transmission: Transferred via SFTP using command-line tools or SAP’s own connectivity add-ons
5. Audit Logging: All activity logged via custom Z-tables or application logs (SLG1)
