Hi,
In system design, this is not supported:
==
he attachment transfer should work with DMS using ESOA., since source code in ECC doesn't handle GOS type, and PR and SC does not have header concept.
==
In order to realize this, you can add enhance code in the following place:
SRM FM BBP_BD_PDDOC_FROM_BAPI_MAPS
* RFC to get the file contents.
CALL FUNCTION 'BBP_RFC_CON_GETATTACH' DESTINATION lv_destination
EXPORTING
iv_parentguid = wa_attach-parent_guid
iv_objectkey = wa_attach-objkey
iv_documentnum = wa_attach-doc_id
iv_documentver = wa_attach-doc_ver_no
IMPORTING
ev_fdescription = lv_fdescription
ev_fmimetype = lv_fmimetype
ev_ffilesize = lv_ffilesize
ev_ffilename = lv_ffilename
ev_sdescription = lv_sdescription
ev_smimetype = lv_smimetype
ev_sfilesize = lv_sfilesize
ev_sfilename = lv_sfilename
TABLES
et_bindata_first = et_fir_bindata
et_bindata_sec = et_sec_bindata.
in ECC FM BBP_RFC_CON_GETATTACH
*to get the MIME type of the document
CALL FUNCTION 'CV120_GET_MIME_TYPE'
EXPORTING
pf_dappl = lt_docdata-wsapplication2
pf_file = lt_docdata-savedocfile2
IMPORTING
pfx_mimetype = ev_smimetype.
You can make a judge in SRM FM, and call a different ECC FM to handle GOS document.
One more place is that SC doesn't have attachment in header level, and you have to add Z-tab in SC header to store attachment.
Best regards,
ivy