| Status |
| ||||||
|---|---|---|---|---|---|---|---|
| Owner | Bernard Ng | ||||||
| Stakeholders |
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 , LFB5 and LFBW and match by matching LIFNR with CNV-3007 final in-scope legacy records (LFA1-LIFNR) after deduplication Extract from legacy table TTXID where TDOBJECT = LFB1is 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 classification data from AUSP, INOB, KLAH, CABN (this is likely covered in CNV-3007 so may not be required)
DCT will be required for enrichment of legacy data with new S4 data eg. tax data , texts, etc.
- all records from legacy tables STXH and STXL where TDOBJECT = LFB1
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2/PI2/WP2 |
| 53,000 | S4 | 53,000 |
Additional Information
Multi-language Requirement
N/ABased on legacy or to-be design, there may be multiple language texts (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 |
| Mandatory with mapping | ||||||
| LFB1 | AKONT | AKONT | Reconciliation Account* | CHAR | 10 | Mandatory with mapping |
| LFB1 | FDGRV | FDGRV | Planning Group | CHAR | 10 |
| Mandatory with mapping | |||||
| LFB1 | LNRZB | LNRZB | Account Number of the Alternative Payee | CHAR | 10 |
| Optional |
| LFB1 |
| ZAHLS | DZAHLS |
| Payment Block (Key) | CHAR | 1 |
| Optional with mapping | |||||
| LFB1 | ZTERM | DZTERM | Terms of Payment Key | CHAR | 4 |
| Optional with mapping |
| LFB1 |
| REPRF | REPRF | Check Double Invoice | CHAR | 1 |
| Optional | |||||
| LFB1 | ALTKN | ALTKN | Previous Account Number | CHAR | 10 |
| Optional |
| LFB1 |
| HBKID |
| HBKID | Short Key for a House Bank |
| CHAR | 4 |
| Optional |
| LFB1 |
| INTAD |
| INTAD | Clerks internet address | CHAR |
| 130 | Optional |
| LFB1 |
| QSREC |
| QSREC | Type of Recipient | CHAR | 2 |
| Optional |
| LFB1 |
| TOGRR |
| TOGRR | Tolerance Group in Invoice Verification | CHAR |
Data Cleansing
| 3 | Optional | |||||
| LFB1 | XLFZB | XLFZB | Indicator: Alternative Payee Using Account Number | CHAR | 1 | Optional |
| LFB1 | ZWELS | ZWELS | Payment Method | CHAR | 10 | Optional |
| LFB1 | QSSKZ | QSSKZ | Withholding Tax Code | CHAR | 2 | Optional |
| LFB1 | UZAWE | UZAWE | Payment Method Supplement | CHAR | 2 | Optional |
| LFBW | LIFNR | LIFNR | Vendor | CHAR | 10 | Mandatory with mapping |
| LFBW | BUKRS | BUKRS | Company code | CHAR | 4 | Mandatory with mapping |
| LFBW | WITHT | 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:
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:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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-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.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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/WP2 | LFBW | WITHT | WITHHOLDING TAX TYPE | S/4HANA | LFBW | WITHT | WITHHOLDING TAX TYPE | Derive from Withholding tax mapping |
59 | PF2/WP2 | LFBW | WT_WITHCD | WITHHOLDING TAX CODE | S/4HANA | LFBW | WT_WITHCD | WITHHOLDING TAX CODE | Derive from Withholding tax mapping |
60 | PF2/WP2 | LFBW | WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | S/4HANA | LFBW | WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | Keep legacy value |
61 | PF2/WP2 | LFBW | QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | S/4HANA | LFBW | QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | Derive from Withholding tax recipient mapping |
62 | PF2/WP2 | LFBW | WT_WTSTCD | WITHHOLDING TAX ID | S/4HANA | LFBW | WT_WTSTCD | WITHHOLDING TAX ID | Keep legacy value |
63 | PF2/WP2 | LFBW | WT_EXNR | EXEMPTION NUMBER | S/4HANA | LFBW | WT_EXNR | EXEMPTION NUMBER | Keep legacy value |
64 | PF2/WP2 | LFBW | WT_EXRT | EXEMPTION % | S/4HANA | LFBW | WT_EXRT | EXEMPTION % | Keep legacy value |
65 | PF2/WP2 | LFBW | WT_WTEXRS | EXEMPTION REASON | S/4HANA | LFBW | WT_WTEXRS | EXEMPTION REASON | Keep legacy value |
| 66 | PF2/WP2 | LFBW | WT_EXDF | EXEMPTION FROM | S/4HANA | LFBW | WT_EXDF | EXEMPTION FROM | Keep legacy value |
| 67 | PF2/WP2 | LFBW | WT_EXDT | EXEMPTION TO | S/4HANA | LFBW | WT_EXDT | EXEMPTION TO | Keep legacy value |
| 68 | WP2/PF2 | STXH | TDOBJECT | Text object | S4 Hana | STXH | TDOBJECT | Text object | Keep legacy value = LFB1 |
| 69 | WP2/PF2 | STXH | TDNAME | 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 | STXH | TDSPRAS | Language Key | S4 Hana | STXH | TDSPRAS | Language Key | Keep legacy value |
| 72 | WP2/PF2 | STXL | TDOBJECT | Text object | S4 Hana | STXH | TDOBJECT | Text object | Keep legacy value = LFB1 |
| 73 | WP2/PF2 | STXL | TDNAME | 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 | STXL | TDSPRAS | Language Key | S4 Hana | STXL | TDSPRAS | Language Key | Keep legacy value |
| 76 | WP2/PF2 | STXL | CLUSTD | Data | S4 Hana | STXL | CLUSTD | Data | Keep legacy value |
1 | PF2/WP2 | 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) |
Based on CNV-3007 relevancy rule and this CS relevancy rule
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:
- The data exists. Syniti connects to the source and loads the data into Syniti. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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
Selection Screen
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 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) |
| LFB1-AKONT | Reconciliation Account | Drop down value from SKB1-HKONT based on BUKRS |
| LFB1-ZUAWA | Sort Key | Drop down value from TZUN-ZUAWA |
| LFB1-ZTERM | Payment Terms | Drop down value. Exist as valid S4 Payment Term (T052-ZTERM where T052-KOART = Blank or ‘K’) |
| LFB1-GUZTE | Credit Memo Payment Terms | Drop down value. Exist as valid S4 Payment Term (T052-ZTERM where T052-KOART = Blank or ‘K’) |
| LFB1-TOGRU | Tolerance Group | Drop down value. T043G-TOGRU based on BUKRS |
| LFB1-REPRF | Check Double Invoice | Mark X or blank |
| LFB1-ZWELS | Payment Methods | Drop down value. Exist as valid S4 Payment Method (T042Z-ZLSCH where T042Z-LAND1 = T001-LAND1) |
| LFB1-TOGRR | Delivery Tolerance Group | Business to enter content as per data type and length permitted |
| LFB1-BEGRU | Authorization Group | Business to enter content as per data type and length permitted |
| LFB1-VZSKZ | Interest Calculation Indicator | Drop down value. T056-VZSKZ |
| LFB1-XVERR | Indicator: clearing between customer an vendor | Mark X or blank |
| LFB1-ZAHLS | Block Key For Payment | Drop down value (T008-ZAHLS) |
| LFB1-EIKTO | Our Account Number With Vendor | Business to enter content as per data type and length permitted |
| LFB1-ZSABE | Clerk at vendor | Business to enter content as per data type and length permitted |
| LFB1-KVERM | Memo | Business to enter content as per data type and length permitted |
| LFB1-FDGRV | Planning Group | Business to enter content as per data type and length permitted |
| LFB1-BUSAB | Accounting Clerk | Business to enter content as per data type and length permitted |
| LFB1-LNRZE | Head office account number | Business to enter content as per data type and length permitted |
| LFB1-LNRZB | Account number of the alternative payee | Business to enter content as per data type and length permitted |
| LFB1-ZINDT | Key date of the last intereste calculation | Business to enter content as per data type and length permitted |
| LFB1-ZINRT | Interest calculation frequency in months | Drop down from 01 to 12 |
| LFB1-DATLZ | Date of the last interest calculation | Business to enter content as per data type and length permitted |
| LFB1-XDEZV | Indicator: Local Processing? | Business to enter content as per data type and length permitted |
| LFB1-WEBTR | Bill of exchange limit (in local currency) | Business to enter content as per data type and length permitted |
| LFB1-KULTG | Probable time until check is valid | Business to enter content as per data type and length permitted |
| LFB1-HBKID | Short Key for a House Bank | Business to enter content as per data type and length permitted |
| LFB1-XPORE | Indicator: Pay all items separately | Mark X or blank |
| LFB1-QSZNR | Certificate Number of the Withholding Tax Exemption | Business to enter content as per data type and length permitted |
| LFB1-QSZDT | Validity Date for Withholding Tax Exemption Certificate | Business to enter content as per data type and length permitted |
| LFB1-QSSKZ | Withholding Tax Code | Business to enter content as per data type and length permitted |
| LFB1-QSREC | RECIPIENT TYPE | Business to enter content as per data type and length permitted |
| LFB1-BLNKZ | Subsidy Indicator for Determining the Reduction Rates | Business to enter content as per data type and length permitted |
| LFB1-MINDK | Minority Indicators | Business to enter content as per data type and length permitted |
| LFB1-ALTKN | Previous Master Record Number | Business to enter content as per data type and length permitted |
| LFB1-ZGRUP | Key for Payment Grouping | Business to enter content as per data type and length permitted |
| LFB1-MGRUP | Key for Payment Grouping | Business to enter content as per data type and length permitted |
| LFB1-UZAWE | Payment Method Eupplement | Business to enter content as per data type and length permitted |
| LFB1-QSBGR | Authority for Exemption from Withholding Tax | Business to enter content as per data type and length permitted |
| LFB1-QLAND | Withholding Tax Country Key | Business to enter content as per data type and length permitted |
| LFB1-XEDIP | Indicato: Send Payment Advices by EDI | Business to enter content as per data type and length permitted |
| LFB1-FRGRP | Release Approval Group | Business to enter content as per data type and length permitted |
| LFB1-TLFXS | Accounting clerk's fax number at the customer/vendor | Business to enter content as per data type and length permitted |
| LFB1-INTAD | Internet address of partner company clerk | Business to enter content as per data type and length permitted |
| LFB1-XLFZB | Indicator: Alternative payee using 49account number | Business to enter content as per data type and length permitted |
| LFB1-GRIDT | Distribution Type for Employment Tax | Business to enter content as per data type and length permitted |
| LFB1-XAUSZ | Indicator for periodic account statements | Business to enter content as per data type and length permitted |
| LFB1-PERNR | Personnel Number | Business to enter content as per data type and length permitted |
| LFB1-NODEL | Deletion bock for master record (company code level) | Business to enter content as per data type and length permitted |
| LFB1-TLFNS | Accounting clerk's telephone number at business partner | Business to enter content as per data type and length permitted |
| LFB1-CIIUCODE | MAIN ECONOMIC ACTIVITY | Business to enter content as per data type and length permitted |
| LFB1-CERDT | CERTIFICATION DATE | Business to enter content as per data type and length permitted |
| LFB1-AVSND | SEND PAYMENT ADVICE BY XML | Business to enter content as per data type and length permitted |
| LFB1-PREPAY_RELEVANT | PREPAYMENT RELEVANCE | Business to enter content as per data type and length permitted |
| LFB1-SPERR | POSTING BLOCK SELECTED COMPANY CODE | Business to enter content as per data type and length permitted |
| LFB1-LOEVM | COMPANY CODE DELETION FLAG | Business to enter content as per data type and length permitted |
| LFBW-WITHT | WITHHOLDING TAX TYPE | Business to enter content as per data type and length permitted |
| LFBW-WT_WITHCD | WITHHOLDING TAX CODE | Business to enter content as per data type and length permitted |
| LFBW-WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | Business to enter content as per data type and length permitted |
| LFBW-QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | Business to enter content as per data type and length permitted |
| LFBW-WT_WTSTCD | WITHHOLDING TAX ID | Business to enter content as per data type and length permitted |
| LFBW-WT_EXNR | EXEMPTION NUMBER | Business to enter content as per data type and length permitted |
| LFBW-WT_EXRT | EXEMPTION % | Business to enter content as per data type and length permitted |
| LFBW-WT_WTEXRS | EXEMPTION REASON | Business to enter content as per data type and length permitted |
| LFBW-WT_EXDF | EXEMPTION FROM | Business to enter content as per data type and length permitted |
| LFBW-WT_EXDT | EXEMPTION TO | Business to enter content as per data type and length permitted |
| LFB5-MAHNA | DUNNING PROCEDURE | Business to enter content as per data type and length permitted |
| LFB5-MANSP | DUNNING BLOCK | Business to enter content as per data type and length permitted |
| LFB5-LFRMA | DUNNING RECIPIENT | Business to enter content as per data type and length permitted |
| LFB5-MADAT_SCR | LAST DUNNING NOTICE | Business to enter content as per data type and length permitted |
| LFB5-GMVDT_SCR | DATE OF THE LEGAL DUNNING PROCEEDINGS | Business to enter content as per data type and length permitted |
| CVIS_LFB5-MAHNS_SCR | DUNNING LEVEL | Business to enter content as per data type and length permitted |
| LFB5-BUSAB | DUNNING CLERK | Business to enter content as per data type and length permitted |
| LFB5-GMVDT | DATE OF THE LEGAL DUNNING PROCEEDINGS | Business to enter content as per data type and length permitted |
| BS001-KUNNR | CUSTOMER | Business to enter content as per data type and length permitted |
| TEXT40 | NAME | Business to enter content as per data type and length permitted |
| SPRAS | PROPOSED LANGUAGE | Business to enter content as per data type and length permitted |
| CVIS_TEXTS_DYNPRO-TDID | TEXTS | Business to enter content as per data type and length permitted |
Extraction Dependencies
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.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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
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
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
LFB1
VZSKZ
Interest Calculation Indicator
13
PF2/PI2/WP2
LFB1
XVERR
Indicator: clearing between customer an vendor
S/4 HANA
LFB1
XVERR
Indicator: clearing between customer an vendor?
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
16
PF2/PI2/WP2
LFB1
ZSABE
Clerk at vendor
S/4HANA
LFB1
ZSABE
Clerk at vendor
17
PF2/PI2/WP2
LFB1
KVERM
Memo
S/4HANA
LFB1
KVERM
Memo
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
Derive via Accounting Clerk mapping
20
PF2/PI2/WP2
LFB1
LNRZE
Head office account number
S/4HANA
LFB1
LNRZE
Head office account number
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
23
PF2/PI2/WP2
LFB1
ZINRT
Interest calculation frequency in months
S/4 HANA
LFB1
ZINRT
Interest calculation frequency in months
24
PF2/PI2/WP2
LFB1
DATLZ
Date of the last interest calculation
S/4 HANA
LFB1
DATLZ
Date of the last interest calculation
25
PF2/PI2/WP2
LFB1
XDEZV
Indicator: Local Processing?
S/4HANA
LFB1
XDEZV
Indicator: Local Processing?
26
PF2/PI2/WP2
LFB1
WEBTR
Bill of exchange limit (in local currency)
S/4HANA
LFB1
WEBTR
Bill of exchange limit (in local currency)
27
PF2/PI2/WP2
LFB1
KULTG
Probable time until check is valid
S/4HANA
LFB1
KULTG
Probable time until check is valid
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
30
PF2/PI2/WP2
LFB1
QSZNR
Certificate Number of the Withholding Tax Exemption
S/4HANA
LFB1
QSZNR
Certificate Number of the Withholding Tax Exemption
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
32
PF2/PI2/WP2
LFB1
QSSKZ
Withholding Tax Code
LFB1
QSSKZ
Withholding Tax Code
33
PF2/PI2/WP2
LFB1
QSREC
RECIPIENT TYPE
S/4 HANA
LFB1
QSREC
RECIPIENT TYPE
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
35
PF2/PI2/WP2
LFB1
MINDK
Minority Indicators
S/4HANA
LFB1
MINDK
Minority Indicators
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
38
PF2/PI2/WP2
LFB1
MGRUP
Key for Payment Grouping
S/4HANA
LFB1
MGRUP
Key for Payment Grouping
39
PF2/PI2/WP2
LFB1
UZAWE
Payment Method Eupplement
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
41
PF2/PI2/WP2
LFB1
QLAND
Withholding Tax Country Key
S/4HANA
LFB1
QLAND
Withholding Tax Country Key
42
PF2/PI2/WP2
LFB1
XEDIP
Indicato: Send Payment Advices by EDI
S/4 HANA
LFB1
XEDIP
Indicator: Send Payment Advices by EDI
43
PF2/PI2/WP2
LFB1
FRGRP
Release Approval Group
S/4HANA
LFB1
FRGRP
Release Approval Group
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
45
PF2/PI2/WP2
LFB1
INTAD
Internet address of partner company clerk
S/4HANA
LFB1
INTAD
Internet address of partner company clerk
46
PF2/PI2/WP2
LFB1
XLFZB
Indicator: Alternative payee using 49account number
S/4HANA
LFB1
XLFZB
Indicator: Alternative payee using account number
47
PF2/PI2/WP2
LFB1
GRIDT
Distribution Type for Employment Tax
S/4HANA
LFB1
GRIDT
Distribution Type for Employment Tax
48
PF2/PI2/WP2
LFB1
XAUSZ
Indicator for periodic account statements
S/4 HANA
LFB1
XAUSZ
Indicator for periodic account statements
49
PF2/PI2/WP2
LFB1
PERNR
Personnel Number
S/4 HANA
LFB1
PERNR
Personnel Number
50
PF2/PI2/WP2
LFB1
NODEL
Deletion bock for master record (company code level)
LFB1
NODEL
Deletion bock for master record (company code level)
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
52
PF2/PI2/WP2
LFB1
CIIUCODE
MAIN ECONOMIC ACTIVITY
S/4HANA
LFB1
CIIUCODE
MAIN ECONOMIC ACTIVITY
53
PF2/PI2/WP2
LFB1
CERDT
CERTIFICATION DATE
S/4HANA
LFB1
CERDT
CERTIFICATION DATE
54
PF2/PI2/WP2
LFB1
AVSND
SEND PAYMENT ADVICE BY XML
S/4HANA
LFB1
AVSND
SEND PAYMENT ADVICE BY XML
55
PF2/PI2/WP2
LFB1
PREPAY_RELEVANT
PREPAYMENT RELEVANCE
S/4HANA
LFB1
PREPAY_RELEVANT
PREPAYMENT RELEVANCE
56
PF2/PI2/WP2
LFB1
SPERR
POSTING BLOCK SELECTED COMPANY CODE
S/4HANA
LFB1
SPERR
POSTING BLOCK SELECTED COMPANY CODE
Default to blank will be updated by vendor Block
57
PF2/PI2/WP2
LFB1
LOEVM
COMPANY CODE DELETION FLAG
S/4HANA
LFB1
LOEVM
COMPANY CODE DELETION FLAG
Default to blank will be updated by vendor Block
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
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
63
PF2/PI2/WP2
LFBW
WT_EXNR
EXEMPTION NUMBER
S/4HANA
LFBW
WT_EXNR
EXEMPTION NUMBER
64
PF2/PI2/WP2
LFBW
WT_EXRT
EXEMPTION %
S/4HANA
LFBW
WT_EXRT
EXEMPTION %
65
PF2/PI2/WP2
LFBW
WT_WTEXRS
EXEMPTION REASON
S/4HANA
LFBW
WT_WTEXRS
EXEMPTION REASON
66
PF2/PI2/WP2
LFBW
WT_EXDF
EXEMPTION FROM
S/4HANA
LFBW
WT_EXDF
EXEMPTION FROM
67
PF2/PI2/WP2
LFBW
WT_EXDT
EXEMPTION TO
S/4HANA
LFBW
WT_EXDT
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 | |
Accounting Clerk Mapping | Legacy to S4Accounting Clerk Mapping | |
| House bank mapping | Legacy to S4House bank mapping | |
| Tolerance Group Group mapping | Legacy to S4Tolerance Group mapping | |
| Payment Method Supplement mapping | Legacy to S4 Payment Method Supplement mapping | |
Recipient type mapping | Legacy to | S4Tolerance Group S4 Recipient type mapping |
Withholding tax recipient mapping | Legacy to S4 | Payment Method Supplement 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 and , LFBW, STXH, STXL | Data |
2 | Ensure that Business Partner – General is and COA GL accounts are loaded | Data |
23 | Ensure all vendor master data collection templates, deduplication and cleansing completeness and no errors | Data |
34 | 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 | ||||
|---|---|---|---|---|
|
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 Trial Balance Upload | 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.
- is BP Vendor General 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).
See also
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|