cancel
Showing results for 
Search instead for 
Did you mean: 

Issue while opening HR documents

Former Member
0 Kudos

Hello All

I recently configured archive link and migrated all the HR and AP/AR documents from documentum to content server. The extension of the documents has been manually changed to TIFF in TOA01 table for AP/AR documents and they are opening with windows photo viewer properly, but the issue is with HR documents.

In toahr table, In spite of changing the extension of HR doc from FAX to TIFF, it is still opening as ALF in windows photo viewer. Is there any config that I need to do here? I configured the doc types as * in OAC2

NOTE: The reason for changing the extension to TIFF is 'with wndows photo viewer, the ALF or FAX type docs cannot be printed, which is only possible with ext TIFF.'

Thanks

VK

Accepted Solutions (0)

Answers (1)

Answers (1)

sasmita_mekap
Advisor
Advisor
0 Kudos

Hello Venkata,

Only changing the extension in TOA01 table would not help if the physical document stored in the content server has a different mimetype than that of TIFF (mimetype for TIFF files is image/tiff).

Please check what is the mietype of the document stored in the server . If it is incorrect, you may need to store the documents again.

Regards,

Sasmita

Former Member
0 Kudos

Hello Sasmita

I checked the mime type of TIF in OAD2. It was showing as below. The same is for type FAX as well and I cannot be able to change it as the system is not allowing to change SAP entries. Though the mime type is different for ALF, all the HR documents of type TIF(as per the table TOAHR), they are still getting opened as ALF. Can you suggest any solution for this?

TIF

DescriptionTag Image File Format
MIME type  image/tiff
Application

EAIWEB.WEBVIEWER2D

FAX

Description     Internal format for TIFF Files

MIME type       image/tiff

Application     EAIWEB.WEBVIEWER2D

ALF

Description     Internal Format for Stored Print Lists

MIME type       application/x-alf

Application

Regards

VK

sasmita_mekap
Advisor
Advisor
0 Kudos

Hello Venkata,

In my previous reply, I was not referring to the mimetype you see in OAD2, because that is the customizing for the document calsses. I was speaking about the actual mimetype with which the

corresponding physical document is stored in the content server, if that is incorrect, only changing TOA01 entry would not help.

You can find the same TOA01 entry via txn OAAD -> Technical Search providing the document ID as the search criteria, and then on the result list click on "Details" button, and you can click on the "Status query" button to check the actual mimetype with whihc this document is stored in the server.

Otherwise, you can run report RSHTTP52 with the document ID and repository name to get the "Content-type" that is the mimeitype of the document.

If the mimetype when storing in the server is incorrect, you may need to store the documents again in the content server with the correct mimetype.

Thanks and Regards,

Sasmita

Former Member
0 Kudos

Hello Sasmita

I checked for one of the tiff document. Though it was chaanged to tiff, its mime type is showing as a-alf

"data  application/x-alf online 12/06/2013 16:22:04 12/06/2013 16:22:04   136,027".

Do you know how can i store it again as tiff? These are migrated documents from documentum to SAP Content server. They cannot be saved again.

Is there any program to change the mime type to tiff?

Thanks

VK

sasmita_mekap
Advisor
Advisor
0 Kudos

Hello VK,

That is what I was trying to explain that nly changing to TIFF in TOA01 would not help because the originial mimetype when storing the document would be that of ALF that is application/x-alf.

I am not sure how you had stored the document originally in documentum content server, you may need to follow the same process to store it again. Because there is no such program to change the mime-type of an archivelink document at the server level, and here the mime-type of the document in the  content server is different from that of tiff.

Thanks and Regards,

Sasmita