This phase consists of a final test of the migration to ensure the stability of the system and a proper go live.
Phase 0 consists of steps that are recommended but not mandatory for the implementation of the migration project. You can confirm the various steps. Your confirmation is saved as an application log in the system. You can then access this log either using transaction SLG1 or by choosing the log icon next to relevant step in the phase. SAP recommends the following steps:
Understand the Hospital Structure Migration. For more information, see:
the Release Notes for SAP ECC Industry Extension Healthcare 7.0
the system documentation
the document for the IMG activities of the different phases
the information on the varios steps of the corresponding phase (i icon) Adapt Custom Code
This step is relevant only if you have customer modifications in the master data environment, or if Business Add-Ins (BAdIs) are used in the master data environment.
The following BAdIs are relevant in Organizational Management (OM):
– HRBAS00INFTY
– HRBAS00_RELAT
– ISH_OM_CUST_DATA_MIGRATE
– ISH_OM_MED_NORG_FILL
For more, information, see the respective BAdI documentation Run Test Migration:
SAP recommends that you test the migration of production data in a test system. If you execute this step, you can estimate the downtime of the production system from the runtime of the different steps and get an overview of the data consistency from the logs. Train Users on New SAP OM Transaction
Once the migration is complete and the changeover to SAP OM is made, Organizational and Building Units are maintained with the OM transaction. SAP recommends that you are trained on this transaction, and that you experiment with the various functionalities.
As Part of the phase 0 of the hospital structure migration it is necessary to adapt customer code. The hierarchy framework provides a set of BAdIs whose
implementations allow you to control the system behavior. The relevant BAdIs in OM are HRBAS00INFTY and HRBAS00_RELAT.
Depending on how your system is configured, the following adjustments may be necessary:
You have to adjust customer-specific modifications to the maintenance of building units and organizational units using the OM BAdIs specified above.
Customer enhancements to the tables NORG, NBAU, and TN11P can be migrated and managed as follows:
The migration of hospital structure data from IS-H offers you the possibility in the
enhancement spot ES_ISH_OM_MIGR with the BAdI IS_OM_CUST_DATA_MIGRATE to migrate customer enhancements of the tables NORG or NBAU or of other master data tables to customer-specific infotypes. For more iformation about this, see the
documentation for the BAdI
Customer-specific data can be filled using the BAdIs ISH_OM_CUST_NBAU_FILL, ISH_OM_CUST_NORG_FILL , and ISH_OM_CUST_TN11P_FILL.
The system dynamically performs foreign-key checks on the data elements ORGID and BAUID. You must implement these checks in customer modifications as well.
SAP provides function modules to read out master data from OM. More information you can find in release notes, also for tables containing migrated data.
The following configurations are not affected by the changeover:
It is not necessary to adjust modifications to the source code of the movement data.
It is not necessary to make adjustments in print control.
Access to the new tables is automatic when you use the new read function modules. The changeover has not caused the keys for the fields NORG and NBAU to change.
In Phase 1: Migration Preparation for OM, the system offers the following steps:
Confirm Adaptation of OM Customizing: This step is relevant only if you wish to change Customizing for Organizational Management (OM) in the
customer's system. Here you can, for example perform the following steps: Assign additional SAP standard infotypes in the Healthcare scenario ISH_OM (For more
information about this, see Infotype Maintenance and Maintain Object Types.
Assign customer-specific infotypes in the Healthcare scenario
Create customer-specific scenarios
Create customer-specific relationships
Create customer-specific search nodes
Confirm Status of OM Data: With this step, you tell the system whether you are already using Organizational Management (OM) to represent IS-H organizational structures.
Maintain Mapping Table: With this step you run the transaction ON_MIG_PHASE_MAP to maintain:
Which institution in IS-H corresponds to which institution in OM
Which OU in IS-H corresponds to which OU in OM
Run Migration of Screen Modification (Test): With this step you run program RN_OM_MIGRATE_DYNP_ATTR in test mode. This program allows you to migrate screen modification entries. When you run this program, the system adjusts entries that exist for master data aintenance screens in transaction ON04 for the tab page screens in the hierarchy framework.
Run Migration for Screen Modification (Prod.): With this step you run program RN_OM_MIGRATE_DYNP_ATTR in productive mode (data will be saved)
One main step of phase 1 is the Maintenance of the Mapping Table of the existing organizational units (OUs) in SAP Patient Management with those of objects in OM. This caters to the scenario where you are already using OM.
You are offered a Customizing view for the purpose of mapping. This view is only accessible if OM
already in use is selected in the step Confirm Status of OM Data.
This view different functionalities:
Propose Values pushbutton which generates a proposal for every SAP Patient Management
OU and institution based on matching the short text of the OU or institution and the abbreviation of an object.
Double-clicking on an SAP Patient Management OU in the view displays the respective details.
Check Consistency pushbutton: System checks the consistency of the generated proposals.
Specific consistency messages are shown for reference, but these messages are not logged in the database. The following checks will be executed:
You must confirm all rows.
Each object ID in OM is allowed to be assigned once only.
Only existing object IDs are allowed to be assigned.
The validity of the IS-H objects and of the OM objects must be the same. If the validity start and the validity end of the IS-H object lies outside of the validity of the OM object, the system issues an error message. If the validity start and the validity end of the OM object lies outside of the validity of the IS-H object, the system issues a warning. In the first case, you must bring the validity of the OM objects and that of the IS-H objects in line with one another.
Release Data pushbutton: the specific consistency messages are shown and logged for future
reference. Data can only be released successfully when no error message is displayed in the log. Releasing data is one of the prerequisites for downtime. If you need to reset the data release because it was started by mistake, use the RN_OM_RESET_STATUS program. You can use this program to reset the status of the maintenance table as long as downtime has not been started.
The Customizing view allows you to confirm the mapping so that the mapping information is taken into account in the data migration reports of institution data and SAP Patient
Management OUs. During release, the system checks if all data is confirmed. Data can only
be released if every SAP Patient Management OU is either confirmed to be linked to, or unlinked to, an OM organizational unit.
The logon language is used for matching the SAP Patient Management short text to the OM object abbreviation. If more than one short text is matched to an object abbreviation, only the first match is displayed as a proposal. However, the view has a dialog box indicating that more than one match exists, offering you the possibility to search for other objects and then make a final proposal.
The system offers the following steps :
Confirm Downtime: This obligatory step marks the downtime of the system to start the migration of the operative data.
Run Consistency Check (Test and Productive Mode): The system checks whether OM already contains organizational units with the same IS-H ID. It also checks whether the corresponding institution exist.
Migration of Institution Data (Test and Productive Mode):
This step runs the program RN_OM_MIGRATE_INSTITUTION. For each institution that exists in IS-H, the program creates an organizational unit (OU) with the object type "O" in OM.
SAP recommends to run the program in tst mode first (also possible before down time)
During data transfer, while creating the infotype 1000 (basic infotype of the object), the system models an institution in the logon language as an organizational unit with the corresponding abbreviation and name as attributes.
Run Migration of IS-H Data (Test and Productive mode):
This step migrates organizational units and building units to Organizational Management (OM) by means of the RN_OM_OU_BU_MIGR program.
For each organizational unit and building unit, the program creates a corresponding object in OM. In the process, it assigns rganizational units (OUs) to the object type "O" and building units (BUs) to the object type "N0".
SAP recommends to run the program in tst mode first (also possible before down time). Run Release Program (Test and Productive Mode):
This step runs the release program for the OM structure.
SAP recommends to run the program in test mode first
Datasets for those organizational and building units that are consistent in hierarchy and attributes are marked to set the release indicators.
Confirm Migration Success: This step activates the Customizing switch that confirms the use of OM for SAP Patient Management hospital structure management.