Best practice for setting up new company in LN - Change management

unknown

Hi all,

I am new to LN and looking for best practice that other users are following when setting up new companies / entities.  We have set up a new company in our QA instance and had our users complete UAT.  I am somewhat flabbergasted to see that there is no way to move these changes from our QA instance to the PRD instance and that the company now needs to be manually re-created in our PRD instance.  I come from an SAP background where configuration changes are managed through transports - changes are first made and unit tested in a DEV environment, then promoted to QA for UAT, and once UAT is completed and changes approved, we released the transport to Production.  It appears there is no similar change management process for LN - is that correct?  How are others managing this process?

Thanks,

Michelle

ashok-kuppuswamy

Hi Michelle,

Yes

What we do is create those companies in Production - Refresh UAT from Production  - complete the testing and modify the configuration in Prod after compiling all results in UAT.

It is a gap and certainly a better candidate for ER. 

Lets ensure to endorse and get a proper solution from Infor.

Thanks