| Status | Tech Review of Updates |
|---|---|
| Owner | Bernard Ng |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Business Partners - Partner with Vendor Account (TR0604) in S/4 HANA.
Business Partner - Partner with Vendor Account 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 from Legacy Source Systems into S/4HANA following the Master Data Design Standard.
The data from legacy system includes:
- External vendors
- Intercompany vendors
The data from legacy system excludes:
- Blocked / marked for deletion
- Inactive vendors without transactions within 2 years
- one time vendors
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2/PI2/WP2 | External Vendors: Extract from LFB1and as determined as active based on the relevancy criteria.
| 53,000 | S4 | 53,000 |
Additional Information
Multi-language Requirement
Document Management
Legal Requirement
Special Requirements
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| No legacy cleansing | Relevancy | ||||
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in
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 LFB1 tables via Syniti (Vendor data) | Data |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| 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-LFB1-MINDK | Minority Indicators | Business to enter content as per data type and length permitted |
| LFB1-LFB1-ALTKN | Previous Master Record Number | Business to enter content as per data type and length permitted |
| LFB1-LFB1-ZGRUP | Key for Payment Grouping | Business to enter content as per data type and length permitted |
| LFB1-LFB1-MGRUP | Key for Payment Grouping | Business to enter content as per data type and length permitted |
| LFB1-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-LFB1-INTAD | Internet address of partner company clerk | Business to enter content as per data type and length permitted |
| LFB1-LFB1-XLFZB | Indicator: Alternative payee using 49account number | Business to enter content as per data type and length permitted |
| LFB1--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-LFBW-WITHT | WITHHOLDING TAX TYPE | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_WITHCD | WITHHOLDING TAX CODE | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | Business to enter content as per data type and length permitted |
| LFBW-LFBW-QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_WTSTCD | WITHHOLDING TAX ID | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_EXNR | EXEMPTION NUMBER | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_EXRT | EXEMPTION % | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_WTEXRS | EXEMPTION REASON | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_EXDF | EXEMPTION FROM | Business to enter content as per data type and length permitted |
| LFBW-LFBW-WT_EXDT | EXEMPTION TO | Business to enter content as per data type and length permitted |
| LFB5-LFB5-MAHNA | DUNNING PROCEDURE | Business to enter content as per data type and length permitted |
| LFB5-LFB5-MANSP | DUNNING BLOCK | Business to enter content as per data type and length permitted |
| LFB5-LFB5-LFRMA | DUNNING RECIPIENT | Business to enter content as per data type and length permitted |
| LFB5-LFB5-MADAT_SCR | LAST DUNNING NOTICE | Business to enter content as per data type and length permitted |
| LFB5-LFB5-GMVDT_SCR | DATE OF THE LEGAL DUNNING PROCEEDINGS | Business to enter content as per data type and length permitted |
| CVIS_LFB5-CVIS_LFB5-MAHNS_SCR | DUNNING LEVEL | Business to enter content as per data type and length permitted |
| LFB5--LFB5-BUSAB | DUNNING CLERK | Business to enter content as per data type and length permitted |
| LFB5--LFB5-GMVDT | DATE OF THE LEGAL DUNNING PROCEEDINGS | Business to enter content as per data type and length permitted |
| BS001-BS001-KUNNR | CUSTOMER | Business to enter content as per data type and length permitted |
| TEXT40-TEXT40 | NAME | Business to enter content as per data type and length permitted |
| SPRAS-SPRAS | PROPOSED LANGUAGE | Business to enter content as per data type and length permitted |
| CVIS_TEXTS_DYNPRO-TDID-CVIS_TEXTS_DYNPRO-TDID | TEXTS | Business to enter content as per data type and length permitted |
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 | Data / Business |
| 3 | Ensure that create, change and deletion of master data is freeze 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 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
- 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 | BP relevancy execution in Syniti | Data |
| 4 | 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 cross reference mapping |
2 | PF2/PI2/WP2 | LFB1 | BUKRS | Company Code | S/4HANA | BS001 | BUKRS | Company Code | Derive via legacy to Company Code mapping |
3 | PF2/PI2/WP2 | LFB1 | AKONT | Reconciliation Account | S/4HANA | LFB1 | AKONT | Reconciliation Account | |
4 | PF2/PI2/WP2 | LFB1 | ZUAWA | Sort Key | S/4HANA | LFB1 | ZUAWA | Sort Key | |
5 | PF2/PI2/WP2 | LFB1 | ZTERM | Payment Terms | S/4HANA | LFB1 | ZTERM | Payment Terms | |
6 | PF2/PI2/WP2 | LFB1 | GUZTE | Credit Memo Payment Terms | S/4HANA | LFB1 | GUZTE | Credit Memo Payment Terms | |
7 | PF2/PI2/WP2 | LFB1 | TOGRU | Tolerance Group | S/4HANA | LFB1 | TOGRU | Tolerance Group | |
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 | |
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 | Default to blank will be updated by vendor Block |
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 | |
19 | PF2/PI2/WP2 | LFB1 | LFB1-BUSAB | Accounting Clerk | S/4HANA | LFB1 | LFB1-BUSAB | Accounting Clerk | |
20 | PF2/PI2/WP2 | LFB1 | LFB1-LNRZE | Head office account number | S/4HANA | LFB1 | 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 | |
22 | PF2/PI2/WP2 | LFB1 | ZINDT | Key date of the last intereste calculation | S/4 HANA | LFB1 | ZINDT | Key date of the last intereste 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 | |
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 | LFB1-MINDK | Minority Indicators | S/4HANA | LFB1 | LFB1-MINDK | Minority Indicators | |
36 | PF2/PI2/WP2 | LFB1 | LFB1-ALTKN | Previous Master Record Number | S/4HANA | LFB1 | LFB1-ALTKN | Previous Master Record Number | |
37 | PF2/PI2/WP2 | LFB1 | LFB1-ZGRUP | Key for Payment Grouping | S/4HANA | LFB1 | LFB1-ZGRUP | Key for Payment Grouping | |
38 | PF2/PI2/WP2 | LFB1 | LFB1-MGRUP | Key for Payment Grouping | S/4HANA | LFB1 | LFB1-MGRUP | Key for Payment Grouping | |
39 | PF2/PI2/WP2 | LFB1 | LFB1-UZAWE | Payment Method Eupplement | S/4HANA | LFB1 | UZAWE | Payment Method Eupplement | |
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 | Indicato: 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 | LFB1-INTAD | Internet address of partner company clerk | S/4HANA | LFB1 | LFB1-INTAD | Internet address of partner company clerk | |
46 | PF2/PI2/WP2 | LFB1 | LFB1-XLFZB | Indicator: Alternative payee using 49account number | S/4HANA | LFB1 | LFB1-XLFZB | Indicator: Alternative payee using account number | |
47 | PF2/PI2/WP2 | LFB1- | 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 | LFBW-WITHT | WITHHOLDING TAX TYPE | S/4HANA | LFBW | LFBW-WITHT | WITHHOLDING TAX TYPE | |
59 | PF2/PI2/WP2 | LFBW | LFBW-WT_WITHCD | WITHHOLDING TAX CODE | S/4HANA | LFBW | LFBW-WT_WITHCD | WITHHOLDING TAX CODE | |
60 | PF2/PI2/WP2 | LFBW | LFBW-WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | S/4HANA | LFBW | LFBW-WT_SUBJCT | SUBJECT TO WITHHOLDING TAX | |
61 | PF2/PI2/WP2 | LFBW | LFBW-QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | S/4HANA | LFBW | LFBW-QSREC | WITHHOLDING TAX TYPE OF RECIPIENT | |
62 | PF2/PI2/WP2 | LFBW | LFBW-WT_WTSTCD | WITHHOLDING TAX ID | S/4HANA | LFBW | LFBW-WT_WTSTCD | WITHHOLDING TAX ID | |
63 | PF2/PI2/WP2 | LFBW | LFBW-WT_EXNR | EXEMPTION NUMBER | S/4HANA | LFBW | LFBW-WT_EXNR | EXEMPTION NUMBER | |
64 | PF2/PI2/WP2 | LFBW | LFBW-WT_EXRT | EXEMPTION % | S/4HANA | LFBW | LFBW-WT_EXRT | EXEMPTION % | |
65 | PF2/PI2/WP2 | LFBW | LFBW-WT_WTEXRS | EXEMPTION REASON | S/4HANA | LFBW | LFBW-WT_WTEXRS | EXEMPTION REASON | |
66 | PF2/PI2/WP2 | LFBW | LFBW-WT_EXDF | EXEMPTION FROM | S/4HANA | LFBW | LFBW-WT_EXDF | EXEMPTION FROM | |
67 | PF2/PI2/WP2 | LFBW | LFBW-WT_EXDT | EXEMPTION TO | S/4HANA | LFBW | LFBW-WT_EXDT | EXEMPTION TO | |
68 | PF2/PI2/WP2 | LFB5 | LFB5-MAHNA | DUNNING PROCEDURE | S/4HANA | LFB5 | LFB5-MAHNA | DUNNING PROCEDURE | |
69 | PF2/PI2/WP2 | LFB5 | LFB5-MANSP | DUNNING BLOCK | S/4HANA | LFB5 | LFB5-MANSP | DUNNING BLOCK | |
70 | PF2/PI2/WP2 | LFB5 | LFB5-LFRMA | DUNNING RECIPIENT | S/4HANA | LFB5 | LFB5-LFRMA | DUNNING RECIPIENT | |
71 | PF2/PI2/WP2 | LFB5 | LFB5-MADAT_SCR | LAST DUNNING NOTICE | S/4HANA | LFB5 | LFB5-MADAT_SCR | LAST DUNNING NOTICE | |
72 | PF2/PI2/WP2 | LFB5 | LFB5-GMVDT_SCR | DATE OF THE LEGAL DUNNING PROCEEDINGS | S/4HANA | LFB5 | LFB5-GMVDT_SCR | DATE OF THE LEGAL DUNNING PROCEEDINGS | |
73 | PF2/PI2/WP2 | CVIS_LFB5 | CVIS_LFB5-MAHNS_SCR | DUNNING LEVEL | S/4HANA | CVIS_LFB5 | CVIS_LFB5-MAHNS_SCR | DUNNING LEVEL | |
74 | PF2/PI2/WP2 | LFB5- | LFB5-BUSAB | DUNNING CLERK | S/4HANA | LFB5 | LFB5-BUSAB | DUNNING CLERK | |
75 | PF2/PI2/WP2 | LFB5- | LFB5-GMVDT | DATE OF THE LEGAL DUNNING PROCEEDINGS | S/4HANA | LFB5 | LFB5-GMVDT | DATE OF THE LEGAL DUNNING PROCEEDINGS | |
76 | PF2/PI2/WP2 | BS001 | BS001-KUNNR | CUSTOMER | S/4HANA | BS001-KUNNR | BS001-KUNNR | CUSTOMER | |
77 | PF2/PI2/WP2 | TEXT40 | TEXT40 | NAME | S/4HANA | TEXT40 | TEXT40 | NAME | Copy from PF2/PI2/WP2 |
78 | PF2/PI2/WP2 | SPRAS | SPRAS | PROPOSED LANGUAGE | S/4HANA | SPRAS | SPRAS | PROPOSED LANGUAGE | Copy from PF2/PI2/WP2 |
79 | PF2/PI2/WP2 | CVIS_TEXTS_DYNPRO-TDID | CVIS_TEXTS_DYNPRO-TDID | TEXTS | S/4HANA | CVIS_TEXTS_DYNPRO-TDID | CVIS_TEXTS_DYNPRO-TDID | TEXTS | Copy from PF2/PI2/WP2 |
Transformation Mapping
Mapping Table Name | Description |
Legacy Vendor-BP Master Mapping | Legacy to S4 Business Partner Vendor mapping |
Business Partner deDupe mapping (Global Data) | dedupe Golden-child (Global) mapping |
Company Code Mapping | Legacy to S4 Company Code Mapping |
Payment Terms Mapping | Legacy to S4 Payment Terms Mapping |
Payment Method Mapping | Payment Method Mapping |
Tax Category Mapping | Legacy to S4 Tax Category Mapping |
Reconciliation Account Mapping | Legacy to S4 Reconciliation Account Mapping |
Sort Key Mapping | Legacy to S4 Sort Key Mapping |
Planning Group Mapping | Legacy to S4 Planning Group Mapping |
deDupe Vendor Company Code Nominations Mapping | Golden-Child Company Code data Mapping |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Extract PF2/PI2/WP2 source tables – LFB1 | 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
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 | Load Sample Business Partners | Data |
2 | Validate sample Business Partners | Data |
3 | Load remaining Business Partners | Data |
4 | Validate data loaded for Business Partners | Data |
5 | Load Sample BP Type – Customer Contact Persons | Data |
6 | Validate sample BP Type – Customer Contact Persons | Data |
7 | Load remaining BP Type – Customer Contact Persons | Data |
8 | Validate data loaded for BP Type – Customer Contact Persons | Data |
9 | Load Sample BP Type – Vendor Contact Persons | Data |
10 | Validate sample BP Type – Vendor Contact Persons | Data |
11 | Load remaining BP Type – Vendor Contact Persons | Data |
12 | Validate data loaded for BP Type – Vendor Contact Persons | Data |
13 | Load Sample BP Type - Bank Contacts (First Name, Last Name) | Data |
14 | Validate sample BP Type - Bank Contacts (First Name, Last Name) | Data |
15 | Load remaining BP Type - Bank Contacts (First Name, Last Name) | Data |
16 | Validate data loaded for BP Type - Bank Contacts (First Name, Last Name) | Data |
17 | Load Sample BP Type – BP General, FI Customer, FI Vendor | Data |
18 | Validate sample BP Type – BP General, FI Customer, FI Vendor | Data |
19 | Load remaining BP Type – BP General, FI Customer, FI Vendor | Data |
20 | Validate data loaded for BP Type – BP General, FI Customer, FI Vendor | Data |
21 | Load Sample Vendors Default Partner | Data |
22 | Validate sample Vendors Default Partner | Data |
23 | Load remaining Vendors Default Partner | Data |
24 | Validate data loaded for Vendors Default Partner | Data |
25 | Load Sample BP - General for remaining customer roles | Data |
26 | Validate sample BP - General for remaining customer roles | Data |
27 | Load remaining BP - General for remaining customer roles | Data |
28 | Validate data loaded for BP - General for remaining customer roles | Data |
29 | Load Sample BP – Customers with Default Partner | Data |
30 | Validate sample BP – Customers with Default Partner | Data |
31 | Load remaining BP – Customers with Default Partner | Data |
32 | Validate data loaded BP – Customers with Default Partner | Data |
33 | Load Sample BP - Bank Role | Data |
34 | Validate sample BP - Bank Role | Data |
35 | Load remaining BP - Bank Role | Data |
36 | Validate data loaded BP - Bank Role | Data |
37 | Load Sample BP Relationship Contact Person to Organisation (Will create KNVK records) | Data |
38 | Validate sample BP Relationship Contact Person to Organisation (Will create KNVK records) | Data |
39 | Load remaining BP Relationship Contact Person to Organisation (Will create KNVK records) | Data |
40 | Validate data loaded for BP Relationship Contact Person to Organisation (Will create KNVK records) | Data |
41 | Load Sample BP - Carrier | Data |
42 | Validate sample BP - Carrier | Data |
43 | Load remaining BP - Carrier | Data |
44 | Validate data loaded BP - Carrier | Data |
45 | Load Sample BP - Credit Management | Data |
46 | Validate sample BP - Credit Management | Data |
47 | Load remaining BP - Credit Management | Data |
48 | Validate data loaded BP - Credit Management | Data |
49 | Load Sample BP Collections Management | Data |
50 | Validate sample BP Collections Management | Data |
51 | Load remaining BP Collections Management | Data |
52 | Validate data loaded BP Collections Management | Data |
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 | Incoterms Configuration |
5 | Plant Configuration |
6 | Confirmation Control Configuration |
7 | Payment Terms Configuration |
8 | Payment Method Configuration |
9 | Reconciliation Account Configuration |
10 | Withholding Tax Types Configuration |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| Intercompany Business Partners | |
Business Partner - Contact | |
Business Partner – General | |
GL Accounts |
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. | ||||