| Status | ||
|---|---|---|
|
🕑 BDS configuration
Due to backwards compatibility, BDS configuration node should be maintained for attachments using this storage method. The configuration should contain relevant object type and document type links from standard SAP transaction OAC3. During processing of inbound attachments it is checked in table TOAOM (related to transaction OAC3) if a given object-document type relationship from the ‘BDS configuration’ node can be found, is active and is related to the relevant document class (e.g. PDF).
The node behaves like the DSM configuration. The configuration option is shown only when BDS is set in customizing as storage type or there are already existing entries in table /pacg/ecm_carch.
There is general and company-specific BDS configuration.
Deletion in FSM |
Determine how deleting an attachment in SAP FSM (stored as BDS in SAP ECC/S4) should affect the files in SAP ECC/S4. [ ] - default, delete the BDS attachment, including the link to the main object (from which an attachment was deleted in FSM) and all other references (links to objects which inherited the attachment based on customizing in transaction /PACG/ECM_ACTIVE or hard-coded logic/PACG/ECM_SCTD). Deletion requests will be sent to FSM for all references. E.g. it is customized in transaction /PACG/ECM_ACTIVE that activities should inherit attachments from service orders. A BDS attachment was added by a user to a service order and inherited by activities. The attachment was removed by a user from the service call in FSM. As a result, it is removed from the service order and activities in SAP ECC/S4. Deletion requests for activity attachments are sent to FSM. R - remove only the link to the main object (the one from which attachment was deleted in FSM), reference objects won’t be affected (e.g. attachments inherited by activities based on settings in transaction /PACG/ECM_ACTIVE)
|
|---|