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

Compare with Current View Page History

« Previous Version 41 Next »

Status

100%

OwnerBernard Ng
Stakeholders

PILLAY-ext, Lawrence NAIDU-ext, Prasad GARCIA-ext, Angel Luis SHAIK-ext, Sadeem 

Purpose

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

Business Partner - FI Vendor Role captures the vendor’s FI data attributes such as Reconciliation Account, Tax Code, Payment data, etc. at the Company Code level.

Conversion Scope

The scope of this document covers the approach for converting active vendors from Legacy Source Systems into S/4HANA following the Master Data Design Standard # 3018. 

There is high dependency on Business Partner General Role / data as per CNV-3007 Business Partners - General (Role 000000) which covers the overall scope and relevancy rules. Deduplication also determines the legacy vs target migration records at General level and subsequent Company code level. Example if 2 vendor records are combined at General level, the same has to be done at Company level. The values to be combined or overwritten has to be confirmed by data owners if values are different eg payment term , payment method, etc.

Fields that are not in company code level will be categorized as 'general' and will be covered in MDS / CNV # 3007.


Relevancy rule :

  1. Extract all records from legacy tables LFB1 and LFBW by matching LIFNR with final in-scope legacy records (LFA1-LIFNR) after deduplication is done in CNV-3007. BUKRS is based on in scope company code mapping.
  2. Exclude blocked vendors (LFB1-SPERR <> blank) and deleted vendors (LFB1-LOEVM <> blank)
  3. Extract all records from legacy table TTXID where TDOBJECT = LFB1 and table TTXIT with same TDID field


DCTs will be required for enrichment of legacy data with new S4 data eg. withholding tax data, texts, etc.


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2/PI2/WP253,000S453,000

Additional Information

Multi-language Requirement

Based on legacy or to-be design, there may be multiple language texts or data enrichment via DCT process (table TTXID and TTXIT)

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A





Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
LFB1LIFNRLIFNRVendorCHAR10Mandatory with mapping
LFB1BUKRSBUKRSCompany codeCHAR4Mandatory with mapping
LFB1ZUAWADZUAWAKey for Sorting According to AssignmentCHAR3Optional
LFB1AKONTAKONTReconciliation Account*CHAR10Mandatory with mapping
LFB1FDGRVFDGRVPlanning GroupCHAR10Optional
LFB1LNRZBLNRZBAccount Number of the Alternative PayeeCHAR10Optional
LFB1ZAHLSDZAHLSPayment Block (Key)CHAR1Mandatory with mapping
LFB1ZTERMDZTERMTerms of Payment KeyCHAR4Mandatory with mapping
LFB1REPRFREPRFCheck Double InvoiceCHAR1Optional
LFB1ALTKNALTKNPrevious Account NumberCHAR10Optional
LFB1HBKIDHBKIDShort Key for a House BankCHAR4Optional
LFB1INTADINTADClerks internet addressCHAR130Optional
LFB1QSRECQSRECType of RecipientCHAR2Optional
LFB1TOGRRTOGRRTolerance Group in Invoice VerificationCHAR3Optional
LFB1XLFZBXLFZBIndicator: Alternative Payee Using Account NumberCHAR1Optional
LFB1ZWELSZWELSPayment MethodCHAR10Optional
LFB1QSSKZQSSKZWithholding Tax CodeCHAR2Optional
LFB1UZAWEUZAWEPayment Method SupplementCHAR2Optional
LFBWLIFNRLIFNRVendorCHAR10Mandatory with mapping
LFBWBUKRSBUKRSCompany codeCHAR4Mandatory with mapping
LFBWWITHTWITHTWithholding Tax Type*CHAR2Mandatory with mapping
LFBWWT_SUBJCTWT_SUBJCTSubjectCHAR1Optional
LFBWQSRECQSRECType of recipientCHAR2Optional
LFBWWT_WITHCDWT_WITHCDWithholding Tax CodeCHAR2Mandatory with mapping
TTXIDTDOBJECTTDOBJECTText objectCHAR10Mandatory
TTXIDTDIDTDIDText IDCHAR4Mandatory
TTXITTDSPRASSPRASLanguage keyCHAR1Mandatory
TTXITTDOBJECTTDOBJECTText objectCHAR10Mandatory
TTXITTDIDTDIDText IDCHAR4Mandatory
TTXITTDTEXTTDTEXTShort textCHAR30Mandatory



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


