Understanding tca merge processes; impact webacst 10 may-17

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. |
Option 1: Voice Streaming Audio Broadcast
• No need to dial in on a telephone
• Questions can be asked via WebEx Chat box
• If you are listening via voice streaming and it
stops, go to Communicate -> Audio Broadcast to
restart the streaming audio
Option 2: Teleconference (Dial In)
• Requires telephone to dial in
• Questions can be asked over the phone or in the
WebEx Chat
• Details
– Conference ID: 88071872
– International dial in: +1 (706) 634-8961
– US Free call: +1 (877) 664-9143
– List with national toll free numbers is available
in Doc ID 1148600.1
– View anytime during the conference using
Communicate > Teleconference > Join
Teleconference from your WebEx menu
2
ATTENTION – AUDIO Options
Understanding TCA Merge Processes & Impact

Upcoming Advisor Webcast Schedule
 Check out Document ID 740966.1
 Select your area of interest
 Scan through the list of Current
Topics
 Register for the session of your
interest
 For upcoming Oracle E-Business
Suite Advisor Webcasts & archived
recordings, see Document ID
1455369.1
3Understanding TCA Merge Processes & Impact

Oracle Advisor Webcast
Understanding Trading Community
Architecture (TCA) Merge Processes &
Impact
Tapas Kumar Ghosh
Principal Software Engineer
May 10, 2017

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.

Oracle Advisor Webcast
Understanding Trading Community
Architecture (TCA) Merge Processes &
Impact
Tapas Kumar Ghosh
Principal Software Engineer
May 10, 2017

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 7Understanding TCA Merge Processes & Impact
Objectives
• Know about TCA Merge processes
• Understand functional impact
• Learn changes in TCA Data Model
• Become familiar with Merge APIs

Program Agenda
Party Merge
Customer / Account Merge
Functional Impact of Merge Processes
TCA Registry Impact
Data Quality Management (DQM) Merge APIs
Known Scenarios
1
2
3
4
5
8
6

Program Agenda
Party Merge
TCA Registry Impact
Data Quality Management Merge APIs
Known Scenarios
1
2
3
4
5
9
6

What is Party Merge?
• Merge parties and their related entities
– Party Sites
– Party Relationships
– Contact Information
– Party Profiles
• Consolidate duplicate parties or party sites
• Merge duplicate party sites of a party

When is Party Merge Used?
• Primarily used for finding and resolving duplicates
• Mergers and acquisitions
– Post Party Merge Considerations
• All existing transactions associate to surviving (merge-to) party
• Cannot reconcile / audit transaction details for acquired (merge-from) party
• Cannot reprint invoices for acquired (merge-from) party

How to Use Party Merge?
• Define and submit Duplicate Identification Batch
• Review duplicates and create Merge Batch
• Submit Merge Batch to Party Merge
• Run Party Merge concurrent program
• Review the Party Merge log
– Request ID
– Log Message
– Execution Status

Accessing Party Merge

Merge Batch Form - Before Party Merge
Understanding TCA Merge Processes & Impact 14
• Delete Merged Records
– Merge-from party status set to
• Deleted when enabled
• Merged when not enabled
• Transfer Operation
– Merge-from & -to party sites not
duplicates
– Merge-from party site transfers to
merge-to party
– Uses copy & merge process (legal
auditing requirements)
– Copy of merge-from party site
created for merge-to party
– Merge-from party site merged with
that copy & set to merged

Merge Batch Form - After Party Merge

Running Party Merge

Party Merge (ARHPMERGE) Log

Party Merge Execution Report

Program Agenda
Party Merge
TCA Registry Impact
Known Scenarios
1
2
3
4
5
19
6

What is Customer / Account Merge?
• Consolidate duplicate customers
• Transfer site use activity from inactive customer / site
– Invoices & Debit Memos
– Credit Memos & Receipts
– Adjustments & Chargebacks
– Commitments

When is Customer / Account Merge Used?
• Merge scenarios
– Site uses of same customer
– All site uses of two different customers
– Individuals or organizations
Post Customer Merge Considerations
– All activities associated with old (merge-from) customer / site
now associates to new (merge-to) customer / site
– Old (merge-from) customers & site uses deleted or set to inactive
– Inactive customers cannot generate new transactions
– Can view inactive customers and reactivate them any time

