Datamigration Reconciliation en Xx

SAP BusinessObjects Data Services 4.0

December 2011

English

Reconciliation Processing

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Functional Documentation

SAP Best Practices Reconciliation Processing: FD

© SAP AG Page 2 of 15


Copyright

© 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle and Java are registered trademarks of Oracle.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text>

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

Reconciliation Processing..............................................................................................................5

1 Purpose.................................................................................................................................. 5

2 Prerequisites.......................................................................................................................... 5

2.1 Preparation................................................................................................................... 5

3 Overview................................................................................................................................ 5

4 Extending the Reconciliation Job............................................................................................8

5 Troubleshooting...................................................................................................................... 8

6 Appendix................................................................................................................................ 9

6.1 Table Structure: MGMT_RECONCILIATION................................................................9

6.2 ERP Reconciliations...................................................................................................10

6.3 HCM Reconciliations.................................................................................................13



Reconciliation Processing

1 PurposeThis functional guide provides instructions on the use of the reconciliation Jobs and reports for all ERP and HCM objects within the SAP Best Practices for Data Migration. The Data Services reconciliation code is delivered as part of the content in the latest release and the example reconciliation reports are delivered as part of the Business Intelligence Archive (BIAR) file also delivered as part of the content.

The SAP BusinessObjects Data Services (DS) tool allows organizations to easily extract, transform, cleanse, map, and validate their legacy data for upload to the SAP system using IDocs.

The Data Services Designer provides a graphical user interface (GUI) development environment in which you define data application logic to extract, validate, transform, and load data from databases and applications into the required data migrations formats. You can also use the Designer to define logical paths for processing message-based queries and transactions from Web-based, front-office, and back-office applications.

The SAP BusinessObjects Enterprise tool allows organizations to easily report and analyze the data within their databases and other information sources. SAP BusinessObjects Web Intelligence provides the tool to build and display the example reports delivered as part of the Data Migration content.

2 Prerequisites

2.1 PreparationEnsure that you have completed all steps specified in the Data Migration Quick Guide to set up the Data Services, BusinessObjects Enterprise and SAP environments for migration.

3 OverviewAs part of the data migration process there will be a need to reconcile the data held in the staging area database tables to the data loaded into the SAP target tables. Due to this requirement we have pre-built reconciliation content in both the DS toolset and example reconciliation reports in the Web Intelligence reporting tool. The reconciliation Jobs in DS Job_DM_Reconcile contains the code required to extract the target data from the SAP environment and run the reconciliation against the data in the ENRICHED data tables in the staging area.

The basic concept here is to check that each and every row and column value we send to SAP makes it safely and correctly. We have the ability to check that the IDoc was received and processed successfully in the DS Job Job_DM_CheckIdocStatus and report on the returned information using the delivered Universe and reports using Web Intelligence. What we need to do next, is check that the data in the underlying SAP tables is there and correctly loaded. We are able to do this in DS, using the Job Job_DM_Reconcile and there should be no significant impact on the target SAP system.



The reconciliation Job should be run as soon as possible, after the load to SAP, as any user interaction on the SAP system affects results. For example, if a user updates a field in SAP (perhaps for a good reason) then this means, that the column no longer reconciles to the staging data and you may end up with a lot of reconciliation issues to resolve.

Once the reconciliation Job has been run in DS then reports can be created on top of the Reconciliation table MGMT_RECONCILIATION so that a point in time copy of the data can be kept for validation and audit purposes.

The prebuilt reconciliation Jobs for DS includes all SAP Best Practice fields identified in the Best Practices tab of the mapping templates and the first query Qry_BestPractices in the Mapping Data Flows for each object / segment. This guide includes the description and usage of the standard code. For information on the enhancement and extension of the code to cover additional fields or segments, refer to the Data Migration Extension Guide.

Job_DM_Reconcile is the DS job which performs the reconciliation. It should be run after a load of data into SAP has been performed for a specified object or objects.

