RobertP
7th April 2015, 13:42
Hello all,
In 5C great functionality exists in Service for Objects and Relations per configuration. It allows for 'Install base' to be migrated without the need for items to pre-exist - yet. Therefore in such cases the derived from item is left blank. The tool is great for loading 50 years of history without needing to actually migrate a zillion item codes.
Seems this has changed in LN. Under configuration management only service bom's can be created requiring item service data. No more objects and relations. Is this correct or have I missed something? If not, how can the 5C solution be achieved in LN? Perhaps in TP? What we need is a repository to store install base without real items. Then create items only as and when required
Thank in advance !
In 5C great functionality exists in Service for Objects and Relations per configuration. It allows for 'Install base' to be migrated without the need for items to pre-exist - yet. Therefore in such cases the derived from item is left blank. The tool is great for loading 50 years of history without needing to actually migrate a zillion item codes.
Seems this has changed in LN. Under configuration management only service bom's can be created requiring item service data. No more objects and relations. Is this correct or have I missed something? If not, how can the 5C solution be achieved in LN? Perhaps in TP? What we need is a repository to store install base without real items. Then create items only as and when required
Thank in advance !