You are here: Definitions>Spanish Definitions>Spanish, Mexico Definitions

SAS Quality Knowledge Base for Contact Information 25

Spanish, Mexico Definitions

Definitions for the Spanish, Mexico locale are described below.

Case Definitions
Gender Analysis Definitions
Identification Analysis Definitions
Match Definitions
Parse Definitions
Pattern Analysis Definitions
Standardization Definitions
Inherited Definitions

Case Definitions

Proper (City - State/Province - Postal Code)
Description	The Proper (City - State/Province - Postal Code ) case definition propercases last line address information.
	Input	Output
Example	77520 cancun, q. roo	77520 Cancun, Q. Roo
Remarks

Proper (Organization)
Description	The Proper (Organization) case definition propercases organization names.
	Input	Output
Examples	diconsa sa de cv	Diconsa SA de CV
Examples	sas institute	SAS Institute
Remarks	The Proper (Organization) case definition uses a list of known organization names to handle exceptions to propercasing rules.

Gender Analysis Definitions

CURP
Description	The CURP gender analysis definition determines the gender of an individual based on their Unique Population Registry Code (Clave Única de Registro de Población).
Possible Outputs	M F U
	Input	Output
Examples	ZAZD801124MBSYQN13	F
	NURV140413HQTWGN12	M
	NURV140413XQTWGN12	U
Remarks	The CURP gender analysis definition is designed to provide valid results when operating on valid CURP identity codes. It is recommended that you use the CURP (Validation) identification analysis definition to validate your input and that you pass only valid CURP identity codes into the CURP gender analysis definition. Results from invalid data cannot be guaranteed to be accurate.

Name
Description	The Name gender analysis definition determines the gender of a name.
Possible Outputs	M F U
	Input	Output
Examples	Guadalupe Salvador Rivera	U
	Jose Maria Rivera Morales	M
	Maria De Lourdes Rodriguez	F
Remarks	If this definition is applied to pre-parsed data, the following input tokens are available: Prefix Given Name Family Name 1 Family Name 2 Suffix Title/Additional Info It is recommended that you map a correlating data field to each available token whenever possible.

Identification Analysis Definitions

CURP (Validation)
Description	The CURP (Validation) identification analysis definition determines if a string is a Unique Population Registry Code (Clave Única de Registro de Población).
Possible Outputs	VALID INVALID
	Input	Output	Comments
Examples	ZAZD801124MBSYQN13	VALID
	RUNO390705HSLPTC02	VALID
	IMS120607120	INVALID	Too short (only 12 characters)
	KAOB750230MASLHJ07	INVALID	Invalid date (Feb 30)
	EOMR330613FDFPKT08	INVALID	Invalid gender (F instead of H or M)
	YOOR280801HXXLTK07	INVALID	Invalid state (XX is not a state)
	EIMV310211MQRPKT1X	INVALID	Invalid last character (X instead of a value 0-9)
	L6NF640805MYNTNN10	INVALID	Invalid second character (6 instead of an A-Z value)
	MOJL020101HCLKWMXY09	INVALID	Too long (over 18 characters)
Remarks	This definition validates on the following criteria: The string is exactly 18 characters in length. Characters 1-4 are alphabetic characters (A-Z, a-z), in a combination that is not deemed offensive. Characters 5-10 are a valid date in YYMMDD format. Character 11 is either H or M, representing the male or female gender respectively. Characters 12-13 are a valid 2-letter Mexican state code, or "NE" for individuals who are foreign-born. Characters 14-16 are alphabetic (A-Z, a-z). Character 17 is alphanumeric (0-9, A-Z, a-z). Character 18 is numeric (0-9).

Individual/Organization
Description	The Individual/Organization identification analysis definition determines whether a string represents the name of an individual or an organization.
Possible Outputs	INDIVIDUAL ORGANIZATION UNKNOWN
	Input	Output
Examples	Grupo Dixon S.A.	ORGANIZATION
	Roberto Cruz Morales	INDIVIDUAL
	Marta Leticia Ceballos Gomez	INDIVIDUAL
	Guttermoth	UNKNOWN
Remarks

Individual/Organization (RFC)
Description	The Individual/Organization (RFC) identification analysis definition determines the identify of an individual or organization based on their Federal Taxpayer Registry Code (Registro Federal de Contribuyentes).
Possible Outputs	INDIVIDUAL ORGANIZATION UNKNOWN
	Input	Output
