Scribd
Upload
14 views

2.1 Objective: Data Object Short Description

Uploaded by

Raghunathan Balasubramanian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views

2.1 Objective: Data Object Short Description

Uploaded by

Raghunathan Balasubramanian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

1.

Introduction
2.1 Objective
The data design document provides the detailed overview of the data migration requirements,
transformation, loading and validation approach for objects mentioned in section 1.2

2.2 Data Objects in-scope

The data objects covered in this document are provided below.

Data Object Short Description

2.3 Data Workshop

List the data workshops where these data objects were analysed for data migration.

Data Workshop Title Date and Time of Workshop

2. Pre-Requisites for Data Migration

This section provides the list of pre-requisites that need to be captured in order to perform data
migration for the objects mentioned in this document overview.

The pre-requisites broadly include transports, configurations or manual tasks that should be
performed by functional consultants / technical consultants. These tasks can be preparation tasks
before the overall data migration activity start or a specific task in between the data migration steps
of data objects. These details are captured in this section under the following two categories.

System pre-requisites – these are tasks, transports, manual activities that should be performed
before performing data migration for a given data object.
Pre-Requisite Data Objects – These pertain to data objects on which the given data object is
dependent upon. For example, customer open items (AR Open Item) cannot be posted before all
relevant master data objects including BP Customer, GL Account, etc., are loaded successfully.

3.1 System Pre-Requisite Tasks

List of configuration activities or manual activities that need to be performed during data
load/migration. If these are covered as part of transports, point these out.

Data Object Pre-Requisite Tasks


If listed in task list, mention the sections applicable.

3.2 Pre-Requisite Data Objects


List the data objects that must be loaded prior to migrating the objects in-scope of this document.

Data Object Pre-Requisite Data Object

3. Data Preparation

The data preparation section provides details on the key activities that must be performed for the
data objects pertaining to this document. These activities are normally referred to as data cleansing
or data preparation activities. The details of these activities for the data objects pertaining to this
document are elaborated in this section. All specific activities identified in this section will be
captured and tracked in the data cleansing backlog for McBride Data Migration.

The data preparation activities fall under the following categories.

Data Correction – Correct the existing data in the source prior to data migration. For example,
update the postal code for all business partners to the country specific format of the address.

Closing historically open transactions – Based on the agreed selective data transfer (SDT) criteria
and the volume of open transactions to be migrated based on a time-slice, the historically open
transactions must be closed in the source system.
Creation of missing data – In cases where the data in the relevant source system is missing, this
needs to be confirmed with the BPO for creation in production source system. This is a critical
activity to ensure that data migration does not fail due to missing reference / master data.

For Example – House Banks in CP CORE cannot be created since all the relevant bank keys from the
bank master data object are not available in the source MDG system.

RACI matrix to be mentioned.

4.1 Data for Correction in source


Provide specific details of the data that should be corrected for each data object that is considered in
this data design document.

Data Object Correction to be performed


Add reference to the cleansing backlog

4.2 Historically Open Transactions to close


Provide the details of the number of historically open transactions that must be closed in source
system for the data objects under consideration in this document.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy