Mapping script issue

Question

Hello experts,
I'm quite new to FDM and Iv'e been trying to write a simple conditional mapping script with no success. for my entity dimension, in most cases, the source is ths same as the target though there are some cases where this does not apply and have to go to a NA_Entity. For example:
SOURCE     TARGET
PE00_0001     PE00_0001
PE00_0002     PE00_0002
PE00_0003     PE00_0003
AL00_0001      NA_Entity
PE00_0004     PE00_0004
CO_HWE        NA_Entity
PE00_0005     PE00_0005
As you can see, all source entities which start with "PE" are equal to the target entity and any other entity not starting with PE should be mapped to the "NA_Entity". I believe it's pretty unefficient to maintain an explicit map so we've decided to create a conditional mapping script (not working yet) which reads as follows:
If Left(varValues(15),2)="PE"
     Then Result = varValues(15)
Else Result ="NA_Entity"
Every time i try to import a file I keep on getting:
Error: An error occurred importing the file.
Detail: Invalid Like Clause: For Dimension Map (ENTITY) and Rule (Peps)
ERROR:
Code............................................. 4026
Description...................................... Invalid Like Clause: For Dimension Map (ENTITY) and Rule (Peps)
Procedure........................................ clsImpProcessMgr.fLoadAndProcessFile
Component........................................ upsWObjectsDM
Version.......................................... 1112
Thread........................................... 5416
IDENTIFICATION:
User............................................. admin
Computer Name.................................... CTARESULDESA2
App Name......................................... INT_IECI
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLOLEDB
Data Server...................................... 10.228.128.168
Database Name.................................... FDM_INTIECI
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... Argentina-EP
Location ID...................................... 758
Location Seg..................................... 3
Category......................................... Reales
Category ID...................................... 13
Period........................................... Nov - 2013
Period ID........................................ 2013-11-30
POV Local........................................ False
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False
I've followed the script guide and Iv'e tried several scripts, all with no success. The only workaround I've found is maintaining an explicit map where 99% percent of the elements map to themselves and the other 1% map to "NA_Entity", not very maintenance friendly.
Thank you very much for your help
Santiago Ruiz.

Answer 1

You do not mention what release of FDM you are working with, but there should be no need for scripting .
Explicit mappings are the most efficient from a performance point of view, but in view of what you want to achieve then all you need are two 'Like' mapping entries.
the first will be mapping PE* to PE*  and the second entry mapping * to 'NA_Entity' to pick up all the other codes.
Alternatively if you are processing millions of records and have a performance issue, then an alternative might be to change the non 'PE' type records with a script on the import format, but i think the two records should be the easiest.