| Status | ||||
|---|---|---|---|---|
|
| Note |
|---|
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 DMS/ArchiveLink (obsolete)) should no longer be used, as well as attachment-related fields in company configuration transactions (/PACG/ECM_COMP - Company definition, /PACG/ECM_CPROP - General Properties of FSM Cloud Connector). |
...
Required actions to perform before usage :
...
- class assignment update
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.
...
Collective attachment configuration has been designed to enable parallel usage of all three storage type solutions (GOS, BDS or DMS) for inbound attachments, depending on company, related ERP object type or file type. Additionally, attachments of a certain file type and/or company can be blocked from transfer to SAP FSM.
...
Correspondence to obsolete transactions
...
Max. attachment size | Enter the maximal allowed attachment size for outbound attachments.
Attachment size should be also adjusted in SAP FSM company settings - ‘CompanySettings.MaxAttachmentSize’.  | ||
|---|---|---|---|
Allow attachment deletion | Allow deletion of attachments from SAP FSM after deleting related GOS attachments from SAP ECC/S4. | ||
Storage type | Storage type for inbound attachments. Available storage types are:
| ||
Block IN | Block (do not save) inbound attachments. | ||
Block OUT | Block (do not transfer) outbound attachments. |
Company-dependent general attachment configuration
If General attachment configuration is maintained for a specific company, it will be used instead of the default.
...
Overwrite rules for storage type configuration
The storage type maintained in the default (global) General Attachment configuration has the least priority and will be used only if none of the below is maintained for a given company/object/file type pattern.
- The storage type set in the default General Attachment configuration will be overwritten by Company-dependent inbound configuration (object- or file type-specific).
If not found…
- It will be overwritten by General inbound configuration (object- or file type-specific).
If nout found…
...
🕑 Inbound configuration
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 an inbound attachment matches the entered patterns (ERP object ID and/or file type), it will be stored as defined in ‘Inbound configuration’. If no ERP object ID is entered, an entry will be relevant for all objects of a given file type (similarly, if only file type is entered, it will be relevant for all ERP objects).
Company-dependent inbound configuration
Company-dependent inbound configuration has priority over the default Inbound Configuration and will be searched for first. Only if no matching pattern is found, other configurations will be searched.
...
Storage type priority rules
As stated before in this document, storage Storage type determination for inbound attachments follows certain priority rules.
...
- 4. If not found, a storage type would be taken from the default General attachment configuration.
...
Inbound configuration example
The following configuration is maintained:
...
If no ERP object ID is entered, an entry will be relevant for all objects of a given file type. If no file type is entered, an entry will be relevant for all objects with a given ERP object ID.
Company-dependent outbound configuration
A blocklist can also be maintained for specific companies.
...
ERP object ID | Object to which a file is attached to.  |
|---|---|
Document type | DMS document type to be used.  |
Document status | Status to be set for the document.  |
Cumulated | It controls if for every new attachment a new DMS document should be created, otherwise attachments are added to the existing one. DMS creates its own documents to which attachments are added and then these documents are linked with other documents in the system and not attachments themselves |
Default storage category DMS | Storage category links logical storage location with physical one.  |
Folder path | Specify path for document storage.  |
Company-dependent DMS configuration
DMS configuration can be maintained for a specific company. If such an entry is found, it will be used instead of the default.
...
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
Mapping between cloud message types, DOKOB (Linked SAP object) types, business types and ERP objects.  This mapping used to be partially ‘hard-coded' and should not be modified unless with special caution and reason.
|
Inbound configuration - process
...
examples
DMS
According to the company-dependent Inbound configuration below, all service call attachments from company 1 will be saved as DMS attachments.
...