You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Status

  Approved

Owner
Stakeholders

Purpose

The purpose of this document is to define the conversion approach and ensure a smooth transition of rebate-related data from the legacy ECC systems into  Condition Contracts in S/4HANA, aligning with the new data structures and functional capabilities offered by the Condition Contract Management framework.

In the current ECC environment, rebate agreements are extensively utilized at both Customer and Customer-Material levels. These agreements are set up to handle a mix of rebate calculation methods, including fixed amount and percentage-based rebates, with or without scales. The analysis of extracted production data indicates a significant volume of active rebate agreements that remain operational and require migration.

In S/4HANA, rebates are represented through Condition Contracts, which offer a more streamlined and flexible framework for managing settlement processes. The target design foresees consolidating the multiple rebate agreement types currently in use into a single condition contract type, capable of covering the four key rebate scenarios. This approach will reduce complexity, standardize the rebate process, and ensure consistency across customer agreements.

Through this conversion, all open rebate agreements from ECC will be transformed into corresponding condition contracts in S/4HANA, where the selection criteria and condition types will continue to be defined at the Customer and Customer-Material levels. This setup ensures that business continuity is maintained, while also leveraging the enhanced capabilities of S/4HANA for better contract management and settlement processing.



Conversion Scope

The scope of this document covers the approach for converting active Rebate Agreements from Legacy Source Systems into S/4HANA Condition Contracts.

The data from legacy system includes:

  1. All Rebate agreements with validity date beyond go-live freeze data
  2. Rebate agreements created for the sales area in scope
  3. Rebate agreements created for the Customer and / or Material in scope
  4. Rebate agreements that are not fully settled
  5. Rebate agreements that are not deleted / cancelled

The data from legacy system excludes:

  1. All the rest that are not part of the above extraction
  2. Rebate Agreement Status is "D - Final Settlement of Agreement Already Carried Out"
  3. Rebate Validity To KONA-DATBI is greater than R4 Go-Live date
  4. Commission Condition Records will be excluded from ETL for Manual creation of Condition contracts as BAU process
  5. Royalties will be excluded from ETC for Manual creation of Condition contracts as BAU process


List of source systems and approximate number of records
SourceScope

Source Approx. No. of Records

Target SystemTarget Approx.

No. of Records

PF2Rebate Agreements28S/4HANA - ROW28
WP2Rebate Agreements18S/4HANA - ROW18
PF2Rebate Agreements15S/4HANA - China15
WP2Rebate Agreements26S/4HANA - China26
PF2Rebate Agreements34S/4HANA - CUI34
WP2Rebate Agreements58S/4HANA - CUI58

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

N/A