Recommendations Prior to Customer / Account Merge
Review reports to identify duplicate / inactive customers / sites
– Duplicate Customer Report
• List of all duplicate customers
– Customer Listing Detail Report
• List of contacts, addresses and relationships of each customer
– Customer Listing Summary Report
• List of customers and their addresses

How to Use Customer / Account Merge?
• Create map that shows site uses to merge and maintain
• Submit the merge process
– Individual Merge: Use Customer Merge window
– Batch Merge: Run Customer Merge concurrent program
• Review the Customer Merge Execution Report
– Request ID
– Status
– Name & Number
– Address & Location

Accessing Customer / Account Merge

Customer Merge Form
• Delete After Merge check box
– Checked: System deletes
merge-from customer from
HZ tables
– Unchecked: System sets
merge-from customer status
to inactive
• Process Priority - assign when
creating Merge Batch
– P1-High
– P2-Medium
– P3-Low

Running Customer / Account Merge

Customer Merge (RAXMRG) Log

Customer Merge Execution Report

Program Agenda
Party Merge
TCA Registry Impact
Known Scenarios
1
2
3
4
5
29
6

Party Merge Legend
PARTY
PARTY SITE
Party Site Use
MERGED
TRANSFERRED
 Active Party
 Active Party Site
 Active Party Site Use
 Merged Party / Site / Site Use
 Transferred Party / Site / Site Use

Party Merge Example - Before Merge
Merge-to PartyMerge-from Party
HYDERABAD - 81 BANGALORE - 76
PARTY A
Bill-To
Ship-To
Marketing
Bill-To
Ship-To
DELHI - 45 BANGALORE - 76
PARTY B
Bill-To Ship-To

Party Merge Example - After Merge
Merge-to PartyMerge-from Party
PARTY A
Bill-To
Ship-To
Marketing
Bill-To
Ship-To
DELHI - 45 BANGALORE - 76
PARTY B
Bill-To
HYDERABAD - 81
Bill-To
Ship-To
Marketing
Bill-To
Ship-To

Party Merge Points to Remember
• May only merge parties of same party type
– Organization  Organization
– Person  Person
• Set HZ: Enable DQM Merge Suggestion profile option to No
– Disables DQM suggestion
– Reduces time lag
– Improves performance during create Merge Batch process

Customer Merge Legend
CUSTOMER
ACCOUNT SITE
Account Site Use
Site Use Activity
INACTIVE
 Active Customer / Account
 Active Account Site
 Active Account Site Use
 Activities like invoice, receipt, etc.
 Inactive Customer / Site / Site Use

Customer Merge Example - Single Customer
Before Merge
Bill-To
CUSTOMER
Ship-To Bill-To Ship-To
Receipt # 1Invoice # 1
After Merge
Bill-To
CUSTOMER
Receipt # 1 Invoice # 1

Customer Merge Example - Multiple Customers
Bill-To
CUSTOMER A
DELHI - 11 MUMBAI - 47
Bill-To
CUSTOMER B
Before Merge

Customer Merge Example - Multiple Customers
Bill-To
CUSTOMER B
Bill-To
CUSTOMER A
DELHI - 11 MUMBAI - 47
After Merge

Customer / Account Merge Points to Remember
• May only merge sites having same site use type
– Bill-To Site  Bill-To Site
– Ship-To Site  Ship-To Site
• Tax Validation for Merge
– Merge addresses must be within same Tax Jurisdiction
– Tax Validation check box in Geography Hierarchy
• Checked: Address elements with tax validation usage must match
• Unchecked: Can merge addresses as long as country is same

Customer / Account Merge Related Profile Options
• AR: Customer Merge Commit Size
– Determines size of the merge sets
• HZ: Location Updatable
– Location unique for each combination of customer account + site use type
• Yes: Update location field
• No: Unique sequential value automatically assigns as merge-to customer location
• HZ: Audit Customer Account Merge
– Creates audit log for products other than TCA
• HZ: Log Customer Merge
– Log information about Customer Merge program in log file

