Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

One of the possible approaches to system copy involves creation of a new company in the test account and initial synchronization of all FSM-relevant data.

(plus) Pros

(minus) Cons

Cross-system consistency of all master and transaction data

Complex procedure of creating and customizing a new company and all the dependent objects

Summary of the necessary steps

  1. Stop the Message Broker for the Quality System​

  2. Create a new FSM company​

  3. Delete the mapping tables on the SAP test system.​

  4. Establish communication between SAP test system and test company (checking and repairing web services may be required).​

  5. Delete unnecessary FSM users in the SAP test system.​

  6. Change number ranges for checklist templates.​

  7. Trigger the initial synchronization of all data (full sync).​

  8. Upload FSM configuration and checklist templates from the source company.​

  9. Update general settings for planning and dispatching.

Before system copy, note all number range statuses on the test system for number ranges starting with /PACG* (use transaction SNRO, table NRIV or FSM Cloud Connector cockpit). Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/804093999/SAP+GUI#1.5.-Number-ranges

Detailed description of the copy steps

  • No labels