Special Requirements




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
Condition Contract Header
NALEGACY_NUMBERNALegacy Contract Number*Text80Required
WCOCOHCONTRACT_TYPEWCB_CONTRACT_TYPECondition Contract Type*CHAR4Required
Not RequiredNot RequiredNot RequiredSupplier as Partner of a Condition ContractText80Not Required
WCOCOHCUST_OWNERWCB_CUST_OWNERCustomer as Partner of a Condition ContractCHAR10Required
WCOCOHREFERENCEWCB_REFERENCECondition Contract: ReferenceCHAR16Required
Not RequiredNot RequiredNot RequiredCondition Contract: AssignmentText16Not Required
WCOCOHZTERMDZTERMTerms of Payment KeyCHAR4Required
Not RequiredNot RequiredNot RequiredCash (Prompt Payment) Discount DaysNumber3Not Required
Not RequiredNot RequiredNot RequiredCash Discount Percentage 1Number5,3Not Required
Not RequiredNot RequiredNot RequiredCash Discount Days 2Number3Not Required
Not RequiredNot RequiredNot RequiredCash Discount Percentage 2Number5,3Not Required
Not RequiredNot RequiredNot RequiredNet Payment Terms PeriodNumber3Not Required
WCOCOHZLSCHDZLSCHPayment MethodCHAR1Required
Not RequiredNot RequiredNot RequiredInactive CC/PartnerText80Not Required
WCOCOHDATE_FROMWCB_DATE_FROMValid FromDATS8Required
WCOCOHDATE_TOWCB_DATE_TOValid ToDATS8Required
WCOCOHEXT_NUMWCB_EXTERNAL_NUMBERExternal Document IdentifierCHAR30Required
WCOCOHCC_CURRWCB_CC_CURRCurrency of Condition ContractCUKY5Required
Not RequiredNot RequiredNot RequiredExchange RateNumber9,5Not Required
Not RequiredNot RequiredNot RequiredTranslation DateDate10Not Required
Not RequiredNot RequiredNot RequiredExchange Rate TypeText80Not Required
Not RequiredNot RequiredNot RequiredAccess TypeText80Not Required
Not RequiredNot RequiredNot RequiredPredecessor Condition ContractText10Not Required
Not RequiredNot RequiredNot RequiredCondition Contract PurposeText80Not Required
Not RequiredNot RequiredNot RequiredExternal Reference Document CategoryText80Not Required
WCOCOHEXT_REFWCB_EXTERNAL_NUMBER2External ReferenceCHAR32Required
Not RequiredNot RequiredNot RequiredBusiness TransactionText80Not Required
Not RequiredNot RequiredNot RequiredVAT Registration NumberText20Not Required
Not RequiredNot RequiredNot RequiredAmount Fields Split Criteria GroupText80Not Required
Not RequiredNot RequiredNot RequiredTax Country / RegionText80Not Required
Not RequiredNot RequiredNot RequiredProcess VariantText80Not Required
Not RequiredNot RequiredNot RequiredExternal Reference ItemNumber10Not Required
Not RequiredNot RequiredNot RequiredCC Determination Relevance in PricingText1Not Required
Not RequiredNot RequiredNot RequiredTax Reporting Country/RegionText80Not Required
Not RequiredNot RequiredNot RequiredUser StatusText80Not Required
Not RequiredNot RequiredNot RequiredCondition Contract: External PartnerText10Not Required
Not RequiredNot RequiredNot RequiredPurchasing OrganizationText80Not Required
Not RequiredNot RequiredNot RequiredPurchasing GroupText80Not Required
Not RequiredNot RequiredNot RequiredCompany CodeText80Not Required
WCOCOHVKORGVKORGSales OrganizationCHAR4Required
WCOCOHVTWEGVTWEGDistribution ChannelCHAR2Required
WCOCOHSPARTSPARTDivisionCHAR2Required
WCOCOHVKGRPVKGRPSales GroupCHAR3Required
WCOCOHVKBURVKBURSales OfficeCHAR4Required
Not RequiredNot RequiredNot RequiredExternal GuidText32Not Required
WCOCOHSETTL_CAL_FINALWB2_SETTLEMENT_CALENDARCalendar for Final SettlementCHAR2Optional
Not RequiredNot RequiredNot RequiredCalendar for Partial SettlementText80Not Required
Not RequiredNot RequiredNot RequiredAccruals Deferral CalendarText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Type SupplierText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Type CustomerText80Not Required
Not RequiredNot RequiredNot RequiredCCS: Settlement MaterialText80Not Required
Not RequiredNot RequiredNot RequiredContract Extension CalendarText80Not Required
Not RequiredNot RequiredNot RequiredPrior SupplierText80Not Required
Not RequiredNot RequiredNot RequiredCalendar for Delta SettlementText80Not Required
WCOCOHSETTL_CAL_ACCRWB2_SETTLEMENT_CALENDAR_ACCRCalendar for Delta Accruals SettlementCHAR2Optional
WCOCOHAF_GROUPWB2_AMOUNT_FIELDS_GROUPAmount Fields GroupCHAR4Required
Not RequiredNot RequiredNot RequiredSettlement Unit of MeasureText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Unit of WeightText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Unit of VolumeText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Points UnitText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Variant in Condition ContractText80Not Required
Not RequiredNot RequiredNot RequiredBusiness Volume Table GroupText80Not Required
Not RequiredNot RequiredNot RequiredWorker as Partner of Condition ContractText80Not Required
Not RequiredNot RequiredNot RequiredSettlement Type WorkerText80Not Required
Not RequiredNot RequiredNot RequiredWorker Cost CenterText80Not Required
Not RequiredNot RequiredNot RequiredData ControllerText80Not Required
Condition Structure Fields
N/ALEGACY_NUMBERN/aLegacy Contract Number*CHAR80Required
N/AORDER_KEYN/aUser-Defined Key*CHAR10Required
KONHKOTABNRKOTABNRCondition Table*CHAR3Required
KONHKVEWEKVEWECondition UsageCHAR1Required
KONHKAPPLKAPPLCondition ApplicationCHAR2Required
KONHKSCHLKSCHACondition Type*CHAR4Required
KONHDATABDATABValid-From DateDATS8Required
KONHDATBIDATBIValid To DateDATS8Required
COND_TABLEKUNNRKUNNR_VCustomer NumberCHAR10Required
COND_TABLEMATNRMATNRMaterial NumberCHAR40Optional
Not RequiredNot RequiredNot RequiredProduct HierarchyNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredVolume Rebate GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCommission GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSupplier SubrangeNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCondition GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Group HierarchyNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredShip-To PartyNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Group 1Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Group 2Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Group 3Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Group 4Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Group 5Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSales OrganizationNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredDistribution ChannelNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredDivisionNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCustomer GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCustomer Price GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial Price GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSettlement Group 1 (Purchasing)Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSupplier's Account NumberNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredPurchasing OrganizationNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredPurchasing Info Record CategoryNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredPlantNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSupplying Plant in Case of Stock TrsferNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredPrior SupplierNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaterial GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCost CenterNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCompany CodeNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredGoods SupplierNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSales GroupNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSales OfficeNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCustomer Attribute for Condition GroupsNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredSold-to PartyNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredPayerNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredBill-to PartyNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredRelease StatusNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredPricing Reference Material of Main ItemNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredProduct Hierarchy 1Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredProduct Hierarchy 2Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredProduct Hierarchy 3Not RequiredNot RequiredNot Required
Item Condition
N/ALEGACY_NUMBERN/aLegacy Contract Number*CHAR80Required
N/AORDER_KEYN/aUser-Dfnd Key*CHAR10Required
T685AKRECHKRECHCalculation TypeCHAR1Optional
KONPKBETRKBETR_KONDAmountCURR11,2Required
KONPKONWAKONWACondition Unit (Currency or Percentage)CUKY5Required
KONPKPEINKPEINPricing UnitDEC5Required
KONPKMEINKMEINUnit of MeasureUNIT3Required
T685KVEWEKVEWECondition UsageCHAR1Required
KONPKAPPLKAPPLCondition ApplicationCHAR2Required
KONPKSCHLKSCHACondition TypeCHAR4Required
KONPKONWAKONWACondition CurrencyCUKY5Optional
KONPKNOWSKNOWSScale CurrencyCUKY5Optional
KONPKONMSKONMSScale Unit of MeasureUNIT3Optional
Not RequiredNot RequiredNot RequiredNumerator For Convers.Not RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredDenom. For ConversionNot RequiredNot RequiredNot Required
KONPKZBZGKZBZGScale BasisCHAR1Optional
KONPSTFKZSTFKZScale TypeCHAR1Optional
Not RequiredNot RequiredNot Required(OBSOLETE) ReferenceNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredReferenceNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredAccrual AmountNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredTax on Sales/Purchases CodeNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredWithholding Tax CodeNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCondition Exclusion IndicatorNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredTerms of Payment KeyNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredFixed Value DateNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredCustomer NumberNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredAccount Number of SupplierNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMax. Number of OrdersNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaximum Condition Base ValueNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredMaximum Condition ValueNot RequiredNot RequiredNot Required
Not RequiredNot RequiredNot RequiredAdditional Value DaysNot RequiredNot RequiredNot Required
Condition Scale
N/ALEGACY_NUMBERN/ALegacy Contract Number*CHAR80Optional
N/AORDER_KEYN/AUser-Dfnd Key*CHAR10Optional
N/ALINE_NON/ALine Number*NUM4Optional
KONMKBETRKBETRAmount/Percentage in Case of ScaleCURR11,2Optional
KONWKSTBWKSTBWCondition Scale Basis ValueCURR15,2Optional
KONMKSTBMKSTBMCondition Scale QuantityQUAN15Optional


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System




