You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Status

30%

OwnerBernard Ng
Stakeholders

Purpose

The purpose of this document is to define the conversion approach for 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
      • VICNCN >= Migration cutoff date minus 5 years
    • Get Business partner from table VIBPOBJREL-PARTNER where : 
      • INTRENO = VICNCN-INTRENO 
      • ROLE = ZLESS
      • VALIDTO >= 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)

For scenarios where companies are not in legacy systems, a DCT is required to extend the role to each company business partner.

The tables/ fields will be similar to object 3007 and 3018 with no changes or additions, the role is an extension to the relevant business partners.

The below table explains the Role Matrix, applicable S4HANA tables and related Conversion Objects

RoleDescriptionTableConversion Object 
000000

General Role

Business Partner Role - General view Customers + Suppliers (including name and address standards, languages, emails, formats, identifications etc.)

BUT000CNV-3007
TR0604

Partner with vendor Role - assignment to a Business Partner and validity dates

BUT100CNV-3021

The key fields for the above mentioned S4HANA tables pertaining to CNV-3021 Partner with vendor are explained below:

  • Table BUT100 - Role assignment:
    • PARTNER - Business Partner Number - unique identifier of the Business partner which can be internally assigned by SAP or externally assigned by user.
    • RLTYP - Business Partner Role - This field is to select the Partner Role. For Issuer the role to be used is TR0604
    • VALID_FROM - Validity Start of a BP Role 
    • VALID_TO - Validity End of a BP Role

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
SourceScope

Source Approx No. of Records

Target SystemTarget 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,000S41,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, following the MDS # 3021

Table: BUT100 - Role TR0604- assignment to a Business Partner.

TableFieldData ElementField descriptionData typeLengthRequirement
BUT100PARTNERBU_PARTNERBusiness Partner NumberCHAR10Mandatory
BUT100RLTYPBU_PARTNERROLE

BP Role

CHAR6Mandatory
BUT100VALID_FROMBU_ROLE_VALID_FROMValidity Start of a BP RoleDEC15Mandatory
BUT100VALID_TOBU_ROLE_VALID_TOValidity End of a BP RoleDEC15Mandatory

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


No legacy cleansing

Based on CNV-3007 and 3018 relevancy rule and this CS relevancy rule


Relevant vendors vs excluded vendorsPF2/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 DescriptionTeam Responsible
1Refresh Vendor general data / XREF in SynitiData
2Refresh Vendor company data in SynitiData
3Extract from tables VICNCN and VIBPOBJRELData




Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
N/A



















Data Collection Template (DCT)

Target Ready Data Collection Template will be created for non ECC companies, to extend TR0604 role : 


Field nameField description Rule
BUT100-PARTNERBusiness Partner Number

This is a required field. 

This number is internally generated by the system

For DCT Purpose, the Business Partner number will need to be populated once the BP numbers are known after load of General Role


Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Ensure Syniti has the necessary connection and access to legacy serversData
2Ensure that create, change and deletion of master data is freeze in legacy Production systemLegacy 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 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 
  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 DescriptionTeam Responsible

1

Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti

Data team

2

Ensure that signed off value mappings have been maintained in the Syniti 

Syniti team

3

Confirm the value mappings as maintained in the Syniti

Data team

4

Ensure that Signed off CONSTRUCT from business has been received and maintained in Syniti 

Syniti/Data team

5

Execute transformation for the object 

Syniti team

6   

Monitor the transformation progress and ensure performance and completion is within allowed timeframe

Syniti/Data team

7.      

Generate Pre-Load reports.

Syniti team

8.      

Generate data load count.

Syniti team

9.      

Log errors as defects, if any and address resolutions. Close defects.

Syniti/Data team

10.      

Re-transform and re-validate the Pre-load reports if necessary.

Syniti/Data team

11.   

Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.

Business

12.   

Analyse and resolve any pre-load defects logged by business.

Syniti/Data team

13.   

Repeat steps 5 to 12 if necessary

Syniti/Data team

14.   

Proceed to pre-load validations

Data team


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

VIBPOBJREL

PARTNER

CONSTRUCT

S4HANA

BUT100PARTNERBusiness Partner Number

Refer to XREF of Business Partner

2

NA

NA

NA

NA

S4HANA

BUT100RLTYP

BP Role

Default to TR0604
3

NA

NA

NA

NA

S4HANA

BUT100VALID_FROMValidity Start of a BP RoleDefault to 10101000000
4

NA

NA

NA

NA

S4HANA

BUT100VALID_TOValidity End of a BP Role

Default to 99991231235959

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 DescriptionTeam Responsible

1

Extract PF2/WP2 source tables

Data

2

Ensure that Business Partner – General (3007) and Company Code (3008) are transformed

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

TaskAction

Verify count

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






Accuracy

TaskAction

Data Accuracy

Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and legacy/ DCT contents

Mapping Error Reports

Verify that all necessary error reports have been validated, and that errors have been addressed.




Business

Completeness

TaskAction

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

TaskAction

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

Configuration

Item #Configuration Item

1

Business Partner Configuration

Conversion Objects

Object #Preceding Object Conversion Approach

3007

Business Partner – General

3018Business Partners - FI Vendor (FLVN00)



Error Handling

Error TypeError DescriptionAction 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 role or BP).

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

TaskAction

Verify Count 

Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results


Accuracy

TaskAction

Data Accuracy

Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and legacy/DCT contents

Error Reports

Verify that all necessary error reports have been validated, and that errors have been addressed.




Business

Completeness

TaskAction

Verify Count

Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results

Validate Loaded Data

Validate, as per the loads files signed-off, that all records were created


Accuracy

TaskAction

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 legacy/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.
  • Object 3021 is in scope based on data design and any exception requested by business.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 9) 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.

  • No labels