sg gtm ecc600 aug2012b

Please make sure that you are always using the most current version of the sizing guideline!

Sizing Guide

Sizing Global Trade Management, Version 6.0

Released for SAP Customers and Partners Document Version 1.0, August, 2012

Copyright/Trademark

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and

Visual Studio are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, z10, z/VM, z/OS,

OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems,

POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale,

PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,

Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are

trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United

States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are

trademarks or registered trademarks of Adobe Systems Incorporated

in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-

Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or

registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry

Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2,

BlackBerry PlayBook, and BlackBerry App World are trademarks or

registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data

API, Google Maps, Google Mobile Ads, Google Mobile Updater,

Google Mobile, Google Store, Google Sync, Google Updater, Google

Voice, Google Mail, Gmail, YouTube, Dalvik and Android are

trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies

Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings

LLC.

Computop is a registered trademark of Computop

Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP

products and services mentioned herein as well as their respective

logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of

Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressly prohibited, as is any

decompilation of these components.

SAP Library document classification: CUSTOMERS & PARTNERS

Documentation in the SAP Service Marketplace

You can find this documentation at the following address: http://service.sap.com/sizing

Sizing SAP Global Trade Management - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

1 1

TABLE OF CONTENTS 1. Introduction .................................................................................................................................. 1 1.1 Functions of SAP Global Trade Management ........................................................................... 1 1.2 Architecture of Global Trade Management ............................................................................... 3 2. Sizing Fundamentals and Terminology ..................................................................................... 3 3. Initial Sizing for SAP Global Trade Management ...................................................................... 4 3.1 Assumptions ................................................................................................................................ 4 3.2 Sizing Guideline ........................................................................................................................... 5 3.2.1 Sizing for TC ............................................................................................................................. 5 3.2.2 Sizing for TC Line Items .......................................................................................................... 6 3.2.3 Sizing for TEW (Optional) ........................................................................................................ 8 4. Miscellaneous ............................................................................................................................... 9 5. Comments and Feedback ............................................................................................................ 9

1. INTRODUCTION The SAP Global Trade Management is one of SAP ECC Extension Sets in SAP ERP central component. The component of SAP Global Trade Management (GTM) offers an integrated set of tools, technologies, and capabilities that enable you to execute the full scope of supply chain process such as managing a contract with purchase and sales process simultaneously, carrying out logistic process and inventory efficiently. Following sections provide an overview of the functions and the architecture of SAP Global Trade Management, and its sizing method. Please note that the information is based on version ERP 6.0 and provided herein may be subject to change.

1.1 FUNCTIONS OF SAP GLOBAL TRADE MANAGEMENT

SAP Global Trade Management (GTM) is aimed for simplifying trading business process which is to control and organize the flow of materials and services from vendors to customers. SAP GTM is the function to call SD and MM functions as an interface in order to provide better usability and flexibility. The principle of the trade business is to match demand from the customer with supply from the vendor. This type of business where purchasing and sales are carried out in parallel within one trading department is known as trade business.

SAP Global Trade Management provides mainly four functions:

Trading Contract

Trading Execution Workbench

Trading Expense

Position Management

The business process of GTM contains aspects of Material Management (MM) and Sales & Distribution (SD). Although there are different operation steps necessary for creating purchase and sales orders, the Trading Contract (TC) creates both sales order and/or purchase orders in one single transaction when saving and releasing the document.


Copyright/Trademark

2 2

Logistic process can be executed in Trading Execution Workbench (TEW) after Trading Contract has been saved and released. Subsequent transactions such as delivery, goods receipt, inventory management, goods issue, invoice verification, and customer billing are executed by calling standard SD/MM components via TEW.

There are several types of expenses associated with trading business such as freight charge, insurance and commissions. Those expenses can be handled in Trading Expense linked with Trading Contract. Thus you can maintain purchase related expenses and sales related expenses centrally. Planned expenses can be entered in Trading Contract as a statistical value. Unplanned and provisional expenses can be entered in logistics documents as well as Trading Contract at a later stage when you receive invoices from customers, freight forwarders and customs offices. It is thus possible to assess accurate profitability as costs and revenue elements linked to Trading Contract.

