Introduction to customizing

This subsection serves as a high-level overview of selected FSM Cloud Connector customizing steps. Please note that the hereby listed transactions are just a fraction of all transactions delivered with FSM Cloud Connector, each of them is described in the https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952499 section. All FSM Cloud Connector transactions can be accessed via area menu /PACG/EC or using dedicated t-codes.

Plenty of customizing transactions require transfer of objects to FSM. This is indicated by an entry in the Corresponding sending transaction column, e.g. after defining service call types (SAP order types) relevant for FSM, they must be transferred to FSM using the dedicated sending transaction, otherwise they won’t be visible there. (S4)pacg 200 sp09 Most customizing transactions have a “Send to FSM” button at the top which navigates you directly to the relevant sending transaction.

Open

Open

 

All sending transactions follow a similar logic. Learn more about it under the following link: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138756

Certain objects, new or updated, will be transferred automatically, this applies to service calls, activities, customers, vendors, materials, equipment, functional location - keep in mind that if objects were created before FSM Cloud Connector and we want to have them in FSM, they must be transferred manually.

To copy existing configuration from one company to another or compare two companies, use transactions https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1918926882 and .