|
Functionality in short
|
|
|
SEM3.ISS (demo version: SM3) finds all @IsIn()-matches
between two fields of two IDEA Files.
Main differences with other search macros on this site (SEMM, SEM2)
are the following:
|
| - |
SEM3 reads the strings to be searched from another IDEA database.
You can write the strings to be searched for e.g. in an Excel spreadsheet,
and import it to IDEA for the use of macro.
|
| - |
it searhes the whole strings provided by you in another IDEA file.
SEM3 does not search parts of them - like SEMM or SEM2.
|
| - |
SEM3 searhes strings shorter than three, too [1].
|
|
|
Why this macro was made?
|
|
|
An audit problem.
The macro is another solution in an audit problem described
- and solved - earlier on this web site:
how to join fields with same body but varying lengths.
|
|
|
SEM3 solution.
Official accont codes are imported to IDEA in a file ('IsFile').
A macro examines whether they
are included in the extended account codes of general ledger file ('InFile').
Whenever a match occurs information about it us written in a file;
that file can be imported to IDEA for inserting official codes in the general ledger file.
Finally, figures are summarized on that level.
|
|
|
Naturally, SEM3 can be used just for searching strings.
You can collect search key words e.g. in Excel sheet (or more of them),
import the sheet to IDEA, and use it as 'IsFile'.
Use SEM3 to examine, whether the collected key words
exist in any another IDEA file ('InFile').
|
|
|
Main techincal solutions/choices
|
|
|
There are some evident needs regarding effectiveness, efficiency and user-friendliness.
Solutions/choices to satisfy them need to be identified.
|
| - |
Only meaningful information should be searched for.
In search leading and trailing spaces are removed from the strings,
but spaces inside the string remain.
|
| - |
The contents are preferred to the form.
Users are privied with an option have the seached done without making difference,
whether a string (in 'IsFile' or 'InFile') is 'as is' or in uppercase.
The choice can be made in either of two field selection dialogs.
|
| - |
Work done should be minimized.
The list of searched strings ('IsFile') is made free from dublicates
[by means of summarization].
|
| - |
There should be a possibility to review match information and edit it
before using that information in further processing.
The match information includes record number of 'InFile',
and the official account code ('IsField').
It is written in an .CSV file that can be easily imported to IDEA for review and processing if needs arise.
|
| - |
User should have an 'next step' option.
He/she should be able to bring also another field from 'IsFile'
containing necessary information for analysis [1].
|
|
[1]
User might want e.g. to have make summarization using certain Codes (see below).
|
|
| Account code |
Account name |
Code |
| 030201 |
Operational expenses |
A |
| 030202 |
Constructing building, project #1 |
B |
| 030203 |
Constructing building, project #2 |
B |
| 030204 |
Aid scheme #1 |
C |
| 030205 |
Aid scheme #2 |
C |
| 030206 |
Aid scheme #3 |
C |
|