Supply Chain Management Blogs by Members
Learn about SAP SCM software from firsthand experiences of community members. Share your own post and join the conversation about supply chain management.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Tenant Refresh Activities in Field Service Management Cloud

Harinandan-Mayya
Explorer
2 weeks ago
287

Introduction

Tenant refresh is a process that allows you to request a refresh of an existing tenant in SAP cloud for customers. It can be used to provide updated data for testing purposes and facilitate major system upgrades. The main purpose is to ensure that non-production systems are aligned with the production system in term of data and configuration.

 Prerequisites

  •  Personal number should be created to login to FSM cloud account
  • User should have the access, especially Admin access is required to do the backup and restore activities
  • Access to the user should be SUPERUSER and USER
  • User should have a S/4 Hana access

Steps to be performed in refresh activities

  • Download the FSM configuration of the test system (to secure ongoing, non-productive developments)​.
  • Deactivate the users for the period in which the productive system is not available.
  • Start the FSM backup in the production account (if possible, close to the start of the SAP system copy)​.
  • Unlock users
  • Import (restore) the FSM backup into the test account and reassign persons.
  • Deactivate/delete unnecessary users in the test account
  • Upload the FSM configuration from step 1, if performed. In some cases, it may also be necessary to re-upload report templates.
  • Restore communication between SAP test system and test account
  • Perform a start-up test (for new and existing orders)

Download the FSM configuration of the test system (to secure ongoing, non-productive developments)​

  • The Upload / Download Company Configuration functionality aids with setting up and maintaining a company configuration throughout multiple company
  • With this feature, it is possible to upload or download company settings, workflow steps, business rules, email templates, screen configurations, etc.
  • To access the Upload / Download Company Configuration function, you must be assigned the ADMINISTRATOR, SUPPORT, or SUPERUSER role
  • To download or upload a company configuration, navigate to Admin > Account > Companies and select the company for which you wish to upload or download a company configuration.

              HarinandanMayya_0-1725261991732.png

             HarinandanMayya_1-1725261991745.png

  • To download the company configuration, select the checkbox and click on download button. The application will then prompt you to select which objects associated with the company you wish to download

           HarinandanMayya_2-1725261991752.png

  • After selecting the Download button in the form, a file containing the company configuration will be downloaded to your local machine.
  • Please note that if the CoreSystems.Now.CompanyUrl setting is downloaded and used for another company, it will result in errors, as the URL must be unique for a given company.

Deactivate the users for the period in which the productive system is not available.

  • This is necessary to avoid inconsistencies which may occur if objects are created/changed during the copy process.

          HarinandanMayya_3-1725261991762.png

Start the FSM backup in the production account (if possible, close to the start of the SAP system copy)​

  • The Backup and Restore module in Admin enable users with sufficient rights to create a backup of the company database, download it and restore it to any company database.
  • A database backup can have a maximum file size of 1GB compressed (this is roughly 20GB uncompressed)
  • Data from supporting microservices is currently not included in the database backup (e.g., Crowd, Holiday Calendar, OrgStructure)
  • This only includes company level data, account level data, for example SAML configuration, Users and so on are not included.
  • Access to the Backup and Restore module is restricted to users with the SUPERUSER role.
  • To access the Backup and Restore module, navigate to Admin > Account > Company > Backup & Restore

           HarinandanMayya_4-1725261991769.png

  • In the Backup and Restore main navigation you get an overview of your company data and attachments.

Within the Company Backup & Restore screen you can perform the following actions:

  • Get a list of your backups.
  • Create a new backup.
  • Delete existing backup(s)
  • Upload a backup from your filesystem.
  • You can have a maximum of 3 backups stored within each company.

        HarinandanMayya_5-1725261991776.png

Restore a Company Backup without Download and Upload

To restore a company backup without download and re-upload you can follow the following steps in your source company

  • Go to Data Backup & Restore
  • Open the detail page of the backup you would like to restore in a different Account/Company
  • Click Share Backup
  • A onetime secret will be generated - copy and save it from the interface
  • The secret can only be used once and is only valid for 30 minutes - if you leave the page the secret can’t be retrieved anymore

           HarinandanMayya_6-1725261991782.png

          HarinandanMayya_7-1725261991793.png

In your Target Company

  • Go to Data Backup & Restore
  • Click Import
  • Enter the Backup Secret from the source company step 4
  • Click Validate
  • Check if the Backup is coming from the correct Source Account ID and Source Company ID
  • Click Restore

         HarinandanMayya_8-1725261991796.png

         HarinandanMayya_9-1725261991798.png

         HarinandanMayya_10-1725261991800.png

         HarinandanMayya_11-1725261991804.png

The backup will be copied to the target company and restored there, depending on the backup size this process can take a while. The backup is further available in the target company.

       HarinandanMayya_12-1725261991807.png

Unlock users​.

Activate the user which are deactivated.

Import (restore) the FSM backup into the test account and reassign persons.

       HarinandanMayya_13-1725261991810.png

Restore a Company Backup

To restore a company backup, you must have a backup listed in the Company Backup & Restore overview.

  • Access a single backup by clicking on the backup name
  • Click Restore and wait until the restore process has finished

          HarinandanMayya_14-1725261991817.png

To re-assign the users automatically based on the username you can do the following steps

  • Access the Persons module of your company
  • Click Reassign Persons to assign persons of your company based on your username to the correct account username

         HarinandanMayya_15-1725261991828.png