Program Agenda
Party Merge
TCA Registry Impact
Known Scenarios
1
2
3
4
5
40
6

CUSTOMER_TABLE
CUSTOMER_COLUMN
Before merge /
Row deleted
After merge /
Row inserted
Data unchanged
Customer Information
PARTY_TABLE
PARTY_COLUMN
Before merge /
Row deleted
After merge /
Row inserted
Data unchanged
TCA Registry Impact Legend
Party Information

TCA Registry
Party Merge Impact

After Merge
STATUS
M
Before Merge
STATUS
A
HZ_ORGANIZATION_PROFILES
ORGANIZATION_
PROFILE_ID
PARTY_
ID
ORGANIZATION_
NAME
EFFECTIVE_
START_DATE
217540 505207 Tapas PM Party A 25-Apr-2017
After Merge
EFFECTIVE_
END_DATE
STATUS
25-Apr-2017 M
Before Merge
EFFECTIVE_
END_DATE
STATUS
Party Merge - Merge-from Party (Party Data)
HZ_PARTIES
PARTY_ID PARTY_NUMBER PARTY_NAME PARTY_TYPE
505207 62371 Tapas PM Party A ORGANIZATION

After Merge
PARTY_SITE_
NUMBER
STATUS
Tapas PM
Customer Site A-M
M
After Merge
STATUS
M
M
Before Merge
STATUS
A
A
HZ_PARTY_SITES
PARTY_SITE_ID PARTY_ID LOCATION_ID
280889 505207 28042
Before Merge
PARTY_SITE_
NUMBER
STATUS
Tapas PM
Customer Site A
A
Party Merge - Merge-from Party (Party Data)
HZ_PARTY_SITE_USES
PARTY_SITE_
USE_ID
PARTY_
SITE_ ID
SITE_USE_TYPE PRIMARY_PER_TYPE
294266 280889 BILL_TO Y
294267 280889 SHIP_TO Y

After Merge
0 rows retrieved
After Merge
0 rows retrieved
HZ_CUSTOMER_PROFILES
CUST_ACCOUNT_
PROFILE_ID
CUST_ACCOUNT_ID STATUS PARTY_ID
176929 151876 A 505207
Party Merge - Merge-from Party (Customer Data)
HZ_CUST_ACCOUNTS
CUST_ACCOUNT_ID PARTY_ID ACCOUNT_NUMBER STATUS
151876 505207 Tapas PM Customer A A

After Merge
0 rows retrieved
After Merge
0 rows retrieved
HZ_CUST_SITE_USES_ALL
SITE_USE_ID
CUST_ACCT_
SITE_ID
SITE_USE_
CODE
PRIMARY_
FLAG
STATUS LOCATION ORG_ID
43835 38842 BILL_TO Y A 123 204
43838 38842 SHIP_TO Y A 456 204
Party Merge - Merge-from Party (Customer Data)
HZ_CUST_ACCT_SITES_ALL
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
PARTY_
SITE_ID
STATUS ORG_ID
BILL_TO_
FLAG
SHIP_TO_
FLAG
38842 151876 280889 A 204 P P

After Merge
No Change
After Merge
No Change
ORGANIZATION_
PROFILE_ID
PARTY_
ID
ORGANIZATION_
NAME
EFFECTIVE_
START_DATE
EFFECTIVE_
END_DATE
STATUS
217541 505208 Tapas PM Party B 25-Apr-2017
Party Merge - Merge-to Party (Party Data)
HZ_PARTIES
PARTY_ID PARTY_NUMBER PARTY_NAME PARTY_TYPE STATUS
505208 62372 Tapas PM Party B ORGANIZATION A

After Merge
-
No Change
New rows
inserted
HZ_PARTY_SITE_USES
PARTY_SITE_
USE_ID
PARTY_SITE_ID
SITE_USE_
TYPE
PRIMARY_PER_TYPE STATUS
294268 280891 BILL_TO Y A
294274 280899 BILL_TO N A
294275 280899 SHIP_TO Y A
After Merge
-
No Change
New row
inserted
HZ_PARTY_SITES
PARTY_
SITE_ID
PARTY_ID
LOCATION_
ID
PARTY_SITE_ NUMBER STATUS
CREATED_BY_
MODULE
280891 505208 28044 Tapas PM Customer Site B A HZ_CPUI
280899 505208 28042 Tapas PM Customer Site A A
HZ_TCA_
CUSTOMER_MERGE
Party Merge - Merge-to Party (Party Data)

