SAP Hardware

Hi ,
I am given the Project of SAP ECC 6 implementation, In that we have to implemment FICO,SD,HR amd MM Module ,
Please let me know what will be hardware configuration of servers , as we are planning to purchase HP Servers .
Secondly Please let me know what is the Use os SAPS in hardware configuration ,
I have used http://service.sap.com/quicksizer, but it doesnot solve the purpose
Can anybody help me in deciding the hardware configuation in step by step way
Thanks & Regds
Manish

Manish
The modules that you are implementing are quite common.
So to decide the hardware configuration,Please tell what will be the apprx. number of your end users and approx. no of your project team.
This will help decide the hardware config.Also are you planning for Windows or Unix
Please let us know this information so that we can help you
Rohit

Similar Messages

SAP Hardware sizing for "User-Based sizing".

Short Text
User-based Hardware Sizing
Long Text
Dear SAP Support,
We would like to know the SAP Hardware sizing for "User-Based sizing".
Our queries is
1. In "User-Based sizing", What we have to consider,
the number of users are calculated in the basis of
Concurrent users in the system in a given point of time
or
total number of users logged into the systems in the whole day?
We have referred the SAP document "Sizing SAP System" and the above
point are not clearly mentioned.
Regards,

As the document says there are number of possible definitions for "users" in SAP context...
For understanding assume that no of users logged to the system they consume different resources / areas in the system, some login to the system whole day but they don't work whole day, some user open multiple session to work while other open multiple session but they don't exactly work on it which means (every new session consume memory/resources) like you said their are concurrent users wherein they work and consume resources (SAP WPs)
So before finalizing the sizing first compare the both reports (user based, thorhgput) and read the advantages and disadvantages for both. You can also consult with SAP / Account Manager to help you
as per SAP document there's no point in counting no of pc's, laptops to calculate no of users
Also refer:
http://www.sap.com/solutions/benchmark/index.epx

How to Minimize SAP Hardware utilization.

We are hosting SAP solutions for our Small and Medium customers. Currently we are focusing on reducing our TCO.
What should be our approach to reduce the cost of hardware. We are already looking for Virtualuization.
But still one instance of SAP ECC 6.0 is taking 150-170 GB Hard disk space. How can i reduce disk space utilization.

Hai,
We are hosting SAP solutions for our Small and Medium customers. Currently we are focusing on reducing our TCO--->
Bladeframe and Flexframe are one of the solutions
Useful Link-
http://www.egenera.com/pdf/sap_netweaver.pdf
What should be our approach to reduce the cost of hardware. We are already looking for Virtualuization---->
There are couple of ways for getting the Virtualization.
Adaptive Computing with SAP ACC is one of that approach
Useful link -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/974dee2c-0a01-0010-7398-c3e4f4274794
But still one instance of SAP ECC 6.0 is taking 150-170 GB Hard disk space. How can i reduce disk space utilization.-----> I think every ECC installation will take atleast a minimum of 150GB for installation,check with any IS specific installations.
Thanks and Regards,

PI 7.0 Hardware Requirements & Confirguration

Hello,
We are planning to install PI 7.0 on the AIX 5.3.x(64 bit) with database DB2 UDB 8.2.x.(64 bit) for a Sandbox environment.
I am new to the XI area. I need some small/detailed information regarding following requirements( from PI BASIS point of view)
1) Hardware requirements
2) Memory requirements
3)Any hardware or platform constraints for the AIX & DB2.
4) PI 7.0 Configuration.
5) Idoc Interfacing.
6) Architectural considerations for Integration server, Java AS, SLD etc.
7) Authorizations in XI
you can mail me on [email protected]
Thanks,
Dnyandev

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/95d7d490-0301-0010-ce93-c58f9a3cde0b">Installation Guide</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/58/d22940cbf2195de10000000a1550b0/content.htm">User Roles in an XI Landscape</a>
The requirements depend on the operating system and the database used for the installation.
Go to http://service.sap.com/instguides -> SAP Netweaver -> Release 04 -> Installation -> SAP Web AS -> SAP Web AS 6.40 SR1 and Related Documentation -> Choose your database (Ex: Oracle ) -> Planning and Preparation -> Select SAP Web AS ABAP for Windows.
Look at Page 37, minimum RAM is 1 GB (because XI is Unicode), ABAP system 25GB.
You should check the same for Web AS Java also.
one more small thought...
You also need to find the how the end user will access your system. In case an end user access outside of the LAN (say via WAN or dial-up) using https, it will have additional requirements for your hardware as you will need compression enabled for improved response time for WAN. Adding compression or SSL may add additional hardware if you based your sizing based on LAN.
And also One easy approach is after you define your test case, run some load test on your QA/Staging system. Use the load test data and find out the hardware requirements based on load test. If your requirement is larger than the staging system, you may have to take a staged approach. In that case you roll-out the system to a certain number of users and monitor the system and plan for additional users based on the monitored results.
Also for RAM memory, HDD size you can check this document:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/unkown/sizing%20guide%20-%20sap%20xi%203.0.pdf
Also go through these links...
/people/susanne.janssen/blog/2005/06/09/efficient-sap-hardware-sizing-quick-sizer
http://service.sap.com/quicksizing

