FCC

[Former Member]

Hello All,

I am working on a outbound scenario. As part of my message mapping I have 10 fields on the target side.

But I dont want to write the 10th field on to file.

Can anyone tell me how can I handle this in FCC

Thanks,

Regards,

Moorthy

[Shabarish_Nair · Accepted solution]

if there is no use of the 10th field, then why the mapping?

Avoid the mapping and make FCC simple

[Former Member · Accepted solution]

I need it as part of monitoring.

[Shabarish_Nair · Accepted solution]

I dont think there is a standard way to remove the last field.

But in case you are using Fixed Fields instead of field separator, it is still possible.

[baskar_gopalakrishnan2 · Accepted solution]

In addition, if you use fieldNames (exclude the 10th field) in that list. FieldFixedLength is mandatory if you have not specfied fieldSeparator.

[Former Member · Accepted solution]

Hi Moorthy

I think there is no standard way of doing it because we don't specify the field names in reciever channel.

We just give field length or field separator.

I think if its fixed field length u can handle and need to make sure that fields get populated with specified length.

Regards

sandeep

[former_member191435 · Accepted solution]

Hi,

Use fieldfixed length- 0 for 10th field ( which u need to avoid)

and use element.fixedLengthtooShorthandling - Cut

then you can avoid the last field.

Thanks,

Sreenivas

[Former Member]

only fix length flat file could be ignore the last field. no standard way for flat file with delimite.

set the 10th field lenth 0 or only give 9 field length.

then give the parameter .fixedLengthtooShorthandling value "Cut"

then you can avoid the last field.

if the target structure like

segment

field1

feild2

...

field9

segment

field10

then there is no problem.

u can only set fix legth for the 10th field. set the length 0 and paramete value "cut"

[Former Member]

Hi Moorthy,

if you have a message mapping, and if you don't wan't to change your target structure, a way could be to "enable" the field. to do it, in message mapping, select the target field and with a right click, choose "enable".

In your receiver CC, inside your content conversion do not declare this last field under "fieldNames", as it will be never created.

if that corresponds to your needs, do not forget to document this tips in technical spec (and/or directly in the mapping itself), that could help maintenance team...

regards

mickael