Status
Owner	CHAN-ext, Beng Chee CELEDONIO-ext, Arnold
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 Vendors - Classification and Characteristic Assignment in S/4 HANA as part of the Vendor Master Data Migration in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting active Vendors - Classification and Characteristic Assignment of vendors class type 0101 from Legacy Source Systems into S/4HANA following Master Data Design Standard.

Link to MDS:

The data from legacy system includes:

Characteristics (CABN-ATNAM) assigned to Classes with the Class Type (KLAH-KLART) = 010
Status (KLAH-STATU) = 1 (Released)
Status (CABN-ATMST) = 1 (Released
Agreed list of Characteristics list with the Characteristic values will be migrated
Vendors’ relevant general data according to relevancy criteria.
Vendor classes (Reference - CNV-1139 -Vendors - Class Type 010) used by active vendors with activities based on the relevancy criteria of CNV-3007
Vendor Characteristics of class type 010 (Reference - CNV-3025 -Vendors - Characteristics of Class Type 010) used by active vendors with activities based on the relevancy criteria of CNV-3007

The data from legacy system excludes:

Characteristics for Deletion (CABN-LKENZ = "X")
Vendors blocked or marked for deletion.
Purchasing organization not in scope
Inactive vendors with no transactions based on the relevancy criteria of CNV-3007

List of source systems and approximate number of records

Source

Scope

Source Approx No. of Records

Target System

Target Approx

No. of Records

WP2 / PF2

Vendors Classification and Characteristic Assignment

AUSP: Characteristic values assigned to the objects (in this cases Business Partners) - Actual assigned values for specific objects for the vendors class type 010

60,000

S4 Hana

60,000

DCT

Vendors Classification and Characteristic Assignment will be build based on the below

Vendors are in the scope based on relevancy criteria of CNV-3007

Characteristics of a class type 010 can also be collected via DCT. An initial extract of the relevant classes will be provided in google sheet format to assist business in decision making on including any relevant classes from PF2 and WP2 as Vendor Class

Any additional characteristics of class type 010 also need to be created to support the new design may be added in the DCT.

A review and standardization will be done across all the characteristics of class type 010 in the DCT.

Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT.

Note: A full Data Construct will be created for Characteristics, as the SyWay design is changing and a complete standardization will be performed. While data may already exist, it cannot be easily transformed to align with the new SyWay data setup.

TBC

S4 Hana

TBC

Additional Information

Multi-language Requirement

Multi language is supported for Vendor Classification and Characteristics assignment. Login via a different language will have its description displayed in the logon language if the language key is maintained in the vendor classifications data.

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

MDS Rules and Google Drive path for the MDS - DD-FUN-050 Master Data Standard_3XXX_Consolidated-Business Partners.xlsx - Google Sheets

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
AUSP	OBJEK	OBJEK	Object to be classified	CHAR	90	R
AUSP	ATINN	ATINN	Internal char no.	NUMC	10	R
AUSP	ATZHL	ATZHL	Int counter	NUMC	3	S
AUSP	MAFID	MAFID	Indicator: Object/Class	CHAR	1	R
AUSP	KLART	KLART	Class Type	CHAR	3	R
AUSP	ADZHL	ADZHL	Int. counter	NUMC	4	S
AUSP	ATWRT	ATWRT	Characteristic Value	CHAR	70	C
AUSP	ATFLV	ATFLV	Value from	NUMC	10	S
AUSP	ATAWE	ATAWE	Internal UoM	CHAR	3	C
AUSP	ATFLB	ATFLB	Value to	NUMC	10	S
AUSP	ATAW1	ATAW1	Internal UoM	CHAR	3	C
AUSP	ATCOD	ATCOD	Code	CHAR	1	C
AUSP	ATTLV	ATTLV	Tolerance from	NUMC	10	C
AUSP	ATTLB	ATTLB	Tolerance to	NUMC	10	C
AUSP	ATPRZ	ATPRZ	Percentage	CHAR	1	C
AUSP	ATINC	ATINC	Increment	NUMC	10	C
AUSP	ATAUT	ATAUT	Authorization Group	CHAR	1	C
AUSP	AENNR	AENNR	Change Number	CHAR	12	C
AUSP	DATUV	DATUV	Valid From	DATS	8	C
AUSP	LKENZ	LKENZ	Deletion indicator	CHAR	1	C
AUSP	ATIMB	ATIMB	Characteristic number	NUMC	10	C
AUSP	ATZIS	ATZIS	Instance counter	NUMC	3	C
AUSP	ATSRT	ATSRT	Sort field for characteristic values.	NUMC	4	C
AUSP	ATVGLART	ATVGLART	Comparison type for characteristic values	CHAR	1	C
AUSP	DATUB	DATUB	Valid to	DATS	8	C
AUSP	DEC_VALUE_FROM	DEC_VALUE_FROM	Lower boundary for numeric fields	DEC	16	C
AUSP	DEC_VALUE_TO	DEC_VALUE_TO	Upper boundary for numeric fields	DEC	16	C
AUSP	CURR_VALUE_FROM	CURR_VALUE_FROM	Lower boundary for currency fields	CURR	16	C
AUSP	CURR_VALUE_TO	CURR_VALUE_TO	Upper boundary for currency fields	CURR	16	C
AUSP	CURRENCY	CURRENCY	Currency	CUKY/CHAR	5	C
AUSP	DATE_FROM	DATE_FROM	LowrBndry Date	DATS	8	C
AUSP	DATE_TO	DATE_TO	UprBndry Date	DATS	8	C
AUSP	TIME_FROM	TIME_FROM	LowrBndry Time	TIME	6	C
AUSP	TIME_TO	TIME_TO	UprBndry Time	TIME	6	C
AUSP	PARTNER_GUID	PARTNER_GUID	Business Partner GUID	RAW	16	S

Table	Field	Data Element	Field Label		Field Detail Descriptions	Length	Requirement
AUSP	OBJEK	OBJEK	Object to be classified	Required - Supplier. Key of the object to be classified. Primary key - mandatory. BP already created in the system. Upfront automated. Type: CHAR Length: 90	CHAR	90	R
AUSP	ATINN	ATINN	Internal char no.	Required - Internal Characteristic Number. Primary key - mandatory. Naming convention to be followed. Upfront automated. Type: NUMC Length: 10	NUMC	10	R
AUSP	ATZHL	ATZHL	Int counter	System Generated - Internal numeric counter for a characteristic value. Primary key - mandatory. Derived by the system. Upfront automated. Type: NUMC Length: 3	NUMC	3	S
AUSP	MAFID	MAFID	Indicator: Object/Class	Required - Indicator: Object/Class. Primary key - mandatory. Flag. Upfront automated. Type: CHAR Length: 1	CHAR	1	R
AUSP	KLART	KLART	Class Type	Required - Uniquely identifies the class type. Upfront automated. Class types are created in customizing for Classification. Value 010: Vendor. Primary key - mandatory. Type: CHAR Length: 3	CHAR	3	R
AUSP	ADZHL	ADZHL	Int. counter	System Generated -Internal Counter (e.g., sequence number for values). Derived by the system, technically is filled automatically. Optional for the user. Upfront automated. Type: NUMC Length: 4	NUMC	4	S
AUSP	ATWRT	ATWRT	Characteristic Value	Conditional - Value of a characteristic. Follow the naming convention. Ongoing Manual If the characteristic has character format (CHAR), this field contains a single character string. Values in time format (TIME) must have the format HH:MM:SS. The separators are set automatically. Example: 112855 --> 11:28:55 The values in date format (DATE) must have the format DD.MM.YYYY. The separators are set automatically. Example: 110100 --> 11.01.2000 Note If you valuate validity parameters, you cannot specify intervals. You can only specify individual values. The following description does not apply to the valuation of validity parameters: If the characteristic format is numeric (NUM), time (TIME), or date (DATE), you can enter a number or (if allowed) an interval. Intervals are written in the following format: Value1 - Value2 (from Value1 to Value2) >Value1 (greater than Value1) >=Value1 (greater than or equal to Value1) <Value2 (less than Value2) <=Value2 (less than or equal to Value2) >Value1 - <Value2 (greater than Value1 and less than Value2) Value1 - <Value2 (greater than or equal to Value1 and less than Value2) >Value1 - Value2 (greater than Value1 and less than or equal to Value2) If the characteristic has more than one value, you can enter multiple values separated by semicolons. If you have maintained a unit of measure for numeric values in the formatting data of the characteristic, the unit is displayed automatically when you confirm. Note If you want to define intervals as allowed values of a characteristic, you must define the characteristic as "multiple-value" when you maintain the characteristic in the Classification System. This also allows you to enter more than one interval. However, if you assign more than one interval to a characteristic of a class during configuration (for example, 1-2 and 5-6 for characteristic LENGTH), the system only reads one of the intervals when generating an inspection lot in QM. To avoid this problem, do NOT assign more than one interval to a characteristic.	CHAR	70	C
AUSP	ATFLV	ATFLV	Value from	System Generated -Lower boundary for numeric values. Derived by the system, technically is filled automatically. Optional for the user. Date, upfront automated. Type: NUMC Length: 10	NUMC	10	S
AUSP	ATAWE	ATAWE	Internal UoM	Conditional - Units of Measure associated with the characteristic. Both link to the unit table. It can be left blank depending on whether that data is relevant for a given record. System checks against the UoM values in the system, customizing, upfront automated. Must be a valid UoM from T006. Type: CHAR Length: 3	CHAR	3	C
AUSP	ATFLB	ATFLB	Value to	System Generated -Upper boundary for numeric values. Derived by the system, technically is filled automatically. Optional for the user. Date, upfront automated. Type: NUMC Length: 10	NUMC	10	S
AUSP	ATAW1	ATAW1	Internal UoM	Conditional - Units of Measure associated with the characteristic. Both link to the unit table. It can be left blank depending on whether that data is relevant for a given record. Must be a valid UoM from T006. Type: CHAR Length: 3	CHAR	3	C
AUSP	ATCOD	ATCOD	Code	Conditional - Indicates value dependency (e.g., used in variant configuration). Against the codes in the system. Upfront automated. Type: CHAR Length: 1	CHAR	1	C
AUSP	ATTLV	ATTLV	Tolerance from	Conditional - Lower limit tolerance value. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated. Type: NUMC Length: 10	NUMC	10	C
AUSP	ATTLB	ATTLB	Tolerance to	Conditional - Upper limit tolerance value. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated. Type: NUMC Length: 10	NUMC	10	C
AUSP	ATPRZ	ATPRZ	Percentage	Conditional - Indicates if tolerance should be shown as a percentage. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated. Type: CHAR Length: 1	CHAR	1	C
AUSP	ATINC	ATINC	Increment	Conditional - Step value or interval for increments. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated. Type: NUMC Length: 10	NUMC	10	C
AUSP	ATAUT	ATAUT	Authorization Group	Conditional - This key defines whether a user is allowed to maintain this characteristic. Ongoing Manual This authorization must be defined in the user master record. The authorization object is C_CABN_GRP. Type: CHAR Length: 1	CHAR	1	C
AUSP	AENNR	AENNR	Change Number	Conditional - Change Number (linked to change documents/transport) Only required if the charc. is linked to a doc. System checks against the doc linked to in S4HANA. Upfront automated. Type: CHAR Length: 12	CHAR	12	C
AUSP	DATUV	DATUV	Valid From	Conditional - Specifies the start date for the validity period of an object (such as material, BOM, or routing). Date, upfront automated. Type: DATS Length: 8	DATS	8	C
AUSP	LKENZ	LKENZ	Deletion indicator	Conditional - Deletion Indicator (logical deletion flag). It can be left blank depending on whether that data is relevant for a given record. Flag. Upfront automated. Type: CHAR Length: 1	CHAR	1	C
AUSP	ATIMB	ATIMB	Characteristic number	Conditional - Characteristic number of a user-defined data type. This often refers to characteristics defined outside standard domain. Upfront automated. Type: NUMC Length: 10	NUMC	10	C
AUSP	ATZIS	ATZIS	Instance counter	Conditional - Used to differentiate multiple instances of characteristic values within the same object. Upfront automated. Type: NUMC Length: 3	NUMC	3	C
AUSP	ATSRT	ATSRT	Sort field for characteristic values.	Conditional - Sort field for characteristic values. Determines ordering when multiple values are processed or displayed. It can be left blank depending on whether that data is relevant for a given record. On going manual. Type: NUMC Length: 4	NUMC	4	C
AUSP	ATVGLART	ATVGLART	Comparison type for characteristic values	Conditional - Values range from blank to '7', indicating inclusion/exclusion logic like subset, superset, identical, or exclusive conditions. It can be left blank depending on whether that data is relevant for a given record. System checks against the options in the system. Upfront automated. Type: CHAR Length: 1	CHAR	1	C
AUSP	DATUB	DATUB	Valid to	Conditional - End date of the characteristic’s validity period. Used to control when a characteristic becomes inactive in classification. It can be left blank depending on whether that data is relevant for a given record. Date, upfront automated Type: DATS Length: 8	DATS	8	C
AUSP	DEC_VALUE_FROM	DEC_VALUE_FROM	Lower boundary for numeric fields	Conditional - Used when characteristic value represents a numeric range. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated. Type: DEC Length: 16	DEC	16	C
AUSP	DEC_VALUE_TO	DEC_VALUE_TO	Upper boundary for numeric fields	Conditional - Together with DEC_VALUE_FROM, defines a numeric interval. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated. Type: DEC Length: 16	DEC	16	C
AUSP	CURR_VALUE_FROM	CURR_VALUE_FROM	Lower boundary for currency fields	Conditional - Used when characteristic value represents a currency range. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated. Type: CURR Length: 16	CURR	16	C
AUSP	CURR_VALUE_TO	CURR_VALUE_TO	Upper boundary for currency fields	Conditional - Defines the top end of a monetary range. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated. Type: CURR Length: 16	CURR	16	C
AUSP	CURRENCY	CURRENCY	Currency	Conditional - Currency key. System checked against the values already customized in the system. Upfront automated. Type: CUKY/CHAR Length: 5	CUKY/CHAR	5	C
AUSP	DATE_FROM	DATE_FROM	LowrBndry Date	Conditional - Start of date range. It can be left blank depending on whether that data is relevant for a given record. Date, upfront automated. Type: DATS Length: 8	DATS	8	C
AUSP	DATE_TO	DATE_TO	UprBndry Date	Conditional - End of date range. It can be left blank depending on whether that data is relevant for a given record. Date, upfront automated. Type: DATS Length: 8	DATS	8	C
AUSP	TIME_FROM	TIME_FROM	LowrBndry Time	Conditional - Start time in time interval. It can be left blank depending on whether that data is relevant for a given record. Timing, upfront automated. Type: TIME Length: 6	TIME	6	C
AUSP	TIME_TO	TIME_TO	UprBndry Time	Conditional - End time in time interval. It can be left blank depending on whether that data is relevant for a given record. Timing, upfront automated. Type: TIME Length: 6	TIME	6	C
AUSP	PARTNER_GUID	PARTNER_GUID	Business Partner GUID	System Generated -Used when the classified object is a Business Partner, providing a unique identifier. Derived by the system technically, optional for the user. Upfront automated Type: RAW Length: 16	RAW	16	S

Data Cleansing

No data cleansing is required for the Vendors - Classification and Characteristic Assignment in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.

As a result, the cleansed Vendors - Classification and Characteristic Assignment data will be populated directly in the Data Collection Template (DCT).

Conversion Process

Collection will be done manually in the Data Collection Template for the following scenarios:

For sites not on SAP-PF2 or WP2 systems
For new Vendors - Classification and Characteristic Assignment data that need to be created to support the to-be design

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

SyWay Project > CNV-3028 Vendors - Classification and Characteristic Assignment > image-2025-11-23_19-39-12-1.png

Data Privacy and Sensitivity

N/A

Extraction

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads.

Extract data from a source into Syniti
The data does not exist (or cannot be converted from its current state) which should manually provided by the business with the help of data team directly in Syniti The
This is to be conducted using DCT (Data Collection Template) in Syniti.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy criteria	SyWay Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team

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
N/A

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Vendors - Classification and Characteristic Assignment data with exception of some fields which require transformation as mentioned in the transformation rule.

The extracted report will be loaded into the required structure using the DCT.
Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

CNV 3028 -Vendors - Classification and Characteristic Assignment DCT Rules:

Table - Field Name	Field Description	Rule	Data Type	Length	Requirement
AUSP-OBJEK	Object to be classified	Supplier. Key of the object to be classified. Primary key - mandatory. BP already created in the system. Upfront automated.	CHAR	90	R
AUSP-ATINN	Internal char no.	Internal Characteristic Number. Primary key - mandatory. Naming convention to be followed. Upfront automated.	NUMC	10	R
AUSP-ATZHL	Int counter	Internal numeric counter for a characteristic value. Primary key - mandatory. Derived by the system. Upfront automated.	NUMC	3	S
AUSP-MAFID	Indicator: Object/Class	Indicator: Object/Class. Primary key - mandatory. Flag. Upfront automated.	CHAR	1	R
AUSP-KLART	Class Type	Uniquely identifies the class type. Upfront automated. Class types are created in customizing for Classification. Value 010: Vendor. Primary key - mandatory.	CHAR	3	R
AUSP-ADZHL	Int. counter	Internal Counter (e.g., sequence number for values). Derived by the system, technically is filled automatically. Optional for the user. Upfront automated.	NUMC	4	S
AUSP-ATWRT	Characteristic Value	Value of a characteristic. Follow the naming convention. Ongoing Manual If the characteristic has character format (CHAR), this field contains a single character string. Values in time format (TIME) must have the format HH:MM:SS. The separators are set automatically. Example: 112855 --> 11:28:55 The values in date format (DATE) must have the format DD.MM.YYYY. The separators are set automatically. Example: 110100 --> 11.01.2000 Note If you valuate validity parameters, you cannot specify intervals. You can only specify individual values. The following description does not apply to the valuation of validity parameters: If the characteristic format is numeric (NUM), time (TIME), or date (DATE), you can enter a number or (if allowed) an interval. Intervals are written in the following format: Value1 - Value2 (from Value1 to Value2) >Value1 (greater than Value1) >=Value1 (greater than or equal to Value1) <Value2 (less than Value2) <=Value2 (less than or equal to Value2) >Value1 - <Value2 (greater than Value1 and less than Value2) Value1 - <Value2 (greater than or equal to Value1 and less than Value2) >Value1 - Value2 (greater than Value1 and less than or equal to Value2) If the characteristic has more than one value, you can enter multiple values separated by semicolons. If you have maintained a unit of measure for numeric values in the formatting data of the characteristic, the unit is displayed automatically when you confirm. Note If you want to define intervals as allowed values of a characteristic, you must define the characteristic as "multiple-value" when you maintain the characteristic in the Classification System. This also allows you to enter more than one interval. However, if you assign more than one interval to a characteristic of a class during configuration (for example, 1-2 and 5-6 for characteristic LENGTH), the system only reads one of the intervals when generating an inspection lot in QM. To avoid this problem, do NOT assign more than one interval to a characteristic.	CHAR	70	C
AUSP-ATFLV	Value from	Lower boundary for numeric values. Derived by the system, technically is filled automatically. Optional for the user. Date, upfront automated.	NUMC	10	S
AUSP-ATAWE	Internal UoM	Units of Measure associated with the characteristic. Both link to the unit table. It can be left blank depending on whether that data is relevant for a given record. System checks against the UoM values in the system, customizing, upfront automated. Must be a valid UoM from T006.	CHAR	3	C
AUSP-ATFLB	Value to	Upper boundary for numeric values. Derived by the system, technically is filled automatically. Optional for the user. Date, upfront automated.	NUMC	10	S
AUSP-ATAW1	Internal UoM	Units of Measure associated with the characteristic. Both link to the unit table. It can be left blank depending on whether that data is relevant for a given record. Must be a valid UoM from T006.	CHAR	3	C
AUSP-ATCOD	Code	Indicates value dependency (e.g., used in variant configuration). Against the codes in the system. Upfront automated.	CHAR	1	C
AUSP-ATTLV	Tolerance from	Lower limit tolerance value. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated.	NUMC	10	C
AUSP-ATTLB	Tolerance to	Upper limit tolerance value. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated.	NUMC	10	C
AUSP-ATPRZ	Percentage	Indicates if tolerance should be shown as a percentage. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated.	CHAR	1	C
AUSP-ATINC	Increment	Step value or interval for increments. It can be left blank depending on whether that data is relevant for a given record. Numeric. Upfront automated.	NUMC	10	C
AUSP-ATAUT	Authorization Group	This key defines whether a user is allowed to maintain this characteristic. Ongoing Manual This authorization must be defined in the user master record. The authorization object is C_CABN_GRP.	CHAR	1	C
AUSP-AENNR	Change Number	Change Number (linked to change documents/transport) Only required if the charc. is linked to a doc. System checks against the doc linked to in S4HANA. Upfront automated.	CHAR	12	C
AUSP-DATUV	Valid From	Specifies the start date for the validity period of an object (such as material, BOM, or routing). Date, upfront automated.	DATS	8	C
AUSP-LKENZ	Deletion indicator	Deletion Indicator (logical deletion flag). It can be left blank depending on whether that data is relevant for a given record. Flag. Upfront automated.	CHAR	1	C
AUSP-ATIMB	Characteristic number	Characteristic number of a user-defined data type. This often refers to characteristics defined outside standard domain. Upfront automated.	NUMC	10	C
AUSP-ATZIS	Instance counter	Used to differentiate multiple instances of characteristic values within the same object. Upfront automated.	NUMC	3	C
AUSP-ATSRT	Sort field for characteristic values.	Sort field for characteristic values. Determines ordering when multiple values are processed or displayed. It can be left blank depending on whether that data is relevant for a given record. On going manual.	NUMC	4	C
AUSP-ATVGLART	Comparison type for characteristic values	Values range from blank to '7', indicating inclusion/exclusion logic like subset, superset, identical, or exclusive conditions. It can be left blank depending on whether that data is relevant for a given record. System checks against the options in the system. Upfront automated.	CHAR	1	C
AUSP-DATUB	Valid to	End date of the characteristic’s validity period. Used to control when a characteristic becomes inactive in classification. It can be left blank depending on whether that data is relevant for a given record. Date, upfront automated	DATS	8	C
AUSP-DEC_VALUE_FROM	Lower boundary for numeric fields	Used when characteristic value represents a numeric range. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated.	DEC	16	C
AUSP-DEC_VALUE_TO	Upper boundary for numeric fields	Together with DEC_VALUE_FROM, defines a numeric interval. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated.	DEC	16	C
AUSP-CURR_VALUE_FROM	Lower boundary for currency fields	Used when characteristic value represents a currency range. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated.	CURR	16	C
AUSP-CURR_VALUE_TO	Upper boundary for currency fields	Defines the top end of a monetary range. It can be left blank depending on whether that data is relevant for a given record. Numeric, upfront automated.	CURR	16	C
AUSP-CURRENCY	Currency	Currency key. System checked against the values already customized in the system. Upfront automated.	CUKY/CHAR	5	C
AUSP-DATE_FROM	LowrBndry Date	Start of date range. It can be left blank depending on whether that data is relevant for a given record. Date, upfront automated.	DATS	8	C
AUSP-DATE_TO	UprBndry Date	End of date range. It can be left blank depending on whether that data is relevant for a given record. Date, upfront automated.	DATS	8	C
AUSP-TIME_FROM	LowrBndry Time	Start time in time interval. It can be left blank depending on whether that data is relevant for a given record. Timing, upfront automated.	TIME	6	C
AUSP-TIME_TO	UprBndry Time	End time in time interval. It can be left blank depending on whether that data is relevant for a given record. Timing, upfront automated.	TIME	6	C
AUSP-PARTNER_GUID	Business Partner GUID	Used when the classified object is a Business Partner, providing a unique identifier. Derived by the system technically, optional for the user. Upfront automated	RAW	16	S

Extraction Dependencies

List the steps that need to occur before extraction can commence

N/A

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 to make the data Target ready.

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
1	Obtain DCT Sign-off from Business	SyWay S2P Data Team
2	Select the wave – S4/HANA – S2P(Source to Pay)	Syniti
3	Go to Process Area Launch and Process the Object – Vendor Classifications	Syniti
4	Review and Validate Error and Preload Reports	Syniti
5	Execute the transformation to prepare the target tables	Syniti
6	Review and Validate Error and Preload Reports	Business/Data owner
7	Generate Load Files	Syniti

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:

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

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.

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

Workflow history