After Merge
-
No Change
New row inserted
After Merge
-
No Change
New row inserted
CUST_ACCOUNT_
PROFILE_ID
176930 151878 A 505208
176929 151876 A 505208
Party Merge - Merge-to Party (Customer Data)
HZ_CUST_ACCOUNTS
151878 505208 Tapas PM Customer B A
151876 505208 Tapas PM Customer A A

After Merge
-
No Change
New rows inserted
After Merge
-
No Change
New row inserted
SITE_USE_ID
CUST_ACCT_
SITE_ID
SITE_USE_
CODE
PRIMARY_
FLAG
43841 38843 BILL_TO Y A 456 204
43835 38842 BILL_TO Y A 123 204
43838 38842 SHIP_TO Y A 456 204
Party Merge - Merge-to Party (Customer Data)
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
PARTY_
SITE_ID
STATUS ORG_ID
BILL_TO_
FLAG
SHIP_TO_
FLAG
38843 151878 280891 A 204 P
38842 151876 280899 A 204 P P

Before Merge
PARTY_ID
505207
505208
After Merge
PARTY_ID
505208
No Change
Before Merge
PARTY_ID
505207
505208
After Merge
PARTY_ID
505208
No Change
CUST_ACCOUNT_
PROFILE_ID
CUST_ACCOUNT_ID STATUS
176929 151876 A
176930 151878 A
Party Merge - Customer Accounts Data Comparison
HZ_CUST_ACCOUNTS
CUST_ACCOUNT_ID ACCOUNT_NUMBER STATUS
151876 Tapas PM Customer A A
151878 Tapas PM Customer B A

Before Merge
PARTY_SITE_ID
280889
280891
After Merge
No Change
After Merge
PARTY_SITE_ID
280899
No Change
SITE_USE_ID
CUST_ACCT_
SITE_ID
SITE_USE_
CODE
PRIMARY_
FLAG
43835 38842 BILL_TO Y A 123 204
43838 38842 SHIP_TO Y A 456 204
43841 38843 BILL_TO Y A 456 204
Party Merge - Customer Accounts Data Comparison
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
STATUS ORG_ID
BILL_TO_
FLAG
SHIP_TO_
FLAG
38842 151876 A 204 P P
38843 151878 A 204 P

TCA Registry
Customer / Account Merge Impact

After Merge
No Change
After Merge
No Change
ORGANIZATION_
PROFILE_ID
PARTY_
ID
ORGANIZATION_
NAME
EFFECTIVE_
START_DATE
EFFECTIVE_
END_DATE
STATUS
217547 505214 Tapas CM Party A1 25-Apr-2017
Customer Merge - Merge-from Customer (Party Data)
HZ_PARTIES
505214 62373 Tapas CM Party A1 ORGANIZATION A

After Merge
No Change
HZ_PARTY_SITE_USES
PARTY_SITE_
USE_ID
PARTY_
SITE_ID
SITE_USE_
TYPE
294279 280906 BILL_TO Y A
294280 280906 SHIP_TO Y A
After Merge
No Change
HZ_PARTY_SITES
PARTY_
SITE_ID
PARTY_
ID
LOCATION_
ID
280906 505214 28055 Tapas CM Customer Site A1 A
Customer Merge - Merge-from Customer (Party Data)

After Merge
Row deleted
Customer Merge - Merge-from Customer (Customer Data)
HZ_CUST_ACCOUNTS
151889 505214 Tapas CM Customer A1 A
Delete After Merge = Yes
Delete After Merge = No
Before Merge
STATUS
A
After Merge
STATUS
I
HZ_CUST_ACCOUNTS
CUST_ACCOUNT_ID PARTY_ID ACCOUNT_NUMBER
151893 505216 Tapas CM Customer A2

After Merge
Row deleted
CUST_ACCOUNT_
PROFILE_ID
176935 151889 A 505214
Before Merge
STATUS
A
After Merge
STATUS
I
CUST_ACCOUNT_
PROFILE_ID
CUST_ACCOUNT_ID PARTY_ID
176937 151893 505216

