Wednesday, September 13, 2006

Oracle Interconnect


Found some free time last Friday. So I decided to poke around Oracle Interconnect. Following are my thoughts about the Product:

---------------------------------------------------------------------------------

In all my previous exposures, where Data Conversion /Linking between heterogeneous systems was always a challenge.

So far, We have used the Traditional approach viz; The Producer (Legacy System or otherwise) of data will be placing the data in a predefined Directory (outbound) in the Server. Depending on the Complexity of the system, it can be picked and placed into the inbound directory of the Receiver's (say Oracle Applications UNIX box), Interface Tables. A Concurrent Program will validate Data Integrity and Apply Business Rules then inserts /Updates into the Actual Tables.

Any changes in the business rules, meant the Code has to be re-written. Data has to be transformed and then the Concurrent Program changes will be validated /tested.

However, Oracle Interconnect (OI) UI can be used to specify and design Transformation of data into Interface Tables. It parallelly invokes Interface Processes. Handle Error Data. Best part was this can be done in a GUI Environment, where you can define the Business Rules.

Hub-and-spoke model:

Similarly, the Common View eliminates need for Complex Code, as well as need for that each application or adapter knows about every connection.

I can relate this issue to a problem I faced earlier:

A VB Based Application was the "Consumer" - recipient of data - and Oracle Apps was the "Producer" - generating Data. Apps Updates an Interface table, with Certification Date. However, the date format for "Consumer" was different. Since the "Producer" was a key component, and changes in Apps could not be implemented in a timely fashion.

Error Correction

OI can process errors; better, It displays error associated with each adapter. OI can link up with Oracle workflow and send out Notifications.

Pre-Packaged Adapters

OI provides variety of Pre-packaged Adapters to interconnect with various solutions.

Conclusion:

OI goes beyond traditional methods and allows Functional users to design and develop a scalable Integration system.

Tuesday, September 12, 2006

Should You Express Emotions at Work?

Interesting article I've recently read in a EQ and Risk Management research group;
Srini

----------------------------------------


"As the emotional intelligence buzz continues to spread in the military, business and corporate worlds, people are asking: "So now are we supposed to express our emotions at work?" - Anon

The difficult truth is it doesn’t matter if we're "supposed to" or not. Every one of us does bring our emotions to the work place. We also express them in the workplace. The key is the awareness to managing them intelligently -- which is the whole point of emotional intelligence (or "EQ").

Emotional Intelligence begins with self-awareness. Knowing your own feelings and understanding where they come from and how they work is the first step to managing them. The goals are to make good decisions incorporating the information feelings provide.

We like to think it's a matter of choice -- expressing them or not -- but that's less often the case than you might think.

I was reminded of this a couple of months ago when I was speaking on a cruise. I broke my ankle on the second day out. They put a soft cast on it in the Mexican hospital, and I awaited my return to the US to get it taken care of.

Yes, it hurt, and I wasn't able to do much, but to me it wasn't intolerable. When I went for meals, I didn't want my tablemates' vacation to be "inconvenienced" or to "worry" them about such a thing while on their vacation, something "unpleasant." That's what we get away for, right? So there I sat, eating and making polite conversation, acting as if nothing were wrong (though of course the cast was evident) but every time I changed position even slightly, I winced.

The gentleman sitting across from me said, "Does your foot hurt?" "No," I replied, not wanting to cause concern.

The next time it happened, the same question, "Is your foot hurting?"

"No," I replied.

This time he challenged me, annoyed, with "Why do you tell me it doesn't hurt when it shows all over your face?"

The thing is that we DO show how we're feeling, whether we want to or not. It can be subtle, in which case some people will miss it, but others who are more perceptive will pick up on it.

When we see expressions on people's faces we can at least tell something's wrong, though we may not be able to read the emotion and figure it out exactly. In this case, it was rather obvious since they knew I'd broken my ankle.

I asked myself why I felt like concealing how I was feeling (though I didn't do it very well). There are reasons why we do. It could be we don't want to make other people uncomfortable, or don't want to appear "weak" or "overly emotional."

Perhaps it's the cultural norm you grew up with (as in my case … you don't talk about unpleasant things 'at table'), or the culture you're currently in. Perhaps we'd rather ignore it ourselves, with the "stiff upper lip" philosophy, or because we think there's nothing anyone else can do about it. Or in our family of origin, perhaps when we didn't express a negative feeling, nothing WAS done about it, so we no longer expect it, and keep it to ourselves.