Condition Contract Header




9066-01WP2, PF2KONAVKORGSales OrganizationS/4HANAWCOCOHVKORGSales OrganizationMAP_VKORG
9066-02WP2, PF2KONAVTWEGDistribution ChannelS/4HANAWCOCOHVTWEGDistribution ChannelMAP_VTWEG
9066-03WP2, PF2KONASPARTDivisionS/4HANAWCOCOHSPARTDivisionMAP_SPART
9066-04WP2, PF2KONAVKBURSales OfficeS/4HANAWCOCOHVKBURSales OfficeMAP_VKBUR
9066-05WP2, PF2KONAVKGRPSales GroupS/4HANAWCOCOHVKGRPSales GroupMAP_VKGRP
9066-06WP2, PF2KONAZTERNPayment TermS/4HANAWCOCOHZTERMPayment TermMAP_ZTERM
9066-07WP2, PF2KONABONEMRebate RecipientS/4HANAWCOCOHCUST_OWNERCustomer as Partner of ContractMAP_KUNNR
9066-08WP2, PF2COND_TABLESKUNNRCustomer MasterS/4HANACOND_TABLESKUNNRCustomer MasterMAP_KUNNR
9066-09WP2, PF2COND_TABLESMATNRMaterial MasterS/4HANACOND_TABLESMATNRMaterial MasterMAP_MATNR
9066-10WP2, PF2KONABOARTAgreement TypeS/4HANAWCOCOHCONTRACT_TYPEContract TypeFIXED VALUEZS01 Copy of 0S01
9066-11WP2, PF2

