# Employee to Business Partner and Vendor Link Check Report (S/4HANA Readiness)

> 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.

- Type: Report, Custom development, ALV report
- Module: HCM
- Estimated effort: M (4–7 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/employee-business-partner-and-vendor-link-check-s4hana/


## 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.

### Closest standard alternatives

- BP: Shows one business partner; does not check the link to employees in bulk.
- PA20: Shows one employee's master data; does not show the business partner and vendor link.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| PA0001 | Employees valid on the key date, company code and personnel area (driving table) | Read | - | ECC + S/4 |
| PA0000 | Employment status and leaving action | Read | PA0000-PERNR = PA0001-PERNR | ECC + S/4 |
| HRP1001 | Person ↔ central person and central person ↔ business partner relationships | Read | HRP1001-OTYPE = 'CP' AND HRP1001-SCLAS = 'P' AND HRP1001-SOBID = PA0001-PERNR | ECC + S/4 |
| BUT000 | Existence, grouping and central block of the business partner | Read | BUT000-PARTNER = HRP1001-SOBID (ilişki 207) | ECC + S/4 |
| BUT0ID | Personnel number identification on the business partner | Read | BUT0ID-PARTNER = BUT000-PARTNER AND BUT0ID-IDNUMBER = PA0001-PERNR | ECC + S/4 |
| LFB1 | Vendor linked to the employee for expense payments, with payment block | Read | LFB1-PERNR = PA0001-PERNR AND LFB1-BUKRS = PA0001-BUKRS | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |
| S_BUKRS | Company code | Range / multiple | PA0001-BUKRS | Yes |
| S_WERKS | Personnel area | Range / multiple | PA0001-WERKS | No |
| S_PERSG | Employee group | Range / multiple | PA0001-PERSG | No |
| P_VENDOR | Vendor record required for active employees | Checkbox | - | No |
| P_LEAVER | Also check leavers of the last 12 months | Checkbox | - | No |
| P_ERRONL | Show findings only | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Personnel no. | PA0001-PERNR |
| Name | PA0001-ENAME |
| Company code | PA0001-BUKRS |
| Personnel area | PA0001-WERKS |
| Employment status | PA0000-STAT2 |
| Central person | HRP1001-OBJID |
| Business partner | BUT000-PARTNER |
| Number of BPs | Calculated: Number of business partners linked to the central person with relationship 207 |
| Personnel no. ID | BUT0ID-IDNUMBER |
| BP block | BUT000-XBLCK |
| Vendor | LFB1-LIFNR |
| Vendor payment block | LFB1-SPERR |
| Finding | Calculated: By the rules: no BP, several BPs, no ID, blocked, no vendor, leaver's vendor open |
| Recommended action | Calculated: Fixed recommendation text per finding |

## How does the report work?

1. 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.
2. 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.
3. 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.
4. The vendor record for expense payments is found through LFB1-PERNR, with its payment block (SPERR).
5. 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.
6. A recommended action (re-run synchronization, block the vendor, etc.) is given as text for each finding.

## Authorization objects

- P_ORGIN: Read authorization for infotypes 0000 and 0001
- PLOG: Authorization to read central person relationships
- B_BUPA_GRP: Display authorization by business partner grouping
- F_LFA1_BUK: Vendor 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=hcm-employee-business-partner-link-check
