Employee to Business Partner and Vendor Link Check Report (S/4HANA Readiness)
Short answer: A report that checks for every employee the business partner link required in S/4HANA (central person and business partner relationship, personnel number identification) and the vendor record used for expense payments. Employees with a missing link, a link to several business partners, or a vendor record still open after leaving are listed.
- Estimated effort
- M · 4–7 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
In S/4HANA every employee needs a business partner, and synchronization errors surface only during expenses, purchasing approvals or workflows. PA20 shows one employee and BP shows one business partner; no standard list checks the link between personnel number, central person, business partner and vendor in bulk.
Who uses it? S/4HANA conversion teams, HR and finance master data owners, travel and expense management teams.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| PA0001HR Master Record: Infotype 0001 (Organizational Assignment) | Employees valid on the key date, company code and personnel area (driving table) | — | ECC + S/4 |
| PA0000HR Master Record: Infotype 0000 (Actions) | Employment status and leaving action | PA0000-PERNR = PA0001-PERNR | ECC + S/4 |
| HRP1001Infotype 1001 (Relationships) Database Table | Person ↔ central person and central person ↔ business partner relationships | HRP1001-OTYPE = 'CP' AND HRP1001-SCLAS = 'P' AND HRP1001-SOBID = PA0001-PERNR | ECC + S/4 |
| BUT000Business Partner: General Data | Existence, grouping and central block of the business partner | BUT000-PARTNER = HRP1001-SOBID (ilişki 207) | ECC + S/4 |
| BUT0IDBusiness Partner ID Numbers | Personnel number identification on the business partner | BUT0ID-PARTNER = BUT000-PARTNER AND BUT0ID-IDNUMBER = PA0001-PERNR | ECC + S/4 |
| LFB1Vendor Master (Company Code) | Vendor linked to the employee for expense payments, with payment block | LFB1-PERNR = PA0001-PERNR AND LFB1-BUKRS = PA0001-BUKRS | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_KEYDT | Key date | Single value | SY-DATUM | Yes | 17.11.2026 |
| S_BUKRS | Company code | Range / multiple | PA0001-BUKRS | Yes | 1000 |
| S_WERKS | Personnel area | Range / multiple | PA0001-WERKS | No | 1000 |
| S_PERSG | Employee group | Range / multiple | PA0001-PERSG | No | 1 |
| P_VENDOR | Vendor record required for active employees | Checkbox | — | No | X |
| P_LEAVER | Also check leavers of the last 12 months | Checkbox | — | No | X |
| P_ERRONL | Show findings only | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Personnel no. | PA0001-PERNR |
| 2 | Name | PA0001-ENAME |
| 3 | Company code | PA0001-BUKRS |
| 4 | Personnel area | PA0001-WERKS |
| 5 | Employment status | PA0000-STAT2 |
| 6 | Central person | HRP1001-OBJID |
| 7 | Business partner | BUT000-PARTNER |
| 8 | Number of BPs | Calculated Number of business partners linked to the central person with relationship 207 |
| 9 | Personnel no. ID | BUT0ID-IDNUMBER |
| 10 | BP block | BUT000-XBLCK |
| 11 | Vendor | LFB1-LIFNR |
| 12 | Vendor payment block | LFB1-SPERR |
| 13 | Finding | Calculated By the rules: no BP, several BPs, no ID, blocked, no vendor, leaver's vendor open |
| 14 | Recommended action | Calculated Fixed recommendation text per finding |
Sample output
| Personnel no. | Name | Company code | Personnel area | Employment status | Central person | Business partner | Number of BPs | Personnel no. ID | BP block | Vendor | Vendor payment block | Finding | Recommended action |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 00012045 | Selin Karamanlı | 1000 | 1000 | 3 | 60012045 | 0 | Active employee has no business partner | Re-run employee synchronization for this person | |||||
| 00012311 | Burak Tekinalp | 1000 | 1100 | 3 | 60012311 | 9000004711 | 2 | 00012311 | More than one business partner | Archive the extra business partner and keep a single relationship | |||
| 00009874 | Hakan Sarıgöl | 1000 | 1000 | 0 | 60009874 | 9000003120 | 1 | 00009874 | E9874 | Leaver's vendor is not blocked | Set a payment block on the vendor if no open items remain |
How does the report work?
- Employees valid on the key date for the selected company code and personnel area, with their employment status (STAT2), are read from PA0000 and PA0001.
- The person’s central person link (P ↔ CP, relationship 209) and the central person’s business partner link (CP ↔ BP, relationship 207) are read from HRP1001.
- The existence and central block of the business partner are checked in BUT000, and the personnel number identification (the ID type written by employee synchronization) in BUT0ID.
- The vendor record for expense payments is found through LFB1-PERNR, with its payment block (SPERR).
- Rules are applied: no business partner for an active employee, more than one business partner, no personnel number identification on the business partner, business partner blocked, vendor missing although required, vendor of a leaver not blocked.
- A recommended action (re-run synchronization, block the vendor, etc.) is given as text for each finding.
Performance notes
Read HRP1001 in bulk by plan version, object type and relationship code; read BUT000, BUT0ID and LFB1 with FOR ALL ENTRIES on the keys found. The report runs for the whole company in minutes and can be re-run after every mock conversion.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the personnel number opens PA20; double-clicking the business partner opens BP.
- Export to Excel
- Runs as a background job
Authorization objects
- P_ORGINRead authorization for infotypes 0000 and 0001
- PLOGAuthorization to read central person relationships
- B_BUPA_GRPDisplay authorization by business partner grouping
- F_LFA1_BUKVendor display authorization by company code
Frequently asked questions
Does the report run in ECC or S/4HANA?
Both. In ECC it helps plan which employees need a business partner and which vendors need clean-up before the conversion; in S/4HANA it regularly checks that synchronization runs completely.
Are the relationship codes and the ID type the same in every system?
The report uses SAP's standard relationship codes (209 and 207) and the ID type of employee synchronization by default. The system's settings are checked at installation; if they differ, they can be changed on the selection screen.
Does the report create missing business partners itself?
No. The report only reads and recommends. Missing links are fixed by re-running the standard employee synchronization, so master data ownership stays in the standard process.
Related reports
Employees Missing Cost Center or Organizational Assignment Report
A custom ALV check report that finds, before payroll runs, active employees with an empty or invalid cost center, assignments left on the default …
Employee Master Data Consistency Check Before Payroll Report
A custom ALV report that shows, before the payroll run, missing mandatory infotypes, gaps in the organizational assignment, overlapping actions on the …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.