Skip to Content
Author's profile photo Former Member

Attachment transfer from SRM to ECC as an URL link – an overview and the customization requirement

Currently attachments can be added when the shopping carts are created in SRM. The same can be viewed when the shopping cart is displayed. The attachments in SRM will be stored in the BBPFILESYS repository. When the purchase requisition (PR) is created automatically in the back end, the URL of the document is transferred and the same is managed through Document management system.

Transferring of attachment as a link enables a duel storage both in SRM and ECC system. The same attachment will transfer to PO when it is created and the attachment can be printed also when the PO is printed.

The storage of attachments as URL needs content repository settings in SRM which enables the document server in EBP to manage physical storage from SAP database to a HTTP based storage and archival system like IXOS. The logical storage of the documents would continue to be in SAP in repository BBPFILESYS.

The content repository configuration settings in SRM/ECC system is as below

Define document types in SRM system in the below path

Path: SPRO -> IMG -> SAP Web Application Server – > Application Server – >Basis Services – > Archive Link -> Basic Customizing – > Edit Document Types.

Configuration settings in ECC system

1.       1.       Create document type – SRM

SPRO – > SAP IMG – > Cross Application components – > Document Management – > Define Document Types (T. Code: DC10)

The standard settings are as below though the exact settings may vary depending on the requirements of the client

In Attributes & Fields selection sections, configure the following:

     Use Kpro: Activate this indicator

           Select the version assignment.

     Number Assignment: Enter ‘3’ (only internal number assignment)

     Internal Number Range: Select an internal number range from search help

              Maintain the Number Exit as MCDOKZNR

Please refer the below attachment


Maintain the Languages in the Define language dependent descriptions as shown in attachment below


Double click on Define object links in the left plane. Create new entries for objects EBAN and EKPO. This means new document type ‘SAP SRM’ will be used to link documents in purchase requisitions (EBAN) and purchase order items (EKPO) as shown in attachment below


Maintain the settings for all the Application types (XLS, DOC, PPT etc) by clicking on “define transport of originals for ALE” as shown in attachment below


2.   Define Data carrier

SPRO – > SAP IMG – > Cross Application components – > Document Management – > General Data – > Define Data Carrier (T. Code: DC20)

a.       Define Data carrier Type “server, frontend” as shown in the below screenshot


     b.       Define servers and files or folders


     c.       Identify front end computers


  d.       Define mount points/logical drive: Here maintain the URL path where the documents gets stored in SRM. I have blurred the custoemr name



1.     3. Define workstation application


         SPRO – > SAP IMG – > Cross Application components – > Document Management – > General Data – > Define work station application (T. Code: DC30)

          All required file types should be included in this list as shown below


          For transferring the URL of the attached document, it is important to maintain *.* in the file format as shown below for a Text (TXT) file format is as shown below


          In Define workstation application in network, Maintain the settings as shown in below screenshot


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Ashish Shah
      Ashish Shah

      Does this also work for extended classic scenario?


      Author's profile photo Former Member
      Former Member
      Blog Post Author

      I must say that I ahvent worked much in extended classic but I believe it should work