| Status |
| |
|---|---|---|
| Owner | ||
| Stakeholders |
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 010 from Legacy Source Systems into S/4HANA following Master Data Design Standard.
To-Be Design: Agreed list of class, characteristics and characteristic values will be Provided by Business/Functional Team which will reflect for Vendors - Classification and Characteristic Assignment of vendors class type 010 conversation scope.
TBC - Intercompany(IC) vendors classes, characteristics and characteristic assignment with the values are not designed or confirmed yet.
| Google Drive Live Link | ||
|---|---|---|
|
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:
- Based on the vendor relevancy criteria of CNV-3007 (CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base)
| 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 and Characteristics Values of a class type 010 be collected via DCT which follows the same approach for the vendor classifications. 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. (TBC - Waiting for the final design or confirmation from functional team and this is applicable to proceed with the DCT construct and Unit testing- 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) 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 |
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).
Validation Reports
Google drive path for the validation reports:
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:
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
- 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
- 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
| 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 / Field detailed description | 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
| 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 |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | AUSP | OBJEK | Object to be classified | S/4 Hana | AUSP | OBJEK | Object to be classified | Supplier Number. - XREF Length should be 10 Characters( add leading zeros if needed ) |
| 2 | DCT | AUSP | ATINN | Internal char no. | S/4 Hana | AUSP | ATINN | Internal char no. | Direct Mapping |
| 3 | DCT | AUSP | ATZHL | Int counter | S/4 Hana | AUSP | ATZHL | Int counter | System Generated |
| 4 | DCT | AUSP | MAFID | Indicator: Object/Class | S/4 Hana | AUSP | MAFID | Indicator: Object/Class | Direct Mapping |
| 5 | DCT | AUSP | KLART | Class Type | S/4 Hana | AUSP | KLART | Class Type | Default value "010" |
| 6 | DCT | AUSP | ADZHL | Int. counter | S/4 Hana | AUSP | ADZHL | Int. counter | System Generated |
| 7 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | AUSP | ATWRT | Characteristic Value | Direct Mapping |
| 8 | DCT | AUSP | ATFLV | Value from | S/4 Hana | AUSP | ATFLV | Value from | System Generated |
| 9 | DCT | AUSP | ATAWE | Internal UoM | S/4 Hana | AUSP | ATAWE | Internal UoM | XREF |
| 10 | DCT | AUSP | ATFLB | Value to | S/4 Hana | AUSP | ATFLB | Value to | System Generated |
| 11 | DCT | AUSP | ATAW1 | Internal UoM | S/4 Hana | AUSP | ATAW1 | Internal UoM | Direct Mapping |
| 12 | DCT | AUSP | ATCOD | Code | S/4 Hana | AUSP | ATCOD | Code | Direct Mapping |
| 13 | DCT | AUSP | ATTLV | Tolerance from | S/4 Hana | AUSP | ATTLV | Tolerance from | Direct Mapping |
| 14 | DCT | AUSP | ATTLB | Tolerance to | S/4 Hana | AUSP | ATTLB | Tolerance to | Direct Mapping |
| 15 | DCT | AUSP | ATPRZ | Percentage | S/4 Hana | AUSP | ATPRZ | Percentage | Direct Mapping |
| 16 | DCT | AUSP | ATINC | Increment | S/4 Hana | AUSP | ATINC | Increment | Direct Mapping |
| 17 | DCT | AUSP | ATAUT | Authorization Group | S/4 Hana | AUSP | ATAUT | Authorization Group | XREF |
| 18 | DCT | AUSP | AENNR | Change Number | S/4 Hana | AUSP | AENNR | Change Number | Direct Mapping |
| 19 | DCT | AUSP | DATUV | Valid From | S/4 Hana | AUSP | DATUV | Valid From | Direct Mapping |
| 20 | DCT | AUSP | LKENZ | Deletion indicator | S/4 Hana | AUSP | LKENZ | Deletion indicator | Direct Mapping |
| 21 | DCT | AUSP | ATIMB | Characteristic number | S/4 Hana | AUSP | ATIMB | Characteristic number | Direct Mapping |
| 22 | DCT | AUSP | ATZIS | Instance counter | S/4 Hana | AUSP | ATZIS | Instance counter | Direct Mapping |
| 23 | DCT | AUSP | ATSRT | Sort field for characteristic values. | S/4 Hana | AUSP | ATSRT | Sort field for characteristic values. | Direct Mapping |
| 24 | DCT | AUSP | ATVGLART | Comparison type for characteristic values | S/4 Hana | AUSP | ATVGLART | Comparison type for characteristic values | Direct Mapping |
| 25 | DCT | AUSP | DATUB | Valid to | S/4 Hana | AUSP | DATUB | Valid to | Direct Mapping |
| 26 | DCT | AUSP | DEC_VALUE_FROM | Lower boundary for numeric fields | S/4 Hana | AUSP | DEC_VALUE_FROM | Lower boundary for numeric fields | Direct Mapping |
| 27 | DCT | AUSP | DEC_VALUE_TO | Upper boundary for numeric fields | S/4 Hana | AUSP | DEC_VALUE_TO | Upper boundary for numeric fields | Direct Mapping |
| 28 | DCT | AUSP | CURR_VALUE_FROM | Lower boundary for currency fields | S/4 Hana | AUSP | CURR_VALUE_FROM | Lower boundary for currency fields | Direct Mapping |
| 29 | DCT | AUSP | CURR_VALUE_TO | Upper boundary for currency fields | S/4 Hana | AUSP | CURR_VALUE_TO | Upper boundary for currency fields | Direct Mapping |
| 30 | DCT | AUSP | CURRENCY | Currency | S/4 Hana | AUSP | CURRENCY | Currency | Direct Mapping |
| 31 | DCT | AUSP | DATE_FROM | LowrBndry Date | S/4 Hana | AUSP | DATE_FROM | LowrBndry Date | Direct Mapping |
| 32 | DCT | AUSP | DATE_TO | UprBndry Date | S/4 Hana | AUSP | DATE_TO | UprBndry Date | Direct Mapping |
| 33 | DCT | AUSP | TIME_FROM | LowrBndry Time | S/4 Hana | AUSP | TIME_FROM | LowrBndry Time | Direct Mapping |
| 34 | DCT | AUSP | TIME_TO | UprBndry Time | S/4 Hana | AUSP | TIME_TO | UprBndry Time | Direct Mapping |
| 35 | DCT | AUSP | PARTNER_GUID | Business Partner GUID | S/4 Hana | AUSP | PARTNER_GUID | Business Partner GUID | System Generated |
Transformation Mapping
Google drive path for the value mapping tables (note: no value mapping tables for the CNV 3028)
"| Google Drive Live Link | ||
|---|---|---|
|
| Mapping Table Name | Mapping Table Description |
|---|---|
| Supplier Number | XREF |
| Internal UoM | XREF |
| Authorization Group | XREF |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure DCT tables completeness | SyWay S2P Data Team |
2 | Ensure all Transformation mappings are up to date. | SyWay S2P Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Record Count | SyWay S2P Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | SyWay S2P Data Team to verify that all fields below meet pass the checks:
|
Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
Completeness
| Task | Action |
|---|---|
Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data). |
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 |
|---|---|---|
1 | Ensure Pre-load sign-offs are obtained. | SyWay Data team |
2 | Go to the load tool and select the correct load Program. | Syniti |
3 | Proceed with Data load. | Syniti |
4 | Validate few records loaded by accessing standard transactions. | Syniti |
5 | Generate the post load reports in the tool. | Syniti |
6 | Log errors as defects, if any and address resolutions. Close defects. | Syniti |
7 | Resolve defects by re-upload and re-generate post load reports if necessary. | Syniti / SyWay Data team |
8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
9 | Repeat steps 5 to 7 if necessary. | Syniti |
Load Phase and Dependencies
N/A
Configuration
R4 Config Template and Config Workbook Google drive path for the reference - R4 Config Templates and Config workbooks - Google Sheets
| Item # | Configuration Item |
|---|---|
1 | T006-Units of Measurement |
2 | TOBJ - Authorization Group |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1139 | CNV-1139 Vendors - Class Type 010 (CNV-1139 Vendors - Class Type 010 - SyWay Project - Syensqo - Wiki knowledge base) |
| 3026 | CNV-3025 Vendors - Characteristics of Class Type 010 (CNV-3025 Vendors - Characteristics of Class Type 010 - SyWay Project - Syensqo - Wiki knowledge base) |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Configuration | Invalid Units of Measurement | Engage Functional team to expedite and fix the error in the system |
Configuration | ATAUT - Authorization Group - Invalid Authorization Group | Engage Functional team to expedite and fix the error in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | SyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in Syniti or standard reports from S/4 HANA. |
Verify Logs | Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.). |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the Characteristics data in target S/4 HANA were loaded correctly via Syniti post load reports or standard reports from S/4 HANA. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Download Post Load Reports from Syniti and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the Vendor Characteristics data in target S/4 HANA were loaded correctly via Syniti post load reports or standard reports from S/4 HANA |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed. (If applicable for Cleansing)
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
See also
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|