Fixed value "99" - External DocumentS/4HANAWCOCOHEXT_REF_CATExternal Reference Document Category
Fixed value "99" - External Document
9066-12WP2, PF2KONAKNUMHAgreement Number S/4HANAWCOCOHEXT_REFExternal Reference

9066-13WP2, PF2KONAZLSCHPayment MethodS/4HANAWCOCOHZLSCHPayment MethosMAP_ZLSCH
9066-14WP2, PF2KONADATABAgreement valid-from dateS/4HANAWCOCOHDATE_FROMValid From

9066-15WP2, PF2KONADATBIAgreement valid-to dateS/4HANAWCOCOHDATE_TOValid To

9066-16WP2, PF2KONAWAERSCurrency KeyS/4HANAWCOCOHCC_CURRCurrency of Condition Contract

9066-17WP2, PF2

Fixed Value "0S02" - Rebate BasisS/4HANAWCOCOHWB2_AMOUNT_FIELDS_GROUPAmount Fields Group
Fixed Value "0S02" - Rebate Basis
Condition Structure Fields
SELECT KNUMH, KOTABNR from KONH where KNUMA_BO = KONA-KNUMA and DATEBI  >= GO-LIVE-DATE
Prepare the following for each Record from KONH
SELECT * FROM ("KOTE" + KONH-KOTABNR) where KNUMH = KONH-KNUMH
9066-17WP2, PF2KONHKOTABNRSource Table KOTE001S/4HANAKONHKOTABNRCondition Table*MAP_KSCHL_Rebates
9066-18WP2, PF2

Fixed Value "A"S/4HANAKONHKVEWECondition Usage
Fixed Value "A"
9066-19WP2, PF2"KOTE" + KONH-KOTABNRKAPPLCondition ApplicationS/4HANAKONHKAPPLCondition Application
Expected Value "V"
9066-20WP2, PF2"KOTE" + KONH-KOTABNRKSCHLCondition Type*S/4HANAKONHKSCHLCondition Type*MAP_KSCHL_Rebates
9066-21WP2, PF2"KOTE" + KONH-KOTABNRDATABValid-From DateS/4HANAKONHDATABValid-From Date

9066-22WP2, PF2"KOTE" + KONH-KOTABNRDATBIValid To DateS/4HANAKONHDATBIValid To Date

9066-23WP2, PF2"KOTE" + KONH-KOTABNRKUNNRCustomer NumberS/4HANACOND_TABLEKUNNRCustomer Number
COND_TABLE =  MAP_KSCHL_Rebates
9066-24WP2, PF2"KOTE" + KONH-KOTABNRMATNRMaterial NumberS/4HANACOND_TABLEMATNRMaterial Number
COND_TABLE =  MAP_KSCHL_Rebates
Item Condition
SELECT KNUMH from KONH where KNUMA_BO = KONA-KNUMA and DATEBI  >= GO-LIVE-DATE
Prepare the following for each Record from KONH
SELECT * FROM KONP where KNUMH = KONH-KNUMH
9066-24WP2, PF2KONAKNUMASystemID+KNUMAS/4HANAN/ALEGACY_NUMBERLegacy Contract Number*
SystemID+KNUMA
9066-25WP2, PF2KONHKNUMHAlaternate - Running number with in KNUMA S/4HANAN/AORDER_KEYUser-Dfnd Key*

9066-26WP2, PF2

SELECT KRECH from T685A where KAPPL = 'V' and KSCHL = KOTE001-KSCHLS/4HANAT685AKRECHCalculation Type

9066-27WP2, PF2KONPKBETR
S/4HANAKONPKBETRAmount

9066-28WP2, PF2KONPKONWA
S/4HANAKONPKONWACondition Unit (Currency or Percentage)

9066-29WP2, PF2KONPKPEIN
S/4HANAKONPKPEINPricing Unit

9066-30WP2, PF2KONPKMEIN
S/4HANAKONPKMEINUnit of Measure

9066-31WP2, PF2

