Yesterday somebody posted a question about Synchronizing IO on the Siebel Forum. I did answer him there but I was not sure how many of you follow the forum so thought I would share my learning about Synchronization of IO with a wider audience :)

It was my first EAI Assignment and we were working on Siebel 7.7 when I came across this functionality. I was working with a team mate and we had very little idea about IO and other EAI stuff.

My teammate took great pains to get the IO in the way we wanted. Our IO was based on Quote BO. We needed 3 Integration Components and within these 3 integration components we need about 50 fields.

It took him almost 6 hrs to modify the IO and to do things such as

  • Inactivating fields not required.
  • Change the XML tags to what we required.
  • Modifying and creating the User Keys
  • Changing names according to our convention

After he was done, he took a break and I took over. I added a field in Quote Item and then I needed to update the IO. I saw synchronize button and quickly checked the bookshelf to know that It is used to synchronize IO with the BC and without thinking further I clicked the button and synchronized the BC.

But after Synchronization was done, I was in for a shock :o . All the changes that my team mate had done were gone :( and IO was back to its original shape, user keys that we modified were made inactive and vanilla user keys were made active. There was just one addition in IO that was of the field that I had added in BC, but  that too was in inactive state as I had chosen this option while synchronization.

We had to do all the rework of bringing back the IO the way that was required.

Moral of the Post

Synchronize only and only if

You need to add integration components (IC) in IO and if only minor changes are required like addition of a field or changing some values like XML tags or external name just do it manually :)

OkAvarageGoodVery GoodExcellent (1 votes, average: 5 out of 5)
Loading ... Loading ...

Related Posts