Versions Compared

Old Version 4

changes.mady.by.user CHAN-ext, Beng Chee

Saved on

compared with

New Version Current

changes.mady.by.user CHAN-ext, Beng Chee

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

Owner

CHAN-ext, Beng Chee MADHOK-ext, Jasleen CELEDONIO-ext, Arnold 

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 Intra/Intercompany Master Data Design Standard. 


The data from legacy system includes:

  1. Intercompany Vendor where Vendor Segment Class LFA1-ZZR_SEGT_ATTR is 'G' and DUNS Ultimate Statistical Code LFA1-ZZR_DUNS_STATS is 'Y2' 
  2. Intercompany Vendor where Vendor Group Key LFA1-KONZS is '0000810135'
  3. Relevancy Criteria n

The data from legacy system excludes:

  1. Intercompany Vendors blocked or marked for deletion.
  2. Purchasing organization or company code not in scope


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 Business Partner - Plants / Intercompany Suppliers master data strictly adheres to Master Data Standards as specified below.

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
000000 Business Partner - Role



GENERAL DATA - Address


BUT000NAME_ORG1BU_NAMEOR1NAMECHAR40R
BUS000FLDS ??BU_SORT1_TXTBU_SORT1_TXTSEARCH TERM 1/2CHAR20C
ADDR1_DATA ??POST_CODE2AD_PSTCD2POSTAL CODECHAR10R
ADDR1_DATA ??CITY1AD_CITY1CITYCHAR40R
ADDR1_DATA ??COUNTRY
COUNTRY

R
ADDR1_DATA ??LANGU
LANGUAGE

R
GENERAL DATA - Identification



VBUT0ID ??TYPE
ID TYPE

C
VBUT0ID ??IDNUMBER
IDENTIFICATION NUMBER

C
DFKKBPTAXNUM TAXTYPEBPTAXTYPECATEGORYCHAR4C
DFKKBPTAXNUM TAXNUMXLBPTAXNUMXLTAX NUMBERSCHAR60C
FLVN01 Vendor - Role



GENERAL DATA - Vendor General Data


LFA1KTOKKKTOKKACCOUNT GROUPCHAR4C
LFA1KUNNRKUNNRCUSTOMERCHAR10C
LFA1LTSNALTSNAVSR RELEVANTCHAR1C
LFA1WERKRWERKRPLANT RELEVANTCHAR1C
LFA1WERKSWERKS_EXTPLANTCHAR4C
PURCHASING - Purchasing Organization


PURCHASING DATA


LFM1WAERSBSTWAORDER CURRENCYCUKY5R
LFM1EIKTOEIKTO_MACC. WITH SUPPLIERCHAR12C
LFM1VSBEDVSBEDSHIPPING CONDITIONSCHAR2C
LFM1WEBREWEBREGR-BASED INV. VERIFICATIONCHAR1C
PARTNER FUNCTIONS


WYT3PARVWPARVWOACHAR2C
WYT3PARVWPARVWVNCHAR2C
WYT3PARVWPARVWPICHAR2C
ADDITIONAL PURCH. DATA


LFM2WERKSWERKS_DPLANTCHAR4C
WRF02K ??HINZE
PURCHASING DATA

C
FLVN00 FI Vendor - Role



COMPANY CODE



VENDOR: ACC. MANAGEMENT



LFB1AKONTAKONTReconciliation AcctCHAR10R
LFB1QSSKZQSSKZWithholding Tax CodeCHAR2C
VENDOR: PAYMENT TRANSACTIONS



LFB1HBKIDHBKIDHOUSE BANKCHAR5C
LFB1ZWELSDZWELSPAYMENT METHODSCHAR10C








Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
3027-001C2Intra Company - Plant Partners


3027-002C2Inter Company - Trade and Non Trade Partners
















Conversion Process

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

image-2025-6-29_22-23-22-1.pngImage Added


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

Change History
limit10

Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals