Mapping Test
Introduction: You can find a description of this phase in section Phase 3 (Introduction).
You can test your mapping while you are creating your profile. You simply select a test file and check the mapping results.
SQL functions in phase 3 will be executed, but the SQL statements of phase 4 (SQL nodes) will not be executed (but can be logged). The Integration Unit will not be executed. Response Routes will not be executed.
The mapping settings can be checked here as well. If you check without warnings, nothing is displayed if there are no errors. If you check with warnings, warnings are displayed if there are no errors. If there are errors, errors and warnings will be displayed for both options.
You can also restart the profile.
Test File
(1) Here you will find a list of available test files. You can simply drag and drop new test files. If you are using Input Agent DB, you can use option Execute SQL and save result with a right-click, which allows you to specify the number of lines that are read from the database and then saved as a test file. If you do not have a test file available, you can use option (2). Note: If the profile has the document type EDIFACT and you have an EDIFACT test file, you can use the context menu to create an analysis report of that file.
(2) Backup files from a previous job of this profile can also be selected for testing. Important note: System variables of the affected job as well as variables with prefix MSG_CALL_ will be available. This is helpful if the job was triggered from the outside or if it received data via Message. Please note that the variables, e.g. the system variable VAR_TIMESTAMP, always get the value of the original job.
(3) If you mark one of the files (1), you can start the test.
Test Results
(1) The target structure filled with data (the target tree). For the data history, also see tab Log and tab Lists/Maps/Variables (per record).
(2) See section Settings (Mapping Test).
(3) Here you can see the contents of lists, maps and variables.
(4) Here data of called subprofiles is displayed (per record). See section Adding Profile as Subnode in Source Structure (Sub Profile).
(5) See function create snapshot(a,b).
(6) See section Replacement Values for Functions.