You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
The purpose of this document is to define the conversion approach for loading Business Partner – Contact Person Relationships in SAP S/4HANA. In ECC, contact persons are linked to customers using contact-specific tables. In S/4HANA, contact persons are modeled as Business Partners with a relationship type (e.g., BUR001) established between them and the related organization.
The scope of this document covers the approach for converting active Contact Person Relationships from Legacy Source Systems into S/4HANA Business Partner (BP) Relationship Master Data (Type BUR001 – Contact Person).
The data from legacy system includes:
- Individuals classified as contact persons and linked to customers or vendors
- These are typically maintained in legacy systems in contact tables KNVK in ECC.
- Each contact is tied to a customer master record and plays a defined communication or business coordination role.
- Contact Person is within the migration scope
- The relationship assignment is only possible of the corresponding contact person is within the migration scope
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|
| WP2 | Customer Contact Person |
| S4 Hana ROW |
|
| PF2 | Customer Contact Person |
| S4 Hana ROW |
|
| WP2 | Customer Contact Person |
| S4 Hana China |
|
| PF2 | Customer Contact Person |
| S4 Hana China |
|
| WP2 | Customer Contact Person |
| S4 Hana CUI |
|
| PF2 | Customer Contact Person |
| S4 Hana CUI |
|
Vendor Contact Person Relationship
To be filled. XXXXX
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|
| | | | | | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The high-level process is represented by the diagram below:
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
| Req # | Requirement Description | Team Responsible |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
| Item # | Step Description | Team Responsible |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
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
| Item # | Step Description | Team Responsible |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Mapping Table Name | Mapping Table Description |
|---|
|
|
|
|
|
|
|
|
| Item # | Step Description | Team Responsible |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
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
| Item # | Step Description | Team Responsible |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
Load Phase and Dependencies
| 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 Type | Error Description | Action Taken |
|---|
|
|
|
|
|
|
|
|
|
- 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.
Workflow history
| Title |
Last Updated By |
Updated |
Status |
|
|
There are no pages at the moment.
|