Fixed Value "A"S/4HANAT685KVEWECondition Usage
Fixed Value "A"
9066-32WP2, PF2KONPKAPPL
S/4HANAKONPKAPPLCondition Application

9066-33WP2, PF2KONPKSCHL
S/4HANAKONPKSCHLCondition TypeMAP_KSCHL_Rebates
9066-34WP2, PF2KONPKONWA
S/4HANAKONPKONWACondition Currency

9066-35WP2, PF2KONPKNOWS
S/4HANAKONPKNOWSScale Currency

9066-36WP2, PF2KONPKONMS
S/4HANAKONPKONMSScale Unit of Measure

9066-37WP2, PF2KONPKZBZG
S/4HANAKONPKZBZGScale Basis

9066-38WP2, PF2KONPSTFKZ
S/4HANAKONPSTFKZScale Type

Condition Scale
SELECT KNUMH from KONH where KNUMA_BO = KONA-KNUMA and DATEBI  >= GO-LIVE-DATE
SELECT * from KONM where KNUMH = KONH-KNUMH
Execute the following when no entries available in KONH
SELECT * from KONW where KNUMH = KONH-KNUMH
9066-38WP2, PF2KONAKNUMASystemID+KNUMAS/4HANAN/ALEGACY_NUMBERLegacy Contract Number*

9066-39WP2, PF2
ORDER_KEYUser-Dfnd Key from the Item ConditionsS/4HANAN/AORDER_KEYUser-Dfnd Key*

9066-40WP2, PF2
LINE_NORunning number with in KNUMA + User-Dfnd KeyS/4HANAN/ALINE_NOLine Number*

9066-41WP2, PF2KONM/KONWKBETRKONM / KNOW table based on Scale Type / when AvailableS/4HANAKONMKBETRAmount/Percentage in Case of Scale

9066-42WP2, PF2KONWKSTBW
S/4HANAKONWKSTBWCondition Scale Basis Value

9066-43WP2, PF2KONMKSTBM
S/4HANAKONMKSTBMCondition Scale Quantity



Conversion Process

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

Data is extracted from SAP ECC System WP2 and PF2, cleansed and transformed for quality and accuracy, then migrated via the Migration Cockpit into multiple SAP S/4HANA systems with dashboards ensuring visibility and control throughout the process. This process follows the ETL (Extract → Transform → Load) framework, ensuring high-quality, validated, and reconciled data is migrated smoothly from ECC to S/4HANA




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


Source System: SAP ECC WP2 and PF2.

Scope: Open rebate agreements, condition records, scales.

Extraction Logic:

  • Retrieve rebate agreements from VBO3 transactions (tables: KONA, KONH, KONP, KONW, KONM).
  • Capture validity dates, rebate basis (sales volume/turnover), and settlement statuses.
  • Include open balances and accruals that need to be carried forward.

Objective: Create a comprehensive snapshot of all open rebate agreements as of the cutover date.

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible
9066-001Confirm scope and extraction approach for each ECC source systems WP2, PF2 (direct DB or manual extract)Data Team (L2C), Data Team (Syniti)
9066-002Establish and validate Syniti connectivity to both ECC source systemsTechnical / Basis Team, Data Team (Syniti)
9066-003Perform full data extraction from relevant rebate agreements from VBO3 transactions (tables: KONA, KONH, KONP, KONW, KONM) from WP2 and PF2 SystemsData Team (Syniti)
9066-004Apply agreed Relevancy Criteria to filter only applicable Rebate agreements and rebate condition records for S/4HANA (e.g., active rebates, active condition records, valid dates, active customers/materials)Data Team (L2C), Data Team (Syniti)
9066-005In case of restricted access or connectivity issues, receive pre-extracted rebate reports/files from source system team and prepare upload file for upload via migration cockpitData Team (L2C), Data Team (Syniti)
9066-006Perform data quality checks on extracted records (e.g., missing key fields, invalid dates, incorrect formats)Data Team (L2C), Data Team (Syniti)
9066-007Review and approve extracted data sample sets from each source system before transformation beginsBusiness / Functional Team
9066-008Archive raw extracts and maintain extraction audit logs for traceabilityData Team (L2C), Data Team (Syniti) / PMO Team


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
N/A



















Data Collection Template (DCT)

Target Ready Data Collection Template can be downloaded from Migration Cockpit for Condition Contracts from target S/4HANA Fiori App.  

DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

Item #AreaStep DescriptionTeam Responsible
1Source System Availability
  • Confirm availability of ECC systems (WP2, FP2) for data extraction within agreed timelines.
  • Validate access to required environments with correct credentials, authorizations, and RFC/user permissions.
Syensqo IT
2Data Structure Alignment
  • Document and map relevant ECC rebate agreement tables (KONA, KONH, KONP).
  • Align ECC structures with S/4HANA condition contract tables (WCOCOH, KONH, KONP, KONW, KONM).
  • Identify custom fields, enhancements, and additional attributes used in business processes.
Data Team(L2C), Syniti
3Referential Integrity
  • Extract rebate agreement header, condition, and settlement-related records in sync.
  • Ensure dependent records (scales,  validity dates) are consistently captured.
Data Team(L2C), Syniti
4Extraction Methodology

Define extraction type:  Full load for open rebates at cutover.  Delta records will follow BAU Process

Syniti


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

Item #Step DescriptionTeam Responsible
1Identify target S/4HANA fields and determine applicable legacy source fields from both ECC systems WP2, PF2Functional Team (L2C)+ Data Team (L2C)
2Review Rebate types,  rebate condition types and access tables used in each ECC source systems WP2, PF2Business Team + Functional Team (L2C)
3Map legacy field values to S/4HANA target values (including field-level mapping and technical names)Data Team (L2C), Data Team (Syniti)
4Define value mapping rules for fields requiring standardization or harmonization across the two source systems WP2, PF2 (i.e., USD, US$ mapped to USD, and ZD01 and ZDISC from ECC system mapped to ZD01 etc.,Functional Team (L2C)+ Data Team (L2C)
5Identify and agree on default values where legacy data is incomplete or inconsistentBusiness Team + Functional Team (L2C)
6Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.)Data Team (Syniti), Data Team (L2C)
7Review transformation logic and mappings with Business for confirmationBusiness Team + Functional Team (L2C)
8Perform initial transformation run and generate draft target-ready datasetData Team (Syniti),
9Review draft target-ready data for structure and completenessData Team (L2C), Functional Team (L2C)
10Share transformed data with Business for Pre-load ValidationBusiness Team
11Incorporate feedback from Business and refine mappings or transformation logic as neededData Team (L2C)
12Finalize and approve transformed data as Target Ready Load FileBusiness + Functional (L2C) + Data Team (L2C)
13Handover final file to Load Team or trigger the load via Syniti Load WorkbenchData Team (Syniti), Data Load Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionMapping Table NameTransformation Logic
9066-01WP2, PF2KONAVKORGSales OrganizationS/4HANAWCOCOHVKORGSales OrganizationMAP_VKORG
9066-02WP2, PF2KONAVTWEGDistribution ChannelS/4HANAWCOCOHVTWEGDistribution ChannelMAP_VTWEG
9066-03WP2, PF2KONASPARTDivisionS/4HANAWCOCOHSPARTDivisionMAP_SPART
9066-04WP2, PF2KONAVKBURSales OfficeS/4HANAWCOCOHVKBURSales OfficeMAP_VKBUR
9066-05WP2, PF2KONAVKGRPSales GroupS/4HANAWCOCOHVKGRPSales GroupMAP_VKGRP
9066-06WP2, PF2KONAZTERNPayment TermS/4HANAWCOCOHZTERMPayment TermMAP_ZTERM
9066-07WP2, PF2KONABONEMRebate RecipientS/4HANAWCOCOHCUST_OWNERCustomer as Partner of ContractMAP_KUNNR
9066-08WP2, PF2COND_TABLESKUNNRCustomer MasterS/4HANACOND_TABLESKUNNRCustomer MasterMAP_KUNNR
9066-09WP2, PF2COND_TABLESMATNRMaterial MasterS/4HANACOND_TABLESMATNRMaterial MasterMAP_MATNR
9066-10WP2, PF2KONABOARTAgreement TypeS/4HANAWCOCOHCONTRACT_TYPEContract TypeFIXED VALUEZS01 Copy of 0S01
9066-11WP2, PF2

Fixed value "99" - External DocumentS/4HANAWCOCOHEXT_REF_CATExternal Reference Document Category
Fixed value "99" - External Document
9066-12WP2, PF2KONAKNUMHAgreement Number S/4HANAWCOCOHEXT_REFExternal Reference

9066-13WP2, PF2KONAZLSCHPayment MethodS/4HANAWCOCOHZLSCHPayment MethosMAP_ZLSCH
9066-14WP2, PF2KONADATABAgreement valid-from dateS/4HANAWCOCOHDATE_FROMValid From