No legacy cleansing

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


Relevant vendors vs excluded vendorsPF2/PI2/WP2








Conversion Process

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


Data Privacy and Sensitivity


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 LFB1, LFBW, TTXID, TTXIT tables via Syniti (Vendor company data) for all legacy systemsData
3Ensure DCT is collected for additional source data if any to combine with extracted source dataData




Selection Screen

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



















Data Collection Template (DCT)

Data Collection Template will be created for enrichment data in target values (the only legacy value will be the vendor number and company code). These data will be combined with transformed legacy data for final loading.


Field nameField description Rule
LFB1-ALTKNPrevious Master Record Number
LFB1-BUKRSCompany Code
LFB1-FDGRVPlanning Group
LFB1-HBKIDShort Key for a House Bank
LFB1-INTADInternet address of partner company clerk
LFB1-LIFNRVendor Number
LFB1-LNRZBAccount number of the alternative payee
LFB1-QSRECRECIPIENT TYPE
LFB1-REPRFCheck Double Invoice
LFB1-TOGRRDelivery Tolerance Group
LFB1-UZAWEPayment Method Supplement
LFB1-XLFZBIndicator: Alternative payee using 49account number
LFB1-ZAHLSBlock Key For Payment
LFB1-ZTERMPayment Terms
LFB1-ZUAWASort Key
LFB1-ZWELSPayment Methods
LFBW-WT_SUBJCTSubject
LFBW-WT_WITHCDWithholding Tax Code
LFBW-QSRECWITHHOLDING TAX TYPE OF RECIPIENT
LFBW-WITHTWITHHOLDING TAX TYPE
LFBW-WT_EXDFEXEMPTION FROM
LFBW-WT_EXDTEXEMPTION TO
LFBW-WT_EXNREXEMPTION NUMBER
LFBW-WT_EXRTEXEMPTION %
LFBW-WT_SUBJCTSUBJECT TO WITHHOLDING TAX
LFBW-WT_WITHCDWITHHOLDING TAX CODE
LFBW-WT_WTEXRSEXEMPTION REASON
LFBW-WT_WTSTCDWITHHOLDING TAX ID
TTXID-TDIDText ID
TTXID-TDOBJECTText object
TTXIT-TDIDText ID
TTXIT-TDOBJECTText object
TTXIT-TDSPRASLanguage key
TTXIT-TDTEXTShort text


Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Ensure Syniti has the necessary connection and access to legacy serversData
2Ensure that the necessary cleansing activities in legacy sources are complete (if any)Data / Business
3Ensure that create, change and deletion of master data is frozen or cut-off 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
1LFA1 relevancy execution in SynitiData
2LFB1 / LFBW / TTXID / TTXIT relevancy execution in SynitiData
3Business partner FI Vendor execution in SynitiData


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/PI2/WP2

LFB1

LIFNR

Vendor Number

S/4HANA

BCS002

LIFNR

Vendor Number

Derive via legacy to BP Master Mapping

2

PF2/PI2/WP2

LFB1

BUKRS

Company Code

S/4HANA

BS001

BUKRS

Company Code

Derive via Company Code mapping

3

PF2/PI2/WP2

LFB1

AKONT

Reconciliation Account

S/4HANA

LFB1

AKONT

Reconciliation Account

Derive via GL account mapping

4

PF2/PI2/WP2

LFB1

ZUAWA

Sort Key

S/4HANA

LFB1

ZUAWA

Sort Key

Derive via Sort key mapping

5

PF2/PI2/WP2

LFB1

ZTERM

Payment Terms

S/4HANA

LFB1

ZTERM

Payment Terms

Derive via Payment Terms mapping

8

PF2/PI2/WP2

LFB1

REPRF

Check Double Invoice

S/4HANA

LFB1

REPRF

Check Double Invoice

Default Check ‘X’

9

PF2/PI2/WP2

LFB1

ZWELS

Payment Methods

S/4HANA

LFB1

ZWELS

Payment Methods

Derive via Payment Methods mapping

10

PF2/PI2/WP2

LFB1

TOGRR

Delivery Tolerance Group

S/4HANA

LFB1

TOGRR

Delivery Tolerance Group