After Merge
Row deleted
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
PARTY_SITE_ID STATUS ORG_ID
BILL_TO_
FLAG
SHIP_TO_
FLAG
38849 151889 280906 A 204 P P
Before Merge
STATUS
A
After Merge
STATUS
I
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
PARTY_
SITE_ID
ORG_ID
BILL_TO_
FLAG
SHIP_TO_
FLAG
38851 151893 280910 204 P

After Merge
Rows deleted
SITE_USE_ID
CUST_ACCT_
SITE_ID
SITE_USE_
CODE
PRIMARY_
FLAG
43852 38849 BILL_TO Y A 123 204
43853 38849 SHIP_TO Y A 456 204
SITE_
USE_ID
CUST_ACCT_
SITE_ID
SITE_USE_
CODE
PRIMARY_
FLAG
LOCATION ORG_ID
43858 38851 BILL_TO Y 123 204
Before Merge
STATUS
A
After Merge
STATUS
I

After Merge
No Change
After Merge
No Change
ORGANIZATION_
PROFILE_ID
PARTY_
ID
ORGANIZATION_
NAME
EFFECTIVE_
START_DATE
EFFECTIVE_
END_DATE
STATUS
217548 505215 Tapas CM Party B1 25-Apr-2017
Customer Merge - Merge-to Customer (Party Data)
HZ_PARTIES
505215 62374 Tapas CM Party B1 ORGANIZATION A

After Merge
-
No Change
New row inserted
HZ_PARTY_SITE_USES
PARTY_SITE_
USE_ID
PARTY_
SITE_ID
SITE_USE_
TYPE
294281 280908 BILL_TO Y A
294285 280914 SHIP_TO Y A
After Merge
-
No Change
New row
inserted
HZ_PARTY_SITES
PARTY_
SITE_ID
PARTY_
ID
LOCATION_
ID
CREATED_BY_
MODULE
280908 505215 28057 Tapas CM Customer Site B1 A HZ_CPUI
280914 505215 28055 49416 A
HZ_TCA_
CUSTOMER_MERGE
Customer Merge - Merge-to Customer (Party Data)

After Merge
No Change
Customer Merge - Merge-to Customer (Customer Data)
HZ_CUST_ACCOUNTS
151891 505215 Tapas CM Customer B1 A
After Merge
No Change
HZ_CUST_ACCOUNTS

After Merge
No Change
CUST_ACCOUNT_
PROFILE_ID
176936 151891 A 505215
After Merge
No Change
CUST_ACCOUNT_
PROFILE_ID
176938 151895 A 505217

After Merge
-
No Change
New row
inserted
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
CREATED_
BY_MODULE
38850 151891 280908 A 204 HZ_CPUI
38853 151891 280914 A 204
HZ_TCA_
CUSTOMER_MERGE
After Merge
-
No Change
New row
inserted
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
CREATED_
BY_MODULE
38852 151895 280912 A 204 HZ_CPUI
38854 151895 280915 A 204
HZ_TCA_
CUSTOMER_MERGE

After Merge
-
No Change
New row
inserted
SITE_USE_ID
CUST_ACCT_
SITE_ID
CREATED_
BY_MODULE
43856 38850 A 456 204 HZ_CPUI
43862 38853 A 456 204
HZ_TCA_
CUSTOMER_MERGE
After Merge
-
No Change
New row
inserted
SITE_USE_ID
CUST_ACCT_
SITE_ID
CREATED_
BY_MODULE
43860 38852 A 123 204 HZ_CPUI
43863 38854 A 123-C 204
HZ_TCA_
CUSTOMER_MERGE

After Merge
-
Row deleted
No Change
Customer Merge - Customer Accounts Data Comparison
HZ_CUST_ACCOUNTS
151889 505214 Tapas CM Customer A1 A
Before Merge
STATUS
A
A
After Merge
STATUS
I
A
HZ_CUST_ACCOUNTS
CUST_ACCOUNT_ID PARTY_ID ACCOUNT_NUMBER
151893 505216 Tapas CM Customer A2
151895 505217 Tapas CM Customer B2

