Ansicht
Dokumentation

BP Migration: Master Data and Relationships (New) ( RELNISH_700_BP_15_MIG06 )

PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Short text

BP Migration: Master Data and Relationships (New)

Use

As of SAP ECC Industry Extension Healthcare 7.0, there are separate new tables created to store the master data. All of the central data (common data) for all the business partners, patients, and patients with provisional master data is stored in the BUT000 table provided by SAP Business Partner (SAP BP). BUT000 has foreign-key relationships to the Address (BUT020), Roles (BUT100) and Relationships (BUT050) tables. Table NBUP hosts all data that is common to all IS-H business partners but not handled by SAP BP (in other words, by BUT000). New tables are created to store the role-specific data for business partners, patients, and patients with provisional master data.

The following table gives the relationships between the tables that existed prior to SAP ECC Industry Extension Healthcare 7.0 and the new tables:

• For business partners:

IS-H BP	SAP BP Re-Architecture	Description
NGPA	BUT000 and NBUP	General business partner data
NDEB	NCUS	Customer
NKRH	NHSP	Hospital
NABG	NEPR	Employer
NPER	NPRS	Person*
NKTR	NINS	Insurance provider

*Person refers to physicians, external physicians, and employees.

• For patients:

IS-H Data Source	SAP BP Data Target
NPAT	BUT000
NPNT

• For patients with provisional master data:

IS-H Data Source	SAP BP Data Target
NPAP	BUT000
NPPT

Data needs to be migrated from the IS-H data source to the SAP BP data target mentioned above.

The primary keys of master data tables NGPA and NPAT must be stored as references to the old records in the corresponding tables of SAP BP (NBUP and NPNT, respectively). This is necessary for the IS-H programs to distinguish between business partners in non-patient roles and business partners in HC Patient role. The reference also facilitates the update of migrated business partners where their corresponding IS-H object has changed in the meantime (delta migration before switching to SAP BP).

The primary key of table NPAP will not be stored in the SAP BP table NPPT as reference. Instead, the old primary key of NPAP and references to this key in other IS-H tables will be updated during migration with the primary key of the SAP BP in role HC Patient w. Prov. Data. The references of the dependent tables for the HC Patient w. Prov. Data (in other words, other tables that store references to the primary key of NPAP) will be updated with the SAP BP keys.

The following are also migrated: IS-H BPs with the deletion indicator set, IS-H patients with the cancellation indicator set and IS-H patients with provisional master data with the cancellation indicator set.

• For Address Data

SAP BP uses Business Address Service (BAS) for address validation and postal code correctness. BAS stores address details in its own table (ADRC). Thus, data is migrated from the NADR table (which was used to store address details prior to SAP ECC Industry Extension Healthcare 7.0) to the ADRC table. Except for the geographical area, all NADR fields can be mapped to table ADRC of BAS. The geographical area is stored in table NPNT for business partners in role HC Patient only.

• For Relationship Data

• For business partners:

Relationships amongst insurance providers are stored in the BUT050 table (contains central details for the relationship) and NIPR table (contains data specific to the Insurance Provider - Insurance Provider relationship). Data is migrated from TNREL to these tables. These include the following relationships:

Is Form Recipient of

Is HC SC Head Office of

Is Invoice Recipient of

Is Head Office for Data Exchange acc. to 301 SGB V (DE) of

An employer acting as the accident insurance provider (stored in NABG table) is stored as a relationship between an HC Insurance Provider and an HC Employer in SAP ECC Industry Extension Healthcare 7.0. Also, the responsible PPA stored in the insurance provider table (NKTR) is stored as a relationship between an HC Insurance Provider and a business partner in SAP ECC Industry Extension Healthcare 7.0. The relationship details of these two relationships are stored in the BUT050 table.

• For Patient:

Next of Kin

The details of the two next of kin of the patient were stored in the NPAT table prior to SAP ECC Industry Extension Healthcare 7.0. After migration, this data is maintained as relationships to the patient, and data is stored in the BUT050 and NNOK (table to store data specific to next of kin relationship) tables after migration.

Patient's Employer

If the patient's employer is maintained as free text in the NPAT table then these details are migrated into the corresponding fields of the NPNT table. If an employer is assigned to a patient then this is stored as a Patient-Employer relationship in SAP ECC Industry Extension Healthcare 7.0. After migration, data is stored in the BUT050 and NPEP (table to store data specific to Patient-Employer relationship) tables.

Patient's Physician

The referral and family physician assigned to a patient are stored as relationships to a patient in SAP ECC Industry Extension Healthcare 7.0. Data is stored in the BUT050 table.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

The data migration programs of Phase 2 can be accessed in Customizing for SAP Healthcare - Industry-Specific Components for Hospitals by choosing Tools -> Migration of Business Partner and Hospital Structure -> Migration of Business Partner -> Phase 2: Data Migration for BP During Uptime.

The data migration programs of Phase 3 can be accessed in Customizing for SAP Healthcare - Industry-Specific Components for Hospitals by choosing Tools -> Migration of Business Partner and Hospital Structure -> Migration of Business Partner -> Phase 3: Data Migration of BP During Downtime.

Further Information

TXBHW - Original Tax Base Amount in Local Currency   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 8522 Date: 20240602 Time: 135231     sap01-206 ( 147 ms )