How to Improve Data Quality

Here's some best practice to improve data quality in your Oracle EBS:

1. Master data especially item should be managed by a dedicated team. keep the team size small and each item category is managed by a single person only.
2. Use catalog and personalize purchase order form to prevent users from miss typing currency. While it seems simple, enter the wrong currency may ruin your item cost.
3. Value your data input operator. They are the role player here. If they did it wrong, it'll carry forward till GL, the company financial report may suffer as the result. Punishment and reward schema may apply. 
4. Keep an eye on Cost Manager and cost workers. If cost workers are idle for sometime then it may indicate there are some rows with error flag in material transactions table. 
5. Make sure the inventory data FLOWS.
6. Build your team to manage Oracle EBS and database. DBA must keep an eye on table space and log issue. The number of pending concurrent in concurrent manager is also something to monitor tightly, if it is high then a quick action must be taken.

so far that's all I can tell right now.

Big Bang or Phased

ERP implementation strategy offers you two options: big bang or phased.

Big bang is simple; all ERP modules go live at the same time. In real life, it requires all business functions to work together in the correct manner which may be totally different.

Phased means the company starts with a few modules -usually Order Management or business function related- and then followed by the other modules later. In phased, you may want to make sure the running modules are settle before you move forward.

Big bang just like a shortcut. It takes you there within less time, less cost but more riskier and with a lot of effort. For a challenge lover, big bang is hot and tempting. Phased on the other hand is safer but requires more man days, thus charge you more.

If budget and time are constrain maybe big bang is the answer, however the risk is also high. If the company never uses an ERP before then migrate to ERP not only mean changing the way data was input into the system but also change the mind set, procedure and work habit. Problems may rise from all directions This could be frustrating.

If you ask me which one is better then I say none. Before making any decision, I will take a look at the things below:

1.     Organization size (number of function that will run ERP, number of user)

2.     Business complexity (refer to Fit & Gap Analysis)

3.     Business impact (It is a common thing that in early stage, ERP does not run smooth at 100% If it is so then how does it affects the daily operation?)

4.     Organization culture

5.     Management back up and ERP team size

Oh by the way, if it is a manufacturing industry with garment/footwear characteristic, I personally recommended phased strategy. Been there, done that.

When People Say No

Often, in a large complex IT implementation, change management is a must to seal the project success story. It could mean more man power or changes on standard of procedure or an additional extra job. Unfortunately, since it hits people comfort zone, you may end up with resistance.

Solving issue that requires cross function contribution is an art of management. We cannot say "Hey, this is what big boss wants, so you ought to do it." If that's the way, you may get nothing but a lips service. A more elegant approach is to listen to them, see from their point of view and try to understand them. Of course sometimes their concerns are reasonable, sometimes they are not. Just don't get emotional when you think their request is not logic. They just do not understand yet that a system is not a magic wand.

Sometimes things go harder and require more intensive negotiation. Explain the obstacle in a way that they'll understand. If there's a dead end and a change management remains mandatory then it is time to escalate it. Obviously, you need back up this time.

Basically, people will follow you if they believe they get something in return, so what you need to do is simply help them see their benefit because they just have not see it yet.

How to Prepare Budget for ERP

I take this from my Linked In post:

How to Prepare Budget for ERP

Okay, so you want to start ERP. Now you need to submit your budget. Remember that this is a long term project -mostly takes about a year or more- so you don't want to running out of $$$ in the middle of work but you also have..

ERP Success Factor: People, People, People

I take this from my Linked In post:

ERP Success Factor: People, People, People

I've been working with Oracle EBS for the last few years. Walking through the implementation, I can say there are five keys success factor if you wish to run Enterprise Resource Planning (ERP). They are people, people, people...