| 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). |
...
❗ Requred class assignment correction
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.
Transaction | Message type | Field name | Idoc class |
|---|---|---|---|
/PACG/ECM_CLSASSIG | /PACG/ECM_ATTCHMOUT | IDOC Class | /PACG/ECM_CL_S_IDOC_O_ATTCHM2 |
/PACG/ECM_CLSASSIGIN | /PACG/ECM_ATTCHMIN | Inb. Data Creat. | /PACG/ECM_CL_S_IDOC_I_ATTCHM2 |
/PACG/ECM_CLSASSIGIN | /PACG/ECM_SIGNATURE | Inb. Data Creat. | /PACG/ECM_CL_S_IDOC_I_ATTCHM2 |
...
| Table of Contents | ||
|---|---|---|
|
General overview
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.
...
Max. attachment size | Enter the maximal allowed attachment size for outbound attachments. If no value is entered, the value of 5242880 bytes will be used. |
|---|---|
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.
...
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.
...
New DMS key structure is as seen below. It provides unique key for each file from DMS document. This key is built based on SAP data element: /PACG/ECM_DMS_KEY
...
Configuration tables
...
Class assignment
Redesigned attachment handling is implemented in new idoc classes.
...
Message type
...
Idoc class
...
Inbound/outbound
...
/PACG/ECM_ATTCHMOUT
...
/PACG/ECM_CL_S_IDOC_O_ATTCHM2
...
outbound
...
/PACG/ECM_ATTCHMIN
...
/PACG/ECM_CL_S_IDOC_I_ATTCHM2
...
inbound
...
/PACG/ECM_SIGNATURE
...
/PACG/ECM_CL_S_IDOC_I_ATTCHM2
...