V5R4, 4.6C, and the SAP Content Server

[Former Member]

Hi All,

We are working an issue with SAP (SAP Support case 536258) regarding an incompatibility between V5R4 and R/3 4.6C connected to SAP Content Server 6.20. The transfer of documents to the Content Server is not correct under Generic Object Services (GOS). These documents appear to be stored, but in a manner that they cannot be retrieved. The component in the ArchiveLink entry is contaminated (####@@@@@@@@@...). So far we have installed the latest patches for SAPHTTP and upgraded the Content Server to 6.30 without any luck. I thought I would post this in case someone has seen this problem before and has a work around.

Regards,

Stan

[Former Member · Accepted solution]

Hi Stan,

are you really sure, that this behaviour has REALLY to do with V5R4 ?

The following tells me something different:

####@@@@@@@@@

=> It is highly likely, that here data is written in EBCDIC and read in ASCII on the content server site - but as binary transfer happens, everything crashes ...

May it be possible, that the data is transfered via a file share ? You should check if the fileshare for the OUTGOING documents from SAP to the content server is set to convert or might be set to binary - at least for this filetype. This would be a typical error I have often seeon already.

Already looking forward to you solution,

Volker Gueldenpfennig

[Former Member · Accepted solution]

Hi Volker,

Thanks for the tip regarding EBCDIC <--> ASCII translation. I've passed that on to SAP support. ArchiveLink does have a transfer directory in the root file system. I'm not sure if it uses it when it stores files, but file do pass through there when they're retrieved.

Regards,

Stan