Status	Revision in Progress
Owner	RAYUDU-ext, Narasimha Kumar
Stakeholders

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:

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

Document Management

Legal Requirement

Special Requirements

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

KOTP100

Material/Ship-to part

x

KOTP110

Material/Ship-to party/Use

x

KOTP200

Material/Plant

x

KOTP210

Material/Plant/Storage Location

x

KOTP400

Material/Vendor

x

KOTP900

Material/Ship.type

x

KOTP910

Ship.point/Transp.Group/Ship.Condition

x

KOTP911

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

x

KOTP990

Material/Ship.type/Ship-to pt

x

KOTP991

Plant/Material/Ship-to pt

x

KOTP992

Plant/Material/Country

x

KOTP993

Plant/Material/Export

x

KOTP994

Plant/Shipping conditiion/Material/Ship-to

x

KOTP996

Plant/Material/Pack.Unit

x

Data Cleansing

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:

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

Selection Screen

Context	Selection Ref Screen	Parameter Name
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 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.
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
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.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 6)	Apr 28, 2026 09:38	VAN NIEKERK-ext, ivan	All custom Tables have been strikethrough for Mock 1 to be revisited later
v. 10	Nov 26, 2025 13:06	VAN NIEKERK-ext, ivan
v. 9	Nov 26, 2025 13:05	VAN NIEKERK-ext, ivan
v. 8	Nov 26, 2025 12:34	RAYUDU-ext, Narasimha Kumar
v. 7	Nov 24, 2025 12:46	VAN NIEKERK-ext, ivan
v. 6	Nov 24, 2025 11:44	VAN NIEKERK-ext, ivan
v. 5	Sept 19, 2025 09:38	VAN NIEKERK-ext, ivan
v. 4	Sept 18, 2025 20:43	VAN NIEKERK-ext, ivan
v. 3	Aug 03, 2025 17:26	RAYUDU-ext, Narasimha Kumar
v. 2	Aug 03, 2025 17:23	RAYUDU-ext, Narasimha Kumar

Go to Page History

Apr 28, 2026	Actor	Type	Activity	Version
Revision in Progress	VAN NIEKERK-ext, ivan	State	changed state to Revision in Progress at 9:38 am	v11
Approved	VAN NIEKERK-ext, ivan	Edit	updated the page at 9:38 am All custom Tables have been strikethrough for Mock 1 to be revisited later
Mar 17, 2026
	TAN-ext, Charmaine	State	changed state to Approved at 8:20 am (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v10
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 8:20 am [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Nov 26, 2025
	VAN NIEKERK-ext, ivan	Comment	commented 1:09 pm its only on KONDP not on the KOTP tables. the key is the condition nr.
		Comment	commented 1:07 pm Corrected
		Edit	updated the page at 1:06 pm
		Comment	commented 1:06 pm No Jira, EG mentioned he would raise a risk.

Workflow history

Space shortcuts

Page tree

CNV-1063 Packing Determination

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

→

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log