Status
Owner	Bernard Ng
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

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

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARA	MATNR	MATNR	Material Number	CHAR	18	Mandatory

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	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:

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

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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 Object data with exception of some fields which require transformation as mentioned in the transformation rule.

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

List the steps that need to occur before extraction can commence

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 Syniti Migrate to make the data Target ready:

1. 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 Syniti Migrate
2. 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

The following pre-load validations will be performed by the 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

The following pre-load validations will be performed by the 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:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

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

The following post-load validations will be performed by the 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

The following post-load validations will be performed by the 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.
• Data Object 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).

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history