Derive via Tolerance Grp mapping  

14

PF2/PI2/WP2

LFB1

ZAHLS

Block Key For Payment

S/4HANA

LFB1

ZAHLS

Block Key for Payment

Derive via Payment block mapping  

18

PF2/PI2/WP2

LFB1

FDGRV

Planning Group

S/4HANA

LFB1

FDGRV

Planning Group

Derive via Planning Group mapping  

21

PF2/PI2/WP2

LFB1

LNRZB

Account number of the alternative payee

S/4HANA

LFB1

LNRZB

Account number of the alternative payee

Derive via legacy to BP Master Mapping

28

PF2/PI2/WP2

LFB1

HBKID

Short Key for a House Bank

S/4HANA

LFB1

HBKID

Short Key for a House Bank

Derive via House bank mapping

33

PF2/PI2/WP2

LFB1

QSREC

RECIPIENT TYPE

S/4 HANA

LFB1

QSREC

RECIPIENT TYPE

Derive via Recipient type mapping

36

PF2/PI2/WP2

LFB1

ALTKN

Previous Master Record Number

S/4HANA

LFB1

ALTKN

Previous Master Record Number

Legacy vendor number LFB1-LIFNR

39

PF2/PI2/WP2

LFB1

UZAWE

Payment Method Supplement

S/4HANA

LFB1

UZAWE

Payment Method Supplement

Derive via Payment Method Supplement mapping

45

PF2/PI2/WP2

LFB1

INTAD

Internet address of partner company clerk

S/4HANA

LFB1

INTAD

Internet address of partner company clerk

To leave blank

46

PF2/PI2/WP2

LFB1

XLFZB

Indicator: Alternative payee using account number

S/4HANA

LFB1

XLFZB

Indicator: Alternative payee using account number

Keep legacy value

56

PF2/PI2/WP2

LFBW

LIFNR

Vendor Number

S/4HANA

BCS002

LIFNR

Vendor Number

Derive via legacy to BP Master Mapping

57

PF2/PI2/WP2

LFBW

BUKRS

Company Code

S/4HANA

BS001

BUKRS

Company Code

Derive via Company Code mapping

58

PF2/PI2/WP2

LFBW

WITHT

WITHHOLDING TAX TYPE

S/4HANA

LFBW

WITHT

WITHHOLDING TAX TYPE

Derive from Withholding tax mapping

59

PF2/PI2/WP2

LFBW

WT_WITHCD

WITHHOLDING TAX CODE

S/4HANA

LFBW

WT_WITHCD

WITHHOLDING TAX CODE

Derive from Withholding tax mapping

60

PF2/PI2/WP2

LFBW

WT_SUBJCT

SUBJECT TO WITHHOLDING TAX

S/4HANA

LFBW

WT_SUBJCT

SUBJECT TO WITHHOLDING TAX

Keep legacy value

61

PF2/PI2/WP2

LFBW

QSREC

WITHHOLDING TAX TYPE OF RECIPIENT

S/4HANA

LFBW

QSREC

WITHHOLDING TAX TYPE OF RECIPIENT

Derive from Withholding tax mapping

62

PF2/PI2/WP2

LFBW

WT_WTSTCD

WITHHOLDING TAX ID

S/4HANA

LFBW

WT_WTSTCD

WITHHOLDING TAX ID

Keep legacy value

63

PF2/PI2/WP2

LFBW

WT_EXNR

EXEMPTION NUMBER

S/4HANA

LFBW

WT_EXNR

EXEMPTION NUMBER

Keep legacy value

64

PF2/PI2/WP2

LFBW

WT_EXRT

EXEMPTION %

S/4HANA

LFBW

WT_EXRT

EXEMPTION %

Keep legacy value

65

PF2/PI2/WP2

LFBW

WT_WTEXRS

EXEMPTION REASON

S/4HANA

LFBW

WT_WTEXRS

EXEMPTION REASON

Keep legacy value

66

PF2/PI2/WP2

LFBW

WT_EXDF

EXEMPTION FROM

S/4HANA

LFBW

WT_EXDF

EXEMPTION FROM

Keep legacy value

67

PF2/PI2/WP2

LFBW

WT_EXDT

EXEMPTION TO

S/4HANA

LFBW

WT_EXDT

EXEMPTION TO

Keep legacy value

