ArchiveLink - creating a new document class - how?

[Former Member]

Hello,

I want to store csv files on our archive via archive link.

But the file type that I need is not available in R/3.

Ok, I think here is where my solution could be found:

-> archive link -> basic customzing -> edit document classes

Document class: I add "CSV"

But what´s behind the MIME type of a web object.

What do I have to do to fill this field with something useful.

What is to implement behind?

Any help is appreciated!

Best regards

Dirk

[Former Member]

Hello,

I want to store csv files on our archive via archive link.

But the file type that I need is not available in R/3.

Ok, I think here is where my solution could be found:

-> archive link -> basic customzing -> edit document classes

Document class: I add "CSV"

But what´s behind the MIME type of a web object.

What do I have to do to fill this field with something useful.

What is to implement behind?

Any help is appreciated!

Best regards

Dirk

[Former Member]

if you go throught there archive link creation in the archiveing process ...

FTWP is the comfiguration tcode for archive of DART extract ....

there Comtemporary Repository has to be created with document area-> here dropdown is there for for archieve link , for MIME ,, BFT ...etc ..

this will decide the file format .....

i am working in DART Exctraction project .....we use to create the archive link for that ......

normally in archiving processs all the files stored in csv only

Girish

[Former Member]

Hello Dirk,

did you find any solution for your problem?

We are also investigating for we want to archive a csv document sent by mail.

We only see function module CONVERT_OTF_AND_ARCHIVE which is restricted to OTF and PDF format.

We woult be glad if you could offer any suggestions

Best regards

Michael Rangs

[Former Member]

Hello Micheal,

this is really long ago, 1,5 years!

I treid to remember, what we did there, but I think we did the implementation for the csv as described here. And the main problem was a malfunction with the archive connection and customizing in the development area which resulted in rejecting the new doc types.

In my project task plan I found this information and a comment that the issue was solved after some

configuration on the archive side.

But this was a very special environment at the customer side.

Best regards

Dirk