Hardware Key Information??

Hello All,
On what hardware change SAP Hardware Key depends??Does it depend on RAM,CPU or Motherboard??Which hardware component change will change my hardware key??

but no where it is written that whether my hardware key changes on changing CPU,RAM??
Quote from SAP Note 174911
On HP UX, AIX, Solaris, and Reliant systems, functions of the operating system are used to determine the hardware key. As a result, the relevant operating system defines how this hardware key is determined.
The hardware key on True64 (formerly DEC UNIX, previously OSF/1) and Linux changes if the computer's network card is replaced. For computers with several network cards, a change in the sequence of cards may change the hardware key. The operating system may randomly switch the internal sequence of the network cards (this has, however, not yet been observed).
Only Windows uses a hardware key that does NOT depend on the hardware. A new installation of Windows definitely causes the hardware key to change.
On OS/390 or z/OS, the key changes when a hardware upgrade is carried out; micro code upgrades may also lead to a new hardware key
I believe that answer your question in detail
I have found in most threads that you try to humiliate others please stop this because you may be expert but not god
This is unfounded, I always post based on my best intention to help... Also is part of my job to keep the forum clean and persuade others to follow the rules.
Yet Again, Read the "Rules of Engagement"
Regards
Juan

SAP permanent license getting changed to temporary

Hello experts,
I am on SAP CRM ABAP 7.0 (Kernel release 701). I am facing a strange problem with respect to sap license. Last week we have installed a permanent license as lots of jobs were failing and it showed type "Perm" in transaction "slicence" with exp date "31.12.9999" corresponding to active hardware key. Bur surprisingly however it changed back to type "Temp" after a while with retention of 1 month.
And today morning it showed a "Valid From" as the date of last restart.
As of now we have installed the permanent license but we fear that it might again get changed to "Temp" after a while or during next restart.
Did any of you faced this earlier and if yes what is the exact cause and solution of this?
Regards
Sourabh Majumdar

