Attachments to backend

[Former Member]

Refer note : 916347

It has been suggested to add two fields in some structure (BBPS_BADI_BE_RQ_CREATE_OLD and BBPS_BADI_BE_PO_CREATE_OLD)

These are nt available in my system (SRM4.0)

Any suggestions , how to go about now?

[former_member114630]

I have some documentation on the configuration process for attachments in the backend with SRM 4.0. Let me know your e-mail address and I can send it to you.

[Former Member]

Hi Monique,

Could you please send me the document too.

aravind_tula@yahoo.com

Thanks,

Aravind

[former_member114630]

Documentation sent.

[Former Member]

Hi Monique,

Can you please share the same doc with me.

smita.kumar@yahoo.com

Thanks in advance,

smita

[Former Member]

Hi Monique,

Could you please send me the document too.

radha_suriya77@yahoo.com

thanks in advance,

radha

[Former Member]

the e-mail id is tellalok@gmail.com

Pl share the document.

[Former Member]

Hi

Configuration for Attachment transfer

Prerequisites

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 > SRM Server > Business Add-Ins (BAdIs) > Follow-

On Document Generation in the Backend-System > Purchase Order in Backend System

Or

Supplier Relationship Management > SRM Server > Business Add-Ins (BAdIs) > Follow-

On Document Generation in the Backend-System > 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.

Hope this helps

Sam

Monique, can you please email your documentation to sd.atkinson@hotmail.com

[Former Member]

Hi Monique Stephens,

Can u please send the document to me.

MAil Id : meetmani22@rediffmail.com

Thanks and regards,

Mani

[Former Member]

Hi Monique,

Could you please send me the documention.

My e-mail address is naing_zawtun@hotmail.com

Thanks in advance,

Naing

[Former Member]

Greetings Monique,

Can you please send me the document too??

panditamar@gmail.com

Thanks,

Amar

[Former Member]

Could you send me the document please,

alejandro.valenzuela@gmail.com

Thanks!

[dean_hinson2]

Hello Monique,

Could you please send me a copy of the documentation?

dean.hinson@us.bosch.com

Thank you!

[Former Member]

Has anyone tried to pass the URL to the R3 backend system instead of the attachment? We are successful except for one thing. The Data Carrier is not filled, causing the link to the DMS document not to be found. When we manually populate the Data carrier using trans CV02N, the link works.

Does anyone know how the Data Carrier can be passed to the backend?

Kind Regards,

Elvi.

[Former Member]

Hi

Refer to these links.

<b>

http://help.sap.com/saphelp_47x200/helpdata/en/41/648838ab4e8a11e10000009b38f8cf/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/49/b32640632cea01e10000000a155106/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/d6/806c39917d423ee10000000a11402f/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/9b/c2b9375e62545ce10000009b38f889/frameset.htm

</b>

I am not sure this is possible as i have not tried this.

Incase it does not helps, please raise an OSS message with SAP.

Regards

- Atul

[Former Member]

Hi Monique,

Can also send the copy of the documentation on the configuration process for attachments in the backend with SRM 4.0.

email addr: kakazat1@telkom.co.za

[Former Member]

Hi,

For SRM 4.0 ,to transfer attachments to backend,you need to do the foll:

-->figure DC10 and DC30 trx in R/3

in DC10 you make a new doc type e.g. SRM and configure it

for the same ref config guide of self service procurement

In DC30 you canfigure various file types.

-->In BADI BBP_CREATE_REQ_BACK(in SRM)

in the method

FILL_REQ_INTERFACE

you need to set attachement active with statement

cv_attach_transfer_active = 'X'.

There are BADI's in SRM 5.0 by the name,

BBP_CREATE_BE_RQ_NEW for PR creation and BBP_CREATE_BE_PO_NEW badi for PO creation.

HTH.

BR,

Disha.

Pls reward points for helpful answers.

[Former Member]

Hi disha

We use SRM server 5.5

I also need this function.

So we tried to change BBP_CREATE_BE_RQ_NEW based on configuration document.

But we were not able to find the parameter.

Can we use the old badi to transfer attachement? Or Should we apply any notes?

We used the old badi " BBP_CREATE_REQ_BACK", but attachment is not transferred to R/3.

(i have areadly finished IMG in R/3)

Thank you

Best Regard

SH