parsing Issue

[Former Member]

Hi all,

    Created Data cleansing solution for input table. In output cleansing results, some records are not parsing properly for person column. Person column is parsed into first name,middle name and last name. For some columns middle name data is empty,data in middle name column is displaying in last name column along with last name data.

    for example person name format is A. Name1 Name2

    After parsing::

                 First name     Middle name      Last name

                     A                                           Name1 Name2

     80 percent of records are parsing properly,remaining 10 percent are issues with middle name. can you please suggest me how to solve this issue.

Thank you.

[Former Member · Accepted solution]

Hi Vineela,

Do you notice same format for all the records?

I mean for the example you gave A. Name1 Name2, do you see a (.) dot after the first word?

When we did name parsing, we handled unparsed names manually through ifthenelse conditions.

--Eliza

[Former Member · Accepted solution]

Hi Elizabeth Torri,  

    Thank you for your reply.This issue is because of directories, I didn't installed directories in my system.Every time I perform cleansing base data cleanse transform is generating instead of particular transform from data cleanse.

[former_member187605 · Accepted solution]

Don't get confused! Address directories are only used by the address_cleanse transform. The data_cleanse transform uses a dictionary that is always available because automatically installed with the DS software.

[Former Member · Accepted solution]

   whenever I use data cleanse in Information steward and publish it into designer I can see only base data cleanse transform in my generated job.But under data cleanse list different transforms are there.

[former_member187605 · Accepted solution]

These are just configurations of the data_cleanse transform. From the documentation, SAP Data Services Refereence Guide:

"

Transform configurations

A transform configuration is a transform with preconfigured input fields, output fields, and options that can be used in multiple data flows. These are useful if you repeatedly use a transform with specific options and input and output fields.

When Data Services is installed, read-only transform configurations are provided for the Data Quality transforms.

You can use transform configurations in your data flows or as an example of a typical transform. After you place an instance of the transform configuration in a data flow, you can override these preset defaults. You can also create your own transform configuration, either by replicating an existing transform configuration or creating a new one.

"

[Former Member · Accepted solution]

Thank you dirk