I'm trying to parse below address using MNS stage but City column is populated with incorect value.
MARTONVASAR H-2462 HUNGARY
After parsing:
City = MARTONVASAR H
country code = HU
Is there anything that needs to be done in MNS stage or before MNS stage to parse address ??
Address parsing issue with MNS stage
Hi,
MNS does not support Hungry. Please see http://publib.boulder.ibm.com/infocente ... d%6e%22%20 for a list of countries.
Your best bet may be to use Address Verification Interface (AVI). However, AVI is an additional cost component.
MNS does not support Hungry. Please see http://publib.boulder.ibm.com/infocente ... d%6e%22%20 for a list of countries.
Your best bet may be to use Address Verification Interface (AVI). However, AVI is an additional cost component.
Regards,
Robert
Robert
Hi,
MNS does not support Hungry. Please see http://publib.boulder.ibm.com/infocente ... d%6e%22%20 for a list of countries.
Your best bet may be to use Address Verification Interface (AVI). However, AVI is an additional cost component.
MNS does not support Hungry. Please see http://publib.boulder.ibm.com/infocente ... d%6e%22%20 for a list of countries.
Your best bet may be to use Address Verification Interface (AVI). However, AVI is an additional cost component.
Regards,
Robert
Robert
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You might look at an input pattern override. I presume that the H-2462 is a postal code of some kind. An input pattern override could parse this into a postal code field or discard it (whichever is appropriate).
You could edit the pattern-action language to achieve the same result, but that would mean you're creating a new rule set.
You could edit the pattern-action language to achieve the same result, but that would mean you're creating a new rule set.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.