Checking results of a simulation or import
After the simulation has been run or after an import has been performed, double-clicking on the import container will take you to the 'Import jobs' tab.
If you do not land in the tab 'Import jobs', then the container was not simulated or executed.
If the table is empty, you can see the cause in the tab 'Error log' (for more details see Managing Import jobs in chapter Status Model of import containers
In the tab 'Import jobs' you can see a high-level summary of the results.
In the field 'Mode' you can see whether a simulation or a productive import was performed. In this example a simulation was performed.
Using the Dropdown box in the field 'Run counter' you can also view previous runs if available.
In the table you can see one row for each target system of the import. The number of target systems corresponds to the definition of the corresponding import step in the delivery matrix.
In the 6th column (Requested requests) you see that 2 transport requests should be transported. In the 7th column (Relevant requests) you can see that Conigma has determined that only one transport request is required. Column 9 (Missing Transport Predecessors) and 10 (Overtakers) did not detect any relevant requests.
Use the button in column 10 (Additional info) to get further details about the import per target system. Another window appears with the following tabs.
In the 'General' tab you can see general administrative information. Among other things you can see the Job ID that you need for selection when diagnosing problems in the Job Monitor.
In the 'Error log' tab, you can see any messages that may have occurred. In most cases you will only see a success message here.
In the 'Request lists' tab you can see details about the individual transport requests.
Display of a simulated import
In the 1st column (Was requested) you see that 2 transport requests should be transported. In the 2nd column (Planned for import) you see that Conigma has recognized that only one transport is required.
Display of productive import
After executing an import, you can also see the actual TMS return code in the TMS-RC column. Of course, there is no TMS-RC in the simulation.
In the 1st column (Was requested) you see that 2 transport requests should be transported. In the 2nd column (Planned for import) you see that Conigma has recognized that both transport requests are required. Using the button in the column 'Maintain user return code' you can override the TMS return code with a user RC if necessary.
Use the last two buttons to view the transport log. The difference is that if you are not logged on to system D03 and there is no trusted RFC connection to this system you will get a login screen to log on. The last button shows in each case a textual extract from the transport log without login.
For more details, see also the Import container Imported requests tab on the upper level of the import container.
In the tab 'Import options' you can see the import options used during import.
In the tab 'Transitions' you can see the individual state transitions the import job has gone through in its status model.
The tab 'Missing Predecessors' shows a table of the missing transport predecessors identified by Conigma, which may become overtaken by requests that are not imported.
Ignored missing predecessors are not displayed by default. By removing the checkbox you can show ignored missing predecessors again.
The 'Export to Excel' button allows you to export these entries to Excel if required.
If you have configured your environment to send mails about missing predecessors, this table will also be displayed in the mail.
See also the following links
Detection of missing predecessors
Reaction to missing predecessors Reaction to missing predecessors
Ignore aborted comparisons for missing predecessors
In the tab 'Overtakers' you can see details about the overtakers detected by Conigma. These overtakers are often caused by pre-delivery transports of a not yet completely finished development and are intended to prevent unintentional downgrading by the currently requested transports.
Here an example with two overtakers and one missing predecessor.
One transport request was requested. However, Conigma's object analysis revealed that two additional transport requests with overlaps to this transport were detected.
The 'Export to Excel' button allows you to export these entries to Excel if required.
Click the 'Show overlapping objects' button to display another window. Here you can see which objects have overlapped in the transports.
Additionally in this example a missing predecessor was determined.
Details of the missing predecessor
See also the following links
Detection of overtakers
Minimum number of overtakers for user interaction
Ignore as predecessor when relation error occurs
In the tab 'Critical Objects' the critical objects defined in the TMS setup are checked and displayed.
The 'Export to Excel' button allows you to export these entries to Excel if required.
see also Ignore critical objects
In the tab 'Analyzer result' you can see further details about the relationships between the involved transports, including why Conigma determined a missing predecessor.
Here you can see all relations between the involved transport requests.
You can also export the results to Excel by clicking the corresponding button.
After setting the option 'Show only relevant entries' you will only see the lines that were relevant in the context of the current import.