9066-15WP2, PF2KONADATBIAgreement valid-to dateS/4HANAWCOCOHDATE_TOValid To

9066-16WP2, PF2KONAWAERSCurrency KeyS/4HANAWCOCOHCC_CURRCurrency of Condition Contract

9066-17WP2, PF2

Fixed Value "0S02" - Rebate BasisS/4HANAWCOCOHWB2_AMOUNT_FIELDS_GROUPAmount Fields Group
Fixed Value "0S02" - Rebate Basis


Transformation Mapping

Mapping Table NameMapping Table Description
MAP_VKORGSales Organization Mapping table
MAP_VTWEGDistribution Channel Mapping table
MAP_SPARTDivision Mapping table
MAP_VKBURSales office Mapping table
MAP_VKGRPSales Group Mapping table
MAP_ZLSCHPayment Method Mapping table
MAP_ZTERMPayment terms Mapping table
MAP_KSCHL_REBATERebate Condition Types Mapping table
MAP_KUNNRCustomer Master Mapping table
MAP_MATNRMaterial Master Mapping table

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Value Mapping Tables are completeFunctional Team (L2C) + Data Team (L2C)
2Condition Contract configuration is completeFunctional Team (L2C) + Data Team (L2C)
3Org structure configuration is completeFunctional Team (L2C) + Data Team (L2C)
4Dependent Master Data records for Customer and Material are loadedFunctional Team (L2C) + Data Team (L2C)


Pre-Load Validation

Project Team

Completeness

TaskAction
Configuration

Ensure necessary configurations are in place in target system and field mapping is aligned with Condition contract type,  access sequence, pricing condition types

Review Mapping TableEnsure all the source organization units are mapped with target values
Check ValuesValidate the pre-load data confirming the values are aligned with target system format and 
Validate template structure and required field populationEnsure mandatory fields as per the target definition table are available

Accuracy

TaskAction
Review Mapping TableEnsure all the source organization units, master data, payment term and condition type and related configurations are mapped with target values
Perform format validation (date, currency, decimal separators) Standardize format to match SAP accepted input (e.g., YYYYMMDD for dates)
Conduct dry runs using Migration Cockpit for condition contractsAnalyze load results and correct format or conversion errors

Business

Completeness

TaskAction
CompletenessReview and confirm if the extraction contain all the open rebate agreements





Accuracy

TaskAction
Review rebates for duplicate or conflicting entriesReview for duplicates within key combinations (e.g., Customer, customer-material-date)
Validity Period CheckReview validity period of the rebate agreements



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 DescriptionTeam Responsible
1Confirm readiness of final approved data sets for each ECC source system WP2 and PF2Business / Functional Team
2Validate transformation rules and mappings in Syniti toolData Team (L2C-Data)
3Generate target-ready load files based on S/4HANA condition table formatData Team (Syniti)
4Review and approve load files before executionBusiness / Functional Team
5Execute automated generation manual load files using Syniti in target structure defined for Migration Cockpit data loadData Team (Syniti)
6Load extracted data using Migration Cockpit for condition contract creationData Team (L2C)
7Extract loaded data from S/4HANA for post-load validationData Team (Syniti)
8Perform post-load data validation (compare target data with source/approved files) for all loaded condition contractsData Team (L2C-Data)
9Log and resolve any data load errors or mismatches identified during validationData Team (L2C-Data) + Functional Team
10Obtain business sign-off on successful load and validationBusiness Team
11Archive load logs, error reports, and validation results for audit/complianceData Team (L2C-Data) / Data Team (Syniti) / PMO


Load Phase and Dependencies

Configuration

Item #Configuration Item
Condition contract configurationsEnsure configurations are complete for the target system and mapping tables are updated accordingly
Condition typesEnsure the condition types are assigned with access sequence and condition tables are active for all the key combinations planned for each rebate condition type
Organization DataEnsure configurations for all the organization units involved in condition contracts are imported into the target system

Conversion Objects

Object #Preceding Object Conversion Approach
Material MasterMaterial Master Basic and Sales View
Business PartnerBusiness Partner Basic and Sales View


Error Handling

