You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Purpose
The purpose of this document is to define the conversion approach to create Business Partner - Counterparty (Object 3040) in S/4 HANA.
Counterparty represents organisation or person with whom a Treasury Transaction is being entered. Counterparty is used as an object while creating Transactions/Instruments such as Money Market deals, Foreign Exchange contracts, Securities etc. in Treasury and Risk Management module of S4HANA.
It is therefore created as a Business Partner with the specific role as Counterparty - Role ID TR0150. While the General Data such as name, address, contact details, identifications and controls are created like a general BP role i.e. 000000,
This role includes general data and company code data. Genaral data is mostly same as data maintained in general role. Company code data includes Payment Instructions which identifies the house bank from which payment will be made or received, the said counterparty can be used for which product types, correpondence details derived flow
S4 HANA Treasury Business partner Master Data supports the following:
> General Role for the business partner which includes information like name, address, search term, contact details, bank details of business partner - This is already covered in MDS.3007
> The Business Partner created under MDS.3007 can be extended to Counterparty Role (TR0151). Counterparty role for the Business partner is required for creatiing financial transactions with in the Treasury module.
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:
The data from legacy system excludes:
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
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 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 |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
| 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 |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
Pre-Load Validation
Project Team
Completeness
Accuracy
Business
Completeness
Accuracy
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 |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
Load Phase and Dependencies
Configuration
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 Type | Error Description | Action Taken |
|---|
|
|
|
|
|
|
|
|
|
Post-Load Validation
Project Team
Completeness
Accuracy
Business
Completeness
Accuracy
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.
