Sender and Receiver FCC

[Former Member]

Hi All,

At sender side i have structure as

<Recordset> 1--1

<header> 0--1

<id>

</header>

<details> 1---unbound

<nameA>

<nameB>

</details>

</recordset>

i have used FCC at sender side but not able to create header in my message.

Then at Receiver side i m using FCC for generating csv file. File is created successfully but i m not able to put heading to each column.

Please guide me to solve this problem.

Regards,

Manisha

[JoelTrinidade · Accepted solution]

Hi Manisha,

Did you try your hand at Recordset Structure

Recordset Structure.addHeaderLine

Recordset Structure.headerLine

Regards

joel

[Former Member]

I have done with receiver side now...

Can anyone guide me how to create Header tag at sender side??

Regards,

Manisha

[Former Member]

Hi Shabarish ,

For Sender,

FCC is

Record structure - Header,1,Details,*

Record Sequence- Ascending

Recordset per Message - *

Key Field Name - ID

Key Field Type - string(case-insensitive)

Header.fieldNames - ID

Header.fieldSeparator - ,

Header.missingLastFields - error

Header.keyFieldValue - 1130

Header.additionallastFields - error

Header.endSeparator - ,

Details.fieldNames - all fields under detail node

Details.fieldSeparator - ,

Details.fieldContentFormatting - nothing

Details.endSeparator - 'nl'

Details.missingLastFields - ignore

Details.keyFieldValue - EA

Details.additionalLastFields - ignore

Here i don't need key field value.

-

---

For Receiver Structure is

<recordset> 0--1

<details> 0--unbound

<type>

<id>

<number>

</details>

</recordset>

FCC is

Details.addHeaderLine - 1

Details.fieldSeparator - ,

recorset.fieldSeparator - 'nl'

Details.endSeparator - 'nl'

I need type, id, number to be appear as heading to csv file column

Regards,

Manisha

[Shabarish_Nair]

can you also paste a sample file input ?

[Former Member]

For Sender

<Recordset>

<header>

<id> i1 </id>

</header>

<details>

<nameA> na1 </nameA>

<nameB> nb1 </nameB>

</details>

<details>

<nameA> na2 </nameA>

<nameB> nb2 </nameB>

</details>

</recordset>

For Receiver

<recordset>

<details>

<type> t1 </type>

<id> i1 </id>

<number> n1 </number>

</details>

<details>

<type> t2 </type>

<id> i2 </id>

<number> n2 </number>

</details>

</recordset>

[Shabarish_Nair]

you posted the xml file. post the flat file that you are trying to convert to xml

anyway, for sender try;

Header.fieldNames - ID

Header.fieldSeparator - 'nl'

Header.endSeparator - 'nl'

[Former Member]

in RWB it is giving me error as

Empty document found. Proceed without sending message

[Shabarish_Nair]

paste the input sample flat test file (not the xml) here

[Former Member]

i have csv file at sender side

StorageLoc 1130

Material Plnt SLoc

2100475 1101 1030

2100475 1101 1030

2100475 1101 1030

at receiver side i need to convert xml into csv file

[Former Member]

Joel,

I have done that at receiver side..still header is not coming in csv file

[Shabarish_Nair]

please paste your FCC parameters you have provided in both the CC to help you more.

[Shabarish_Nair]

> Hi All,
> 
> At sender side i have structure as
> 
> <Recordset>       1--1
>   <header>           0--1
>     <id>
>   </header>
>   <details>           1---unbound
>     <nameA>
>     <nameB>
>   </details>
>   </recordset>
> 
> i have used FCC at sender side but not able to create header in my message.

what is the header that you want? what is the FCC you have given?

> Then at Receiver side i m using FCC for generating csv file. File is created successfully but i m not able to put heading to each column.
> 
> Please guide me to solve this problem.
> 
> Regards,
> Manisha

use the option

NameA.addHeaderLine

Specify whether the text file will have a header line with column names. The following values are permitted:

·        0 u2013 No header line

·        1 u2013 Header line with column names from the XML document

·        2 u2013 As for 1, followed by a blank line

·        3 u2013 Header line is stored as NameA.headerLine in the configuration and is applied

·        4 u2013 As for 3, followed by a blank line

http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm