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.
|
|
|---|---|
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
Stop the Message Broker for the Quality System
Create a new FSM company
Delete the mapping tables on the SAP test system.
Establish communication between SAP test system and test company (checking and repairing web services may be required).
Delete unnecessary FSM users in the SAP test system.
Change number ranges for checklist templates.
Trigger the initial synchronization of all data (full sync).
Upload FSM configuration and checklist templates from the source company. In some cases it may also be necessary to re-upload report templates.
Update general settings for planning and dispatching.
| Note |
|---|
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
...