Account Mapping

The columns listed below are required and must be present in all mappings. The names and case of the columns are automatically generated and should not be changed. The order of the columns does not matter. In addition to the columns below, many destinations will have additional columns in the mapping table that are specific to their data format. The information in the mappings specifies the physical transformation of source data into destination data.

•Mapping Key: This column contains the resolved values found in the source data corresponding to the Mapping Key Macro which was provided in the wizard or one of the below special tokens.

•DEF: This token is used to capture any line which does not need an individual mapping. This token can be mapped to DNT or any other macro command, which will map the lines captured by DEF to the resolved value of the macro.

•ALL: This token is used to map all source lines to a single mapping action, even if the individual lines have their own mappings. This token can be mapped to DNT, or any other macro command. This token should only be used in extreme circumstances. While DEF is used to capture any lines that are not mapped, ALL is used to capture all source lines, even if individual line mappings exist.

•Mapping Action: This column contains action for which the data should be handled.

•DNT: This token is used to designate a source lines as Do Not Transfer. Source lines that are mapped to DNT do not get transformed into destination data.

•Condition: Optionally you may see (or create) a column named Condition. If you do so you may enter a macro command that is used in addition to the above columns to further qualify whether a mapping is applied. If a macro expression is used it will be considered a match during application if the expression resolves to anything other than an empty (zero-length) string value. If used in conjunction with a wildcard expression (such as * for match all) in the source line field it allows for filtering based on values from the source other than the line code. Conditional mappings are applying during the first phase of mapping and are executed prior to the DEF token to ensure the DEF entries will still be appropriate in the event that the condition does not resolve to a non-empty string.

•Error: Optionally you may see (or create) a column named Error. If you do so you may enter a message (that may contain macro commands) that will be used to fail a transformation during the mapping phase if the mapping was applied to a journal line. Error entries are evaluated as the last step in the mapping phase and as such you can write rules to check amounts after allocations have been performed. If the expression in Error resolves and yields an empty (zero-length) string no error will be raised and the transformation will not be halted. During processing the Error macro expression will be resolved and replaced with the results if the execution. This ensures that only friendly error messages are displayed to the end user.

Send comments on this topic.

Created with an evaluation copy of HelpSmith.
To remove this notice, you should purchase the full version of the product.