Add-on version 200

The hereby described customizing transaction enables parallel usage of three storage type solutions - GOS, BDS and DMS. Starting from FSM Cloud Connector Add-On version 200, the entire attachment configuration should be maintained here. DMS- and BDS-specific transactions (folder https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953499) should no longer be used, as well as attachment-related fields in company configuration transactions (https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953211, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515).

Customers can decide to continue using the older attachment handling approach. Using the new attachment handling approach might require reimplementation of older BAdIs as new BAdIs, whenever possible () and movement of customer enhancements into new attachment classes.

E.g. BADI for additional reference setting - /PACG/ECM_ATTCHM_ADD_REF, in class /PACG/ECM_CL_S_IDOC_I_ATTCHM_1 is currently not available in the new class /PACG/ECM_CL_S_IDOC_I_ATTCHM2, new options in transaction can be used instead.

Additionally, maintenance of additional entries in standard SAP attachment configurations might be required, e.g. transactions DC10 or OAC3.

Learn more about other aspects of attachment setup:

Important to know

Make sure to run the setup program first (/PACG/ECM_SETUP - FSM Connector's Setup). Redesigned attachment handling is implemented in new idoc classes which should be adjusted in transactions /PACG/ECM_CLSASSIG - FSM Connector's Outgoing Messages Configuration and /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration.

Transaction	Message type	Field name	Idoc class

Transaction	Message type	Field name	Idoc class
/PACG/ECM_CLSASSIG	/PACG/ECM_ATTCHMOUT	IDOC Class	/PACG/ECM_CL_S_IDOC_O_ATTCHM2
/PACG/ECM_CLSASSIGIN	/PACG/ECM_ATTCHMIN	Inb. Data Creat.	/PACG/ECM_CL_S_IDOC_I_ATTCHM2
/PACG/ECM_CLSASSIGIN	/PACG/ECM_SIGNATURE	Inb. Data Creat.	/PACG/ECM_CL_S_IDOC_I_ATTCHM2

General overview

The collective attachment configuration has been designed to enable parallel usage of three storage type solutions (GOS, BDS or DMS) for inbound attachments. A specific storage type can be determined based on a company ID and/or object type and/or file type. Additionally, users can define a list of object types/file types blocked from transfer to SAP FSM.

General Attachment configuration

Customize general attachment settings, such as maximal allowed attachment size, default storage type for inbound attachments or if inbound/outbound attachment transfer should be blocked. This node can be default or company specific.

Learn more:

Advanced storage type determ. / OLD LABEL Inbound configuration

Inbound attachments of certain object types and file types can be stored differently. Customize default storage types for specific ERP objects (e.g. SERVICECALL) and/or file types (e.g. PDF). If no relevant entry is maintained for an inbound object/file type, the storage type from ‘General Attachment configuration’ will be used. This node can be default or company specific.

Learn more:

Block from transfer to FSM / OLD LABEL Outbound configuration

Outbound attachment block list. Specify which ERP objects and/or file types should be restricted from transfer to SAP FSM. This node can be default or company specific.

Learn more:

Learn more about the configuration

Correspondence to obsolete transactions

Obsolete transaction	New attachment configuration

Obsolete transaction	New attachment configuration
	SAP standard transactions OAC2 and OAC3 available as links in folder
	(default or company-dependent)
	No direct correspondence. Certain attachments can be restricted from transfer to SAP FSM based on object type and/or file type in
	Field ‘Folder path’ in

Copy configuration node entries

To copy all entries from a given configuration node and its sub-nodes to another company, select the relevant node, click the ‘Copy configuration’ button and enter the target company ID.

Entries in the target company configuration will be merged with the ones from the source company. Existing entries with the same key will be overwritten with values from the source company.

Clear configuration

To remove the entire configuration from a node and all its sub-nodes, select a node and click the ‘Clear configuration’ button.

A pop-up window will appear.

Expand/collapse all nodes

(S4)PACG 200 SP09

Use the buttons ‘Expand comp. conf.’ and ‘Collapse comp. conf’ to show/hide all company-specific configuration nodes: