Attachment size configuration is necessary for proper inbound and outbound attachment handling. Allowed attachment size can be adjusted in:
Example recommended values:
Customizing | Recommended value |
|---|---|
FSM company settings (CompanySettings.MaxAttachmentSize) | 20,971,520 Bytes (= 20 MB) |
Message Broker configuration file | Maximum (for Windows 2.0, see: [WINDOWS 2.0] Maximum message size for webservices, for Windows 3.0/Linux set value '0'). |
Transporter settings (TransporterSettings.TransferDocumentSize) | The new transporter version - 1000, the older version - 20 |
FSM Cloud Connector (/PACG/ECM_CUST_ATTA) | In the newer FSM Cloud Connector version generic idocs (resent to FSM after adding an attachment in FSM) are significantly lighter than the attachments themselves. In the older version the max. att. size should be aligned with the max. att. size set in FSM company settings. |
FSM company settings
Use the FSM company setting CompanySettings.MaxAttachmentSize to specify the maximum allowed size of attachments added in SAP FSM (e.g. the mobile app). It is recommended that the allowed attachments size doesn’t exceed 20 MB.
Message Broker configuration file
Windows 2.X
To adjust the possible message size for webservices (e.g. to transfer large/multiple attachments), maintain the following Http Binding settings in the Message Broker configuration file:
[WINDOWS 2.0] Maximum message size for webservices
The attachment size specified in Message Broker settings should be bigger than the one allowed in FSM Company setting CompanySettings.MaxAttachmentSize. This is because the inbound attachment files are converted to XML in SAP ECC/S4 and the XMLs become slightly bigger after conversion. As a result, such attachments could cause Message Broker to crash because of memory lack.
Windows 3.X
In the newer Message Broker version, property MaxRequestBodySize defines the maximum size of http request the web service will accept. If not provided, .NET default is used, which is 30000000 (around 28 MB). If MaxRequestBodySize is set to 0, no limit is applied. This is customized in the application configuration file: [WINDOWS 3.X] Application config file
Linux 3.X
Similar to the Windows 3.X version of Message Broker, property MaxRequestBodySize defines the maximum size of http request the web service will accept. If not provided, .NET default is used, which is 30000000 (around 28 MB). If MaxRequestBodySize is set to 0, no limit is applied. This is customized in the application configuration file: [LINUX 3.X] Application config file
Transporter settings in FSM company settings
TransporterSettings.TransferDocumentSize
FSM Cloud Connector, transaction /PACG/ECM_CUST_ATTA, node General Attachment configuration, field MaxAttSize
Use this customizing to not allow sending attachments bigger than the specified size (in bytes) from SAP ECC/S4 to SAP FSM. If no value is entered, the value of 5242880 bytes (5.24 MB) will be used.
// the conversion thing and that MB setting must be bigger than FSM
// the transporter thing
// the attachment resending thing and how it’s affected by CUST_ATTA max att. size
// example recommended values