Federal Judge Rules Oracle can Bid for PeopleSoft

terrymaster69 writes "The NY Times reports (free reg, required) that Oracle may have the go ahead to continue its hostile bidding for PeopleSoft. The Justice Department had previously tried to paint the merger as anti-competitive in the corporate services software market. 'Judge Vaughn R. Walker of the Federal District Court in San Francisco rejected the government's definition of the market as too narrow, noting that the software business is particularly dynamic, with a host of current and emerging competitors in that area including Microsoft.'"

Comments

Re:not out of the woods

[LostCluster]

"3 major players"... but there are a ton of industry-specific ERP-ish systems out there for every industry you can think of ranging from office supply sellers to construction project managers. Also, there's plenty of business out there who skip over the full marketplace and hire a programmer to make their own resource tracking program using tools as simple as Microsoft Access which works great for a truely small business even though its scalablity is limited.

I agree with the judge here... the ERP software field is filled with players small and large. There's no monopoly risk in letting Oracle and PeopleSoft merge... just like there's far more places that sell hambugers than McDonald's and Burger King. Just because their two of the biggest, doesn't make a merger that creates a monopoly possible.

Re:Point

[skaffen42]

Microsoft have considered buying SAP have they? Don't make us all laugh now. SAP is as big, if not bigger, than Microsoft.

Dude, what have you been smoking? SAP has a market cap of about $46 billion and anual revenue of about $9 billion a year. Microsoft has a market cap of nearly $300 billion and revenues of around $37 billion a year. So I'm not really sure how you can claim SAP is as big as MS.

For comparison, Oracle has a market cap of $51 billion vs. Peoplesoft's market cap of $7 billion. Looking at it that way, the ratio in sizes between MS/SAP compared to Oracle/Peoplesoft is about the same.

Draw your own conclusions...

Karma-whoring

[genixia]

Registration free story is available from the BBC.

Re:it's not architectures

[BitterAndDrunk]

It's a combination of a few factors: (this is from my work implementing SAP and Oracle)

1. They're not designed with an end user in mind - they're designed to make the accounting package interact with every other bolt-on module. What occurs is a programmer with no idea how to, say, plan a line is put in charge of developing all the forms and interfaces for that type of job.
2. Kruft/feature creep - Customer A wants a feature to shine the shoes of his CEO and accompanying sycophants. Oracle says "ok" and implements it on top of preexisting flows. The documentation may or may not be updated.
3. Generalization of businesses - the underlying assumption of ANY ERP is most of the business processes that will be tracked/automated/integrated are generic and standard to a business and will only require modest tweaking. This is the most blatant of lies the ERP vendors make (niche players excluded). Overgeneralization forces almost a reinvention of the wheel - either changing processes or changing the program. Guess which one happens most ;)

4. Finally, an ERP is just such a damn big undertaking. AR/AP, human resources, CRM (which Oracle's product is laughable. Too bad I make a living off of it), inventory, purchasing, manufacturing, planning, sales - all need to be integrated.

   While there are "standards" of how to implement all of these products, the teams tend to be distinct and insulated from one another, sometimes taking completely different approaches to how they implement the solutions, making a customization effort quite difficult.

   One of the biggest gooches is also the nasty little relationship of ERP vendors and their own consulting firms. They're trying to make money by implementing these products, so the documentation tends to be shoddy and it tends to be very difficult to get real answers on how to do something or how a specific thing works. Hell, Oracle's J2EE architecture is bogus, with most industry standard functions having changed names, making a standard J2EE developer near useless. Well, until you decompile the whole stinking stack to trace back what you need.

   And as an aside to the main topic, Oracle has a long history of acquiring firms and integrating their designs. This is nothing new, but it won't be an improvement on the peoplesoft product.