Download a Company Backup

To restore a company backup, you must have a backup listed in the Company Backup & Restore overview.

  • Access a single backup by clicking on the backup name
  • Click Download to download this specific backup

Upload a Company Backup

To restore a company backup, you must have a backup listed in the Company Backup & Restore overview.

  • Click Upload in the overview and select a company backup file from your filesystem.

Backup and Restore Attachments

Within the Attachment Backup & Restore screen you can perform the following actions:

  • Get a list of your attachment backups
  • Create a new backup
  • Delete existing backup(s)
  • Upload a backup from your filesystem

     HarinandanMayya_16-1725261991833.png

Restore an Attachment Backup

To restore a company backup, you must have a backup listed in the Attachment Backup & Restore overview.

  • Access a single backup by clicking on the backup name
  • Click Restore and wait until the restore process has finished

 Download an Attachment Backup

To restore a company backup, you must have a backup listed in the Attachment Backup & Restore overview.

  1. Access a single backup by clicking on the backup name
  2. Click Download to download this specific backup

Deactivate/delete unnecessary users in the test account

      HarinandanMayya_17-1725261991839.png

Upload the FSM configuration from step 1, if performed

      HarinandanMayya_18-1725261991845.png

Add the downloaded file and select the checkbox, then click on upload

     HarinandanMayya_19-1725261991850.png

Restore communication between SAP test system and test account (Webservice, Technical User passwords, Company Account Mapping)

E4C Configuration in SAP ECC

Delete the mappings in Quality system, which is copied from Production system. Transaction

/PACG/ECM_DEL_MAP_N or via below step

        HarinandanMayya_20-1725261991899.png

Mention the company ID and uncheck the simulation run and execute

      HarinandanMayya_21-1725261991911.png

Selecting all the indicator and clicking on Delete mappings once delete logs can be checked via Display log, if this step is not done, inbound idoc will move into 68 statuses.

       HarinandanMayya_22-1725261991931.png

Update the FSM account and company details. The company name should be the same while created in the cloud. Transaction /PACG/ECM_CACC.

     HarinandanMayya_23-1725261991940.png

 

Check if the FSM related Partner profile in WE20 and port in WE21 is still existing in Quality system after system copy.

        HarinandanMayya_24-1725261991953.png

If these records disappeared after system copy You must create new ones.

In transaction WE20 go to partner profile and then create new record.

Partner No. – should be the same as company name.

Partner Type – choose “LS” logical system.

Ty. – type of responsible for this system it could be department or user etc. in our case it is US (user)

Agent – SAP ID of responsible person

Lang. – main language

       HarinandanMayya_25-1725261991972.png

Webservice in SAP ECC

Check the webservice set up for Quality System. (It is copied from Production system, hence the Quality system set up is overwritten)

     HarinandanMayya_26-1725261992004.png

After clicked the button SOAMANAGER You will go to window

     HarinandanMayya_27-1725261992024.png

Check the username and password from Message broker file for Quality system

HarinandanMayya_28-1725261992043.png

If the Service is deleted after a system copy, then create a new service with below steps indicated in screen shots.

     HarinandanMayya_29-1725261992063.png

Save the service and check if the service is active.

The technical user used to log in to SAP ECC/S4

Make sure to verify the technical user used for authentication to SAP system by Message Broker (Message Broker configuration file àsection SapDefinitions). This check should include –

  • Username
  • Password
  • Validity Dates
  • The lock indicator

Technicians/Planners set up for Quality System

After system copy, the technicians list is copied from Production system to Quality system. As we do not need to activate all the technicians/planners, delete the users which are not needed.

Path to delete the users copied from production and to update only the required test users is as follows

HarinandanMayya_30-1725261992083.png

Warehouse setup for Quality System

In some cases, when system is copied, it is necessary to maintain settings for warehouse again. Path to maintain the Warehouse /PACG/ECM_WRHOUSE.

     HarinandanMayya_31-1725261992095.png

If warehouse is missed, it is necessary to make new entry.

    HarinandanMayya_32-1725261992108.png

Number Ranges for Checklist Templates

If there are checklist templates in FSM that do not exist in SAP ECC/S4, checklist template number range must be changed. E.g. when a production system is copied, the related FSM company may already have multiple checklists created and each of them is mapped with an SAP id. If a new checklist template version is created, a generic idoc may end up with status 40 because of a failed attempt to map the new FSM id with an SAP id previously mapped with another FSM id. To avoid the consumption of already used IDs, navigate to transaction SNRO and increase the NR status field for number range /PACG/CLTT: -

      HarinandanMayya_33-1725261992114.png

If there are checklist templates in FSM that do not exist in SAP ECC/S4, checklist template number range must be changed.

Message Broker and FSM Cloud Company Configuration

 Message Broker Update

Get the existing E4C configuration file from message broker and update the message broker file with the company names for the new/updated company.

      HarinandanMayya_34-1725261992117.png

 

Once the file is updated, restart the windows service.

Send the data from ECC to FSM

Using ‘Trigger initial synchronization’ from cloud, which request all the data from ECC. No manual interference is needed except Idoc monitoring. This step also creates a lot of Idoc depending on the business data in your ECC system.

        HarinandanMayya_35-1725261992120.png

Perform a start-up test (for new and existing orders)

Once the setup is done, we can check the order is getting dispatched to FSM and, we can check the exiting order before the refresh activity.

 Reference link: 

 

 

Labels in this area
Popular Blog Posts