Layer Impacts¶
When code is customized, you override or overtake code from the Core or another lower layer. If you are about to lift the code in this other layer from one Update version to another, you need to verify that the overrides or overtakes you have in your Cust layer are not in conflict with the changes from the other layer. Such impacts are detected by the Layer impact analysis in IFS Update Analyzer.
More details about Code Layers can be studied here.
After the analysis is complete, the impact on the files are showed in the column Layer Impact in the main grid. For more detail information about each file, select Diff Viewer in the context menu
Layered Files¶
Customization files with extension like.cs, .plsql or.entity are examples of files that are considered as Layered Files, but all layered file types are mentioned in Settings Other. When analyzing Layered files, only the differences between Overrides and Overtakes are considered and not the entire file.
Note: If a file exists in the Modifications path, and if it’s a core file with layered support (instead of customization file), then the impact of such files will be analyzed as Non-Layered File. This situation typically occurs when you have single patched a CORE file which has layered support.
For a given Layered File in the Modification folder,
| If it exists in both of the Base Update and Target Update and if overtakes in Modification files has changed in between base version and target version of those files, | High Impact |
| If it exists in both of the base update and target update and if overrides in Modification files has changed in between base version and target version of those files, | Low Impact |
| If it doesn’t exists in any of the corresponding base update and target update or if overrides and overtakes in Modification files hasn’t changed in between base version and target version of those files, | No Impact |
| If it doesn’t exist either base file or target file | Unknown |
Non Layered Files¶
All the file types other than Layered Files are Non Layered Files. This includes binary files. When analyzing Layered file the entire files is compared.
For a given Non Layered File in the Modification folder,
| If it exists in both of the Base Update and Target Update and if that file has changed in between base and target version of that file | High Impact |
| If it doesn’t exist either base file or target file | Unknown |
| Else | No Impact |
Layer Impact Information¶
More information about Layer Impact will be shown in Layer Impact Info column. Following information will be shown where applicable,
| Information | Explanation |
|---|---|
| New file in Modification | File exist only in customization |
| File added in Target UPD | File exist in target UPD but does not exist in base UPD |
| File Not Found in Target UPD | File does not exist in target UPD but exist in base UPD |
| Corresponding Base and Target files do not exist but Overtakes found in customer file | Corresponding core file not found in base or target UPD but there are overtakes in Cust layer file |
| Overtaken Method(s) not found in Base and Target UPD files | Overtaken method(s) in Cust layer file not found in corresponding core files in base UPD and target UPD |
| Multiple overloaded methods found | There are multiple overloaded methods with same name in corresponding core files in base or target UPD, as the overridden/overtaken method |
| Found flagged methods | Found flagged methods |
| Only white space changes found | Only white space changes found |
| Target file is older than that of modified! | Binary file in target UPD is older than that of the Cust layer file |