Status

Percentage Progress | Vectors (Formerly: SP Percentage progress bar)

backgroundColor	0052CC
percentage	60100

Owner

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

Extract all records from legacy tables LFB1 and LFBW by matching LIFNR with CNV-3007 final in-scope legacy records (LFA1-LIFNR) after deduplication is done in CNV-3007. BUKRS is based on in scope company code mapping.
Exclude blocked vendors (LFB1-SPERR <> blank) and deleted vendors (LFB1-LOEVM <> blank)
Extract all records from legacy table TTXID where tables STXH and STXL where TDOBJECT = LFB1 and table TTXIT with same TDID field
Extract classification data from table INOB where OBTAB = LFB1. If found, extract from table AUSP with similar OBJEK and KLART = 010

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

Source	Scope	Source Approx No. of Records	Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2/PI2/WP2	Based on relevancy criteria exists in General Role / data as per CNV-3007 Business Partners - General (Role 000000)	53,000	S4	53,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 STXH and STXL)

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
LFB1	LIFNR	LIFNR	Vendor	CHAR	10	Mandatory with mapping
LFB1	BUKRS	BUKRS	Company code	CHAR	4	Mandatory with mapping
LFB1	ZUAWA	DZUAWA	Key for Sorting According to Assignment	CHAR	3

Optional

Mandatory with mapping
LFB1	AKONT	AKONT	Reconciliation Account*	CHAR	10	Mandatory with mapping
LFB1	FDGRV	FDGRV	Planning Group	CHAR	10

OptionalLFB1LNRZB

Mandatory with mapping

LFB1

FRGRPFRGRPRelease GroupCHAR4Optional

LNRZB

Account Number of the Alternative Payee

CHAR

10

OptionalLFB1XVERRXVERR_LFB1Clearing with CustomerCHAR

1

Optional
LFB1	ZAHLS	DZAHLS	Payment Block (Key)	CHAR	1

Mandatory

Optional with mapping
LFB1	ZTERM	DZTERM	Terms of Payment Key	CHAR	4

Mandatory LFB1

Optional with mapping

LFB1

GUZTEGUZTETerms of Payment Key for Credit MemosCHAR4Optional

REPRF	REPRF	Check Double Invoice	CHAR	1	Optional
LFB1	ALTKN	ALTKN	Previous Account Number	CHAR	10	Optional
LFB1

TOGRU

HBKID

TOGRU

HBKID

Short Key for a House Bank

Tolerance Group

	CHAR	4	Optional
LFB1

EIKTO

INTAD

EIKTO_KOur Account Number with the SupplierCHAR12Optional

INTAD

Clerks internet

LFB1BUSABBUSABAccounting ClerkCHAR2OptionalLFB1ZSABEDZSABE_KClerk at SupplierCHAR15OptionalLFB1HBKIDWT_SUBJCTShort Key for a House BankCHAR4OptionalLFB1INTADTDIDClerks internet

address	CHAR	130	Optional
LFB1	QSREC	QSREC	Type of Recipient	CHAR	2	Optional
LFB1	TOGRR	TOGRR	Tolerance Group in Invoice Verification	CHAR	3	Optional
LFB1	XLFZB	XLFZB	Indicator: Alternative Payee Using Account Number	CHAR	1

Mandatory with mapping

Optional
LFB1	ZWELS	ZWELS	Payment Method	CHAR	10	Optional
LFB1

BEGRU

QSSKZ

BEGRUAuthorization Group

QSSKZ

Withholding Tax Code

CHAR

4

2	Optional
LFB1

VZSKZ

UZAWE

VZSKZInterest Calculation Indicator

UZAWE

Payment Method Supplement

CHAR

2

Optional

LFB1

LFBW

KVERM

LIFNR

DATLZ

LIFNR

Memo

Vendor

CHAR

30

10

Optional

Mandatory with mapping

LFB1

LFBW

LNRZE

BUKRS

KULTGHead office account number

BUKRS

Company code

CHAR

10

4

Optional

Mandatory with mapping

LFB1

LFBW

ZINDT

WITHT

