The AD impact analysis can now be triggered from AC custom ShiftLeft analyser (0075) previously (9009): Trigger AD Analysis. The analysis run name will be AD Triggered from AC in AD. Once the analysis run is completed in AD, the impact score will be available in the transport form if AC – AD is licensed and configured and will not be available in their related business tasks.
Please note that an analysis run is created for each individual transport even when the ShiftLeft analyser is triggered for a business task or multiple selected transport forms. For example, if analyser (0075) 9009 is executed for five transports, Five separate analysis runs will be created in AD.
It is recommended to run the analysis from test queue or outbox of DEV target. So the impact analysis will be running against the subsequent target(s) of dev system.
For example: If triggered from test queue or outbox of GBD – AD Development, analysis run will be created against GBP – AD Production.
Parameters
| AD_VERSION | Specify the version of AD installed(Supports AD 1.30 and higher) (Example value: 1.40) |
| IMPACT_SYST | Specify the source system (Example value: ABC) |
| LANDSCAPEID | Specify the landscape ID created in AD where the analysis run is needed (Example value: 0001) |
| RFC_AD_CENTAL_SYS | Specify the RFC destination of AD central system(Domain controller) if it is different to AC domain controller (Example value: TRANSPORT EXPRESS ABC) |
| USAGE_DATA_SYS | This will be by default the target if not specified. (Best practise: Keep empty) |
| USAGE_DAYS | This will be 30 days by default if not specified (Best practise: Keep empty) |
Post your comment on this topic.