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

Compare with Current View Page History

« Previous Version 4 Next »

Status

  In Progress

Owner

CHAN-ext, Beng Chee MADHOK-ext, Jasleen 

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Business Partners - Plants / Intercompany Suppliers in S/4 HANA.


Conversion Scope

The scope of this document covers the approach for converting active Intra/Intercompany Vendors from Legacy Source Systems into Business Partners - Plants / Intercompany Suppliers in S/4HANA following the Plant_IntraInte Master Data Design Standard.


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

DCT

All active BP's in Intercompany DCT, includes

  • Plant
  • Trade partner
  • Non Trade partner

The number range for Inter-Company is external (as per in MDS) with the following prefixed

  • PLYYYY, where YYYY is plant code (Plant Partner to support stock transfer process. One record per plant)
  • ICTXXXX, where XXXX is company code (Trade Partner to support intercompany stock transfer process)
  • ICNXXXX, where XXXX is company code (Non Trade Partner to support intercompany stock transfer process)

Data collection will be prepared and there's a mapping between Syensqo entities as Vendor in WP2/PF2 and those created in BP Intercompany entities.     


S4 Hana















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
000000 Business Partner - Role



GENERAL DATA - Address


BUT000NAME_ORG1
NAME


BUS000FLDSBU_SORT1_TXT
SEARCH TERM 1/2


ADDR1_DATAPOST_CODE2
POSTAL CODE


ADDR1_DATACITY1
CITY


ADDR1_DATACOUNTRY
COUNTRY


ADDR1_DATALANGU
LANGUAGE


GENERAL DATA - Identification



VBUT0IDTYPE
ID TYPE


VBUT0IDIDNUMBER
IDENTIFICATION NUMBER


DFKKBPTAXNUM TAXTYPE
CATEGORY


DFKKBPTAXNUM TAXNUMXL
TAX NUMBERS


FLVN01 Vendor - Role



GENERAL DATA - Vendor General Data


LFA1KTOKK
ACCOUNT GROUP


LFA1KUNNR
CUSTOMER


LFA1LTSNA
VSR RELEVANT


LFA1WERKR
PLANT RELEVANT


LFA1WERKS
PLANT


PURCHASING - Purchasing Organization


PURCHASING DATA


LFM1WAERS
ORDER CURRENCY


LFM1EIKTO
ACC. WITH SUPPLIER


LFM1VSBED
SHIPPING CONDITIONS


LFM1WEBRE
GR-BASED INV. VERIFICATION


PARTNER FUNCTIONS


WYT3PARVW
OA


WYT3PARVW
VN


WYT3PARVW
PI


ADDITIONAL PURCH. DATA


LFM2WERKS
PLANT


WRF02KHINZE
PURCHASING DATA


FLVN00 FI Vendor - Role



COMPANY CODE



VENDOR: ACC. MANAGEMENT



LFB1AKONT
Reconciliation Acct


LFB1QSSKZ
Withholding Tax Code


VENDOR: PAYMENT TRANSACTIONS



LFB1HBKID
HOUSE BANK


LFB1ZWELS
PAYMENT METHODS
























Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


























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:

  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













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.

DCT Rules

Field NameField DescriptionRule












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. 4) Aug 04, 2025 09:27 CHAN-ext, Beng Chee
v. 8 Jul 22, 2025 10:10 CHAN-ext, Beng Chee
v. 7 Jul 17, 2025 15:12 CHAN-ext, Beng Chee
v. 6 Jul 09, 2025 18:23 CHAN-ext, Beng Chee
v. 5 Jul 09, 2025 18:18 CHAN-ext, Beng Chee
v. 4 Jul 09, 2025 16:44 CHAN-ext, Beng Chee
v. 3 Jul 03, 2025 09:00 CHAN-ext, Beng Chee
v. 2 Jul 03, 2025 08:55 CHAN-ext, Beng Chee
v. 1 Jun 29, 2025 17:45 CHAN-ext, Beng Chee

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels