Developing a cross scenario data change allows for controlled updates from child to parent scenarios, aligning with company policy on not adjusting lead times in shared scenarios.

To evaluate the impact of converting planned orders to scheduled receipts and then push changes to the parent scenario, while adhering to company policy that prohibits adjustments to lead times in shared scenarios:

Statement B:Develop a cross scenario data change. This will allow users to make their changes in their scenarios and then push these changes to the parent scenario. This method ensures that changes are captured and transferred correctly while adhering to the company’s policy regarding lead times.

References:

Scenario planning

Scenario planning capabilities in Kinaxis RapidResponse allow for testing changes in private scenarios before pushing them to shared ones1.

Change management

The Engineering Change Management application in RapidResponse supports evaluating the effect of changes and determining the optimal time for implementation, which can be adapted for evaluating the impact of converting planned orders2.

Kinaxis documentation suggests using scenarios to track changes and push them to parent scenarios without affecting system performance3.

Best practices in Kinaxis RapidResponse include maintaining the integrity of shared scenarios by not altering critical parameters like lead times45.