cancel
Showing results for 
Search instead for 
Did you mean: 

Material Segmentation fields are not editable in material master (S/4 Hana)

Amiran
Explorer

Hello,

In S/4 it is not possible to activate segmentation for material if this material has already been used in documents(Material document, Sales order, Purchase order and etc.). Segmentation functionality is activated (LOG_SEGMENTATION) and works fine in general. We experienced problems with materials that have been used previously. It's not possible to enter segmentation data not in MM02 and nor from SGT_SETUP transaction.

In ECC 6.0 EHP7 in similar situations, it is possible to activate segmentation for the material. the system creates a blank segment and assigns already existed batches to that blank segment.

This option was disabled in S/4 (as I understand). Transaction SGT_CONVERT_MATERIAL is disabled as well and included in the blocklist.

Please consult, what may be the reason for such restriction(why it was possible in EHP7 and is restricted in S/4), and can we have some workarounds in this situation?

Thank you very much

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hi Amiran,

we are facing the same issue in an S4CORE 104 SP002. Have you solved the issue?

Thank you!

Vladimir_Z
Explorer
0 Kudos

Please advise the message that you are facing when running tcode.

Lakshmipathi
Active Contributor
0 Kudos

Not sure whether it is disabled in S/4 Hana but as per OSS note 2594461, it should work if you carry out necessary code corrections as recommended therein.

Amiran
Explorer
0 Kudos

Thank you for your answer Lakshmipathi,

Unfortunately, this note is not compatible with my system (SCORE 104 SP 0002).

As I mention, in our system t-code SGT_CONVERT_MATERIAL is in the blocklist and this is due to standard functionality.

In previous versions it was possible to activate segmentation despite material was already in use and have stock, open orders and etc.

So, I need to understand the reasons/logic for such a decision from SAP and/or find workarounds.

Thanks,

Amiran