| Status | In Progress |
|---|---|
| Owner | THAGARAJ-ext, Samuel Samuel thangaraj |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create in S/4 HANA.
In SAP S/4HANA, Supplier Risk is part of Supplier Lifecycle and Performance Management (SLPM) and plays a crucial role in evaluating, monitoring, and mitigating potential risks associated with suppliers.
Here’s a detailed overview of what “Supplier Risk” covers, especially in the context of Supplier Segmentation or Qualification and what you should include in your conversion or data integration specification.
1. Risk Categories
| Risk Type | Description |
|---|---|
| Operational Risk | Disruptions in supplier operations, delivery, or production |
| Financial Risk | Supplier’s credit rating, bankruptcy risk, financial instability |
| Compliance Risk | Violations of laws, regulations, or standards (e.g., labor laws, corruption) |
| Geopolitical Risk | Country instability, sanctions, tariffs |
| Environmental/Sustainability Risk | Supplier’s environmental impact, carbon footprint |
| Cybersecurity Risk | Risk of data breaches or poor digital security practices |
| Reputational Risk | Negative publicity, brand damage |
| Supply Chain Risk | Concentration of supply, lack of alternatives |
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:
- ECC PF2
- ECCWP2
The data from legacy system excludes:
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| SAP ECC PF2( As Is) | SAP ECC Production (to be) | |||
| SAP ECC WP2 (As Is) | SAP ECC Production(to be) | |||
| Convergence(As Is) | Convergence Production(to be) | |||
Additional Information
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 |
|---|---|---|---|---|---|---|
BUT000, LFA1, LFM1, LFB1 | ||||||
BUT000, LFA1, LFM1, LFB1 | Supplier ID | BP_ID (Business Partner) | Unique ID of supplier in SAP | |||
| Risk Category | RISK_CATEGORY_ID | Financial, Operational | |||
| Risk Score | RISK_SCORE | Typically 0–100 or A/B/C |
| Reviewer | REVIEWER_ID | User or role that entered the risk data | |
|---|---|---|---|
| Risk Description | RISK_DESCRIPTION | Text explanation or reference |
| Risk Source | RISK_SOURCE | Manual, Ariba, External, Internal audit |
| Valid From / To | VALID_FROM, VALID_TO | Date fields |
| Mitigation Plan | MITIGATION_PLAN | Optional; what actions are in place |
/SRMSMC/EVAL_RESULT, /SRMSMC/SUP_EVAL | Last Reviewed Date | REVIEW_DATE | When was this risk last evaluated? |
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
Extraction
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
Extraction Run Sheet
| 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 |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team 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:
- 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
Transformation Run Sheet
| 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 |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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
| 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 Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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.