ERF_GEN_HZ_MIG0001_WP0180

DS080 MIGRATION
DELIVERABLE DOCUMENT
COLLECTIONS
CCI_CUSTOMERS
NOTE: Do not change the following keywords table:

$Author::ramkumar$

$Date::2017-05-19 12:05:34 +0530 (Fri, 19 May 2017) $

$Revision:: 2077#$

Author: Purush
Creation Date: Sep 02, 2015
Last Updated: May 17, 2017
Document Ref: <>
Version: 1.0

Approvals:

<Approver 1>

<Approver 2>

Copyright 2013, Chain-Sys, All Rights Reserved

1 DOCUMENT CONTROL

1.1 Change Record

2

Date Author Version Change Reference

02-SEP-2015 Sandhiya 1.0 Initial version

17-APR-2017 Purush 1.1 Added the primary flag validation in update cust
pay method procedure in the packages
XXAL_AR_UPD_ACC_CIUSTOMER_PKG and
XXAL_BANK_PKG
27-APR-2017 Aathikumaran.A 1.2 Added the FND_LOBS Sequence for File Type
Attachment in the package
XXAL_ROUTING_ATTACHMENT_PKG
17-May-2017 Purush 1.3 Defect fixed for XXAL_IBY_FNDCPT_SETUP_PKG
# 30603

1.2 Reviewers

Name Department
Nicola Sahlieh Manager R12 Data Conversion
Hariharan/Saravanan/Ram Managers R12 Data Migration

Page 2 of 16
1.3 Abbreviations
Abbreviation Description
API Application Program Interface
PPG Professional Printing Group
CIG Customer Imaging Group
DFF Descriptive Flex Fields
11i Refers To Oracle Application Version 11.5.8
R12 Refers To Oracle Application Version 12.2.2
DM Data Migration

Page 3 of 16
 1.3 Contents
1 DOCUMENT CONTROL.................................................................................................................................................... II
1.1 CHANGE RECORD.................................................................................................................................................................. II
1.2 REVIEWERS.......................................................................................................................................................................... II
1.3 ABBREVIATIONS.................................................................................................................................................................... II
1.4 CONTENTS.......................................................................................................................................................................... III
2. INTRODUCTION................................................................................................................................................................... 4
2.1 GOAL................................................................................................................................................................................. 4
2.2 SCOPE................................................................................................................................................................................ 4
2.2.1 CIG..................................................................................................................................................................................4
2.2.2 Data Migration...............................................................................................................................................................4
2.2.2.1 Key Assumptions.................................................................................................................................................................... 4
2.2.2.2 Migration Approach............................................................................................................................................................... 4
2.3 PURPOSE............................................................................................................................................................................ 5
3. MIGRATION INFORMATION................................................................................................................................................. 6
3.1 MIGRATION DESCRIPTION.......................................................................................................................................................6
3.2 MIGRATION TYPE................................................................................................................................................................. 8
3.3 EXTRACT INFORMATION......................................................................................................................................................... 9
3.4 TEMPLATE AND LOADER INFORMATION.....................................................................................................................................9
3.4.1 Template Information.....................................................................................................................................................9
3.4.2 Loader Information......................................................................................................................................................10
3.5 PROJECT INFORMATION.............................................................................................................................................................11
3.6 SCHEDULE INFORMATION..........................................................................................................................................................11
4 OPEN AND CLOSED ISSUES............................................................................................................................................ 12
4.1 OPEN ISSUES..................................................................................................................................................................... 12
4.2 CLOSED ISSUES...................................................................................................................................................................12

Page 4 of 16
2. INTRODUCTION
This document is intended for the technical team who will execute the data migration process as part of migration
from e-Business Suite R11.5.8 (Source) to R12.2.2 (Target). It elaborates the data migration of the Customer
Creation from the source to the target.

Page 5 of 16
 2.1 Goal
The purpose of this document is to provide the following:
Necessary and sufficient information about appMIGRATE Migration process.
This document needs to be signed off by the business users and the DM functional team.

2.2 Scope
This data migration project is part of the CIG-PPG project stream.
The scope of the project in general is the implementation of Finance and Supply Chain functions in R12.

2.2.1 CIG

Business Imaging Group (CIG) is Canon Business Unit for business market. The Financials and Supply Chain
functions of CIG are currently available in Oracle EBS R11i system (CIG-R11). These functions will be supported
in the Oracle EBS R12 system.
Therefore, data from CIG-R11 should be migrated to R12. HP OEM & Expenses data will be excluded because it
will be migrated in the other earlier project.

2.2.2 Data Migration