Examples	ABC680524F23	ORGANIZATION
	VECJ680524V23	INDIVIDUAL
	ABCDE12345678	UNKNOWN
	H1N831130GD9	UNKNOWN
	PIA850230ZVA	UNKNOWN
	BEPJ361225IS@	UNKNOWN
Remarks	This definition validates using the following criteria: For organizations and individuals the string is either 12 or 13 characters in length. The string length determines if the entity is an individual or organization. The first 3 (for 12-character strings) or 4 characters (for 13-character strings) are alphabetic characters (A-Z, a-z), with a combination that is not deemed to be offensive. The following 6 characters are a valid date in YYMMDD format. The last 3 characters are alphanumeric characters (A-Z, a-z, 0-9).

Match Definitions

Address
Description	The Address match definition generates match codes which can be used to cluster records containing addresses.
Max Length of Match Code	20 characters
	Input	Cluster ID
Examples	Av Los Angeles num 325 Ote	1
	Ave. Los Angeles 325Ote.	1
	Ave Las Angeles #325 Oriente	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).
Remarks	The Address (v24) match definition is a temporary definition provided to facilitate an upgrade of the Address definition. The Address definition accepts parsed input, but this will be changed in a future release. Address (v24) does not accept parsed input, which will also be true of Address in the future. The token change will require you to update any jobs using the Match Codes (Parsed) node for the Address definition, using the non-parsed Match Codes node, and providing input as a single field. Jobs using the non-parsed input Match Codes node will not require an update. In addition, the match code length will be changed. This change might require you to update any jobs using the Address definition so that the match code fields can handle the new length. The Address (v24) definition uses the match code length that will be used by Address in the future. If you want to begin using the updated processing now rather than waiting for a later release, you can update your jobs to call the Address (v24) definition. Be aware however that the Address (v24) definition will be deprecated in a subsequent release after the Address definition has been updated.

Address (Full)
Description	The Address (Full) match definition generates match codes which can be used to cluster records containing complete two-line addresses.
Max Length of Match Code	118 characters
	Input	Cluster ID
Examples	Av Independencia 800 Bario De San Agustin Municipio De Jalatlaco CP 05286 Edo De Mexico	0
	Avenida Independencia 800 Bario De San Agustin Municipio De Jalatlaco CP 05286 Edo De Mexico	0
	Avenida Independencia 800 Bario De San Agustin Municipio De Jalatlaco CP 5286 Edo De Mexico	0
	Av Independencia #800 Bario De San Agustin Municipio De Jalatlaco CP 5286 Edo De Mexico	0
	Calle Insurgentes 9908 APDO POSTAL 1329	1
	Av Insurgentes 9908 APDO POSTAL 1329	1
	Torre Mayor Condominio horizontal 200, 82200 Mazatlan, Sinaloa	2
	Torre Mayor Condominio horizontal 200, 82200 Mazatlan de Norte, Sinaloa	2
	Torre Mayor Condominio horizontal 200, 82200 Mazatlan de sur, Sinaloa	2
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Address (PO Box Only)
Description	The Address (PO Box Only) match definition generates match codes which can be used to cluster records containing the PO Box portion of an address.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	APDO POSTAL 1329, Avenida Insurgentes #325	0
	APDO POSTAL 1329, Avenida Insurgentes 123	0
	Ave. Insurgentes 325 APDO POSTAL #1329	0
	APDO POSTAL 1329	0
	APDO 345	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Address (Street Only)
Description	The Address (Street Only) match definition generates match codes which can be used to cluster records containing the street portion of an address.
Max Length of Match Code	68 characters
	Input	Cluster ID
Examples	Av Insurgentes num 325	0
	Ave. Insurgentes 325	0
	Avenida Insurgentes #325	0
	APDO POSTAL 1329, Avenida Insurgentes #325	0
	Ave. Insurgentes 325 APDO POSTAL 1329	0
	Ave. Universidad 1200	1
	Ave. Universidad No. 1200	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Address (v24)
Description	The Address (v24) match definition generates match codes which can be used to cluster records containing addresses.
Max Length of Match Code	68 characters
	Input	Cluster ID
Examples	Av Insurgentes num 325	0
	Ave. Insurgentes 325	0
	Avenida Insurgentes #325	0
	APDO POSTAL 1329, Calle Insurgentes 9908	1
	Calle Insurgentes 9908 APDO POSTAL 1329	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).
