| Status | ||||
|---|---|---|---|---|
|
...
Maintain default global attachment configuration. This data will be used if no company-dependent configuration is found (see folder Company dependent configuration).
...
🕑 Cloud Message to DMS object configuration
Mapping between cloud message types, DOKOB (Linked SAP object) types, business types and ERP objects.
...
This mapping used to be partially ‘hard-coded' and should not be modified unless with special caution.
...
Field
...
Description
...
Example value
...
CLOUD_OBJECT
...
Cloud message type
...
SERVICECALL
...
BUS_TYPE
...
Type of Objects in Persistent Object References
...
BUS2088
...
OBJID
...
ERP Object ID
...
SERVICECALL
...
DOKOB
...
Linked SAP object
...
AFKO
📁 Company Dependent configuration
Default configurations configuration transactions can be maintained on company level. If a company-dependent configuration is found, it will be used instead of the global default (folder Default configuration).
...
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.
...
🕑 Cloud Message to DMS object configuration
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
Mapping between cloud message types, DOKOB (Linked SAP object) types, business types and ERP objects.  This mapping used to be partially ‘hard-coded' and should not be modified unless with special caution and reason.
|
Inbound configuration - process example
...