Skip to Content

SAP as a legacy system – Experience of a life time

Recently  our company was acquired by another. Ans soon we  were on the project to dismantle SAP system and replace it with buyers ERP system which was Oracle OPM ERP system.  

Thus SAP became a Legacy system. It was such a strange feeling to hear SAP being called a legacy system.  It was time to test firsthand SAP’s much talked about strengths as Organic, integrated ERP system. Not in power point but in real life,  with same business processes. For me it was a opportunity of a life time.

 1.Separate material master- Oracle OPM 11.i (which is equivalent of SAP PP-PI ECC 6.0) has separate material master for purchasing  and Process manufacturing. What! Same data stored at two different place and synchronized using batch program. Sounds disaster to me.

 2. Direct data updates – Most master and transaction data in Oracle can be updated Using direct input. So if you don’t like  the GR dates, Just Use mass update program?  I wish I had that flexibility with SAP.

 3. Role & responsibilities – To navigate from say  ‘material document’ to  ‘warehouse stock’  to  ‘material master’ just click , click, click in SAP.   In Oracle,  I must switch responsibilities (equivalent of role in SAP)

 By the time I found out correct responsibility to stwich, I had hard time remembering what  I was looking for.

4. Transaction codes – I have started loving the 4 digit transaction codes and table names so much more now. when I say MMBE, every SAP users knows what I am talking about. No such mundane pleasure in oracle. And those 4 digit table names in MARA, MARC, MARD…they are just made in heaven.

 4. Printing and data download – I must admit, This is really easy compared to SAP.  Wish I could send data to PDF or Excel so effortlessly.

After this project, my love and respect for SAP grew even further. 

Did anyone had similar experience? I would be very interested to know.   

2 Comments
You must be Logged on to comment or reply to a post.