Remarks	The Address (v24) match definition is a temporary definition provided to facilitate an upgrade of the Address definition. The Address definition accepts parsed input, but this will be changed in a future release. Address (v24) does not accept parsed input, which will also be true of Address in the future. The token change will require you to update any jobs using the Match Codes (Parsed) node for the Address definition, using the non-parsed Match Codes node, and providing input as a single field. Jobs using the non-parsed input Match Codes node will not require an update. In addition, the match code length will be changed. This change might require you to update any jobs using the Address definition so that the match code fields can handle the new length. The Address (v24) definition uses the match code length that will be used by Address in the future. If you want to begin using the updated processing now rather than waiting for a later release, you can update your jobs to call the Address (v24) definition. Be aware however that the Address (v24) definition will be deprecated in a subsequent release after the Address definition has been updated.

City
Description	The City match definition generates match codes which can be used to cluster records containing city names.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	Acaspulco	1
	Acasppulco	1
	Mexico City	2
Remarks	Note: The results listed above reflect the default match sensitivity (85).

City - State/Province - Postal Code
Description	The City - State/Province - Postal Code match definition generates match codes which can be used to cluster records containing last line address information.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	11570 Distrito Federal, Mexico	1
	Mexico Distrito Federal, CP 11570	1
	11570 DF Mexico	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Name
Description	The Name match definition generates match codes which can be used to cluster records containing names of individuals.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	Imelda Marina Escobar Hernandez	0
	Sra Imelda Escobar Hernandez	0
	Excel·lentíssim i Magnífic Senyor Marcel·lí J. Rigau i Molins	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).
	If this definition is applied to pre-parsed data, the following input tokens are available: Name Prefix Given Name First Family Name Second Family Name It is recommended that you map a correlating data field to each available token whenever possible.
	The Name (v24) match definition is a temporary definition provided to facilitate an upgrade of the Name definition. The Name definition accepts parsed input and the input tokens will be changed in a future release. Name (v24) uses the tokens that will be used by Name in the future. The token change will require you to update any jobs using the Match Codes (Parsed) node for the Name definition so that the tokens specified in that node will match the tokens used by the definition. Jobs using the non-parsed input Match Codes node will not require an update. In addition, the match code length will be changed. This change might require you to update any jobs using the Name definition so that the match code fields can handle the new length. The Name (v24) definition uses the match code length that will be used by Name in the future. If you want to begin using the new tokens or the updated processing now rather than waiting for a later release, you can update your jobs to call the Name (v24) definition. Be aware however that the Name (v24) definition will be deprecated in a subsequent release after the Name definition has been updated.

Name (v24)
Description	The Name (v24) match definition generates match codes which can be used to cluster records containing names of individuals.
Max Length of Match Code	27 characters
	Input	Cluster ID
Examples	Imelda Marina Escobar Hernandez	0
	Sra Imelda Escobar Hernandez	0
	Excel·lentíssim i Magnífic Senyor Marcel·lí J. Rigau i Molins	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).
	If this definition is applied to pre-parsed data, the following input tokens are available: Prefix Given Name Family Name 1 Family Name 2 Suffix Title/Additional Info It is recommended that you map a correlating data field to each available token whenever possible.
	The Name (v24) match definition is a temporary definition provided to facilitate an upgrade of the Name definition. The Name definition accepts parsed input and the input tokens will be changed in a future release. Name (v24) uses the tokens that will be used by Name in the future. The token change will require you to update any jobs using the Match Codes (Parsed) node for the Name definition so that the tokens specified in that node will match the tokens used by the definition. Jobs using the non-parsed input Match Codes node will not require an update. In addition, the match code length will be changed. This change might require you to update any jobs using the Name definition so that the match code fields can handle the new length. The Name (v24) definition uses the match code length that will be used by Name in the future. If you want to begin using the new tokens or the updated processing now rather than waiting for a later release, you can update your jobs to call the Name (v24) definition. Be aware however that the Name (v24) definition will be deprecated in a subsequent release after the Name definition has been updated.

Organization
Description	The Organization match definition generates match codes which can be used to cluster records containing organization names.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	Agroasemex SA	1
	Agroasemex	1
	SAS Institute	2
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Phone
Description	The Phone match definition generates match codes which can be used to cluster records containing phone numbers.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	+52 (55) 5122 4300	1
	52-55-5122-4300	1
	52-55-51224300	1
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Postal Code
Description	The Postal Code match definition generates match codes which can be used to cluster records containing postal codes.
Max Length of Match Code	15 characters
	Input	Cluster ID
Examples	11570	1
	-11570	1
	13210	2
Remarks	Note: The results listed above reflect the default match sensitivity (85).

Parse Definitions

Address
Description	The Address parse definition parses addresses into a set of tokens.
Output Tokens	Recipient Building/Site Street Extension PO Box Additional Info
	Input	Output