76PF2/PI2/WP2TTXIDTDOBJECTText objectS/4HANATTXIDTDOBJECTText object

Keep legacy value

77PF2/PI2/WP2TTXIDTDIDText IDS/4HANATTXIDTDIDText ID

Keep legacy value

78PF2/PI2/WP2TTXITTDSPRASLanguage keyS/4HANATTXITTDSPRASLanguage key

Keep legacy value

79PF2/PI2/WP2TTXITTDOBJECTText objectS/4HANATTXITTDOBJECTText object

Keep legacy value

78PF2/PI2/WP2TTXITTDIDText IDS/4HANATTXITTDIDText ID

Keep legacy value

79PF2/PI2/WP2TTXITTDTEXTShort textS/4HANATTXITTDTEXTShort text

Keep legacy value

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

Transformation Mapping

Mapping Table Name

Description

BP Master Mapping

Legacy to S4 Business Partner Vendor mapping

Company Code Mapping

Legacy to S4 Company Code Mapping

Payment Terms Mapping

Legacy to S4 Payment Terms Mapping

Payment Method Mapping

Payment Method Mapping

Tax Category Mapping

Legacy to S4 Tax Category Mapping

GL Account Mapping

Legacy to S4 GL Account Mapping

Sort Key Mapping

Legacy to S4 Sort Key Mapping

Planning Group Mapping

Legacy to S4 Planning Group Mapping

Withholding tax type / code Mapping

Legacy to S4 Withholding tax type / code Mapping

Tolerance Group Mapping

Legacy to S4Tolerance Group Mapping

Payment block Mapping

Legacy to S4Payment block Mapping

Authorization Group Mapping

Legacy to S4Authorization Group Mapping

Planning Group Mapping

Legacy to S4Planning Group Mapping

House bank mappingLegacy to S4House bank mapping
Tolerance Group mappingLegacy to S4Tolerance Group mapping
Payment Method Supplement mappingLegacy to S4 Payment Method Supplement mapping

Recipient type mapping

Legacy to S4 Recipient type mapping




Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

1

Extract PF2/PI2/WP2 source tables – LFB1, LFBW, TTXID, TTXIT

Data

2

Ensure that Business Partner – General and COA GL accounts are loaded

Data

3

Ensure all vendor master data collection templates, deduplication and cleansing completeness and no errors

Data

4

Ensure that all required Configurations are in S/4HANA

Data

5

Ensure mappings are completed

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

Loading will be done through migration cockpit and therefore, data from the transformation export view to be exported into the load file format.

export views to be prepared based on the field list from the load template attached. 

 Source data for Supplier.xml

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 DCTs and 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

4

Payment Terms Configuration

5

Payment Method Configuration

6

Reconciliation Account Configuration

7

Withholding Tax Types Configuration

8

Sort Key configuration

9

Planning Group configuration

10

Tolerance Group configuration

11

Payment block configuration

12

Authorization Group configuration

13

Planning Group configuration

14

Accounting Clerk configuration

15

House bank configuration

16

Tolerance Group configuration

17

Payment Method Supplement configuration

18

 Recipient type configuration

Conversion Objects

Object #Preceding Object Conversion Approach

3007

Business Partner – General

1067

GL Account Operational CoA (incl. secondary CE)

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 payment terms).

If it is an invalid data, business needs to review and correct the source of the data either in PF2/PI2/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 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

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 DCT contents

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

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

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 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.
  • BP Vendor General is in scope based on data design and any exception requested by business.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 41) Mar 09, 2026 11:46 NG-ext, Bernard
v. 48 Jan 30, 2026 13:36 NG-ext, Bernard
v. 47 Jan 30, 2026 13:35 NG-ext, Bernard
v. 46 Jan 29, 2026 10:44 NG-ext, Bernard
v. 45 Jan 21, 2026 14:38 NG-ext, Bernard
v. 44 Jan 08, 2026 10:21 NG-ext, Bernard
v. 43 Dec 18, 2025 12:57 NG-ext, Bernard
v. 42 Dec 18, 2025 07:50 NG-ext, Bernard
v. 41 Dec 15, 2025 12:23 NG-ext, Bernard
v. 40 Dec 15, 2025 09:17 NG-ext, Bernard

Go to Page History

Workflow history

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

  • No labels