The Data Migration in scope is part of CIG-PPG project stream which will migrate data from CIG & PPG into R12
environment.

2.2.2.1 Key Assumptions

For the migration of PPG data, data migration tools will extract data directly from PPG systems. The output
data sheet in Excel files in the predefined migration template format. These files will be the input for the data
migration to R12.

2.2.2.2 Migration Approach

Any organization specific data, the migration will be done by country/group of countries. The Data will be filtered
on the Operating Units or Inventory Organizations of the particular countries to be migrated.

Pilot Migration will be done for Organizations Related with Countries/Operating Units, The Netherlands, United
Kingdom and Belgium.

Page 6 of 16
 2.3 Purpose
The purpose of this document is to explain the following:
Migration Description.
Extract Information.
Template and Loader Information.
Project Information.
Scheduler Information.

Page 7 of 16
3. MIGRATION INFORMATION

Page 8 of 16
 3.1 Migration Description
The Customer Creation Migration uses the below mentioned Standard APIs for the migration of
Customer Creation data from the Source into the target system.
API NAME AND PROCEDURE
HZ_PARTY_V2PUB.CREATE_PERSON
HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUST_PROF
ILE_AMT
IBY_EXT_BANKACCT_PUB.ADD_JOINT_ACCOUNT_OW
NER
IBY_FNDCPT_SETUP_PUB.SET_PAYER_ATTRIBUTES
HZ_CONTACT_POINT_V2PUB.CREATE_WEB_CONTACT
_POINT
ZX_PARTY_TAX_PROFILE_PKG.UPDATE_ROW
ZX_REGISTRATIONS_PKG.INSERT_ROW
IBY_FNDCPT_SETUP_PUB.SET_PAYER_ATTRIBUTES
HZ_CODE_ASSIGNMENTS_PKG.INSERT_ROW
HZ_ORIG_SYSTEM_REF_PUB.CREATE_ORIG_SYSTEM_
REFERENCE
HZ_LOCATION_V2PUB.CREATE_LOCATION
HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACC
T_SITE
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE
_USE
IBY_EXT_BANKACCT_PUB.CREATE_EXT_BANK_ACCT
HZ_PARTY_CONTACT_V2PUB.CREATE_ORG_CONTACT
HZ_CUST_ACCOUNT_ROLE_V2PUB.CREATE_CUST_AC
COUNT_ROLE
HZ_CONTACT_POINT_V2PUB.CREATE_CONTACT_POIN
T details.
HZ_CONTACT_POINT_V2PUB.CREATE_EMAIL_CONTAC
T_POINT
HZ_CUST_ACCOUNT_ROLE_V2PUB.CREATE_ROLE_RES
PONSIBILITY
PURPOSE
This Package is used to create
Customer details.
This API is used to create Customer
Account details.
This API is used to create Customer
Profile Amount.
This API is used to create Account
Details.
This API is used to create Payer
Attributes.
This API is used to create Contact
details.
This API is used to update tax details.
This API is used to create tax details.
This API is used to create payer
details.
This API is used to create assign Fiscal
Code details.
This API is Used to Create Orig System
Reference Detail
This Package is used to create
Customer Location details.
This Package is used to create
Customer Site details.
This Package is used to create
Customer Account Site
This Package is used to create
Customer Site details.
This Package is used to create
Customer Bank Account Details.
This Package is used to create
Customer Org Contacts.
This Package is used to create
Customer Account Role.
This API is used to create Contact
This API is used to create Email
Contact details.
This API is used to create Customer
Role.
Page 9 of 16
 HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCT_REL This API is used to create Customer
ATE Account Relationship.
This API is used to create Customer
HZ_RELATIONSHIP_V2PUB.CREATE_RELATIONSHIP
Relationship.
This API is used to create the
FND_ATTACHED_DOCUMENTS_PKG
customer attachments.

Extract the Customer Creation data from the source system.

Populate the extracted Customer Creation data into the appLOAD staging tables in the target
system.
Validate the data in the staging tables using validation queries against the target system.
Update the validation failed records as pre-validation error records and success records can be
processed again.
Pass the pre-validation success records into the Standard API.
Once the Standard API execution has completed, generate log files for success, error, and pre-
validation errors in the Process Summary.
Validate the successfully processed records in Oracle base tables as well as EBS Application
Form in the target system.
Verify the extracted record count against the loaded record count in the target system.

Page 10 of 16
 3.2 Migration Type
The Customer creation migration uses for scheduler method and contains the following steps:
Extract the Customer creation data from the source system by applying filter conditions.

Extracted data populated in staging table.

After Prevalidation, success data will be used as input for the appMIGRATE loader.
The following screenshot shows the Input Source file processing method:

