Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 65

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.

...

Collective attachment configuration has been designed to enable parallel usage of all three storage type solutions (GOS, BDS or DMS), depending on company, related ERP object type or file type.

...

Additional attachment enhancements

Along with introduction of the combined configuration transaction, additional attachment-related features have been added to FSM Cloud Connector, including:

  • Automatic transfer of GOS and BDS attachments to SAP FSM after creating them in SAP ECC/S4. Automatic transfer of DMS attachments to SAP FSM after checking in and saving in SAP ECC/S4.

  • Reconstruction of DMS attachment keys. Learn more: Migration of DMS attachments (due to key change).

  • A BAdI for adding UDFs to attachments (/PACG/ECM_UDF_IN_ATTM, called in method /PACG/ECM_IF_A_ATTACHMENTS~RECEIVE_SAVE of class /PACG/ECM_CL_A_ATTACHMENTS).

Correspondence to obsolete transactions

...

Obsolete transaction

...

New attachment configuration

...

/PACG/ECM_ARCH – Relevant Archive Link Objects

...

/PACG/ECM_DMSI – Determine SAP DMS Doc. Cloud->SAP

...

DMS configuration (default or company-dependent)

...

/PACG/ECM_DMSO - Determine SAP DMS Doc. SAP->Cloud

...

/PACG/ECM_CDMS - Set folder path to store inbound attachments for DMS

...

📁 SAP standard attachment configuration

Use these links to navigate to SAP standard attachment configurations - OAC2, OAC3 and DC10. These system configurations should be maintained for proper processing of DMS and BDS attachments.

...

🔗 OAC2 - SAP ArchiveLink: Global doc. types

Maintain global document types for BDS attachments.

...

Link object types with document types and content repository ID for BDS attachments.

...

🔗 DC10 - Define document types

Define document types and object links for DMS attachments.

...

📁 Default configuration

Maintain a set of default (global) attachment configurations. This data will be used if no company-dependent configuration is found (see folder Company dependent configuration).

...

📁 Company Dependent configuration

The set of configuration transactions (General attachment configuration, Inbound configuration, Outbound configuration and DMS configuration) can be maintained on company level. If a company-dependent configuration is found, it will be used instead of the global default (configurations in folder Default configuration).

...

🕑 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.

...

...

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. When an attachment is created for a service order in SAP ECC/S4 and this field is checked, attachment reference will be created for the related activities (also in SAP ECC/S4). Such activity attachments will be automatically transferred to SAP FSM, if not blocked by the outbound configuration (e.g. setting ‘block out’ in the General configuration).

...

Link SAP Notif Atta

...

Activities can inherit attachments from the related notifications. When an attachment is created for a notification in SAP ECC/S4 and this field is checked, attachment reference will be created for the related activities (also in SAP ECC/S4). Such activity attachments will be automatically transferred to SAP FSM, if not blocked by the outbound configuration (e.g. setting ‘block out’ in the General configuration).

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…

  • It will be overwritten by Company-dependent General attachment configuration.

🕑 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).

Info

Notice that one field functions different than the field with the same name placed in the General attachment configuration (see the table below).

...

Link SAP SO Atta

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 new activity attachment will be transferred to SAP FSM.

...

Correspondence to obsolete transactions

Obsolete transaction

New attachment configuration

/PACG/ECM_ARCH – Relevant Archive Link Objects

SAP standard transactions OAC2 and OAC3 available as links in folder SAP standard attachment configuration

Image Added

/PACG/ECM_DMSI – Determine SAP DMS Doc. Cloud->SAP

DMS configuration (default or company-dependent)

Image Added

/PACG/ECM_DMSO - Determine SAP DMS Doc. SAP->Cloud

No direct correspondence. Certain attachments can be restricted from transfer to SAP FSM based on object type and/or file type in Outbound configuration

Image Added

/PACG/ECM_CDMS - Set folder path to store inbound attachments for DMS

Field ‘Folder path’ in DMS configuration

Image Added

📁 SAP standard attachment configuration

Use these links to navigate to SAP standard attachment configurations - OAC2, OAC3 and DC10. These system configurations should be maintained for proper processing of DMS and BDS attachments.

...

🔗 OAC2 - SAP ArchiveLink: Global doc. types

Maintain global document types for BDS attachments.

...

Link object types with document types and content repository ID for BDS attachments.

...

🔗 DC10 - Define document types

Define document types and object links for DMS attachments.

...

📁 Default configuration

Maintain a set of default (global) attachment configurations. This data will be used if no company-dependent configuration is found (see folder Company dependent configuration).

...

📁 Company Dependent configuration

The set of configuration transactions (General attachment configuration, Inbound configuration, Outbound configuration and DMS configuration) can be maintained on company level. If a company-dependent configuration is found, it will be used instead of the global default (configurations in folder Default configuration).

...

🕑 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.

...

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’.

Image Added

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.

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…

  • It will be overwritten by Company-dependent General attachment configuration.

🕑 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.

...

  • 4. If not found, a storage type would be taken from the default General attachment configuration.

...

Example

The following configuration is maintained:

...

Max Att size

Allow atta deletion

Storage type

Block in

Block out

Link SAP SO Atta

Link SAP Notif Atta

52428800

x

G

🕒 Inbound configuration

ERP Object ID

File Type

Storage type Link SAP SO Atta

ACTIVITY

G

📁 Company-dependent configuration

...

Max Att size

Allow atta deletion

Storage type

Block in

Block out

Link SAP SO Atta

Link SAP Notif Atta

52428800

x

B

🕒 Inbound configuration

ERP Object ID

File Type

Storage type Link SAP SO Atta

SERVICECALL

B

SERVICECALL

PDF

D

EQUIPMENT

D

...

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.

...