Clarification: Transfering Attachments to Backend (R/3)

[Former Member]

Hi,

We are on SRM 5.0 with 4.6D R/3.

I need some clarification. Do we need to have DMS implemented and configured to transfer attachments from SRM to Backend (R/3)?

Reading the notes and SDN forums on this subject, I beleive DMS must be implemented and configured in Backend (R/3) to transfer attachments from SRM to R/3.

Thanks,

Naing

[former_member195032]

Hi Naing,

You need to have DMS Implemented.

From SAP Enterprise Buyer Release 5.0 you can transfer attachments from the shopping cart to a backend

system where they are added to follow-on documents. This function is available from SAP R/3 Release 4.6c.

In the shopping cart, you can add attachments on item level. In the classic scenario, they are transferred to the

purchase requisition and purchase order follow-on documents of the backend system. Purchasers can also

display and edit the attachments in the backend system on item level.

There are two ways to store attachments in the backend system.

1. The attachment is stored in the SRM System and the backend system. After the attachment is

transferred to the backend system, both documents are separate. There is no link between the

documents.

2. Only the URL of the original document is transferred to the backend system. A user name and

password in the Enterprise Buyer System is required to display the document.

Note: The document cannot be displayed if the URL is longer than 128 characters. Nevertheless, the

URL is saved to the database.

<b>Setting up Attachments</b>Use

You have to make the following settings if you want to use attachments in combination with

your purchasing documents.

<b>Procedure</b>

...

1. To display attachments in your Internet browser, make the relevant settings in the

Internet Communication Framework in transaction SICF.

2. If you want to have several clients in the system, create an alias for each client, with the

alias pointing to /default_host/sap/ebp/docserver.

3. In the tab page Service Data, create the client number in the Client field under the

logon data.

4. Choose one of the following options for logon. SAP recommends that you choose the

first option.

a. For the Single-Sign-On configuration, do the following:

-> Go to transaction SMICM and choose Goto &#8594; Services.

-> View the domain name that is being used for SAP Web Application

Server and check against the domain name being used in the webserver

for SAP Internet Transaction Server. The same domain name must be

used for both, for example, washost.<sap.corp>:4711/… and

itshost.<sap.corp>:0815/…

->Go to transaction SS02, enter RFC destination NONE and execute. Check

that the profile parameters login/create_sso2_ticket and

login/accept_sso2_ticket of your Enterprise Buyer system are set to value

-> (ticket including certificate). If this is not the case, go to transaction

RZ11 and change the values accordingly.

This means that the ticket generated when the user logs on to the ITS

can be accepted by the HTTP service.

->Change ITS service to GLOBAL. This allows the generation of a ticket to

be requested during logon.

->Ensure that the parameter ~mysapcomgetsso2cookie is set to the value

1.

->Publish the service

-> Define a user in the HTTP service. If you are only using one client, define the

user in the Docserver node. If you have several clients, define a user in the Alias

node. We recommend that you choose user type Communication.

<b>Configuration for Attachment transfer</b>

<b>Prerequisites</b>

In order to store shopping cart attachments in the backend system, you must first activate the

transfer by creating an active method and by setting the indicator for parameter

CV_ATTACH_TRANSFER_ACTIVE in BAdI BBP_CREATE_PO_BACK (for purchase orders)

or BAdI BBP_CREATE_REQ_BACK (for purchase requisitions).

See Implementation Guide (IMG):

Supplier Relationship Management &#8594; SRM Server &#8594; Business Add-Ins (BAdIs) &#8594; Follow-

On Document Generation in the Backend-System &#8594; Purchase Order in Backend System

Or

Supplier Relationship Management &#8594; SRM Server &#8594; Business Add-Ins (BAdIs) &#8594; Follow-

On Document Generation in the Backend-System &#8594; Purchase Requisition in Backend-

System

Procedure

Then you must configure the R/3 Document Management System (DMS) in transaction

DC10:

...

1. Create document type SRM. Note that no flag is set in any of the columns.

2. Double click in the detail view to define the new Doc. type desc. = SRM Documents.

Set the Use KPro indicator.

-> Enter 1 in the Number assignment field.

->Enter an internal number range interval. You can use an existing interval or

create a new one in transaction CV90. The internal number range must be used,

because the GUID of the SRM attachments has more digits than the number in

the backend system.

->Maintain the number exit. The number exit is a program exit for document

number. It controls number assignment and version numbering for documents.

The default setting is MCDOKZNR. If you want to control the number assignment

or the version increment via a USER_EXIT, then you have to replace the

program MCDOKZNR with a company-specific program. You can find further

information in the field help for number exit.

-> In the screen area Field selection enter – in the field Document Status.

3. Go to the Dialog Structure and double-click on the entry Define object links. Define the

new object links EKPO and EBAN. Maintain object link descriptions for EKPO

(Purchase order item; Scr.no. 248) and EBAN (Purchase req. item; Scr. no. 247)

4. Define the workstation application in transaction DC30.

All required file types should be included in this list.

Regards,Nishant