Especially linux servers are known for changing hardware keys along with the MAC address. If you have linux you might want to read note [1178686 - Linux: Alternative method to generate an SAP hardware key|https://service.sap.com/sap/support/notes/1178686]
Check in SLICENSE if your license entry is displayed with blue characters, this would be the active license. If it is black, then the license is for another hardware key.
Cheers Michael

SAPS in sizing Guide

Hi
Can you please help me to find out more details about processor in MDM sizing?
From CPU I got result: 6500 I do not know how can I find processor, can you help me ?
I found something here:
http://aroundsap.blogspot.com/2007/09/sap-hardware-sizing-and-benchmarking.html
but that is not exactly what I am looking for.
Many thanks for finding CPU type.
My result for RAM is 10 GB do you think that is correct, we have 8 repositories?
I think my calculation is correct - I just woult like to have others consultancy
Thank you in advance.
Have a nice day.
BR
Michal

Hi ,
SAP periodically benchmarks different servers and indicates their SAPS. Visit:
http://www.sap.com/solutions/benchmark/index.epx
Select on the right under SD Benchmarks ->"SD two-tier results" (as NW MDM is more similar to a 2 tier architecture).
A table will open with all benchmarked server's SAPS results.
The list updates periodically.
You can download it to a text delimited file.
Hard to indicate regarding the RAM you received without having more details.
The calculation should be done for each repository on the server separately and then added up.
Generally, 10GB memory seems a resonable result.
Regards,
Hedda Cohen.

Number for bDocs processed per hour in custom interface to SAP CRM from Tibco

Hello Experts,
Could you please let me know the ideal Number for bDocs processed per hour for a interface which has SAP CRM and TIBCO.
The intent is to use to most easy to scale technology for a custom interface to SAP CRM from Tibco .
I did check the forums but was not able to get a definitive answer.
I understand that it is not possible to quantify the exact number of BDocs that can be processed in an hour,but could you please let me know the factors on which it depends.
Regards,
Akash

It depends on type of data you want to process and the size of your hardware. My rule of thumb is that you should be able to do at least 1 BDOC per second in a worst case scenario or 3600 records for a small size system. Keep in mind the biggest bottleneck is the database update/lookup times. A properly sized large system, could do much more volume. Your best bet is put in the desired transactional throughput into the SAP quicksizer and then work with your SAP hardware partner to approriately size your production box.
If you already have hardware for production bought/existing, then find out the current SAPS rating for your hardware and then use the quicksizer to determine the target SAPS needed to meet your requirements.
Take care,
Stephen

Performance Check in XI

Hi All,
I want to check the performance of the scenario (RFC to Soap) in XI/PI like how much time it has taken process the messages (Total time taken from ECC<>PI<>Third party application) in step wise like,
When the message got fired from ECC,when it reached PI/XI and when it fired from PI/XI to reached 3rd party application.
Please guide me how to find out timing?
Thanks & Regards
Uma

hi,
Use perfromnace monitoring .
find below blogs it micght help you and ask netweaveadmin.
/people/susanne.janssen/blog/2005/07/01/quick-sizer--getting-started
/people/susanne.janssen/blog/2005/06/09/efficient-sap-hardware-sizing-quick-sizer
/people/susanne.janssen/blog/2006/02/03/interpreting-quick-sizer-results
regards,
raj

Cache server configuration

Hi,
 We have installed the content server quite long back and it is working fine. Now as part of plant rollout we are installing cache server for other locations. We have installed cache server. But We have few doubts in configuring. Can sombody has any material wrt cache server configuration (like SCMSHO,SCMSCA...) with screen shots.
prasanna

Hello,
find the below comments ,could be helpful for you.
Pre-Installation Checklist for the SAP Knowledge Warehouse
Cache server Softwere
 Windows NT 4.0 Server English ( SP 4 or 5)
 Windows NT Option Pack 4.0 with following components:
 IIS 4.0
 MS Data Access Components 1.5 (MDAC:ADO,ODBC and OLE DB) or higher
 MS Managemant Console
 NT Option Pack Common Files
 Transaction Server (TS Core Componennts)
 Windows Scripting Host (Windows Scripting Host Files)
 MS Proxy Server 2.0
 No non-SAP applications must be installed.
 TCP/IP - protocol
 RFC to the R/3 system must be possible
Cache Server Hardware
 Manufactured by a SAP hardware partner
 512 MB RAM
 2 x Pentium Pro 200 MHz or higher (no Alpha CPUs)
 Raid 1 for the operating system
 Raid 5 for the devspaces of the SAP DB (recommended: 72 GB available)
 Raid 1 for the logs of the SAP DB (at least 2 GB available, should not be on the same Raid like the Devspaces or the NT Page file)
 High performance SCSI controller
 Hostname must satisfy the requirements for R/3 -Installations
Regards,
Murali.S

Programming standards

what are theprogramming standardsfollowed?

where....
·         Use select single * from ... as much as possible. Only use select * from ... when absolutely necessary. Select single will return only one record. However, if you dont specify the whole key to the table, the returned record will be any line of the records that meets the specified key.   Only use Select Single when the full key of the table is known.
·         Specifying values for as many of the tables key fields in a WHERE clause will make the SELECT statement more efficient than checking values after the select.
·         Never use any processing statement within SELECT ENESELECT. In case it is required, populate an internal table corresponding to the table, loop at the internal table and do the processing there.
·         Specifying the left-most/least specific key fields in a WHERE clause improves efficiency.
For example, the key fields (in sequence) of the table KNC3 (Customer special G/L transaction )
MANDT       -         Client
KUNNR       -         Customer number
BUKRS       -         Company code
GJAHR       -         Fiscal year
SHBKZ       -         Special G/L indicator
When selecting data from this table, it would be more efficient to specify a value in the WHERE clause for the field KNC3-BUKRS, rather than KNC3-GJAHR. That is:
SELECT * FROM KNC3
      WHERE KUNNR EQ 0000000001
      AND   BUKRS EQ US01.
ENDSELECT.
will be more efficient than:
SELECT * FROM KNC3
          WHERE KUNNR EQ 0000000001
          AND   GJAHR EQ 1996.
ENDSELECT.
·         You can specify as many WHERE conditions as you like in all types of database tables ‑ i.e. transparent tables, pool tables and cluster tables. However, you should be aware for performance reasons that complex WHERE conditions involving pool and cluster tables usually cannot be passed to the database system. They must be processed by the SAP database interface through post‑selection.
·         Selecting via non-key fields.   When selecting records from a database table when only part of a field (on which selection is based) is known, use the LIKE option as part of the WHERE clause.
For example:
SELECT *    FROM T001G
WHERE     BUKRS EQ   US01
AND       TXTKO LIKE __PERS%.
ENDSELECT.
is more efficient than:
SELECT * FROM T001G
WHERE BUKRS EQ US01.
CHECK T001G-TXTKO+2(4) = PERS.
3.1.7.5   Defining Variables
·         When defining variable use LIKE as much as possible to ensure automatic consistency with the items in the R/3 tables.
·         All variables should have a description to the right of the declaration.
·         Always keep the SAP names. DO NOT translate. If you need the same type of data from different tables like document numbers for different documents, prefix the name with the table name like:
       WS_VBAK_VBELN                                         Sales Order No.
       WS_LIKP_VBELN                                         Delivery No.
3.1.7.6   Testing one field for multiple values
When testing an individual field for multiple values, you can use:
IF        field = value1.
ELSEIF    field = value2.
ELSEIF    field = value3.
                         or
CASE field.
    WHEN value1.
    WHEN value2.
    WHEN value3.
ENDCASE.
The first method is more efficient when checking a field for up to about five values. Beyond this, you should use the CASE statement. At this point it becomes more efficient than the nested Ifs, and will also improve the readability of the program code
3.1.7.7   Optimizing IF and CASE structures
To optimize IF and CASE structures, always test values in order of the likelihood of each value occurring.
For example, WS_FIELDX can have values A, B, or C.   A value of B is the most likely value to occur, followed by C, then A. To optimize a CASE statement for WS_FIELDX, code the CASE statement as follows:
CASE WS_fieldx.
      WHEN B.      Most likely value
      WHEN C.      Next most likely value
      WHEN A.      Least likely value
ENDCASE.
Here, if WS_FIELDX has a value of B, only one test is performed, if it has a value of C, two tests must be performed, and so on. Coding in this manner reduces the average number of tests performed by the program.
3.1.7.8   Performing Calculations
    When performing calculations in ABAP, the amount of CPU time used depends on the data type. In very simple terms, Integers (type I) is the fastest, Floating Point (type F) requires more time, and Packed (type P) is the most expensive. Normally, Packed number arithmetic is used to evaluate arithmetic expressions. If, however, the expression contains a floating point function, or there is at least one type F operand, or the result field is type F, floating point arithmetic is used instead for the entire expression. On the other hand, if only type I fields or date and time fields occur, the calculation involves integer operations.
Since floating point arithmetic is relatively fast on SAP hardware platforms, it should be used when a greater value range is needed and rounding errors can be tolerated. Rounding errors may occur when converting the external (decimal) format to the corresponding internal format (base 2 or 16) or vice‑versa.
3.1.7.9   Packed Number Arithmetic
If the program attribute Fixed point arithmetic is not set, type P fields are interpreted as integers without decimal places. The DECIMALS parameter of the DATA statement only affects the format of the WRITE output.
For this reason, SAP recommends that you always set the program attribute Fixed point arithmetic when working with type P fields
3.1.7.10          Moving identical structures
Use:                 MOVE structure1                  TO structure2.
or                      structure2 = structure1
instead of:       MOVE-CORRESPONDING structure1         TO structure2.
3.1.8 Commands
The following is a selected list of preferred commands along with a short functionality description of the command. For further details, use the ABAP editor help.
3.1.8.1   Catch/EndCatch
You can catch ABAP runtime errors in the processing block enclosed in the CATCH ... ENDCATCH statements.
Syntax: CATCH SYSTEM-EXCEPTIONS except1 = rc1 ... exceptn = rcn.
Note the following:
·         rc1 ... rcn must be numeric literals.
·         CATCH ... ENDCATCH may be placed anywhere where IF ... ENDIF (for example) may occur. It is local, not cross-event.
·         It may be nested to any depth.
·         It only catches runtime errors in the current call level. This means, for example, that runtime errors resulting from PERFORM- or CALL FUNCTION statements are not trapped by CATCH ... ENDCATCH.
Example:
PARAMETERS fact TYPE i.
DATA: fact_save TYPE i,
      res(16) TYPE p.
ARITHMETIC_ERRORS contains COMPUTE_BCD_OVERFLOW ***
CATCH SYSTEM-EXCEPTIONS ARITHMETIC_ERRORS = 5.
res = fact_save = fact.
SUBTRACT 1 FROM fact.
DO fact TIMES.
    MULTIPLY res BY fact. "

BPM Speed Up Tunning

My Scenario is Real-Time.
My Scenario is
RFC(Destination)->XI(BPM)->FILE.
So, BPM scenario is start->reciecve->transformation->Send. BPM is very simple.
But the scenario time is 3.3 second. But I woud like to 0.1 to 0.5 second.
How to ?
Help me
Message was edited by: JuYeop Kim
Message was edited by: april19
Message was edited by: JuYeop Kim

Hi,
As Bhavesh as suggested, try your best to avoid transformation steps within the BPM. This would definitely improve the performance..
Please go through these links to know more about Performance tuning in XI:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8b-c935e444b0ad
http://help.sap.com/saphelp_erp2005/helpdata/en/42/e7bb8f7c9d3ee0e10000000a1553f6/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/88/21bc3ff6beeb0ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/ee3441d95dd92be10000000a1550b0/frameset.htm
/people/susanne.janssen/blog/2005/06/09/efficient-sap-hardware-sizing-quick-sizer
Also go through SAP Note 857530
I hope it helps....
Regards,
Abhy

Hi Experts! Clarififcation regardng the phases of project in real time

Hi ,
Can any body please explain the phases of project and thier details like wht all will be done at each stage in the real time since i am very new to tht kind of phases ..
Please donot kindly send me any links for reference rather plz describe it in detail..
Regards,
Eshwant....

Hi,
Implementation processes:
Project preparation
The project preparation phase, depicted below, focuses at two main activities, i.e. to make a setup for the TSO and to define a solution vision. These activities allow an organization to put in on the right track towards implementation.
Design and initially staff the SAP TSO
TSO chart exampleThe first major step of the project preparation phase is to design and initially staff an SAP technical support organization (TSO), which is the organization that is charged with addressing, designing, implementing and supporting the SAP solution. This can be programmers, project management, database administrators, test teams, etc. At this point, the focus should be at staffing the key positions of the TSO, e.g. the high-level project team and SAP professionals like the senior database administrator and the solution architect. Next to that, this is the time to make decisions about choosing for internal staff members or external consultants.
The image at the right shows a typical TSO chart.
Craft solution vision
The second project preparation job is to define a so-called solution vision, i.e. a vision of the future-state of the SAP solution, where it is important to address both business and financial requirements (budgets). The main focus within the vision should be on the companys core business and how the SAP solution will better enable that core business to be successful. Next to that, the shortcomings of the current systems should be described and short but clear requirements should be provided regarding availability (uptime), security, manageability and scalability of the SAP system.
Sizing and blueprinting
The next phase is often referred to as the sizing and blueprinting phase and forms the main chunk of the implementation process
Perform cost of ownership analysis
Figure 5: Solution stack delta analysisThis phase starts with performing a total cost of ownership analysis (TCO analysis) to determine how to get the best business solution at the lowest costs. This means to compare SAP solution stack options and alternatives and then determine what costs each part of the stack will bring and when these costs will be incurred. Parts of the stack are for example the hardware, operating system and database, which form the acquisition costs. Next to that, there should be taken a look at recurring costs like maintenance costs and downtime costs. Instead of performing a complete TCO analysis for various solution stack alternatives that would like to compare, it can be wise just to do a so-called delta analysis, where only the differences between solutions (stacks) are identified and analyzed. The image at the right depicts the essence of a delta analysis.
Identify high availability and disaster recovery requirements
The next step is identifying the high availability requirements and the more serious disaster recovery requirements. This is to plan what to do with later downtime of the SAP system, caused by e.g. hardware failures, application failures or power outages. It should be noted that it is very important to calculate the cost of downtime, so that an organization has a good idea of its actual availability requirements.
Engage SAP solution stack vendors
Figure 6: Simplified SAP solution stackA true sizing process is to engage the SAP solution stack vendors, which is the next step. This means selecting the best SAP hardware and software technology partners for all layers and components of the solution stack, based on a side-by-side sizing comparison. The most important factors that are of influence here are the estimated numbers of (concurrent) users and batch sizes. A wise thing to do is to involve SAP AG itself to let them create a sizing proposal stating the advised solution stack, before moving to SAPs technology partners/SAP vendors, like HP, Sun Microsystems and IBM. A simplified solution stack is depicted at the right, showing the many layers for which software and hardware has to be acquired. Note the overlap with the OSI model.
Staff TSO
The TSO is the most important resource for an organization that is implementing SAP, so staffing the TSO is a vital job which can consume a lot of time. In a previous phase, the organization should already have staffed the most vital positions. At this point the organization should staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin the installation/implementation of the SAP data center. Examples are: data center experts, network infrastructure experts, security specialists and database administration experts.
There are many ways to find the right people within or outside the organization for all of the TSO positions and it depends on the organization how much time it wants to spend on staffing.
Training
One of the most vital stages of the implementation process is training. Very few people within an organization are SAP experts or even have worked with SAP software. It is therefore very important to train the end users but especially the SAP TSO: the people who design and implement the solution. Many people within the TSO need all kinds of training. Some examples of these positions:
SAP Network Specialists
SAP Database Administrators
SAP Security specialists
Documentation specialists
Et cetera
All of these people need to acquire the required SAP knowledge and skills or even SAP certifications through training. Moreover, people need to learn to do business in a totally new way. To define how much SAP training every person needs, a company can make use of a skillset matrix. With this matrix, a manager can identify who possesses what knowledge, to manage and plan training, by defining the height of expertise with a number between e.g. 1 and 4 for each skill for each employee.
Setup SAP data center
The next step is to set up the SAP data center. This means either building a new data center facility or transforming the current data center into a foundation capable of supporting the SAP solution stack, i.e. all of the technology layers and components (SAP software products) in a productive SAP installation. The most important factor when designing the data center is availability. The high availability and disaster recovery requirements which should have been defined earlier, give a good idea of the required data center requirements to host the SAP software. Data center requirements can be a:
Physical requirement like power requirements
Rack requirement
Network infrastructure requirement or
Requirement to the network server.
Perform installations
The following step is to install the required SAP software parts which are called components and technological foundations like a web application server or enterprise portals, to a state ready for business process configuration. The most vital sub steps are to prepare your OS, prepare the database server and then start installing SAP software. Here it is very important to use installation guides, which are published for each SAP component or technology solution by SAP AG. Examples of SAP components are:
R/3 Enterprise Transaction Processing
mySAP BI Business Information Warehouse
mySAP CRM Customer Relationship Management
mySAP KW Knowledge Warehouse
mySAP PLM Product Lifecycle Management
mySAP SCM Supply Chain Management
mySAP SEM Strategic Enterprise Management
mySAP SRM Supplier Relationship Management
Round out support for SAP
Before moving into the functional development phase, the organization should identify and staff the remaining TSO roles, e.g. roles that relate to helpdesk work and other such support providing work.
[edit] Functional development
The next phase is the functional development phase, where it is all about change management and testing. This phase is depicted below.
Figure 7: Functional development phase
Address change management
The next challenge for an organization is all about change management / change control, which means to develop a planned approach to the changes the organization faces. The objective here is to maximize the collective efforts of all people involved in the change and to minimize the risk of failure of implementing the changes related to the SAP implementation.
The implementation of SAP software will most surely come with many changes and an organization can expect many natural reactions, i.e. denial, to these changes. To fight this, it is most important to create a solid project team dedicated to change management and to communicate the solution vision and goals of this team. This team should be prepared to handle the many change issues that come from various sources like:
End-user requests
Operations
Data center team
DBA group
Systems management
SAP systems and operations management
Next thing is to create a foundation for the SAP systems management and SAP computer operations, by creating a SAP operations manual and by evaluating SAP management applications. The manual is a collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents.
Functional, integration and regression testing
Testing is very important before going live with any system. Before going live with a SAP system, it is vital to do many different kinds of testing, since there is often a large, complex infrastructure of hardware and software involved. Both requirements as well as quality parameters are to be tested. Important types of testing are:
Functional testing: to test using functional use cases, i.e. a set of conditions or variables under which a tester will determine if a certain business process works
Integration testing
Regression testing
All tests should be preceded by creating solid test plans.
[edit] Final preparation
The last phase before going live can be referred to as the final preparation phase and is depicted below.
Figure 8: Final preparation phase
Systems and stress testing
Another vital preparation activity before going live with SAP is systems and stress testing. This means planning, scripting, executing and monitoring system and stress tests, to see if the expectations of the end users, defined in service level agreements, will be met. This can be done with SAPs standard application benchmarks, to benchmark the organizations configurations against configurations that have been tested by SAPs hardware technology partners. Again, a test plan should be created at first.
Prepare for cutover
The final phase before going live with SAP is often referred to as the cutover phase, which is the process of transitioning from one system to a new one. The organization needs to plan, prepare and execute the cutover, by creating a cutover plan that describes all cutover tasks that have to be performed before the actual go-live. Examples of cutover tasks are:
Review and update all systems-related operations procedures like backup policies and system monitoring
Assign ownership of SAPs functional processes to individuals
Let SAP AG do a GoingLive check, to get their blessing to go live with the system
Lock down the system, i.e. do not make any more changes to the SAP system
[edit] Go Live
All of the previously described phases all lead towards this final moment: the go-live. Go-live means to turn on the SAP system for the end-users and to obtain feedback on the solution and to monitor the solution. It is also the moment where product software adoption comes into play. More information on this topic:
Product Software Adoption: Big Bang Adoption
Product Software Adoption: Parallel Adoption
Product Software Adoption: Phased Adoption
HTH
Regards,
Dhruv Shah

Study business process requirements in sd implementation project?

how to study business process requirements in sd implementation project?

Hi chandu,
I will suggest you first go through the document given below
SAP Implementation is the whole of processes that defines a complete method to implement SAP software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software.
Concept Definition
CHANGE MANAGEMENT ***Activities involved in (1) defining and installing new values, attitudes, norms, and behaviors within an organization that support new ways of doing work and overcome resistance to change; (2) building consensus among customers and stakeholders on specific changes designed to better meet their needs; and (3) planning, testing, and implementing all aspects of the transition from one organizational structure or business process to another. (www.gao.gov)
CHANGE MANAGEMENT DOCUMENTATION All documentation that is required and being delivered whilst performing change management, e.g. the functional test cases and all the other documents a new end-user of SAP requires and the various tools and approaches used to manage change by the TSO. (Anderson, 2003)
COST OF OWNERSHIP ANALYSIS Determination of where and when the costs are inquired within the context of the SAP solution stack and ongoing operations. The analysis addresses all internal and external costs, both one-time as well as recurring (Anderson, 2003)
CUTOVER The process of transitioning from one system to a new one (Anderson, 2003)
CUTOVER PLAN All documentation related to planning, preparing and executing cutover, describing how to lock down the system from a technical change management perspective, preparing the TSO for its new role and rolling out the SAP graphical user interface to all future end users. (Anderson, 2003)
DATA CENTER A data center is a facility used for housing a large amount of electronic equipment, typically computers and communications equipment. (www.wikipedia.org)
DATA CENTER REQUIREMENT A requirement for the SAP data center, i.e. a physical requirement like power requirements, a rack requirement, a network infrastructure requirement or a requirement to the network server. (Anderson, 2003)
DISASTER RECOVERY (DR) REQUIREMENT Requirement that focuses on downtime that lasts many hours to days or even weeks (Anderson, 2003)
FUNCTIONAL TEST CASE A set of conditions or variables under which a tester will determine if a certain business process works (www.wikipedia.org)
HIGH AVAILABILITY (HA) REQUIREMENT Requirements that describes the amount of time that the system needs to be available to satisfy the needs of the users. (Anderson, 2003)
INSTALLATION DOCUMENTATION All documentation related to the installation of an end-to-end SAP solution (Anderson, 2003)
OPERATIONS MANUAL The collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents. (Anderson, 2003)
SAP SAP AG is the name of the biggest European software company. The head office is in Walldorf, Germany. SAP was founded in 1972 as Systemanalyse und Programmentwicklung ("Systems Analysis and Product") by five former IBM employees in Mannheim, Germany. (www.wikipedia.org)
SAP IMPLEMENTATION PROJECT PLAN A comprehensive project plan that contains all products that are delivered whilst performing an SAP implementation project (Anderson, 2003)
SOLUTION STACK Set of software subsystems or components needed to deliver a fully functional solution, e.g. a product or service. (www.wikipedia.org)
SOLUTION STACK PARTNERS LIST A list of all vendors that deliver the products that make up the SAP solution stack (Anderson, 2003)
SOLUTION VISION A vision of the future-state of the SAP solution (Anderson, 2003)
STRESS TEST PLAN A test plan that is focused at determining the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. (www.wikipedia.org)
TEST PLAN A detail of how the test will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed. (IEEE 829)
TRAINING The acquisition of knowledge, skills, and attitudes as a result of the teaching of vocational or practical skills and knowledge that relates to specific useful skills (www.wikipedia.org)
TRAINING PLAN Consisting of training units, a training plan is the result of hierarchical decompositions of a training goal, tailored according to the learning preferences and prior knowledge of the trainee. A plan is the means by which the trainee satisfies the goal. (www.ece.eps.hw.ac.uk/)
TSO Technical Support Organization. The people that are committed to implementation and management of SAP. (Anderson, 2003)
TSO CHART A chart that depicts the structure of the TSO. (Anderson, 2003)
Activity Sub-Activity Description
Project preparation Craft solution vision Refine and communicate a SOLUTION VISION of the future-state of the SAP solution, to sketch a design that meets both business and financial requirements. The focus should be on the companyu2019s core business and how the SAP solution will better enable that core business to be successful.
Design and initially staff the SAP TSO Design and staff the key positions of the SAP Technical Support Organization (TSO), the organization that is charged with addressing, designing, implementing and supporting the SAP solution.
Sizing and blueprinting Perform cost of ownership analysis Perform a COST OF OWNERSHIP ANALYSIS to determine how to get the best business solution for the least money i.e. to determine where and when the costs are incurred within the context of the SAP solution stack.
Identify high availability and disaster recovery requirements Determine all HIGH AVAILABILITY and DISASTER RECOVERY REQUIREMENTS, to plan what to do with later downtime of the SAP system
Engage SAP solution stack vendors Select the best SAP hardware and software technology partners for all layers and components of the SAP SOLUTION STACK, based on a side-by-side sizing comparison
Staff TSO Staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin installation/implementation of the SAP data center.
Execute training Train the various members of the SAP TSO, like data center specialists, high availability specialist and network specialists and train the end-users to give all the required SAP knowledge and skills
Setup SAP DATA CENTER Build a new SAP DATA CENTER facility or transform the current data center into a foundation capable of supporting the SAP SOLUTION STACK
Perform installations Install the (My)SAP components and technological foundations like a web application server or enterprise portal.
Round out support for SAP Identify and staff the remaining TSO roles, e.g. roles that relate to help desk work and other such support providing work.
SAP functional development Address Change Management Develop a planned approach to the changes in the organization. The objective is to maximize the collective efforts of all people involved in the change and minimize the risk of failure of implementing the changes related to the SAP implementation.
Address SAP systems and operations management Create a foundation for the SAP systems management and SAP computer operations, by creating a SAP OPERATIONS MANUAL and by evaluating SAP management applications.
Perform functional, integration and regression tests Test the SAP business processes, by executing functional tests to ensure that business processes work, integration tests to ensure that the organizationu2019s business processes work together with other business processes and regression tests to prove that a specific set of data and processes yield consistent and repeatable results.
Final Preparation Perform systems and stress tests Plan, script, execute and monitor SAP STRESS TESTS, to see if the expectations of the end users, defined in service level agreements, will be met.
Prepare for cutover Plan, prepare and execute the CUTOVER, by creating a CUTOVER PLAN that describes all cutover tasks that have to be performed before the actual go-live
Go Live Turn on the SAP system for the end-users
Hope this will help.
Reward Point if helpful.
Thanks,
Raja

ECC6 Sizing Question!

HI All
I need some advice and possible a recommendation on SAP Sizing.
We currently run an ECC6 (Netweaver 2004s) Platform in a 32Bit Environment and we are looking to upgrade to 64-Bit technology (as recommended by SAP). However I want to look at resizing our landscape completely, so has anyone used and companies who specialise in this?
We are based in the UK.
Many Thanks
Phil

Dear Phil,
These are some ofthe good links for Hardware Sizing.
SAP Market place:
https://websmp102.sap-ag.de/sizing
SDN:
Right-Sizing Your Hardware [original link is broken]
These are 2 good links:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS1672
http://aroundsap.blogspot.com/2007/09/sap-hardware-sizing-and-benchmarking.html
This link has got a good document which is really helpful.
www.dell.com/downloads/global/solutions/sap_sizing_wp.doc
There is one book from SAP Press which if you can get will give you good idea on Sizing:
www.sap-press.com/product.cfm?account=&product=H2904
Please click on the folowing link. Use your S-key.
Click on this link:
https://websmp102.sap-ag.de/sizing
Use Quick Sizer: The Quick Sizer is a tool jointly developed by SAP and its hardware partners to help customers get an idea about initial sizing. It is free of cost.
Click on the Customer name . Make a Project Name.
Press on calculate result. This will calculate sizing for you. There are certain details which are required as input such as:
Which systems do you require?
Productive Sys.
Consolidation system
Development System
Database & Operating System
Database DB2 UDBDB2-OS/390DB2-i5/OSDB2-AS/400InformixMAXDBOracleMS SQL Server
Details of DB (e.g. version, parallel)
Current size of DB (in GB)
Operating System AIXAS/400HP-UXLINUXOS/390SOLARISTrue64-UNIXWINDOWS
Details of OS (e.g. version)
Solution
SAP Customer Relationship Mgmt
SAP Enterprise Resource Planning
SAP ERP Financials
SAP ERP Human Capital Mgmt
SAP Product Lifecycle Mgmt
SAP Supplier Relationship Mgmt
SAP Supply Chain Mgmt
SAP NetWeaver
Please let me know if any clarifications are required.
Regards,
Rakesh

SAP Hardware

Similar Messages

Maybe you are looking for