Example 1	Paseo de la Reforma 505 Piso 38	Recipient
		Building/Site
		Street	Paseo de la Reforma 505
		Extension	Piso 38
		PO Box
		Additional Info
	Input	Output
Example 2	Hospital General de México, Calle Dr. Balmis No. 148	Recipient
		Building/Site	Hospital General de México
		Street	Calle Dr. Balmis No. 148
		Extension
		PO Box
		Additional Info
	Input	Output
Example 3	A/A: Linda Salcido AV INDEPENDENCIA 800	Recipient	A/A: Linda Salcido
		Building/Site
		Street	AV INDEPENDENCIA 800
		Extension
		PO Box
		Additional Info
Remarks	The Address (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Address parse definition has been replaced with a copy of the Address (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Address (v23) it is suggested that you change them back.

Address (Full)
Description	The Address (Full) parse definition parses addresses containing complete two-line addresses into a set of tokens.
Output Tokens	Recipient Building/Site Street Extension PO Box Neighborhood/Village Delegation/Municipality State/Province Postal Code Country Additional Info
	Input	Output
Example 1	Paseo de la Reforma 505 Piso 38 Del. Cuauhtémoc C.P. 06500 México, D.F.	Recipient
		Building/Site
		Street	Paseo de la Reforma 505
		Extension	Piso 38
		PO Box
		Neighborhood/Village
		Delegation/Municipality	Del. Cuauhtémoc
		State/Province	México, D.F.
		Postal Code	C.P. 06500
		Country
		Additional Info
	Input	Output
Example 2	Hospital General de México, Calle Dr. Balmis No. 148, Col. Doctores, Delegacion Cuauhtemoc, Mexico, D.F., C.P. 06726	Recipient
		Building/Site	Hospital General de México
		Street	Calle Dr. Balmis No. 148
		Extension
		PO Box
		Neighborhood/Village	Col. Doctores
		Delegation/Municipality	Delegacion Cuauhtemoc
		State/Province	México, D.F.
		Postal Code	C.P. 06726
		Country
		Additional Info
	Input	Output
Example 3	A/A: Linda Salcido AV INDEPENDENCIA 800 BARIO DE SAN AGUSTIN MUNICIPIO DE JALATLACO CP 52860 EDO DE MEXICO	Recipient	A/A: Linda Salcido
		Building/Site
		Street	AV INDEPENDENCIA 800
		Extension
		PO Box
		Neighborhood/Village	BARIO DE SAN AGUSTIN
		Delegation/Municipality	MUNICIPIO DE JALATLACO
		State/Province	EDO DE MEXICO
		Postal Code	CP 52860
		Country
		Additional Info
Remarks

Address (Global)
Description	The Address (Global) parse definition parses addresses into a globally recognized set of tokens.
Output Tokens	Recipient Building/Site Street Extension PO Box Additional Info
	Input	Output
Example 1	Paseo de la Reforma 505 Piso 38	Recipient
		Building/Site
		Street	Paseo de la Reforma 505
		Extension	Piso 38
		PO Box
		Additional Info
	Input	Output
Example 2	Hospital General de México, Calle Dr. Balmis No. 148	Recipient
		Building/Site	Hospital General de México
		Street	Calle Dr. Balmis No. 148
		Extension
		PO Box
		Additional Info
	Input	Output
Example 3	A/A: Linda Salcido AV INDEPENDENCIA 800	Recipient	A/A: Linda Salcido
		Building/Site
		Street	AV INDEPENDENCIA 800
		Extension
		PO Box
		Additional Info
Remarks	Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.
Remarks	The Address (Global) (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Address (Global) parse definition has been replaced with a copy of the Address (Global) (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Address (Global) (v23) it is suggested that you change them back.

Address (Global) (v23)
Description	The Address (Global) (v23) parse definition parses addresses into a globally recognized set of tokens.
Output Tokens	Recipient Building/Site Street Extension PO Box Additional Info
	Input	Output
Example 1	Paseo de la Reforma 505 Piso 38	Recipient
		Building/Site
		Street	Paseo de la Reforma 505
		Extension	Piso 38
		PO Box
		Additional Info
	Input	Output
Example 2	Hospital General de México, Calle Dr. Balmis No. 148	Recipient
		Building/Site	Hospital General de México
		Street	Calle Dr. Balmis No. 148
		Extension
		PO Box
		Additional Info
	Input	Output
Example 3	A/A: Linda Salcido AV INDEPENDENCIA 800	Recipient	A/A: Linda Salcido
		Building/Site
		Street	AV INDEPENDENCIA 800
		Extension
		PO Box
		Additional Info
Remarks	Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.
Remarks	The Address (Global) (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Address (Global) parse definition has been replaced with a copy of the Address (Global) (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Address (Global) (v23) it is suggested that you change them back.

Address (v23)
Description	The Address (v23) parse definition parses addresses into a set of tokens.
Output Tokens	Recipient Building/Site Street Extension PO Box Additional Info
	Input	Output
Example 1	Paseo de la Reforma 505 Piso 38	Recipient
		Building/Site
		Street	Paseo de la Reforma 505
		Extension	Piso 38
		PO Box
		Additional Info
	Input	Output
Example 2	Hospital General de México, Calle Dr. Balmis No. 148	Recipient
		Building/Site	Hospital General de México
		Street	Calle Dr. Balmis No. 148
		Extension
		PO Box
		Additional Info
	Input	Output
Example 3	A/A: Linda Salcido AV INDEPENDENCIA 800	Recipient	A/A: Linda Salcido
		Building/Site
		Street	AV INDEPENDENCIA 800
		Extension
		PO Box
		Additional Info
Remarks	The Address (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Address parse definition has been replaced with a copy of the Address (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Address (v23) it is suggested that you change them back.

City - State/Province - Postal Code
Description	The City - State/Province - Postal Code parse definition parses last line address information into a set of tokens.
Output Tokens	City Province Postal Code Municipio/Delegación
	Input	Output
Example	11570 Mexico, DF	City	Mexico
		Province	DF
		Postal Code	11570
		Municipio/Delegación
Remarks

City - State/Province - Postal Code (Global)
Description	The City - State/Province - Postal Code (Global) parse definition parses last line address information into a globally recognized set of tokens.
Output Tokens	City State/Province Postal Code Additional Info
	Input	Output
Example	11570 Mexico, DF	City	Mexico
		State/Province	DF
		Postal Code	11570
		Additional Info
Remarks	Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.

Name
Description	The Name parse definition parses names of individuals into a set of tokens.
Output Tokens	Prefix Given Name Family Name 1 Family Name 2 Suffix Title/Additional Info
	Input	Output
Example 1	Dr. Juan Carlos Lopez	Prefix	Dr.
		Given Name	Juan Carlos
		Family Name 1	Lopez
		Family Name 2
		Suffix
		Title/Additional Info
	Input	Output
Example 2	Maria Julia Garcia Arroyo	Prefix
		Given Name	Maria Julia
		Family Name 1	Garcia
		Family Name 2	Arroyo
		Suffix
		Title/Additional Info
	Input	Output
Example 3	Mr John D'Onofrio Jr, CEO	Prefix	Mr
		Given Name	John
		Family Name 1	D'Onofrio
		Family Name 2
		Suffix	Jr
		Title/Additional Info	CEO
Remarks	The Name (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Name parse definition has been replaced with a copy of the Name (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Name (v23) it is suggested that you change them back.

Name (Global)
Description	The Name (Global) parse definition parses names of individuals into a globally recognized set of tokens.
Output Tokens	Prefix Given Name Middle Name Family Name Suffix Title/Additional Info
	Input	Output
Example 1	Dr. Juan Carlos Lopez	Prefix	Dr.
		Given Name	Juan Carlos
		Middle Name
		Family Name	Lopez
		Suffix
		Title/Additional Info
	Input	Output
Example 2	Maria Julia Garcia Arroyo	Prefix
		Given Name	Maria Julia
		Middle Name
		Family Name	Garcia Arroyo
		Suffix
		Title/Additional Info
	Input	Output
Example 3	Sr. Juan Gomez Gonzales Prof	Prefix	Sr.
		Given Name	Juan
		Middle Name
		Family Name	Gomez Gonzales
		Suffix
		Title/Additional Info	Prof
Remarks	Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.

Name (v23)
Description	The Name (v23) parse definition parses names of individuals into a set of tokens.
Output Tokens	Prefix Given Name Family Name 1 Family Name 2 Suffix Title/Additional Info
	Input	Output
Example 1	Dr. Juan Carlos Lopez	Prefix	Dr.
		Given Name	Juan Carlos
		Family Name 1	Lopez
		Family Name 2
		Suffix
		Title/Additional Info
	Input	Output
Example 2	Maria Julia Garcia Arroyo	Prefix
		Given Name	Maria Julia
		Family Name 1	Garcia
		Family Name 2	Arroyo
		Suffix
		Title/Additional Info
	Input	Output
Example 3	Mr John D'Onofrio Jr, CEO	Prefix	Mr
		Given Name	John
		Family Name 1	D'Onofrio
		Family Name 2
		Suffix	Jr
		Title/Additional Info	CEO
Remarks	The Name (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Name parse definition has been replaced with a copy of the Name (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Name (v23) it is suggested that you change them back.

Organization
Description	The Organization parse definition parses company and organization information into a set of tokens.
Output Tokens	Organization Legal Form Site
	Input	Output
Example 1	Grupo Carso S.A. de C.V.	Organization	Grupo Carso
		Legal Form	S.A. de C.V.
		Site
Remarks	The Organization (v24) parse definition is a temporary definition provided to facilitate an upgrade of the Organization definition. In a future release, the output tokens of the Organization definition will be changed. This change will require you to update any jobs using the Organization definition so that the tokens specified in those jobs will match the tokens used by the definition. The Organization (v24) definition uses the tokens that will be used by Organization in the future. If you want to begin using the new tokens and updated processing now rather than waiting for a later release, you can update your jobs to call the Organization (v24) definition. Be aware however that the Organization (v24) definition will be deprecated in a subsequent release after the Organization definition has been updated.

Organization (v24)
Description	The Organization (v24) parse definition parses company and organization information into a set of tokens.
Output Tokens	Name Legal Form Site Additional Info
	Input	Output
Example 1	Grupo Carso S.A. de C.V.	Name	Grupo Carso
		Legal Form	S.A. de C.V.
		Site
		Additional Info
	Input	Output
Example 2	CEPSA SA CHIHUAHUA - Compañía Española de Petróleos	Name	CEPSA
		Legal Form	SA
		Site	CHIHUAHUA
		Additional Info	Compañía Española de Petróleos
	Input	Output
Example 3	Hewlett Packard Española SL, Barcelona	Name	Hewlett Packard Española
		Legal Form	SL
		Site	Barcelona
		Additional Info
	Input	Output
Example 4	BBV TITULIZACION, S.A. (S.G.F.T.H.)	Name	BBV TITULIZACION
		Legal Form	S.A.
		Site
		Additional Info	(S.G.F.T.H.)
Remarks	The Organization (v24) parse definition is a temporary definition provided to facilitate an upgrade of the Organization definition. In a future release, the output tokens of the Organization definition will be changed. This change will require you to update any jobs using the Organization definition so that the tokens specified in those jobs will match the tokens used by the definition. The Organization (v24) definition uses the tokens that will be used by Organization in the future. If you want to begin using the new tokens and updated processing now rather than waiting for a later release, you can update your jobs to call the Organization (v24) definition. Be aware however that the Organization (v24) definition will be deprecated in a subsequent release after the Organization definition has been updated.

Phone
Description	The Phone parse definition parses phone numbers into a set of tokens.
Output Tokens	Prefix Country Code Area Code Base Number Extension Line Type Additional Info
	Input	Output
Example 1	52 5521234567	Prefix
		Country Code	52
		Area Code	55
		Base Number	21234567
		Extension
		Line Type
		Additional Info
	Input	Output
Example 2	044 5521234567	Prefix	044
		Country Code
		Area Code	55
		Base Number	21234567
		Extension
		Line Type
		Additional Info
	Input	Output
Example 3	Oficina: 55 2123 4567 ext 156	Prefix
		Country Code
		Area Code	55
		Base Number	2123 4567
		Extension	156
		Line Type	Oficina:
		Additional Info
	Input	Output
Example 4	Movil: 55 2123 4567 (noches)	Prefix
		Country Code
		Area Code	55
		Base Number	2123 4567
		Extension
		Line Type	Movil:
		Additional Info	(noches)
Remarks	The Prefix token will contain the domestic long-distance dialing code (01), the domestic cellular dialing codes (044 and 045), and their accepted variants.
Remarks	The Phone (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Phone parse definition has been replaced with a copy of the Phone (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Phone (v23) it is suggested that you change them back.

Phone (Global)
Description	The Phone (Global) parse definition parses phone numbers into a globally recognized set of tokens.
Output Tokens	Country Code Area Code Base Number Extension Line Type Additional Info
	Input	Output
Example	+52 (55) 5122 4300	Country Code	52
		Area Code	55
		Base Number	51224300
		Extension
		Line Type
		Additional Info
Remarks	Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.

Phone (IFETEL)
Description	The Phone (IFETEL) parse definition parses an IFETEL-compliant phone number into a set of tokens.
Output Tokens	Prefix Country Code Cellular Code LADA Serie Numero Extension Additional Info
	Input	Output
Example 1	520442432604890	Prefix
		Country Code	52
		Cellular Code	044
		LADA	243
		Serie	260
		Numero	4890
		Extension
		Additional Info
	Input	Output
Example 2	013323456789	Prefix	01
		Country Code
		Cellular Code
		LADA	33
		Serie	2345
		Numero	6789
		Extension
		Additional Info
	Input	Output
Example 3	8162047148 ext 304	Prefix
		Country Code
		Cellular Code
		LADA	81
		Serie	6204
		Numero	7148
		Extension	304
		Additional Info
	Input	Output
Example 4	234 234 5678901	Prefix
		Country Code
		Cellular Code
		LADA
		Serie
		Numero
		Extension
		Additional Info	2 3 4 2 3 4 5 6 7 8 9 0 1
Remarks	The input string for Example 4 contains too many digits for IFETEL compliance.
	The Phone (IFETEL) definition is specific to the Spanish, Mexico locale. The purpose of the definition is to separate a telephone number into the tokens used by the IFETEL national phone number registry. If the input string does not contain a Mexican phone number in IFETEL-compliant format, the output will have a NO SOLUTION parse result and the input string will be output in the Additional Info token as shown in Example 4, with spaces between the digits. The recommended procedure is to use the Result code field in the Parse node of your Data Job to store the results of the parsing operation. Then the data job should use the value of the Result code field to determine how the record should be processed. Records with an "OK" Result Code should be processed as valid IFETEL phone numbers. Those with a "NO SOLUTION" or "NULL" Result Code should be processed separately, if it all.

Phone (v23)
Description	The Phone (v23) parse definition parses phone numbers into a set of tokens.
Output Tokens	Prefix Country Code Area Code Base Number Extension Line Type Additional Info
	Input	Output
Example 1	52 5521234567	Prefix
		Country Code	52
		Area Code	55
		Base Number	21234567
		Extension
		Line Type
		Additional Info
	Input	Output
Example 2	044 5521234567	Prefix	044
		Country Code
		Area Code	55
		Base Number	21234567
		Extension
		Line Type
		Additional Info
	Input	Output
Example 3	Oficina: 55 2123 4567 ext 156	Prefix
		Country Code
		Area Code	55
		Base Number	2123 4567
		Extension	156
		Line Type	Oficina:
		Additional Info
	Input	Output
Example 4	Movil: 55 2123 4567 (noches)	Prefix
		Country Code
		Area Code	55
		Base Number	2123 4567
		Extension
		Line Type	Movil:
		Additional Info	(noches)
Remarks	The Prefix token will contain the domestic long-distance dialing code (01), the domestic cellular dialing codes (044 and 045), and their accepted variants.
Remarks	The Phone (v23) parse definition is now deprecated and will be removed in a future release of the QKB. The Phone parse definition has been replaced with a copy of the Phone (v23) definition which takes advantage of the new tokens and updated processing. If you changed your jobs to use Phone (v23) it is suggested that you change them back.

Pattern Analysis Definitions

None.

Standardization Definitions

Address
Description	The Address standardization definition standardizes addresses.
	Input	Output
Examples	Paseo de la Reforma 76 1ER PISO	Pso de la Reforma 76 1er Piso
Examples	Avenida Hidalgo 1524 Colonia Cordoba Americas	Av Hidalgo 1524 Col Cordoba Americas
Remarks	The Address (v24) standardization definition is a temporary definition provided to facilitate an upgrade of the Address definition. The Address definition accepts parsed input, but will not accept parsed input in a future release. Address (v24) does not accept parsed input, which will also be true of Address in the future. The removal of input tokens will require you to update any jobs using the Standardization (Parsed) node for the Address definition, replacing the Standardization (Parsed) node with the Standardization node and providing input as a single field. Jobs using the Standardization node will not require an update. If you want to begin using the updated processing now rather than waiting for a later release, you can update your jobs to call the Address (v24) definition. Be aware however that the Address (v24) definition will be deprecated in a subsequent release after the Address definition has been updated.

Address (v24)
Description	The Address (v24) standardization definition standardizes addresses.
	Input	Output
Examples	Pso de la Reforma 76 Tercero Piso	Paseo de la Reforma 76, Piso 3
Examples	Av Hidalgo 1524 Col Cordoba Americas	Avenida Hidalgo 1524 (Col Cordoba Americas)
Remarks	The Address (v24) standardization definition is a temporary definition provided to facilitate an upgrade of the Address definition. The Address definition accepts parsed input, but will not accept parsed input in a future release. Address (v24) does not accept parsed input, which will also be true of Address in the future. The removal of input tokens will require you to update any jobs using the Standardization (Parsed) node for the Address definition, replacing the Standardization (Parsed) node with the Standardization node and providing input as a single field. Jobs using the Standardization node will not require an update. If you want to begin using the updated processing now rather than waiting for a later release, you can update your jobs to call the Address (v24) definition. Be aware however that the Address (v24) definition will be deprecated in a subsequent release after the Address definition has been updated.

City
Description	The City standardization definition standardizes city names.
	Input	Output
Examples	mexico city	Mexico City
Examples	PALACHO	Palacho
Remarks

City - State/Province - Postal Code
Description	The City - State/Province - Postal Code standardization definition standardizes last line address information.
	Input	Output
Example	13210 Mexico Distrito Federal	13210 Mexico, DF
Remarks

Name
Description	The Name standardization definition standardizes names of individuals.
	Input	Output
Examples	senora maria garcia arroyo	Sra Maria Garcia Arroyo
	LEONEL DE JESUS CAMPOS	Leonel de Jesus Campos
	Director Tecnico Eduardo Gonzalez De La Peña	Director Tecnico Eduardo Gonzalez de la Peña
	Reverendo Antonio Parrera	R Antonio Parrera
Remarks	If this definition is applied to pre-parsed data, the following input tokens are available: Name Prefix Given Name First Family Name Second Family Name It is recommended that you map a correlating data field to each available token whenever possible.
Remarks	The Name (v24) standardization definition is a temporary definition provided to facilitate an upgrade of the Name definition. The Name definition accepts parsed input and the input tokens will be changed in a future release. Name (v24) uses the tokens that will be used by Name in the future. The token change will require you to update any jobs using the Standardization (Parsed) node for the Name definition so that the tokens specified in that node will match the tokens used by the definition. Jobs using the non-parsed input Standardization node will not require an update. If you want to begin using the new tokens or the updated processing now rather than waiting for a later release, you can update your jobs to call the Name (v24) definition. Be aware however that the Name (v24) definition will be deprecated in a subsequent release after the Name definition has been updated.

Name (v24)
Description	The Name (v24) standardization definition standardizes names of individuals.
	Input	Output
Examples	Antonio la Merced	Antonio La Merced
	JOSE ALEJANDRO ASENCIO DE LA PENA	José Alejandro Asencio de la Pena
	Señor Marcell d'Marco Camey Martinez	Sr Marcell D'Marco Camey Martinez
	Luis de Torres Contador Publico	CP Luis de Torres
Remarks	If this definition is applied to pre-parsed data, the following input tokens are available: Prefix Given Name Family Name 1 Family Name 2 Suffix Title/Additional Info It is recommended that you map a correlating data field to each available token whenever possible.
Remarks	The Name (v24) standardization definition is a temporary definition provided to facilitate an upgrade of the Name definition. The Name definition accepts parsed input and the input tokens will be changed in a future release. Name (v24) uses the tokens that will be used by Name in the future. The token change will require you to update any jobs using the Standardization (Parsed) node for the Name definition so that the tokens specified in that node will match the tokens used by the definition. Jobs using the non-parsed input Standardization node will not require an update. If you want to begin using the new tokens or the updated processing now rather than waiting for a later release, you can update your jobs to call the Name (v24) definition. Be aware however that the Name (v24) definition will be deprecated in a subsequent release after the Name definition has been updated.

Organization
Description	The Organization standardization definition standardizes organization names.
	Input	Output
Examples	dataflux	DataFlux
Examples	Aventis Pharma S.A. DE C.V.	Aventis Pharma SA de CV
Remarks

Phone
Description	The Phone standardization definition standardizes phone numbers for domestic use.
	Input	Output
Examples	52 55 5122 4300	+52 (55) 5122 4300
Examples	+52 55-5122-4300	+52 (55) 5122 4300
Remarks

Phone (Basic)
Description	The Phone (Basic) standardization definition standardizes phone numbers to a more basic format.
	Input	Output
Examples	52 55 5122 4300	52 55 5122 4300
Examples	+52 55-5122-4300	52 55 5122 4300
Remarks

Postal Code
Description	The Postal Code standardization definition standardizes postal codes.
	Input	Output
Examples	-13210	13210
Examples	13210,	13210
Remarks

Inherited Definitions

In addition to the definitions listed on this page, the Spanish, Mexico locale also inherits all definitions for the Spanish language and all Global definitions.