Location hierarchy separation

[markurius]

Hi experts,

Our EHSM location master data (S/4 1709) are currently synced/linked to asset/functional location hierarchy maintained in Plant Maintenance (PM) module. However, due to business process change, the asset/functional location hierarchy in Plant Maintenance will be split into 2 separate hierarchies but attributes such as company code and planning/maintenance plant ID are kept the same.

Just wondering what will be the impact of this hierarchy separation in PM, if any, to EHSM location master data? Is it possible to still keep one location master data hierarchy in EHSM? Or do we need to split EHMS location master data hierarchy to follow suit?

Many thanks.

Regards,

[nihal_nayak]

Can you elaborate how you are 'splitting' the hierarchy in PM?

[markurius]

Hi Nihal,

By splitting I mean a new hierarchy is created and some of the asset/functional location entries from current PM hierarchy is moved this new hierarchy. At the end of the day, there are 2 PM asset/functional location hierarchies.