XPOREKey date of the last intereste calculationDATS8OptionalLFB1ZINRTQSZNRInterest calculation frequency in monthsNUMC2OptionalLFB1DATLZQSZDTDate of the last interest calculationDATS8OptionalLFB1XDEZVQSSKZIndicator: Local Processing?CHAR1OptionalLFB1WEBTRQSRECBill of exchange limit (in local currency)CURR13OptionalLFB1KULTGBLNKZProbable time until check is validDEC3OptionalLFB1XPOREZGRUPIndicator: Pay all items separatelyCHAR1OptionalLFB1QSZNRMGRUPCertificate Number of the Withholding Tax ExemptionCHAR10OptionalLFB1QSZDTUZAWEValidity Date for Withholding Tax Exemption CertificateDATS8OptionalLFB1QSSKZQSBGRWithholding Tax CodeCHAR2OptionalLFB1BLNKZXEDIPSubsidy Indicator for Determining the Reduction RatesCHAR3OptionalLFB1MINDKTLFXSMinority IndicatorsCHAR3OptionalLFB1ZGRUPXLFZBKey for Payment GroupingCHAR2OptionalLFB1MGRUPGRIDTKey for Dunning GroupingCHAR2OptionalLFB1UZAWEXAUSZPayment Method SupplementCHAR2OptionalLFB1QSBGRPERNRAuthority for Exemption from Withholding TaxCHAR1OptionalLFB1QLANDNODELWithholding Tax Country KeyCHAR3OptionalLFB1XEDIPTLFNSIndicato: Send Payment Advices by EDICHAR1OptionalLFB1TLFXSCERDTAccounting clerk's fax number at the customer/vendorCHAR31OptionalLFB1GRIDTSPERRDistribution Type for Employment TaxCHAR2OptionalLFB1XAUSZLOEVMIndicator for periodic account statementsCHAR1OptionalLFB1PERNRWT_SUBJCTPersonnel NumberNUMC8OptionalLFB1TLFNSMAHNAAccounting clerk's telephone number at business partnerCHAR30OptionalLFB1CIIUCODEMANSPMAIN ECONOMIC ACTIVITYNUMC4OptionalLFB1CERDTLFRMACERTIFICATION DATEDATS8OptionalLFB1AVSNDMADAT_SCRSEND PAYMENT ADVICE BY XMLCHAR1OptionalLFB1PREPAY_RELEVANTGMVDT_SCRPREPAYMENT RELEVANCECHAR1OptionalLFBWLIFNRLIFNRVendorCHAR10Mandatory with mappingLFBWBUKRSBUKRSCompany codeCHAR4Mandatory with mappingLFBWWITHTWITHTWithholding Tax Type*CHAR2Mandatory with mappingLFBWWT_SUBJCTWT_SUBJCTSubjectCHAR1OptionalLFBWWT_WITHCDWT_WITHCDWithholding Tax CodeCHAR2Mandatory with mappingLFBWWT_WTSTCDWT_WTSTCDWithholding Tax Identification NumberCHAR16OptionalLFBWWT_EXNRWT_EXNRExemption NumberCHAR25OptionalLFBWWT_EXRTWT_EXRTExemption RateDEC5OptionalLFBWWT_WTEXRSWT_WTEXRSExemption ReasonCHAR2OptionalLFBWWT_EXDFWT_EXDFExemption FromDATS8OptionalLFBWWT_EXDTWT_EXDTExemption ToDATS8OptionalINOBCUOBJCUOBJInternal object numberCHAR18MandatoryINOBKLARTKLASSENARTClass typeCHAR3MandatoryINOBOBTABTABELLEDatabase tableCHAR30MandatoryINOBOBJEKCUOBNObject numberCHAR90MandatoryAUSPOBJEKCUOBNObject numberCHAR90MandatoryAUSPATINNATINNInternal characteristicCHAR10MandatoryAUSPKLARTKLASSENARTClass typeCHAR3MandatoryAUSPATWRTATWRTCharacteristic valueCHAR70MandatoryTTXIDTDOBJECTTDOBJECTText objectCHAR10MandatoryTTXIDTDIDTDIDText IDCHAR4MandatoryTTXITTDSPRASSPRASLanguage keyCHAR1MandatoryTTXITTDOBJECTTDOBJECTText objectCHAR10MandatoryTTXITTDIDTDIDText IDCHAR4MandatoryTTXITTDTEXTTDTEXTShort textCHAR30Mandatory

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

