Block from transfer to FSM / Outbound configuration
- proaxia
- Alicja
Block from transfer to FSM / OLD LABEL Outbound configuration
Specify which ERP Objects, File Type or Storage Type 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 (eg. PDF, TXT, XML),
If no File Type is entered, an entry will be relevant for all objects with a given ERP Object ID (eg. ACTIVITY, SERVICECALL, EQUIPMENT),
(S4)PACG 200 SP15 If no Storage Type is entered, an entry will be relevant for all objects with a given Storage Type (eg. BDS, DMS, GOS).
(S4)PACG 200 SP16 If no ‘Older than (in months)’ is entered, attachment creation date will not restrict transfer.
Company-specific outbound configuration
A blocklist can also be maintained for specific companies.
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
Company-specific configuration - Block from transfer to FSM - Company 1000 | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
EQUIPMENT |
| |
PDF files attached to equipment will not be transferred to FSM company 1000.
Example 2
Company-specific configuration - Block from transfer to FSM - Company 1000 | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
EQUIPMENT |
|
|
No equipment attachment will be transferred to FSM company 1000.
Example 3
Company-specific configuration - Block from transfer to FSM - Company 1000 | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
|
| |
No PDF attachment will be transferred to FSM company 1000.
Example 4
Default configuration - Block from transfer to FSM | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
EQUIPMENT |
| |
PDF files attached to equipment will not be transferred to any FSM company, regardless of company-dependent outbound configuration.
Example 5
Default configuration - Block from transfer to FSM - Company 1000 | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
EQUIPMENT | GOS | |
PDF file attached to equipment as GOS will not be transferred to FSM company 1000.
Example 6
Default configuration - Block from transfer to FSM - Company 1000 | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
|
| BDS |
No BDS object will be transferred to FSM company 1000.
Example 7
Default configuration - Block from transfer to FSM | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
EQUIPMENT |
| DMS |
DMS attached to equipment will not be transferred to any FSM company, regardless of company-dependent outbound configuration.
Example 8
Default configuration - Block from transfer to FSM - Company 1000 | ||
|---|---|---|
ERP Object ID | File Type | Storage Type |
| GOS | |
PDF file attached as GOS will not be transferred to FSM company 1000.
Related content
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.