Page 11 of 16
 3.3 Extract Information
Given below is the extract used for extracting data from 11i Instance. Any manual transformation,
If required, will be done by the users.

Extract Name Description

AR_COLLECTON_CCI_CUSTOMER_MASTER_EX
TRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_ACCOUNT_
EXTRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_ADDRESS_E
XTRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_BILL_TO_EX
TRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_SHIP_TO_EX
TRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_RELATIONS
HIP_EXTRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_CONTACT_E
XTRACT_SQL
AR_COLLECTION_CCI_CUSTOMER_TAX_DETAIL
_SQL
AR_COLLECTION_CCI_CUSTOMER_ATTACHME
NT_SQL
Extract Query for Customer Party
Extract Query for Customer
Account
Extract Query for Customer
Address
Extract Query for Customer
Business
Purpose(Bill To)
Extract Query for Customer
Business Purpose(Ship To)
Extract Query for Customer
Relationship.
Extract Query for Customer
Contact.
Extract Query for Customer Tax.
Extract Query for Customer
Attachment.

3.4 Template and Loader

Information
3.4.1 Template Information
The following attached file contains the Template information.

AR_COL_CUSTOME AR_COL_CUSTOME AR_COL_CUST_BUSI AR_COL_CUST_BUSI

R_CREATION_R12.2.2.PDF
R_ADDRSS_CREATION_R12.2.2.PDF
NESS_PURPOSE_BILL_TO_CREATION_R12.2.2.PDF
NESS_PURPOSE_SHIP_TO_CREATION_R12.2.2.PDF

AR_CUSTOMER_REL AR_CUSTOMER_CO AR_CUSTOMER_TAX AR_CUSTOMER_ATT

ATIONSHIPS_R12.2.2.pdf
NTACT_CRE_R12.2.2.pdf
_DETAILS_R12.2.2.pdf ACHMENT_R12.2.2.pdf

Page 12 of 16
3.4.2 Loader Information
Loader Name Description
CCI_CUST_MAS Collection Customer Creation
CCI_ADDRESS Collection Customer Address
CCI_BILL_TO Collection Customer Business Purpose(Bill To)
CCI_SHIP_TO Collection Customer Business Purpose(Ship To)
CCI_RELP Collection Customer Relationship
CCI_CONTACT Collection Customer Contact
CCI_CUST_TAX Collection Customer Tax.
CCI_CUST_ATT Collection Customer Attachment.

1.The following screenshot contains the loader information:

2.There is defect changes in the below attached packages against the defect 32502 as part of CBS France
Data Migration in the Month for April2017.

XXAL_AR_UPD_ACC_ XXAL_AR_UPD_ACC_ XXAL_BANK_PKGS.pl XXAL_BANK_PKGB.pl

CUSTOMER_PKGB.pls CUSTOMER_PKGS.pls s s

Page 13 of 16
 3.To fix the bug reported under defect 32502 is When the multiple receipt method is created in the account
level while the primary flag is updated as Y for all the receipt method. But as per the functionality is to be only
one receipt method primary flag is Y rest of them are N

4. There is Defect Changes in the below attached package against the defect 33230 as part of AR Collection Data
Migration in the month for April2017.

XXAL_ROUTING_ATT XXAL_ROUTING_ATT
ACHMENT_PKGB.pls ACHMENT_PKGS.pls

5. To Fix the Bug report under defect 33230 is Records were inserted in fnd_lobs without using its sequence
resulted seq value lags behind the max value of file id in fnd_lobs and throwing an error of unique
constriant violated.so Add FND_LOBS Sequence for File Id in File Type Attachment in this package.
6. To fix the reported issues 30603 is In customer business purpose level there is an bank account with two
different iban numbers and its created as two seperate records.but in the debit authorization (mandates) is assigned for both
two bank accounts.

XXAL_IBY_FNDCPT_S XXAL_IBY_FNDCPT_S
ETUP_PKGB.pls ETUP_PKGS.pls

Page 14 of 16
3.5 Project Information
Project Name Description
AR_CCI_CUSTOMER_CREATION_SQ
Project for Collection Customer
L_PROJECT

3.6 Schedule Information

Scheduler Name Description

AR_CCI_CUSTOMER_CREATION_SQL_ Scheduler for Collection
SCHEDULER Customer

Page 15 of 16
4 OPEN AND CLOSED ISSUES

4.1 Open Issues

ID Issue References Resolution Responsibility Target Date Impact Date

4.2 Closed Issues

ID Issue References Resolution Responsibility Target Date Impact Date

Page 16 of 16