Therefore, the products that can truly manage SAP business processes must be heterogeneous in their platform support, must cover both J2EE- and ABAP-based applications, and must be able to correlate traditional and non-traditional metrics into the overall business transaction the end user cares about. SAP business processes implemented on the SAP NetWeaver platform typically also connect to traditional backends such as SAP R/3. Although newer SAP applications are developed on top of the SAP NetWeaver platform, most business applications continue to reside on traditional platforms such as SAP R/3. The migration path for SAP customers will be evolutionary in nature. This paper discusses the impact of performance of creating users in SAP Netweaver Portal using different methods like ERP, etc, to find out that is it possible or not. SAP customers that have been running their business processes on traditional SAP R/3 Basis platforms are migrating to the SAP NetWeaver infrastructure and Enterprise Services Architecture (ESA) to gain business agility through distributed architecture. With ever-evolving changes in business, coupled with constant evolution of technology that promises increasingly efficient ways of doing business, enterprises running on traditional 3-tier infrastructures are migrating to distributed service-oriented platforms. Today's enterprises face high costs and the complexity of implementing business-critical processes that are by nature distributed run on heterogeneous infrastructure and touch multiple parties including customers, partners, and suppliers.

Sap netweaver portal flynn