Message code list of MAPPER category

Message codes corresponding to errors in Mapper.

MAPPER0001E

This message code is output when [Null option] is set to "Throw exception when unable to determine/calculate/process" in a logic that supports null option.

Cause Solution
An error occurred during processing of a logic whose [Null option] is set to "Throw exception when unable to determine/calculate/process". Check the [Null option] settings or the input data of the logic.

Corresponding error

MAPPER0002E

This message code is output when a Mapper logic is mapped to an unsupported type.

Cause Solution
The Mapper logic is mapped to an unsupported type (e.g. Mapper logic which returns boolean value is mapped to date type). Check the mapping.

Corresponding error

MAPPER0003E

This message code is output when data conversion inside Mapper logic failed.

Cause Solution
Data conversion failed due to some reason (e.g. character string in an invalid format is specified to date type). Check the mapping.

Corresponding error

MAPPER0004E

This message code is output when an error occurs in Encrypt/Decrypt logic.

Cause Solution
The key may be invalid. Check the logic settings and data of the input handlers.

Corresponding error

MAPPER0005E

This message code is output when [2 or more match records] is set to "Raise exception" in Replace by DB Table logic.

Cause Solution
Two or more matching records found. Check the logic settings and contents of the database.

Corresponding error

MAPPER0006E

This message code is output when [0 match record] is set to "Raise exception" in Replace by DB Table logic.

Cause Solution
No matching record found. Check the logic settings and the database contents.

Corresponding error

MAPPER0007E

This message code is output when a problem related to global custom logic occurs.

Cause Solution
The referent global custom logic does not exist. The referent global custom logic may have been deleted or not imported along with the project.
If the global custom logic is exported, import it from server migration.
The number of input handlers between the referrer and referent global custom logics does not match. Match the number of input handlers between the referrer and referent global custom logics.
The mapping of the referent global custom logic is invalid. Check the mapping of the referent global custom logic.

Corresponding error