...
...
🕑 Block from transfer to FSM /
| Status | ||
|---|---|---|
|
Specify which ERP objects and/or file types should be restricted from transfer to SAP FSM. E.g., do not transfer activity attachments to SAP FSM if their file type is ‘PDF’.
...
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.
| Info |
|---|
If company-dependent configuration is maintained, keep the default Outbound configuration empty, otherwise it will add up to the company-dependent blocklist as shown in example 4. |
...
Example 1
Outbound configuration for company 1 | |
|---|---|
ERP Object ID | File Type |
EQUIPMENT | |
PDF files attached to equipment will not be transferred to FSM company 1.
Example 2
Outbound configuration for company 1 | |
|---|---|
ERP Object ID | File Type |
EQUIPMENT | |
No equipment attachment will be transferred to FSM company 1.
Example 3
Outbound configuration for company 1 | |
|---|---|
ERP Object ID | File Type |
No PDF attachment will be transferred to FSM company 1.
Example 4
Default outbound configuration | |
|---|---|
ERP Object ID | File Type |
EQUIPMENT | |
PDF files attached to equipment will not be transferred to any FSM company, regardless of company-dependent outbound configuration.