Position Management enables you to make association link between sales side item and purchase side item with pre-defined selection group as a portfolio. It also enables you to recognize position quantity and open quantity in order to reduce risk of position (such as having goods in stock).

Trading Contract

Trading Contract (TC) enables you to implement various business patterns by integrating sales order and purchase order. You can, for example, create the following types of Trading Contract:

Purchasing-side Trading Contract

Sales-side Trading Contract

Two-sided Trading Contract

By using the trading contract, you can maintain related data on both sales and purchase side simultaneously in one contract. If sales and purchase process carried out separately, it can be used as one-side contract such as purchase side only contract or sales side only contract. It also used as a pre-contract or long term contract for sales and purchase activities.

The document flow shows links of all related documents and gives you full control over purchases, sales, expenses and subordinate logistics documents. For sizing, please refer to section 3.2.1 Sizing for TC and 3.2.2 Sizing for TC Line Items.


Trading Execution Workbench (TEW) provides one unified interface to trigger and process several kinds of logistic documents such as Outbound Delivery, Inbound Delivery, Goods Receipt, and other logistic documents. As the advantage of using TEW, variety of business processes which depend on the customer requirements can be defined and mapped to the system document in flexible way.

For using TEW, trading contract is the basis document to control entire business processes. For sizing, please refer to section 3.2.3 Sizing for TEW (Optional).


Copyright/Trademark

3 3

1.2 ARCHITECTURE OF GLOBAL TRADE MANAGEMENT Figure 1 shows the architecture of SAP Global Trade Management in SAP ERP Central Component (SAP ECC) 6.0. This component contains the concept of separate layers, Core 6.00 and Extension Sets 6.00. SAP Global Trade Management (GTM) is one of the SAP ECC Extension Sets (EA-GLT). SAP GTM provides functionality to call SD and MM functions in SAP ECC Core to obtain better usability and efficiency. The sizing recommendation for using the Trading Contract is provided with the numbers of your trading contracts. From a technical point of view, TEW is a flexible tool to execute logistics processes (e.g. Outbound Delivery, Billing, Goods Receipt transactions) by calling SD and/or MM transactions so that variety of business processes can be defined and mapped based on customer’s requirements. Thus basic sizing recommendation for TEW is provided based on SD and MM functions mapped to customer’s business scenarios.

Figure 1: Architecture of SAP Global Trade Management

2. SIZING FUNDAMENTALS AND TERMINOLOGY SAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide, we assume that you are familiar with sizing fundamentals. You can find more information at http://service.sap.com/sizing Sizing Guidelines General Sizing Procedures. This section explains the most important sizing terms, as these terms are used extensively in this document.

Sizing Sizing means determining the hardware requirements of an SAP application, such as the network bandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware and database is influenced by both business aspects and technological aspects. This means that the number of users using the various application components and the data load they put on the server must be taken into account.

SAP ERP Central Component 6.0 (ECC600)

Core SAP-APPL

SAP GTM (EA-GLT) Extension Set

Sales Order Sales Contract

Trading Contract


Trading Expense

Purchase Order

Outbound Delivery

Inbound Delivery

Goods Issue

Goods Receipt

Billing

Invoice Verification

Agency Document Accounting Document

Position Management

Fu

nctio

n Mo

dule

BA

PI

Ba

tch Inpu

t B

AP

I

Function M

odu

le / Class

Function M

odu

le


Copyright/Trademark

4 4

