Ansicht
Dokumentation
BP_MIG_PHASE3 - Phase 3: BP Data Migration During Downtime
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
During this phase the customer's productive system will be down. You must not use the system for any purpose other than migration in this phase.
In this phase, data is migrated for those records which are changed, newly-created, or left out during Phase 2. This phase repeats the steps for data migration from Phase 2. It also includes some new steps.
Completing this phase with the step Confirm Migration Success activates the changeover to SAP Business Partner (SAP BP). Once this step is completed, you cannot run any of the migration steps. Hence, SAPstrongly recommends that you migrate all customer-relevant records corresponding to a step before confirming the migration success. Once you complete Phase 3, you can start the productive system and maintain the BPs via the BP transaction.
You must execute all steps in Phase 2 before starting Phase 3. You must execute the following steps during Phase 3:
- Confirm Setting of Migration to Phase 3
- Run Migration of HC BPs and Relationships (available only in General mode)
- Run Migration of HC Business Partners (available only in Expert mode)
- Run Migration of Relationships corresponding to HC BPs (available only in Expert mode)
- Run Migration of Patients and Dependent Objects
- Run Migration of Patients with Prov. Data
- Run Migration of Screen Modification
- Run Resolution of Multiple FI Assignments
- Confirm Final Customizing Steps
- Confirm Migration Success
SAP recommends that you ensure that all relevant records are migrated during this phase, but you are not be restricted from proceeding even if you have not migrated all records.
You can complete the migration process migrating only a few BPs, patients, and attached relationships. Hence, SAP strongly recommends that you migrate all the records corresponding to a step. In the case of an error, try to resolve it using the log messages and migrate the record again. If you don't resolve the errors and re-migrate, those records will not be migrated and you will not be able to maintain those with the BP transaction. Once this phase is completed you will not be able to migrate any non-migrated records.
This phase can be executed in two modes: General mode and Expert mode. General mode is the default mode of execution. You can switch at any time to Expert mode by using the toggle button in the application toolbar. These two modes of execution are interchangeable at any time during migration. Expert mode requires more input during execution and is recommended for expert users.
All the steps in this phase are obligatory. SAP strongly recommends that you execute all the steps in the given sequence, and that you read the documentation available in the information (i pushbutton) corresponding to each step, before executing that step.
- Confirm Setting of Migration to Phase 3
- This step brings the migration status to Phase 3. You must confirm this step before executing any step in Phase 3.
- Run Migration of HC BPs and Relationships (available only in General Mode)
- This step creates or updates SAP Business Partners (SAP BPs) in different roles corresponding to HC-specific BPs in different functions (which were newly created or changed during migration). This step also determines the relationships between BPs and creates or updates the corresponding relationships between the migrated SAP BPs.
- Run Migration of HC Business Partners (available only in Expert mode)
- This step creates SAP BPs in different roles corresponding to HC-specific business partners in different functions (which were newly created or changed during migration).
- Run Migration of Relationships corresponding to HC BPs (available only in Expert mode)
- For each HC-specific BP, this step determines the relationships (which were newly created or changed during migration) to other BPs. It then creates similar relationships between the corresponding SAP BP (already migrated). You must migrate the BP roles (previous step) before creating the relationships. The program is unable to create relationships, if the corresponding BP has not already been migrated.
- Run Migration of Patients and Dependent Objects
- This step migrates patient master data and relationships (which were newly created or changed during migration).
- Run Migration of Patients with Prov. Data
- This step migrates patients with provisional master data that were newly created and changed during migration.
- Run Migration of Screen Modification
- This step adapts the existing HC-specific screen modification for BP and patient screens to the new screens where SAP BP is used for the maintenance of BP and patient data.
- Run Resolution of Multiple FI Assignments
- This step determines and resolves the multiple FI assignments for the HC-specific BPs and Patient Insurance Relationships. Since only one SAP BP can be assigned to one FI customer (and the other way around) multiple FI assignments for HC-specific BPs and patients must be determined and resolved.
- Confirm Final Customizing Steps
- This step creates Master Data Synchronization (MDS) links for all valid FI assignments. Links are created between the FI customer and the corresponding SAP BP (created after migration). This step uses the information stored in the FI assignment table, which was filled during Resolution of Multiple FI Assignments.
- Confirm Migration Success
- This step concludes the migration process for the BPs as well as the hospital structure. Confirming this step deactivates the use of IS-H BPs and IS-H hospital structure, and activates access to the migrated hospital structure and BP data. When programs that access the hospital structure or business partners are run, the system ignores old data and uses the new data.
TXBHW - Original Tax Base Amount in Local Currency Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 7125 Date: 20240524 Time: 004703 sap01-206 ( 141 ms )