WITHT	Withholding Tax Type*	CHAR	2	Optional with mapping
LFBW	WT_SUBJCT	WT_SUBJCT	Subject	CHAR	1	Optional
LFBW	QSREC	QSREC	Type of recipient	CHAR	2	Optional
LFBW	WT_WITHCD	WT_WITHCD	Withholding Tax Code	CHAR	2	Optional with mapping
STXH	TDOBJECT	TDOBJECT	Text object	CHAR	10	Conditional
STXH	TDNAME	TDNAME	Text Name	CHAR	70	Conditional
STXH	TDID	TDID	Text ID	CHAR	4	Conditional
STXH	TDSPRAS	TDSPRAS	Language Key	LANG	1	Conditional
STXL	TDOBJECT	TDOBJECT	Text object	CHAR	10	Conditional
STXL	TDNAME	TDNAME	Text name	CHAR	70	Conditional
STXL	TDID	TDID	Text ID	CHAR	4	Conditional
STXL	TDSPRAS	SPRAS	Language key	CHAR	1	Conditional
STXL	CLUSTD	CLUSTD	Data	CHAR	7902	Conditional

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

BUT100	PARTNER	BU_PARTNER	Business Partner Number	CHAR	10	Mandatory
BUT100	RLTYP	BU_PARTNERROLE	BP Role	CHAR	6	Mandatory

Data Cleansing

ID

Criticality

Error Message/Report Description

Rule

Output

Source System

No legacy cleansing

Based on CNV-3007 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:

Image Added

Data Privacy and Sensitivity

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 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, STXH, STXL 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)

Data Collection Template is required for enrichment purposes eg. legacy fields are missing data which is mandatory in target S4. The DCT fields are target values requiring no transformation.

Field Name	Field description	Rule
LFB1-LIFNR	Vendor number
LFB1-BUKRS	Company code
~~LFB1-ZUAWA~~	~~Key for Sorting According to Assignment~~
~~LFB1-ZTERM~~	~~Terms of Payment Key~~
~~LFB1-XLFZB~~	~~Indicator: Alternative Payee Using Account Number~~
LFB1-FDGRV	Planning Group

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 (if any)	Data / Business
3	Ensure that create, change and deletion of master data is frozen or cut-off 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 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 Syniti
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 / LFBW / STXH/ STXL relevancy execution in Syniti	Data
3	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 Master Mapping
2	PF2/WP2	LFB1	BUKRS	Company Code	S/4HANA	BS001	BUKRS	Company Code	Derive via Company Code mapping
3	PF2/WP2	LFB1	AKONT	Reconciliation Account	S/4HANA	LFB1	AKONT	Reconciliation Account	Derive via GL account mapping
4	PF2/WP2	LFB1	ZUAWA	Sort Key	S/4HANA	LFB1	ZUAWA	Sort Key	Derive via Sort key mapping (default mapping to 009)
5	PF2/WP2	LFB1	ZTERM	Payment Terms	S/4HANA	LFB1	ZTERM	Payment Terms	Derive via Payment Terms mapping
8	PF2/WP2	LFB1	REPRF	Check Double Invoice	S/4HANA	LFB1	REPRF	Check Double Invoice	Default Check ‘X’
9	PF2/WP2	LFB1	ZWELS	Payment Methods	S/4HANA	LFB1	ZWELS	Payment Methods	Derive via Payment Methods mapping
10	PF2/WP2	LFB1	TOGRR	Delivery Tolerance Group	S/4HANA	LFB1	TOGRR	Delivery Tolerance Group	Derive via Tolerance Grp mapping
14	PF2/WP2	LFB1	ZAHLS	Block Key For Payment	S/4HANA	LFB1	ZAHLS	Block Key for Payment	Derive via Payment block mapping
18	PF2/WP2	LFB1	FDGRV	Planning Group	S/4HANA	LFB1	FDGRV	Planning Group	Derive via Planning Group mapping
21	PF2/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/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/WP2	LFB1	QSREC	RECIPIENT TYPE	S/4 HANA	LFB1	QSREC	RECIPIENT TYPE	Derive via Recipient type mapping
36	PF2/WP2	LFB1	ALTKN	Previous Master Record Number	S/4HANA	LFB1	ALTKN	Previous Master Record Number	Legacy vendor number LFB1-LIFNR
39	PF2/WP2	LFB1	UZAWE	Payment Method Supplement	S/4HANA	LFB1	UZAWE	Payment Method Supplement	Derive via Payment Method Supplement mapping
45	PF2/WP2	LFB1	INTAD	Internet address of partner company clerk	S/4HANA	LFB1	INTAD	Internet address of partner company clerk	To leave blank
46	PF2/WP2	LFB1	XLFZB	Indicator: Alternative payee using account number	S/4HANA	LFB1	XLFZB	Indicator: Alternative payee using account number	Keep legacy value
56	PF2/WP2	LFBW	LIFNR	Vendor Number	S/4HANA	BCS002	LIFNR	Vendor Number	Derive via legacy to BP Master Mapping
57	PF2/WP2	LFBW	BUKRS	Company Code	S/4HANA	BS001	BUKRS	Company Code	Derive via Company Code mapping
58	PF2

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:

