3 ms·

It makes sense that it wasn't covered. Its really specific to a non-CS domain (Business). You probably learned image-processing techniques, but not how to use

by Tobani 13y ago

It makes sense that it wasn't covered. Its really specific to a non-CS domain (Business). You probably learned image-processing techniques, but not how to use photoshop. You might have learned how to use acid-compliant databases, not how to use quickbooks. Designers might have classes on how to use photoshop. Accountants might have classes on how to use quickbooks. You might find a business-related class that covers ERP-related topics?

endersshadow 13y ago
While you may know what ERP stands for, you're missing the bigger picture on what modern ERPs do. They aren't specific to a domain--they do everything from managing manufacturing processes to keeping the books for retailers. I've seen specific ERPs written for dairy distributors used by ice makers. Planning is just one part of an ERP. The General Ledger, WIP, logisitics, customer lists, etc, etc all can and do go into ERPs. Moreover, folks that are experts on an ERP typically are an expert either on (a) one type of ERP (e.g.-SAP), or (b) ERPs for a specific domain (e.g.-manufacturing). You don't typically get somebody who knows many different ERPs across many different businesses. During an ERP implementation, you'll usually hire one of type A, and one of type B, and then a whole team of developers/implementers. Each vendor gives extensive training on all sorts of different aspects of their ERPs, but really, if you'd like to get a handle on what they do, you need to know how enterprises work. And the only way you're going to do that is by working in an enterprise. I've had my exposure to ERPs by building data warehouses that have to read and interact with them. But, my college degree's in management and economics, so things like accounting and business processes were already something I had passing familiarity with. ERPs will make little to no sense if you don't understand how corproate accounting works. ERPs are wildly complex, and each has about 1000 different packages that you can use to do...I don't even know half of what they do. The best way to get some familiarity with ERPs is to get hired in some place where they'll teach you all about it. This includes training in the classroom and on the job. These are typically consulting firms--there are a few big ones, and there are a few boutique ones that do only ERPs. Also, the vendors typically have implementation teams, so you may want to do that, as well. I will note that ERP implementers almost always are required to travel extensively, so if somebody reading this wants to go into it as a career, understand what you're getting into. Travel is insanely lucrative if you don't mind it, but if you have a family or other commitments, it can tear you apart.
- lanaius 13y ago
  A previous employer was a pharmaceutical company that performed all document management for audits, quality, and manufacturing within JDE.
- deleted 13y ago
  [deleted]
- pessimizer 13y ago
  >While you may know what ERP stands for, you're missing the bigger picture on what modern ERPs do. I think his point was that ERPs are specific proprietary applications that are not used as tools for programming, and wouldn't ever show up in any CS curriculum. I didn't see any statement on what ERPs are capable of doing. >But, my college degree's in management and economics, so things like accounting and business processes were already something I had passing familiarity with. ERPs will make little to no sense if you don't understand how corproate accounting works. >You might find a business-related class that covers ERP-related topics? I'm not sure why your response was framed like a disagreement.
  - Tobani 13y ago
    > I'm not sure why your response was framed like a disagreement. They were being pedantic about something in the original post, so I edited the post so the actual point wasn't lost.
  - endersshadow 13y ago
    My intent was to expand upon the idea that it's only a business tool, and direct somebody looking to get into ERPs on how to get educated in them. Taking a course related to ERPs, or for a business user, will get you not very far if you want to do things on the technical side. This is why I mentioned training, career paths, and how I became familiar with them. The only thing I disagreed with the parent about was that I don't consider ERPs to be a "specific domain," anymore than "all of the businesses in the world" is a "specific domain." My intent was to explain to a layman that ERPs manage a ton of different processes, and that they are very complex applications with many different options. Apparently, I have failed to do that. So, sincerely, all apologies.

by Tobani 13y ago

endersshadow 13y ago

While you may know what ERP stands for, you're missing the bigger picture on what modern ERPs do. They aren't specific to a domain--they do everything from managing manufacturing processes to keeping the books for retailers. I've seen specific ERPs written for dairy distributors used by ice makers. Planning is just one part of an ERP. The General Ledger, WIP, logisitics, customer lists, etc, etc all can and do go into ERPs. Moreover, folks that are experts on an ERP typically are an expert either on (a) one type of ERP (e.g.-SAP), or (b) ERPs for a specific domain (e.g.-manufacturing). You don't typically get somebody who knows many different ERPs across many different businesses. During an ERP implementation, you'll usually hire one of type A, and one of type B, and then a whole team of developers/implementers. Each vendor gives extensive training on all sorts of different aspects of their ERPs, but really, if you'd like to get a handle on what they do, you need to know how enterprises work. And the only way you're going to do that is by working in an enterprise. I've had my exposure to ERPs by building data warehouses that have to read and interact with them. But, my college degree's in management and economics, so things like accounting and business processes were already something I had passing familiarity with. ERPs will make little to no sense if you don't understand how corproate accounting works. ERPs are wildly complex, and each has about 1000 different packages that you can use to do...I don't even know half of what they do. The best way to get some familiarity with ERPs is to get hired in some place where they'll teach you all about it. This includes training in the classroom and on the job. These are typically consulting firms--there are a few big ones, and there are a few boutique ones that do only ERPs. Also, the vendors typically have implementation teams, so you may want to do that, as well. I will note that ERP implementers almost always are required to travel extensively, so if somebody reading this wants to go into it as a career, understand what you're getting into. Travel is insanely lucrative if you don't mind it, but if you have a family or other commitments, it can tear you apart.

lanaius 13y ago
A previous employer was a pharmaceutical company that performed all document management for audits, quality, and manufacturing within JDE.
deleted 13y ago
[deleted]
pessimizer 13y ago
>While you may know what ERP stands for, you're missing the bigger picture on what modern ERPs do. I think his point was that ERPs are specific proprietary applications that are not used as tools for programming, and wouldn't ever show up in any CS curriculum. I didn't see any statement on what ERPs are capable of doing. >But, my college degree's in management and economics, so things like accounting and business processes were already something I had passing familiarity with. ERPs will make little to no sense if you don't understand how corproate accounting works. >You might find a business-related class that covers ERP-related topics? I'm not sure why your response was framed like a disagreement.
- Tobani 13y ago
  > I'm not sure why your response was framed like a disagreement. They were being pedantic about something in the original post, so I edited the post so the actual point wasn't lost.
- endersshadow 13y ago
  My intent was to expand upon the idea that it's only a business tool, and direct somebody looking to get into ERPs on how to get educated in them. Taking a course related to ERPs, or for a business user, will get you not very far if you want to do things on the technical side. This is why I mentioned training, career paths, and how I became familiar with them. The only thing I disagreed with the parent about was that I don't consider ERPs to be a "specific domain," anymore than "all of the businesses in the world" is a "specific domain." My intent was to explain to a layman that ERPs manage a ton of different processes, and that they are very complex applications with many different options. Apparently, I have failed to do that. So, sincerely, all apologies.