Status
Owner	THANGARAJAN-ext, Ganesan
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the data conversion approach for creating Pricing Condition Records in the SAP S/4HANA target system, as part of a Greenfield implementation.

In SAP ECC, sales pricing condition records exist as part of the pricing procedure configuration and are stored in condition tables such as KONV, A*, and related master and transactional tables. These records are used to define pricing elements such as base price, discounts, freight, and surcharges across sales documents.
 
In SAP S/4HANA, the structure and usage of pricing condition records remain largely consistent; however, data models may be simplified, and dependencies on business partners (replacing customer/vendor master records) become critical in ensuring consistency across sales and purchasing functions.
 
This conversion aims to migrate active and relevant sales pricing condition records from existing ECC systems into S/4HANA by applying required transformation logic using Syniti as the data migration and transformation platform. The converted records will be loaded into the target S/4HANA system using standard SAP mechanisms such as IDOCs, BAPIs, or direct table loads where applicable.

Conversion Scope

The scope of this document includes the end-to-end approach for:

• Extracting existing Pricing Condition Records from SAP ECC systems WP2 and PF2.
• Applying transformation and cleansing logic via Syniti to conform with the S/4HANA data model and business partner framework.
• Loading the transformed condition records into SAP S/4HANA while ensuring data integrity, correct assignment to condition types, condition tables, access sequences, and pricing procedures.

This process will support the migration of condition records such as:

• Base Price (e.g., PR00)
• Discounts (e.g., K007, K004)
• Freight and surcharges

The conversion will ensure all condition records are aligned to the new Pricing Key combinations defined for example, based on Business Partner, Material Masters and relevant Organizational Units (Sales Org, Distribution Channel, Division) as designed for the target S/4HANA landscape.

The data from legacy system includes:

1. List price at various key combinations including scale-based pricing as applicable
2. Discounts and surcharges at various key combinations
3. Freight condition records at various key combinations

The data from legacy system excludes:

1. Tax condition records that will be covered in CONV-1034 Tax condition records spec.
2. Rebate condition records that will be managed via Condition contracts set up

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	Pricing Condition Records		S/4HANA System
PF2	Pricing Condition Records		S/4HANA System

Additional Information

Multi-language Requirement

International Version	Description
C	Simplified Chinese
R	Cyrillic
K	Kanji (Japanese)
A	Arabic
3	Korean
T	Thai
H	Hangul

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KONH	KNUMH	KNUMH	Condition Record Number	CHAR	10	Mandatory (Key)
KONH	ERDAT	ERDAT	Created On	DATS	8	Optional
KONH	DATAB	DATAB	Valid From	DATS	8	Mandatory
KONH	DATBI	DATBI	Valid To	DATS	8	Mandatory
KONP	KSCHL	KSCHL	Condition Type	CHAR	4	Mandatory
KONP	KBETR	KBETR	Rate	CURR	11	Mandatory
KONP	KPEIN	KPEIN	Pricing Unit	DEC	5	Mandatory if UoM
KONP	KMEIN	KMEIN	Unit of Measure	UNIT	3	Optional
KONP	WAERS	WAERS	Currency	CUKY	5	Mandatory
KONP	KZBZG	KZBZG	Calculation Type	CHAR	1	Mandatory

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1034-001	C1	Remove obsolete condition records	Eliminate pricing condition records where the material, customer, or condition type is blocked or discontinued.	List of obsolete records	WP2/PF2
1034-002	C1	Validate Customer-Material master data	Ensure pricing condition records refer to valid and active Customer and Material master records.	List of invalid Customer Material combinations	WP2/PF2
1034-003	C1	Remove expired condition records	Delete condition records where validity end date has already passed. Exception the condition records required for open sales orders under migration scope	List of expired records	WP2/PF2
1034-004	C1	Validate mandatory fields	Check for missing mandatory fields (e.g. Condition Value, Currency, UoM, Scale data, Validity dates).	List of incomplete records	WP2/PF2
1034-005	C2	Detect duplicate condition records	Identify and flag duplicate pricing condition records for the same condition type, key combination, and validity period. This is possible as the source is from multiple systems WP2 and PF2	List of duplicate records	WP2/PF2
1034-006	C1	Validate currency consistency	Validate that the currency used in pricing conditions matches the currency allowed for the corresponding sales organization or customer master data.	List of inconsistent currency	WP2/PF2
1034-007	C2	Validate scale data	Identify and correct scale records with inconsistent or overlapping ranges (quantity/value).	List of scale issues	WP2/PF2
1034-008	C1	Validate unit of measure consistency	Validate unit of measure used in pricing conditions aligns with material master base UoM and allowed UoMs.	List of inconsistent UoM records	WP2/PF2

Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

A Target Ready Data Collection Template will be created for the required data, except for fields that need transformation as per the defined transformation rules. These templates will follow the format required by the target S/4HANA pricing configuration.

Each template corresponds to a specific condition table structure, designed to handle data based on the key combinations used for one or more condition types. You can identify the correct template based on the condition type and the relevant sales organizations or entities.

Please find the complete list of Data Collection Templates in the link attached below.

DCT-CNV-1034-Pricing Condition Records

Please note, creation of Data collection template must be aligned with pricing configurations for Condition types, Access sequence and Associated Condition Tables.  For now, the following Template is prepared based on Pricing Configurations from S/4HANA Sandbox environment.  This will be replaced once the pricing configuration is ready.

<Object> DCT Rules

Field Name	Field Description	Rule
KSCHL	Condition Type	Mandatory. Must be a valid condition type configured in S/4HANA. Use lookup list provided.
Field List Based on Chosen Access Table / Key Combination (Refer to Full Template List Above)
VKORG	Sales Organization	Mandatory. Must match valid Sales Org values in target system. Only authorized values per scope should be used.
VTWEG	Distribution Channel	Optional based on condition table. Must be valid if provided.
SPART	Division	Optional. Use only if applicable. Validate against S/4HANA master data.
KUNNR	Customer Number	Must be a valid customer number in the S/4HANA master data.
LIFNR	Vendor Number	Use only when condition type applies to vendor. Must match master data.
MATNR	Material Number	Used only for material-based pricing. Should be padded to 18 characters.
WERKS	Plant	Optional. Use only if relevant for the pricing condition.
Mandatory Fields in All DCTs
KBETR	Condition Rate	Mandatory. Should be numeric. Decimal separator should be "." (e.g., 25.50).
KONWA	Currency	Mandatory. Must be a valid ISO currency code (e.g., USD, EUR).
KPEIN	Pricing Unit	Mandatory. Must be numeric and represent number of units (e.g., 1, 1000).
KMEIN	Unit of Measure	Mandatory. Must match valid UOM from SAP (e.g., EA, KG, L).
DATAB	Valid From Date	Mandatory. Format: YYYYMMDD. Cannot be in the past or beyond system date range.
DATBI	Valid To Date	Mandatory. Format: YYYYMMDD. Must be later than Valid From date.

Extraction Dependencies

List the steps that need to occur before extraction can commence

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 Syniti Migrate 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 Syniti Migrate
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 Description	Team Responsible

Transformation Rules

The source and target tables have the same fields as listed in the key combination.  Please check the attached file for the complete source-to-target field mapping  CNV-1034-Transformation Rules

Rule #	Source system	Condition Type	Source Table	Key Combination (Fields)	Target System	Target Table	Target Condition Type	Target Description	Transformation Logic
1034-001	QF2	BOLL	A764	ALAND / LLAND / VKORG	S/4HANA	A764	BOLL
1034-002	QF2	BOLL	A110	LLAND / VKORG	S/4HANA	A110	BOLL
1034-003	QF2	CTXJ	A604	AUART_SD	S/4HANA	A604	CTXJ
1034-004	QF2	CV	A534	KUNNR / LLAND / SPART / VKBUR / VKORG / VTWEG / ZZPRODH_P3	S/4HANA	A534	CV

Transformation Mapping

Please check the attached file for the complete field to mapping table mapping CNV-1034-Transformation Rules

Field Name	Mapping Table Name	Mapping Table Description
AUART_SD	AUART	Sales Document Types
BUKRS	BUKRS	Company Code
KUNAG	KUNNR	Business Partner - Customer
KUNNR	KUNNR	Business Partner - Customer
KUNRG	KUNNR	Business Partner - Customer
KUNWE	KUNNR	Business Partner - Customer
LGORT	LGORT	Storage Location
MATKL	MATKL	Material Group
MATNR	MATNR	Material Master
PRODH	PRODH	Product Hierarchy
SPART	SPART	Division
VKBUR	VKBUR	Sales Office
VKORG	VKORG	Sales Organization
VKORGAU	VKORG	Sales Organization
VTWEG	VTWEG	Distribution Channel
WERKS	WERKS	Plant

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Configuration	Ensure necessary configurations are in place in target system and field mapping is aligned with access sequence, pricing condition types
Review Mapping Table	Ensure all the source organization units are mapped with target values
Check Values	Validate the pre-load data confirming the values are aligned with target system format and
Validate template structure and required field population	Ensure mandatory fields like VKORG, VTWEG, MATNR, KUNNR, KSCHL, valid dates are filled

Accuracy

Task	Action
Review Mapping Table	Ensure all the source organization units are mapped with target values
Check mapping rules against configuration (access sequences, condition tables)	Cross-check mapping sheet with customizing entries in V/03, V/04, V/05, V/08
Set up validation rules based on condition tables and field catalog	Use rule-based validation and lookups against master data (e.g., MARA, KNA1)
Perform format validation (date, currency, decimal separators)	Standardize format to match SAP accepted input (e.g., YYYYMMDD for dates)
Implement logic to detect duplicate condition records	Example: Run duplicate checks using key combinations (e.g., VKORG + MATNR + KUNNR)
Conduct dry runs using LTMC or BAPIs and review logs	Analyze load results and correct format or conversion errors

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
Review populated templates for missing or incorrect values	Use checklists to verify completeness and correctness before submission
Ensure all required pricing scenarios are covered	Confirm that customer/material-specific special conditions are not missed

Accuracy

Task	Action
Review condition records for duplicate or conflicting entries	Review for duplicates within key combinations (e.g., customer-material-date)
Validity Period Check	Review validity period of the condition records to ensure pricing coverage
Spot-check high-impact pricing conditions for accuracy	Validate pricing accuracy for key customers and materials

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 Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history