Error TypeError DescriptionAction Taken
Invalid Condition contract TypeCondition contract type not found or not configured in target S/4HANA systemValidated against configuration; corrected or replaced with valid condition contract type
Invalid Condition TypeCondition contract type not found or not configured in target S/4HANA systemValidated against configuration; corrected or replaced with valid KSCHL
Missing Key FieldsOne or more key fields (e.g., VKORG, MATNR, KUNNR) are blank or incorrectly formatted when required as per the selected Key CombinationPopulated missing values; ensured format (e.g., leading zeros for KUNNR/MATNR)
Invalid Date RangeValid From (DATAB) is after Valid To (DATBI)Corrected the date range to ensure DATAB < DATBI and in required date format
Duplicate RecordsIdentical key combinations found more than once in the load fileDuplicates removed or merged as per business rule. Aligned with Business and documented for future loads
Unmapped ValuesValues for fields like UoM (KMEIN), Currency (KONWA), etc. not mapped in SynitiUpdated mapping tables; ensured value conversion aligned with S/4HANA settings
Invalid Currency FormatIncorrect currency formatting or unsupported currency codeStandardized to valid ISO currency codes (e.g., USD, EUR, JPY)
Invalid Number FormatKBETR or KPEIN contains special characters or comma separatorsCleaned formatting; ensured decimal values used with '.' as separator
Authorization ErrorsLack of access to execute load in target client/systemRaised access request; obtained necessary authorizations
Condition Table MismatchField structure in load file doesn’t match condition table in target systemCorrected the file structure to align with condition table (A4AO, etc.)
Transformation MissRequired transformation logic not applied before loadRe-applied transformation rules and revalidated source-target mapping
Obsolete Master DataCustomer or material master data no longer exists in target systemReplaced or removed based on business input
Technical Load FailureFile not processed due to syntax/format error or system issueReviewed logs; regenerated file; re-executed load after resolving issue
Missing Condition Record DependenciesDependent records (e.g., access sequences, pricing procedures) not availableReviewed config dependencies; coordinated with config team for correction


Post-Load Validation

Project Team

Completeness

TaskAction
Execute Condition contract list report T-Code WCOCOALLRun the report transaction to review and confirm the expected condition contracts are created.
Duplicate Records checkReview the condition contract list using reference rebate agreement number (legacy rebate #) and ensure no duplicate condition contracts created
Perform technical reconciliation with database tables (e.g., KONH, KONP)Query SAP tables and match field-level values using SE16N or custom report

Accuracy

TaskAction
Compare uploaded data against source file values

Validate the post load extracted data against pre-load data to ensure

  1. Number of records loaded against load file
  2. Any mismatch in condition value, unit , validity period against each input record at the KEY combination level
  3. Ensure field by field value match across all loaded records
Review condition recordsReview the and confirm all the open and valid condition records are created under each condition contract



Business

The business team plays a vital role in validating the completeness and accuracy of data loaded into S/4HANA. Their review ensures that condition contracts, key pricing elements such as condition types, customer-material combinations, and validity dates are correctly migrated and aligned with business requirements. This validation helps identify any missing or incorrect records early, supports a smooth cutover, and ensures that rebate processes function correctly from day one in the new system.

Completeness

TaskAction
Participate in Post-Load WalkthroughsJoin scheduled validation sessions with the migration and functional teams
Review Loaded Condition contractsAccess the S/4HANA system (via transactions like WCOCO or custom reports) to view loaded condition contracts data
Check for Missing RecordsIdentify any missing condition contracts, condition records or key combinations that were expected but not loaded

Accuracy

TaskAction
Compare Against Approved Load FileCross-check data in S/4HANA against the final business-approved load file used for migration
Validate Accuracy of Converted/Transformed DataReview any transformed fields (e.g., currency conversion, unit mappings) for correctness
Log and Report DiscrepanciesUse provided discrepancy log format or defect management tool to report any findings


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

Version Published Changed By Comment
CURRENT (v. 21) Feb 26, 2026 09:31 THANGARAJAN-ext, Ganesan Remove CUI related instances
v. 42 Feb 26, 2026 07:53 THANGARAJAN-ext, Ganesan Remove CUI related instances
v. 41 Nov 24, 2025 10:21 THANGARAJAN-ext, Ganesan
v. 40 Nov 05, 2025 16:47 THANGARAJAN-ext, Ganesan
v. 39 Oct 13, 2025 12:25 THANGARAJAN-ext, Ganesan
v. 38 Oct 07, 2025 08:45 THANGARAJAN-ext, Ganesan
v. 37 Sept 12, 2025 11:41 THANGARAJAN-ext, Ganesan
v. 36 Sept 12, 2025 07:12 THANGARAJAN-ext, Ganesan
v. 35 Sept 12, 2025 06:55 THANGARAJAN-ext, Ganesan
v. 34 Sept 12, 2025 04:58 THANGARAJAN-ext, Ganesan

Go to Page History

  • No labels