Purpose

The purpose of this document is to define the conversion approach to create 1151 Certificate Profiles in S/4 HANA.
in S/4 HANA.

Certificate Profiles are used in SAP Quality Management (QM) to control and define the certification requirements for materials and suppliers. A Certificate Profile specifies which quality certificates are required for a material, at what stage of the process they must be provided, and the specific inspection characteristics or parameters to be validated. This ensures that incoming materials or finished products meet the defined quality and regulatory standards before acceptance or shipment.

In SAP S/4HANA, the structure and usage of Certificate Profiles remain consistent with SAP ECC, generally defined by key attributes such as Material / Plant / Certificate Type. Certificate Profiles may include additional parameters such as certificate category, inspection lot linkage, and certificate relevance for procurement or production.

In SAP ECC, aside from the standard structure, Certificate Profiles may also exist with extended combinations or enhancements, for example:
    •    Profiles assigned to multiple materials or plants
    •    Custom fields defining regulatory or customer-specific certification needs
    •    Obsolete or inactive profiles that are no longer in use

Such cases must be reviewed carefully (MDS) to determine whether they remain relevant for migration.

This conversion aims to migrate active and valid Certificate Profiles from existing ECC systems into SAP S/4HANA by applying the required transformation logic using Syniti as the data migration and transformation platform. The converted records will be loaded into the target SAP S/4HANA system using standard SAP mechanisms such as BAPIs (e.g., BAPI_QM_CERTIFICATE_PROFILE_CREATE), IDOCs, or direct table loads, ensuring compliance with quality and regulatory requirements.

Conversion Scope

The scope of this document covers the approach for converting active Certificate Profiles from Legacy Source Systems into S/4HANA following the Certificate Profiles Master Data Design Standard.

The data from legacy system includes:

1. Active Certificate Profiles used within the last four (4) years in procurement. (QCVK-ERSTELDAT >= CURRENT DATE - 4)

2. Plant-specific Certificate Profiles that will be migrated to the To-Be Plant Mapping in Enterprise Structure Catalog worksheet "30. Plants"

3. Certificate Profiles referenced in active material-vendor (procurement).  Refer Material and BP-Vendor objects.

The data from legacy system excludes:

1. Certificate Profiles not used in more than four (4) years.

2. Certificate Profiles belonging to deleted plants (per To-Be Plant mapping).

3. Certificate Profiles referenced in inactive material-vendor (procurement).

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

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.

See also

Change log