Problem with attachments transfer to R/3 PO

[Former Member]

Hi

SRM SERVER 550 SP 6 ECC 6

I'm in a classic scenario.

I used the old BADI BBP_CREATE_PO_BACK method with the following parameters I debugged and the flow stop so I think it should work:

move 'SRM' to CV_ATTACH_BE_DOC_TYPE.

move 'X' to CV_ATTACH_TRANSFER_ACTIVE.

move 'DMS_C1_ST' to CV_ATTACH_BE_STORAGE_CAT.

I did the customizing DC10, DC30 and the kpro customizing.

I tested to include attach in R/3 POs.

I debugged and the BAPI_DOCUMENT_CREATE2'

returns 0

lt_description & lt_objectlinks have content

lt_files blank

the importing parameter

doctype SRM

docnumber 0000000000000010000000004

But I can't see my attachment in ME23N.

Any idea

thanks

Regards

[Former Member]

Hi

SRM SERVER 550 SP 6 ECC 6

I'm in a classic scenario.

I used the <b>IF_EX_BBP_CREATE_BE_PO_NEW~FILL_PO_INTERFACE1</b> method with the following parameters I debugged and the flow stop so I think it should work:

<b>CS_CTRL_ATT-TRANSFER_ACTIVE = 'X'.</b>

I did the customizing DC10, DC30 and the kpro customizing.

<b>Result of DC10 (record in TDWA table)</b>

Document Type SRM

Field selection -

Status Change

Rev. Assgmt

VersNumIncr. 1

Version Assgmt

Number Assgmt 1

IntNum range 03

Ext.No.range 01

Change Docs

ArchAuth

Alt screen 0

AScEx.

NumExit MCDOKZNR

PRT

File size 10000000

Class

Class Type

Delete Original

Transport origin.

Use KPro X

Display Class

Default Appl.

Dis. WS applic.

Ignore originals

CM Relevnce

VersionSequence

Description SRM Documents

<b>DC30 with .xls values introduced</b>

function module used B46C_ATTACHMENT_CREATE for my version

<b>Customizing entries in DMS (R/3)</b>

Under Cross Application Components --> Document management --> General Data --> Define Data Carrier

--- data carrier type in the dialog structure 'Define data carrier type 'server, front end'' (PC with Path as C:\temp).

--- Enter a default entry in the dialog structure 'Identify frontend computers'.

<b>As a result of this table TDWD appear with this values</b>

Data Carrier Default

DataCar.type PC

Net.adr DEFAULT

Description Default for local PC

Vault path

DVA computer

Inactive

And TDWE

<b>DataCar.type PC</b>

Online X

Printer

Archive

Address type

CAD system

Description PC mit Windows

Path c:\temp

Vault

Ex

<b>Runtime debugging.</b> B46C_ATTACHMENT_CREATE

• Attention it could be this *****

Call to BAPI_DOCUMENT_CREATE2

exporting ls_document_data (ls_document data only has the description with value)

...

tables

lt_description (1 record with description)

lt_objectlinks (OBJECTTYPE EKPO

OBJECTKEY 620000010100010 )

lt_files (no values)

No entries in R/3 SOFFPHIO tables for example are created for WF-batch

Any suggestion.

[Former Member]

Hi & thanks

I am looking in ME23 or ME23N (in the top left corner) the services object icon then expand menu and option attachment list. But my attachment doesn't appear.

Disha I have done that you said (only differnce parameters CV_ATTACH_BE_DOC_TYPE and CV_ATTACH_BE_STORAGE_CAT but I think that my values were the default values)

any other suggestion??

THnks

regards

[Former Member]

Hi

<b>Please go through this -></b>

What is your SRM and R/3 version releases ?

<u>Attachment transfer to R/3 purchasing doc is now standard since SRM 4.0.

Your R/3 backend should be at least 46C.</u>

<b>Make sure you have the following configured in your system:</b>

<u>1. Create and Activate Implementation for BADI BBP_SC_TRANSFER_BE. Set CV_ATTCH_TRANSFER_ACTIVE paramater in SRM

2. Configure Document Type in R/3

- Transaction DC10 - Add a New Document Type SRM (if not already exists). Set 'Use KPro', 'Version Assign' and 'Change Docs'. Set the Internal and External Number Range (02 and 01). Use MCDOKZNR as Number Exit. Ver No. Incr = 1 and Set the File Size (Usually 10000000 bytes).</u>

<b>Once the Document Type is created, define Object links to PO Item and Pur Req Item. Use - Screen Number 247 and Screen Number 248 with Valuation Object of EBAN and EKPO for Objects EBAN (PReq) and EKPO (PO) for Doc Type SRM.

3. Check whether you have all the workstation applications configured in R/3 (DOC, TXT, PDF, XLS etc) in Transaction DC30.</b>

<u>Additional Checks:</u>

<b>- If you are transferring attachments and not link - make sure you have Implemented OSS Note: 820897 in R/3.</b>

<u>If the above settings does not give you results - you may want to debug and find out the exact error message while creating the attachment.

- Check the R/3 Release and get the corresponding driver from BBP_FUNCTION_MAP table with Object Type as DOCUMENT and Method - CreateFromData.

- Set the Breakpoint at Function Module BAPI_DOCUMENT_CREATE2 and at CVAPI_DOC_CHECKIN in the above driver. These Function Modules will return you the exact error message.</u>

<u>It must be activated in BADI BBP_CREATE_REQ_BACK.

You must also specify backend content storage parameters in this BADI, based on the backend customizing of DMS.</u>

<b>Customizing entries in DMS.

Check the following in R/3 -->

Under Cross Application Components --> Document Data --> General Data --> Define Data Carrier

--- Enter a data carrier type in the dialog structure 'Define data carrier type 'server, front end'' (for example, PC with Path as C:\temp).

--- Enter a default entry (using the button) in the dialog structure 'Identify frontend computers'.</b>

<u>You can use the following parameters for transferring the attachements to the backend system:

CT_ATTACH_BE KW attachments including document

CV_ATTACH_BE_DOC_TYPE Document type (standard is SRM)

CV_ATTACH_BE_STORAGE_CAT Storage type (standard is DMS_C1_ST)

CV_ATTACH_TRANSFER_ACTIVE Activate transfer of attachments

CV_ATTACH_USE_URL Transfer URL only

Then during the PR creation, SRM uses META_ATTACHMENT_CREATE using previous parameters.

BAPI_DOCUMENT_CREATE2 will be called in R/3.</u>

<u>

</u>

Hope this will help.

Regards

- Atul

[former_member114630]

The attachment will not appear through the services for object section. Underneath the item overview section of the PO are several icons. The last icon would look like an envelope with a paper clip. You will need to select the line item first, then click on the icon to get to the attachment.

[Former Member]

Hi,

You just need to set the indicator "CV_ATTACH_TRANSFER_ACTIVE" in the BADI for the atatchemnt to be trasnferred to the backend doc.

Also do the settings in DC10 and DC30

DC10 - create a Document type for SRM

DC30 - Maintain all relevant extensions ,

In DC30 for the required file type do the settings e.g.

WS appln =XLS

Description= MS excel

Archieve Idn=*

File suffix=xls

file format=*.xls

Mime type=application/msexcel

appl icon=(select sxcel icon)

BR,

Disha.

Pls reward points for useful answers.

[former_member114630]

Where are you looking in ME23N to find the attachment?