| 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 from legacy tables LFB1, LFB5 and LFBW and match LIFNR with CNV-3007 final in-scope legacy records (LFA1-LIFNR) after deduplication
- Extract from legacy table TTXID where TDOBJECT = LFB1 and table TTXIT with same TDID field
- Exclude blocked vendors (LFB1-SPERR <> blank) and deleted vendors (LFB1-LOEVM <> blank)
- Extract classification data from table INOB where OBTAB = LFB1. If found, extract from table AUSP with similar OBJEK and KLART = 010
DCT will be required for enrichment of legacy data with new S4 data eg. tax data , texts, etc.
| 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
Based on legacy or to-be design, there may be multiple language texts or data enrichment via DCT process
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 |
| LFB1 | AKONT | AKONT | Reconciliation Account* | CHAR | 10 | Mandatory with mapping |
| LFB1 | FDGRV | FDGRV | Planning Group | CHAR | 10 | Optional |
| LFB1 | FRGRP | FRGRP | Release Group | CHAR | 4 | Optional |
| LFB1 | LNRZB | LNRZB | Account Number of the Alternative Payee | CHAR | 10 | Optional |
| LFB1 | XVERR | XVERR_LFB1 | Clearing with Customer | CHAR | 1 | Optional |
| LFB1 | ZAHLS | DZAHLS | Payment Block (Key) | CHAR | 1 | Mandatory with mapping |
| LFB1 | ZTERM | DZTERM | Terms of Payment Key | CHAR | 4 | Mandatory with mapping |
| LFB1 | GUZTE | GUZTE | Terms of Payment Key for Credit Memos | CHAR | 4 | Optional |
| LFB1 | REPRF | REPRF | Check Double Invoice | CHAR | 1 | Optional |
| LFB1 | ALTKN | ALTKN | Previous Account Number | CHAR | 10 | Optional |
| LFB1 | TOGRU | TOGRU | Tolerance Group | CHAR | 4 | Optional |
| LFB1 | EIKTO | EIKTO_K | Our Account Number with the Supplier | CHAR | 12 | Optional |
| LFB1 | BUSAB | BUSAB | Accounting Clerk | CHAR | 2 | Optional |
| LFB1 | ZSABE | DZSABE_K | Clerk at Supplier | CHAR | 15 | Optional |
| LFB1 | HBKID | WT_SUBJCT | Short Key for a House Bank | CHAR | 4 | Optional |
| LFB1 | INTAD | TDID | Clerks internet address | CHAR | 130 | Optional |
| LFB1 | QSREC | QSREC | Type of Recipient | 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 |
| LFB1 | ZWELS | ZWELS | Payment Method | CHAR | 10 | Optional |
| LFB1 | BEGRU | BEGRU | Authorization Group | CHAR | Optional | |
| LFB1 | VZSKZ | VZSKZ | Interest Calculation Indicator | CHAR | Optional | |
| LFB1 | KVERM | DATLZ | Memo | CHAR | Optional | |
| LFB1 | LNRZE | KULTG | Head office account number | CHAR | Optional | |
| LFB1 | ZINDT | XPORE | Key date of the last intereste calculation | CHAR | Optional | |
| LFB1 | ZINRT | QSZNR | Interest calculation frequency in months | CHAR | Optional | |
| LFB1 | DATLZ | QSZDT | Date of the last interest calculation | CHAR | Optional | |
| LFB1 | XDEZV | QSSKZ | Indicator: Local Processing? | CHAR | Optional | |
| LFB1 | WEBTR | QSREC | Bill of exchange limit (in local currency) | CHAR | Optional | |
| LFB1 | KULTG | BLNKZ | Probable time until check is valid | CHAR | Optional | |
| LFB1 | XPORE | ZGRUP | Indicator: Pay all items separately | CHAR | Optional | |
| LFB1 | QSZNR | MGRUP | Certificate Number of the Withholding Tax Exemption | CHAR | Optional | |
| LFB1 | QSZDT | UZAWE | Validity Date for Withholding Tax Exemption Certificate | CHAR | Optional | |
| LFB1 | QSSKZ | QSBGR | Withholding Tax Code | CHAR | Optional | |
| LFB1 | BLNKZ | XEDIP | Subsidy Indicator for Determining the Reduction Rates | CHAR | Optional | |
| LFB1 | MINDK | TLFXS | Minority Indicators | CHAR | Optional | |
| LFB1 | ZGRUP | XLFZB | Key for Payment Grouping | CHAR | Optional | |
| LFB1 | MGRUP | GRIDT | Key for Payment Grouping | CHAR | Optional | |
| LFB1 | UZAWE | XAUSZ | Payment Method Eupplement | CHAR | Optional | |
| LFB1 | QSBGR | PERNR | Authority for Exemption from Withholding Tax | CHAR | Optional | |
| LFB1 | QLAND | NODEL | Withholding Tax Country Key | CHAR | Optional | |
| LFB1 | XEDIP | TLFNS | Indicato: Send Payment Advices by EDI | CHAR | Optional | |
| LFB1 | TLFXS | CERDT | Accounting clerk's fax number at the customer/vendor | CHAR | Optional | |
| LFB1 | GRIDT | SPERR | Distribution Type for Employment Tax | CHAR | Optional | |
| LFB1 | XAUSZ | LOEVM | Indicator for periodic account statements | CHAR | Optional | |
| LFB1 | PERNR | WT_SUBJCT | Personnel Number | CHAR | Optional | |
| LFB1 | NODEL | QSREC | Deletion bock for master record (company code level) | CHAR | Optional | |
| LFB1 | TLFNS | MAHNA | Accounting clerk's telephone number at business partner | CHAR | Optional | |
| LFB1 | CIIUCODE | MANSP | MAIN ECONOMIC ACTIVITY | CHAR | Optional | |
| LFB1 | CERDT | LFRMA | CERTIFICATION DATE | CHAR | Optional | |
| LFB1 | AVSND | MADAT_SCR | SEND PAYMENT ADVICE BY XML | CHAR | Optional | |
| LFB1 | PREPAY_RELEVANT | GMVDT_SCR | PREPAYMENT RELEVANCE | CHAR | 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 | Mandatory with mapping |
| LFBW | WT_SUBJCT | WT_SUBJCT | Subject | CHAR | 1 | Optional |
| LFBW | WT_WITHCD | WT_WITHCD | Withholding Tax Code | CHAR | 2 | Mandatory with mapping |
| LFBW | WT_WTSTCD | WT_WTSTCD | Withholding Tax Identification Number | CHAR | 16 | Optional |
| LFBW | WT_EXNR | WT_EXNR | Exemption Number | CHAR | 25 | Optional |
| LFBW | WT_EXRT | WT_EXRT | Exemption Rate | DEC | 5 | Optional |
| LFBW | WT_WTEXRS | WT_WTEXRS | Exemption Reason | CHAR | 2 | Optional |
| LFBW | WT_EXDF | WT_EXDF | Exemption From | DATS | 8 | Optional |
| LFBW | WT_EXDT | WT_EXDT | Exemption To | DATS | 8 | Optional |
| INOB | CUOBJ | CUOBJ | Internal object number | CHAR | 18 | Mandatory |
| INOB | KLART | KLASSENART | Class type | CHAR | 3 | Mandatory |
| INOB | OBTAB | TABELLE | Database table | CHAR | 30 | Mandatory |
| INOB | OBJEK | CUOBN | Object number | CHAR | 90 | Mandatory |
| AUSP | OBJEK | CUOBN | Object number | CHAR | 90 | Mandatory |
| AUSP | ATINN | ATINN | Internal characteristic | CHAR | 10 | Mandatory |
| AUSP | KLART | KLASSENART | Class type | CHAR | 3 | Mandatory |
| AUSP | ATWRT | ATWRT | Characteristic value | CHAR | 70 | Mandatory |
| TTXID | TDOBJECT | TDOBJECT | Text object | CHAR | 10 | Mandatory |
| TTXID | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| TTXIT | TDSPRAS | SPRAS | Language key | CHAR | 1 | Mandatory |
| TTXIT | TDOBJECT | TDOBJECT | Text object | CHAR | 10 | Mandatory |
| TTXIT | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| TTXIT | TDTEXT | TDTEXT | Short text | CHAR | 30 | 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/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:
- 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
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 1 | Refresh LFA1 tables via Syniti (Vendor general data) | Data |
| 2 | Refresh LFB1, LFBW, INOB, AUSP, TTXID, TTXIT tables via Syniti (Vendor company data) | Data |
| 3 | Ensure DCT is collected for additional source data if any to combine with extracted source data | 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 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 | |
| LFB1-BUKRS | Company Code | |
| LFB1-AKONT | Reconciliation Account | |
| LFB1-ZUAWA | Sort Key | |
| LFB1-ZTERM | Payment Terms | |
| LFB1-GUZTE | Credit Memo Payment Terms | |
| LFB1-TOGRU | Tolerance Group | |
| LFB1-REPRF | Check Double Invoice | |
| LFB1-ZWELS | Payment Methods | |
| LFB1-TOGRR | Delivery Tolerance Group | |
| LFB1-BEGRU | Authorization Group | |
| LFB1-VZSKZ | Interest Calculation Indicator | |
| LFB1-XVERR | Indicator: clearing between customer an vendor | |
| LFB1-ZAHLS | Block Key For Payment | |
| LFB1-EIKTO | Our Account Number With Vendor | |
| LFB1-ZSABE | Clerk at vendor | |
| LFB1-KVERM | Memo | |
| LFB1-FDGRV | Planning Group | |
| LFB1-BUSAB | Accounting Clerk | |
| LFB1-LNRZE | Head office account number | |
| LFB1-LNRZB | Account number of the alternative payee | |
| LFB1-ZINDT | Key date of the last intereste calculation | |
| LFB1-ZINRT | Interest calculation frequency in months | |
| LFB1-DATLZ | Date of the last interest calculation | |
| LFB1-XDEZV | Indicator: Local Processing? | |
| LFB1-WEBTR | Bill of exchange limit (in local currency) | |
| LFB1-KULTG | Probable time until check is valid | |
| LFB1-HBKID | Short Key for a House Bank | |
| LFB1-XPORE | Indicator: Pay all items separately | |
| LFB1-QSZNR | Certificate Number of the Withholding Tax Exemption | |
| LFB1-QSZDT | Validity Date for Withholding Tax Exemption Certificate | |
| LFB1-QSSKZ | Withholding Tax Code | |
| LFB1-QSREC | RECIPIENT TYPE | |
| LFB1-BLNKZ | Subsidy Indicator for Determining the Reduction Rates | |
| LFB1-MINDK | Minority Indicators | |
| LFB1-ALTKN | Previous Master Record Number | |
| LFB1-ZGRUP | Key for Payment Grouping | |
| LFB1-MGRUP | Key for Payment Grouping | |
| LFB1-UZAWE | Payment Method Eupplement | |
| LFB1-QSBGR | Authority for Exemption from Withholding Tax | |
| LFB1-QLAND | Withholding Tax Country Key | |
| LFB1-XEDIP | Indicato: Send Payment Advices by EDI | |
| LFB1-FRGRP | Release Approval Group | |
| LFB1-TLFXS | Accounting clerk's fax number at the customer/vendor | |
| LFB1-INTAD | Internet address of partner company clerk | |
| LFB1-XLFZB | Indicator: Alternative payee using 49account number | |
| LFB1-GRIDT | Distribution Type for Employment Tax | |
| LFB1-XAUSZ | Indicator for periodic account statements | |
| LFB1-PERNR | Personnel Number | |
| LFB1-NODEL | Deletion bock for master record (company code level) | |
| LFB1-TLFNS | Accounting clerk's telephone number at business partner | |
| LFB1-CIIUCODE | MAIN ECONOMIC ACTIVITY | |
| LFB1-CERDT | CERTIFICATION DATE | |
| LFB1-AVSND | SEND PAYMENT ADVICE BY XML | |
| LFB1-PREPAY_RELEVANT | PREPAYMENT RELEVANCE | |
| LFBW-WITHT | WITHHOLDING TAX TYPE | |
| LFBW-WT_WITHCD | WITHHOLDING TAX CODE | |
| LFBW-WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | |
| LFBW-QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | |
| LFBW-WT_WTSTCD | WITHHOLDING TAX ID | |
| LFBW-WT_EXNR | EXEMPTION NUMBER | |
| LFBW-WT_EXRT | EXEMPTION % | |
| LFBW-WT_WTEXRS | EXEMPTION REASON | |
| LFBW-WT_EXDF | EXEMPTION FROM | |
| LFBW-WT_EXDT | EXEMPTION TO | |
| INOB-CUOBJ | Internal object number | |
| INOB-KLART | Class type | |
| INOB-OBTAB | Database table | |
| INOB-OBJEK | Object number | |
| AUSP-OBJEK | Object number | |
| AUSP-ATINN | Internal characteristic | |
| AUSP-KLART | Class type | |
| AUSP-ATWRT | Characteristic value | |
| TTXID-TDOBJECT | Text object | |
| TTXID-TDID | Text ID | |
| TTXIT-TDSPRAS | Language key | |
| TTXIT-TDOBJECT | Text object | |
| TTXIT-TDID | Text ID | |
| TTXIT-TDTEXT | Short text |
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 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/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 | |
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 | LFBW | WITHT | WITHHOLDING TAX TYPE | S/4HANA | LFBW | WITHT | WITHHOLDING TAX TYPE | Derive from Withholding tax mapping |
57 | PF2/PI2/WP2 | LFBW | WT_WITHCD | WITHHOLDING TAX CODE | S/4HANA | LFBW | WT_WITHCD | WITHHOLDING TAX CODE | Derive from Withholding tax mapping |
58 | PF2/PI2/WP2 | LFBW | WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | S/4HANA | LFBW | WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | |
59 | PF2/PI2/WP2 | LFBW | QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | S/4HANA | LFBW | QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | Derive from Withholding tax mapping |
60 | PF2/PI2/WP2 | LFBW | WT_WTSTCD | WITHHOLDING TAX ID | S/4HANA | LFBW | WT_WTSTCD | WITHHOLDING TAX ID | |
61 | PF2/PI2/WP2 | LFBW | WT_EXNR | EXEMPTION NUMBER | S/4HANA | LFBW | WT_EXNR | EXEMPTION NUMBER | |
62 | PF2/PI2/WP2 | LFBW | WT_EXRT | EXEMPTION % | S/4HANA | LFBW | WT_EXRT | EXEMPTION % | |
63 | PF2/PI2/WP2 | LFBW | WT_WTEXRS | EXEMPTION REASON | S/4HANA | LFBW | WT_WTEXRS | EXEMPTION REASON | |
64 | PF2/PI2/WP2 | LFBW | WT_EXDF | EXEMPTION FROM | S/4HANA | LFBW | WT_EXDF | EXEMPTION FROM | |
65 | PF2/PI2/WP2 | LFBW | WT_EXDT | EXEMPTION TO | S/4HANA | LFBW | WT_EXDT | EXEMPTION TO | |
| 66 | PF2/PI2/WP2 | INOB | CUOBJ | Internal object number | S/4HANA | INOB | CUOBJ | Internal object number | |
| 67 | PF2/PI2/WP2 | INOB | KLART | Class type | S/4HANA | INOB | KLART | Class type | |
| 68 | PF2/PI2/WP2 | INOB | OBTAB | Database table | S/4HANA | INOB | OBTAB | Database table | |
| 69 | PF2/PI2/WP2 | INOB | OBJEK | Object number | S/4HANA | INOB | OBJEK | Object number | |
| 70 | PF2/PI2/WP2 | AUSP | OBJEK | Object number | S/4HANA | AUSP | OBJEK | Object number | |
| 71 | PF2/PI2/WP2 | AUSP | ATINN | Internal characteristic | S/4HANA | AUSP | ATINN | Internal characteristic | |
| 72 | PF2/PI2/WP2 | AUSP | KLART | Class type | S/4HANA | AUSP | KLART | Class type | |
| 73 | PF2/PI2/WP2 | AUSP | ATWRT | Characteristic value | S/4HANA | AUSP | ATWRT | Characteristic value | |
| 74 | PF2/PI2/WP2 | TTXID | TDOBJECT | Text object | S/4HANA | TTXID | TDOBJECT | Text object | |
| 75 | PF2/PI2/WP2 | TTXID | TDID | Text ID | S/4HANA | TTXID | TDID | Text ID | |
| 76 | PF2/PI2/WP2 | TTXIT | TDSPRAS | Language key | S/4HANA | TTXIT | TDSPRAS | Language key | |
| 77 | PF2/PI2/WP2 | TTXIT | TDOBJECT | Text object | S/4HANA | TTXIT | TDOBJECT | Text object | |
| 78 | PF2/PI2/WP2 | TTXIT | TDID | Text ID | S/4HANA | TTXIT | TDID | Text ID | |
| 79 | PF2/PI2/WP2 | TTXIT | TDTEXT | Short text | S/4HANA | TTXIT | TDTEXT | Short text |
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 mapping | Legacy to S4Tolerance Group mapping |
| Payment Method Supplement mapping | Legacy to S4 Payment Method Supplement 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 | Data |
2 | Ensure that Business Partner – General is loaded | Data |
2 | Ensure all vendor master data collection templates, deduplication and cleansing completeness and no errors | Data |
3 | Ensure that all required Configurations are in S/4HANA | Data |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify count | Verify that the record count in the pre-load file is the same as the record count based on the approved DCT records |
Accuracy
| Task | Action |
|---|---|
Data Accuracy | Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents |
Mapping Error Reports | Verify that all necessary error reports have been validated, and that errors have been addressed. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count for External Vendor (not Key Input Supplier) | Verify that the record count in the pre-load file is the same as the record count based on the relevancy (including deduplication) results |
Verify Count for Intercompany Vendor | Verify that the record count in the pre-load file is the same as the record count based on the approved DCT records (intercompany Vendors) |
Verify Relevancy Rules | Verify that the relevancy rules were correctly applied |
Accuracy
| Task | Action |
|---|---|
Verify Data Accuracy | Verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents |
Review Error Reports | Verify that all necessary error reports have been validated, and that errors have been addressed. |
Verify Transformation Rules | Verify that the transformation rules are correct and have been carried out correctly |
Load
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.
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 required mappings are submitted and complete | Data team |
3 | Ensure Pre-load sign-offs are obtained. | Data team |
4 | Execute 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 |
|
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 (intercompany Vendors) |
Verify Count for Key Input Suppliers | Verify that the record count in the post-load file for Key Input supplier types are the same as the record count based on the approved DCT records for Key Input Suppliers |
Accuracy
| Task | Action |
|---|---|
Data Accuracy | Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents |
Error Reports | Verify that all necessary error reports have been validated, and that errors have been addressed. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count for External Vendor | Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results |
Verify Count for Intercompany Vendor | Verify that the record count in the post-load file is the same as the record count based on the approved DCT records (intercompany Vendors) |
Verify Count for Key Input Suppliers | Verify that the record count in the pre-load file for Key Input supplier types are the same as the record count based on the approved DCT records for Key Input Suppliers |
Validate Loaded Data | Validate, as per the loads files signed-off, that all records were created |
Accuracy
| Task | Action |
|---|---|
Verify Data Accuracy | Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents |
Review Error Reports | Verify that all necessary error reports have been validated, and that errors have been addressed. |
Validate Loaded Data | Validate, as per the loads files signed-off, that all records were created |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- 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
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||