Classification & Master Data Add-ons
On the perennial question of characteristic values longer than 30 characters, the correct answer since S/4HANA is: it depends. What matters is which mode your system runs in — and few people know that off the top of their head.
30 characters, 70 characters — or an add-on after all?
Classically, character-type characteristic values (field ATWRT) are limited to 30 characters. SAP S/4HANA changed that — though not automatically. Since S/4HANA 1511 the database field holds 70 characters, and that length can actually be used provided the system runs in target mode with field length extension activated (customising under Cross-Application Components → General Application Functions → Field Length Extension → Activate extended fields, transaction FLETS).
The catch lies in compatibility mode: many S/4 systems still run there because interfaces, partner add-ons or custom programs cannot cope with the extended field lengths. In that mode the database fields are 70 characters wide, but maintenance (CT04) still stops at 30. This is exactly what causes the recurring puzzlement that "the standard should be able to do it" and yet it does not.
From that follows an honest positioning of our characteristic value add-on: in an S/4HANA system in target mode with field length extension active you do not need it for the 70 characters — that is standard. It stays relevant for SAP ECC, for S/4 systems in compatibility mode that remain there for good reasons, and for cases where even 70 characters are not enough.
The real consulting question is therefore not the add-on but: which mode does your system run in, what depends on a switch to target mode, and which route to the goal is cheaper? We clarify that before anything gets installed.
And once the longer fields are there? That is when the work starts. Over the years your users have worked around the 30-character limit: with abbreviations, with values spread across several characteristics, with additional fields or Z tables. Those legacies do not disappear just because the field suddenly holds 70 characters. We convert existing characteristic values into the longer form — analysing where things were abbreviated or split, merging the values, updating the dependent objects and dismantling the old workarounds in a controlled way.
At a glance
- Assessment: target mode or compatibility mode?
- Evaluating and supporting field length extension (FLETS)
- Converting existing characteristic values into the longer form
- Add-on for ECC, compatibility mode and values >70 characters
- No append fields, no modification of the standard
- Characteristic hierarchies & dependencies
- MMRI: automated material master short-text translation
Check first, then decide
The assessment costs little and saves an unnecessary installation.
- Does your system run in target mode or compatibility mode?
- Is field length extension already activated?
- What depends on a switch: interfaces, partner add-ons, custom code?
- Are 70 characters even enough for your use case?
Converting existing values
Longer fields alone do not clear up the past — that is the actual project work.
- Analysis: where was it abbreviated, split or worked around?
- Merging values that were spread across several characteristics
- Turning abbreviations into the full designation
- Updating dependent objects: classification, variant tables, dependency knowledge
- Dismantling old workarounds (extra characteristics, Z tables, append fields)
- Logged, repeatable execution instead of manual work
When the add-on earns its keep
It does not replace a standard that already works — it closes the gap next to it.
- SAP ECC without field length extension
- S/4HANA in compatibility mode
- Requirements beyond 70 characters
- No append fields, enhancements or modifications
- Integration into the standard screens (originated in the DVS environment)
- Search across the extended value included
Characteristics & hierarchies
What goes beyond mere field length.
- Complex dependencies between characteristics and values
- Hierarchical characteristic structures
- Classification as the basis for retrieval and configuration
- Performance with large characteristic and value volumes
MMRI translation add-on
Multilingual short texts in the material master without duplicate work.
- Automatic generation on creation and change
- Initial load of existing short texts
- Update of the material masters after maintenance
- RFC export for external translation providers
- Recurring terms translated only once
Consistent renaming
When the problem is not the value but the material number itself.
- Rename and replace material masters system-wide
- Dependent objects across FI, CO, MM, SD, PM, PP and PLM
- Classification, long texts and document links included
- Complete before/after audit log
- Details at material-addon.com
Frequently asked questions
Is 30 characters still the limit in S/4HANA?
Not necessarily. Since SAP S/4HANA 1511 the ATWRT field holds 70 characters, but they can only be used if the system runs in target mode with field length extension activated (transaction FLETS). In compatibility mode, input in CT04 remains capped at 30 characters despite the 70-character field width.
How do we find out which mode our system runs in?
We check that as part of a short assessment. In our experience many S/4 systems still run in compatibility mode because interfaces, partner add-ons or custom programs cannot handle the extended fields — often without anyone being aware of it in daily business.
Do we still need your add-on at all?
Honest answer: not necessarily. If your system runs in target mode with field length extension active and 70 characters are enough, the standard covers it — and we will advise against buying. The add-on remains useful for SAP ECC, in compatibility mode, and when you need more than 70 characters. What is called for in that case has a different name: converting your existing values into the longer form.
We already have the longer fields — why would we still need support?
Because the longer fields are only the technical precondition. The data still carries the past: abbreviations, values spread across several characteristics, additional fields and Z tables created as workarounds. We analyse that inventory, convert the values into their full form, update dependent objects such as classification, variant tables and dependency knowledge, and dismantle the old workarounds in a controlled way — logged and repeatable rather than by hand.
Can the conversion run during live operation?
As a rule yes. We work with test runs on a copy, review the result together with your business department and then carry out the conversion in the target system in a traceable way. Scope and timing follow your processes, not the other way round.
Can the long characteristic values be searched?
Yes, searching across the extended value is part of the solution — a key difference to typical workarounds using long texts or additional characteristics.
Does the add-on modify the SAP standard?
No. It works without system modifications, enhancements and append fields, runs in the registered CaRD namespace and brings its own customising — release- and upgrade-friendly.
How quickly does the MMRI add-on pay off?
Experience shows: quickly. Recurring terms are translated only once and maintenance in known languages happens automatically — saving translation costs and maintenance effort with every material creation.
Does this match your project?
Talk directly to our consultants — no detours.