But what happens when we don't? For one thing, we send mixed messages and, as with my table companion, this annoys other people. It erodes trust. To him, I was lying. I was saying I wasn't in pain (verbally) when I was (nonverbally, facial _expression). It was "little white lie" in my culture; a big lie in his. He was an outspoken guy, a rancher from rural Texas. He wanted it all out on the table.

When we don't express our emotions, but they're "leaking out" or when we plaster a "mask" on our faces, removing all _expression (or trying to), we're perceived as "being hidden." This erodes trust.

Most of the emotional content in communication takes place nonverbally, as it did in this exchange. I was (trying) to talk as if nothing were wrong, when my facial expressions (evidently) were showing pain. I wasn't that aware of this inconsistency -- which, often we are not. Had this been on occasion where I wanted, or needed, to hide how I was feeling, it would help me to be more aware of my expressions, yes?

This was a social occasion, and here was the result. When I finally came out (to his way of thinking) and "admitted" I was in pain (I thought they would know, of course!), I received lots of help. They moved a chair so I could put my foot up, they escorted me from the dining room, they were solicitous of my well-being. These are all nice things!

And here's the other side of the communication coin ... in the back of my mind, I was sure everyone "knew" I was in great pain. Have you ever broken a bone? It's excruciating! I assumed everyone knew that and that his question meant ... "Assuming you're in pain, is it tolerable? It is intolerable? Is there anything we can do? Can we help you?" (We leave out a lot of words in our communication, and we always carry a lot of assumptions into the conversations.)

When we express our emotions (appropriately) at work, the same things can happen. For instance, if you're confused by the instructions you've been given, it's best to express this. Then you can get the clarification you need.

If you're annoyed by the noise your colleague is making at their desk, if you express it appropriately, then it can be solved.

If you're frustrated someone's not making a deadline, or disappointed when a colleague's let you down, it's best to express it verbally and appropriately, rather than bottle it up inside, or fail to address the situation, or leave all those assumptions rattling around.

Equally importantly, if you're on a project team and you are skeptical about a procedure, or have a gut feeling a strategy isn't going to work, these feelings must be expressed for the success of the venture. Our emotions guide us. We ignore them to our peril.

When we deal with our emotions at the time, it keeps little things from becoming big issues. It keeps you out of the place of resentment. It allows you to get what you want and need, and for others to as well.

Work is about people, emotions and relationships. In order to make this work best, we need to acknowledge the feelings are there, and deal with them. That's what emotional intelligence is all about.

We've done a good job at treating the intellectual side of work. We hire people for their academic degrees, credentials, and experience. Then we train them in skills, providing graduated experience for them to learn from, and mentor them in technical areas or send them to classes.

What's been ignored is coaching in the "people" element, what's commonly called the "soft" skills. Emotional Intelligence coaching is about training in emotional management, communication, leadership, vision, resilience, flexibility and the other EQ competencies.

Businesses don't succeed, people do. Take care of the "people" side of the equation with EQ.

Sunday, September 10, 2006

contact me photo

LinkedIn Network

LinkedIn seems to be an excellent way to promote yourself. I am a recent member to this n/w and I am excited to find that I have already discovered a few ex-colleagues, I never even knew that they live right close by.
In my perception, the difference between expanding network and spamming is just a thin line. LinkedIn operates by feedback received. If any person declines you, that gets added to the negative pool; It seems that for those who sent a few messages, do not need to worry; However, for those who are sending out large number of messages, will put on notice;
LinkedIn provides a warning or a chance to correct your ways before shutting down your account (paid or otherwise).
In general this is pretty cool way to get in touch;

Saturday, September 9, 2006

My First Post

There is of course, a first for everything. In spite of the fact, that millions have already blogged, here I am, a novice, getting into Blogging world.

I was bombarded by a pleothera of ideas; Write about a unique experience I had in the more than 13 years of IT experience, I've had so far; Write about a product /enhancement on Oracle ERP - of course, I'd love to write about quite a few; Last but not least, write about bugs /problems/issues, I've faced in Oracle World and other places; Faced with competing ideas and with a time-constraint, I initially postponed the decision, then finally decided to let go; I understood that this is more like a First step a Child takes.
So here goes the first one;

Oh, speaking of steps, I'm reminded of the famous quote:
That’s one small step for a man, one giant leap for mankind. - Neil Armstrong, July 21, 1969