General purpose | Each FSM Company must be added to this customizing. Maintain general FSM company data, such as address or time zone. Company address maintained here will be replicated to SAP FSM (see tab ‘Company information’ in the FSM Admin module) and can be then used for report generation. |
|---|---|
Sending transaction (?) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138939 (S4)PACG 200 SP09 You can navigate to the sending transaction using the button Send to FSM, placed on the toolbar. |
Object assignment (?) | Object COMPINFO must be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company |
Within SAP FSM, companies need to be defined. A company usually corresponds to a legal independent company (e.g. country subsidiary) or the part of a company.
Learn more about company creation: Create FSM Companies.
According to the Company in the FSM Cloud Connector, a Company ID and the logical system (transaction BD54) are associated with each other so that the message exchange can be executed.
If logical systems different on test and prod systems and transport is conducted, the target logical system would get overwritten. To fix this. adjust logical system on the target system in /PACG/ECM_COMPL - Logical system for company.
Customizing options
Email Text | Name of the standard text (SO10) which will be used in the Mail in case of Service reports sent by the FSM App. |
|---|---|
PDF Small Text1 | Name of the standard text 1 (SO10), which will be used at the beginning of Offline Service Report which is created by the FSM App. |
PDF Small Text2 | Name of the standard text 2 (SO10), which will be used at the beginning of Offline Service Report which is created by the FSM App. |
Role for BILLTO | SAP Business Partner Role which will be mapped as standard Bill-To address of a Business Partner in FSM App. |
MaxAttSize (obsolete) | You can define the max. Size of an attachment which can be used in the FSM App. Starting from FSM Cloud Connector Add-On version 200, the entire attachment configuration should be maintained with transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/842661889. Attachment-related fields in company configuration transactions (https://proaxia-prod-doc.atlassian.net/wiki/pages/resumedraft.action?draftId=31953211, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515) should no longer be used. This particular customizing from now on should be maintained in node General attachment configuration, field ‘MaxAttSize’ of the new Attachment configuration. |
Time Zone | Time Zone of the Company |
Time Zone (the second one) | If the found time zone is equal to the company time zone and the time zone id is maintained, then the time zone id will be taken from the company and not from /PACG/ECM_TZCNV - time zone conversion table. |
Tzone Customer | This setting should not be used anymore – check Use TimeZone in /PACG/ECM_CTET - Time Effort Type. If this flag is set the Time Zone of the Customer is used when posting time efforts. It assumes the mobile device was in the time zone of the customer when capturing the data. |
Tzone Syst | Get time zone from TTZCU table. The entry found in this table is based on the time zone of the client (maintained in STZAC). |
MultiBranch Enabled | Do not use. Refer to Branch |
Def. Price List | Default price list type |
Def. Payt Terms | Default customer payment terms. |
Def.Locale | Default locale of the company |
Distance metrics | Do not use. |
Hide FSM Logo | Do not use. |
Use WFM | This field should be considered obsolete. Usage of this field is fully eliminated since release 2202, it was also removed from the customizing transaction. In FSM Cloud Connector SP 2 for add-on 200 and older, it should be checked to enable sending open activities without a technician as ‘DRAFT’. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135519 Distinguish if the actual planner is used Based on HTML or the previous resource planner Based on Silverlight. |
NumOfYears | Holiday calendar integration | Specify how many years should be calculated and sent to FSM for holidays depending on Easter date (holiday rule ‘V' in table THOL) or with fixed weekday (holiday rule 'W'). The field is also used to calculate ‘valid to’ value of holiday calendars which are valid only in the past. In such a case the ‘valid from’ value is the current year and the 'valid to’ is the current year plus the number specified in this field. Learn more about the calendar integration feature: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/564166714 |
External Id | Add 'External ID' property to outbound idocs of all the SAP FSM objects sent to the specific company. External ID set up allows access to FSM objects created by third parties, additionally allows third parties to map with FSM objects generated from SAP ECC/S4. If checked, all objects transferred to SAP FSM will contain an additional segment - /PACG/ECM_IS_EXTERNAL, with field EXTERNALID. The field stores the object’s external ID (by default, SAP key, the same as the object’s main ID).  This property corresponds to field ‘externalId’ in SAP FSM DTOs. |