Sometimes when you use open interface (Customer Interface) or HZ APIs to create or amend Customers, it is not visible from front end, though you can see the changes from back end.
DQM Synchronization program (DQM Serial Sync Index Program (DQM Serial Sync Index Program)) is submitted automatically when a user updates any customer information.
This program is for Synchronizing the party records from the HZ tables into the DQM indexed tables which is what you query against when you search in the application.
DQM indexed tables are:
HZ_PARTIES = HZ_STAGED_PARTIES
HZ_PARTY_SITES = HZ_STAGED_PARTY_SITES
HZ_CONTACTS = HZ_STAGED_CONTACTS
HZ_CONTACT_POINTS = HZ_STAGED_CONTACT_POINTS
In R12, the DQM Synchronization can be set to: Automatic/Batch/Disabled
> Navigation: Customers Online Data Librarian Super User/Trading Community Manager > Administration Tab > DQM tab > DQM Synchronization Method
> Further more, when one sync concurrent request is in pending status, no other sync concurrent request would even be submitted. If a party is created while a sync concurrent program is already running, the DQM Serial Sync Index Program was not run for the newly created party.
To overcome this, you can set the profile option at site level:
HZ: Ignore Concurrent Request Limits for DQM Synchronization
If it is set to yes,it will run the DQM Serial Sync Index Program irrespective of the other sync concurrent programs.
Ref: Metalink Note [ID 465993.1]
Even after above changes, if it does not run automatically,
1> Clear the Global Cache
>> Navigation: Functional Administrator > Core Services > Caching Framework
> Global Configuration > Clear All Cache > Ignore warning message.
2> Please run the "DQM Synchronization Program" manually from "Trading Community Manager" responsibility.
No comments:
Post a Comment