Image Removed

Data Privacy and Sensitivity

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 DescriptionTeam Responsible1Refresh LFA1 tables via Syniti (Vendor general data)Data2Refresh LFB1, LFBW, INOB, AUSP, TTXID, TTXIT tables via Syniti (Vendor company data)Data3Ensure 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/setN/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 RuleLFB1-LIFNRVendor NumberLFB1-BUKRSCompany CodeLFB1-AKONTReconciliation AccountLFB1-ZUAWASort KeyLFB1-ZTERMPayment TermsLFB1-GUZTECredit Memo Payment TermsLFB1-TOGRUTolerance GroupLFB1-REPRFCheck Double InvoiceLFB1-ZWELSPayment MethodsLFB1-TOGRRDelivery Tolerance GroupLFB1-BEGRUAuthorization GroupLFB1-VZSKZInterest Calculation IndicatorLFB1-XVERRIndicator: clearing between customer an vendorLFB1-ZAHLSBlock Key For PaymentLFB1-EIKTOOur Account Number With VendorLFB1-ZSABEClerk at vendorLFB1-KVERMMemoLFB1-FDGRVPlanning GroupLFB1-BUSABAccounting ClerkLFB1-LNRZEHead office account numberLFB1-LNRZBAccount number of the alternative payeeLFB1-ZINDTKey date of the last intereste calculationLFB1-ZINRTInterest calculation frequency in monthsLFB1-DATLZDate of the last interest calculationLFB1-XDEZVIndicator: Local Processing?LFB1-WEBTRBill of exchange limit (in local currency)LFB1-KULTGProbable time until check is validLFB1-HBKIDShort Key for a House BankLFB1-XPOREIndicator: Pay all items separatelyLFB1-QSZNRCertificate Number of the Withholding Tax ExemptionLFB1-QSZDTValidity Date for Withholding Tax Exemption CertificateLFB1-QSSKZWithholding Tax CodeLFB1-QSRECRECIPIENT TYPELFB1-BLNKZSubsidy Indicator for Determining the Reduction RatesLFB1-MINDKMinority IndicatorsLFB1-ALTKNPrevious Master Record NumberLFB1-ZGRUPKey for Payment GroupingLFB1-MGRUPKey for Payment GroupingLFB1-UZAWEPayment Method EupplementLFB1-QSBGRAuthority for Exemption from Withholding TaxLFB1-QLANDWithholding Tax Country KeyLFB1-XEDIPIndicato: Send Payment Advices by EDILFB1-FRGRPRelease Approval GroupLFB1-TLFXSAccounting clerk's fax number at the customer/vendorLFB1-INTADInternet address of partner company clerkLFB1-XLFZBIndicator: Alternative payee using 49account numberLFB1-GRIDTDistribution Type for Employment TaxLFB1-XAUSZIndicator for periodic account statementsLFB1-PERNRPersonnel NumberLFB1-TLFNSAccounting clerk's telephone number at business partnerLFB1-CIIUCODEMAIN ECONOMIC ACTIVITYLFB1-CERDTCERTIFICATION DATELFB1-AVSNDSEND PAYMENT ADVICE BY XMLLFB1-PREPAY_RELEVANTPREPAYMENT RELEVANCELFBW-WITHTWITHHOLDING TAX TYPELFBW-WT_WITHCDWITHHOLDING TAX CODELFBW-WT_SUBJCTSUBJECT TO WITHHOLDING TAXLFBW-QSRECWITHHOLDING TAX TYPE OF RECIPIENTLFBW-WT_WTSTCDWITHHOLDING TAX IDLFBW-WT_EXNREXEMPTION NUMBERLFBW-WT_EXRTEXEMPTION %LFBW-WT_WTEXRSEXEMPTION REASONLFBW-WT_EXDFEXEMPTION FROMLFBW-WT_EXDTEXEMPTION TOINOB-CUOBJInternal object numberINOB-KLARTClass typeINOB-OBTABDatabase tableINOB-OBJEKObject numberAUSP-OBJEKObject numberAUSP-ATINNInternal characteristicAUSP-KLARTClass typeAUSP-ATWRTCharacteristic valueTTXID-TDOBJECTText objectTTXID-TDIDText IDTTXIT-TDSPRASLanguage keyTTXIT-TDOBJECTText objectTTXIT-TDIDText IDTTXIT-TDTEXTShort text

