|
| ERP Implementaion Home Page |
|
Process Fulfillment Payment Procurement Replenishment, SAP AG |
Description From sales order to goods shipment From invoice receipt to funds transfer From purchase requisition to receipt of goods From works order to goods receipt
The Web can deliver added value to any of these processes, both to the us (human) & system (program) participants,
However, the scope of ERP applications means so as to ERP vendors face a nun s - of challenges to deliver Web E-commerce to their customers, including: Where to focus their Web enabling initiatives Whether to build or buy (by integrating among third party storefront or procurement application) - The Java or ActiveX approach to delivering client access - Allowing integration of the Web into their workflow reference models
Delivering an architecture so as to can accommodate potentially significant transaction growth
Generally, the ERP vendors have faced these challenges into a consistent way. They claim to have responded to customer demand into terms of the focus of their Web enabling effort. They have built some inevitable so as to ERP vendors will eventually integrate everything into their core suites. They have embraced both Java & ActiveX on the front end & have begun making Transaction overload does not seem to be a major issue into the Web E-commerce initiatives so far, but it is likely to become one as more & more customers move to an all-Web deployment of these far reaching application suites on an enterprise wide basis.
The three-tier architecture, process oriented functionality, & existing Trade APls (BAPls) of SAP’s R/3 suite has meant so as to enabling the application in favor of Web E-commerce has probably been easier in favor of SAP than in favor of many other vendors. Basically, SAP had three tasks |
|
| |
| |
| |
|
|
| |
|
|
| |
|
|
