HCM Report Custom development ALV report

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

  • BP Maintain Business Partner. Shows one business partner; does not check the link to employees in bulk.
  • PA20 Display HR Master Data. Shows one employee's master data; does not show the business partner and vendor link.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
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 actionPA0000-PERNR = PA0001-PERNRECC + S/4
HRP1001Infotype 1001 (Relationships) Database TablePerson ↔ central person and central person ↔ business partner relationshipsHRP1001-OTYPE = 'CP' AND HRP1001-SCLAS = 'P' AND HRP1001-SOBID = PA0001-PERNRECC + S/4
BUT000Business Partner: General DataExistence, grouping and central block of the business partnerBUT000-PARTNER = HRP1001-SOBID (ilişki 207)ECC + S/4
BUT0IDBusiness Partner ID NumbersPersonnel number identification on the business partnerBUT0ID-PARTNER = BUT000-PARTNER AND BUT0ID-IDNUMBER = PA0001-PERNRECC + S/4
LFB1Vendor Master (Company Code)Vendor linked to the employee for expense payments, with payment blockLFB1-PERNR = PA0001-PERNR AND LFB1-BUKRS = PA0001-BUKRSECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_KEYDTKey dateSingle valueSY-DATUMYes17.11.2026
S_BUKRSCompany codeRange / multiplePA0001-BUKRSYes1000
S_WERKSPersonnel areaRange / multiplePA0001-WERKSNo1000
S_PERSGEmployee groupRange / multiplePA0001-PERSGNo1
P_VENDORVendor record required for active employeesCheckbox—NoX
P_LEAVERAlso check leavers of the last 12 monthsCheckbox—NoX
P_ERRONLShow findings onlyCheckbox—NoX

Output columns

#ColumnSource
1Personnel no.PA0001-PERNR
2NamePA0001-ENAME
3Company codePA0001-BUKRS
4Personnel areaPA0001-WERKS
5Employment statusPA0000-STAT2
6Central personHRP1001-OBJID
7Business partnerBUT000-PARTNER
8Number of BPsCalculated Number of business partners linked to the central person with relationship 207
9Personnel no. IDBUT0ID-IDNUMBER
10BP blockBUT000-XBLCK
11VendorLFB1-LIFNR
12Vendor payment blockLFB1-SPERR
13FindingCalculated By the rules: no BP, several BPs, no ID, blocked, no vendor, leaver's vendor open
14Recommended actionCalculated Fixed recommendation text per finding

Sample output

Personnel no.NameCompany codePersonnel areaEmployment statusCentral personBusiness partnerNumber of BPsPersonnel no. IDBP blockVendorVendor payment blockFindingRecommended action
00012045Selin Karamanlı100010003600120450Active employee has no business partnerRe-run employee synchronization for this person
00012311Burak Tekinalp100011003600123119000004711200012311More than one business partnerArchive the extra business partner and keep a single relationship
00009874Hakan Sarıgöl100010000600098749000003120100009874E9874Leaver's vendor is not blockedSet a payment block on the vendor if no open items remain
A view built with fictional sample data; not real system data.

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.

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

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.

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