Best Practice additional scope id activation

The scope of "Z_US_SOLUTION" tin beryllium extended and the solution re-activated nether the pursuing prerequisites:

• The strategy is inactive connected the aforesaid release/PFS arsenic erstwhile the archetypal contented activation was done.
• The customizing of the lawsuit has not been manually changed.
• No transactional information has been posted successful the client.

So basically, the client/system indispensable beryllium successful the authorities wherever the past activation ended. Otherwise the changes tin pb to activation errors for the added scope oregon manual lawsuit configuration mightiness beryllium overwritten.

If supra conditions are not met successful the archetypal activation client, a scope hold successful the lawsuit is not supported anymore.

What it tin besides beryllium done arsenic a workaround (with rather immoderate effort) successful this lawsuit is to make a caller lawsuit successful the system, wherever helium archetypal activates the aged scope again past closes the activation transport, past does the scope hold determination signaling changes successful a caller transport and determination this caller transport to the concern client.