Master data
- proaxia
- Alicja
This subsection serves as a high-level overview of selected FSM Cloud Connector customizing steps for master data objects:
Master data customizing determines which SAP ECC/S4 objects can be transferred to SAP FSM and with which properties. For more detailed descriptions, navigate to links included in each step.
Sending transactions for master data are usually used to transfer individual objects/a small fraction of objects for test purposes. On production systems, master data (and other customizing data) is usually transferred collectively via full sync. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1831108615
Selected integration relationships, i.e. how SAP objects are reflected in FSM:
SAP ECC/S4 | SAP FSM |
Material | Item |
Customer/Vendor/Business Partner | Business Partner |
Storage location | Warehouse |
Order component | Reserved material |
HR employee / SAP user | User (admin) / Person (master data) |
Work schedule | Work time pattern |
HR absence | Person reservation |
Object assignment
Configuration Step | Customizing transaction |
Specify if a given FSM object type should be relevant for transfer to a given FSM company based on its assignment to a plant/sales area/personnel area/purchasing organization/company code assignment. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952548 |
Specify which sales area/plant/personnel area/purchasing organization/company code a given object type must be assigned to in order to be relevant for transfer to a given FSM company | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565 ; https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952576 ; https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952587 ; https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952598 ; https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1615069187 |
Certain objects are not dependent on any of the assignment areas above. Specify if it should be possible to send all objects of a specific type to a given FSM company. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 |
To ensure that all FSM Cloud Connector objects will be communicated from SAP ECC/S4, you can transfer the list of so-called supported objects | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1448935436 |
Users
Configuration Step | Customizing transaction | Corresponding sending transaction |
Assign personnel areas relevant for employee transfer. Employees assigned to them can be transferred to a given FSM company (use object type ‘EMPLOYEE’) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952587 |
|
Binding between an SAP user (PERSON of type ‘ERPuser’) and an HR employee (PERSON of type ‘EMPLOYEE’) is maintained via infotype 0105 Communication, subtype 0001 | PA30 |
|
Maintain general user settings, such as user name source or email source | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138277 |
|
FSM-relevant users must be entered in one of the user maintenance transactions, otherwise it won’t be possible to transfer them to SAP FSM | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601665 / https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601806 |
|
Specify how person address should be determined. Learn more about Person address: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1461092377 | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953288 |
|
Permission groups (assignment to User Policy Groups) can be managed from SAP ECC/S4, if permission group IDs are maintained in a dedicated customizing. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/360218625 |
|
FSM user entries can be created automatically after assignment of a specified user role to an SAP user. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/521764887 |
|
Customize how employee’s skills sent to SAP FSM should be determined. See an example of skill/tag creation and transfer to SAP FSM: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/857210891. Learn more about prerequisites for REQUIREMENT transfer and the delivered BAdI implementation: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38175423 | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137524 | /PACG/ECM_TRIG_TAG - Tag send; /PACG/ECM_TRIG_SKILL - Skill send |
Optionally enter period work schedules which can be transferred to FSM as work time patterns. Transfer technician assignment to such a schedule. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1216970914 | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1216970914 |
Optionally customize what should be sent to FSM as regions (geographical regions or work centers) and how regions should be determined for technicians. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136514, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138382 | /PACG/ECM_TRIG_RGPWC - Work center as Region or /PACG/ECM_TRIG_RGPAR - Address region as Region |
Business partners
Configuration Step | Customizing transaction | Corresponding sending transaction |
Assign sales areas relevant for customer transfer. Customers assigned to them can be transferred to a given FSM company (use object type ‘CUSTOMER’) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565 | CUSTOMER MASTERDATA: /PACG/ECM_CUSTMASTER - Customer, address, contact person |
Assign purchasing organizations relevant for vendor transfer. Vendors assigned to them can be transferred to a given FSM company (use object type ‘VENDOR’) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952598 | VENDOR MASTERDATA: /PACG/ECM_VENDMASTER - Vendor, address, contact person |
Specify if SAP business partners (see transaction BP) are used on the system and should be used to determine contact persons | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515 |
|
Specify which customer/vendor account groups in SAP ECC/S4 are relevant for SAP FSM and as which customer groups they should be reflected in SAP FSM (CUSTOMER/LEAD) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953445 ; https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137589 |
|
Specify how customer addresses should be determined. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1166606379 and/or https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2309259265 |
|
A variant of the transaction above, which uses account groups | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953423 |
|
If Business Partners are used on a given system (see transaction BP), you must specify which BP roles are allowed for being used as an FSM customer, supplier or contact person. The customizing is prefilled by the setup program. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1645805569 |
|
Equipment
Configuration Step | Customizing transaction | Corresponding sending transaction |
Assign plants relevant for equipment/functional location transfer. Equipment/functional locations assigned to them can be transferred to a given FSM company (use object type ‘EQUIPMENT’) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952576 | EQUIPMENT/FUNCTIONAL LOCATION MASTERDATA: /PACG/ECM_EQUI - Equipment Master; /PACG/ECM_TRIG_TELO - Functional Location |
Specify general equipment/functional location settings | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953646 |
|
Specify how equipment’s address should be determined. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953663 |
|
Specify which equipment/functional location categories are relevant for transfer to SAP FSM | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953738 https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953761 |
|
Optionally specify which equipment/functional location types are relevant for transfer to SAP FSM | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953778 https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953795 |
|
Transfer equipment/functional location as deleted, permanently deleted, inactive, active or not at all based on system or user status of the transferred object | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953812 |
|
Generate UDFs based on a characteristics class which will store equipment characteristics. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138716 | /PACG/ECM_TRIG_UDF - UDF Definition |
Optionally allow transfer of measuring points and readings created for a given equipment. Decide for which equipment/func. loc. categories transfer of measuring points and documents is allowed, as well as which measuring point categories are relevant for FSM. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953738 / https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953761, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/73072660 |
|
Items
Object assignment scenarios for materials
Additional settings impacting transfer of materials to FSM
Configuration step | Customizing transaction |
Specify which material types are relevant for transfer to SAP FSM. | |
Based on material’s status, a material can be sent to SAP FSM as active, inactive, deleted or not at all |
|
Settings impacting properties of transferred materials
Configuration step | Customizing transaction |
Maintain additional material settings on material type level. | |
Maintain additional material settings on company level | |
Specify if materials which are simultaneously batch-managed and serialized in SAP ECC/S4 should be transferred to FSM as batch or serial materials (in SAP FSM an item can be managed only either by serial numbers or batches, not both). | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31954010 |
Based on material’s status, a material can be sent to SAP FSM as active, inactive, deleted or not at all |
|
Warehouses
Configuration Step | Customizing transaction | Corresponding sending transaction |
Specify how a warehouse description should be constructed | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137615 |
|
Define FSM-relevant warehouses - the ones which are relevant for sending, master data, stock levels and material movements sending to FSM. Define warehouses' owners and additional owners (technicians’ ‘own’ stocks). | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1651048453 |
|
Define FSM-relevant consignment stocks (customer’s number needs to be provided). To assure warehouse visibility in FSM, an owner must be defined. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1650688053 |
|
Define which stock level quantities for material can be sent to SAP FSM, beside the available stock level per storage location. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31954055 |
|
Attachments
Configuration Step | Customizing transaction |
The collective attachment configuration has been designed to enable parallel usage of three storage type solutions (GOS, BDS or DMS) for inbound attachments. A specific storage type for attachments from FSM can be determined based on a company ID and/or object type and/or file type. Additionally, users can define a list of object types/file types blocked from transfer to SAP FSM. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/842661889 |
Specify if service order/notification/equipment/functional location attachments added in SAP ECC/S4 should be inherited by the related activities or if attachments added to activities in SAP FSM should be inherited by the related service order/notification/equipment/functional location. Optionally enable transfer of PRT attachments. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135497 |
Specify if attachments added to service calls in FSM should be inherited by the related notifications/activities | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2094727169, fields ‘Copy scall att. from FSM to notif.', 'Copy scall att. from FSM to activities' |
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.