Assumptions
SAP Inventory Manager allows remote employees to access, complete, and manage warehouse or inventory documents and information via mobile devices. It enables them to carry out their daily functions without being tied to a certain location and machine.
The synchronization or download operation executes the client operations, also known as transactions. These transactions include device initiated downloads, updates, and insert operations. The device then sends requests and transaction data to the SAP Mobile Platform for processing. The fetch operation starts and the requested documents are sent to the device.
This described process is performed by users regularly and utilizes much of the server resources. Therefore, it makes a good candidate for a sizing exercise.
-
The resource consumption of a sync or fetch process in SAP Inventory Manager depends on the volume of data that is handled by the back-end servers. Therefore, a throughput based sizing is applied in this guide.
-
All sizing data in this document is related to client-initiated syncs. If heavy volumes of scheduled or on demand pushes are required, more detailed analysis and implementation-specific performance testing is recommended.
-
Purchase order documents were downloaded to measure the performance for the sizing guide. The following table shows the amount of data per user, per download.
| Type of Data | Number of Records |
|---|---|
| Purchase orders | 400 |
| Number of items per purchase order | 10 |