Extraction Dependencies

Item #Step DescriptionTeam Responsible1Ensure Syniti has the necessary connection and access to legacy serversData2Ensure that the necessary cleansing activities in legacy sources are complete (if any)Data / Business3Ensure 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:

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
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 Responsible1LFA1 relevancy execution in SynitiData2LFB1 / LFBW / INOB / AUSP / TTXID / TTXIT relevancy execution in SynitiData3Business partner FI Vendor execution in SynitiData

Transformation Rules

Class type68/PI2/WP2OBTABObject number70/PI2/WP2OBJEKObject number71/PI2/WP2ATINNInternal characteristic72/PI2/WP2KLARTCharacteristic value74/PI2/WP2TDOBJECTText object75/PI2/WP2TDIDText ID76PI2/TTXIT

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
6	PF2/PI2/WP2	LFB1	GUZTE	Credit Memo Payment Terms	S/4HANA	LFB1	GUZTE	Credit Memo Payment Terms	Derive via Payment Terms mapping
7	PF2/PI2/WP2	LFB1	TOGRU	Tolerance Group	S/4HANA	LFB1	TOGRU	Tolerance Group	Derive via Tolerance Group 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
11	PF2/PI2/WP2	LFB1	BEGRU	Authorization Group	S/4 HANA	LFB1	BEGRU	Authorization Group	Derive via Authorization Grp mapping
12	PF2/PI2/WP2	LFB1	VZSKZ	Interest Calculation Indicator	S/4 HANA	LFB1	VZSKZ	Interest Calculation Indicator	To leave blank
13	PF2/PI2/WP2	LFB1	XVERR	Indicator: clearing between customer an vendor	S/4 HANA	LFB1	XVERR	Indicator: clearing between customer an vendor?	To leave blank
14	PF2/PI2/WP2	LFB1	ZAHLS	Block Key For Payment	S/4HANA	LFB1	ZAHLS	Block Key for Payment	Derive via Payment block mapping
15	PF2/PI2/WP2	LFB1	EIKTO	Our Account Number With Vendor	S/4HANA	LFB1	EIKTO	Our account number with Vendor	To leave blank
16	PF2/PI2/WP2	LFB1	ZSABE	Clerk at vendor	S/4HANA	LFB1	ZSABE	Clerk at vendor	To leave blank
17	PF2/PI2/WP2	LFB1	KVERM	Memo	S/4HANA	LFB1	KVERM	Memo	To leave blank
18	PF2/PI2/WP2	LFB1	FDGRV	Planning Group	S/4HANA	LFB1	FDGRV	Planning Group	Derive via Planning Group mapping
19	PF2/PI2/WP2	LFB1	BUSAB	Accounting Clerk	S/4HANA	LFB1	BUSAB	Accounting Clerk	To leave blank
20	PF2/PI2/WP2	LFB1	LNRZE	Head office account number	S/4HANA	LFB1	LNRZE	Head office account number	To leave blank
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
22	PF2/PI2/WP2	LFB1	ZINDT	Key date of the last intereste calculation	S/4 HANA	LFB1	ZINDT	Key date of the last interest calculation	To leave blank
23	PF2/PI2/WP2	LFB1	ZINRT	Interest calculation frequency in months	S/4 HANA	LFB1	ZINRT	Interest calculation frequency in months	To leave blank
24	PF2/PI2/WP2	LFB1	DATLZ	Date of the last interest calculation	S/4 HANA	LFB1	DATLZ	Date of the last interest calculation	To leave blank
25	PF2/PI2/WP2	LFB1	XDEZV	Indicator: Local Processing?	S/4HANA	LFB1	XDEZV	Indicator: Local Processing?	To leave blank
26	PF2/PI2/WP2	LFB1	WEBTR	Bill of exchange limit (in local currency)	S/4HANA	LFB1	WEBTR	Bill of exchange limit (in local currency)	To leave blank
27	PF2/PI2/WP2	LFB1	KULTG	Probable time until check is valid	S/4HANA	LFB1	KULTG	Probable time until check is valid	To leave blank
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
29	PF2/PI2/WP2	LFB1	XPORE	Indicator: Pay all items separately	S/4HANA	LFB1	XPORE	Indicator: Pay all items separately	To leave blank
30	PF2/PI2/WP2	LFB1	QSZNR	Certificate Number of the Withholding Tax Exemption	S/4HANA	LFB1	QSZNR	Certificate Number of the Withholding Tax Exemption	To leave blank
31	PF2/PI2/WP2	LFB1	QSZDT	Validity Date for Withholding Tax Exemption Certificate	S/4 HANA	LFB1	QSZDT	Validity Date for Withholding Tax Exemption Certificate	To leave blank
32	PF2/PI2/WP2	LFB1	QSSKZ	Withholding Tax Code	LFB1	QSSKZ	Withholding Tax Code	To leave blank
33	PF2/PI2/WP2	LFB1	QSREC	RECIPIENT TYPE	S/4 HANA	LFB1	QSREC	RECIPIENT TYPE	Derive via Recipient type mapping
34	PF2/PI2/WP2	LFB1	BLNKZ	Subsidy Indicator for Determining the Reduction Rates	S/4 HANA	LFB1	BLNKZ	Subsidy Indicator for Determining the Reduction Rates	To leave blank
35	PF2/PI2/WP2	LFB1	MINDK	Minority Indicators	S/4HANA	LFB1	MINDK	Minority Indicators	To leave blank
36	PF2/PI2/WP2	LFB1	ALTKN	Previous Master Record Number	S/4HANA	LFB1	ALTKN	Previous Master Record Number	Legacy vendor number LFB1-LIFNR
37	PF2/PI2/WP2	LFB1	ZGRUP	Key for Payment Grouping	S/4HANA	LFB1	ZGRUP	Key for Payment Grouping	To leave blank
38	PF2/PI2/WP2	LFB1	MGRUP	Key for Payment Grouping	S/4HANA	LFB1	MGRUP	Key for Payment Grouping	To leave blank
39	PF2/PI2/WP2	LFB1	UZAWE	Payment Method Supplement	S/4HANA	LFB1	UZAWE	Payment Method Supplement	Derive via Payment Method Supplement mapping
40	PF2/PI2/WP2	LFB1	QSBGR	Authority for Exemption from Withholding Tax	S/4HANA	LFB1	QSBGR	Authority for Exemption from Withholding Tax	To leave blank
41	PF2/PI2/WP2	LFB1	QLAND	Withholding Tax Country Key	S/4HANA	LFB1	QLAND	Withholding Tax Country Key	To leave blank
42	PF2/PI2/WP2	LFB1	XEDIP	Indicato: Send Payment Advices by EDI	S/4 HANA	LFB1	XEDIP	Indicator: Send Payment Advices by EDI	To leave blank
43	PF2/PI2/WP2	LFB1	FRGRP	Release Approval Group	S/4HANA	LFB1	FRGRP	Release Approval Group	To leave blank
44	PF2/PI2/WP2	LFB1	TLFXS	Accounting clerk's fax number at the customer/vendor	S/4HANA	LFB1	TLFXS	Accounting clerk's fax number at the customer/vendor	To leave blank
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
47	PF2/PI2/WP2	LFB1	GRIDT	Distribution Type for Employment Tax	S/4HANA	LFB1	GRIDT	Distribution Type for Employment Tax	To leave blank
48	PF2/PI2/WP2	LFB1	XAUSZ	Indicator for periodic account statements	S/4 HANA	LFB1	XAUSZ	Indicator for periodic account statements	To leave blank
49	PF2/PI2/WP2	LFB1	PERNR	Personnel Number	S/4 HANA	LFB1	PERNR	Personnel Number	To leave blank
51	PF2/PI2/WP2	LFB1	TLFNS	Accounting clerk's telephone number at business partner	S/4 HANA	LFB1	TLFNS	Accounting clerk's telephone number at business partner	To leave blank
52	PF2/PI2/WP2	LFB1	CIIUCODE	MAIN ECONOMIC ACTIVITY	S/4HANA	LFB1	CIIUCODE	MAIN ECONOMIC ACTIVITY	To leave blank
53	PF2/PI2/WP2	LFB1	CERDT	CERTIFICATION DATE	S/4HANA	LFB1	CERDT	CERTIFICATION DATE	To leave blank
54	PF2/PI2/WP2	LFB1	AVSND	SEND PAYMENT ADVICE BY XML	S/4HANA	LFB1	AVSND	SEND PAYMENT ADVICE BY XML	To leave blank
55	PF2/PI2/WP2	LFB1	PREPAY_RELEVANT	PREPAYMENT RELEVANCE	S/4HANA	LFB1	PREPAY_RELEVANT	PREPAYMENT RELEVANCE	To leave blank
56	PF2/PI2/WP2	LFBW	WITHT	WITHHOLDING TAX TYPE	S/4HANA	LFBW	WITHT	WITHHOLDING TAX TYPE	Derive from Withholding tax mapping
5759	PF2/PI2/WP2	LFBW	WT_WITHCD	WITHHOLDING TAX CODE	S/4HANA	LFBW	WT_WITHCD	WITHHOLDING TAX CODE	Derive from Withholding tax mapping
5860	PF2/PI2/WP2	LFBW	WT_SUBJCT	SUBJECT TO WITHHOLDING TAX	S/4HANA	LFBW	WT_SUBJCT	SUBJECT TO WITHHOLDING TAX	Keep legacy value
5961	PF2/PI2/WP2	LFBW	QSREC	WITHHOLDING TAX TYPE OF RECIPIENT	S/4HANA	LFBW	QSREC	WITHHOLDING TAX TYPE OF RECIPIENT	Derive from Withholding tax recipient mapping
6062	PF2/PI2/WP2	LFBW	WT_WTSTCD	WITHHOLDING TAX ID	S/4HANA	LFBW	WT_WTSTCD	WITHHOLDING TAX ID	Keep legacy value
6163	PF2/PI2/WP2	LFBW	WT_EXNR	EXEMPTION NUMBER	S/4HANA	LFBW	WT_EXNR	EXEMPTION NUMBER	Keep legacy value
6264	PF2/PI2/WP2	LFBW	WT_EXRT	EXEMPTION %	S/4HANA	LFBW	WT_EXRT	EXEMPTION %	Keep legacy value
6365	PF2/PI2/WP2	LFBW	WT_WTEXRS	EXEMPTION REASON	S/4HANA	LFBW	WT_WTEXRS	EXEMPTION REASON	Keep legacy value64
66	PF2/PI2/WP2	LFBW	WT_EXDF	EXEMPTION FROM	S/4HANA	LFBW	WT_EXDF	EXEMPTION FROM	Keep legacy value65
67	PF2/PI2/WP2	LFBW	WT_EXDT	EXEMPTION TO	S/4HANA	LFBW	WT_EXDT	EXEMPTION TO	Keep legacy value
66	PF2/PI2/WP2	INOB	CUOBJ	Internal object number	S/4HANA	INOB	CUOBJ	Internal object number	Keep legacy value
68	WP2/PF2	STXH	TDOBJECT	Text object	S4 Hana	STXH	TDOBJECT	Text object	67	PF2/PI2/WP2	INOB	KLART	Class type	S/4HANA	INOB	KLART		Keep legacy value = LFB1
69	WP2/PF2	INOB	STXH	TDNAME	Database table	S/4HANA	INOB	OBTAB	Database table	Keep legacy value	69	PF2/PI2/WP2	INOB	OBJEK	Object number	S/4HANA	INOB	OBJEK	Text Name	S4 Hana	STXH	TDNAME	Text Name	Derive via legacy to BP Master Mapping (leading zero within 10 chars) concatenate with company code mapping (4 chars)
70	WP2/PF2	STXH	TDID	Text ID	S4 Hana	STXH	TDID	Text ID	Keep legacy value
71	WP2/PF2	AUSP	STXH	TDSPRAS	Object number	S/4HANA	AUSP	OBJEK	Language Key	S4 Hana	STXH	TDSPRAS	Language Key	Keep legacy value
72	WP2/PF2	AUSP	STXL	TDOBJECT	Internal characteristic	S/4HANA	AUSP	ATINN	Text object	S4 Hana	STXH	TDOBJECT	Text object	Keep legacy value = LFB1
73	WP2/PF2	AUSP	STXL	TDNAME	Class type	S/4HANA	AUSP	KLART	Class type	Keep legacy value	73	PF2/PI2/WP2	AUSP	ATWRT	Characteristic value	S/4HANA	AUSP	ATWRT	Text Name	S4 Hana	STXL	TDNAME	Text Name	Derive via legacy to BP Master Mapping (leading zero within 10 chars) concatenate with company code mapping (4 chars)
74	WP2/PF2	STXL	TDID	Text ID	S4 Hana	STXL	TDID	Text ID	Keep legacy value
75	WP2/PF2	TTXID	STXL	TDSPRAS	Text object	S/4HANA	TTXID	TDOBJECT	Language Key	S4 Hana	STXL	TDSPRAS	Language Key	Keep legacy value
76	WP2/PF2	TTXID	STXL	CLUSTD	Text ID	S/4HANA	TTXID	TDID	Data	S4 Hana	STXL	CLUSTD	Data	Keep legacy value

