My Oracle Support Banner

Record Update Not Propageted To Server DB (Doc ID 2215833.1)

Last updated on DECEMBER 20, 2016

Applies to:

Siebel CRM - Version 15.3 [IP2015] and later
Information in this document applies to any platform.


On the remote client, the customer has some scripts and business service that does the following:

1 - A business service create a new contact and business address by default on the organization of the logged in user.
2 - BS script then update contact (s_contact/s_org_ext) and address (s_con_addr) Organization Id to make it match the other Organization. The goal of this script is to create an identical contact from an organization to an other.

The transactions are created in the proper order in the local S_DOCK_TXN_LOG table, with the insert to S_CON_ADDR followed by an update to S_CON_ADDR. However, when the remote user synchronizes to send the transactions to the server, the .dx file bundles the transactions incorrectly by putting the update to S_CON_ADDR before the insert to S_CON_ADDR. As a result, the server data is incorrect and the remote client never gets the update.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.