ECS - PO Atatchments to the Backend

[Former Member]

Using ECS, are attachments transferred to the backend system (R/3)? I have found references for instructions to transfer attachments for Classic but not ECS. If so, can anyone provide instructions. For ECS, the BADI BBP_ECS_PO_OUT_BADI is executed. The IT_ATTACH table is populated but it looks like it is not transferring it to the backend. The backend function BBP_PO_INBOUND is called in R/3 but the IT_ATTACH table information is not passed to the backend functions.

Any ideas?

[Former Member · Accepted solution]

Yes, we have done that. The BADIs referenced are only called for Classic senarios and not Extended Classic. After tracing the BADIs, BAPIs, and functions being called when a SRM order is transferred to the backend R/3 system in the ECS mode, it appears that attachments are not carried to the backend system. They are only stored on SRM. Can anyone confirm this?

[yann_bouillut · Accepted solution]

Hi,

Yes this is the standard behaviour : SRM attachment with ECS remains in SRM

Kind regards,

Yann

[former_member195032]

Hi Russell,

Have you done configuration for Document Management system.

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.

Config Guide content pasted above from Page 28.SRM 5.0

Regards,Nishant