Batch Characteristics will be collected via DCT. An extract of the relevant Characteristics will be provided to assist business in standardizing the Characteristics from PF2 and WP2.

SAP S/4 HANA

Batch Characteristics will be collected via DCT. An extract of the relevant Characteristics will be provided to assist business in standardizing the Characteristics from PF2 and WP2.

SAP S/4 HANA

DATUV

ANZST

ATKLE

Optional

But if Data Type is CURR, this is Mandatory

MSEHI

Exponent display

CAWN_DEC_FROM

Lower Boundary for Numeric Field

DECFLOAT34

CAWN_DEC_TO

Upper Boundary for Numeric Field

DECFLOAT34

Characteristic

Name that uniquely identifies a characteristic.

Mandatory

TBD

Characteristics Name - Need to follow the naming Convention which will distinguish across different functions (Eg; Vendor Classification or EAM Characteristics)

Mandatory

When the Load File is generated, Current Date should be captured

• Descriptions need to follow a standard naming convention across all characteristics.
• Use similar formats for similar types of characteristics
• Avoid abbreviations unless they are commonly accepted by Syensqo

Characteristic Group

The characteristics group can be used to group together similar characteristics. It is used to make finding characteristics easier.

Conditional

Need to select the appropriate characteristics group for the batch characteristics. As these are configurable values, these are TBD until Functional defines it.

Mandatory

Fixed Value as 1 - Released

Mandatory 

Below are list of values used: 

• Character format (CHAR): for characteristic values that consist of a character string
• Numeric format (NUM): for numeric characteristic values
• Date format (DATE): for characteristic values that represent a date
• Time format (TIME): for characteristic values that represent a time
• Currency format (NUM): for characteristic values that are entered in a currency

Mandatory

• If a characteristic has data type "character" (CHAR), you can maintain a language-dependent description for values. This description can be up to 30 characters long, regardless of the number you enter here.
• If a characteristic has data type "Currency" (CURR), No of Characters to be maximum 15
• If a characteristic has data type "Number" (CURR), No of Characters to be maximum 15

Conditional

Indicator to set the characteristic values entered are automatically converted into upper-case letters.

Optional

If these are defined in Configuration for  "character" (CHAR)for Need to use the specific template for this Characteristics. 

If these are defined in Configuration for  "Currency" (CURR), it is automatically populated.

Mandatory 

If CURR Data type is selected, Fill in the Currency of the characteristic.

Two options are possible: 

• Single Values
• Multiple Values

Conditional.

Exponent display

Conditional.

This can to be filled, when data type chosen NUM

List of Values: 
0: No exponent
1: Standard
2: Exponent entered
3: Scientific exponent

Conditional.

Indicator (check box).

Conditional.

Indicator (check box).

Conditional.

Indicator (check box).

Conditional.

Indicator (check box).

Conditional

If the format of the Characteristics need to refer from Table, this is filled in

Conditional

Transparent Table ( Check Table is maintained so that Characteristics Values are used from the Table in Transaction Data) 

Conditional

If the format of the Characteristics need to refer from Table-Field, this is filled in

Conditional - If Reference Table and Field are not provided 

Mandatory - If the format of the characteristics needs to be referenced from a table, this information should be provided here.

Conditional.

Indicator (check box).

Conditional.

Indicator (check box).

Conditional.

Indicator (check box).

Conditional.

Indicator (check box).

Mandatory

TBD

This should be assigned from CABN-ATNAM

System Generated. 

System creates a internal sequential number for each Characteristic Value

Optional

Characteristics values are defined here if these are created in Characters.

Lower Boundary for Numeric Field

Optional

From Characteristics values are defined here if these are created in Numeric For Eg: 0 % - 100% Etc.

Upper Boundary for Numeric Field

1

Obtain DCT Sign-off from Business.

SCM Data Team

2

In dspMigrate, select the wave – S4/HANA – P2F-SCM

Syniti

3

Go to Process Area Launch and Process the Object – Characteristics

Syniti

4

Review and Validate Error and Preload Reports

Syniti

5

Execute the transformation to prepare the target tables

Syniti

6

Validate data from pre-load and error reports

Business/Data owner

7

Generate load files

Syniti

Direct Mapping

If has value in DCT, Direct Mapping.

If blank, default to Creation Date.

Direct Mapping

Need Dropdown in DCT.

1) CHAR

2) NUM

3) CURR

Direct Mapping

Valid for only Data Type CURR 

Exponent display

Exponent display

Direct Mapping

If check table is assigned then Characteristics Values are not populated in Characteristic Values DCT.

Direct Mapping

Lower Boundary for Numeric Field

Lower Boundary for Numeric Field

Upper Boundary for Numeric Field

Upper Boundary for Numeric Field

1

Ensure DCT tables completeness

Syniti

2

Ensure all Transformation mappings are up to date.

Syniti

SCM 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.

Verify Consent

Verify the appropriate consents for the records have been obtained by the business/Data Owners and properly recorded

Conversion Accuracy

SCM Data team to verify that all the data in the load table/file is accurate as per signed-off DCT contents and transformation rules with below checks: 

1. Mandatory Fields
2. Field and Value Mapping Correctness
3. Null Checks

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.

Verify Consent

Verify that the appropriate consents for the records have been obtained by the business and properly recorded

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).

1

Ensure Pre-load sign-offs are obtained.

SCM Data team

2

Go to the load tool and select the correct load Program.

SCM Data team

3

Proceed with Data load.

SCM Data team

4

Validate few records loaded by accessing standard transactions.

SCM Data team

5

Generate the post load reports in the tool.

SCM Data team

6

Log errors as defects, if any and address resolutions. Close defects.

SCM Data team

7

Resolve defects by re-upload and re-generate post load reports if necessary.

SCM 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.

SCM Data team

If it is a missing configuration item, then engage Functional team to expedite and fix the error in the system.

Invalid Data

<parameter> is not valid.

The parameter entry needs to be reviewed

Technical Setup

Interface / Connection issue within target system’s landscape

N/A – the data will be loaded directly to S/4HANA environment

Verify that the record count in the post-load file is the same as the record count based on the relevancy (including any deduplication) results 

Data Accuracy

SCM Data team to verify that all the data in the post load table/file is accurate as per signed-off transformation rules and DCT contents

Error Reports

Verify that all necessary error reports have been validated, and that errors have been addressed.

Data Consistency

Verify that the data loaded is correctly reflected in T-Code: CT04 or Table: CABN/CABNT.

Verify Count

Verify that the record count in the post load file is the same as the record count based on the relevancy (including deduplication) results

Validate Loaded Data

Validate, as per the load files signed-off, that all records were created

Data Accuracy

Verify that all the data in the S/4HANA table is accurate as per signed-off DCT contents and transformation rules

For mock loads, the post load data validation will be as per scrambled data, thus data accuracy is not to be checked against DCT which holds the actual data. Post-load data to be validated against the pre-load report (scrambled data).

Verify Relationships

Verify that each Vendor have been assigned to the appropriate Business Partner correctly