Skip to Content

SRM - Archivelink configuration for BO attachments

Hi gurus,

we're working on a requirement on a brand new SAP SRM 7 installation.

We would like to store Shopping Cart's (BUS2121) attachments, which in our scenario are present at item's level, into an external repository by means of an Archivelink configuration.

This is basically our aim, even though the complete requirement is quite complex.

We didn't have any experience on configuring Archivelink on an SRM machine, therefore we followed the same "basis" tasks we worked on in a different ECC configuration in the past:

- Transaction OAA3: we defined a new HTTP protocol registry, say HTTP1, for the Archivelink interface 0046, and we generated it successfully;

- Transaction OAC0; we created a new repository, say ZF, with the following specifications:

     Document Area: Archivelink

     Archive type: content server HTTP
     Registry: HTTP1 (the one created at step 1)
     Version nr: 0046
    

     The rest of the technical details refer to the connection endpoint; after the certificates exchange, everything seems to be ok (Connection tests are good).

- Transaction OAC2: we defined two kind of documents, ZBUS2121_1 and ZBUS2121_2, for each type of documents (*).

- Transaction OAC3: we bound basically the SC item's business object (BUS2121001) to our document types (ZBUS2121_1 and ZBUS2121_2), specifying that the repository to be used is ZF and the reference table is TOA01.

Now we're having problems with the OACT transaction.

As far as we understood, we should work on the Content repository BBPFILESYSTEM - which is described as BBP: Document area.

The problem is that we don't know how to handle this part of configuration because we didn't found a way to bind that entry to the ZF repository we created in the archivelink configuration steps described above.

We're probably missing something... any help is really appreciated!

Waiting for your support and help,

Best regards.

M.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Jun 15, 2015 at 03:01 PM

    Hi Matteo,

    please check this site for more information:

    Attachment store mechanism in SRM 7 - Supplier Relationship Management - SCN Wiki

    Best regards,

    Janos

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Matteo,

      from the archive point of view, ARC_DOC_ID and PHIO_ID are equivalent. If
      you talk to the archive this id plus the content repository has to be sent. For
      KPRO the content repository is calculated via the category, for ArchiveLink you
      have it directly.

       

      You can check this with function module SCMS_DOC_INFO. With this you can get
      information about an archived object (ArchiveLink or KPRO) from an archive
      server.

      For an KPRO document you can specify the category in STOR_CAT, but you can also specify the repository id in CREP_ID. The ARC_DOC_ID or PHIO_ID can always be entered in DOC_ID.

      The result for an ArchiveLink document is always a component "data" or "data1":

      Whereas called with a KPRO document you will get the file name in the COMP_ID.

      I could imagine that BAPI BBP_ATT_CHECK is used when a file is uploaded in a shopping cart. Unfortunately there is only a importing paramter (with all information about the document) and you cannot change it here. So you would have to make a modification to change the file name to data.

      I do not recommend this! Please consider other solutions and try to get some information from SAP/SRM consultants if there are standard possibilites for your needs. As I said, I'm not familiar with SRM and all my information comes from a quick look into the system.

      Regards,

      Benedikt

  • Jun 15, 2015 at 02:39 PM

    Hi Matteo,

    transaction OACT (Categories) belongs to Knowledge Provider (KPRO). It's not necessary for ArchiveLink scenario and you cannot use a content repository with document area "ArchiveLink" in KPRO.

    Regards,

    Benedikt

    Add comment
    10|10000 characters needed characters exceeded

    • Dear Benedikt, Janos,

      thanks for your observations. I'm not actually getting the point as I'm stuck on the configuration; is it possible to configure Archivelink is SRM so that Business object's attachments can be stored on an external repository?

      The reason why we would like to use archivelink is as follows; we would like to use TOA0x's ARC_DOC_ID reference to spread an unique identifier of an uploaded content throu SAP systems connected to the same external repository.

      The complete requirement is quite tricky, but the main reason of this choice relies on the above assumpion, as some SAP ERP are configured through Archivelink to store documents in a common external repository.

      Thanks for the support; if anyone could elaborate a bit a sketch of possible approach, that would be awesome.

      Best regards,

      M.

  • Jun 26, 2015 at 08:34 AM

    Thanks everybody,

    at the end, I think I'll go for a custom solution in order to store SRM BO's attachment by means of archivelink. This will obviously pass through the comprehension of the available APIs offered by archivelink.

    Thanks again for your support!
    M.

    Add comment
    10|10000 characters needed characters exceeded