If this Job is run before the configuration has been completed and the object level Jobs have been run in their initially delivered state, then it results in errors. The Job relies on the staging tables to exist in the staging area database before it is executed.

The Job Job_DM_Reconcile has three types of Global Variables;

1. $G_Default_Language – this defaults to ‘E’ for English but can be changed if another language is required, to choose which language is used when extracting from multi language text tables.

2. $G_Clear_Reconciliation – this defaults to ‘Y’ which will re-create the table MGMT_RECONCILIATION on execution of the Job. Note that this must be set to ‘N’ after the initial run of this job to leave the table. If left set to ‘Y’, then it effectively deletes any prior reconciliation results in the table by dropping and re-creating the table.

3. All of the other Global Variables are of the form $G_Reconcile_Xxxx, where Xxxx is a specific object, for example, Customer or Material. There is one of these variables per object in the SAP Best Practice scope. They are all set to ‘N’ by default. You need to set each variable to ‘Y’ for objects which you have loaded.

It should be noted that this Job is provided with all Workflows and Dataflows running in series (sequentially) rather than in parallel, this is to ensure the load on the SAP system is not too great. If speed of reconciliation is a priority then these could be run in parallel by modifying the Job structure.

The way DS treats an SAP null is important and we need to set an option from the DS Designer application before we execute the Job Job_DM_Reconcile process. From the main menu, select Tools and then Options and expand the SAP tree and select Environment, you need to make sure the “Convert SAP null to null” box is checked, otherwise the reconciliation process can return un-reliable results.

It is also important to deselect the “Convert SAP null to null” box, after you have run the Reconciliation jobs, and are satisfied with the results; as it can adversely affect the other jobs.



UseFollow the instructions in this section to execute the Reconciliation Job to reconcile your data loaded into SAP.

Procedure1. Access the Data Services Designer by choosing the following navigation options:

a. For Data Services 3.2

Database type Microsoft SQL Server

Database server name <the computer name>\SAPBPDM

Database nameDM_REPO_ERP (replace ERP with CRM / HCM depending on deployment target)

Windows authentication Select the checkbox

b. For Data Services 4.0

System - Host <BOE Server Name: BOE Server Port>

User name Administrator or BOE assigned user name

PasswordAdministrator password or assigned BOE password

Authentication Enterprise

2. Choose the Log on button and then select the repository

RepositoryDM_REPO_ERP(replace ERP with CRM / HCM depending on deployment target)

3. From the Local Object Library, open the DM_BPFDM_Reconciliation project.From the Project Area, right-click the Job Job_DM_Reconcile (Job_HCM_Reconcile for HCM reconciliation) and choose Execute. If the system displays a prompt to save all changes and execute, choose OK.

4. On the Execution Properties dialog box, choose the Global Variable tab and perform the following:

Set the $G_Default_Language global variable to the language you wish to use ‘E’ by default.

Set the $G_Clear_Reconciliation global variable to ‘Y’ or ‘N’ depending on whether you want to re-create the MGMT_RECONCILIATION table or not respectively.

Set the $G_Reconcile_Xxxx global variables that is, $G_Reconcile_Customer to ‘Y’ for the objects that you want to reconcile and choose OK.

These values are effective only for the current runtime. To set the default values for each execution, right-click the Job in the Project Area and select properties, the global variables are available on a tab in this window and can be set as above.

To find the statistics of a job, choose . To check the log, choose . Ensure that there are no errors and that the job is completed successfully before you move on to the next step.

Result



The reconciliation process would have run and populated the specified object data into the MGMT_RECONCILIATION staging table. The table is located in the staging database associated with the DS_STG_MGMT_LKP datastore. This table can then be reported on using the Universes ERP Management and Lookups or HCM Management and Lookups. The pre-delivered reconciliation reports are located in the _Management Tables folder in the standard content under the ERP and HCM folder structures. For a definition of the MGMT_RECONCILIATION table structure and field definitions, refer to the appendix of this document.

