| 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 E4C). |
...
Required actions to perform before usage
1. Run the setup program
It is required to run the setup program for relevant partners - /PACG/ECM_SETUP - FSM Connector's Setup.
2. 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.
...
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.
...
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.
...
- 4. If not found, a storage type would be taken from the default General attachment configuration.
Example
...
The following configuration is maintained:
📁 Default configuration
🕒 General attachment configuration
Max Att size | Allow atta deletion | Storage type | Block in | Block out |
|---|---|---|---|---|
52428800 | x | G |
🕒 Inbound configuration
ERP Object ID | File Type | Storage type |
|---|---|---|
ACTIVITY | G |
📁 Company-dependent configuration
🕒 0001 - General attachment configuration
Max Att size | Allow atta deletion | Storage type | Block in | Block out |
|---|---|---|---|---|
52428800 | x | B |
🕒 Inbound configuration
ERP Object ID | File Type | Storage type |
|---|---|---|
SERVICECALL | B | |
SERVICECALL | D | |
EQUIPMENTG | D |
🕒 DMS configuration
DMS configuration for company 1 | |||||
|---|---|---|---|---|---|
ERP object ID | Document Type | Document status | Cumulated | DefStorageCat DMS | Folder path |
ZPK | MU | DMS_C1_ST | /tmp/ | ||
SERVICE CALL | ZXK | MS | DMS_C1_ST | /tmp/ | |
Service call attachments
...
created in FSM company 1
...
According to the inbound configuration for company 1 (which is used first):
Service call attachments of file type other than PDF , will be stored as DMS BDS attachments. Other service
Service call attachments of file type PDF, will be stored as BDS DMS attachments. Equipment attachments from FSM company 1
According to the DMS configuration for company 1:
Service call attachments stored as DMS will use document type ‘ZXK’, status ‘MS’ and default storage category ‘DMS_C1_ST’.
Equipment attachments created in FSM company 1
According to the inbound configuration for company 1:
Equipment attachments will be stored as GOS DMS attachments, regardless of their file type.
Activity attachments will be stored based on the default inbound configuration settings, and if they don’t match any pattern found there, based on General attachment configuration.
Example 2
...
Default Inbound configuration
...
ERP Object ID
...
File Type
...
Storage type
...
SERVICECALL
...
B
...
SERVICECALL
...
...
D
...
All inbound service call attachments of file type PDF will be stored as DMS attachments, regardless of the company - if this setting is not overwritten by a company-dependent entry.
...
According to the DMS configuration for company 1:
Equipment attachments stored as DMS will use document type ‘ZPK’, status ‘MU’ and default storage category ‘DMS_C1_ST’ (this setting is relevant for all objects other than service calls).
Activity attachments created in FSM company 1
Since no company-specific inbound configuration is maintained for Activities, the Default inbound configuration is used:
Activity attachments will be stored as GOS.
Item attachments created in FSM company 1
Since no company-specific and default inbound configuration is maintained for object ‘ITEM’, the General attachment configuration for company 1 will be used:
Item attachments will be stored as BDS attachments - if this setting is not overwritten by a company-dependent entry. Equipment attachments will be stored based on the company-dependent inbound configuration settings, and if they don’t match any pattern found there, based on General attachment configuration.
Item attachments created in FSM company 2
Since no company 2-specific and default inbound configuration is maintained for object ‘ITEM’, and the General attachment configuration is only maintained for company 1, the default General attachment configuration will be used:
Item attachments will be stored as GOS.
🕑 Outbound configuration
...
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.
| Info |
|---|
If company-dependent configuration is maintained, keep the default Outbound configuration empty, otherwise it will add up to the company-dependent blocklist as shown in example 4. |
...
Example 1
Outbound configuration for company 1 | |
|---|---|
ERP Object ID | File Type |
EQUIPMENT | |
PDF files attached to equipment will not be transferred to FSM company 1.
Example 2
Outbound configuration for company 1 | |
|---|---|
ERP Object ID | File Type |
EQUIPMENT | |
...
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.
...