Status
Owner	RAYUDU-ext, Narasimha Kumar
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 conversion approach to create Packing Determination Data in S/4 HANA. following the DD-FUN-050 Master Data Stadard_1063-Packing Determination Master data design standard

We will taking on all the packing determination records from Legacy Systems for Materials in Scope as per Basic Data View,

An access sequence is assigned to the condition type. The key combinations contained in the access sequence are used for assigning the Packing instruction to characteristics combinations such as material/customer.

Conversion Scope

The data from legacy system includes:

1. We will migrate all the packing determinations from Legacy Systems for Materials in Scope as per Basic Data View, Materials without a Deletion indicator

The data from legacy system excludes:

All Condition Types with an expired Valid to Date (DATBI)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

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

This MDS will be further updated once the actual Determination Types and Key Combinations to be used by the business are known. This will thus feed into the CNV.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KOTPxxx	KSCHL	KSCHL_PV	Application	CHAR	4	Required
KOTPxxx	MATNR	MATNR	Material Number	CHAR	18
KOTPxxx	WERKS	WERKS_D	Plant for packing Instruction determination	CHAR	4	Conditional
KOTPxxx	LIFNR	LIFNR	Vendor for Packing Instruction	HAR	10	Conditional
KOTPxxx	KUNWE	PL_KUNWE	Ship-to Party or packing instruction determination	CHAR	10	Conditional
KOTPxxx	ABRVW	ABRVW	Usage Indicator	CHAR	3	Conditional
KOTPxxx	LGORT	LGORT_D	Storage Location	CHAR	4	Conditional
KOTPxxx	DATAB	KODATAB	Validity start date of the condition record	DATS	8	Required
KOTPxxx	DATBI	KODATBI	Validity end date of the condition record	DATS	8	Required
KONDP	PACKNR	PL_PACKNR_CONV	Packing Instruction	CHAR	22	Required
KONDP	PACKNR1	PL_PACKNR_CONV	Packing instruction	CHAR	22	Conditional
KONDP	PACKNR2	PL_PACKNR_CONV	Alternative Packing instruction 2	CHAR	22	Conditional
KONDP	PACKNR3	PL_PACKNR_CONV	Alternative Packing instruction 3	CHAR	22	Conditional
KONDP	PACKNR4	PL_PACKNR_CONV	Alternative Packing instruction 4	CHAR	22	Conditional

Depending On the Determination Type Various Tables and Columns Come into Scope. (See Figure1)

figure1

The following Matrix shows which fields are in scope per table:

x designates a copy Action

Note*  KOTHP9xx series are as per Current "as is" Naming. As the tables are custom numbering dependant on Config the "To Be" numbering may be different. Can only confirm once setup in target

FIELD

KAPPL

KSCHL

DATBI

DATAB

KNUMH

MATNR

KUNWE

ABRVW

WERKS

LGORT

LIFNR

VERSART

VSTEL

TRAGR

ZZVSBED

LAND1

EXPKZ

ZZUNIT

Table Name

Key Combination)

Field Description →

Application

Condition type for packing object determination

Valid To

Valid From

Cond.record no.

Material

Ship-to party for packing instruction determination

Usage Indicator

Plant

Storage Location

Vendor

Shipping Type

Shipping Point/Receiving Point

Transportation Group

Shipping Conditions

Country Key

Export Indicator

Packing Unit

KOTP001

Material

x

x

x

x

x

x

KOTP100

Material/Ship-to part

x

x

x

x

x

x

x

KOTP110

Material/Ship-to party/Use

x

x

x

x

x

x

x

x

KOTP200

Material/Plant

x

x

x

x

x

x

x

KOTP210

Material/Plant/Storage Location

x

x

x

x

x

x

x

x

KOTP400

Material/Vendor

x

x

x

x

x

x

x

KOTP900

Material/Ship.type

x

x

x

x

x

x

x

KOTP910

Ship.point/Transp.Group/Ship.Condition

x

x

x

x

x

x

x

x

KOTP911

Ship.point/Transp.Group/Ship.Condition/Ship-to party

x

x

x

x

x

x

x

x

x

KOTP990

Material/Ship.type/Ship-to pt

x

x

x

x

x

x

x

x

KOTP991

Plant/Material/Ship-to pt

x

x

x

x

x

x

x

x

KOTP992

Plant/Material/Country

x

x

x

x

x

x

x

x

KOTP993

Plant/Material/Export

x

x

x

x

x

x

x

x

KOTP994

Plant/Shipping conditiion/Material/Ship-to

x

x

x

x

x

x

x

x

x

KOTP996

Plant/Material/Pack.Unit

x

x

x

x

x

x

x

x

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
		To be Confirmed

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
	To be confrimed

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.

Context	Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Inbound	■Material/Plant/Vendor	Packing instruction applied at inbound step to store the material with packaging (received from vendor/other site, Vendor Return, GR of Production)
Inbound	■Material/Vendor	Packing instruction applied at inbound step to store the material with packaging (received from vendor/other site, Vendor Return, GR of Production)
Inbound	■Material	Packing instruction applied at inbound step to store the material with packaging (received from vendor/other site, Vendor Return, GR of Production)
Outbound	■Material/Plant/Customer	Packing instruction applied in Outbound process Repacking process can be applied in Inbound process and/or for stock in storage.
Outbound	■Material/Customer	Packing instruction applied in Outbound process Repacking process can be applied in Inbound process and/or for stock in storage.
Outbound	■Material	Packing instruction applied in Outbound process Repacking process can be applied in Inbound process and/or for stock in storage.

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

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

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

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

The following pre-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 pre-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.

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