FSM Component Manager Extension: Installation Guide

Owned by Zied Ouerghemi
Last updated: Sept 22, 2023
6 min read

1. System requirements

Before proceeding with FCM extension installation, these requirements are mandatory:

  • Integrated ERP system (SAP ECC or S/4 backend) through Proaxia FSM cloud connector – Service pack 9 or higher. . 

  • FCM Extension License.

  • ERP Transport installation (provided by proaxia).

2. Extension installation

In order to make the installation of FCM extension possible, it is necessary to set up the application authentication by Business Technology Platform services for FSM account and grant access permissions for each company.

Account & Company informations

To access your FSM API, the technical FSM account & company informations are needed.

  • From the account details, the customer is required to provide:

Account ID
Name
Cluster

  • From the company details, the following are required:

Company ID
Name

FCM Extension installation in FSM

  1. Once FCM extension route URL is provided by Proaxia Team (after all of the above info are available), select FSM Foundational Services menu.

 

  1. From ‘Directory', click on FCM Extension tile then choose 'Install’.

 

  1. Enter the App route URL provided by Proaxia then click on 'Next step'.

 

  1. In ‘Extension Details’ step click on 'Next Step’, then tick ‘I agree that SAP will share my data with Proaxia.’ checkbox and press ‘Next step’ again.

 

  1. Choose ‘Service call Modal Acivity Outlet Tab’ and Click on 'Finish'.

3. SAP Transport installation:

Transport importation

Once agreed with proaxia on the extension usage, an SAP Transport contains all necessary configurations for FCM extension integration with your SAP backend system (such as UDO and UDF…) will be provided under 2 files, starting with K* and R*.

Please, store these files in dedicated folder and save the path.

Example:

 

Next step is to call transaction /PACG/ECM_TRANSP_IMP and to fill in all the fields.

Selection screen of transport importation program:

  1. Path – Local - this is the path where you stored two files provided by proaxia.

  2. Path – Server (DIR_TRANS) - This is path to application server location where the files will be stored. We recommend using default value.

  3. File Extension – This is the system from which we created these files. In our case it is ‘ERD’.

  4. Transport Nr – This is the number of transport, please, double check this value to make sure that the number is the same as in provided files.

 

In next step please, execute the program and check if the log contains success messages only:

Then, please open t-code STMS. In this step, using the following setting we will upload that transport into transport queue:

Confirm the upload and import the request into your system using ‘Import Request’ functionality.

Setup program:

Once the transport is successfully imported, run the setup program (t-code /PACG/FSME_RM_SETUP).

  1. FSM Company ID - This is a list of FSM companies for which the installation will be performed.

  2. Generate UDFs (Configuration) - Generating ‘PACG_ME_*’ UdfMeta that are required for the FCM extension to work properly. The tables that are updated in this step are: /PACG/ECM_UDF1, /PACG/ECM_UDF1T, /PACG/ECM_UDF2.

  3. Send UDFs to the cloud – Transferring newly created UdfMeta to the selected FSM company.

  4. Generate UDOs (Configuration) – Generating ‘PACG_ME_*’ UdoMeta that are required for the FCM extension to work properly. The tables that are updated in this step are: /PACG/ECM_UDO1, /PACG/ECM_UDO1T, /PACG/ECM_UDO2, /PACG/ECM_UDO3.

  5. Send UDOs to the cloud – Transferring newly created UdoMeta to the selected FSM company.

  6. Generate Events – Generation of events definition in t-code SWETYPV (Event Type Linkages).

  7. Generate UdoValue for Plant SH – Creation of values for Plant Search Help in FCE Extension. This logic takes plants from table /PACG/ECM_PLAS (for selected company and OBJID = ‘RMAT’) and creates UdoValues for them.

  8. Generate UdoValue for St.lc SH – Creation of values for Storage Location Search Help in FCE Extension. This logic takes all plants from previous step and then gets storage locations from table T001L.

  9. Test Mode – Validate only - This option allows you to run the program in test mode, in the message log you will find all the elements that will be executed after starting the program in productive mode.

Example of Log when calling the program in test mode:

Generation of UdoValue for existing components

After successful generation of all needed objects the FCM extension can be used in the FSM planning and dispatching board. However, to generate UdoValues for existing components (reservations) within open service orders, we have provided one more program. It’s available by using t-code /PACG/FSME_RM_UDO.

Selection screen of sending program:

  1. FSM Company ID - This is a specific FSM company for which the generation will be performed.

  2. Order – There you can select specific service order number for which the generation will be executed.

  3. Orders created after – This date limit the selection, so that only specific orders are taken into consideration. By default, we use the two years period.

  4. Open FSM activities – By using this checkbox you improve the selection, only orders with open FSM activities are taken into account.

  5. Save log – by default the SLG log will be stored, so it can be analysed who triggered the program and when.

  6. Display log – You can determine if the log should pop up at the end of program execution (if execution in background, that it’s not needed).

  7. Force sending – By default, FSM Cloud Connector prevents re-transfer of a message which was already sent (transfer of an object which was already sent and hasn’t changed ever since). This is called the hash mechanism. To omit that check and re-transfer an unchanged object (e.g. for test purposes or to unblock it in FSM), keep the ‘Force sending’ flag active.