Thursday Sep 03, 2015

Webcast: Data Quality Management (DQM) Search & Match Deep Dive

Data Quality Management (DQM) Search & Match Deep Dive

Date: September 16, 2015 at 11:00 am ET, 8:00 am PT, 4:00 pm GMT, 8:30 pm, India Time (Mumbai)

This one-hour session will build on the Understanding Trading Community Architecture (TCA) Customer Entities & User Interface webcast and is recommended for technical and functional users who want to have a better understanding of the Data Quality Management (DQM) feature in TCA and how it works when performing searches or preventing duplicate customer-related data. We will also cover troubleshooting common DQM issues.

Topics will include:

  • DQM Overview & Setup
  • Creating custom attributes & transformations
  • How Match Rules work
  • DQM Synchronization
  • Troubleshooting common issues

Details & Registration via the My Oracle Support Community thread:  Advisor Webcast on 16-Sep-15: Data Quality Management (DQM) Search & Match Deep Dive

Thursday Jan 02, 2014

Do you Deal with Supplier Profile Management flows?

Do you Deal with Supplier Profile Management flows?  Well if so, you will want to read this…..

There have been a lot of changes in Release 12 and higher with the integration of Trading Community Architecture (TCA), where supplier data is part of the parties architecture.

See these important references to get the full picture:

  • Doc ID 1591187.1-*Upgrade Issues* Supplier Data Model, Upgrade Scripts and Patches For Data Issues In The Upgrade To 12.X: this note provides a compilation of important references for this data model change (including manuals).
  • Doc ID 1607664.1- Diagrams of TCA - Trading Community Architecture - Data Models Showing Logical Design as Used in Supplier Management:  diagrams showing the data models in 11i and R12 for Supplier Management are shown here.  These diagrams are useful for comparing differences between the releases and understanding the logical data model.  The ERD - Entity Relationship Diagrams - are also provided to clarify the models further.
  • Doc ID 1596801.1- UPGRADE Supplier Data Model From 11i to R12 - List and Description of Scripts Used During Upgrade: obtain details of upgrade scripts used for upgrading supplier data from 11i to R12 to comply with the new data model for supplier data in R12.  This data is used by products from Oracle Applications like iSupplier, Purchasing, iProcurement, Sourcing, Payables, etc.
  • Doc ID 1591190.1- *Upgrade Issues* Supplier Data Issues After Upgrade to 12.X and Generic Data Fix Patches: this document lists the data issues after the upgrade and the generic data fix patches available.

Still have Questions? Access this Procurement community post and, using the reply link, put in your question/comment.

Friday Aug 09, 2013

AR: Why Can't I Inactivate Parties in Accounts Receivable?

Are you confused by Parties versus Customers in Receivables?  Are you wondering how to  inactivate a customer/party using AR forms and screens? 

Back in Release 11.5 the customer was maintained through the Customer Standard form, which was owned by Accounts Receivables.  As the data model became more complex,  the Trading Community Architecture (TCA) product and data model was created.   All applications within the E-Business suite that require interaction with a customer integrate with TCA.  Customer information is no longer stored in the individual applications but rather in a central repository/registry maintained within TCA.

For an insight into the terminology of TCA, check out the following blog entry 

Understanding the Customer Form in Release 12 from an AR Perspective!!

From a current AR perspective, when you create a new customer, you are actually creating a Customer Account.  However, because the data is now kept within TCA, the structure of data must adhere to the rules defined within TCA.  One of these rules is, You can define a Party without creating Customer Accounts for it, but a Customer Account always has to be tied to one and only one Party. In compliance with this rule, when you create a Customer Account in AR, the code automatically takes care of creating the Party associated to the Customer Account for you.

At the AR level, you will only transact at the Customer Account level and never the Party level.  This is why in the Customer form owned by AR, you will not have access to manipulate the status of the Party.  To change the status of a Party you would have to access the data via applications such as: Telesales or Customers Online.  You will still be able to inactivate the customer status in the Create Customer screen, but the related party will still be active until you also change this in these applications.

 In order to understand the specifics of these relationships, we would like to advise you of the following MOS documents which will provide you with specific information and troubleshooting tips 

Customer Form, Party Issue: How To Inactivate / Reactivate a Party? Doc ID 883461.1

Customer Form, Address/Sites: Troubleshooting, How To, Known Issues and Patches Doc ID 1437866.1

Oracle Receivables: Overview of the Customer Form in Release 12 Doc ID 1436547.1


Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected



« July 2016