Purpose

The purpose of this document is to define the conversion approach to create active Batch Search Strategies in S/4 HANA based on the Master Data Standards DD-FUN-050 Master Data Standard_1062-Batch Search Strategy
in S/4 HANA.

When entering the goods issue of a material handled in batches, you can enter * in the Batch field in order to initiate automatic batch determination. The system then uses a specific search strategy to find batches with certain characteristic values (such as status, shelf life, etc.) and suggests these batches in a list. In this list, the batches are sorted by specific criteria (sort sequence), and the characteristic values are displayed. The system suggests how to distribute the given quantity to the batches found. You can accept the system’s proposal for the goods movement or you can distribute the quantity manually.

The system can only search for batches on the basis of search strategies. Therefore, you have to define these strategies. In a search strategy, you define the values according to which the system is to find batches.

A search strategy is assigned to a strategy type. Strategy types  you can define a search strategy at various levels.For Syway we will be migrating the following strategies.

The Strategy Type has A few Key Combinations

Conversion Scope

All Active batch search strategies that are valid according to Validity dates in legacy.  

1. You choose a strategy type and a key combination. And based on this combination it will determine the table for the strategy

The data from legacy system includes depending on Key Combination:

Conversion Scope

1. You choose a strategy type and a key combination. And based on this combination it will determine the table for the strategy

The data from legacy system includesexcludes:

1. Deleted Conditions (KONDH LEEVM_KO)
2. Search Strategies which has expired (KODATBI in the Past)

The data from legacy system excludes:

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

Example of Upload Template: Source data for Condition record for batch determination (for all areas) Example

The technical design of the target for this conversion approach.

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

figure 1

Image Added

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

x designates a copy Action

O Designates copy from xref (Where legacy and Target do not keep the same Numbering use applicable cross reference table)

Note*  KOTH9xx series are as per Current "as is" Naming. As the tables are custom numbering dependant on Condition records. the "To Be" numbering may be different. Can only confirm once new condition records are created as to what the table names will be in target

 Target Config Mapping to merge the sources:

Data Cleansing

Conversion Process

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

Image Added

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

In order to migrate this object the following Dependencies should have been completed before attempting the migration

• Characteristics
• Class
• Customer
• Product

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