Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourYellow
titleAdd-on version 200

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.

...

Max. attachment size

Enter the maximal allowed attachment size for outbound attachments.

Note

If no value is entered, the value of 5242880 bytes will be used.

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:

  • B - BDS

  • D - DMS

  • G - SAP Office (GOS)

  • U - customer’s solution (with BAdI)

Block IN

Block (do not save) inbound attachments.

Block OUT

Block (do not transfer) outbound attachments.

Link SAP SO Atta

Activities can inherit attachments from the related service orders.

Inbound attachments (from SAP FSM)

If a service call attachment is received from SAP FSM and this field is set, attachment reference will be added to the related activities and the activity attachment will be transferred to SAP FSM.

Info

Keep in mind that this setting can be effected by the General/Inbound attachment configuration for SERVICECALL objects. If an attachment is relevant for saving for SERVICECALL objects, the attachment reference will be created for the related activities as well, regardless of the customizing for ACTIVITY objects. Similarly, if an attachment is not relevant for saving for SERVICECALL objects, the attachment reference will not be created for activites.

Outbound attachments (from SAP ECC/S4)

This field is checked during outbound processing of service order attachments. If it’s set, an attachment reference will be added to the related activities and the activity attachments will be transferred to SAP FSM.

Info

Keep in mind that this setting can be affected by the outbound attachment configuration. E.g. if all outbound attachments are blocked, attachment reference will not be created for an activity.

Link SAP Notif Atta

Activities can inherit attachments from the related notifications.

Inbound attachments (from SAP FSM)

If a notification attachment is received from SAP FSM and this field is set, attachment reference will be added to the related activities and the activity attachment will be transferred to SAP FSM.

Info

Keep in mind that this setting can be effected by the General/Inbound attachment configuration for NOTIFICATION SERVICENOTIFICATION objects. If an attachment is relevant for saving for NOTIFICATION SERVICENOTIFICATION objects, the attachment reference will be created for the related activities as well, regardless of the customizing for ACTIVITY objects. Similarly, if an attachment is not relevant for saving for NOTIFICATION SERVICENOTIFICATION objects, the attachment reference will not be created for activites.

Outbound attachments (from SAP ECC/S4)

This field is checked during outbound processing of notification attachments. If it’s set, an attachment reference will be added to the related activities and the activity attachments will be transferred to SAP FSM.

Info

Keep in mind that this setting can be affected by the outbound attachment configuration. E.g. if all outbound attachments are blocked, attachment reference will not be created for an activity.

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.

...

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.

...