1	PF2/	WP2		TDSPRAS	Language key	S/4HANA	TTXIT	TDSPRAS	Language key	Keep legacy value
77	PF2/PI2/WP2	TTXIT	TDOBJECT	Text object	S/4HANA	TTXIT	TDOBJECT	Text object	Keep legacy value
78	PF2/PI2/WP2	TTXIT	TDID	Text ID	S/4HANA	TTXIT	TDID	Text ID	Keep legacy value
N/A	N/A	N/A	S4HANA	BUT100	PARTNER	Business Partner Number	Refer to XREF of Business Partner
2	PF2/WP2	N/A	N/A	N/A	S4HANA	BUT100	RLTYP	BP Role	Default to FLVN00
3	PF2/WP2	N/A	N/A	N/A	S4HANA	BUT100	VALID_FROM	Validity Start of a BP Role	Default to 10101000000 (01.01.1900)
4	PF2/WP2	N/A	N/A	N/A	S4HANA	BUT100	VALID_TO	Validity End of a BP Role	Default to 99991231235959 (31.12.9999)	79	PF2/PI2/WP2	TTXIT	TDTEXT	Short text	S/4HANA	TTXIT	TDTEXT	Short 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 mapping	Legacy to S4House bank mapping
Tolerance Group mapping	Legacy to S4Tolerance Group mapping
Payment Method Supplement mapping	Legacy to S4 Payment Method Supplement mapping
Recipient type mapping	Legacy to S4 Recipient type mapping
Withholding tax recipient mapping	Legacy to S4 Withholding tax recipient mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Extract PF2/PI2/WP2 source tables – LFB1, LFBW, INOB, AUSP, TTXID, TTXITSTXH, STXL	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

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 recordsapproved 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 contentsrules 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 approved 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 contentsand 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.

View file

name	Source data for Supplier.xml
height	250

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

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 approved 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 approved 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 contentsand 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 contentsand 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.

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Apr 01, 2026	Actor	Type	Activity	Version
Approved	TAN-ext, Charmaine	State	changed state to Approved at 1:08 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v49
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 1:08 pm [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Mar 12, 2026
	JAIN-ext, Gaurav	State	changed expiry date to '19 Mar, 2026 01:23 pm' at 1:23 pm
	JAIN-ext, Gaurav	State	changed state to Lead Approval at 1:23 pm	v49
Tech Review	JAIN-ext, Gaurav	State	gave Syniti Team Review approval at 1:23 pm
		State	changed expiry date to '17 Mar, 2026 01:22 pm' at 1:22 pm
		State	changed state to Tech Review at 1:22 pm Changes approved as per CR0387	v49
Pending adjustment	JAIN-ext, Gaurav	State	changed state to Pending adjustment at 1:21 pm	v49

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 24

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

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