Expert Sizing & Methods of Sizing Validation
This presentation will, explain principles of expert sizing, that is, sizing beyond the scope of tools, show you how to create your own sizing guidelines, provide a small check list for test cases and test systems, and explain methods of sizing validation. Download the Document
This presentation will, explain principles of expert sizing, that is, sizing beyond the scope of tools, show you how to create your own sizing guidelines, provide a small check list for test cases and test systems, and explain methods of sizing validation. 1Public
Public
Expert Sizing & Methods
of Sizing Validation
Sebastian Schmitt, SAP
Public
Expert Sizing & Methods
of Sizing Validation
Sebastian Schmitt, SAP
2Public
Goals of this Presentation
Sometimes customers and consultants develop their own application or strongly modify existing coding, so
that standard guidelines often cannot apply.
This presentation will
• Explain principles of expert sizing, that is, sizing beyond the scope of tools
• Show you how to create your own sizing guidelines
• Provide a small check list for test cases and test systems
• Explain methods of sizing validation
Goals of this Presentation
Sometimes customers and consultants develop their own application or strongly modify existing coding, so
that standard guidelines often cannot apply.
This presentation will
• Explain principles of expert sizing, that is, sizing beyond the scope of tools
• Show you how to create your own sizing guidelines
• Provide a small check list for test cases and test systems
• Explain methods of sizing validation
3Public
Expert Sizing
§ Guidelines
§ Expert Usage of Quick Sizer
§ Creating Your Own Sizing Guideline
Methods of Sizing Validation
Agenda
Expert Sizing
§ Guidelines
§ Expert Usage of Quick Sizer
§ Creating Your Own Sizing Guideline
Methods of Sizing Validation
Agenda
4Public
ECC Server
Send orders to SCM via qRFC
Send Advanced shipping notification (ASN) to
SCM via PI
Interface Integration – Example of Complex Data Flow
User 1 User n
1. CRM à SCM (ATP check): sRFC (synchronous RFC, proprietary protocol)
2. CRM à ECC (transfer unchecked delivery): qRFC (CRM middleware)
3. ECC ß à SCM (transfer orders): qRFC (CIF, proprietary protocol)
4. PI à ECC (transfer ASN): http / XML
5. ECC à PI à SCM (transfer Advanced Shipping Notification (ASN)): http / XML
PI Server
Send ASN to ECC
From ECC route ASN to SCM
CRM Server
Perform ATP check in SCM
Send unchecked delivery to ECC
qRFC
http / XML
http / XMLqRFC
http / XML
SCM Server
Receive ASN from PI
Receive orders from ECC
Send orders to ECC
1
2 3
4
5
5
User 1 User nUser 1 User n
sRFC
1
2
3
4
5
ECC Server
Send orders to SCM via qRFC
Send Advanced shipping notification (ASN) to
SCM via PI
Interface Integration – Example of Complex Data Flow
User 1 User n
1. CRM à SCM (ATP check): sRFC (synchronous RFC, proprietary protocol)
2. CRM à ECC (transfer unchecked delivery): qRFC (CRM middleware)
3. ECC ß à SCM (transfer orders): qRFC (CIF, proprietary protocol)
4. PI à ECC (transfer ASN): http / XML
5. ECC à PI à SCM (transfer Advanced Shipping Notification (ASN)): http / XML
PI Server
Send ASN to ECC
From ECC route ASN to SCM
CRM Server
Perform ATP check in SCM
Send unchecked delivery to ECC
qRFC
http / XML
http / XMLqRFC
http / XML
SCM Server
Receive ASN from PI
Receive orders from ECC
Send orders to ECC
1
2 3
4
5
5
User 1 User nUser 1 User n
sRFC
1
2
3
4
5
5Public
General Statements
• Effects of custom coding/3rd party often not predictable
– A ”small” modification may have a large impact
Method
• Analysis: To what extend are bread-and-butter processes affected?
– Small backend transactions without business impact may be omitted
– If necessary, measure performance of test cases
– SAP delivers the toolset (CCMS, eCATT)
– For quality assurance, performance measurements ought to be done, anyhow
• Use modular approach
– You may use SAP standard sizing tools for the SAP-related sizing
– Add the requirements of 3rd party, custom coding on top
– Note: some ISVs (Independent Software Vendors) are required to provide standard sizing guidelines
Sizing Integrated Scenarios: Custom Coding/3 rd Party/Cloud
3000 SAPS
12 GB memory
800 SAPS
3 GB memory
2000 SAPS
6 GB memory
1500 SAPS
6 GB memory
4000 SAPS
12 GB memory
11,300 SAPS
39 GB memory
General Statements
• Effects of custom coding/3rd party often not predictable
– A ”small” modification may have a large impact
Method
• Analysis: To what extend are bread-and-butter processes affected?
– Small backend transactions without business impact may be omitted
– If necessary, measure performance of test cases
– SAP delivers the toolset (CCMS, eCATT)
– For quality assurance, performance measurements ought to be done, anyhow
• Use modular approach
– You may use SAP standard sizing tools for the SAP-related sizing
– Add the requirements of 3rd party, custom coding on top
– Note: some ISVs (Independent Software Vendors) are required to provide standard sizing guidelines
Sizing Integrated Scenarios: Custom Coding/3 rd Party/Cloud
3000 SAPS
12 GB memory
800 SAPS
3 GB memory
2000 SAPS
6 GB memory
1500 SAPS
6 GB memory
4000 SAPS
12 GB memory
11,300 SAPS
39 GB memory