After Merge
-
Row deleted
No Change
CUST_ACCOUNT_
PROFILE_ID
176935 151889 A 505214
176936 151891 A 505215
Before Merge
STATUS
A
A
After Merge
STATUS
I
A
CUST_ACCOUNT_
PROFILE_ID
CUST_ACCOUNT_ID PARTY_ID
176937 151893 505216
176938 151895 505217

After Merge
-
Row deleted
No Change
New row
inserted
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
CREATED_
BY_MODULE
38849 151889 280906 A 204 HZ_CPUI
38850 151891 280908 A 204 HZ_CPUI
38853 151891 280914 A 204
HZ_TCA_
CUSTOMER_MERGE

After Merge
-
Status changed
No Change
New row
inserted
CUST_ACCT_
SITE_ID
CUST_
ACCOUNT_ID
CREATED_
BY_MODULE
38851 151893 280910 I 204 HZ_CPUI
38852 151895 280912 A 204 HZ_CPUI
38854 151895 280915 A 204
HZ_TCA_
CUSTOMER_MERGE

After Merge
-
Rows deleted
No Change
New row
inserted
SITE_USE_ID
CUST_ACCT_
SITE_ID
CREATED_
BY_MODULE
43852 38849 A 123 204 HZ_CPUI
43853 38849 A 456 204 HZ_CPUI
43856 38850 A 456 204 HZ_CPUI
43862 38853 A 456 204
HZ_TCA_
CUSTOMER_MERGE

After Merge
-
Status changed
No Change
New row
inserted
SITE_USE_ID
CUST_ACCT_
SITE_ID
CREATED_
BY_MODULE
43858 38851 I 123 204 HZ_CPUI
43860 38852 A 123 204 HZ_CPUI
43863 38854 A 123-C 204
HZ_TCA_
CUSTOMER_MERGE

Program Agenda
Party Merge
TCA Registry Impact
Known Scenarios
1
2
3
4
5
72
6

Create Merge Request API
Package: HZ_DUP_MERGE_PUB
Procedure: create_dup_merge_request
– Creates merge request in Oracle Data Librarian
– Merge request contains parties that are potential candidates for merge
– Release 12: API is already included
– Release 11i: API available via Patch 5046954

Customer Account Merge Request API
Package: HZ_ACCOUNT_MERGE_PUB
Procedure: create_account_merge_request
– Creates an account merge request in Oracle Data Librarian
– Merge request contains customers that are potential candidates for merge
– New API introduced in Release 12.2
– Not available in earlier releases

Program Agenda
Party Merge
TCA Registry Impact
Known Scenarios
1
2
3
4
5
75
6

Types of Party Merge Errors
• Data Errors
– Party Merge fails at batch / party level for corrupt data
– Entire batch fails
– None of the parties are merged
• Procedure Errors
– Party Merge fails if procedures not correctly coded / registered / tested
– Merge log identifies the procedure that causes failure

Party Merge Known Scenarios
• Party Merge fails with Error: Aborting Batch
– Create missing objects using correct xxxx.odf file (Doc ID 1454150.1)
• After Party Merge, unable to search by Account Number
– DQM Serial Sync Index Program is not being called
– Apply Patch 9209726 (Doc ID 986874.1)
• Party Merge fails with Error: Merge failed in procedure
ZX_PARTY_MERGE_PKG.ZX_MERGE for entity ZX_PARTY_TAX_PROFILE
– Apply Patch 9184831 (Doc ID 1144255.1)

Customer Merge Known Scenarios
• Customer Merge fails with MSG-00001:
ARP_CMERGE_ARCUS.create_same_sites : ORA-01422: exact fetch
returns more than requested
– Invalid / incorrect data in HZ_CUST_SITE_USES_ALL table
• Customer Merge fails with OE_CUST_MERGE.Merge- : ORA-01426:
numeric overflow
– Invalid data in OE_ORDER_LINES_ALL table

Summary
What we covered today
 Learnt about Party Merge
 Conceptualized Customer Merge
 Understood functional impact
 Deep-dive into TCA Registry
 Familiarized with Merge APIs
 Discussed known scenarios