Benchmarking Sizing information can be determined using SAP Standard Application Benchmarks and scalability tests (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizing recommendations to customers by placing a substantial load upon a system during the testing of new hardware, system software components, and relational database management systems (RDBMS). All performance data relevant to the system, user, and business applications are monitored during a benchmark run and can be used to compare platforms.

SAPS The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. It is derived from the Sales and Distribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully business processed order line items per hour. (For more information about SAPS, see http://www.sap.com/benchmark Measuring in SAPS).

Initial Sizing Initial sizing refers to the sizing approach that provides statements about platform-independent requirements of the hardware resources necessary for representative, standard delivery SAP applications. The initial sizing guidelines assume optimal system parameter settings, standard business scenarios, and so on.

Expert Sizing This term refers to a sizing exercise where customer-specific data is being analyzed and used to put more detail on the sizing result. The main objective is to determine the resource consumption of customized content and applications (not SAP standard delivery) by comprehensive measurements. For more information, see http://service.sap.com/sizing Sizing Guidelines General Sizing Procedures Expert Sizing.

Configuration and System Landscaping Hardware resource and optimal system configuration greatly depend on the requirements of the customer-specific project. This includes the implementation of distribution, security, and high availability solutions by different approaches using various third-party tools. In the case of high availability through redundant resources, for example, the final resource requirements must be adjusted accordingly. There are some "best practices" which may be valid for a specific combination of operating system and database. To provide guidance, SAP created the NetWeaver configuration guides (http://service.sap.com/instguides SAP NetWeaver).

3. INITIAL SIZING FOR SAP GLOBAL TRADE MANAGEMENT The current focus for sizing examples below lies mainly on the Trading Contract and additional information of the TEW part as an option. From application point of view, GTM is the module that executes both SD and MM functions in background. To implement GTM into your environment, it is recommended for you to recognize that SAPS (for GTM) is slightly larger than SAPS for SD and/or MM module because GTM calls SD and/or MM functions.

3.1 ASSUMPTIONS For sizing, we assume business scenario as followings.

Scenarios to be measured for Trading Contracts are:

1) Creating TC (one TC contains five items),

2) Changing TC (change TC status)

Scenarios to be measured for TEW are not defined here as variety of business processes can be defined based on customer’s requirements in TEW.

Trading Expense and Position Management are out of scope in this sizing document.


Copyright/Trademark

5 5

3.2 SIZING GUIDELINE To calculate SAPS for GTM server(s) following points need to be considered:

Basic SAPS for TC is measured by TC transaction volume at peak time with five items in each TC (Section 3.2.1).

In case a business scenario requires TC with more/less than five items, please adjust the value of SAPS (Section 3.2.2).

In addition, when TEW is implemented, it is necessary to calculate SD and/or MM sizing for the basement value to calculate SAPS for TEW (Section 3.2.3).

3.2.1 SIZING FOR TC The sizing for TC is based on the number of Trading Contract processed per hour at peak time. Theoretically, to process TCs without wait time (in other words, process TC sequentially without interrupting or pausing) following SAPS figure is obtained (Table 1). The figure is calculated with 5 items for each TC. This statement is under the assumption that the CPU should run at 65% average system load of the productive system.

Table 1 : SAPS for Peak Time (GTM on ECC6.0)

Category Up to Total Number of TC per Hour Minimum SAPS for GTM

Small 1,000 270 SAPS

Medium 5,000 1,350 SAPS

Large 10,000 2,700 SAPS

X-Large 20,000 5,400 SAPS

The main memory depends on the number of active, parallel working users and the number of TC items. The figure is again calculated with 5 items for each TC(Table 2). In general, the main memory is administrated internally by 4 MByte blocks on the workload. This means this restriction has to be taken into account during the calculation of the memory. Additionally a buffer offset of 2 GBytes is added. The main memory can be considered for the creation or change of the Trading Contract.


Copyright/Trademark

6 6

Table 2 : Main Memory (GTM on ECC6.0)

Category Up to Number of User Main Memory for GTM

Small 1 2,017 MB

Medium 10 2,170 MB

Large 25 2,420 MB

X-Large 100 3,650 MB

The disk size depends on the number of Trading Contracts created per week, the number of TC items and the retention period: The figure is calculated for different numbers of Trading Contracts created per week with 5 items for each TC and a retention period of 52 weeks(Table 3). The disk size has to be considered only in case of the creation of the Trading Contract.

Table 3 : Minimum Disk Size (GTM on ECC6.0)

Category Up to Total Number of TC per Week Minimum Disk Size for GTM

Small 1,000 2 GB

Medium 10,000 16 GB

Large 50,000 82 GB

X-Large 100,000 164 GB

3.2.2 SIZING FOR TC LINE ITEMS For sizing, we assume that it is necessary to consider average line items per document. To reflect the number of line items in TC, multiply factors to SAPS figures. As the number of TC items increase, the number of SAPS also increases accordingly. We assume that the CPU should run at 65% average system load of a productive system. By doing approximation line items for each TC, following figures are obtained (Table 4).


Copyright/Trademark

7 7

Table 4 : SAPS for Peak Time with Item Dependency (GTM on ECC6.0)

Category Up to

Number of TC per Hour

Minimum SAPS for GTM

1 Item 10 Items 20 Items 50 Items 100 Items

Small 1,000 171 393 641 1,383 2,620

Medium 5,000 853 1,967 3,204 6,914 13,100

Large 10,000 1,707 3,933 6,407 13,829 26,200

X-Large 20,000 3,414 7,867 12,814 27,657 52,395

If you need to create TC with more than 100 items on regular basis, please contact with SAP consultant. For sizing the main memory depends on the number of TC items. In this table you see the values based of the combination of users and items(Table 5).

Table 5 : Main Memory with Item Dependency (GTM on ECC6.0)

Category Up to

Number of User

Minimum Main Memory for GTM [MB]


Small 1 2,017 2,017 2,017 2,025 2,025

Medium 10 2,170 2,170 2,170 2,250 2,250

Large 25 2,420 2,420 2,420 2,610 2,610

X-Large 100 3,650 3,650 3,650 4,450 4,450

The disk size depends also on the number of TC items.


Copyright/Trademark

8 8

Table 6 : Disk Size with Item Dependency (GTM on ECC6.0)

Category Up to Total

Number of TC per week

Minimum Disk Size for GTM [GB]


Small 1,000 1 3 5 12 22

Medium 10,000 8 27 48 112 220

Large 50,000 40 135 240 557 1086

X-Large 100,000 79 269 481 1115 2171

3.2.3 SIZING FOR TEW (OPTIONAL) Note that it is not possible to measure exactly SAPS for TEW because variety of business processes can be defined in TEW according to customer business scenarios. For sizing of TEW, please consider following conditions.

TEW consume relatively large resources such as CPU times, memories, network traffics and database accesses because of its usability and flexibility.

For usability, TEW first screen uses complex GUIs (from technical point of view, each control objects equal to very small screens and many small screens are included in main screen). It consumes above resources.

Before (and after) TEW executes transactions, some ABAP classes are called to realize user specific requirements within the TEW program. It also costs hardware resources.

Within TEW, other programs such as SD and MM programs are called with using “CALL TRANSACTION”. It consumes more resources than calling them directly.

At a rough estimate, SAPS for TEW can be calculated as follows;

For existing SAP customer: If you already use SD and/or MM, consider SD and/or MM transactions onto Quick-Sizer, estimate the SAPS figure and multiply it by 1.3.

For new customers: Estimate how many SD and/or MM documents will be created at first. By considering SD and/or MM transactions onto Quick-Sizer, SAPS figure can be estimated by multiplying it by 1.3.

This means, 30% more SAPS is required when SD and/or MM documents are processed from TEW. To refer to SAPS, include the following link: SAPS is a hardware-independent unit to describe the CPU-related performance characteristic of a given hardware configuration. For more information on SAPS and their equivalent in hardware performance, see www.sap.com/benchmark -> SAPS.


Copyright/Trademark

9 9

4. MISCELLANEOUS Note that sizing information is our recommendation, which results from observed data at a certain environment. In case any additional suggestion is necessary for sizing data of GTM into your environment, please contact with SAP consultants or sales representatives.

5. COMMENTS AND FEEDBACK Both comments and feedback are very welcome; please send them to Yoshikazu Miyake, SAP AG [email protected] or Markus Urbanek, SAP AG [email protected].

sg gtm ecc600 aug2012b

Documents