Q on File Adapter Key

[Former Member]

All,

I have a requirement,

Outbound file-> to PI to database.....

the file is like this : Header,1,detail,*

now the problem is that when i specify the content conversion parameters: the Adapter expects a key field.

but my partner's outbound file doen't have a key file in it to identify the header from the detail.

i have even specified the Keyfield as ignore in the content conversion.

Any hints/ tips wud be well appreciated>

Thanks,

Hank

[Former Member]

thnk u all for ur replies and feeds...:) tht ws really helpful..

in ths case ive found a work around ths requirement..:)

cheers...

[Former Member]

thnk u all for your replies and suggestions....i got a workaround ths

cheers

[Former Member]

>> Header,1,detail,*

If you have specified the Recordset Structure as Header,1,detail,*

then keyfield becomes mandatory.

Do you really need Header in your payload,are you doing any message mapping by using it?

If not,you can drop the Header field and only specify Details,* in Recordset structure,in that case you won't need keyfield.

second option would be to either write a OS script or ask the sender system to ass keyfield values.

Thanks

Aamir

[Former Member]

Hey

Key parameter is not mandatory for File content conversion.

If you dont have a key in sender file,just dont specify any parameter related to it

Thanks

Aamir

[Former Member]

Thanks Aamir....

Here is the thing, i tried the FCC w/o the Key paramter and i get an error in the Adapter monitoring saying that it expects the key field paramter.

on PI 7.0

[Former Member]

the outbound file is like this....

header_item, header_date, header_sl......

detail(1)_field1,detail(1)_field2......

detail(2)_field1,detail(2)_field2......

thanks

[Former Member]

Joivani,

u dont need keyfield for the file u hv given.

header,1,detail,* is correct.

You need to mention this parameters for both header and detail:

.fieldSeparator as , and endSeparator as 'nl'. It is very straight forward. It should work else give the parameters you mentioned and the source message type.

Regards,

---Satish