Top Articles & Community Links
 Data Quality Management (DQM) Batch
Duplicate Identification Setup and Usage (Doc
ID 1664298.1)
 Complete End-to-End steps for Party Merge
Using HZ_DUP_MERGE_PUB.CREATE_DUP_
MERGE_REQUEST API (Doc ID 2153439.1)
 How To Create A Customer Account Merge
Request Using Customer Account Merge API?
(Doc ID 2021591.1)
 Trading Community Architecture (TCA), Party
Merge: Troubleshooting, Known issues and
Patches (Doc ID 1454150.1)

Top Articles & Community Links
 Customer Merge / Party Merge: Listing of
ORA Errors An index of ORA errors within
the Customer Merge / Party Merge
(Doc ID 1457656.1)
 Party Merge Issue: Unable To Search By
Account Number After Party Merge Is
Performed (Doc ID 986874.1)
 ZX_PARTY_MERGE_PKG.ZX_MERGE for
entity ZX_PARTY_TAX_PROFILE (Doc ID
1144255.1)

Session Related Community Links
 Questions? For follow up questions on
topics covered in this webcast connect
via this Receivables Community
thread:
https://community.oracle.com/thread/4043592
 This thread will link to a copy of the
presentation, the webcast recording
and will include the Q&A from the
webcast

Oracle Advisor Webcast Series
 Review the current schedule &
archived recording for your
product from Doc 740966.1
 Select your Product Area, for us
 E-Business Suite (EBS)
 Financials
83
Locating Current Schedule & Archived Recordings

Oracle Advisor Webcast Program
Locating Current Schedule & Archived Recordings
Access the E-Business Suite
area directly via Doc ID
1455369.1
Drill down to area of interest
Links typically updated
within 48 hours
 Use Questions? Link to ask
webcast related questions

Three Ways To Access Webcast Presentation PDFs
1. PDF link from Doc ID
740966.1 (within 48
hours)
2. Receivables
Community > Content
Tab > Documents
(within 24 hours)
3. Select Webcast
Category to see only
Webcast related
content

Stay Connected
Oracle E-Business Suite Support Social Media Channels
86
My Oracle Support E-Business Suite Community:
https://community.oracle.com/community/support/oracle_e-business_suite
My Oracle Support Blogs:
http://blogs.oracle.com/EBS
Twitter:
@Oracle_EBS
Facebook
http://www.facebook.com/OracleEBusinessSuiteSupport

Learn More - Resources and References to Get Proactive
Get Proactive Portfolio for your products
Check out the Get Proactive Portfolio for your products. Get familiar with the top
proactive tools. Doc 432.1
Ask the Get Proactive Team get-proactive_ww@oracle.com
Get Proactive Events Calendar
Automatically updated to include latest Advisor Webcasts, MOS Essentials
trainings, user group sessions, and more
Stay Informed about Upcoming Events. Doc 125716.1

Learn More - Resources and References on Support Portals
Help Documentation
at your fingertips
My Oracle Support and
Cloud Support Portal
documentation. Find it
from the Help link in the
top right corner of most
pages in both portals.
Oracle Support
Essentials Webcasts
Live instruction, Q&A on
how to best use the
Support Portals. The How
To Series covers content
similar to Help in a step-
by-step approach. Doc
553747.1
My Oracle Support
‘How To’ Series
Detailed training videos,
documentation. Latest
how-to content,
webcasts, self-paced
replay. Select a feature or
role to get started. Doc
603505.1
Oracle Support
Accreditation
learning
Leverage the Oracle
Support Accreditation
portfolio of portal and
product accreditations.
Get accredited today.
Doc 1583898.1

Q & A
89
• To ask a question on the phone
line, select *1 on your phone.
• To ask a question online, use the
Q&A area at the top.
• Your question will be read aloud in
the order received.
• Question can also be asked on the
My Oracle Support Communities

Understanding tca merge processes; impact webacst 10 may-17

Understanding tca merge processes; impact webacst 10 may-17

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Understanding tca merge processes; impact webacst 10 may-17

Similar to Understanding tca merge processes; impact webacst 10 may-17 (20)

Recently uploaded

Recently uploaded (20)

Understanding tca merge processes; impact webacst 10 may-17