In some instances, SAP defaults field values based on data entered via the segment when it loads into SAP. In this scenario, the Reconciliation Report displays data in the Target column and not in the Source column. Although this is not considered Failed, it appears in the Failed section of the report since there was no mapping source data.

4 Extending the Reconciliation JobFor information on extending the Reconciliation Job code within DS, refer to the Data Migration Extension Guide included in this documentation package.

5 Troubleshooting Version Incompatibility

Data Services Designer only imports the project file (atl) if the file version is the same or lower than the Data Services version that you are running on your machine.



6 Appendix

6.1 Table Structure: MGMT_RECONCILIATION

Field Name Data Type Description

UID Int Unique row identifier generated by the DS code.

REPOSITROY_NAME Varchar(256) Name of the repository running the job

JOB_RUN Varchar(20) The specific Job_Run_Id generated by DS.

SOURCE_TABLE Varchar(100) Name of the source table (XXX_ENRICHED) that is being compared.

TARGET_TABLE Varchar(100) Name of the target table (SAP) that is being compared.

ROW_ID Varchar(256) The Row identifier (key) that identifies the record that is, for Customer Master Basic, this is the Customer Number.

SOURCE_COLUMN Varchar(100) Name of the source column in the XXX_ENRICHED staging table that is being compared.

TARGET_COLUMN Varchar(100) Name of the target column in the SAP table that is being compared.

SOURCE_VALUE Varchar(256) Value held in the source column in the staging table that is being compared.

TARGET_VALUE Varchar(256) Value held in the target SAP column that is being compared

PASS_RESULT Varchar(1) Y or N depending on whether the values match or not respectively



6.2 ERP Reconciliations

OBJECT_NAME JOB_NAME Reconciliation Exists?

Comments

Accounts Payable Job_DM_AccountsPayableReceivableBalances_IDOC

Yes Display records using transaction FB03

Activity Price Job_DM_ActivityPrice_IDOC No Display records using transaction KP06

Activity Type Job_DM_ActivityTypes_IDOC Yes Display records using transaction KL03

Bank Job_DM_Bank_IDoc Yes Display records using transaction FI03

Bill of Material Job_DM_BillOfMaterial_IDOC Yes Display BoM using CS03

Characteristic Job_DM_Characteristics_IDOC Yes

Display records using transaction CT04

VALID_FROM_DATE and DEFAULT_VALUE are both populated with SAP generated values regardless of what is posted via the IDoc

Class Job_DM_Class_IDOC Yes Display records using transaction CL02

Config Profile For Material

Job_DM_ConfigProfile4Material_IDOC

No Display records using transaction

Contracts Job_DM_Contracts_IDoc No Display records using transaction ME33K

Cost Element Job_DM_SecondaryCostElement_IDOC

Yes Display records using transaction KA06

Cost Centers Job_DM_CostCenter_IDoc Yes Display records using transaction KS03

Standard Hierarchy Job_DM_StandardHierarchy_IDOC

No Display records using transaction OKENN

Customer Job_DM_CustomerMaster_IDOC

Yes Display records using transaction XD03

Equipment Job_DM_Equipments_IDoc Yes

Display records using transaction IE03Legacy Equipment Number populated in Inventory Number field.

Exchange Rates Job_DM_ExchangeRates_IDoc Yes Display records using transaction TCURMNT.




Comments

The Factor_From, Factor_To fields do not always appear to reconcile as SAP sometimes enters in its own default values.

Fixed Asset Job_DM_FixedAsset_IDoc Yes Display records using transaction AS03.

Functional Location

Job_DM_FunctionalLocation_IDOC

Yes

Display records using transaction IL03.Display full Hierarchy Using IH01Legacy Functional Location populated in Inventory Number field.

Inspection Method Job_DM_InspectionMethod_IDOC

Yes

Display records using transaction QS33

The InspMethodLongTexts E1BPQMTB reconciliation is out of scope and so is not included in the reconciliation job.

Inspection Plan Job_DM_InspectionPlan_IDOC Yes Display records using transaction QP03

Internal Order Job_DM_InternalOrder_IDOC Yes

