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

Compare with Current View Page History

« Previous Version 2 Current »

Status

  In Progress

Owner
Stakeholders

Purpose

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


Conversion Scope

The scope of this document covers the approach for converting active Business Partners - Employee (BUP003) from Legacy Source Systems into S/4HANA following the Business Partners - Employee (BUP003) Master Data Design Standard.

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.

The data from legacy system includes:

The data from legacy system excludes:


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records





















Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement






















Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


























Conversion Process

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

For data that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.

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

Data Privacy and Sensitivity


Extraction

Extract data from a source into . There are 2 possibilities:

  1. The data exists. connects to the source and loads the data into . There are 3 methods:
    1. Perform full data extraction from relevant tables in the source system(s).
    2. Perform extraction through the application layer.
    3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
  2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . 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 DescriptionTeam Responsible
1Refresh LFB1 tables via Syniti (Vendor data)Data










Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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.

Business Partners - Employee (BUP003) DCT Rules

Field NameField DescriptionRule
LFB1-LIFNRVendor NumberDrop down value from LFA1-LIFNR Business Partner DCT as FI Vendor on required company code level
LFB1-BUKRSCompany CodeDrop down value from T001-BUKRS company code DCT (only with active for finance indicator)
LFB1-AKONTReconciliation AccountDrop down value from SKB1-HKONT based on BUKRS
LFB1-ZUAWASort KeyDrop down value from TZUN-ZUAWA
LFB1-ZTERMPayment TermsDrop down value. Exist as valid S4 Payment Term (T052-ZTERM where T052-KOART = Blank or ‘K’)
LFB1-GUZTECredit Memo Payment TermsDrop down value. Exist as valid S4 Payment Term (T052-ZTERM where T052-KOART = Blank or ‘K’)
LFB1-TOGRUTolerance GroupDrop down value. T043G-TOGRU based on BUKRS
LFB1-REPRFCheck Double InvoiceMark X or blank
LFB1-ZWELSPayment MethodsDrop down value. Exist as valid S4 Payment Method (T042Z-ZLSCH where T042Z-LAND1 = T001-LAND1)
LFB1-TOGRRDelivery Tolerance GroupBusiness to enter content as per data type and length permitted
LFB1-BEGRUAuthorization GroupBusiness to enter content as per data type and length permitted
LFB1-VZSKZInterest Calculation IndicatorDrop down value. T056-VZSKZ
LFB1-XVERRIndicator: clearing between customer an vendorMark X or blank
LFB1-ZAHLSBlock Key For PaymentDrop down value (T008-ZAHLS)
LFB1-EIKTOOur Account Number With VendorBusiness to enter content as per data type and length permitted
LFB1-ZSABEClerk at vendorBusiness to enter content as per data type and length permitted
LFB1-KVERMMemoBusiness to enter content as per data type and length permitted
LFB1-FDGRVPlanning GroupBusiness to enter content as per data type and length permitted
LFB1-BUSABAccounting ClerkBusiness to enter content as per data type and length permitted
LFB1-LNRZEHead office account numberBusiness to enter content as per data type and length permitted
LFB1-LNRZBAccount number of the alternative payeeBusiness to enter content as per data type and length permitted
LFB1-ZINDTKey date of the last intereste calculationBusiness to enter content as per data type and length permitted
LFB1-ZINRTInterest calculation frequency in monthsDrop down from 01 to 12
LFB1-DATLZDate of the last interest calculationBusiness to enter content as per data type and length permitted
LFB1-XDEZVIndicator: Local Processing?Business to enter content as per data type and length permitted
LFB1-WEBTRBill of exchange limit (in local currency)Business to enter content as per data type and length permitted
LFB1-KULTGProbable time until check is validBusiness to enter content as per data type and length permitted
LFB1-HBKIDShort Key for a House BankBusiness to enter content as per data type and length permitted
LFB1-XPOREIndicator: Pay all items separatelyMark X or blank
LFB1-QSZNRCertificate Number of the Withholding Tax ExemptionBusiness to enter content as per data type and length permitted
LFB1-QSZDTValidity Date for Withholding Tax Exemption CertificateBusiness to enter content as per data type and length permitted
LFB1-QSSKZWithholding Tax CodeBusiness to enter content as per data type and length permitted
LFB1-QSRECRECIPIENT TYPEBusiness to enter content as per data type and length permitted
LFB1-BLNKZSubsidy Indicator for Determining the Reduction RatesBusiness to enter content as per data type and length permitted
LFB1-LFB1-MINDKMinority IndicatorsBusiness to enter content as per data type and length permitted
LFB1-LFB1-ALTKNPrevious Master Record NumberBusiness to enter content as per data type and length permitted
LFB1-LFB1-ZGRUPKey for Payment GroupingBusiness to enter content as per data type and length permitted
LFB1-LFB1-MGRUPKey for Payment GroupingBusiness to enter content as per data type and length permitted
LFB1-LFB1-UZAWEPayment Method EupplementBusiness to enter content as per data type and length permitted
LFB1-QSBGRAuthority for Exemption from Withholding TaxBusiness to enter content as per data type and length permitted
LFB1-QLANDWithholding Tax Country KeyBusiness to enter content as per data type and length permitted
LFB1-XEDIPIndicato: Send Payment Advices by EDIBusiness to enter content as per data type and length permitted
LFB1-FRGRPRelease Approval GroupBusiness to enter content as per data type and length permitted
LFB1-TLFXSAccounting clerk's fax number at the customer/vendorBusiness to enter content as per data type and length permitted
LFB1-LFB1-INTADInternet address of partner company clerkBusiness to enter content as per data type and length permitted
LFB1-LFB1-XLFZBIndicator: Alternative payee using 49account numberBusiness to enter content as per data type and length permitted
LFB1--LFB1-GRIDTDistribution Type for Employment TaxBusiness to enter content as per data type and length permitted
LFB1-XAUSZIndicator for periodic account statementsBusiness to enter content as per data type and length permitted
LFB1-PERNRPersonnel NumberBusiness to enter content as per data type and length permitted
LFB1-NODELDeletion bock for master record (company code level)Business to enter content as per data type and length permitted
LFB1-TLFNSAccounting clerk's telephone number at business partnerBusiness to enter content as per data type and length permitted
LFB1-CIIUCODEMAIN ECONOMIC ACTIVITYBusiness to enter content as per data type and length permitted
LFB1-CERDTCERTIFICATION DATEBusiness to enter content as per data type and length permitted
LFB1-AVSNDSEND PAYMENT ADVICE BY XMLBusiness to enter content as per data type and length permitted
LFB1-PREPAY_RELEVANTPREPAYMENT RELEVANCEBusiness to enter content as per data type and length permitted
LFB1-SPERRPOSTING BLOCK SELECTED COMPANY CODEBusiness to enter content as per data type and length permitted
LFB1-LOEVMCOMPANY CODE DELETION FLAGBusiness to enter content as per data type and length permitted
LFBW-LFBW-WITHTWITHHOLDING TAX TYPEBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_WITHCDWITHHOLDING TAX CODEBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_SUBJCTSUBJECT TO WITHHOLDING TAXBusiness to enter content as per data type and length permitted
LFBW-LFBW-QSRECWITHHOLDING TAX TYPE OF RECIPIENTBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_WTSTCDWITHHOLDING TAX IDBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_EXNREXEMPTION NUMBERBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_EXRTEXEMPTION %Business to enter content as per data type and length permitted
LFBW-LFBW-WT_WTEXRSEXEMPTION REASONBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_EXDFEXEMPTION FROMBusiness to enter content as per data type and length permitted
LFBW-LFBW-WT_EXDTEXEMPTION TOBusiness to enter content as per data type and length permitted
LFB5-LFB5-MAHNADUNNING PROCEDUREBusiness to enter content as per data type and length permitted
LFB5-LFB5-MANSPDUNNING BLOCKBusiness to enter content as per data type and length permitted
LFB5-LFB5-LFRMADUNNING RECIPIENTBusiness to enter content as per data type and length permitted
LFB5-LFB5-MADAT_SCRLAST DUNNING NOTICEBusiness to enter content as per data type and length permitted
LFB5-LFB5-GMVDT_SCRDATE OF THE LEGAL DUNNING PROCEEDINGSBusiness to enter content as per data type and length permitted
CVIS_LFB5-CVIS_LFB5-MAHNS_SCRDUNNING LEVELBusiness to enter content as per data type and length permitted
LFB5--LFB5-BUSABDUNNING CLERKBusiness to enter content as per data type and length permitted
LFB5--LFB5-GMVDTDATE OF THE LEGAL DUNNING PROCEEDINGSBusiness to enter content as per data type and length permitted
BS001-BS001-KUNNRCUSTOMERBusiness to enter content as per data type and length permitted
TEXT40-TEXT40NAMEBusiness to enter content as per data type and length permitted
SPRAS-SPRASPROPOSED LANGUAGEBusiness to enter content as per data type and length permitted
CVIS_TEXTS_DYNPRO-TDID-CVIS_TEXTS_DYNPRO-TDIDTEXTSBusiness to enter content as per data type and length permitted

Extraction Dependencies

Item #Step DescriptionTeam Responsible













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:

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in
  2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #Step DescriptionTeam Responsible













Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

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













Pre-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





Load

The load process includes:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #Step DescriptionTeam Responsible













Load Phase and Dependencies

Configuration

Item #Configuration Item






Conversion Objects

Object #Preceding Object Conversion Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 2) Jul 17, 2025 13:52 TEE-ext, Paul
v. 2 Jul 14, 2025 07:50 TEE-ext, Paul
v. 1 Jul 11, 2025 10:34 TEE-ext, Paul

  • No labels