When working with Oracle E-Business Suite R12, especially in Receivables (AR) or Trading Community Architecture (TCA), you might encounter a situation where you create a new customer, but it doesn't show up in the Customer Search screen. Several things could be causing this. Here's a checklist to help you troubleshoot:
✅ 1. Customer Status
-
Ensure the customer account is active.
✅ 2. Customer Site and Site Use
-
Ensure at least one customer site exists for the customer.
-
Also ensure site use is defined – e.g., "Bill To", "Ship To".
-
Without proper site and site use, the customer might not appear in downstream flows or searches.
✅ 3. Party vs Account Confusion
Oracle uses Trading Community Architecture (TCA), where a party (in HZ_PARTIES) may exist without a customer account (in HZ_CUST_ACCOUNTS).
-
Verify that the customer has a customer account created (not just a party).
-
Check
HZ_CUST_ACCOUNTStable for the party ID.
✅ 4. Search Criteria Too Narrow
-
Try searching with wildcards (%).
-
Make sure you're using the correct Operating Unit or Responsibility.
-
Sometimes responsibility data access security can filter out results.
✅ 5. Responsibility Data Access Security (MOAC)
-
If you're using MOAC (Multi-Org Access Control):
-
Ensure your responsibility has access to the Operating Unit where the customer was created.
✅ 6. Customer Created via API or Interface Table
-
If created via API (e.g.,
HZ_CUST_ACCOUNT_V2PUB.create_customer_account) or interface: -
Ensure the commit happened.
-
Check for errors or rollback during interface/API execution.
✅ 7. Query Backend to Confirm Creation
You can run below query to verify if the customer exists:
SELECT hca.account_number, hp.party_name, hca.status
FROM hz_cust_accounts hca,
hz_parties hp
WHERE hca.party_id = hp.party_id
AND UPPER(hp.party_name) LIKE UPPER('%CUSTOMER_NAME%');
✅ 8. Run the DQM Synchronization Program
Oracle EBS R12 uses a feature called Data Quality Management (DQM) for customer search and matching. To make newly created or updated customer records searchable through the DQM engine, Oracle requires that customer data be synchronized with the DQM tables.
If the DQM Synchronization Program has not been run after customer creation, the new customer will not be available in the Customer Search screen, even though it exists in the backend tables like HZ_PARTIES or HZ_CUST_ACCOUNTS.
The DQM Synchronization Program syncs customer and party data from TCA into the DQM indexed tables that support flexible and fast customer search. It’s a necessary step especially after bulk customer creation or integration processes.
Comments
Post a Comment