Display records using transaction KO03Legacy Internal Order number populated in External Order Number field.

Inventory BalanceJob_DM_InventoryBalances_IDOC No

Validate loaded data using Inventory Report transaction MB52

Master Inspection Chars

Job_DM_MasterInspectionChars_IDOC Yes

Display records using transaction QS23

Field ‘From_Date’ does not always reconcile as expected as SAPs defaults this value.

Material Job_DM_MaterialMaster_IDOC

Yes Display records using transaction MM03

Material Classification

Job_DM_MaterialClassification_IDOC

Yes Display records using transaction MM03




Comments

Material External Customer Repl

Job_DM_MaterialExtCustomerRepl_IDOC

Yes

Material QM Inspection Type

Job_DM_MaterialQMInspectionType_IDOC

Yes Display records using transaction QM08

Object Dependency

Job_DM_ObjectDependencies_IDOC

Yes

Open Deliveries Job_DM_OpenDeliveries_IDoc Yes Display records using transaction VL03N

Order Reservation Job_DM_OrderReservation_IDoc

No Display records using transaction MB23

Plan Ind Req Job_DM_PlannedIndependentRequirements_IDoc

No

Profit Centers Job_DM_ProfitCenters_IDoc Yes Display records using transaction KE53

Purchase Order Job_DM_PurchaseOrder_IDOC Yes Display records using transaction ME23N

Purchasing Info Record

Job_DM_PurchasingInfoRecords_IDOC

Yes Display records using transaction ME13

Purchasing Requisitions

Job_DM_PurchasingRequisitions_IDoc

No Display records using transaction ME53N

Reference Operation Set

Job_DM_ReferenceOperationSet_IDoc

No Display records using transaction CA13

Routings Job_DM_Routings_IDOC Yes

Legacy Routing number populated in Old Task List Number field. Display records using transaction CA03

Sales Order Job_DM_SalesOrder_IDOC Yes Display records using transaction VA03

Scheduling Agreements

Job_DM_SchedulingAgreements_IDoc

No Display records using transaction ME33L

SD Pricing Job_DM_SDPricing_IDOC Yes Display records using transaction VK13

Service Master Job_DM_ServiceMaster_IDoc Yes

Display records using AC02Legacy Service Master number populated in EAN/UPC field.

Source List Job_DM_SourceList_IDOC Yes Display records using transaction ME03

Cost Center Groups

Job_DM_CostCenterGroups_IDoc

No Display records using transaction KSH3

Vendor Job_DM_Vendor_IDOC Yes Display records using transaction XK03

Work Breakdown Structure

Job_DM_WorkBreakdownStructure_IDOC

Yes




Comments

Work Center Job_DM_WorkCentres No Display records using transaction IR03

6.3 HCM Reconciliations


Comments

Org Management

Job_DM_HCM_OrgManagement_IDOC

YesDisplay records using transactionPA20. Enter specific Infotype Number.

Initial Employee Conversion

Job_DM_HCM_Initial_Employee_Conversion_Idoc

Yes Display records using transactionPA20. Enter specific Infotype Number.

Benefits Job_DM_HCM_Benefits_IDOC


Current Employee Conversion

Job_DM_HCM_Current_Employee_Conversion_Idoc


PayrollJob_DM_HCM_Payroll_IDOC Yes

Display records using transactionPA20. Enter specific Infotype Number When reconciling data for infotype 0235, there may be scenarios where the reconciliation indicates an error in the results, but the data loaded is correct. Fields TYPXX, FRMXX and EXPXX occur multiple times within the table. When data is loaded into the PA0235 table, the system loads the data sequentially into these fields, starting with the first occurrence and sequentially thereafter. Based on the specific subtype, the data displays correctly for the employee within HCM, regardless of its position in the table.

Pers Admin Job_DM_HCM_PersAdmin_IDOC





Comments

US_EEO_WC Job_DM_HCM_US_EEO_WC_IDOC



Documents

Datamigration Reconciliation en Xx