Status	30%
Owner	Bernard Ng
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Business Partners - Partner with Vendor Account (TR0604) in S/4 HANA.

Business Partner - Partner with Vendor Account Role is used in Real Estate Management (RE-FX) for entities acting as a supplier/vendor who needs an associated Vendor account for payments. It links a general business partner to the vendor functionality within SAP, ensuring role-specific details and processes (like invoicing/payments) are handled correctly.

Conversion Scope

The scope of this document covers the approach for extending the Business Partner TR0604 role from Legacy Source Systems into S/4HANA following the Master Data Design Standard # 3021.

Relevancy rule :

Vendor is active with RE/FX contracts within 5 years -
- check REAL ESTATE CONTRACT data in VICNCN table where :
  - BUKRS = company codes that are in scope
- Get Business partner from table VIBPOBJREL-PARTNER where :
  - INTRENO = VICNCN-INTRENO
  - ROLE = ZLESS
  - VALIDTO is not < Migration cutoff date minus 5 years
exists in General Role / data as per CNV-3007 Business Partners - General (Role 000000) and Company data as per CNV-3018 Business Partners - FI Vendor (FLVN00)

The tables/ fields of Business partner will be similar to object 3007 and 3018 with no changes or additions.

There are 2 group go-live as below:

Group 1 go-live is planned for 1 July 2028
Group 2 go-live is planned for 1 Jan 2029

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2/WP2	Extract business partner from VIBPOBJREL-PARTNER and as determined as active based on the relevancy criteria. Some companies not in legacy will be added to S4 requiring use of DCT	1,000	S4	1,000

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

Error Message/Report Description	Rule	Output	Source System
No legacy cleansing	Based on CNV-3007 and 3018 relevancy rule and this CS relevancy rule	Relevant vendors vs excluded vendors	PF2/WP2

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

N/A

Extraction

Extract data from a source into Syniti. There are 2 possibilities:

The data exists. Syniti connects to the source and loads the data into Syniti. There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if Syniti cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti. This is to be conducted using DCT (Data Collection Template) in Syniti

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Refresh Vendor general data / XREF in Syniti	Data
2	Refresh LFB1, LFBW, TTXID, TTXIT tables via Syniti (Vendor company data) for all legacy systems	Data

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field name	Field description	Rule
LFB1-LIFNR	Vendor Number	Drop down value from LFA1-LIFNR Business Partner DCT as FI Vendor on required company code level
LFB1-BUKRS	Company Code	Drop down value from T001-BUKRS company code DCT (only with active for finance indicator)

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Ensure Syniti has the necessary connection and access to legacy servers	Data
2	Ensure that the necessary cleansing activities in legacy sources are complete	Data / Business
3	Ensure that create, change and deletion of master data is freeze in legacy Production system	Legacy IT

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible
1	LFA1 relevancy execution in Syniti	Data
2	LFB1 relevancy execution in Syniti	Data
3	BP relevancy execution in Syniti	Data
4	Business partner FI Vendor execution in Syniti	Data

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source description	Target system	Target Table_Field	Target Table_Field	Target description	Transformation logic
1	PF2/WP2	LFB1	LIFNR	Vendor Number	S/4HANA	BCS002	LIFNR	Vendor Number	Derive via legacy to BP cross reference mapping
2	PF2/WP2	LFB1	BUKRS	Company Code	S/4HANA	BS001	BUKRS	Company Code	Derive via legacy to Company Code mapping

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Mapping Table Name	Description
Legacy Vendor-BP Master Mapping	Legacy to S4 Business Partner Vendor mapping
Business Partner deDupe mapping (Global Data)	dedupe Golden-child (Global) mapping
Company Code Mapping	Legacy to S4 Company Code Mapping
deDupe Vendor Company Code Nominations Mapping	Golden-Child Company Code data Mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Extract PF2/WP2 source tables – LFB1	Data
2	Ensure that Business Partner – General is loaded	Data
2	Ensure all vendor master data collection templates, deduplication and cleansing completeness and no errors	Data
3	Ensure that all required Configurations are in S/4HANA	Data

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify count	Verify that the record count in the pre-load file is the same as the record count based on the approved DCT records

Accuracy

Task	Action
Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents
Mapping Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.

Business

Completeness

Task	Action
Verify Count for External Vendor (not Key Input Supplier)	Verify that the record count in the pre-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Count for Intercompany Vendor	Verify that the record count in the pre-load file is the same as the record count based on the approved DCT records (intercompany Vendors)
Verify Relevancy Rules	Verify that the relevancy rules were correctly applied

Accuracy

Task	Action
Verify Data Accuracy	Verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Verify Transformation Rules	Verify that the transformation rules are correct and have been carried out correctly

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step description	Team responsible
1	Ensure the load tools are transported into the correct tool instance.	Data team
2	Ensure all required mappings are submitted and complete	Data team
3	Ensure Pre-load sign-offs are obtained.	Data team
4	Execute Upload tool	Data team
5	Generate the post load reports in tool.	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 5 to 7 if necessary.	Data team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Obtain the approved upload USER ID’s to be used (e.g. Firefighter ID)
2	SAP USER profile (SU3) Date and Decimal Notation Formats are in sync with the load format
3	Company Code Configuration

Conversion Objects

Object #	Preceding Object Conversion Approach
3007	Business Partner – General
1067	GL Account Operational CoA (incl. secondary CE)

Error Handling

Error Type

Error Description

Action Taken

Configuration

<configuration> is not valid/missing

If it is a missing configuration item then engage Functional team to expedite and fix the error in the system.

Invalid Data

<parameter> is not valid.

The parameter entry needs to be reviewed (ex. invalid payment terms).

If it is an invalid data, business needs to review and correct the source of the data either in PF2/WP2 or if it’s mapped in DCT.

Technical Setup

Interface / Connection issue within target system’s landscape

N/A – the data will be loaded directly to S/4HANA environment

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Count for External Vendor	Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Count for Intercompany Vendor	Verify that the record count in the post-load file is the same as the record count based on the approved DCT records (intercompany Vendors)
Verify Count for Key Input Suppliers	Verify that the record count in the post-load file for Key Input supplier types are the same as the record count based on the approved DCT records for Key Input Suppliers

Accuracy

Task	Action
Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents
Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.

Business

Completeness

Task	Action
Verify Count for External Vendor	Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Count for Intercompany Vendor	Verify that the record count in the post-load file is the same as the record count based on the approved DCT records (intercompany Vendors)
Verify Count for Key Input Suppliers	Verify that the record count in the pre-load file for Key Input supplier types are the same as the record count based on the approved DCT records for Key Input Suppliers
Validate Loaded Data	Validate, as per the loads files signed-off, that all records were created

Accuracy

Task	Action
Verify Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Validate Loaded Data	Validate, as per the loads files signed-off, that all records were created

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
is in scope based on data design and any exception requested by business.
One-Time Vendors are not going to be converted. There will be a redesign of One-Time Vendor master data in S4 and the business partner creation in S/4HANA will be facilitated by functional team (configuration window).

Change log

Version	Published	Changed By
CURRENT (v. 7)	Feb 03, 2026 08:23	NG-ext, Bernard
v. 25	Jan 26, 2026 14:22	NG-ext, Bernard
v. 24	Jan 26, 2026 13:51	FANSALKAR-ext, Ashish
v. 23	Jan 26, 2026 11:18	NG-ext, Bernard
v. 22	Jan 22, 2026 10:37	NG-ext, Bernard
v. 21	Jan 22, 2026 10:33	NG-ext, Bernard
v. 20	Jan 22, 2026 10:06	NG-ext, Bernard
v. 19	Jan 21, 2026 14:27	NG-ext, Bernard
v. 18	Jan 21, 2026 14:19	NG-ext, Bernard
v. 17	Jan 21, 2026 11:53	NG-ext, Bernard

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

Mar 19, 2026	Actor	Type	Activity	Version
Tech Review of Updates	NG-ext, Bernard	State	changed state to Tech Review of Updates at 3:27 pm	v26
Mar 18, 2026
Update in progress	WENNINGER-ext, Sascha	State	changed state to Update in progress at 5:53 pm	v26
Feb 10, 2026
Edited following Tech Review	NG-ext, Bernard	Comment	commented 8:32 am If you are referring to the FLVN001 role, that is covered in # 3026
Feb 09, 2026
	GOMES-ext, Andreia	Comment	commented 7:44 pm PARA-ext, Anil / NG-ext, Bernard In the To be design we expect that all RE-FX contract have a PO assigned. This means that the Business Partner will also needs to be extended to a Purchase role.
Feb 03, 2026
	NG-ext, Bernard	Edit	updated the page at 8:23 am
	NG-ext, Bernard	State	changed state to Edited following Tech Review at 7:23 am	v26

Workflow history

Space shortcuts

Page tree

CNV-3021 Business Partners - Partner with Vendor Account (TR0604)

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history