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

Name that uniquely identifies a characteristic.

Follow the naming convention which will distinguish across different functions

For Eg:

QM_00001 (QM Related Characteristics)

SC_00001 (Supply/Logistics Related Characteristics)

Mandatory

TBD

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

Valid From

The class validity starts from this date. If it is not set the current system date will be used as valid-from date.

Mandatory

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

Description

Language-dependent description of characteristic.

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

Status

The characteristic status gives information on the processing status of the characteristic and determines whether it can be used elsewhere in the system.
Possible values:
0 = in preparation
1 = released
2 = locked

Mandatory

Fixed Value as 1 - Released

Data Type

The data type defines whether a characteristic value is a character string, a number, a date, or a time.
CHAR Character Format
CURR Currency Format
DATE Date Format
NUM Numeric Format
TIME Time Format
UDEF User-Defined Data Type

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

Number of Characters

Total number of characters that you can enter when you assign a value to this characteristic. This figure includes the number of decimal places.

This figure does not include plus or minus signs or decimal points.

Important:
In the S/4HANA cloud system, the number of characters, in a character format(CHAR) characteristic, max to 30.

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

Case Sensitive

This indicator determines whether lower-case letters can be entered in characteristic values.
If this field is blank, the characteristic values entered are automatically converted into upper-case letters.
'X' = Case sensitive

Conditional

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

Template

Entries for this characteristic are checked against this template.
Character format (CHAR): You can only define template characters which have been defined in Customizing. These settings determine whether a template can contain only letters, figures, figures or letters, or special characters.
Numeric format (NUM): Numeric template characters can also be defined in Customizing.

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.

Decimal places

Total number of characters that you can enter when you assign a value to this characteristic. This figure includes the number of decimal places.

This figure does not include plus or minus signs or decimal points

Currency

Key for the currency in which the amounts are managed in the system (in ISO code).
The field is mandatory if the data type is currency (CURR).

Mandatory 

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

Value Assignment

The possible entries for value assignment(Single/Multiple Value):
Value Descriptions
 S Single-value
 M Multiple value

Two options are possible: 

• Single Values
• Multiple Values

Unit of Measure

Unit in which a numeric characteristic value is entered. When you assign a value to the characteristic, you can enter a different unit if it can be converted to the unit entered in characteristics maintenance. The dimension (such as length or volume) determines which units can be converted to which

Conditional.

Exponent display

Specifies how the numerical value of a characteristic is to be displayed with an exponent.
Possible values:
0 = Display w/o an exponent
1 = Exponent set automatically.
 There's always one place before the decimal point
 Example: _,____E+__
2 = Display w/ exponent entered.
 Example: _,____E+33
3 = Display in scientific format (3,6,9)
 There are always three places before the decimal point
 Example: __,_____E+SS

Exponent used when characteristic value is displayed.
Can only be used for numerical characteristics

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

Interval values allowed

This indicator determines whether you have the option of entering an interval as a value for a numeric characteristic.
'X' = Interval values allowed

Conditional.

Indicator (check box).

Negative values allowed

Defines whether negative values can be assigned to a characteristic.
'X' = negative values can be assigned

Conditional.

Indicator (check box).

Entry Required

Determines whether you are required to assign a value to a characteristic.
'X' = entry is required

Conditional.

Indicator (check box).

Language

Please enter here the language of your description (ISO format).

Sy-Way Program Languages Scope: 

English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish.

English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish.

Additional Values

This indicator determines whether values that are not defined as allowed values can be assigned to a characteristic.
'X' = no value check
The additional values indicator can be set to 'X' in the following value check types:
1. Allowed values
2. Function module

Conditional.

Indicator (check box).

Restrictable characteristic

This indicator shows that the allowed values of this characteristic can restricted during Variant
Configuration, depending on the configuration environment.
Note:
You can only use this indicator in constraints.
This indicator is not relevant to classification.

This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.

Conditional 

Indicator (check box).

Reference Table

Name of a table that contains the allowed values for the characteristic.

This table can have exactly one key field. Tables that do not conform to this specification are not accepted.
This can can also contain a client.

If you want to check values using a table that does not conform to this specification, you can use a function module to define the check table.

Conditional

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

Check Table

To get the Characteristics values from Reference Table, Need to select this option so that we can reference the table to get the Characteristics Value. For Eg: UD Code Etc., 

Conditional

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

Reference Field

This table can have exactly one key field

Conditional

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

Not ready for input

This indicator determines whether the characteristic is shown as available for entry on the characteristic value assignment screen.

If you do not want a value to be assigned to a characteristic, you must select this indicator. For example, the value may be inferred from object dependencies.

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.

No display

Characteristic Not to be Displayed

If you select this indicator, the characteristic is not shown on the characteristic value assignment screen. You see the Hidden characteristics pushbutton on the characteristic value assignment screen. Choose this pushbutton to see the characteristic.

If the Entry required indicator is set for the characteristic, you must assign a value to the characteristic, even if it is not shown on the screen. You see a dialog box before you leave the characteristic value assignment screen, in which you can assign a value to the characteristic.

Conditional.

Indicator (check box).

Display Allowed Values

Display allowed values defined in characteristic
Determines whether the allowed values for a characteristic are displayed after the characteristic when you assign values to a characteristic.

Conditional.

Indicator (check box).

Unformatted Entry

Unformatted entry control

Used to define the length of the entry field when assigning values to a characteristic.

If this field is not selected, the entry field is shortened to the number of characters in the format for the characteristic. Otherwise, a 30-character field is available for entry, so that you can enter intervals or several values, separated by a semicolon.

Conditional.

Indicator (check box).

Propose Template

If we use template to populate the Characteristics Values using the Template.

Indicator: display template when assigning values
Indicator: defines whether the template is displayed in the characteristic value field as an aid to entry.

For Eg: 

 If we use template, Example: _,____E+__

Conditional.

Indicator (check box).

Internal characteristic

Name that uniquely identifies a characteristic.

Mandatory

TBD

This should be assigned from CABN-ATNAM

Int counter

The item number is only an additional technical key to allow multiple values in the file and to prevent errors by the duplicate record check.
It must be unique over all "Value" structures because it is also a key field for the "Value Descriptions".
It is not mapped to a target field.
Please maintain a number from 0001 to 9999 per multiple value.

System Generated. 

System creates a internal sequential number for each Characteristic Value

Characteristic Value

The language-dependent long value of a characteristic.
You must either maintain the language-dependent value (description) here in this column.

Important:
In the S/4HANA cloud system, the length of the characteristic value, in a character format(CHAR) characteristic, max to 30.

Optional

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

Lower Boundary for Numeric Field

Internal Floating Point From

Numerical Value from (Floating point)
Ignore the automatically set decimals.
NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99.
Missing Decimals are automatically set when pressing Enter.
The value is related on the Unit of measure (UoM) maintained on the header data of the characteristics.
For example, if the UoM of the characteristic is JHR, '2' means two years.
The system ignores units in the fields UNIT_FROM and UNIT_TO here. These are used only for later display.
It is important that the UoM according to ISO 639 in the field VALUE_FROM_ISO is the same as the characteristic that was defined for the characteristic.

Optional

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

Relational operators to define the intervals with the following input options:
 Code Operator Value1(Value From) Operator Value2(Value To)
 1 EQ =
 2 GE >= LT <
 3 GE >= LE <=
 4 GT > LT <
 5 GT > LE <=
 6 LT <
 7 LE <=
 8 GT >
 9 GE >=
For example:
VALUE_FROM: 20
VALUE_TO: 28
VALUE_RELATION: 2
Imported value: 20 - < 28

Upper Boundary for Numeric Field

Internal Floating Point To

Numerical Value to (Floating point) (only used in intervals)
Ignore the automatically set decimals.
NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99.
Missing Decimals are automatically set by the Spreadsheet, when pressing Enter.
The value is related on the characteristic's Unit of measure.

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